The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.12-rc2-mm1: ieee1394 process hang
Date: Thu, 7 Apr 2005 20:07:32 +0100	[thread overview]
Message-ID: <20050407190732.GB26850@linux-mips.org> (raw)
In-Reply-To: <20050407015845.6fb3c171.akpm@osdl.org>

On Thu, Apr 07, 2005 at 01:58:45AM -0700, Andrew Morton wrote:

> > I'm having problems with 1394 in 2.6.12-rc2-mm1.  When I connect my
> >  Apple iSight camera, it is not detected; repeated
> >  connections/disconnections don't help.  When I tried to rmmod all the
> >  appropriate modules (rmmod video1394 raw1394 ohci1394 ieee1394), the
> >  rmmod command hung.  Alt-Sysreq-t shows this:
> 
> I don't think there have been any 1394 changes recently.  This bug might be
> more fallout from Pat's recent changes.
> 
> More attempts have been made to fix that stuff up.  Maybe you could try
> http://www.zip.com.au/~akpm/linux/patches/stuff/2.6.12-rc2-mm1.5.gz

I'm not so sure, last week I had similar results with an external IEEE 1394
disk drive.  On the first attempt it wasn't detected, in the 2nd and 3rd
attempt detecting worked ok.  After copying a data for like 2min the system
paniced with no useful data in the log.  Further attempts resulted in more
hangs and panics.  The kernel was the latest and greatest FC3 kernel,
kernel-2.6.10-1.770_FC3.

(I'm a 1h flight away from the system so can't do any more testing on that
system)

  Ralf

      reply	other threads:[~2005-04-07 19:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-07  8:34 2.6.12-rc2-mm1: ieee1394 process hang Jeremy Fitzhardinge
2005-04-07  8:58 ` Andrew Morton
2005-04-07 19:07   ` Ralf Baechle [this message]

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=20050407190732.GB26850@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=akpm@osdl.org \
    --cc=jeremy@goop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox