Karmic Hangs on Lenovo Y530
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: ubiquity
Computer is Lenovo Y530, 64-bit Intel Core2 duo.
I upgraded to Karmic from Jaunty following the official release and my system has become significantly less stable because of it. In Jaunty there were absolutely no problems to speak of. Now in Karmic my system is very unstable: It will randomly freeze while I am using it, whether I am actively using it or letting it sit. Sometimes it will randomly reboot, especially on occasions when I close and open the laptop lid again. Very often it will hang or spontaneously reboot during the boot or login sequences.
When I say "freeze" or "hang", I mean that the visual display freezes and the computer becomes absolutely unresponsive to keyboard or mouse input. When this happens the only solution I have found is to hard reboot the computer.
My laptop has integrated Intel graphics. I tried downgrading to xserver-
Another thread I saw suggested uninstalling network-manager and replacing it with wicd. Same problems. I looked in /etc/log/debug and /etc/log/kern.log and saw that at the last time when the system hung it was doing something with wlan0, so I was hoping this would solve my problem. It didn't.
I'm not sure what information about my system the developers need to see. I'll post some log excerpts that I saw that I thought looked interesting, please let me know if I need to post anything else.
Entries in /etc/log/debug when it crashed last night before I went to bed:
Nov 20 20:02:59 Terra-Linux kernel: [ 147.670033] wlan0: no IPv6 routers present
Nov 20 20:03:23 Terra-Linux kernel: [ 171.910073] wlan0: no probe response from AP 00:1f:33:e7:18:51 - disassociating
Nov 20 20:04:35 Terra-Linux kernel: [ 243.835819] wlan0: authenticate with AP 00:1f:33:e7:18:51
Nov 20 20:04:35 Terra-Linux kernel: [ 243.841078] wlan0: authenticated
Nov 20 20:04:35 Terra-Linux kernel: [ 243.841088] wlan0: associate with AP 00:1f:33:e7:18:51
Nov 20 20:04:35 Terra-Linux kernel: [ 243.845756] wlan0: RX AssocResp from 00:1f:33:e7:18:51 (capab=0x431 status=0 aid=1)
Nov 20 20:04:35 Terra-Linux kernel: [ 243.845764] wlan0: associated
Nov 20 20:04:45 Terra-Linux kernel: [ 254.510026] wlan0: no IPv6 routers present
Nov 20 20:43:41 Terra-Linux kernel: [ 2591.010120] wlan0: no probe response from AP 00:1f:33:e7:18:51 - disassociating
Nov 20 20:44:48 Terra-Linux kernel: [ 2657.927465] wlan0: authenticate with AP 00:1f:33:e7:18:51
Nov 20 20:44:48 Terra-Linux kernel: [ 2657.932243] wlan0: authenticated
Nov 20 20:44:48 Terra-Linux kernel: [ 2657.932252] wlan0: associate with AP 00:1f:33:e7:18:51
Nov 20 20:44:48 Terra-Linux kernel: [ 2657.936793] wlan0: RX ReassocResp from 00:1f:33:e7:18:51 (capab=0x431 status=0 aid=1)
Nov 20 20:44:48 Terra-Linux kernel: [ 2657.936802] wlan0: associated
Here's /etc/log/kern.log from approximately the same time period:
Nov 20 20:04:29 Terra-Linux kernel: [ 237.823402] ADDRCONF(
Nov 20 20:04:35 Terra-Linux kernel: [ 243.835819] wlan0: authenticate with AP 00:1f:33:e7:18:51
Nov 20 20:04:35 Terra-Linux kernel: [ 243.841078] wlan0: authenticated
Nov 20 20:04:35 Terra-Linux kernel: [ 243.841088] wlan0: associate with AP 00:1f:33:e7:18:51
Nov 20 20:04:35 Terra-Linux kernel: [ 243.845756] wlan0: RX AssocResp from 00:1f:33:e7:18:51 (capab=0x431 status=0 aid=1)
Nov 20 20:04:35 Terra-Linux kernel: [ 243.845764] wlan0: associated
Nov 20 20:04:35 Terra-Linux kernel: [ 243.849805] ADDRCONF(
Nov 20 20:04:45 Terra-Linux kernel: [ 254.510026] wlan0: no IPv6 routers present
Nov 20 20:43:41 Terra-Linux kernel: [ 2591.010120] wlan0: no probe response from AP 00:1f:33:e7:18:51 - disassociating
Nov 20 20:44:48 Terra-Linux kernel: [ 2657.927465] wlan0: authenticate with AP 00:1f:33:e7:18:51
Nov 20 20:44:48 Terra-Linux kernel: [ 2657.932243] wlan0: authenticated
Nov 20 20:44:48 Terra-Linux kernel: [ 2657.932252] wlan0: associate with AP 00:1f:33:e7:18:51
Nov 20 20:44:48 Terra-Linux kernel: [ 2657.936793] wlan0: RX ReassocResp from 00:1f:33:e7:18:51 (capab=0x431 status=0 aid=1)
Nov 20 20:44:48 Terra-Linux kernel: [ 2657.936802] wlan0: associated
Shortly before that, I see this snippet in /etc/log/kern.log that looks scary:
Nov 20 20:03:32 Terra-Linux kernel: [ 181.040153] Corrupted low memory at ffff880000001988 (1988 phys) = 00005018
Nov 20 20:03:32 Terra-Linux kernel: [ 181.040164] Corrupted low memory at ffff880000001c28 (1c28 phys) = 46001300000000
Nov 20 20:03:32 Terra-Linux kernel: [ 181.040171] Corrupted low memory at ffff880000001c78 (1c78 phys) = 0000006d
Nov 20 20:03:32 Terra-Linux kernel: [ 181.040180] Corrupted low memory at ffff880000003d78 (3d78 phys) = 0000009f
Nov 20 20:03:32 Terra-Linux kernel: [ 181.040186] Corrupted low memory at ffff880000003dd0 (3dd0 phys) = 00000910
Nov 20 20:03:32 Terra-Linux kernel: [ 181.040193] Corrupted low memory at ffff8800000040d8 (40d8 phys) = 3008700120093
Nov 20 20:03:32 Terra-Linux kernel: [ 181.040199] Corrupted low memory at ffff8800000040e0 (40e0 phys) = 886009308920097
Nov 20 20:03:32 Terra-Linux kernel: [ 181.040204] Corrupted low memory at ffff8800000040e8 (40e8 phys) = 13009300470013
Nov 20 20:03:32 Terra-Linux kernel: [ 181.040212] Corrupted low memory at ffff880000004e78 (4e78 phys) = 000000ff
Nov 20 20:03:32 Terra-Linux kernel: [ 181.040220] Corrupted low memory at ffff880000005e10 (5e10 phys) = 13000600170012
Nov 20 20:03:32 Terra-Linux kernel: [ 181.040226] Corrupted low memory at ffff880000005e20 (5e20 phys) = 12009200000000
Nov 20 20:03:32 Terra-Linux kernel: [ 181.040232] Corrupted low memory at ffff880000005e68 (5e68 phys) = 0000fc00
Nov 20 20:03:32 Terra-Linux kernel: [ 181.040238] Corrupted low memory at ffff880000005e78 (5e78 phys) = 0000ff00
About a minute before that, I see this similar sequence (with backtrace!):
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050139] Corrupted low memory at ffff880000004138 (4138 phys) = 882008600060096
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050146] Corrupted low memory at ffff880000004268 (4268 phys) = 803088300000000
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050152] Corrupted low memory at ffff880000005e08 (5e08 phys) = 97000200830016
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050156] Corrupted low memory at ffff880000005e10 (5e10 phys) = 17009600030096
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050160] Corrupted low memory at ffff880000005e68 (5e68 phys) = 0000fd00
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050163] ------------[ cut here ]------------
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050174] WARNING: at /build/
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050179] Hardware name: INVALID
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050181] Memory corruption detected in low memory
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050184] Modules linked in: binfmt_misc ppdev joydev snd_hda_
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050268] Pid: 9, comm: events/0 Not tainted 2.6.31-15-generic #50-Ubuntu
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050270] Call Trace:
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050276] [<ffffffff8105e
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050279] [<ffffffff8105e
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050283] [<ffffffff81036
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050287] [<ffffffff81036
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050291] [<ffffffff81036
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050295] [<ffffffff81073
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050299] [<ffffffff81073
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050302] [<ffffffff81078
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050306] [<ffffffff81073
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050309] [<ffffffff81078
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050313] [<ffffffff81013
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050316] [<ffffffff81078
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050319] [<ffffffff81013
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050322] ---[ end trace 6430df1305f77287 ]---
Nothing else looks interesting (to me) in other log files. I'll be happy to post more info if needed
I've attached my /etc/log/syslog. It contains some more information
General Timeline:
Last night (Nov 20th) the computer froze so I shut it off and went to bed. The last entries on Nov20th should be around that time. xorg-video- intel.2. 4 and then upgrading again to xserver- xorg-video- intel.
This morning, It froze several times, though I didn't keep track of when. This morning I tried uninstalling network-manager, replacing it with wicd, downgrading my video driver to xserver-