public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Collins <bcollins@debian.org>
To: Zygo Blaxell <uixjjji1@umail.furryterror.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.21 IDE and IEEE1394+SBP2 regressions, orinoco_pci progress
Date: Tue, 8 Jul 2003 22:12:01 -0400	[thread overview]
Message-ID: <20030709021201.GH5830@phunnypharm.org> (raw)
In-Reply-To: <pan.2003.07.08.22.25.12.249185.15455@umail.hungrycats.org>

> The IEEE1394+SBP2 driver combination in 2.4.21 has problems.  When the
> kernel is compiled for single-processor the SBP2 driver can't log into my
> SBP2 devices and hangs rmmod when the module is removed--in other words,
> it's useless.  When compiled for SMP, the SBP2 driver works more or less
> normally, but still requires an IEEE1394 bus reset to work the second time
> a device is attached.  Note this is a laptop, so it only has one
> processor.

You did do rescan-scsi-bus.sh? What do you mean by "can't login"? Do you
mean it shows a login timeout, or that it doesn't even try? What does
/proc/bus/ieee1394/devices show?

Do I understand correctly that this is under cardbus?

-- 
Debian     - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo       - http://www.deqo.com/

  reply	other threads:[~2003-07-09  3:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-09  2:49 2.4.21 IDE and IEEE1394+SBP2 regressions, orinoco_pci progress Zygo Blaxell
2003-07-09  2:12 ` Ben Collins [this message]
2003-07-09 14:54   ` Zygo Blaxell
2003-07-09  3:13 ` jiho
2003-07-09 13:50   ` Zygo Blaxell
     [not found]   ` <E19aFLE-0003NF-00@satsuki.furryterror.org>
2003-07-10  2:17     ` jiho
2003-07-09  9:34 ` Benjamin Herrenschmidt
2003-07-09 14:31   ` Zygo Blaxell

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=20030709021201.GH5830@phunnypharm.org \
    --to=bcollins@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=uixjjji1@umail.furryterror.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox