From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: Ben Collins <bcollins@debian.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: OOPS when copying data from local to an external drive (ieee1394)
Date: Tue, 9 Mar 2004 02:11:33 -0500 [thread overview]
Message-ID: <200403090211.33930.dtor_core@ameritech.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0403070229490.29087@montezuma.fsmlabs.com>
On Monday 08 March 2004 01:50 am, Zwane Mwaikambo wrote:
> On Sun, 7 Mar 2004, Dmitry Torokhov wrote:
>
> > I started getting oopses when cpying data from local IDE to an external
> > Firewire drive. Not always, but quite often. The kernel is a bk pull a
> > day before 2.6.4-rc2 was released, I do not see any ieee1394 updates
> > since.
> >
> > Unfortunately the oops was not saves in the logs, so here is what I managed
> > to write down:
>
> > Oops: 00002 [#1]
> > PREEMPT
> > CPU: 0
> > EIP: 0060 [<c0243d087>] Tainted: P
> > EFLAGS: 00010047
> > EIP is at hpsb_packet_sent+0x86/0x90
> > eax: 00100100 ebx: dfd74000 ecx: dd6edfb0 edx: 00200200
>
> A spot of linked list corruption.
>
> > esi: 00000001 edi: dd6cdf60 ebp: c03e3ee0 esp: c03c3edc
> > ds: 007b es: 007b ss: 0068
> > Process swapper (pid: 0; threadinfo=c03c2000, task=c034a800)
> > ....
> > Call trace:
> > [<co25306e>] dma_trm_tasklet+0xae/0x1b0
>
> Does this patch help any?
>
Unfortunately I am still getting oopses with exactly the same call trace.
On top of that I am now seeing the following in the logs:
Mar 9 01:41:21 core kernel: ieee1394: sbp2: aborting sbp2 command
Mar 9 01:41:21 core kernel: Write (10) 00 11 27 de 17 00 00 f8 00
Mar 9 01:41:21 core kernel: ieee1394: sbp2: aborting sbp2 command
Mar 9 01:41:21 core kernel: Write (10) 00 11 27 df 0f 00 00 f8 00
Mar 9 01:41:21 core kernel: ieee1394: sbp2: aborting sbp2 command
Mar 9 01:41:21 core kernel: Write (10) 00 11 27 e0 07 00 00 f8 00
Mar 9 01:41:21 core kernel: ieee1394: sbp2: aborting sbp2 command
Mar 9 01:41:21 core kernel: Write (10) 00 11 27 e0 ff 00 00 f8 00
Mar 9 01:41:21 core kernel: ieee1394: sbp2: aborting sbp2 command
Mar 9 01:41:21 core kernel: Write (10) 00 11 27 e1 f7 00 00 f8 00
Mar 9 01:41:21 core kernel: ieee1394: sbp2: aborting sbp2 command
Mar 9 01:41:21 core kernel: Write (10) 00 11 27 e3 e7 00 00 f8 00
Mar 9 01:41:21 core kernel: ieee1394: sbp2: aborting sbp2 command
Mar 9 01:41:22 core kernel: Write (10) 00 11 27 e4 df 00 00 f8 00
Mar 9 01:41:23 core kernel: ieee1394: sbp2: aborting sbp2 command
Mar 9 01:41:23 core kernel: Write (10) 00 11 27 e5 d7 00 00 f8 00
Mar 9 01:41:26 core kernel: ieee1394: sbp2: sbp2util_node_write_no_wait failed
Mar 9 01:41:28 core last message repeated 8 times
Mar 9 01:41:56 core kernel: ieee1394: sbp2: aborting sbp2 command
Mar 9 01:41:56 core kernel: Write (10) 00 11 2a f8 ff 00 00 f8 00
Mar 9 01:41:56 core kernel: ieee1394: sbp2: aborting sbp2 command
Mar 9 01:41:56 core kernel: Write (10) 00 11 2a f9 f7 00 00 f8 00
Mar 9 01:41:56 core kernel: ieee1394: sbp2: aborting sbp2 command
Mar 9 01:41:56 core kernel: Write (10) 00 11 2a fa ef 00 00 f8 00
Mar 9 01:41:56 core kernel: ieee1394: sbp2: aborting sbp2 command
Mar 9 01:41:56 core kernel: Write (10) 00 11 2a fb e7 00 00 f8 00
Mar 9 01:41:56 core kernel: ieee1394: sbp2: aborting sbp2 command
Mar 9 01:41:56 core kernel: Write (10) 00 11 2a fc df 00 00 f8 00
Mar 9 01:41:56 core kernel: ieee1394: sbp2: aborting sbp2 command
Mar 9 01:41:56 core kernel: Write (10) 00 11 2a fe cf 00 00 f8 00
I did not have these messages before. The kernel was pulled today
from bkbits plus your patch (and some of my patches but they only
affect input drivers).
--
Dmitry
next prev parent reply other threads:[~2004-03-09 7:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 6:39 OOPS when copying data from local to an external drive (ieee1394) Dmitry Torokhov
2004-03-08 6:50 ` Zwane Mwaikambo
2004-03-09 7:11 ` Dmitry Torokhov [this message]
2004-03-09 15:16 ` Zwane Mwaikambo
2004-03-09 15:41 ` Ben Collins
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=200403090211.33930.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=bcollins@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linuxpower.ca \
/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