| View previous topic :: View next topic |
| Author |
Message |
skwang
Tux's lil' helper
Joined: 12 May 2004
Posts: 149
Location: Chicago, IL
|
 Posted: Fri Mar 23, 2007 7:06 pm Post subject: ACPI suspend causes kernel panic [SOLVED] |
 |
|
When I suspend (to RAM) my notebook for a second time my kernel has a semi-panic / hicup. I'll explain in much more detail below. But first some background.
The notebook is a Lenovo T60 running and amd64 setup with gentoo-sources-2.6.19-r5. I upgraded the kernel from 2.6.18-r6 recently, and this problem started. Before I could suspend to RAM without any problems.
Now when I suspend to RAM the first time using any user-level application, i.e. acpitool or klaptop, everything works as it should.
When I go to suspend to RAM a second time, my notebook's LCD display is sent to a virtual terminal with lots of kernel output messages. My system does not freeze, and I can return to Xwindows via Ctrl-Alt-F7. When I look in dmesg or /proc/kmsg I get:
| Code: | <4>Disabling non-boot CPUs ...
<4>CPU 1 is now offline
<6>SMP alternatives: switching to UP code
<1>Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP:
<1> [<ffffffff80269a99>] __drain_pages+0x2b/0x66
<4>PGD 24f8b067 PUD 24971067 PMD 0
<0>Oops: 0000 [1] SMP
<4>CPU 0
<4>Modules linked in: snd_pcm_oss snd_mixer_oss snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device fglrx(P) tp_smapi hdaps thinkpad_ec ibm_acpi ieee80211_crypt_tkip e1000 snd_hda_intel snd_hda_codec snd_pcm snd_timer snd snd_page_alloc ipw3945 ieee80211 ieee80211_crypt intel_agp joydev
<4>Pid: 6222, comm: klaptop_acpi_he Tainted: P 2.6.19-gentoo-r5 #2
<4>RIP: 0010:[<ffffffff80269a99>] [<ffffffff80269a99>] __drain_pages+0x2b/0x66
<4>RSP: 0018:ffff810025011db8 EFLAGS: 00010046
<4>RAX: ffff81000000b800 RBX: 0000000000000046 RCX: 0000000000000000
<4>RDX: 0000000000000010 RSI: ffff81003f8df8e0 RDI: ffff81000000b400
<4>RBP: 0000000000000000 R08: 0000000000000002 R09: 0000000000000000
<4>R10: 0000000000000549 R11: 000000000000054a R12: ffff81000000b800
<4>R13: 0000000000000000 R14: 0000000000000001 R15: ffff810028d5fc80
<4>FS: 00002b6363e4b6e0(0000) GS:ffffffff8086d000(0000) knlGS:0000000000000000
<4>CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
<4>CR2: 0000000000000000 CR3: 0000000024f4f000 CR4: 00000000000006e0
<4>Process klaptop_acpi_he (pid: 6222, threadinfo ffff810025010000, task ffff8100275968b0)
<4>Stack: 0000000000000001 0000000000000001 0000000000000007 ffff810037df9060
<4> 0000000000000001 ffffffff80269ae6 ffffffff80737e10 ffffffff8024302c
<4> 0000000000000000 0000000000000001 0000000000000001 ffffffff80250d5e
<4>Call Trace:
<4> [<ffffffff80269ae6>] page_alloc_cpu_notify+0x12/0x28
<4> [<ffffffff8024302c>] notifier_call_chain+0x24/0x36
<4> [<ffffffff80250d5e>] _cpu_down+0x159/0x217
<4> [<ffffffff80251064>] disable_nonboot_cpus+0xc5/0x161
<4> [<ffffffff802564b5>] enter_state+0x8f/0x1ab
<4> [<ffffffff8025663a>] state_store+0x69/0x7d
<4> [<ffffffff802c93c2>] sysfs_write_file+0xbe/0xee
<4> [<ffffffff8028bbb2>] vfs_write+0xce/0x17a
<4> [<ffffffff8028c188>] sys_write+0x45/0x71
<4> [<ffffffff8020996e>] system_call+0x7e/0x83
<4> [<00002b6363cc4e40>]
<4>
<4>
<4>Code: 8b 75 00 4c 89 e7 e8 a1 fb ff ff c7 45 00 00 00 00 00 53 9d
<1>RIP [<ffffffff80269a99>] __drain_pages+0x2b/0x66
<4> RSP <ffff810025011db8>
<0>CR2: 0000000000000000
<4> |
I said that this causes a kernel "panic" because although the system looks to be working, I can't actually use it. For one, the kernel is set up as SMP because there are two processors (Intel Core 2 Duo). After this kernel problem, I only seem to have one precessor: cpu0. If I fire up 'top', cpu1 seems to be missing (You can see it saying "CPU1 is now offline" above). Because of this kernel hicup other strange hardware problems occur. More importantly, I can't even shutdown. When I go to 'halt' the notebook as the notebook just hangs. I have to manually power it down.
Does anyone know what is causing this problem?
What I've tried:1) Removing the different third-party modules from my system before suspending twice => doesn't work
2) Booting with 'noapic' => system freezes during boot right after message "Starting runlevel"
3) Hibernate aka suspend to disk => same problem: first time is okay, second fails
Last edited by skwang on Sat Apr 28, 2007 9:56 pm; edited 1 time in total |
|
| Back to top |
|
 |
