On Thursday, 9 August 2007 17:20, Mariusz Kozlowski wrote:
> > > > Happens every time I reattach usb pen drive.
> > > >
> > > > usb 1-2: new high speed USB device using ehci_hcd and address 10
> > > > usb 1-2: configuration #1 chosen from 1 choice
> > > > scsi6 : SCSI emulation for USB Mas
> > > Happens every time I reattach usb pen drive.
> > >
> > > usb 1-2: new high speed USB device using ehci_hcd and address 10
> > > usb 1-2: configuration #1 chosen from 1 choice
> > > scsi6 : SCSI emulation for USB Mass Storage devices
> > > usb 1-2: new device found, idVendor=13fe, idProduct
On Thursday, 9 August 2007 16:43, Alan Stern wrote:
> On Thu, 9 Aug 2007, Mariusz Kozlowski wrote:
>
> > Hello,
> >
> > Happens every time I reattach usb pen drive.
> >
> > usb 1-2: new high speed USB device using ehci_hcd and address 10
> > usb 1-2: configuration #1 chosen from 1 choice
> >
On Thu, 9 Aug 2007, Mariusz Kozlowski wrote:
> Hello,
>
> Happens every time I reattach usb pen drive.
>
> usb 1-2: new high speed USB device using ehci_hcd and address 10
> usb 1-2: configuration #1 chosen from 1 choice
> scsi6 : SCSI emulation for USB Mass Storage devices
> usb 1-2: new
On Tue, 31 Jul 2007, Matthew Dharm wrote:
> What the heck happened to your logs? It looks like about 75% of the data
> is being lost from the log file...
With all the USB I/O activity going on, syslogd must not be getting
enough CPU time to capture all the kernel log data.
If more detail is ne
On Sun, Jul 29, 2007 at 08:00:01PM -0700, Linus Torvalds wrote:
>
>
> On Fri, 27 Jul 2007, Alan Stern wrote:
> >
> > I don't think it's a refcounting problem. My guess is that the
> > underlying cause is the bug in your urb->status removal patch for
> > usb_start_wait_urb() -- the one I fixed
On Fri, 27 Jul 2007, Alan Stern wrote:
>
> I don't think it's a refcounting problem. My guess is that the
> underlying cause is the bug in your urb->status removal patch for
> usb_start_wait_urb() -- the one I fixed here:
>
> http://marc.info/?l=linux-usb-devel&m=118531582013355&w=2
>
> Of
On Fri, 27 Jul 2007, Oliver Neukum wrote:
> Am Donnerstag 26 Juli 2007 schrieb Greg KH:
> > Alan and Oliver, was this caused by the autosuspend changes for
> > usb-storage?
>
> The oops itself looks like refcounting. What caused the initial io error
> does not become clear from the log. It is pos
Am Donnerstag 26 Juli 2007 schrieb Greg KH:
> Alan and Oliver, was this caused by the autosuspend changes for
> usb-storage?
The oops itself looks like refcounting. What caused the initial io error
does not become clear from the log. It is possible that the device cannot
stand suspension. But ther
Am Dienstag, 19. Juni 2007 schrieb Pete Zaitcev:
> On Tue, 19 Jun 2007 11:11:18 +0800, "jidong xiao" <[EMAIL PROTECTED]> wrote:
>
> > But I remember, the reason we use sg is that, we can transfer
> > several buffers in one DMA operation, thus we can speed things up
> > accordingly because we tur
Maybe we can retry at this situation.
On 6/18/07, Oliver Neukum <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I am looking at usb_sg_init().
>
> void usb_sg_wait (struct usb_sg_request *io)
> {
>int i, entries = io->entries;
>
>/* queue the urbs. */
>spin_lock_irq (&io-
Please configure your email client to wrap long lines after about 75
columns.
On Mon, 19 Feb 2007, Mukesh Kohli wrote:
> > After seeing the transactions by hooking analyzer in between I am seeing
> > the failure happening due to ACK not being sent by the controller in
> > response to data (512 b
Thanks a lot for your reply. Kindly see my responces inline.
On Mon, 19 Feb 2007, Mukesh Kohli wrote:
> Hello Guys,
>
> I am trying to create a duplicate copy of a file onto a USB 2.0 device
> (memory stick) connected to my SOC (system on chip) board. Basic idea is
> to test data transfer across
On Mon, 19 Feb 2007, Mukesh Kohli wrote:
> Hello Guys,
>
> I am trying to create a duplicate copy of a file onto a USB 2.0 device
> (memory stick) connected to my SOC (system on chip) board. Basic idea is
> to test data transfer across USB host controller and USB Device. It is
> failing randomly
Dylan Taft wrote:
> Gmail for some reason isn't letting me paste this patch without word
> wrapping, even if it's not wrapped in my editor.
> Does it show up right for anyone else? Sigh.
Are you attempting to submit this as a patch? If so, I can clean it up when
I pull it into my tree. Though, I
On Thu, Jan 04, 2007 at 04:01:19PM -0800, Pete Zaitcev wrote:
> But it seems that I found a case when this does not work. It happens
> with Sun's virtual floppy, which returns a seemingly normal INQUIRY
> data (this is CBI, LUN set to 1, and device simply ignores it, most
> likely):
>
> 81003f
Alan:
Alan Stern wrote:
>USB error codes are explained in the source file
>Documentation/usb/error-codes.txt. 84 is EILSEQ, which indicates an
>invalid bit stream was received from the device (bad CRC, invalid
>bit-stuffing, etc.). It could be a cable-level hardware problem.
>
>
Ok, thanks
On Tue, 28 Nov 2006, Bill Gatliff wrote:
> Guys:
>
>
> I'm trying to get USB pen drives working on a 2.4.26/PPC-based embedded
> system. Unfortunately, at the moment a kernel upgrade to something less
> ancient isn't an option. :(
>
> I can't rule out a hardware problem, but the drive I'm t
[cut]
> Alexandre,
>
> I'll get a patch out for this this week. It'll take me a few days
> since most of my time right now is helping my girlfriend who just had
> knee surgery... but I thought I'd acknowledge your email in the meantime.
>
Take your time man, i wish a good recovery to her; Thank
Alexandre Pereira Nunes wrote:
Hi,
I have a UCR-61S2B with rev 1.0, here is relevant /proc/bus/usb/devices
data:
> I traced it down to this change (excerpt from patch-2.6.18):
Alexandre,
I'll get a patch out for this this week. It'll take me a few days since most
of my time right now i
Alan Stern wrote:
>> I have an usb HP cd-writer plus 8200. It is not working properly with
>> usb-storage (linux 2.6.17.1 righ now, but does'nt work with eny 2.6 kernel,
>> udev 0.97), and is identified by the system as a hard disk (sda) insted of a
>> removable cd device (sr0).
This is fixed
On Thu, 7 Sep 2006, Luigi Genoni wrote:
> Hi,
>
> I have an usb HP cd-writer plus 8200. It is not working properly with
> usb-storage (linux 2.6.17.1 righ now, but does'nt work with eny 2.6 kernel,
> udev 0.97), and is identified by the system as a hard disk (sda) insted of a
> removable cd d
On Friday 18 August 2006 7:38 am, Alan Stern wrote:
> On Fri, 18 Aug 2006, Manish RATHI wrote:
>
> > I am facing problem with mentor usb host mode.
>
> Please be more specific. What is a mentor?
One can pray it's not the HDRC code referenced at
http://www.mentor.com/products/ip/usb/usb20otg/
On Fri, 18 Aug 2006, Manish RATHI wrote:
> Hi,
> I am facing problem with mentor usb host mode.
Please be more specific. What is a mentor?
> I am doing mass storage emulation using pen driver with bulk only transport
> protocol.
What is a pen driver? Do you know what software it uses to provi
[mailto:[EMAIL PROTECTED]
Sent: Monday, August 14, 2006 8:06 PM
To: Manish RATHI
Cc: [email protected]
Subject: Re: [linux-usb-devel] Usb storage mount problem
On Mon, 14 Aug 2006, Manish RATHI wrote:
> Hi,
> I am using my usb controller driver in host mode for mass to
On Thu, Aug 17, 2006 at 01:55:03PM -0700, Matthew Dharm wrote:
> On Thu, Aug 17, 2006 at 03:57:52PM -0400, Alan Stern wrote:
> > P.S.: There's one good thing about the phone: It always sets a correct
> > value for the Residue! Lots of devices don't.
>
> It also appears to be framing the commands
On Thu, Aug 17, 2006 at 03:57:52PM -0400, Alan Stern wrote:
> P.S.: There's one good thing about the phone: It always sets a correct
> value for the Residue! Lots of devices don't.
It also appears to be framing the commands and responses properly, which is
good. That is, status messages come whe
On Thu, Aug 17, 2006 at 03:57:52PM -0400, Alan Stern wrote:
> On Thu, 17 Aug 2006, Greg KH wrote:
>
> > > Did you notice that the number of sectors being reported looks very close
> > > to MAXLONG? And I'm pretty sure your phone does not have 2.2TB of
> > > storage.
> >
> > Yeah, I wish. And i
On Thu, 17 Aug 2006, Greg KH wrote:
> > Did you notice that the number of sectors being reported looks very close
> > to MAXLONG? And I'm pretty sure your phone does not have 2.2TB of storage.
>
> Yeah, I wish. And it's not my phone, unless I can figure out how to
> distract the owner enough to
On Thu, 17 Aug 2006 11:24:51 -0700, Greg KH <[EMAIL PROTECTED]> wrote:
> [ 125.718000] SCSI device sda: 4294967294 512-byte hdwr sectors (2199023 MB)
>[]
> [ 125.922000] end_request: I/O error, dev sda, sector 4294967040
> [ 125.922000] Buffer I/O error on device sda, logical block 21474835
On Thu, Aug 17, 2006 at 11:34:20AM -0700, Matthew Dharm wrote:
> On Thu, Aug 17, 2006 at 11:24:51AM -0700, Greg KH wrote:
> > I've got access to a new phone for a few hours here, and it doesn't seem
> > to want to play nice with the usb-storage driver (imagine that...)
> >
> > Here's the dmesg of
On Thu, Aug 17, 2006 at 11:34:20AM -0700, Matthew Dharm wrote:
> On Thu, Aug 17, 2006 at 11:24:51AM -0700, Greg KH wrote:
> > I've got access to a new phone for a few hours here, and it doesn't seem
> > to want to play nice with the usb-storage driver (imagine that...)
> >
> > Here's the dmesg of
On Thu, Aug 17, 2006 at 11:24:51AM -0700, Greg KH wrote:
> I've got access to a new phone for a few hours here, and it doesn't seem
> to want to play nice with the usb-storage driver (imagine that...)
>
> Here's the dmesg of the device without debugging turned on, I'll enable
> it and send that lo
On Thu, Aug 17, 2006 at 11:24:51AM -0700, Greg KH wrote:
> I've got access to a new phone for a few hours here, and it doesn't seem
> to want to play nice with the usb-storage driver (imagine that...)
>
> Here's the dmesg of the device without debugging turned on, I'll enable
> it and send that lo
On Thu, 17 Aug 2006, Manish RATHI wrote:
> Hi,
> Following entries are there for /dev/sdc and /dev/sdb
>
> crw-r--r--1 root root 5, 1 May 9 15:48 console
> crw-r--r--1 root root 29, 0 May 11 13:48 fb0
> crw-r--r--1 root root 89, 0 May 11 13:51 i2c-
rom: Alan Stern [mailto:[EMAIL PROTECTED]
Sent: Monday, August 14, 2006 8:06 PM
To: Manish RATHI
Cc: [email protected]
Subject: Re: [linux-usb-devel] Usb storage mount problem
On Mon, 14 Aug 2006, Manish RATHI wrote:
> Hi,
> I am using my usb controller driver in host
On Mon, 14 Aug 2006, Manish RATHI wrote:
> Hi,
> I am using my usb controller driver in host mode for mass torage emulation.
> Mass torage device is detected and I got following prints
> SCSI device sdb: 1024 512-byte hdwr sectors (1 MB)
>
>
> sdb: Write Protect is off
>
> sdb: assuming drive
> Hi,
> I am using my usb controller driver in host mode for mass torage
> emulation.
> Mass torage device is detected and I got following prints
>
>
> / # INQUIRY message sent
>
> Vendor: Generic Model: Flash D Rev:
>
> Type: Direct-Access ANSI SCSI revision:
Daniel Drake wrote:
> This patch adds a new unusual_devs flag for when usb-storage needs to ignore
> a device that it would otherwise claim.
>
> We need to ignore the ZyXEL G220F as it is a virtual CDROM drive which
> includes the windows driver for this USB-WLAN adapter. After the windows
> drive
Looks fine to me. The difference between this patch and the last one is a
"6 of one, half-dozen of the other" to me, but I see the benefits of this
approach.
Signed-off-by: Matthew Dharm <[EMAIL PROTECTED]>
Matt
On Mon, Jul 24, 2006 at 10:46:17PM +0100, Daniel Drake wrote:
> Alan Stern wrote:
>
Alan Stern wrote:
In general the idea looks okay to me, but I would change the details in
storage/usb.c. Check for US_FL_IGNORE_DEVICE in the get_device_info()
routine, and make that routine return int instead of void. If the flag is
present you can simply return -ENODEV. Then in storage_pr
On Sun, 23 Jul 2006, Daniel Drake wrote:
> Matthew Dharm wrote:
> > I think that is a better approach than your patch. Perhaps the zd1211rw
> > driver could know the VID/PID of the fake CD-ROM to attach to it and send
> > the fake eject command. The usb-storage (and probably ub) would just have
Matthew Dharm wrote:
I think that is a better approach than your patch. Perhaps the zd1211rw
driver could know the VID/PID of the fake CD-ROM to attach to it and send
the fake eject command. The usb-storage (and probably ub) would just have
to ignore the device.
Ok, I've handled the zd1211rw
On Tue, 18 Jul 2006, Matthew Dharm wrote:
> On Tue, Jul 18, 2006 at 05:01:32PM +0100, Daniel Drake wrote:
> > Alan Stern wrote:
> > >Wouldn't it be easy enough to write a user program to send the necessary
> > >command URB via usbfs?
>
> That seems more reasonable.
>
> > That aside, it's not som
On Tue, Jul 18, 2006 at 12:25:37PM -0700, Pete Zaitcev wrote:
> On Tue, 18 Jul 2006 17:01:32 +0100, Daniel Drake <[EMAIL PROTECTED]> wrote:
>
> > When you plug the device in, usb-storage picks it up, but during the 5
> > second delay_use pause, the device gets bored and disconnects itself. It
>
On Tue, 18 Jul 2006 17:01:32 +0100, Daniel Drake <[EMAIL PROTECTED]> wrote:
> When you plug the device in, usb-storage picks it up, but during the 5
> second delay_use pause, the device gets bored and disconnects itself. It
> then reconnects and the process repeats.
Bias it to ub :-)
-- Pete
On Tue, Jul 18, 2006 at 05:01:32PM +0100, Daniel Drake wrote:
> Alan Stern wrote:
> >Wouldn't it be easy enough to write a user program to send the necessary
> >command URB via usbfs?
That seems more reasonable.
> That aside, it's not something that really makes sense to do in
> userspace - the
Alan Stern wrote:
> Wouldn't it be easy enough to write a user program to send the necessary
> command URB via usbfs?
Well, not really. This device does a bad job at emulating a CDROM and I
haven't yet found a way to keep it attached to the system in stable fashion.
When you plug the device in,
On Tue, 18 Jul 2006, Daniel Drake wrote:
> How's that for a confusing subject line?
>
> ZyDAS offer a special flavour of their ZD1211 USB 802.11 network adapters,
> where the device appears as a USB mass storage CDROM drive when you plug it
> in. The fake CDROM includes the windows driver, which
On Sat, Jun 24, 2006 at 05:27:10PM -0700, Phil Dibowitz wrote:
> This patch adds a US_FL_MAX_SECTORS_64 and removes the Genesys special-cases
> for this that were in scsiglue.c. It also adds the flag to other devices
> reported to need it.
>
> Signed-off-by: Phil Dibowitz <[EMAIL PROTECTED]>
This
On Sat, Jun 24, 2006 at 05:27:54PM -0700, Phil Dibowitz wrote:
> This patch adds the kernel version to the usb-storage Protocol/SubClass
> unneeded message in order to help us troubleshoot such problems.
>
> Signed-off-by: Phil Dibowitz <[EMAIL PROTECTED]>
This looks good. Greg, please apply.
M
Joerg Thoennes wrote:
> Jun 1 10:25:21 hostname kernel: usb 2-4: new high speed USB device
> using address 2
> Jun 1 10:25:22 hostname kernel: Initializing USB Mass Storage driver...
> Jun 1 10:25:22 hostname kernel: usb-storage: This device
> (05ab,0060,1106 S 06 P 50) has unneeded SubClass and
It's difficult to tell without timestamps, but this looks like a SCSI
revalidation bug.
That is, the device reports very late that it is just initializing. The
SCSI layer sees this as a media-change, but then doesn't revalidate
properly.
Since the first access is from vfat trying to determine if
On Fri, 28 Apr 2006, Patrick Agrain wrote:
> Hi all,
>
> I have a mount problem which occurs only on the first try after a replug of
> any available USB2.0 Memory Key.
> The EHCI controller and USB storage drivers are from 2.4.32 kernel (Yes, I
> know ;-)
Then you also know that you're not goi
On Tue, 18 Apr 2006, Patrick Agrain wrote:
> Hi Alan,
>
>
>
> >This isn't a simple mapping. A single USB device may correspond to 0, 1,
> >or more entries in /dev. Also, it's not clear why you want to know the
> >major and minor numbers rather than the filename of the /dev entry.
>
> In that
Much appreciated Alan.
Thanks,
Garyc
--- Alan Stern <[EMAIL PROTECTED]> wrote:
> On Tue, 18 Apr 2006, gary clark wrote:
>
> > Hello,
> >
> > Is there a system call maybe an ioctl that can be
> > performed within usb storage driver to obtain the
> > major and minor numbers corresponding to thos
Hi Alan,
This isn't a simple mapping. A single USB device may correspond to 0, 1,
or more entries in /dev. Also, it's not clear why you want to know the
major and minor numbers rather than the filename of the /dev entry.
In that case, what would be the best way to know the device node on w
On Tue, 18 Apr 2006, gary clark wrote:
> Hello,
>
> Is there a system call maybe an ioctl that can be
> performed within usb storage driver to obtain the
> major and minor numbers corresponding to those found
> in /dev on a USB device.
No.
> I perform an open system call using usbfs i.e
> /proc
On Fri, 20 Jan 2006, Bahadir Balban wrote:
> Hi,
>
> % dd if=/dev/sda count=1 | hexdump
>
> gives all zeroes. If I increase count, occasionally some data shows up
> which isn't meaningful ascii, but mostly zero.
If you really do get all zeros then the partition sector is empty. Hence
there ar
> On 1/20/06, Alan Stern <[EMAIL PROTECTED]> wrote:
>> What do you get from "dd if=/dev/sda count=1 | hexdump -C"?
>>
>> Alan Stern
>>
>
> Hi,
>
> % dd if=/dev/sda count=1 | hexdump
>
> gives all zeroes. If I increase count, occasionally some data shows up
> which isn't meaningful ascii, but mostly
On 1/20/06, Alan Stern <[EMAIL PROTECTED]> wrote:
> What do you get from "dd if=/dev/sda count=1 | hexdump -C"?
>
> Alan Stern
>
Hi,
% dd if=/dev/sda count=1 | hexdump
gives all zeroes. If I increase count, occasionally some data shows up
which isn't meaningful ascii, but mostly zero. The same f
On Fri, 20 Jan 2006, Bahadir Balban wrote:
> Hi,
>
> I am testing a new hc driver. My intention is to mount a usb flash
> disk. The problem is that the device is recognised properly by the
> message:
>
> usb 1-1.3: Product: DiskOnKey
> usb 1-1.3: Manufacturer: M-Sys
> usb 1-1.3: SerialNumber: 02
On Tue, 13 Dec 2005, Andrea Arcangeli wrote:
> I've an USB storage key that gives these errors on my x86_64 system:
> ohci_hcd :01:00.1: urb 810022377d40 path 2 ep2out 5fce cc 5 -->
> status -110
> hub 2-0:1.0: state 5 ports 3 chg evt 0004
> ohci_hcd :01:00.1: GetStatus root
On Tue, Dec 13, 2005 at 03:02:15PM -0800, Pete Zaitcev wrote:
> On Tue, 13 Dec 2005 23:34:37 +0100, Andrea Arcangeli <[EMAIL PROTECTED]>
> wrote:
>
> > ohci_hcd :01:00.1: urb 810022377d40 path 2 ep2out 5fce cc 5 -->
> > status -110
> > hub 2-0:1.0: state 5 ports 3 chg evt 0004
>
On Tue, 13 Dec 2005 23:34:37 +0100, Andrea Arcangeli <[EMAIL PROTECTED]> wrote:
> ohci_hcd :01:00.1: urb 810022377d40 path 2 ep2out 5fce cc 5 -->
> status -110
> hub 2-0:1.0: state 5 ports 3 chg evt 0004
> ohci_hcd :01:00.1: GetStatus roothub.portstatus [1] = 0x00100103 PRSC
> That flag already exists. SG_FLAG_LUN_INHIBIT -- see
> sg.torque.net for
> details.
>
> Matt
Thanks, I somehow missed that. It should solve my problem.
Tim
---
SF.Net email is sponsored by:
Tame your development challenges with Apache's
On Wed, Sep 14, 2005 at 01:18:52PM -0700, Timothy Thelin wrote:
>
> > It ought to be possible to add a flag that would prevent the
> > SCSI midlayer
> > from overlaying the LUN bits on top of cdb[1]. Then we could
> > still set
> > the revision number to 2 and you would be happy.
>
> Sounds
On Wed, Sep 14, 2005 at 12:19:39PM -0700, Timothy Thelin wrote:
>
> > > Why would a usb-storage device ever report itself as scsi0
> > if it actually
> > > supports scsi3? Is it because the USB/ATA bridge spec
> > doesn't support asking
> > > the device it self, so the usb-subsystem just makes
> It ought to be possible to add a flag that would prevent the
> SCSI midlayer
> from overlaying the LUN bits on top of cdb[1]. Then we could
> still set
> the revision number to 2 and you would be happy.
Sounds plausable, but i'm not an expert on the Linux scsi stack
to know where the flag
On Wed, 14 Sep 2005, Timothy Thelin wrote:
> > SCSI 3 triggers new and exciting behavior from SCSI core.
Note that usb-storage even sets the version number for SCSI-3 devices back
to 2. That's because a lot of them report SCSI-3 and then crash when
asked to carry out a REPORT LUNS command.
It
> > Why would a usb-storage device ever report itself as scsi0
> if it actually
> > supports scsi3? Is it because the USB/ATA bridge spec
> doesn't support asking
> > the device it self, so the usb-subsystem just makes an (un?
> ;)-educated
> > guess? Or is it because it is possible, but the
> On Wed, Sep 14, 2005 at 10:45:37AM -0700, Timothy Thelin wrote:
> >
> > I was curious about the reasoning behind this decision and
> how to fix an
> > issue that came up because of it.
>
> The reasoning goes something like this: There are lots of
> devices which
> report 0, but need the SCS
> On Wednesday 14 September 2005 19:45, Timothy Thelin wrote:
> > I was curious about the reasoning behind this decision and
> how to fix an
> > issue that came up because of it.
> > ...
> > (1) Is easy to do, but is it going to cause other issues?
> I'd imagine any
> > *usb storage* device tha
On Wed, Sep 14, 2005 at 08:29:19PM +0200, Christian Iversen wrote:
> On Wednesday 14 September 2005 19:45, Timothy Thelin wrote:
> > I was curious about the reasoning behind this decision and how to fix an
> > issue that came up because of it.
> > ...
> > (1) Is easy to do, but is it going to cause
On Wed, Sep 14, 2005 at 10:45:37AM -0700, Timothy Thelin wrote:
>
> I was curious about the reasoning behind this decision and how to fix an
> issue that came up because of it.
The reasoning goes something like this: There are lots of devices which
report 0, but need the SCSI-II 10-byte commands
On Wednesday 14 September 2005 19:45, Timothy Thelin wrote:
> I was curious about the reasoning behind this decision and how to fix an
> issue that came up because of it.
> ...
> (1) Is easy to do, but is it going to cause other issues? I'd imagine any
> *usb storage* device that reports scsi0 rea
On Fri, 29 Jul 2005, Vedran Rodic wrote:
> Thanks. I've tried with noacpi and noapic options on both kernels I've
> mentioned with much better results. There is no 10 IRQ count in
> /proc/interrupts, which now of course looks different because other code
> is taking care of the interrupt ar
Alan Stern wrote:
An interrupt count of 10 is what you get when some device is issuing
interrupt requests on that IRQ line and the kernel doesn't realize it.
Apparently one of your devices other than the EHCI controller is using IRQ
18. Sometimes upgrading the computer's BIOS will fix
On Thu, 28 Jul 2005, Vedran Rodic wrote:
> Hello
>
> I'm using the latest available kernel.org version 2.6.13-git9, on a
> nforce2 IGP chipset.
>
> There is a Flash card reader attached.
>
> As soon as I've booted the kernel, I got some kernel messages about USB
> errors.
>
> In kernel 2.6.1
On Monday 06 June 2005 1:37 pm, Alan Stern wrote:
> On Mon, 6 Jun 2005, David Brownell wrote:
> >
> > What I'm curious about is whether there's something that usbcore
> > is doing to the poor root hubs that make them disconnect devices.
>
> What could usbcore possibly do to make a hub disconnect
On Mon, 6 Jun 2005, David Brownell wrote:
> Thing is, other folk have been complaining recently about cases
> where devices seem to be spontaneously disconnecting from Linux.
> (Often storage devices, for that matter.) And I'm wondering if
> your setup can be used to turn up more information on t
On Mon, 6 Jun 2005, Jamie Guinan wrote:
> > That's odd. While I'm not familiar with the details of OHCI or the
> > LH7A404 driver, normally a host controller driver does not check the port
> > status when communicating with a device. Port status is checked
> > asynchronously by the hub driver
On Monday 06 June 2005 12:03 pm, Jamie Guinan wrote:
>
> 2) Does the 0x30101 look like a sane response? I'm seeing 0x30100
> when I remove an IOGEAR media reader connected through via a
> standard USB TypeA port.
What's a bit curious is that the connect status bit change
is set (CSC)
On Mon, 6 Jun 2005, Alan Stern wrote:
> On Mon, 6 Jun 2005, Jamie Guinan wrote:
>
> > Hi,
> >
> > I'm running linux 2.6.11 (vanilla) on a custom board, with a
> > Sharp LH7A404.
> >
> > .config:
> > CONFIG_ARCH_LH7A40X=y
> > CONFIG_ARCH_LH7A404=y
> >
> > I've been having problems with a US
On Mon, 6 Jun 2005, Jamie Guinan wrote:
> Hi,
>
> I'm running linux 2.6.11 (vanilla) on a custom board, with a
> Sharp LH7A404.
>
> .config:
> CONFIG_ARCH_LH7A40X=y
> CONFIG_ARCH_LH7A404=y
>
> I've been having problems with a USB storage chip connected to the
> USB host interface (ST72F65,
On Sat, 21 May 2005, mike lee wrote:
> Dear all
>I don't know whether i come to a right place to ask, if i am not
> please tell me.
>
>I am now using vfat for my usb-storage disk, but i found that whether
> a poweroff of my device, what i have done to the disk has gone. It is
> not the ca
On Wed, May 18, 2005 at 10:19:41AM -0400, David Zeuthen wrote:
>
> Hey,
>
> On Wed, 2005-04-27 at 21:34 -0700, Greg KH wrote:
> > > Greg, ok if I prepare a patch to look at or don't you like the split?
> >
> > Let's see what the patch looks like :)
>
> Did anything happen on this issue? Is ther
Hey,
On Wed, 2005-04-27 at 21:34 -0700, Greg KH wrote:
> > Greg, ok if I prepare a patch to look at or don't you like the split?
>
> Let's see what the patch looks like :)
>
Did anything happen on this issue? Is there a patch yet? :-)
Thanks,
Dave
-
On Fri, Apr 29, 2005 at 12:28:30PM -0700, David Brownell wrote:
> On Friday 29 April 2005 11:23 am, Roman Kagan wrote:
> >
> > ... instead of trying to make sure the attributes are available via
> > sysfs at hotplug time, we can use another means to pass them to hotplug:
> > we can add a routine,
On Fri, 2005-04-29 at 22:16 +0200, Oliver Neukum wrote:
> Am Freitag, 29. April 2005 22:01 schrieb Greg KH:
> > > > I'd rather just guarantee that the sysfs device were fully
> > > > constructed (attributes and all) before the driver binding and
> > > > hotplug stages of enumeration started. That'
On Friday 29 April 2005 12:35 pm, Oliver Neukum wrote:
> Am Freitag, 29. April 2005 21:28 schrieb David Brownell:
> > On Friday 29 April 2005 11:23 am, Roman Kagan wrote:
> > >
> > > ... add environment variable ...
> >
> > Color me amused. That was the original way to pass information
> > to ho
Am Freitag, 29. April 2005 22:01 schrieb Greg KH:
> > > I'd rather just guarantee that the sysfs device were fully
> > > constructed (attributes and all) before the driver binding and
> > > hotplug stages of enumeration started. That's been a problem
> > > all along, and that's what those recent c
On Fri, Apr 29, 2005 at 10:23:36PM +0400, Roman Kagan wrote:
> On Wed, Apr 27, 2005 at 04:14:08PM -0700, Patrick Mansfield wrote:
> > On Wed, Apr 27, 2005 at 05:21:10PM -0400, Alan Stern wrote:
> >
> > > David's right. Why did kobject_hotplug() move out of kobject_add() and
> > > into its callers
On Fri, Apr 29, 2005 at 09:35:52PM +0200, Oliver Neukum wrote:
> Am Freitag, 29. April 2005 21:28 schrieb David Brownell:
> > On Friday 29 April 2005 11:23 am, Roman Kagan wrote:
> > >
> > > ... instead of trying to make sure the attributes are available via
> > > sysfs at hotplug time, we can use
Am Freitag, 29. April 2005 21:28 schrieb David Brownell:
> On Friday 29 April 2005 11:23 am, Roman Kagan wrote:
> >
> > ... instead of trying to make sure the attributes are available via
> > sysfs at hotplug time, we can use another means to pass them to hotplug:
> > we can add a routine, which,
On Friday 29 April 2005 11:23 am, Roman Kagan wrote:
>
> ... instead of trying to make sure the attributes are available via
> sysfs at hotplug time, we can use another means to pass them to hotplug:
> we can add a routine, which, when called from the .hotplug function
> and given pointers to stru
On Wed, Apr 27, 2005 at 04:14:08PM -0700, Patrick Mansfield wrote:
> On Wed, Apr 27, 2005 at 05:21:10PM -0400, Alan Stern wrote:
>
> > David's right. Why did kobject_hotplug() move out of kobject_add() and
> > into its callers sometime after 2.6.11? In particular the invocation in
> > device_ad
On Thu, Apr 28, 2005 at 02:47:23AM +0200, Kay Sievers wrote:
> On Wed, Apr 27, 2005 at 04:14:08PM -0700, Patrick Mansfield wrote:
> > On Wed, Apr 27, 2005 at 05:21:10PM -0400, Alan Stern wrote:
> >
> > > David's right. Why did kobject_hotplug() move out of kobject_add() and
> > > into its callers
On Wed, Apr 27, 2005 at 04:14:08PM -0700, Patrick Mansfield wrote:
> On Wed, Apr 27, 2005 at 05:21:10PM -0400, Alan Stern wrote:
>
> > David's right. Why did kobject_hotplug() move out of kobject_add() and
> > into its callers sometime after 2.6.11? In particular the invocation in
> > device_ad
On Wed, Apr 27, 2005 at 05:21:10PM -0400, Alan Stern wrote:
> David's right. Why did kobject_hotplug() move out of kobject_add() and
> into its callers sometime after 2.6.11? In particular the invocation in
> device_add() is in the wrong place; it needs to come before
> bus_add_device() starts
1 - 100 of 369 matches
Mail list logo
