From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Calum Selkirk <cselkirk@xs4all.nl>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: firewire in 2.4.21-ben2
Date: 27 Jul 2003 12:06:31 -0400 [thread overview]
Message-ID: <1059321991.529.4.camel@gaston> (raw)
In-Reply-To: <20030726143945.GJ24614@xs4all.nl>
On Sat, 2003-07-26 at 10:39, Calum Selkirk wrote:
> * Calum Selkirk [cselkirk@xs4all.nl] [2003-07-17 12:11 +0200]:
>
> > * Benjamin Herrenschmidt [benh@kernel.crashing.org] [2003-07-15 11:30 +0200]:
> >
> > [snip]
> > > > After I reboot back in 2.4.20-ben10 everything works fine...
> > >
> > > That's a change in the firewire layer, you have to trigger a scsi
> > > probe yourself now. Either using the rescan-scsi-bus.sh script, or the
> > > scsiadd command for example
> >
> > just FYI, I have had the kernel oops on one occasion when rescaning the
> > scsi bus this way (with a 2.4.21-ben2). Sorry, wasn't able to get a
> > backtrace, though I will attempt to if it happens again.
>
> OK .. attatched is a backtrace (hopefully accuratly transcribed) and
> snippit from /var/log/messages.
>
> As i said previously I haven't been able to reproduce this, it's only
> happened to me on one occassion (the above backtrace is from another
> user/machine). Might this be related to the other ieee1394 bug, where
> unloading ohci1394 after sleep will oops?
A backtrace with just numbers is useless, you should either provide
insmod -m output or run the oops through ksymoops.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-07-27 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 19:19 firewire in 2.4.21-ben2 daRonin
2003-07-15 9:30 ` Benjamin Herrenschmidt
2003-07-17 10:11 ` Calum Selkirk
2003-07-26 14:39 ` Calum Selkirk
2003-07-27 16:06 ` Benjamin Herrenschmidt [this message]
2003-07-27 20:56 ` Calum Selkirk
-- strict thread matches above, loose matches on Subject: below --
2003-07-15 4:40 Bill Fink
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=1059321991.529.4.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=cselkirk@xs4all.nl \
--cc=linuxppc-dev@lists.linuxppc.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.