Re: Aiee, killing interrupt handler!
In-Reply-To: <[EMAIL PROTECTED]> On Tue, 19 Dec 2006 17:37:09 +0800, Hawk Xu wrote: > > You need to post the entire oops message, not just the last part. It should > > start with "BUG". And using a more recent kernel would be a good idea. > > > > I'm sorry, but that's all we have now. Our customer just sent us a > photo of the kernel panic screen. They need to boot in 50-line vga mode then, so more can be seen. > Our client also sent the /var/log/kernel file to us. According to the > log file, everytime before kernel panic, there are some error messages. > The server encountered kernel panic three times, below are the error > messages before each time: Those are normal when running buggy usermode code, but they should never be able to affect the kernel. -- MBTI: IXTP - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Aiee, killing interrupt handler!
In-Reply-To: [EMAIL PROTECTED] On Tue, 19 Dec 2006 17:37:09 +0800, Hawk Xu wrote: You need to post the entire oops message, not just the last part. It should start with BUG. And using a more recent kernel would be a good idea. I'm sorry, but that's all we have now. Our customer just sent us a photo of the kernel panic screen. They need to boot in 50-line vga mode then, so more can be seen. Our client also sent the /var/log/kernel file to us. According to the log file, everytime before kernel panic, there are some error messages. The server encountered kernel panic three times, below are the error messages before each time: Those are normal when running buggy usermode code, but they should never be able to affect the kernel. -- MBTI: IXTP - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Aiee, killing interrupt handler!
Chuck Ebbert wrote: Our server(running Oracle 10g) is having a kernel panic problem: <> Process swapper (pid: 0, threadinfo 80582000, task 80464300) Stack: 0296 8013f325 81007f7f54d0 0100 0001 000e 8053e098 8013f3a5 81007f7f54d0 810002c10a20 You need to post the entire oops message, not just the last part. It should start with "BUG". And using a more recent kernel would be a good idea. I'm sorry, but that's all we have now. Our customer just sent us a photo of the kernel panic screen. Our customer is running Oracle10g(64bit) and an 32-bit daemon application on our server. Our client also sent the /var/log/kernel file to us. According to the log file, everytime before kernel panic, there are some error messages. The server encountered kernel panic three times, below are the error messages before each time: 1) Dec 14 14:00:39 kf85-1 kernel: set_local_var[1886]: segfault at fffc rip 55f41d69 rsp b358 error 6 2) Dec 15 10:03:17 kf85-1 kernel: set_local_var[2459]: segfault at fffc rip 55f41d69 rsp c2e8 error 6 Dec 15 10:36:27 kf85-1 kernel: modeling[12173] trap bounds rip:806aec8 rsp:9820 error:0 Dec 15 10:51:49 kf85-1 kernel: modeling[14405]: segfault at 0008 rip 56b97e8c rsp aa78 error 6 Dec 15 11:09:14 kf85-1 kernel: set_local_var[20817]: segfault at fffc rip 55f41d69 rsp c928 error 6 Dec 15 11:16:29 kf85-1 kernel: set_local_var[21760]: segfault at fffc rip 55f41d69 rsp bd98 error 6 Dec 15 15:10:52 kf85-1 kernel: rtdb_server[17604] trap bounds rip:80f5247 rsp:5b9f9040 error:0 Dec 15 15:11:01 kf85-1 kernel: rtdb_server[18631] trap bounds rip:80f5247 rsp:58905040 error:0 Dec 15 15:11:16 kf85-1 kernel: rtdb_server[18718] trap bounds rip:80f5247 rsp:59300040 error:0 Dec 15 15:11:23 kf85-1 kernel: rtdb_server[18762] trap bounds rip:80f5247 rsp:59106040 error:0 Dec 15 15:14:17 kf85-1 kernel: rtdb_server[18869] trap bounds rip:80f5247 rsp:5b10a040 error:0 Dec 15 15:14:22 kf85-1 kernel: rtdb_server[19567] trap bounds rip:80f5247 rsp:59106040 error:0 Dec 15 15:14:32 kf85-1 kernel: rtdb_server[19586] trap bounds rip:80f5247 rsp:57903040 error:0 3) Dec 15 15:48:30 kf85-1 kernel: set_local_var[2430]: segfault at fffc rip 55f41d69 rsp c7f8 error 6 Dec 15 16:16:17 kf85-1 kernel: GFileManager[10453]: segfault at 3135 rip 574d5f99 rsp 597b3158 error 6 And I didn't figure out why the kernel panic was not in the kernel log file. Thanks! hxu - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Aiee, killing interrupt handler!
Chuck Ebbert wrote: Our server(running Oracle 10g) is having a kernel panic problem: Process swapper (pid: 0, threadinfo 80582000, task 80464300) Stack: 0296 8013f325 81007f7f54d0 0100 0001 000e 8053e098 8013f3a5 81007f7f54d0 810002c10a20 You need to post the entire oops message, not just the last part. It should start with BUG. And using a more recent kernel would be a good idea. I'm sorry, but that's all we have now. Our customer just sent us a photo of the kernel panic screen. Our customer is running Oracle10g(64bit) and an 32-bit daemon application on our server. Our client also sent the /var/log/kernel file to us. According to the log file, everytime before kernel panic, there are some error messages. The server encountered kernel panic three times, below are the error messages before each time: 1) Dec 14 14:00:39 kf85-1 kernel: set_local_var[1886]: segfault at fffc rip 55f41d69 rsp b358 error 6 2) Dec 15 10:03:17 kf85-1 kernel: set_local_var[2459]: segfault at fffc rip 55f41d69 rsp c2e8 error 6 Dec 15 10:36:27 kf85-1 kernel: modeling[12173] trap bounds rip:806aec8 rsp:9820 error:0 Dec 15 10:51:49 kf85-1 kernel: modeling[14405]: segfault at 0008 rip 56b97e8c rsp aa78 error 6 Dec 15 11:09:14 kf85-1 kernel: set_local_var[20817]: segfault at fffc rip 55f41d69 rsp c928 error 6 Dec 15 11:16:29 kf85-1 kernel: set_local_var[21760]: segfault at fffc rip 55f41d69 rsp bd98 error 6 Dec 15 15:10:52 kf85-1 kernel: rtdb_server[17604] trap bounds rip:80f5247 rsp:5b9f9040 error:0 Dec 15 15:11:01 kf85-1 kernel: rtdb_server[18631] trap bounds rip:80f5247 rsp:58905040 error:0 Dec 15 15:11:16 kf85-1 kernel: rtdb_server[18718] trap bounds rip:80f5247 rsp:59300040 error:0 Dec 15 15:11:23 kf85-1 kernel: rtdb_server[18762] trap bounds rip:80f5247 rsp:59106040 error:0 Dec 15 15:14:17 kf85-1 kernel: rtdb_server[18869] trap bounds rip:80f5247 rsp:5b10a040 error:0 Dec 15 15:14:22 kf85-1 kernel: rtdb_server[19567] trap bounds rip:80f5247 rsp:59106040 error:0 Dec 15 15:14:32 kf85-1 kernel: rtdb_server[19586] trap bounds rip:80f5247 rsp:57903040 error:0 3) Dec 15 15:48:30 kf85-1 kernel: set_local_var[2430]: segfault at fffc rip 55f41d69 rsp c7f8 error 6 Dec 15 16:16:17 kf85-1 kernel: GFileManager[10453]: segfault at 3135 rip 574d5f99 rsp 597b3158 error 6 And I didn't figure out why the kernel panic was not in the kernel log file. Thanks! hxu - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Aiee, killing interrupt handler!
In-Reply-To: <[EMAIL PROTECTED]> On Tue, 19 Dec 2006 12:06:20 +0800, Hawk Xu wrote: > Our server(running Oracle 10g) is having a kernel panic problem: <> > Process swapper (pid: 0, threadinfo 80582000, task 80464300) > Stack: 0296 8013f325 81007f7f54d0 0100 >0001 000e 8053e098 8013f3a5 >81007f7f54d0 810002c10a20 You need to post the entire oops message, not just the last part. It should start with "BUG". And using a more recent kernel would be a good idea. > And, we have these error messages in the /var/log/kernel file: > > Dec 7 17:19:09 kf85-1 kernel: set_local_var[9683]: segfault at > fffc rip 55f41d69 rsp c4e8 error 6 > Dec 7 17:27:44 kf85-1 kernel: set_local_var[12020]: segfault at > fffc rip 55f41d69 rsp b978 error 6 32-bit Oracle on 64-bit kernel? If so, it's probably not going to work. -- MBTI: IXTP - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Aiee, killing interrupt handler!
Hi!
Our server(running Oracle 10g) is having a kernel panic problem:
Process swapper (pid: 0, threadinfo 80582000, task 80464300)
Stack: 0296 8013f325 81007f7f54d0 0100
0001 000e 8053e098 8013f3a5
81007f7f54d0 810002c10a20
Call Trace: {group_send_sig_info+85}
{send_group_sig_info+53}
{it_real_fn+0} {it_real_fn+22}
{run_timer_softirq+383}
{profile_pc+32}
{__do_softirq+113}
{do_softirq+53}
{apic_timer_interrupt+99}
{kernel_thread+130}
{default_idle+0}
{default_idle+32}
{cpu_idle+74} {start_kernel+469}
{_sinittext+579}
Code: 80 3f 00 7e f9 e9 4a fd ff ff e8 b0 25 ec ff e9 74 fd ff ff
console shuts up ...
<0>Kernel panic - not syncing: Aiee, killing interrupt handler!
And, we have these error messages in the /var/log/kernel file:
Dec 7 17:19:09 kf85-1 kernel: set_local_var[9683]: segfault at
fffc rip 55f41d69 rsp c4e8 error 6
Dec 7 17:27:44 kf85-1 kernel: set_local_var[12020]: segfault at
fffc rip 55f41d69 rsp b978 error 6
Dec 7 17:29:39 kf85-1 kernel: dbi[12608]: segfault at
rip 080ecea8 rsp a0b0 error 4
Dec 14 14:00:39 kf85-1 kernel: set_local_var[1886]: segfault at
fffc rip 55f41d69 rsp b358 error 6
Dec 15 10:03:17 kf85-1 kernel: set_local_var[2459]: segfault at
fffc rip 55f41d69 rsp c2e8 error 6
Dec 15 10:36:27 kf85-1 kernel: modeling[12173] trap bounds rip:806aec8
rsp:9820 error:0
Dec 15 10:51:49 kf85-1 kernel: modeling[14405]: segfault at
0008 rip 56b97e8c rsp aa78 error 6
Dec 15 11:09:14 kf85-1 kernel: set_local_var[20817]: segfault at
fffc rip 55f41d69 rsp c928 error 6
Dec 15 11:16:29 kf85-1 kernel: set_local_var[21760]: segfault at
fffc rip 55f41d69 rsp bd98 error 6
Dec 15 15:10:52 kf85-1 kernel: rtdb_server[17604] trap bounds
rip:80f5247 rsp:5b9f9040 error:0
Dec 15 15:11:01 kf85-1 kernel: rtdb_server[18631] trap bounds
rip:80f5247 rsp:58905040 error:0
Dec 15 15:11:16 kf85-1 kernel: rtdb_server[18718] trap bounds
rip:80f5247 rsp:59300040 error:0
Dec 15 15:11:23 kf85-1 kernel: rtdb_server[18762] trap bounds
rip:80f5247 rsp:59106040 error:0
Dec 15 15:14:17 kf85-1 kernel: rtdb_server[18869] trap bounds
rip:80f5247 rsp:5b10a040 error:0
Dec 15 15:14:22 kf85-1 kernel: rtdb_server[19567] trap bounds
rip:80f5247 rsp:59106040 error:0
Dec 15 15:14:32 kf85-1 kernel: rtdb_server[19586] trap bounds
rip:80f5247 rsp:57903040 error:0
Dec 15 15:48:30 kf85-1 kernel: set_local_var[2430]: segfault at
fffc rip 55f41d69 rsp c7f8 error 6
Dec 15 16:16:17 kf85-1 kernel: GFileManager[10453]: segfault at
3135 rip 574d5f99 rsp 597b3158 error 6
The kernel version is 2.6.12.5. The kernel panic problem happened 3
times last week, and we don't know whether there are some relationships
between the kernel panic and the error messages in the kernel log file.
That's all we know now, the server is in Nanjing, which is 1000
kilometers south of us, and we are not allowed to access the server.
Any help would be great!
Best regards,
hxu
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Aiee, killing interrupt handler!
Hi!
Our server(running Oracle 10g) is having a kernel panic problem:
Process swapper (pid: 0, threadinfo 80582000, task 80464300)
Stack: 0296 8013f325 81007f7f54d0 0100
0001 000e 8053e098 8013f3a5
81007f7f54d0 810002c10a20
Call Trace: IRQ 8013f325{group_send_sig_info+85}
8013f3a5{send_group_sig_info+53}
80137a50{it_real_fn+0} 80137a66{it_real_fn+22}
8013c9bf{run_timer_softirq+383}
80111660{profile_pc+32}
80138921{__do_softirq+113}
801389d5{do_softirq+53}
8010e3d3{apic_timer_interrupt+99} EOI
8010e676{kernel_thread+130}
8010bc40{default_idle+0}
8010bc60{default_idle+32}
8010be9a{cpu_idle+74} 805847b5{start_kernel+469}
80584243{_sinittext+579}
Code: 80 3f 00 7e f9 e9 4a fd ff ff e8 b0 25 ec ff e9 74 fd ff ff
console shuts up ...
0Kernel panic - not syncing: Aiee, killing interrupt handler!
And, we have these error messages in the /var/log/kernel file:
Dec 7 17:19:09 kf85-1 kernel: set_local_var[9683]: segfault at
fffc rip 55f41d69 rsp c4e8 error 6
Dec 7 17:27:44 kf85-1 kernel: set_local_var[12020]: segfault at
fffc rip 55f41d69 rsp b978 error 6
Dec 7 17:29:39 kf85-1 kernel: dbi[12608]: segfault at
rip 080ecea8 rsp a0b0 error 4
Dec 14 14:00:39 kf85-1 kernel: set_local_var[1886]: segfault at
fffc rip 55f41d69 rsp b358 error 6
Dec 15 10:03:17 kf85-1 kernel: set_local_var[2459]: segfault at
fffc rip 55f41d69 rsp c2e8 error 6
Dec 15 10:36:27 kf85-1 kernel: modeling[12173] trap bounds rip:806aec8
rsp:9820 error:0
Dec 15 10:51:49 kf85-1 kernel: modeling[14405]: segfault at
0008 rip 56b97e8c rsp aa78 error 6
Dec 15 11:09:14 kf85-1 kernel: set_local_var[20817]: segfault at
fffc rip 55f41d69 rsp c928 error 6
Dec 15 11:16:29 kf85-1 kernel: set_local_var[21760]: segfault at
fffc rip 55f41d69 rsp bd98 error 6
Dec 15 15:10:52 kf85-1 kernel: rtdb_server[17604] trap bounds
rip:80f5247 rsp:5b9f9040 error:0
Dec 15 15:11:01 kf85-1 kernel: rtdb_server[18631] trap bounds
rip:80f5247 rsp:58905040 error:0
Dec 15 15:11:16 kf85-1 kernel: rtdb_server[18718] trap bounds
rip:80f5247 rsp:59300040 error:0
Dec 15 15:11:23 kf85-1 kernel: rtdb_server[18762] trap bounds
rip:80f5247 rsp:59106040 error:0
Dec 15 15:14:17 kf85-1 kernel: rtdb_server[18869] trap bounds
rip:80f5247 rsp:5b10a040 error:0
Dec 15 15:14:22 kf85-1 kernel: rtdb_server[19567] trap bounds
rip:80f5247 rsp:59106040 error:0
Dec 15 15:14:32 kf85-1 kernel: rtdb_server[19586] trap bounds
rip:80f5247 rsp:57903040 error:0
Dec 15 15:48:30 kf85-1 kernel: set_local_var[2430]: segfault at
fffc rip 55f41d69 rsp c7f8 error 6
Dec 15 16:16:17 kf85-1 kernel: GFileManager[10453]: segfault at
3135 rip 574d5f99 rsp 597b3158 error 6
The kernel version is 2.6.12.5. The kernel panic problem happened 3
times last week, and we don't know whether there are some relationships
between the kernel panic and the error messages in the kernel log file.
That's all we know now, the server is in Nanjing, which is 1000
kilometers south of us, and we are not allowed to access the server.
Any help would be great!
Best regards,
hxu
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Aiee, killing interrupt handler!
In-Reply-To: [EMAIL PROTECTED] On Tue, 19 Dec 2006 12:06:20 +0800, Hawk Xu wrote: Our server(running Oracle 10g) is having a kernel panic problem: Process swapper (pid: 0, threadinfo 80582000, task 80464300) Stack: 0296 8013f325 81007f7f54d0 0100 0001 000e 8053e098 8013f3a5 81007f7f54d0 810002c10a20 You need to post the entire oops message, not just the last part. It should start with BUG. And using a more recent kernel would be a good idea. And, we have these error messages in the /var/log/kernel file: Dec 7 17:19:09 kf85-1 kernel: set_local_var[9683]: segfault at fffc rip 55f41d69 rsp c4e8 error 6 Dec 7 17:27:44 kf85-1 kernel: set_local_var[12020]: segfault at fffc rip 55f41d69 rsp b978 error 6 32-bit Oracle on 64-bit kernel? If so, it's probably not going to work. -- MBTI: IXTP - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.4.5 Kernel panic: Aiee, killing interrupt handler!
Hello, I have compiled 2.4.5 four times now, and it just won't boot. I have compiled and used every previous 2.4 kernel without problems, using the same configuration. The compiler is gcc 2.95.2, but I also tried gcc 3.0 without success. The system crashes early in the boot process, so I haven't been able to capture the whole error message. One of the first things I see scroll by is "Machine Check Exception", then the last three lines are: >Code: [20 bytes, variable. Sometimes 20 times "%2x"] >Kernel panic: Aiee, killing interrupt handler! >In interrupt handler - not syncing Now this is an old Compaq LTE 5200 laptop, Pentium 120MHz, 72MB RAM. cat /proc/pci yields: PCI devices found: Bus 0, device 0, function 0: Host bridge: OPTi Inc. 82C557 [Viper-M] (rev 0). Bus 0, device 1, function 0: ISA bridge: OPTi Inc. 82C558 [Viper-M ISA+IDE] (rev 0). Bus 0, device 2, function 0: VGA compatible controller: Cirrus Logic GD 7543 [Viking] (rev 0). Non-prefetchable 32 bit memory at 0xc000 [0xc0ff]. Non-prefetchable 32 bit memory at 0xc100 [0xc1ff]. As I said, I had no problems with 2.4.n, n<5. I tried a 2.4.6pre kernel (5, I think), and that *didn't work* either. I would greatly appreciate if anyone had any suggestions regarding this. And if they could cc: it to me, that would be great. Thanks! David Bragason, - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.4.5 Kernel panic: Aiee, killing interrupt handler!
Hello, I have compiled 2.4.5 four times now, and it just won't boot. I have compiled and used every previous 2.4 kernel without problems, using the same configuration. The compiler is gcc 2.95.2, but I also tried gcc 3.0 without success. The system crashes early in the boot process, so I haven't been able to capture the whole error message. One of the first things I see scroll by is Machine Check Exception, then the last three lines are: Code: [20 bytes, variable. Sometimes 20 times %2x] Kernel panic: Aiee, killing interrupt handler! In interrupt handler - not syncing Now this is an old Compaq LTE 5200 laptop, Pentium 120MHz, 72MB RAM. cat /proc/pci yields: PCI devices found: Bus 0, device 0, function 0: Host bridge: OPTi Inc. 82C557 [Viper-M] (rev 0). Bus 0, device 1, function 0: ISA bridge: OPTi Inc. 82C558 [Viper-M ISA+IDE] (rev 0). Bus 0, device 2, function 0: VGA compatible controller: Cirrus Logic GD 7543 [Viking] (rev 0). Non-prefetchable 32 bit memory at 0xc000 [0xc0ff]. Non-prefetchable 32 bit memory at 0xc100 [0xc1ff]. As I said, I had no problems with 2.4.n, n5. I tried a 2.4.6pre kernel (5, I think), and that *didn't work* either. I would greatly appreciate if anyone had any suggestions regarding this. And if they could cc: it to me, that would be great. Thanks! David Bragason, bragason at uni-freiburg dot de - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
SMP aic7xxx 2.4.3 boot panic: Aiee, killing interrupt handler
Has anyone else had this or a similar problem? I tried to upgrade to 2.4.3 from 2.2.18 recently, but I invariably got a kernel panic on boot - I ran the oops through ksymoops, and it seemed to indicate that the problem occurred while in the aic7xxx driver [although I may, of course, be misinterpreting the ouput hideously] I'm, going to try the old aic7xxx driver tonight, to see if that works any better. [I posted the oops a couple of days ago, and I don't want to spam the list with it again, but if anyome is interested in the output, I'd be happy to send it, pluys any extra details required... ] -- "They're unfriendly, which is fortunate, really. They'd be difficult to like." -- Avon - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
SMP aic7xxx 2.4.3 boot panic: Aiee, killing interrupt handler
Has anyone else had this or a similar problem? I tried to upgrade to 2.4.3 from 2.2.18 recently, but I invariably got a kernel panic on boot - I ran the oops through ksymoops, and it seemed to indicate that the problem occurred while in the aic7xxx driver [although I may, of course, be misinterpreting the ouput hideously] I'm, going to try the old aic7xxx driver tonight, to see if that works any better. [I posted the oops a couple of days ago, and I don't want to spam the list with it again, but if anyome is interested in the output, I'd be happy to send it, pluys any extra details required... ] -- "They're unfriendly, which is fortunate, really. They'd be difficult to like." -- Avon - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Kernel panic: Aiee, killing interrupt handler!
Hi, I got this machine, which I use for my research groups file (samba) and printing (lpd over samba) needs. This is the second time it has gone down for me, as shown below. There's really nothing to say about it; it has worked fine for about two weeks, and then an unprovoked panic. As you might see, it went down on a saturday, and this is the only thing in the log on that day; it's been standing idle for the whole day. The spec. is, as I'm sure you can see from the dmesg+lspci attachment: Pentium 90MHz 32Mb RAM SiS 85C501/2 CMD640 IDE SMC-Ultra 8216C IBM Deskstar DTLA-305040 41Gb, 128Mb swap, 2Gb ext2, and the rest one big reiserfs. linux-2.4.2 RedHat 6.2 I have to use setmax (from LARGE-HDD-HOWTO) in order to get the deskstar to mount. An oddity is this; We didn't have enough network points in our office, so I made a bridge (the bridging code is compiled into the kernel), using a second (SMC-Ultra) network card. And all of a sudden, I didn't have to use setmax any more. The kernel took care of the disk fine. As we got new points installed, I stopped using the bridge, and, once again I had to use setmax. Strange. I must add, I've used this machine for about a year to run an instrument, without any problems, only with linux-2.2 and a 6Gb harddrive instead of the deskstar. I've also added an extra ISA card parport for a second printer. I hope something of this helps. And if someone could tell me what is wrong here, I would be much obliged. I've had much resistance within the university for using linux as it is, and, if it starts going down every now and again, they'll chuck it out without a doubt. If I can do somthing else, in order to help, plese let me know. Cheeres, /Chris Kernel panic: Aiee, killing interrupt handler! In interrupt handler not syncing Unable to handle kernel NULL pointer dereference at virtual address 000b printing eip: c01104c3 *pde = Oops: CPU: 0 EIP: 0010: [] EFLAGS: 00010013 eax: epx: 000b ecx: c10a6000 edx: c02108dc esi: c0210c18 edi: 0003 ebp: c10a5eb0 esp: c10a5e94 Process kreclaimd pid:4, stackpage = c10a5000 Stack: c02109c0 c0210c18 c02108dc 0001 0286 0001 0002 c0128335 0020 0002 c10af124 0002 0002 c0210c10 c012850c c012532a c10af124 0246 0002 0021 0003 c0125467 Call trace: [] [] [] [] [] [] [] [] [] [] [] Code: 8b 1b 8b 4f 04 8b 01 85 45 fc 74 51 31 c0 9c 5e fa c7 01 00 Kernel panic: Aiee, killing interrupt handler! In interrupt handler not syncing -- Christer Bäckström Optoelectronic Materials Chemistry Group Department of Chemistry University of Wales, Bangor Bangor, Gwynedd LL57 2UW Wales, UK E-mail : [EMAIL PROTECTED] Telephone Office: +44(0)1248 388302 Telephone Laboratory: +44(0)1248 388304 Linux version 2.4.2 ([EMAIL PROTECTED]) (gcc version 2.95.3 19991030 (prerelease)) #23 Thu Feb 22 22:03:19 GMT 2001 BIOS-provided physical RAM map: BIOS-e820: 0009fc00 @ (usable) BIOS-e820: 0400 @ 0009fc00 (reserved) BIOS-e820: 00018000 @ 000e8000 (reserved) BIOS-e820: 01f0 @ 0010 (usable) BIOS-e820: 0001 @ (reserved) On node 0 totalpages: 8192 zone(0): 4096 pages. zone(1): 4096 pages. zone(2): 0 pages. Kernel command line: auto BOOT_IMAGE=2 ro root=302 hda=79780,16,63 ide_setup: hda=79780,16,63 Initializing CPU#0 Detected 90.001 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 179.40 BogoMIPS Memory: 30320k/32768k available (846k kernel code, 2060k reserved, 286k data, 180k init, 0k highmem) Dentry-cache hash table entries: 4096 (order: 3, 32768 bytes) Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes) Page-cache hash table entries: 8192 (order: 3, 32768 bytes) Inode-cache hash table entries: 2048 (order: 2, 16384 bytes) CPU: Before vendor init, caps: 01bf , vendor = 0 Intel Pentium with F0 0F bug - workaround enabled. CPU: After vendor init, caps: 01bf CPU: After generic, caps: 01bf CPU: Common caps: 01bf CPU: Intel Pentium 75 - 200 stepping 04 Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX PCI: PCI BIOS revision 2.00 entry at 0xfc920, last bus=0 PCI: Using configuration type 1 PCI: Probing PCI hardware PCI: Unable to handle 64-bit address for device 00:00.0 PCI: Unable to handle 64-bit address for device 00:00.0 PCI: Unable to handle 64-bit address for device 00:00.0 PCI: Failed to allocate resource 1 for Silicon Integrated Systems [SiS] 85C501/2 PCI: Failed to allocate resource 3 for Silicon Integrated Systems [SiS] 85C501/2 PCI: Failed to allocate resource 5 for Silicon Integrated Systems [SiS] 85C501/2 isapnp: Scanning for Pnp cards... isapnp: No Plug & Play device found Linux NET4.0 for Linux 2.4 Based upon Swansea University Comp
Kernel panic: Aiee, killing interrupt handler!
Hi, I got this machine, which I use for my research groups file (samba) and printing (lpd over samba) needs. This is the second time it has gone down for me, as shown below. There's really nothing to say about it; it has worked fine for about two weeks, and then an unprovoked panic. As you might see, it went down on a saturday, and this is the only thing in the log on that day; it's been standing idle for the whole day. The spec. is, as I'm sure you can see from the dmesg+lspci attachment: Pentium 90MHz 32Mb RAM SiS 85C501/2 CMD640 IDE SMC-Ultra 8216C IBM Deskstar DTLA-305040 41Gb, 128Mb swap, 2Gb ext2, and the rest one big reiserfs. linux-2.4.2 RedHat 6.2 I have to use setmax (from LARGE-HDD-HOWTO) in order to get the deskstar to mount. An oddity is this; We didn't have enough network points in our office, so I made a bridge (the bridging code is compiled into the kernel), using a second (SMC-Ultra) network card. And all of a sudden, I didn't have to use setmax any more. The kernel took care of the disk fine. As we got new points installed, I stopped using the bridge, and, once again I had to use setmax. Strange. I must add, I've used this machine for about a year to run an instrument, without any problems, only with linux-2.2 and a 6Gb harddrive instead of the deskstar. I've also added an extra ISA card parport for a second printer. I hope something of this helps. And if someone could tell me what is wrong here, I would be much obliged. I've had much resistance within the university for using linux as it is, and, if it starts going down every now and again, they'll chuck it out without a doubt. If I can do somthing else, in order to help, plese let me know. Cheeres, /Chris Kernel panic: Aiee, killing interrupt handler! In interrupt handler not syncing Unable to handle kernel NULL pointer dereference at virtual address 000b printing eip: c01104c3 *pde = Oops: CPU: 0 EIP: 0010: [c01104c3] EFLAGS: 00010013 eax: epx: 000b ecx: c10a6000 edx: c02108dc esi: c0210c18 edi: 0003 ebp: c10a5eb0 esp: c10a5e94 Process kreclaimd pid:4, stackpage = c10a5000 Stack: c02109c0 c0210c18 c02108dc 0001 0286 0001 0002 c0128335 0020 0002 c10af124 0002 0002 c0210c10 c012850c c012532a c10af124 0246 0002 0021 0003 c0125467 Call trace: [c0128335] [c012850c] [c012532a] [c01254bf] [c019eb02] [c0185719] [c018526e] [c0109fdf] [c010a13e] [c0108e60] [c0112270] Code: 8b 1b 8b 4f 04 8b 01 85 45 fc 74 51 31 c0 9c 5e fa c7 01 00 Kernel panic: Aiee, killing interrupt handler! In interrupt handler not syncing -- Christer Bckstrm Optoelectronic Materials Chemistry Group Department of Chemistry University of Wales, Bangor Bangor, Gwynedd LL57 2UW Wales, UK E-mail : [EMAIL PROTECTED] Telephone Office: +44(0)1248 388302 Telephone Laboratory: +44(0)1248 388304 Linux version 2.4.2 ([EMAIL PROTECTED]) (gcc version 2.95.3 19991030 (prerelease)) #23 Thu Feb 22 22:03:19 GMT 2001 BIOS-provided physical RAM map: BIOS-e820: 0009fc00 @ (usable) BIOS-e820: 0400 @ 0009fc00 (reserved) BIOS-e820: 00018000 @ 000e8000 (reserved) BIOS-e820: 01f0 @ 0010 (usable) BIOS-e820: 0001 @ (reserved) On node 0 totalpages: 8192 zone(0): 4096 pages. zone(1): 4096 pages. zone(2): 0 pages. Kernel command line: auto BOOT_IMAGE=2 ro root=302 hda=79780,16,63 ide_setup: hda=79780,16,63 Initializing CPU#0 Detected 90.001 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 179.40 BogoMIPS Memory: 30320k/32768k available (846k kernel code, 2060k reserved, 286k data, 180k init, 0k highmem) Dentry-cache hash table entries: 4096 (order: 3, 32768 bytes) Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes) Page-cache hash table entries: 8192 (order: 3, 32768 bytes) Inode-cache hash table entries: 2048 (order: 2, 16384 bytes) CPU: Before vendor init, caps: 01bf , vendor = 0 Intel Pentium with F0 0F bug - workaround enabled. CPU: After vendor init, caps: 01bf CPU: After generic, caps: 01bf CPU: Common caps: 01bf CPU: Intel Pentium 75 - 200 stepping 04 Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX PCI: PCI BIOS revision 2.00 entry at 0xfc920, last bus=0 PCI: Using configuration type 1 PCI: Probing PCI hardware PCI: Unable to handle 64-bit address for device 00:00.0 PCI: Unable to handle 64-bit address for device 00:00.0 PCI: Unable to handle 64-bit address for device 00:00.0 PCI: Failed to allocate resource 1 for Silicon Integrated Systems [SiS] 85C501/2 PCI: Failed to allocate resource 3 for Silicon Integrated Systems [SiS] 85C501/2 PCI: Failed to allocate resource 5 for Silicon Integrated Systems [SiS] 85C501/2 isapnp: Scanning for Pnp cards... isapnp
