Karmic Hangs on Lenovo Y530

Bug #486300 reported by Whiteknight on 2009-11-21
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
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-xorg-video-intel-2.4 drivers as I saw recommended in one similar bug report with no success. If anything the computer became less stable. I have also tried disabling certain compiz effects and even shut down compiz entirely with no success, following advice in another ticket.

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(NETDEV_UP): wlan0: link is not ready
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(NETDEV_CHANGE): wlan0: link becomes ready
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/buildd/linux-2.6.31/arch/x86/kernel/check.c:134 check_for_bios_corruption+0xe5/0x100()
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_codec_intelhdmi snd_hda_codec_si3054 arc4 snd_hda_codec_realtek ecb iwlagn iwlcore mac80211 snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm iptable_filter ip_tables x_tables snd_seq_dummy uvcvideo snd_seq_oss snd_seq_midi snd_rawmidi videodev v4l1_compat snd_seq_midi_event v4l2_compat_ioctl32 ricoh_mmc snd_seq snd_timer snd_seq_device sdhci_pci sdhci cfg80211 psmouse serio_raw snd soundcore snd_page_alloc sbp2 asus_laptop lp led_class parport fbcon tileblit font bitblit softcursor ohci1394 ieee1394 tg3 i915 drm i2c_algo_bit intel_agp video output
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] [<ffffffff8105e788>] warn_slowpath_common+0x78/0xb0
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050279] [<ffffffff8105e81c>] warn_slowpath_fmt+0x3c/0x40
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050283] [<ffffffff810366a5>] check_for_bios_corruption+0xe5/0x100
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050287] [<ffffffff810366c0>] ? check_corruption+0x0/0x30
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050291] [<ffffffff810366c9>] check_corruption+0x9/0x30
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050295] [<ffffffff810737a5>] run_workqueue+0x95/0x170
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050299] [<ffffffff81073924>] worker_thread+0xa4/0x120
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050302] [<ffffffff81078b30>] ? autoremove_wake_function+0x0/0x40
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050306] [<ffffffff81073880>] ? worker_thread+0x0/0x120
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050309] [<ffffffff81078746>] kthread+0xa6/0xb0
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050313] [<ffffffff810130ea>] child_rip+0xa/0x20
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050316] [<ffffffff810786a0>] ? kthread+0x0/0xb0
Nov 20 20:01:32 Terra-Linux kernel: [ 61.050319] [<ffffffff810130e0>] ? child_rip+0x0/0x20
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

Whiteknight (wknight8111) wrote :

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.
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-xorg-video-intel.2.4 and then upgrading again to xserver-xorg-video-intel.

Whiteknight (wknight8111) wrote :
Download full text (3.6 KiB)

Here's the output of dmesg from this morning. Shows a similar event:

[ 61.044961] WARNING: at /build/buildd/linux-2.6.31/arch/x86/kernel/check.c:134 check_for_bios_corruption+0xe5/0x100()
[ 61.044964] Hardware name: INVALID
[ 61.044965] Memory corruption detected in low memory
[ 61.044967] Modules linked in: binfmt_misc ppdev joydev snd_hda_codec_intelhdmi snd_hda_codec_si3054 snd_hda_codec_realtek arc4 ecb snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss iwlagn iwlcore snd_mixer_oss mac80211 iptable_filter snd_pcm uvcvideo snd_seq_dummy videodev v4l1_compat v4l2_compat_ioctl32 ip_tables x_tables snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device psmouse serio_raw sdhci_pci sdhci ricoh_mmc cfg80211 snd soundcore snd_page_alloc sbp2 lp parport asus_laptop led_class fbcon tileblit font bitblit softcursor ohci1394 tg3 ieee1394 i915 drm i2c_algo_bit intel_agp video output
[ 61.045021] Pid: 9, comm: events/0 Not tainted 2.6.31-15-generic #50-Ubuntu
[ 61.045023] Call Trace:
[ 61.045029] [<ffffffff8105e788>] warn_slowpath_common+0x78/0xb0
[ 61.045033] [<ffffffff8105e81c>] warn_slowpath_fmt+0x3c/0x40
[ 61.045037] [<ffffffff810366a5>] check_for_bios_corruption+0xe5/0x100
[ 61.045040] [<ffffffff810366c0>] ? check_corruption+0x0/0x30
[ 61.045044] [<ffffffff810366c9>] check_corruption+0x9/0x30
[ 61.045049] [<ffffffff810737a5>] run_workqueue+0x95/0x170
[ 61.045052] [<ffffffff81073924>] worker_thread+0xa4/0x120
[ 61.045056] [<ffffffff81078b30>] ? autoremove_wake_function+0x0/0x40
[ 61.045060] [<ffffffff81073880>] ? worker_thread+0x0/0x120
[ 61.045063] [<ffffffff81078746>] kthread+0xa6/0xb0
[ 61.045067] [<ffffffff810130ea>] child_rip+0xa/0x20
[ 61.045070] [<ffffffff810786a0>] ? kthread+0x0/0xb0
[ 61.045073] [<ffffffff810130e0>] ? child_rip+0x0/0x20
[ 61.045075] ---[ end trace 2ccf769ad2edf493 ]---
[ 131.161807] tg3 0000:01:00.0: PME# disabled
[ 131.173028] tg3 0000:01:00.0: irq 30 for MSI/MSI-X
[ 131.228284] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 131.270204] wlan0: deauthenticating by local choice (reason=3)
[ 131.570208] Registered led device: iwl-phy0::radio
[ 131.570253] Registered led device: iwl-phy0::assoc
[ 131.570295] Registered led device: iwl-phy0::RX
[ 131.570336] Registered led device: iwl-phy0::TX
[ 131.611615] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 167.334967] Registered led device: iwl-phy0::radio
[ 167.334986] Registered led device: iwl-phy0::assoc
[ 167.335004] Registered led device: iwl-phy0::RX
[ 167.335020] Registered led device: iwl-phy0::TX
[ 167.393746] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 212.906180] wlan0: authenticate with AP 00:1f:33:e7:18:51
[ 212.908564] wlan0: authenticated
[ 212.908569] wlan0: associate with AP 00:1f:33:e7:18:51
[ 212.913425] wlan0: RX AssocResp from 00:1f:33:e7:18:51 (capab=0x431 status=0 aid=2)
[ 212.913435] wlan0: associated
[ 212.936283] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 223.540046] wlan0: no IPv6 routers present
[ 241.040131] Corrupted low memory at ffff880000005e08 (5e08 phys) = 17001200000000
[ 241.040141] Corrupted low memory at ffff880000005...