Mcatt
n00b
Joined: 15 Apr 2007
Posts: 1
|
| Posted: Sun Apr 15, 2007 12:23 am Post subject: |
|
|
I am getting almost exactly the same error on my Acer Aspire 5634. Once again a Core 2 Duo system running amd64 gentoo-sources-2.6.19-r5.
| Quote: |
Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP:
[<ffffffff8025ab78>] __drain_pages+0x26/0x60
PGD 6f1f6067 PUD 71789067 PMD 0
Oops: 0000 [1] SMP
CPU 0
Modules linked in: snd_seq snd_pcm_oss snd_mixer_oss nvidia(P) i2c_core ipw3945 snd_hda_intel snd_hda_codec snd_pcm snd_timer snd soundcore snd_page_alloc
Pid: 6790, comm: hal-system-powe Tained: P 2.6.19-gentoo-r5 #26
RIP: 0010:[<ffffffff8025ab78>] [<ffffffff8025ab78>] __drain_pages+0x26/0x60
RSP: 0018:ffff810071a0fdc8 EFLAGS: 00010046
RAX: 0000000000000001 RBX: 0000000000000046 RCX: 0000000000000000
RDX: 0000000000000010 RSI: 0000000000000000 RDI: ffff81000000c400
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: ffff81007a8fbc38 R11: ffffffff802ab5f4 R12: ffff81000000c800
R13: 0000000000000000 R14: 0000000000000001 R15: ffff81007c07dec0
FS: 00002b366c94bda0(0000) GS:ffffffff807b4000(0000) knIGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0:000000008005003b
CR2 0000000000000000 CR3: 00000000716b4000 CR4: 00000000000006e0
Process hal-system-powe (pid: 6790, threadinfo ffff810071a0e000, task ffff81006f2a8e60)
Stack: 0000000000000001 0000000000000001 0000000000000007 ffff81007d639510
0000000000000001 ffffffff8025abc4 ffffffff806bfa10 ffffffff80556aa2
0000000000000001 0000000000000000 0000000000000001 ffffffff8024a1fc
Call Trace:
[<ffffffff8025abc4>] page_alloc_cpu_notify+0x12/0x28
[<ffffffff80556aa2>] notifier_call_chain+0x20/032
[<ffffffff8024a1fc>] _cpu_down+0x15b/0x271
[<ffffffff8024a4da>] disable_nonboot_cpus+0xaa/0x13c
[<ffffffff8024f307>] enter_state+0x8b/0x1a1
[<ffffffff8024f47d>] state_score+0x60/0x7b
[<ffffffff802b2878>] sysfs_write_file+0xba/0xee
[<ffffffff8027ac66>] vfs_write+0x45/0x6e
[<ffffffff8027b1fc>] sys_write+0x45/0x6e
[<ffffffff8020957e>] system_call+0x7e/0x83
[<00002b366c7c4e40>]
Code: 8b 75 00 4c 89 e7 e8 5b fc ff ff v7 45 00 00 00 00 00 53 9d
RIP [<ffffffff8025ab78>] __drain_pages+0x26/0x60
RSP <FFFF810071A0FDC8>
CR2: 0000000000000000
|
I also have to manually power it down, and i get the same problem with suspend to disk. |
|
| Back to top |
|
|
skwang
Tux's lil' helper
Joined: 12 May 2004
Posts: 149
Location: Chicago, IL
|
| Posted: Sun Apr 15, 2007 5:36 pm Post subject: |
|
|
| Mcatt - For now I went back to using 2.6.18-r6 which has working ACPI power features. I have not tried the new 2.6.20 (stable) amd64 kernel. |
|
| Back to top |
|
|
skwang
Tux's lil' helper
Joined: 12 May 2004
Posts: 149
Location: Chicago, IL
|
| Posted: Sat Apr 28, 2007 9:56 pm Post subject: |
|
|
| I'm happy to report that kernel version gentoo-sources-2.6.20-r7 (amd64 stable) seems to support suspend-to-RAM without and problems. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
