mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sean Neakums <sneakums@zork.net>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: USB: gphoto2 hangs, device disconnection oddity (was Re: 2.6.5-rc1-mm2)
Date: Thu, 18 Mar 2004 20:31:16 +0000	[thread overview]
Message-ID: <6u4qslhp7v.fsf@zork.zork.net> (raw)
In-Reply-To: <20040317201454.5b2e8a3c.akpm@osdl.org> (Andrew Morton's message of "Wed, 17 Mar 2004 20:14:54 -0800")

On one machine (a Dell Inspiron 4100 laptop), with 2.6.5-rc1-mm2 and
2.6.5-rc1-mm1, but not with 2.6.5-rc1, gphoto2 hangs trying to talk to
my camera:

    $ ps -C gphoto2 -o comm,s,wchan
    COMMAND          S WCHAN
    gphoto2          D usb_disable_device

However, I was able to connect, mount and perform large transfers to a
USB Storage device without any problems, although the device still
shows up in lsusb after it is umounted and disconnected, and plugging
in the camera has no effect, which is how I first noticed this problem.

Here's the Inspiron's controller:

    $ sudo lspci -s 00:1d.0 -vvvv
    00:1d.0 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #1) (rev 01) (prog-if 00 [UHCI])
            Subsystem: Intel Corp.: Unknown device 4541
            Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
            Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
            Latency: 0
            Interrupt: pin A routed to IRQ 11
            Region 4: I/O ports at bf80 [size=32]

But on another machine (Gigabyte 6VTXD board, VIA chipset) running
2.6.5-rc1-mm1, gphoto2 works fine.  Here's its controller:

    $ sudo lspci -s 00:07 -vvvv
    [...]
    00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 1a) (prog-if 00 [UHCI])
            Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
            Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
            Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
            Latency: 64, Cache Line Size: 0x08 (32 bytes)
            Interrupt: pin D routed to IRQ 10
            Region 4: I/O ports at c800 [size=32]
            Capabilities: [80] Power Management version 2
                    Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                    Status: D0 PME-Enable- DSel=0 DScale=0 PME-

    00:07.3 USB Controller: VIA Technologies, Inc. USB (rev 1a) (prog-if 00 [UHCI])
            Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
            Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
            Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
            Latency: 64, Cache Line Size: 0x08 (32 bytes)
            Interrupt: pin D routed to IRQ 10
            Region 4: I/O ports at cc00 [size=32]
            Capabilities: [80] Power Management version 2
                    Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                    Status: D0 PME-Enable- DSel=0 DScale=0 PME-
    [...]


  parent reply	other threads:[~2004-03-18 20:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-18  4:14 2.6.5-rc1-mm2 Andrew Morton
2004-03-18 16:01 ` 2.6.5-rc1-mm2 John Cherry
2004-03-18 20:31 ` Sean Neakums [this message]
2004-03-19  9:27 ` 2.6.5-rc1-mm2 Marc-Christian Petersen
2004-03-30 19:27 ` 2.6.5-rc1-mm2 Jesse Barnes
2004-03-30 19:36   ` 2.6.5-rc1-mm2 Andrew Morton
2004-03-30 19:44     ` 2.6.5-rc1-mm2 Jesse Barnes
2004-03-31 19:02       ` 2.6.5-rc1-mm2 Jesse Barnes
2004-03-31 20:06         ` 2.6.5-rc1-mm2 Andrew Morton
2004-03-31 23:15           ` 2.6.5-rc1-mm2 Jesse Barnes
2004-03-31 23:56             ` 2.6.5-rc1-mm2 Andrew Morton
2004-03-31 23:58               ` 2.6.5-rc1-mm2 Jesse Barnes
2004-04-01  0:16                 ` 2.6.5-rc1-mm2 Jesse Barnes
2004-04-01 19:28               ` 2.6.5-rc1-mm2 Jesse Barnes

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=6u4qslhp7v.fsf@zork.zork.net \
    --to=sneakums@zork.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-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®