All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Ben Collins <bcollins@debian.org>
Cc: linux-kernel@vger.kernel.org
Subject: OOPS when copying data from local to an external drive (ieee1394)
Date: Sun, 7 Mar 2004 01:39:30 -0500	[thread overview]
Message-ID: <200403070139.30268.dtor_core@ameritech.net> (raw)

Hi,

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
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
recal_task_prio+0xb4/0x1f0
tasklet_action
do_softirq
do_IRQ
common_interrupt
acpi_process_idle
default_idle
rest_init
default_init
rest_init
cpu_idle
start_kernel
unknown_bootparam

Code: ...
Kernel panic: Fatal exception in interrupt
In interrupt handler - not synching


This OOPS is with NVIDIA module loaded but I have seen exactly the
same trace without the module loaded.

-- 
Dmitry

             reply	other threads:[~2004-03-07  6:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-07  6:39 Dmitry Torokhov [this message]
2004-03-08  6:50 ` OOPS when copying data from local to an external drive (ieee1394) Zwane Mwaikambo
2004-03-09  7:11   ` Dmitry Torokhov
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=200403070139.30268.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=bcollins@debian.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.