Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 60172 - Bad EIP value. - Kernel panic: Attempted to kill init! with Dimension 8300 and P4 with Hyper Threading enabled
Summary: Bad EIP value. - Kernel panic: Attempted to kill init! with Dimension 8300 an...
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: x86-kernel@gentoo.org (DEPRECATED)
URL:
Whiteboard:
Keywords: Bug
Depends on:
Blocks:
 
Reported: 2004-08-12 13:32 UTC by Fabian Köster
Modified: 2004-08-27 00:09 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fabian Köster 2004-08-12 13:32:02 UTC
I have a Dell Dimension 8300 with Pentium 4 3.0 GHz and Bios Revision A05 (latest).
When I enable Hyper Threading, sometimes I get a kernel panic with the following message:

Call Trace:
  [<c027a04c>] psmouse_interrupt+0xa3/0x2da
  [<c027cb76>] serio_interrupt+0x7b/0x7d
  [<c027d3ee>] i8042_interrupt+0xc9/0x15d
  [<c027d141>] i8042_aux_write+0x54/0x68
  [<c027a317>] psmouse_sendbyte+0x94/0x96
  [<c027a494>] psmouse_command+0x17b/0x188
  [<c027a585>] genius_detect+0x2c/0xb5
  [<c027a81f>] psmouse_extensions+0x101/0x1b9
  [<c027a931>] psmouse_probe+0x5a/0x85
  [<c027ac99>] psmouse_connect+0x102/0x27b
  [<c027c796>] serio_find_dev+0x56/0x58
  [<c027cbb3>] serio_register_port+0x3b/0x52
  [<c0574d67>] i8042_port_register+0x68/0x89
  [<c0574fd5>] i8042_init+0x18e/0x193
  [<c0574b01>] serio_init+0x1f/0x41
  [<c0560872>] do_initcalls+0x27/0xb3
  [<c013008c>] init_workqueues+0x17/0x2e
  [<c01004c3>] init+0x96/0x25b
  [<c010042d>] init+0x0/0x25b
  [<c0103271>] kernel_thread_helper+0x5/0xb

Code: Bad EIP value.
  <0>Kernel panic: Attempted to kill init!

This problem appears with every 2.6 kernel up to the newest 2.6.7-gentoo-r13, I haven't tried with 2.4.

Sometimes the system boots fine, sometimes the error mentioned above happens and sometimes an other error is shown (something with acpi, I'm not sure because it happened only a few times and I don't remember the message.)

My, a bit unnormal, workaround is to wait for the fan to slow down, because the probability for a perfect boot is higher then ( I don't know why! )


Reproducible: Sometimes
Steps to Reproduce:
1.
2.
3.

Actual Results:  
 

Expected Results:
Comment 1 Greg Kroah-Hartman (RETIRED) gentoo-dev 2004-08-13 09:33:35 UTC
Does this also happen on a stock 2.6.7 kernel from kernel.org?
Comment 2 Fabian Köster 2004-08-14 03:26:48 UTC
I'm not really sure about that, but I think so, because other distributions like SuSE and Debian Sid had similar problems.
Comment 3 Fabian Köster 2004-08-15 04:57:53 UTC
I tested the vanilla kernel from kernel.org (version 2.6.7) and it gave me that:

 printing eip:
00000000
*pde = 00000000
Oops: 0000 [#1]
PREEMPT SMP
Modules linked in:
CPU:    0
EIP:    0060:[<00000000>] Not tainted
EFLAGS: 00010206 (2.6.7)
EIP is at 0x0
eax: c0595fb8 ebx: ftc02000 ecx: 00000000 edx: 000000fa
input: PS/2 Generic Mouse on isa0060/serio1
esi: 000000 edi: 000000fa ebp: c0504740 esp: c0597f68
ds: 007b es: 007b ss: 0068
Process kirqd (pid: 43, thread info=c0597000 task=f7dcd260)
Stack: c032f3d0 f7c02000 c0595fb8 <6>serio: i8042 KBD port at 0x60,0x64 irq1
c0595fb8 c0105a50 0000003f 000000fa 000000fa
    000000fa c0595fb8 c0331efa c0504740 000000fa 00000000 c0595fb8 0000003d
    00000020 c0332772 c0504740 000000fa 00000000 c0595fb8 c1bb7828 04000001
Call Trace:
Stack pointer is garbage, not printing trace
Code: Bad EIP value.
 <0> Kernel panic: Fatal exception in interrupt
In Interrupt handler - not syncing

Maybe there are some copy mistakes - sorry for that - but I don't know how to handle it digital. Is it possible to capture the kernel-log over serial-port on a second computer or something?
Comment 4 Fabian Köster 2004-08-15 04:59:55 UTC
By the way: It works fine with Windows XP - so it can't be any hardware defect
Comment 5 Greg Kroah-Hartman (RETIRED) gentoo-dev 2004-08-16 00:35:44 UTC
Ok, please try the 2.6.8 kernel, and if that still gives you the same error, 
report it at bugzilla.kernel.org, as it's an upstream bug, nothing we can 
do about it here from the gentoo side, sorry.
Comment 6 Fabian Köster 2004-08-16 02:51:31 UTC
Same problem with 2.6.8

Doesn't matter, thanks for help.
Comment 7 Fabian Köster 2004-08-27 00:09:12 UTC
Installed Debian Sarge just now and it seems as if it doesn't has the problem - so there must be a patch.