* kernel crash
@ 2001-04-01 10:15 nak
0 siblings, 0 replies; 10+ messages in thread
From: nak @ 2001-04-01 10:15 UTC (permalink / raw)
To: linux-kernel, linux-arm
This is a general plea for help .. We were told Linux was the most stable OS
for embedded work so we put it to use in running our ARM based pacemaker.
It did well on the preliminary tests using simulated output we managed 3
weeks with no problems and almost perfect rhythm generation.
On the fourth week we began animal testing our product and it did fine for 5
days 3 hours and 10 minutes.
On Thursday March 22 at 0419 hrs a software crash caused a malfunction in
the pacemaker resulting in a large discharge of current, defibrilating the
heart and forcing it into an angonal rhythm from which we were unable to
cardiovert.
On top of that, the catastrophic failure means we will be unable to begin
human testing of our product until early 2003.
One of our techs managed to retrieve something he called an "oops"? from the
monitor and I've enclosed it below. If anyone can help us with this please
get back to me. We need to fix this as soon as possible so we can make final
product release as early as possible.
sincerely,
Dr. Nakasumo
Cardiac Products Dept.
APF Bioelectronics
Unable to handle kernel paging request at virtual address ea0032fb
pgd = c0004000
*pgd = 00000000, *pmd = 00000000
Internal error: Oops: 2
CPU: 0
pc : [<c0021124>] lr : [<c0021450>]
sp : c8785c98 ip : a0000013 fp : c8785cd0
r10: 01000000 r9 : 00000003 r8 : c8785cf8
r7 : 00000003 r6 : 00003240 r5 : e7933000 r4 : ea0032fb
r3 : 00000001 r2 : 01000000 r1 : c016209c r0 : ea0032fb
Flags: nzcv IRQs on FIQs on Mode SVC_32 Segment kernel
Control: C860117F Table: C860117F DAC: 0000001D
Process mtdblockd (pid: 7, stackpage=c8785000)
Stack:
c8785c80: c0021450 c0021124 00000013 ffffffff 00000000 00000
000
c8785ca0: 00000000 00000004 ffffffff ea0032fb c8785cf8 c0121cf4 00000003 a0000
013
c8785cc0: 00000000 c8785cf4 c8785cd4 c0021450 c0020e44 ffffffff c8785d2c c9000
000
c8785ce0: c8785e28 00000005 c8785d4c c8785cf8 c001ab20 c0021390 00003240 00000
000
c8785d00: ea0032fb ea0000bb ffffffff c8784000 c9000000 c8785e28 00000005 00000
000
c8785d20: 00000000 c8785d4c c0374821 c8785d40 c0020d00 c0020afc a0000013 fffff
fff
c8785d40: c8785e00 c8785d50 c0020d00 c0020ad0 00000000 00000000 00000000 00000
000
c8785d60: 00000000 00000000 00000000 c8784000 00000000 00000001 c8785da4 c8785
d88
c8785d80: c0036390 c0036260 40000013 fa000000 c8785e0c fa000014 c8785dbc c8785
da8
c8785da0: c00367e4 c0036368 40000013 fa000000 c8785ddc c8785dc0 c001aa08 c0036
7c0
c8785dc0: 00000000 0000001a 00000000 c01893b0 c8785e08 c8785de0 ffffffff c9000
000
c8785de0: c8785e28 c0121d0c 00000005 20000013 00800080 c8785e24 c8785e04 c0021
450
c8785e00: c0020b2c ffffffff c8785e5c 00000000 00000000 ffffffff c8785e94 c8785
e28
c8785e20: c001ab20 c0021390 c9000000 e8040020 0003ffe0 00000000 00000000 00000
000
c8785e40: 00000000 00000000 ffffffff ffffffff 00800080 c8785e94 ffffffff c8785
e70
c8785e60: c00bf190 c011a7c0 20000013 ffffffff 00040000 00040000 c9000000 00040
000
c8785e80: 00000000 c8036504 c8785eb0 c8785e98 c00bf190 c011a78c c0189c60 c8036
4c0
c8785ea0: c015ddf0 c8785f28 c8785eb4 c00bc964 c00bf168 c8784000 c8036504 c8784
000
c8785ec0: 0000090d 00000000 00040000 00000000 00040000 00000000 c80364c0 00040
000
c8785ee0: 00000000 c8784000 00000000 00000000 00000000 c8784000 00000000 00000
000
c8785f00: 00040000 00000000 00000000 00000000 00040000 c9000000 c8785f78 c8785
f5c
c8785f20: c8785f2c c00b9ed4 c00bc0e4 c8785f78 c9000000 c01cf428 c01cf420 00001
000
c8785f40: 00000000 00040000 00000000 00000000 c8785fa4 c8785f60 c00bf588 c00b9
e1c
c8785f60: c8785f78 c9000000 00040000 c01db160 c0350000 00001000 00000000 c01cf
428
c8785f80: c02d0660 00000008 c018e158 c015de90 6901b116 c015de78 c8785fc4 c8785
fa8
c8785fa0: c00bfcd4 c00bf414 00000000 c8784000 c8785fc8 c018e158 c8785ffc c8785
fc8
c8785fc0: c00bfee4 c00bfba8 00000000 c8784000 c015de94 c015de94 00000000 c0187
160
c8785fe0: c0187120 c0188ba4 c018c494 c0014c34 00000000 c8786000 c001c620 c00bf
d8c
Backtrace:
Function entered at [<c0020e38>] from [<c0021450>] do_alignment
Function entered at [<c0021384>] from [<c001ab20>] do_data_abort
r8 = 00000005 r7 = C8785E28 r6 = C9000000 r5 = C8785D2C
r4 = FFFFFFFF
Function entered at [<c0020ac4>] from [<c0020d00>] __do_vmalloc_fault
Function entered at [<c0020b20>] from [<c0021450>] __do_page_fault
Function entered at [<c0021384>] from [<c001ab20>] do_DataAbort
r8 = FFFFFFFF r7 = 00000000 r6 = 00000000 r5 = C8785E5C
r4 = FFFFFFFF
Function entered at [<c011a780>] from [<c00bf190>] memcpy
r9 = C8036504 r8 = 00000000 r7 = 00040000 r6 = C9000000
r5 = 00040000 r4 = 00040000
Function entered at [<c00bf15c>] from [<c00bc964>] sa1100_copy_from
r6 = C015DDF0 r5 = C80364C0 r4 = C0189C60
Function entered at [<c00bc0d8>] from [<c00b9ed4>] cfi_intelext_read
Function entered at [<c00b9e10>] from [<c00bf588>] part_read
Function entered at [<c00bf408>] from [<c00bfcd4>] do_cached_write
Function entered at [<c00bfb9c>] from [<c00bfee4>] handle_mtdblock_request
r7 = C018E158 r6 = C8785FC8 r5 = C8784000 r4 = 00000000
Function entered at [<c00bfd80>] from [<c001c620>] mtdblock_thread
Aiee, killing interrupt handler
Scheduling in interrupt
kernel BUG at sched.c:698!
Unable to handle kernel NULL pointer dereference at virtual address 00000000
pgd = c0004000
*pgd = c01a0001, *pmd = c01a0001, *pte = c000308b, *ppte = c000300a
Internal error: Oops: 0
CPU: 0
pc : [<c001fdc8>] lr : [<c002e0ac>]
sp : c8785b08 ip : c8785ac4 fp : c8785b18
r10: 00000000 r9 : c0189c60 r8 : 00000000
r7 : 0000000b r6 : c8784000 r5 : c8784000 r4 : 00000000
r3 : 00000000 r2 : c0154ea8 r1 : 00000000 r0 : 00000001
Flags: nZCv IRQs on FIQs on Mode SVC_32 Segment kernel
Control: C860117F Table: C860117F DAC: 0000001D
Process mtdblockd (pid: 7, stackpage=c8785000)
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: kernel crash
@ 2001-04-02 16:40 Wayne.Brown
0 siblings, 0 replies; 10+ messages in thread
From: Wayne.Brown @ 2001-04-02 16:40 UTC (permalink / raw)
To: nak; +Cc: linux-kernel, linux-arm
I hope you were using a scratch monkey...
^ permalink raw reply [flat|nested] 10+ messages in thread
* RE: kernel crash
@ 2001-04-12 15:16 Cyrille Ngalle
2001-04-12 15:31 ` Russell King
0 siblings, 1 reply; 10+ messages in thread
From: Cyrille Ngalle @ 2001-04-12 15:16 UTC (permalink / raw)
To: nak, linux-kernel, linux-arm
Hi all !!
This is just to reinforce the message below.
This crash is ver easy to reproduce.
Use bootldr (with the last patch from Nico) [it also happens with
Redboot]
+
Lunix 2.4.0 + patch rmk2 + diff rmk2-np2
+ a ramdisk.
Once logged in Linux, type these commands :
SHELL> mknod /dev/dsp c 14 3
SHELL> echo foo > /dev/dsp
and there you are => kernel crash
I had a deeper look and this seems to be the scheduler that is not
handling some page stuff properly (I am not a specialist but this is
what I observed).
This has been reported several times in various mailing lists. I haven't
found yet
any patch fixing this.
Is there someone around the place looking at this problem as many people
seem to be waiting
for this fix ???
Thanks again folks,
Cyrille
-----Original Message-----
From: nak@apfbioelectronics.com [mailto:nak@apfbioelectronics.com]
Sent: Sunday, April 01, 2001 12:15 PM
To: linux-kernel@vger.kernel.org; linux-arm@lists.arm.linux.org.uk
Subject: kernel crash
This is a general plea for help .. We were told Linux was the most
stable OS
for embedded work so we put it to use in running our ARM based
pacemaker.
It did well on the preliminary tests using simulated output we managed 3
weeks with no problems and almost perfect rhythm generation.
On the fourth week we began animal testing our product and it did fine
for 5
days 3 hours and 10 minutes.
On Thursday March 22 at 0419 hrs a software crash caused a malfunction
in
the pacemaker resulting in a large discharge of current, defibrilating
the
heart and forcing it into an angonal rhythm from which we were unable to
cardiovert.
On top of that, the catastrophic failure means we will be unable to
begin
human testing of our product until early 2003.
One of our techs managed to retrieve something he called an "oops"? from
the
monitor and I've enclosed it below. If anyone can help us with this
please
get back to me. We need to fix this as soon as possible so we can make
final
product release as early as possible.
sincerely,
Dr. Nakasumo
Cardiac Products Dept.
APF Bioelectronics
Unable to handle kernel paging request at virtual address ea0032fb
pgd = c0004000
*pgd = 00000000, *pmd = 00000000
Internal error: Oops: 2
CPU: 0
pc : [<c0021124>] lr : [<c0021450>]
sp : c8785c98 ip : a0000013 fp : c8785cd0
r10: 01000000 r9 : 00000003 r8 : c8785cf8
r7 : 00000003 r6 : 00003240 r5 : e7933000 r4 : ea0032fb
r3 : 00000001 r2 : 01000000 r1 : c016209c r0 : ea0032fb
Flags: nzcv IRQs on FIQs on Mode SVC_32 Segment kernel
Control: C860117F Table: C860117F DAC: 0000001D
Process mtdblockd (pid: 7, stackpage=c8785000)
Stack:
c8785c80: c0021450 c0021124 00000013 ffffffff
00000000 00000
000
c8785ca0: 00000000 00000004 ffffffff ea0032fb c8785cf8 c0121cf4
00000003 a0000
013
c8785cc0: 00000000 c8785cf4 c8785cd4 c0021450 c0020e44 ffffffff
c8785d2c c9000
000
c8785ce0: c8785e28 00000005 c8785d4c c8785cf8 c001ab20 c0021390
00003240 00000
000
c8785d00: ea0032fb ea0000bb ffffffff c8784000 c9000000 c8785e28
00000005 00000
000
c8785d20: 00000000 c8785d4c c0374821 c8785d40 c0020d00 c0020afc
a0000013 fffff
fff
c8785d40: c8785e00 c8785d50 c0020d00 c0020ad0 00000000 00000000
00000000 00000
000
c8785d60: 00000000 00000000 00000000 c8784000 00000000 00000001
c8785da4 c8785
d88
c8785d80: c0036390 c0036260 40000013 fa000000 c8785e0c fa000014
c8785dbc c8785
da8
c8785da0: c00367e4 c0036368 40000013 fa000000 c8785ddc c8785dc0
c001aa08 c0036
7c0
c8785dc0: 00000000 0000001a 00000000 c01893b0 c8785e08 c8785de0
ffffffff c9000
000
c8785de0: c8785e28 c0121d0c 00000005 20000013 00800080 c8785e24
c8785e04 c0021
450
c8785e00: c0020b2c ffffffff c8785e5c 00000000 00000000 ffffffff
c8785e94 c8785
e28
c8785e20: c001ab20 c0021390 c9000000 e8040020 0003ffe0 00000000
00000000 00000
000
c8785e40: 00000000 00000000 ffffffff ffffffff 00800080 c8785e94
ffffffff c8785
e70
c8785e60: c00bf190 c011a7c0 20000013 ffffffff 00040000 00040000
c9000000 00040
000
c8785e80: 00000000 c8036504 c8785eb0 c8785e98 c00bf190 c011a78c
c0189c60 c8036
4c0
c8785ea0: c015ddf0 c8785f28 c8785eb4 c00bc964 c00bf168 c8784000
c8036504 c8784
000
c8785ec0: 0000090d 00000000 00040000 00000000 00040000 00000000
c80364c0 00040
000
c8785ee0: 00000000 c8784000 00000000 00000000 00000000 c8784000
00000000 00000
000
c8785f00: 00040000 00000000 00000000 00000000 00040000 c9000000
c8785f78 c8785
f5c
c8785f20: c8785f2c c00b9ed4 c00bc0e4 c8785f78 c9000000 c01cf428
c01cf420 00001
000
c8785f40: 00000000 00040000 00000000 00000000 c8785fa4 c8785f60
c00bf588 c00b9
e1c
c8785f60: c8785f78 c9000000 00040000 c01db160 c0350000 00001000
00000000 c01cf
428
c8785f80: c02d0660 00000008 c018e158 c015de90 6901b116 c015de78
c8785fc4 c8785
fa8
c8785fa0: c00bfcd4 c00bf414 00000000 c8784000 c8785fc8 c018e158
c8785ffc c8785
fc8
c8785fc0: c00bfee4 c00bfba8 00000000 c8784000 c015de94 c015de94
00000000 c0187
160
c8785fe0: c0187120 c0188ba4 c018c494 c0014c34 00000000 c8786000
c001c620 c00bf
d8c
Backtrace:
Function entered at [<c0020e38>] from [<c0021450>] do_alignment
Function entered at [<c0021384>] from [<c001ab20>] do_data_abort
r8 = 00000005 r7 = C8785E28 r6 = C9000000 r5 = C8785D2C
r4 = FFFFFFFF
Function entered at [<c0020ac4>] from [<c0020d00>] __do_vmalloc_fault
Function entered at [<c0020b20>] from [<c0021450>] __do_page_fault
Function entered at [<c0021384>] from [<c001ab20>] do_DataAbort
r8 = FFFFFFFF r7 = 00000000 r6 = 00000000 r5 = C8785E5C
r4 = FFFFFFFF
Function entered at [<c011a780>] from [<c00bf190>] memcpy
r9 = C8036504 r8 = 00000000 r7 = 00040000 r6 = C9000000
r5 = 00040000 r4 = 00040000
Function entered at [<c00bf15c>] from [<c00bc964>] sa1100_copy_from
r6 = C015DDF0 r5 = C80364C0 r4 = C0189C60
Function entered at [<c00bc0d8>] from [<c00b9ed4>] cfi_intelext_read
Function entered at [<c00b9e10>] from [<c00bf588>] part_read
Function entered at [<c00bf408>] from [<c00bfcd4>] do_cached_write
Function entered at [<c00bfb9c>] from [<c00bfee4>]
handle_mtdblock_request
r7 = C018E158 r6 = C8785FC8 r5 = C8784000 r4 = 00000000
Function entered at [<c00bfd80>] from [<c001c620>] mtdblock_thread
Aiee, killing interrupt handler
Scheduling in interrupt
kernel BUG at sched.c:698!
Unable to handle kernel NULL pointer dereference at virtual address
00000000
pgd = c0004000
*pgd = c01a0001, *pmd = c01a0001, *pte = c000308b, *ppte = c000300a
Internal error: Oops: 0
CPU: 0
pc : [<c001fdc8>] lr : [<c002e0ac>]
sp : c8785b08 ip : c8785ac4 fp : c8785b18
r10: 00000000 r9 : c0189c60 r8 : 00000000
r7 : 0000000b r6 : c8784000 r5 : c8784000 r4 : 00000000
r3 : 00000000 r2 : c0154ea8 r1 : 00000000 r0 : 00000001
Flags: nZCv IRQs on FIQs on Mode SVC_32 Segment kernel
Control: C860117F Table: C860117F DAC: 0000001D
Process mtdblockd (pid: 7, stackpage=c8785000)
_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
Please visit the above address for information on this list.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: kernel crash
2001-04-12 15:16 Cyrille Ngalle
@ 2001-04-12 15:31 ` Russell King
2001-04-13 13:16 ` nak
0 siblings, 1 reply; 10+ messages in thread
From: Russell King @ 2001-04-12 15:31 UTC (permalink / raw)
To: Cyrille Ngalle; +Cc: nak, linux-kernel, linux-arm
On Thu, Apr 12, 2001 at 05:16:33PM +0200, Cyrille Ngalle wrote:
> This is just to reinforce the message below.
And why is it of interest to LKML? I can think if no one here who'd
be interested in it.
> This crash is ver easy to reproduce.
>
> Use bootldr (with the last patch from Nico) [it also happens with
> Redboot]
It is not a function of the bootloader, this is irrelevent.
Also, I believe that the original posters message was an April Fool's
joke (was posted on the 1st April to the linux-arm lists).
However, the problem it describes is not, and I do have a fix in my
tree, but the delta between my last patch and my current tree is one
line, which hardly seems worth putting out a new ARM patch.
--- linux.rel/arch/arm/mm/fault-armv.c Fri Apr 6 19:09:05 2001
+++ linux/arch/arm/mm/fault-armv.c Thu Apr 12 16:30:25 2001
@@ -490,7 +490,7 @@
bad_or_fault:
if (type == TYPE_ERROR)
goto bad;
-
+ regs->ARM_pc -= 4;
/*
* We got a fault - fix it up, or die.
*/
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: kernel crash
2001-04-12 15:31 ` Russell King
@ 2001-04-13 13:16 ` nak
0 siblings, 0 replies; 10+ messages in thread
From: nak @ 2001-04-13 13:16 UTC (permalink / raw)
To: Russell King; +Cc: Cyrille Ngalle, linux-kernel, linux-arm
Ok, I see this has started to interfere with the bug tracking process so
I'll kill it now (I seriously thought it was already dead).
Yep it was an april fools joke.
for the record:
2 offers for help;
1 post asking me if I mounted a scratch monkey( heh);
1 email begging me to abandon the project for the sake of humanity (and
linux' reputation)
And this adds 1 attempt to use it as corroborating evidence. Who knows, it
might have even been this guy's post I ripped the oops from.
On Thu, 12 Apr 2001, Russell King wrote:
> On Thu, Apr 12, 2001 at 05:16:33PM +0200, Cyrille Ngalle wrote:
> > This is just to reinforce the message below.
>
> And why is it of interest to LKML? I can think if no one here who'd
> be interested in it.
>
> > This crash is ver easy to reproduce.
> >
> > Use bootldr (with the last patch from Nico) [it also happens with
> > Redboot]
>
> It is not a function of the bootloader, this is irrelevent.
>
> Also, I believe that the original posters message was an April Fool's
> joke (was posted on the 1st April to the linux-arm lists).
>
> However, the problem it describes is not, and I do have a fix in my
> tree, but the delta between my last patch and my current tree is one
> line, which hardly seems worth putting out a new ARM patch.
>
> --- linux.rel/arch/arm/mm/fault-armv.c Fri Apr 6 19:09:05 2001
> +++ linux/arch/arm/mm/fault-armv.c Thu Apr 12 16:30:25 2001
> @@ -490,7 +490,7 @@
> bad_or_fault:
> if (type == TYPE_ERROR)
> goto bad;
> -
> + regs->ARM_pc -= 4;
> /*
> * We got a fault - fix it up, or die.
> */
>
>
> --
> Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
> http://www.arm.linux.org.uk/personal/aboutme.html
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* kernel crash
@ 2002-06-26 11:02 Pavel Gulchouck
2002-06-26 19:03 ` James Stevenson
0 siblings, 1 reply; 10+ messages in thread
From: Pavel Gulchouck @ 2002-06-26 11:02 UTC (permalink / raw)
To: linux-kernel
Hello.
RedHat 7.3, kernel 2.4.18-4, ext3, swap to partition, no SMP.
Any suggestions?
Should I change aufs to ufs in squid, or it's not related to this crash?
Jun 20 04:33:30 gate kernel: ------------[ cut here ]------------
Jun 20 04:33:30 gate kernel: kernel BUG at inode.c:1066!
Jun 20 04:33:30 gate kernel: invalid operand: 0000
Jun 20 04:33:30 gate kernel: ip_nat_ftp ipt_REJECT ipt_REDIRECT cls_u32 sch_tbf sch_cbq autofs smbfs ne2k-p
Jun 20 04:33:30 gate kernel: CPU: 0
Jun 20 04:33:31 gate kernel: EIP: 0010:[iput+47/496] Tainted: P
Jun 20 04:33:31 gate kernel: EIP: 0010:[<c0148cdb>] Tainted: P
Jun 20 04:33:31 gate kernel: EFLAGS: 00010286
Jun 20 04:33:31 gate kernel:
Jun 20 04:33:31 gate kernel: EIP is at iput [kernel] 0x2f (2.4.18-4)
Jun 20 04:33:31 gate kernel: eax: 0000001c ebx: c5d12810 ecx: 00000001 edx: 0020c5f3
Jun 20 04:33:31 gate kernel: esi: c74fd400 edi: 00000000 ebp: 0000004b esp: c11c1f50
Jun 20 04:33:31 gate kernel: ds: 0018 es: 0018 ss: 0018
Jun 20 04:33:31 gate kernel: Process kswapd (pid: 4, stackpage=c11c1000)
Jun 20 04:33:31 gate kernel: Stack: c022bbab 0000042a c009dd78 c009dd60 c5d12810 c0146c66 c5d12810 c11c0000
Jun 20 04:33:31 gate kernel: c012e148 00000000 00000000 ffffffff c02cad78 00000000 000000e8 0000003a
Jun 20 04:33:31 gate kernel: 000001d0 000000e8 00000000 66666667 c0146f84 0000025c c012eb96 00000006
Jun 20 04:33:31 gate kernel: Call Trace: [prune_dcache+262/372] prune_dcache [kernel] 0x106
Jun 20 04:33:31 gate kernel: Call Trace: [<c0146c66>] prune_dcache [kernel] 0x106
Jun 20 04:33:31 gate kernel: [page_launder_zone+1344/1648] page_launder_zone [kernel] 0x540
Jun 20 04:33:31 gate kernel: [<c012e148>] page_launder_zone [kernel] 0x540
Jun 20 04:33:31 gate kernel: [shrink_dcache_memory+32/48] shrink_dcache_memory [kernel] 0x20
Jun 20 04:33:31 gate kernel: [<c0146f84>] shrink_dcache_memory [kernel] 0x20
Jun 20 04:33:31 gate kernel: [do_try_to_free_pages+26/376] do_try_to_free_pages [kernel] 0x1a
Jun 20 04:33:31 gate kernel: [<c012eb96>] do_try_to_free_pages [kernel] 0x1a
Jun 20 04:33:31 gate kernel: [kswapd+248/680] kswapd [kernel] 0xf8
Jun 20 04:33:31 gate kernel: [<c012ee64>] kswapd [kernel] 0xf8
Jun 20 04:33:31 gate kernel: [_stext+0/28] stext [kernel] 0x0
Jun 20 04:33:31 gate kernel: [<c0105000>] stext [kernel] 0x0
Jun 20 04:33:31 gate kernel: [kernel_thread+38/48] kernel_thread [kernel] 0x26
Jun 20 04:33:31 gate kernel: [<c0106e7a>] kernel_thread [kernel] 0x26
Jun 20 04:33:31 gate kernel: [kswapd+0/680] kswapd [kernel] 0x0
Jun 20 04:33:31 gate kernel: [<c012ed6c>] kswapd [kernel] 0x0
Jun 20 04:33:31 gate kernel:
Jun 20 04:33:31 gate kernel:
Jun 20 04:33:32 gate kernel: Code: 0f 0b 59 58 85 f6 74 09 8b 46 20 85 c0 74 02 89 c7 85 ff 74
--
Lucky carrier,
Pavel.
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: kernel crash
2002-06-26 11:02 Pavel Gulchouck
@ 2002-06-26 19:03 ` James Stevenson
2002-06-27 8:00 ` Pavel Gulchouck
0 siblings, 1 reply; 10+ messages in thread
From: James Stevenson @ 2002-06-26 19:03 UTC (permalink / raw)
To: gul, linux-kernel
>
> Jun 20 04:33:30 gate kernel: ------------[ cut here ]------------
> Jun 20 04:33:30 gate kernel: kernel BUG at inode.c:1066!
> Jun 20 04:33:30 gate kernel: invalid operand: 0000
> Jun 20 04:33:30 gate kernel: ip_nat_ftp ipt_REJECT ipt_REDIRECT cls_u32
sch_tbf sch_cbq autofs smbfs ne2k-p
> Jun 20 04:33:30 gate kernel: CPU: 0
> Jun 20 04:33:31 gate kernel: EIP: 0010:[iput+47/496] Tainted: P
> Jun 20 04:33:31 gate kernel: EIP: 0010:[<c0148cdb>] Tainted: P
> Jun 20 04:33:31 gate kernel: EFLAGS: 00010286
what makes your kernel tainted ?
do you have some binary only drivers ?
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: kernel crash
2002-06-26 19:03 ` James Stevenson
@ 2002-06-27 8:00 ` Pavel Gulchouck
0 siblings, 0 replies; 10+ messages in thread
From: Pavel Gulchouck @ 2002-06-27 8:00 UTC (permalink / raw)
To: James Stevenson; +Cc: linux-kernel
Hi!
On Wed, Jun 26, 2002 at 08:03:20PM +0100, James Stevenson writes:
> > Jun 20 04:33:30 gate kernel: ------------[ cut here ]------------
> > Jun 20 04:33:30 gate kernel: kernel BUG at inode.c:1066!
> > Jun 20 04:33:30 gate kernel: invalid operand: 0000
> > Jun 20 04:33:30 gate kernel: ip_nat_ftp ipt_REJECT ipt_REDIRECT cls_u32 sch_tbf sch_cbq autofs smbfs ne2k-p
> > Jun 20 04:33:30 gate kernel: CPU: 0
> > Jun 20 04:33:31 gate kernel: EIP: 0010:[iput+47/496] Tainted: P
> > Jun 20 04:33:31 gate kernel: EIP: 0010:[<c0148cdb>] Tainted: P
> > Jun 20 04:33:31 gate kernel: EFLAGS: 00010286
>
> what makes your kernel tainted ?
It's a question for me.
> do you have some binary only drivers ?
No.
--
Lucky carrier,
Pavel.
^ permalink raw reply [flat|nested] 10+ messages in thread
* kernel crash
@ 2007-12-30 18:25 Jerry Geis
0 siblings, 0 replies; 10+ messages in thread
From: Jerry Geis @ 2007-12-30 18:25 UTC (permalink / raw)
To: linux-kernel
I am running kernel 2.6.23.9
last night I had a crash.
This was all that was in the /var/log/messages.
I run centos 5.1 with the above kernel.
This was late at night noone was using the machine.
The machine is an AMD 6400+ X2, NVIDIA (with nvidia drivers). Software
RAID with 2 seagate 500GIG drives as raid-1.
Any know issues with this?
Dec 29 20:28:04 devcentos5x64 kernel: Unable to handle kernel paging
request at 00000000ffff8160 RIP:
Dec 29 20:28:04 devcentos5x64 kernel: [<ffffffff88035502>]
:jbd:journal_commit_transaction+0x328/0x100a
Dec 29 20:28:04 devcentos5x64 kernel: PGD 101af3067 PUD 0
Dec 29 20:28:04 devcentos5x64 kernel: Oops: 0002 [1] SMP
Jerry
^ permalink raw reply [flat|nested] 10+ messages in thread
* kernel crash
@ 2011-10-06 21:59 Pau Espin Pedrol
0 siblings, 0 replies; 10+ messages in thread
From: Pau Espin Pedrol @ 2011-10-06 21:59 UTC (permalink / raw)
To: linux-kernel
Hi,
Since more a less kernel 3.0 my intel i5 has kernel panics (computer
stops working at all and keyboard leds start to blink).
I can't recall exactly, but I think it was more a less the same time
since I started using nvidia drivers with twinview (2 screens), which
could may be the cause?
I'm using archlinux, so I've been told the kernel is a vanilla kernel.
I can somehow "reproduce" the crash here. I mean, every day when I
boot my PC, I know a kernel crash will happen in the next 1-15 min
aprox. Then I reboot my PC and I don't have any kernel panic till next
day.
It sometimes happens at bootime, sometimes when I'm just logged in
into X server and doing work or when I halt the computer.
I was able to get some photos of the kernel backtrace when the crash
appears while booting/halting.
Here you have the link to a tar.gz file which contains several photos
with backtraces:
http://pespin.espeweb.net/tmp/kernel-panic/kernel-panic-bt.tar.gz
You can find more information of the PC in several text files I
uploaded tho the same dir: http://pespin.espeweb.net/tmp/kernel-panic/
Let's hope they are of help to you.
If you need me to try something or give me more information just tell me!
PS: Please add me to the CC when answering this mail as I am not
subscribed to the ml ;)
--
Pau Espin Pedrol
mail/jabber: pespin.shar@gmail.com
http://blog.espeweb.net
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2011-10-06 21:59 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-12-30 18:25 kernel crash Jerry Geis
-- strict thread matches above, loose matches on Subject: below --
2011-10-06 21:59 Pau Espin Pedrol
2002-06-26 11:02 Pavel Gulchouck
2002-06-26 19:03 ` James Stevenson
2002-06-27 8:00 ` Pavel Gulchouck
2001-04-12 15:16 Cyrille Ngalle
2001-04-12 15:31 ` Russell King
2001-04-13 13:16 ` nak
2001-04-02 16:40 Wayne.Brown
2001-04-01 10:15 nak
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox