mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kthread conversion: convert ieee1394 from kernel_thread
Date: Sun, 18 Jun 2006 12:29:51 +0200	[thread overview]
Message-ID: <44952B1F.2000109@s5r6.in-berlin.de> (raw)
In-Reply-To: <44944D8A.6090808@s5r6.in-berlin.de>

I wrote:
> I will try to rework this patch

While doing so I discovered an old bug which happens with current code 
as well as with Linux 2.6.16.x and 2.6.15.x, maybe also on older kernels:

When "modprobe ohci1394" is followed shortly by "modprobe -r ohci1394" 
(say, 1 second after the previous modprobe finished), one of the 
following may happen:
  - kernel panic due to exception in interrupt
    (happened on 2.6.15.x preempt uniprocessor)
    or
  - modprobe -r hangs in D state, as does knodemgrd_0
    (happened on 2.6.16.x preempt SMP on a uniprocessor machine).

I have two FireWirew host adapters installed. The knodemgrd_1 slept 
interruptibly (S state) while the other slept uninterruptibly (D state) 
right after modprobe -r was issued. This happens with or without other 
nodes attached to the FireWire ports. Host adapters are based on a TI 
1394b chip (host 0) and on a VIA 1394a chip (host 1).

"All's right with the world" if a longer pause is put between modprobe 
and modprobe -r, say 4 seconds.

(I will add a bugzilla entry and try to resolve this eventually...)
-- 
Stefan Richter
-=====-=-==- -==- =--=-
http://arcgraph.de/sr/

  reply	other threads:[~2006-06-18 10:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-10 14:31 Serge E. Hallyn
2006-06-10 14:42 ` Christoph Hellwig
2006-06-10 15:11   ` Stefan Richter
2006-06-10 15:42     ` Christoph Hellwig
2006-06-10 16:34       ` Ben Collins
2006-06-10 16:38         ` Christoph Hellwig
2006-06-10 18:08           ` Ben Collins
2006-06-10 18:37             ` Christoph Hellwig
2006-06-17 18:44               ` Stefan Richter
2006-06-18 10:29                 ` Stefan Richter [this message]
2006-06-18 16:57                 ` [PATCH 2.6.17-rc6-mm2 0/6] ieee1394: nodemgr: misc API conversions Stefan Richter
2006-06-18 16:57                   ` [PATCH 2.6.17-rc6-mm2 1/6] ieee1394: nodemgr: remove unnecessary includes Stefan Richter
2006-06-18 16:59                     ` [PATCH 2.6.17-rc6-mm2 2/6] ieee1394: do not spawn a kernel_thread for user-initiated bus rescan Stefan Richter
2006-06-18 17:00                       ` [PATCH 2.6.17-rc6-mm2 3/6] ieee1394: make module parameter ignore_drivers writable Stefan Richter
2006-06-18 17:02                         ` [PATCH 2.6.17-rc6-mm2 4/6] ieee1394: nodemgr: switch to kthread API Stefan Richter
2006-06-18 17:03                           ` [PATCH 2.6.17-rc6-mm2 5/6] ieee1394: nodemgr: replace reset semaphore Stefan Richter
2006-06-18 17:05                             ` [PATCH 2.6.17-rc6-mm2 6/6] ieee1394: convert nodemgr_serialize semaphore to mutex Stefan Richter
2006-06-10 18:12           ` [PATCH] kthread conversion: convert ieee1394 from kernel_thread Stefan Richter

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=44952B1F.2000109@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --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

all inboxes | Powered by JetHome®