All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Kinneberg <kinnebergsteve@acmsystems.com>
To: "Philippe Gramoullé" <philippe.gramoulle@mmania.com>
Cc: Ben Collins <bcollins@debian.org>, Andrew Morton <akpm@digeo.com>,
	linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>,
	Linux1394dev <linux1394-devel@lists.sourceforge.net>
Subject: Re: 2.5.67-mm3: Bad: scheduling while atomic with IEEE1394 then hard freeze ( lockup on CPU0)
Date: 16 Apr 2003 10:32:54 -0700	[thread overview]
Message-ID: <1050514375.589.1843.camel@stevek> (raw)
In-Reply-To: <20030416184528.19c20372.philippe.gramoulle@mmania.com>

On Wed, 2003-04-16 at 09:45, Philippe Gramoullé wrote:
> 
> # dmesg
> oot is not IRM capable, resetting...
> ieee1394: Remote root is not IRM capable, resetting...
> ieee1394: Remote root is not IRM capable, resetting...
> ieee1394: Remote root is not IRM capable, resetting...
> [message repeated 178 times and as long as the DV Camcorder in turned on]

I realize this isn't the problem you're really concerned about, but the
above may happen if you are using a version of the 1394 code off the
linux-2.4 branch prior to the patch I sent to the list Monday that Ben
recently applied.  (You should be able to get around this without
downloading the latest code and recompiling by setting attempt_root=1
when insmodding ohci1394.

-- 
Steve Kinneberg
ACM Systems
3034 Gold Canal Drive
Rancho Cordova, CA  95670
Phone: (916) 463-7987
Email: kinnebergsteve@acmsystems.com


  reply	other threads:[~2003-04-16 17:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-15 22:05 2.5.67-mm3: Bad: scheduling while atomic with IEEE1394 then hard freeze ( lockup on CPU0) Philippe Gramoullé
2003-04-15 23:05 ` Andrew Morton
2003-04-15 23:17   ` Philippe Gramoullé
2003-04-15 23:34     ` Andrew Morton
2003-04-16  5:54       ` Greg KH
2003-04-16 16:58         ` Patrick Mochel
2003-04-16 23:40           ` Philippe Gramoullé
2003-04-17  3:54             ` Greg KH
2003-04-16  0:49   ` Ben Collins
2003-04-16 16:45     ` Philippe Gramoullé
2003-04-16 17:32       ` Steve Kinneberg [this message]
2003-04-16 22:30         ` Philippe Gramoullé
2003-04-16 23:35           ` Steve Kinneberg
2003-04-16 23:52             ` Philippe Gramoullé
2003-04-17  2:48           ` Dan Maas
2003-04-16 18:09       ` Ben Collins
2003-04-18 18:51   ` Florin Iucha

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=1050514375.589.1843.camel@stevek \
    --to=kinnebergsteve@acmsystems.com \
    --cc=akpm@digeo.com \
    --cc=bcollins@debian.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=philippe.gramoulle@mmania.com \
    /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.