public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roger Leblanc <r_leblanc@videotron.ca>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Deadlock in kernel on USB shutdown
Date: Wed, 02 Jan 2002 19:13:35 -0500	[thread overview]
Message-ID: <3C33A22F.40906@videotron.ca> (raw)

----- Original Message -----
From: "Greg KH" <greg@kroah.com>
To: "Roger Leblanc" <r_leblanc@videotron.ca>
Cc: <linux-kernel@vger.kernel.org>
Sent: Wednesday, January 02, 2002 9:40 AM
Subject: Re: Deadlock in kernel on USB shutdown



>> On Tue, Jan 01, 2002 at 04:48:41PM -0500, Roger Leblanc wrote:
>
>>> > Hi,
>>> >
>>> > I just compiled version 2.4.17 of the Linux kernel for my Pentium III.
>>> > It is compiled with modular USB support so I can run my USB scanner (an
>>> > Epson Perfection 1200U).
>>> >
>>> > The scanner works fine but the system freeses when I shut it down. I
>>> > investigated a bit and found that in the file:
>>> > <kernel_root>/drivers/usb/usb.c
>>> > in function:
>>> > usb_disconnect(struct usb_device **pdev)
>>> >
>>> > there is a call to function:
>>> > usbdevfs_remove_device(dev)
>>> > at line 2423.
>>> >
>>> > That is the exact point where it freeses. If I comment out that line,
>>> > everything goes fine. I know! This is not the proper way to fix it! But
>>> > at least, it fixes my problem. Since I'm not a kernel expert, I will
>>> > leave it to you to find the right way to fix it.
>>
>>
>> Does the system lock up when you unload the usbcore module by hand
>> without shutting the system down?
>>
>> Are your init scripts unmounting the usbdevfs filesystem properly before
>> trying to unload the usbcore module?
>
It doesn't get that far. The first thing my init script (or Mandrake 8.1 
script) does at shutdown is to run modprobe -r on modules usb-ohci, 
usb-uhci and uhci. The system freeses when it gets to usb-uhci. It does 
it also if I run these commands on the command line.

Thanks

Roger




             reply	other threads:[~2002-01-03  0:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-03  0:13 Roger Leblanc [this message]
2002-01-03  0:18 ` Deadlock in kernel on USB shutdown Greg KH
2002-01-03  0:25   ` Roger Leblanc
2002-01-03  0:28     ` Greg KH
2002-01-03  1:09       ` Roger Leblanc
2002-01-03  1:32         ` Greg KH
2002-01-03  2:10           ` Roger Leblanc
2002-01-03  3:03             ` Greg KH
2002-01-03  3:26               ` Roger Leblanc
2002-01-03 18:57                 ` Greg KH
2002-01-04 21:46                   ` Roger Leblanc
     [not found] <000701c193f6$4ca368a0$6800000a@brownell.org>
2002-01-03  2:25 ` Roger Leblanc
  -- strict thread matches above, loose matches on Subject: below --
2002-01-01 21:48 Roger Leblanc
2002-01-02 14:40 ` Greg KH

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=3C33A22F.40906@videotron.ca \
    --to=r_leblanc@videotron.ca \
    --cc=greg@kroah.com \
    --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