Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 312767 - sys-kernel/gentoo-sources-2.6.31-r10 BUG on shutdown (kernel/time/clockevents.c:262)
Summary: sys-kernel/gentoo-sources-2.6.31-r10 BUG on shutdown (kernel/time/clockevents...
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-02 09:10 UTC by David Ward
Modified: 2010-04-23 12:35 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
.config (as requested) (.config,66.29 KB, text/plain)
2010-04-04 12:11 UTC, David Ward
Details
.config (as requested) (.config,66.29 KB, text/plain)
2010-04-04 12:11 UTC, David Ward
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Ward 2010-04-02 09:10:34 UTC
while trying to shut down my x86 machine (kernel 2.6.31-gentoo-r10) a kernel BUG occurs, I have the framebuffer device installed and can see the whole kernel BUG message.  The jist of the message is as follows:

kernel BUG at kernel/time/clockevents.c:262
invalid opcode: 0000 [#1] SMP
last sysfs file: /sys/devices/pci0000:00/0000:00:1f.1/host0/target0:0:0/0:0:0:0/block/sda/uvent
Modules linked in: snd_intel8x0 snd_ac97_codec ac97_bus
Pid: 5249, comm: halt Not tainted (2.6.31-gentoo-r10 #4)
...
/etc/init.d/shutdown.sh: line 9:  5249 Segmentation fault         /sbin/halt "${opts}"

the same last line appeared even when I did not have framebuffer, alsa modules, or anything else installed.  I have been told that backporting my kernel will solve this issue, but am not comfortable with doing so.  this is on an intel pentium 4.

Reproducible: Always

Steps to Reproduce:
1. login
2. send a command that is supposed to halt the machine (ie. 'poweroff')
3. After Remounting remaining filesystems readonly kernel bug appears

Actual Results:  
Computer does not halt, filesystems not unmounted, often resulting in fsck being run on next boot.

Expected Results:  
The computer is supposed to halt
Comment 1 Andreas K. Hüttel archtester gentoo-dev 2010-04-02 09:52:02 UTC
Who told you to backport what? 

Please post your .config. 

What's the last script output before the BUG?
Comment 2 David Ward 2010-04-02 10:18:11 UTC
post my .config here, or in a pastebin?
also it happens immediately after 'remounting remaining filesystems readonly'
Comment 3 David Ward 2010-04-04 12:11:06 UTC
Created attachment 226541 [details]
.config (as requested)
Comment 4 David Ward 2010-04-04 12:11:32 UTC
Created attachment 226543 [details]
.config (as requested)
Comment 5 Mike Pagano gentoo-dev 2010-04-08 23:13:19 UTC
This is reported to be fixed in 2.6.32.  Can you upgrade your kernel and test?

I've also seen that the kernel parameter nolapic provides a workaround for 2.6.31.