Andreas Jaeger
Same problem on the FSC V810. When is this CD available?? We need it!
It's on ftp.suse.com, so it should be on all the mirrors soon...
Download it e.g. from:
ftp://ftp.gwdg.de/pub/linux/suse/ftp.suse.com/people/aj/PatchCD
The FSC V810 has also another problem - a BIOS problem. This one cannot be fixed with the new kernel. As soon as I know more, I'll tell here,
Ok, I tried that patch CD on a Fujitsu Siemens CELSIUS V810 and the kernel panic is still there: mtrr: v2.0 (20020519) general protection fault: 0000 [1] SMP CPU 1 Modules linked in: Pid: 0, comm: swapper Tainted: MG (2.6.8-24.10-smp SL92_BRANCH-200412221154270000) RIP: 0010:[<ffffffff8011a93e>] <ffffffff8011a93e>{generic_set_all+318} RSP: 0018:000001007ffabf48 EFLAGS: 00010006 RAX: 000000001e1e1e1e RBX: 0000000000000000 RCX: 0000000000000250 RDX: 000000001e1e1e1e RSI: 0000000000000000 RDI: 0000000000000000 RBP: 0000000000000008 R08: 0000000006060606 R09: ffffffff8045df88 R10: 0000000000000000 R11: 0000000006060606 R12: 0000000000000000 R13: 0000000000000008 R14: 00000100cfeec7c0 R15: 0000000000000c00 FS: 0000000000000000(0000) GS:ffffffff804e2e80(0000) knlGS:0000000000000000 CS: 0010 DS: 0018 ES: 0018 CR0: 00000000c005003b CR2: 0000000000000000 CR3: 00000000cff02000 CR4: 0000000000000060 Process swapper (pid: 0, threadinfo 000001007ffa2000, task 0000010037e0b030) Stack: ffffffff804e3c10 00000100cff01ed8 0000000000000001 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ffffffff8011947b 0000000000000000 0000000000000006 Call Trace:<IRQ> <ffffffff8011947b>{ipi_handler+75} <ffffffff8011c940>{smp_call_function_interrupt+64} <ffffffff8010f5c0>{default_idle+0} <ffffffff80110f2f>{call_function_interrupt+99} <EOI> <ffffffff8010f5e0>{default_idle+32} <ffffffff8010f9ea>{cpu_idle+26} Code: 0f 30 41 ba 01 00 00 00 31 ff 8d 8f 58 02 00 00 0f 32 41 89 RIP <ffffffff8011a93e>{generic_set_all+318} RSP <000001007ffabf48> <0>Kernel panic - not syncing: Aiee, killing interrupt handler! NMI Watchdog detected LOCKUP on CPU0, registers: CPU 0 Modules linked in: Pid: 1, comm: swapper Tainted: MG (2.6.8-24.10-smp SL92_BRANCH-200412221154270000) RIP: 0010:[<ffffffff80119580>] <ffffffff80119580>{set_mtrr+208} RSP: 0000:00000100cff01ec8 EFLAGS: 00000002 RAX: 0000000000000001 RBX: 00000000ffffffff RCX: 0000000000000002 RDX: 0000ffff0000ffff RSI: 0000000000000000 RDI: ffffffff8045e110 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000040000 R11: 0000000000000000 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffffffff804e2e00(0000) knlGS:0000000000000000 CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b CR2: 0000000000000000 CR3: 0000000000101000 CR4: 00000000000006e0 Process swapper (pid: 1, threadinfo 00000100cff00000, task 0000010037e0b7e0) Stack: ffffffff8040e080 0000000000000246 0000000100000001 0000000000000000 0000000000000000 00000100ffffffff 0000000000000000 0000000000000008 0000000000000000 0000000000000000 Call Trace:<ffffffff804f11a0>{mtrr_init+352} <ffffffff8010c2f2>{init+514} <ffffffff8011129f>{child_rip+8} <ffffffff8010c0f0>{init+0} <ffffffff80111297>{child_rip+0} Code: f3 90 8b 44 24 10 85 c0 75 f6 be 08 00 00 00 48 c7 c7 10 e1 console shuts up ... I still wonder how the BIOS shall be involved with that. Since the problem is also occuring on other distributions I tried it out on Fedora Core 3 and installed kernels from kernel.org. Doing this the panic occurs in Kernel 2.6.9 from kernel.org, a vanilla 2.6.8 still boots on FC3 but with some Ooopses. The weird thing is that I don't see much that changed in the sources of the MTRR routines and I really don't see a difference that can cause that trouble here. So I guess there is a change somewhere else that affects our system. It really looks weird, kernels up to 2.6.8 (vanilla) are booting on FC3, so its difficult to explain to our customers that this should be a BIOS issue. Do you have an idea how we can get closer to that bug? If its really a BIOS issue I would love to tell it to the BIOS developer, but at the moment I don't have enough hard data to tell him things like "Kernel is issueing a BIOS call, BIOS is messing up" or something else. Regards Rainer -- Dipl.-Inf. (FH) Rainer Koenig Project Manager Linux Fujitsu Siemens Computers VP BC E SW OS Phone: +49-821-804-3321 Fax: +49-821-804-2131