Read more...

Whiteknight (wknight8111) wrote :

Here's my kern.log from this morning. A few interesting points:

11:02, "BUG: unable to handle kernel paging request at ffff880085200000". This started a long series of errors that say "BUG: scheduling while atomic: Xorg/1286/0x10000001". Several of these popped up between 11:02 and 11:04

11:04, corrupted low memory warnings leading up to a freeze. I had to hard reboot the system.

11:09, more corrupted low memory warnings leading to a WARNING and a backtrace

15:59, same

16:04, more corrupted low memory warnings, but didn't create a backtrace or a freeze (I'm still on the same session and running OK)

Whiteknight (wknight8111) wrote :

It's been several days without so much as a confirmation that another human has even read this report. In the interim, the state of my computer has steadily decreased and is now essentially unusable. I sincerely want to get this issue resolved not only so I can use the system again, but so that other people who run into these kinds of problems can get them resolved quickly as well.

Without any direction, I've been trying to post logfiles that I thought were pertinent. After rebooting 7 times tonight, I have been unable to get my computer running even for long enough to post a new log. It froze twice while booting, once while running a disk check, once while logging in, twice after logging in but before I could open any applications, and the 7th time I tried my mouse didn't work and then the screen went blank with the caps lock and numlock lights flashing (which I have been lead to believe is indicative of a kernel panic).

After 7 attempts to get the computer working, I have given up and am not able to post any new logs tonight. Tomorrow I'm going to attempt a fresh install, although I'm not certain yet whether I will be re-installing Ubuntu or whether I will try something else entirely.

I also have a Y530 and ran into the exact same trouble with a clean install of Karmic (I had been running LinuxMint 7 without issues). The trouble appears to be at the kernel level. I rebuilt to a custom build of 2.6.31.6 and the freezing issues haven't been happening.

Whiteknight (wknight8111) wrote :

Thanks for the confirmation, meanasspenguin! I tried a fresh install, but the installer program did the exact same thing (randomly freezing) three times in a row before I gave up. I've since downgraded to 9.04 for now. If I work up the nerve to try the 9.10 upgrade again I will do a custom kernel build as well and see if that fixes things.

Similar problems here on my Y530.

I thought it had something to do with the upgrade process from 9.04 to 9.10, so I reinstalled from scratch. Now it's even worse than before!

David Henry (djhenry) wrote :

I also have this problem with my Y530 in Ubuntu 9.10. Other partitions on the same system with Mint 7 and Ubuntu 9.04 are not affected. I am compiling a custom kernel build now to see if that helps.

Can you please test and report if this works?

memory_corruption_check_size=128K

in the boot options.

The default is

memory_corruption_check_size=64K

but it seems that's not enough for some systems.

Thanks

If you don't know how to set BootOptions read

https://help.ubuntu.com/community/BootOptions

Also this thread is very important to anyone looking at this bug

http://linux.derkeiler.com/Mailing-Lists/Kernel/2009-07/msg04621.html

Simon Quigley (tsimonq2) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 486300

and any other logs that are relevant for this particular issue.

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers