From: Bradley Chapman <kakadu_croc@yahoo.com>
To: Ben Collins <bcollins@debian.org>
Cc: linux1394-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Beaver In Detox AND IEEE1394 badness message
Date: Wed, 26 Nov 2003 14:37:09 -0800 (PST) [thread overview]
Message-ID: <20031126223709.37332.qmail@web40911.mail.yahoo.com> (raw)
In-Reply-To: <20031126222052.GA462@phunnypharm.org>
Mr. Collins,
--- Ben Collins <bcollins@debian.org> wrote:
> > blk: queue dfd658cc, I/O limit 4095Mb (mask 0xffffffff)
> >
> > The badness message appears AFTER this line:
> >
> > ohci1394_0: OHCI-1394 1.1 (PCI): IRQ=[10] MMIO=[e8207000-e82077ff] Max
> > Packet=[2048]
> >
> > It used to appear BEFORE this line. Do the IEEE1394 fixes in the detoxed beaver
> > kernel have something to do with that? Or was it a fix in an earlier kernel?
>
> Odd, I fixed one, and another one pops up. Sucks that it doesn't show up
> for me, but thanks for the traceback.
You're welcome.
>
> Do things operate normally for you? Disabling kernel debug will kill the
> message (the symptom, not the problem). With the fixes I sent Linus, I
> am mainly interested in it just working.
Unfortunately, this is only an academic exercise -- I don't actually have any
IEEE1394 devices to test this driver with! *blushes*
However, a bug is a bug is a bug, so I reported it anyway. If it's absolutely
necessary, I think I can get my hands on some IEEE1394 stuff from a few people
I know and test it with that.
Brad
=====
__________________________________
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/
next prev parent reply other threads:[~2003-11-26 22:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 22:19 Beaver In Detox AND IEEE1394 badness message Bradley Chapman
2003-11-26 22:20 ` Ben Collins
2003-11-26 22:37 ` Bradley Chapman [this message]
2003-11-27 1:26 James J Myers
2003-11-27 9:09 Bob Gill
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=20031126223709.37332.qmail@web40911.mail.yahoo.com \
--to=kakadu_croc@yahoo.com \
--cc=bcollins@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).