linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stelian Pop <stelian.pop@fr.alcove.com>
To: Ben Collins <bcollins@debian.org>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: The IEEE-1394 saga continued... [ was: IEEE-1394 problem on init ]
Date: Sat, 26 Apr 2003 18:10:09 +0200	[thread overview]
Message-ID: <20030426161009.GC18917@vitel.alcove-fr> (raw)
In-Reply-To: <20030426143445.GC2774@phunnypharm.org>

On Sat, Apr 26, 2003 at 10:34:45AM -0400, Ben Collins wrote:

> > And guess what ? The new patch broke (again) my setup. When I plug
> > in my iPod, the scsi layer does not see it anymore.
> 
> Good lord would you calm down.

No. You did broke the subsystem in several occasions, you do this
at the bad moment, and now you introduced a change in behaviour
in a stable kernel release, between -rc1 and -rc2, without any
warning. I think I have enough reasons to be angry.

> Run the rescan-scan-scsi.sh script floating around. Out own website
> describes having to use this for 2.4 kernels.
[...]

The FAQ on linux1394 site was indeed updated 2 days ago. I'm sorry
I didn't think to look there.

Before posting, I did try to check the linux1394 mailing lists for 
information. linux1394-announce has no new mails since march, 
linux1394-devel didn't seem to contain anything obvious about this
(besides a thread "Re: Problem with Kernel 2.4.21-rc1 - latest svn"
which I couldn't read due to sourceforge problems - it kept saying
"no such forum"...)

I did look at the subversion checkin' log. I did look at the bitkeeper
checkin' log. Nothing there.

> It was either leave sbp2
> oopsing, or rewrite the load logic so that there was no way for left
> over scsi cruft. The side affect is that the only hot-plug situation
> ieee1394 had in 2.4 is gone.

Strange, usb-storage seems to work quite fine with respect to the
scsi layer and hotplug...

> Before, loading sbp2 before loading ohci1394 gave the same affect. Now,
> loading sbp2 before ohci1394 also requires running rescan-scan-scsi.sh.
> Blame the scsi layer, not me.

BTW: hotplug removing is still half broken: the hotplug remove event
is send only when the device is physically disconnected. If I remove
the sbp2 module with rmmod, I'll get nothing.

This means that if you do
	rmmod sbp2
	modprobe sbp2
your SCSI device will be lost and you'll have to call 'rescan-scsi-bus'
by hand...

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

-- 
Stelian Pop <stelian.pop@fr.alcove.com>
Alcove - http://www.alcove.com

  reply	other threads:[~2003-04-26 15:58 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-23 12:29 IEEE-1394 problem on init [ was Re: Linux 2.4.21-rc1 ] Tony Spinillo
2003-04-23 12:53 ` Stelian Pop
2003-04-23 13:01   ` Ben Collins
2003-04-23 13:22     ` Stelian Pop
2003-04-23 13:32       ` Ben Collins
2003-04-23 13:46         ` Ben Collins
2003-04-23 13:58         ` Stelian Pop
2003-04-23 13:54           ` Ben Collins
2003-04-23 14:21             ` Stelian Pop
2003-04-23 14:23               ` Ben Collins
2003-04-23 14:51                 ` Stelian Pop
2003-04-23 14:44                   ` Ben Collins
2003-04-23 14:48                   ` Ben Collins
2003-04-23 15:29                     ` Stelian Pop
2003-04-23 19:13                       ` Marcelo Tosatti
2003-04-23 19:05                         ` Ben Collins
2003-04-23 19:27                           ` Marcelo Tosatti
2003-04-23 20:20                         ` Stelian Pop
2003-04-23 20:24                           ` Ben Collins
2003-04-23 20:42                             ` Stelian Pop
2003-04-26  8:29                               ` The IEEE-1394 saga continued... [ was: IEEE-1394 problem on init ] Stelian Pop
2003-04-26 14:34                                 ` Ben Collins
2003-04-26 16:10                                   ` Stelian Pop [this message]
2003-04-26 16:12                                     ` Ben Collins
2003-04-26 17:00                                       ` Stelian Pop
2003-04-26 16:59                                         ` Ben Collins
2003-04-26 14:40                                 ` Ben Collins
2003-04-26 16:23                                   ` Stelian Pop
2003-04-26 16:25                                     ` Ben Collins
2003-04-26 17:15                                       ` Stelian Pop
2003-04-24 21:44                         ` IEEE-1394 problem on init [ was Re: Linux 2.4.21-rc1 ] Bill Davidsen
2003-04-24 21:41                           ` Ben Collins
2003-04-25 18:06                             ` Bill Davidsen
2003-04-25 18:16                               ` Ben Collins
2003-04-26 10:36                                 ` Bill Davidsen

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=20030426161009.GC18917@vitel.alcove-fr \
    --to=stelian.pop@fr.alcove.com \
    --cc=bcollins@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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).