From: Robert Gadsdon <robert@rgadsdon2.giointernet.co.uk>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.5 - panic when intensive disk access on 120GB firewire disk
Date: Mon, 05 Apr 2004 11:35:45 +0100 [thread overview]
Message-ID: <40713681.6060308@rgadsdon2.giointernet.co.uk> (raw)
In-Reply-To: <200404042356.21109.dtor_core@ameritech.net>
This fixes the problem on my system. All I get is a couple of
'ieee1394: unsolicited response packet received - no tlabel match'
messages on the console.
Many thanks.
Robert Gadsdon.
Dmitry Torokhov wrote:
> On Sunday 04 April 2004 03:22 pm, Robert Gadsdon wrote:
>
>>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]
>
>
> Could you please try the patch below.
>
> Thank you.
prev parent reply other threads:[~2004-04-05 10:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-04 20:22 2.6.5 - panic when intensive disk access on 120GB firewire disk Robert Gadsdon
2004-04-05 4:56 ` Dmitry Torokhov
2004-04-05 10:35 ` Robert Gadsdon [this message]
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=40713681.6060308@rgadsdon2.giointernet.co.uk \
--to=robert@rgadsdon2.giointernet.co.uk \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rgadsdon2@netscape.net \
/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