From: Robert Gadsdon <robert@rgadsdon2.giointernet.co.uk>
To: linux kernel <linux-kernel@vger.kernel.org>
Subject: 2.6.5 - panic when intensive disk access on 120GB firewire disk
Date: Sun, 04 Apr 2004 21:22:58 +0100 [thread overview]
Message-ID: <40706EA2.7040900@rgadsdon2.giointernet.co.uk> (raw)
Kernel panic from 2.6.5 'final' when running slocate (updatedb)
accessing 120GB firewire disk:
Oops: 00002 [#1]
PREEMPT SMP
CPU: 0
EIP: 0060:[<f8a10a27>] Not tainted
EFLAGS: 00010047 (2.6.5)
EIP is at hpsb_packet_sent+0x27/0x90 [ieee1394]
eax: 00100100 ebx: f76e0000 ecx: e1fea3c0 edx: 00200200
esi: 00000001 edi: e1fea3c0 ebp: f76e2078 esp: c042df14
ds : 007b es: 007b ss : 0068
Process swapper (pid: 0, threadinfo=c042c000 task=c03aa160)
Stack: f76e21bc f89329e8 f76e0000 e1fea3c0 00000001 f75f8da0 f76e21e8
00000292
f76e21fc 00000000 c042c000 c045b5d8 c0127d93 f76e21bc 00000001
c042b028
0000000a 00000046 c0127ac7 c042b028 c042c000 c042c000 00000009
00000020
Call Trace :
[<f89329e8>] dma_trm_tasklet+0xa8/0x1b0 [ohci1394]
[<c0127d93>] tasklet_action+0x73/0xe0
[<c0127ac7>] do_softirq+0xc7/0xd0
[<c010b82b>] do_IRQ+0x13b/0x1a0
[<c0109928>] common_interrupt+0x18/0x20
[<c0106970>] default_idle+0x0/0x40
[<c010699c>] default_idle+0x2c/0x40
[<c0106a2b>] cpu_idle+0x3b/0x50
[<c042e4c0>] unknown_bootoption +0x0/0x120
[<c042e95b>] start_kernel+0x1bb/0x210
[<c042e4c0>] unknown_bootoption+0x0/0x120
Code: 89 50 04 89 02 c7 41 04 00 02 20 00 c7 01 00 01 10 00 c6 41
<0>Kernel panic: Fatal exception in interrupt
In interrupt handler - not syncing
Similar problem with 2.6.4 and 2.6.5-rc and 2.6.5-rc-mm kernels, and is
100% repeatable..
Robert Gadsdon
next reply other threads:[~2004-04-04 20:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-04 20:22 Robert Gadsdon [this message]
2004-04-05 4:56 ` 2.6.5 - panic when intensive disk access on 120GB firewire disk Dmitry Torokhov
2004-04-05 10:35 ` Robert Gadsdon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40706EA2.7040900@rgadsdon2.giointernet.co.uk \
--to=robert@rgadsdon2.giointernet.co.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox