Re: [linux-usb-devel] [PATCH] Driver for Apple Cinema Display
On Saturday 27 May 2006 13:30, Michael Hanselmann wrote: Hello Andrew On Fri, May 26, 2006 at 01:16:30PM -0700, Andrew Morton wrote: + up(pdata-bd-sem); + retval = appledisplay_bl_get_brightness(pdata-bd); + if (retval = 0) + pdata-bd-props-brightness = retval; + down(pdata-bd-sem); Gee it's odd to go upping a semaphore on entry to a schedule_work() handler. What's going on here? As Benjamin wrote, I mixed up down() and up(). The patch below fixes this. All other comments were due to that. Also, HZ / 8 is not the right way to specify 125ms. It just happens to be right in the default desktop config where HZ == 1000. -- Regards, Christian Iversen --- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnkkid=107521bid=248729dat=121642 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] [PATCH] Driver for Apple Cinema Display
On Saturday 27 May 2006 13:36, Christian Iversen wrote: On Saturday 27 May 2006 13:30, Michael Hanselmann wrote: Hello Andrew On Fri, May 26, 2006 at 01:16:30PM -0700, Andrew Morton wrote: + up(pdata-bd-sem); + retval = appledisplay_bl_get_brightness(pdata-bd); + if (retval = 0) + pdata-bd-props-brightness = retval; + down(pdata-bd-sem); Gee it's odd to go upping a semaphore on entry to a schedule_work() handler. What's going on here? As Benjamin wrote, I mixed up down() and up(). The patch below fixes this. All other comments were due to that. Also, HZ / 8 is not the right way to specify 125ms. It just happens to be right in the default desktop config where HZ == 1000. On second thought, maybe I got that wrong. I don't know the schedule_delayed_work() function. Can anyone sort this out? -- Regards, Christian Iversen --- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnkkid=107521bid=248729dat=121642 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] Re: RFC - Let ub handle iPods
On Saturday 29 April 2006 17:48, Alan Stern wrote:
On Sat, 29 Apr 2006, Phil Dibowitz wrote:
Tangential question - you're making the decision for the user here, so
more so than Why does Pete want to drive his iPod with ub, why does
this make sense for everyone who uses Linux?
Phil, I think you have misunderstood the point of this patch. It doesn't
make any decisions for the user. Just the opposite.
The way libusual currently works is that every entry in unusual_devs.h is
automatically directed to usb-storage, not to ub. The patch adds a way to
specify that a particular entry should be directed according to the user's
preference, by coding such entries with the UNUSUAL_DEV2 macro instead of
UNUSUAL_DEV.
Even for such entries, the default is still to direct them to usb-storage.
(Unless the last field in UNUSUAL_DEV2 is set to USB_US_TYPE_UB, which the
patch does not do.) Only if the user explicitly requests it will libusual
switch over to using ub.
+#define UNUSUAL_DEV2(id_vendor, id_product, bcdDeviceMin,
bcdDeviceMax, \ + vendorName, productName, useProtocol,
useTransport, \
+ initFunction, flags, useType) \
+{ USB_DEVICE_VER(id_vendor, id_product, bcdDeviceMin,bcdDeviceMax), \
+ .driver_info = (flags)|((useType)24) }
UNUSUAL_DEV2?! Ew. How about UNUSUAL_DEV_UB?
I agree that UNUSUAL_DEV2 is not the best name. But UNUSUAL_DEV_UB is
even worse, because these entries are not automatically directed to ub.
I'm not sure what a better name might be. USUAL_DEV? That looks rather
peculiar.
UNUSUAL_DEV_AUTO? (Because it auto-selects the driver)
--
Regards,
Christian Iversen
---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] usb replug
On Wednesday 29 March 2006 15:20, Gimmy P wrote: Hi everybody :) I'm developing a remote camera control system with a java software on a minimalistic debian linux os. I'm using a usb camera driven with gphoto2. Sometimes it happens that the camera freezes, and a manual replug of the usb cable is necessary to make it work again. My question is: is there any way to do it remotely, therefore without acting manually on the cable? I'd appreciate any advice or web link. Thanks Maybe you unload / reload the ehci/uhci/ohci modules? -- Regards, Christian Iversen --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] Re: USB support on via motherboards
On Wednesday 15 February 2006 17:58, Alan Stern wrote:
This confirms that your hardware is physically broken; it's not a software
problem.
There are three UHCI controllers, one per file above, each with two ports.
The port statuses are given in the lines marked stat1 and stat2. It
looks like your USB drive is plugged into port 1 of the third controller,
:00:11.4, because that stat1 value is different from the others.
The 9 in the 0490 indicates that the D+ signal line has a high voltage,
which never happens unless something is plugged in. However the 0 at the
end indicates that the controller thinks no device is connected.
Therefore the controller is not working correctly.
That sounds like a trivial check that could save a lot of time debugging. How
about something like the following pseudo-code? :
if (data_plus_line_high(usb_dev) nothing_plugged_in(usb_dev)) {
printk(Fatal error: USB port on fire\n);
}
--
Regards,
Christian Iversen
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642
___
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] Thinko in hcd.c?
On Saturday 21 January 2006 00:43, Pete Zaitcev wrote: Looks like an inverted condition. Maybe it was meant to be a de-Morgan of uses new polling and has an URB for that. Not sure though... diff -upr -X dontdiff linux-2.6.16-rc1/drivers/usb/core/hcd.c linux-2.6.16-rc1-lem/drivers/usb/core/hcd.c --- linux-2.6.16-rc1/drivers/usb/core/hcd.c 2006-01-17 21:11:27.0 -0800 +++ linux-2.6.16-rc1-lem/drivers/usb/core/hcd.c 2006-01-20 14:47:16.0 -0800 @@ -524,7 +524,7 @@ void usb_hcd_poll_rh_status(struct usb_h unsigned long flags; charbuffer[4]; /* Any root hubs with 31 ports? */ - if (!hcd-uses_new_polling !hcd-status_urb) + if (!hcd-uses_new_polling || !hcd-status_urb) return; But in that case, wouldn't + if (hcd-uses_new_polling hcd-status_urb) be better / easier to read? or is there something I'm missing? -- Regards, Christian Iversen --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] Re: [2.6 patch] drivers/usb/misc/sisusbvga/sisusb.c: remove dead code
On Wednesday 23 November 2005 20:02, Greg KH wrote:
On Mon, Nov 21, 2005 at 12:22:39AM +0100, Adrian Bunk wrote:
The Coverity checker found this obviously dead code.
I think the checker is wrong, this does not look correct to me.
How can a value != 0, in the first line of a body of a
while (value) {...
?
I think the checker is correct, FWIW.
--
Regards,
Christian Iversen
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] USB stack hangs after sporadic disconnect
On Monday 14 November 2005 20:39, David Brownell wrote: On Monday 14 November 2005 9:35 am, Jan Kiszka wrote: ehci_hcd :00:10.3: GetStatus port 3 status 00180b POWER sig=j PEC CSC CONNECT Translation: the root hub spontaneously disconnected. There are such reports, which are as far as I can tell always with VIA hardware. I have no idea what causes them. Any chance this could be detected and ignored as bogus, as was done with the issue I helped locate in the ehci driver? (which was sort of similar, from my (limited) viewpoint :-) -- Regards, Christian Iversen --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] USB-kbd+mouse spontaneously disconnects
On Saturday 05 November 2005 17:47, Christian Iversen wrote: Does nobody have a single idea what's wrong here? I'm having an El Cheapo usb keyboard+mouse usb device, and an Logitech MX700 usb mouse connected to a computer. Bus 003 Device 001: ID : Bus 002 Device 001: ID : Bus 001 Device 005: ID 060b:5811 Solid Year ACK-571U Wireless Keyboard Bus 001 Device 003: ID 046d:c506 Logitech, Inc. MX-700 Cordless Mouse Receiver Bus 001 Device 001: ID : The MX700 has no problems, I'm just including it here for completeness. The keyboardmouse (km) is the problem. It sometimes disconnects for no good reason. If the km has disconnected, it can easily be reconnected by physically reconnecting the device, but that's wrong on so many levels.. :-) Now, I finally managed to get a debug-enabled dmesg output at the time something like this happened. I have to be completely honest when I say I can't remember if this is at the first or second disconnect. It seems to be the second one, though. Can somebody take a look at the atteched dmesg? It's with usb full-debug mode on, and goes all the way back to the start of the machine. It should be easy to read, and complete. I can't really figure out what's going on, so I hope someone here can :-) -- Regards, Christian Iversen --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] USB-kbd+mouse spontaneously disconnects
I'm having an El Cheapo usb keyboard+mouse usb device, and an Logitech MX700 usb mouse connected to a computer. Bus 003 Device 001: ID : Bus 002 Device 001: ID : Bus 001 Device 005: ID 060b:5811 Solid Year ACK-571U Wireless Keyboard Bus 001 Device 003: ID 046d:c506 Logitech, Inc. MX-700 Cordless Mouse Receiver Bus 001 Device 001: ID : The MX700 has no problems, I'm just including it here for completeness. The keyboardmouse (km) is the problem. It sometimes disconnects for no good reason. If the km has disconnected, it can easily be reconnected by physically reconnecting the device, but that's wrong on so many levels.. :-) Now, I finally managed to get a debug-enabled dmesg output at the time something like this happened. I have to be completely honest when I say I can't remember if this is at the first or second disconnect. It seems to be the second one, though. Can somebody take a look at the atteched dmesg? It's with usb full-debug mode on, and goes all the way back to the start of the machine. It should be easy to read, and complete. I can't really figure out what's going on, so I hope someone here can :-) -- Regards, Christian Iversen Linux version 2.6.13-venus ([EMAIL PROTECTED]) (gcc version 3.3.5 (Debian 1:3.3.5-13)) #1 SMP Thu Oct 20 12:09:56 CEST 2005 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - 1ffec000 (usable) BIOS-e820: 1ffec000 - 1ffef000 (ACPI data) BIOS-e820: 1ffef000 - 1000 (reserved) BIOS-e820: 1000 - 2000 (ACPI NVS) BIOS-e820: - 0001 (reserved) 511MB LOWMEM available. On node 0 totalpages: 131052 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 126956 pages, LIFO batch:31 HighMem zone: 0 pages, LIFO batch:1 DMI 2.3 present. ACPI: RSDP (v000 ASUS ) @ 0x000f6e20 ACPI: RSDT (v001 ASUS A7V266-E 0x30303031 MSFT 0x31313031) @ 0x1ffec000 ACPI: FADT (v001 ASUS A7V266-E 0x30303031 MSFT 0x31313031) @ 0x1ffec080 ACPI: BOOT (v001 ASUS A7V266-E 0x30303031 MSFT 0x31313031) @ 0x1ffec040 ACPI: DSDT (v001 ASUS A7V266-E 0x1000 MSFT 0x010b) @ 0x ACPI: PM-Timer IO Port: 0xe408 Allocating PCI resources starting at 2000 (gap: 2000:dfff) Built 1 zonelists Kernel command line: root=/dev/hda1 Local APIC disabled by BIOS -- you can enable it with lapic mapped APIC to d000 (01413000) Initializing CPU#0 PID hash table entries: 2048 (order: 11, 32768 bytes) Detected 1343.234 MHz processor. Using pmtmr for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 513056k/524208k available (3699k kernel code, 10688k reserved, 1440k data, 276k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 2688.08 BogoMIPS (lpj=1344040) Mount-cache hash table entries: 512 CPU: After generic identify, caps: 0383f9ff c1cbf9ff CPU: After vendor identify, caps: 0383f9ff c1cbf9ff CPU: CLK_CTL MSR was 6003d22f. Reprogramming to 2003d22f CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 256K (64 bytes/line) CPU: After all inits, caps: 0383f9ff c1cbf9ff 0020 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. mtrr: v2.0 (20020519) Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. ACPI: setting ELCR to 0200 (from 0c20) CPU0: AMD Athlon(TM) XP1500+ stepping 01 SMP motherboard not detected. Local APIC not detected. Using dummy APIC emulation. Brought up 1 CPUs NET: Registered protocol family 16 ACPI: bus type pci registered PCI: PCI BIOS revision 2.10 entry at 0xf0ed0, last bus=1 PCI: Using configuration type 1 ACPI: Subsystem revision 20050408 ACPI: Interpreter enabled ACPI: Using PIC for interrupt routing ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 9 10 11 12 14 15) ACPI: PCI Root Bridge [PCI0] (:00) PCI: Probing PCI hardware (bus 00) ACPI: Assume root bridge [\_SB_.PCI0] segment is 0 ACPI: Assume root bridge [\_SB_.PCI0] bus is 0 Boot video device is :01:00.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT] Linux Plug and Play Support v0.97 (c) Adam
[linux-usb-devel] Problems with external soundcard (almost working)
Hello all. I'm having a bit of trouble using the SoundBlaster Live USB soundcard with Linux 2.6.13. I can play back sound, no problem. I can even record without a hitch. But when I try skype, I get ... ehci_hcd :00:10.3: iso sched full d24fd5e0 (now 572 max 2620) ALSA sound/usb/usbaudio.c:767: cannot submit datapipe for urb 0, err = -28 ehci_hcd :00:10.3: iso sched full d24fd5e0 (now 572 max 2620) ALSA sound/usb/usbaudio.c:767: cannot submit datapipe for urb 0, err = -28 ehci_hcd :00:10.3: iso sched full d24fd5e0 (now 572 max 2620) ALSA sound/usb/usbaudio.c:767: cannot submit datapipe for urb 0, err = -28 ehci_hcd :00:10.3: iso sched full d24fd5e0 (now 572 max 2620) ALSA sound/usb/usbaudio.c:767: cannot submit datapipe for urb 0, err = -28 ehci_hcd :00:10.3: iso sched full d24fd360 (now 744 max 2792) ALSA sound/usb/usbaudio.c:767: cannot submit datapipe for urb 0, err = -28 ... and so on. Now, I've searched a bit, and -28 i supposed to be ENOSPC, which had (in one explanation) something to do with bandwidth handling. That doesn't seem to be the case here. This could of course be something completely related to skype, but other programs don't seem to trigger that error. Any ideas? -- Regards, Christian Iversen --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] Usb storage devices auto-promoted to scsi2 spec issue
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 really implements the scsi3 form of the commands that it happens to support. (2) Is more invasive, but is probably more of a correct solution. This will require a larger effort involving multiple groups coordinating the efforts. I can't really comment on the rest of your mail, even though the points seem well thought-out, but I would like to offer just a single comment: 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 devices can't be trusted to tell the truth? -- Regards, Christian Iversen --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] [PATCH] USB: Spelling fixes for drivers/usb.
On Monday 09 May 2005 22:13, Glenn Maynard wrote: On Sun, May 08, 2005 at 10:25:24PM -0500, Dmitry Torokhov wrote: AFAIK cancelled is British English while canceled is American. FWIW (not much), I'm American, and canceled looks very wrong to me. FWIW (even less), I'm Danish, and canceled looks very wrong to me too. -- Regards, Christian Iversen pgpEvRqsB7D9z.pgp Description: PGP signature
Re: [linux-usb-devel] no more applied, thanks emails from me.
On Wednesday 04 May 2005 18:50, Greg KH wrote: On Wed, May 04, 2005 at 11:16:54AM -0500, Dmitry Torokhov wrote: On 5/4/05, Alan Stern [EMAIL PROTECTED] wrote: On Tue, 3 May 2005, Greg KH wrote: Just a short note to know that I'll probably not be sending any kind of ACK message out to the mailing list anymore when I apply patches to my tree. Instead, the patch submitter will get a message when it gets applied, that contains a bunch of info about what patch it was, and others that they have pending in my tree. I'm doing this as I had been generating those applied, thanks emails by hand, and have been getting tired of them, and I know that some people were getting annoyed by this type of message (so much so that they generated procmail filters to keep from having to see them.) Shucks, I liked those applied, thanks messages. Terse and to-the-point. Especially true if there was a discussion WRT the patch(es). Sometimes it is nice to know if series have finally made it in even if you are not the author. If you are cc: on the patch, you should be getting an announcement about it. And if you have any questions if a patch went in or not, please feel free to ask. I'm just a end-user/non-usb programmer, and I like those messages too :) It's much easier to follow if a patch has been accepted or not. YMMV. -- Regards, Christian Iversen pgpML2VUvj9hf.pgp Description: PGP signature
Re: [linux-usb-devel] ehci hcd driver trouble. known issue or just odd hardware?
On Wednesday 05 January 2005 12:58, Pedro Venda wrote: David Brownell wrote: | On Tuesday 04 January 2005 4:31 am, Pedro Venda wrote: |David Brownell wrote: || On Monday 03 January 2005 5:05 pm, you wrote: ||David Brownell wrote: ||| It's something wierd that started a while back, and so far ||| it doesn't make sense to me. But see below, and please ||| try the patch I've attached. If it fails, please send ||| the full CONFIG_USB_DEBUG output showing the error (as ||| below) and contents of /sys/class/usb_host/usb4/registers ||| after the fault. || ||I've tried the patch and it failed. | | OK, try this slightly modified version. Looks like | the Intel chip sets the HALT bit then spontaneously | clears it, while the ALI may never set it. this one has a different output, although I don't understand if it's working properly since there are still some fatal errors... there isn't a fatal error but a BOGUS error, as introduced by the patch. [...output...] EHCI 1.00, hcd state 1 instead of the old value 0 means that the driver's working now? Have you tried it? I use a powered hub (with an LED) to tell if ehci is on. If you have a removeable hard drive or dvd-drive, you should notice a huge difference in throughput. care to comment? is this a good enough patch for the whole usb community or does it simply cover this isolated bogus error and by itself is unsafe for other environments? Allow me to comment on this. I'm the guy who found out that the controller reports a bogus fatal error, and I made the first patch that fixed it. When David Brownell saw my hack (which was to comment out a function call that resets the chip in the error handling), he came up with the patch you just tried, which is a more right way to handle it. I've been running with this patch for some time now (well, at least 10 days), and I haven't had any problems of any kind. USB just seems to work for me now. Of course, that could be pure luck, but since David and I looked at which changes have been going on in the ehci-driver, and the usb-core in general at the revisions where it originally broke, we discovered that it _no_ direct changes were made in the ehci-driver in the breaking revision. That suggests to me that the chip doesn't entirely work within specs, that the driver is good, and that we need this patch to catch a corner case that is wrongly handled by the hardware. That could be wrong, of course, but that's my view of the situation :) (it's kind of perplexing that different controllers seem to have somewhat of the same problem, but I think time will finally tell what's going on here) -- Regards, Christian Iversen --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] ehci hcd driver trouble. known issue or just odd hardware?
On Wednesday 05 January 2005 18:12, David Brownell wrote: On Wednesday 05 January 2005 3:58 am, Pedro Venda wrote: David Brownell wrote: | OK, try this slightly modified version. Looks like | the Intel chip sets the HALT bit then spontaneously | clears it, while the ALI may never set it. this one has a different output, although I don't understand if it's working properly since there are still some fatal errors... there isn't a fatal error but a BOGUS error, as introduced by the patch. That patch _reports_ that the hardware's error report (IRQ) is BOGUS. The original issue was that the driver wasn't noticing that the chip was misbehaving, and treated it like a real problem instead of an ignorable chip misbehavior. EHCI 1.00, hcd state 1 instead of the old value 0 means that the driver's working now? More like the _hardware_ is working, now that the driver knows enough to ignore that error IRQ in certain cases. The patch I submit won't actually print anything when it gets that BOGUS path ... there's nothing to be done with that IRQ except ignore it, and no point in potentially worrying end users or sysadmins. Maybe you should keep it in when Defined(DEBUG)? -- Regards, Christian Iversen --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] Can't rmmod usbcore with very latest kernel (solved!)
I have just found out that the problem turned out to be that usbfs WAS mounted. This is what happened: 1) I tried booting as normal. At this stage usbfs got mounted, which I didn't notice. 2) I renamed /lib/modules/.../drivers/usb/ to usb-2, and rebooted. Since usbcore was not found, usbfs was not mounted. I really thought that usbcore couldn't be removed after ehci-hcd was inserter, but I cannot reproduce this. I'm really very sorry I wasted your time :-/ -- Regards, Christian Iversen --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Can't rmmod usbcore with very latest kernel
I can't rmmod usbcore with latest (2.6.10-rc3-bk14). rmmod / modprobe -r usbcore gives FATAL: Module usbcore is in use.. rmmod -f usbcore gives the odd ERROR: Removing 'usbcore': Resource temporarily unavailable What's up here? Is the kernel trying to prevent me from shooting myself in the foot? If so, can I let it know that it's MY foot, and I want to take responsibility? :) There's nothing to see in dmesg, even with verbose logging. I sent David Brownell my dmesg on a (presumably?) unrelated matter, so he might be able to make heads and tails of this. -- Regards, Christian Iversen --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] Can't rmmod usbcore with very latest kernel
On Wednesday 22 December 2004 01:11, David Brownell wrote: On Tuesday 21 December 2004 11:12 am, Christian Iversen wrote: I can't rmmod usbcore with latest (2.6.10-rc3-bk14). rmmod / modprobe -r usbcore gives FATAL: Module usbcore is in use.. rmmod -f usbcore gives the odd ERROR: Removing 'usbcore': Resource temporarily unavailable What's up here? Hmm, if this is after you get that fatal error out of EHCI during init (which I've not had time to do much with; and it doesn't happen on any of my hardware) I suspect it's just that usbcore isn't cleaning up properly there. All the HCDs, and other USB drivers, need to be first idled, then removed; but the hub driver, at least, doesn't get cleaned up. You're right, I just noticed the correlation between these two events. Is this a problem with ehci-hcd, or usbcore? (who should I nag about this? :) -- Regards, Christian Iversen --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] Can't rmmod usbcore with very latest kernel
On Wednesday 22 December 2004 02:18, you wrote: On Tue, Dec 21, 2004 at 08:12:16PM +0100, Christian Iversen wrote: I can't rmmod usbcore with latest (2.6.10-rc3-bk14). rmmod / modprobe -r usbcore gives FATAL: Module usbcore is in use.. rmmod -f usbcore gives the odd ERROR: Removing 'usbcore': Resource temporarily unavailable Are you sure usbfs isn't mounted anywhere? If so, you will not be able to unload usbcore. Yes, it's a problem with ehci-hcd when it dies with fatal error on my (presumably) buggy hardware. David Brownell is looking into it now. -- Regards, Christian Iversen --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] usb-storage crashes on 2.6.10-rc2 (SMP) in a NEW and INTERESTING way
On Thursday 18 November 2004 16:45, David Brownell wrote: On Wednesday 17 November 2004 16:04, Christian Iversen wrote: However, the world is not trouble-free yet, as linux still crashes in certain situations on 2.6.10-rc2 with SMP systems. (UP systems are fine). The new bug is http://bugme.osdl.org/show_bug.cgi?id=3761, which I marked as blocking because it's just too easy to bring the whole system down. ... usb 4-2: USB disconnect, address 2 usb 4-2.3: USB disconnect, address 5 target5:0:0: Illegal state transition NULL-cancel Badness in scsi_device_set_state at drivers/scsi/scsi_lib.c:1717 [b0324d16] scsi_device_set_state+0xc6/0x130 ... This one's a SCSI bug, not a USB one, according to previous diagnosis. Oops, my bad. Although, it can't be entirely a SCSI bug, can it? The USB subsystem loses the high-speed connection and drops back to 1.1 speed. Or is that perhaps because the SCSI subsystem coughed and died? ..and if it's a SCSI bug, how can I A) Move it to the SCSI-section on bugme.osdl.org? B) Tell the right people? -- Regards, Christian Iversen --- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] usb-storage crashes on 2.6.10-rc2 (SMP) in a NEW and INTERESTING way
On Thursday 18 November 2004 20:29, Pete Zaitcev wrote:
On Thu, 18 Nov 2004 01:04:48 +0100, Christian Iversen
[EMAIL PROTECTED] wrote:
http://bugme.osdl.org/show_bug.cgi?id=3728, which has now been fixed.
However, the world is not trouble-free yet, as linux still crashes in
certain situations on 2.6.10-rc2 with SMP systems. (UP systems are fine).
Ah, 2.6.10-rc2. Thanks for posting the precise version. I am so tired of
people who write latest or current.
No problem at all, everybody should do this.. ;-)
Please try this patch by Mike Christie:
--- scsi-target-2.6/drivers/scsi/hosts.c 2004-10-09 07:56:54.363746835
-0700 +++ scsi-target-2.6.work/drivers/scsi/hosts.c 2004-10-09
07:49:21.287638490 -0700 @@ -55,6 +55,12 @@
return scsi_device_cancel(to_scsi_device(dev), *(int *)data);
}
+static int scsi_target_cancel_cb(struct device *dev, void *data)
+{
+ device_for_each_child(dev, data, scsi_device_cancel_cb);
+ return 0;
+}
+
/**
* scsi_host_cancel - cancel outstanding IO to this host
* @shost: pointer to struct Scsi_Host
@@ -64,7 +70,7 @@
{
set_bit(SHOST_CANCEL, shost-shost_state);
device_for_each_child(shost-shost_gendev, recovery,
- scsi_device_cancel_cb);
+ scsi_target_cancel_cb);
wait_event(shost-host_wait, (!test_bit(SHOST_RECOVERY,
shost-shost_state)));
}
For some reason, I had to apply it by hand. Poor patch(1) got confused.
Problem with tab chars?
Anyhow, it works _perfectly_. Thank you so very much :-)
*party time*
If you read the bug-description, you will see some mention of low USB speeds.
This is an unrelated issue, which I'll post to the mailing list shortly.
--
Regards,
Christian Iversen
---
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Problem with (at least) ALI USB 2.0 controller on 2.6.10-rc2
No kernel newer than 2.6.5 seems to work for my SMP box these days.. :-/
On Linux 2.6.10-rc2, my ALI USB controller no longer works properly.
Specifically, ehci connection are slow (not usb2.0 high-speed). It seems that
the kernel thinks that my controller has experienced a fatal error. The
following fix to line 858 of ehci-hcd.c gets past that:
change
if (unlikely ((status STS_FATAL) != 0)) {
to
if (0) {
Then, it more or less works, but you get tons of I/O errors when reading:
end_request: I/O error, dev sr0, sector 2712
Buffer I/O error on device sr0, logical block 339
end_request: I/O error, dev sr0, sector 2712
Buffer I/O error on device sr0, logical block 339
end_request: I/O error, dev sr0, sector 2712
Buffer I/O error on device sr0, logical block 339
end_request: I/O error, dev sr0, sector 2712
Buffer I/O error on device sr0, logical block 339
end_request: I/O error, dev sr0, sector 2712
Buffer I/O error on device sr0, logical block 339
end_request: I/O error, dev sr0, sector 2720
Buffer I/O error on device sr0, logical block 340
end_request: I/O error, dev sr0, sector 2720
On reconnecting devices I get strange warnings, like so:
usb 1-4: USB disconnect, address 2
usb 1-4.3: USB disconnect, address 6
usb 1-4.4: USB disconnect, address 5
usb 1-4: new high speed USB device using ehci_hcd and address 7
hub 1-4:1.0: USB hub found
hub 1-4:1.0: 4 ports detected
usb 1-4.3: new full speed USB device using ehci_hcd and address 8
usb 1-4.3: not running at top speed; connect to a high speed hub
scsi7 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 8
usb-storage: waiting for device to settle before scanning
usb 1-4.4: new full speed USB device using ehci_hcd and address 9
usb 1-4.4: not running at top speed; connect to a high speed hub
scsi8 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 9
usb-storage: waiting for device to settle before scanning
Vendor: PLEXTOR Model: DVDR PX-712ARev: 1.05
Type: CD-ROM ANSI SCSI revision: 00
sr0: scsi3-mmc drive: 15x/94x writer cd/rw xa/form2 cdda tray
Attached scsi CD-ROM sr0 at scsi7, channel 0, id 0, lun 0
Attached scsi generic sg11 at scsi7, channel 0, id 0, lun 0, type 5
usb-storage: device scan complete
Vendor: PLEXTOR Model: CD-R PX-W2410A Rev: 1.04
Type: CD-ROM ANSI SCSI revision: 00
sr1: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
Attached scsi CD-ROM sr1 at scsi8, channel 0, id 0, lun 0
Attached scsi generic sg12 at scsi8, channel 0, id 0, lun 0, type 5
usb-storage: device scan complete
cdrom: open failed.
cdrom: open failed.
end_request: I/O error, dev sr0, sector 2512
(on high-speed devices, hubs and controllers)
but no oops'es, crashes or lockups. Just a kernel that doesn't work work :-/
I feel I'm so very close to having solved the last problem with 2.6.10-rc2,
and I would really like to use it. Any suggestions?
-- ver_linux:
Linux boreas.iversen-net.dk 2.6.10-rc2-boreas #9 SMP Thu Nov 18 21:45:48 CET
2004 i686 GNU/Linux
Gnu C 3.3.4
Gnu make 3.80
binutils 2.15
util-linux 2.12
mount 2.12
module-init-tools 3.1-pre6
e2fsprogs 1.35
reiserfsprogs 3.6.19
reiser4progs line
xfsprogs 2.6.20
nfs-utils 1.0.6
Linux C Library2.3.2
Dynamic linker (ldd) 2.3.2
Procps 3.2.2
Net-tools 1.60
Console-tools 0.2.3
Sh-utils 5.2.1
Modules Loaded ns83820 psmouse prism54
--
Regards,
Christian Iversen
---
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
___
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] usb-storage crashes on 2.6.10-rc2 (SMP) in a NEW and INTERESTING way
On Thursday 18 November 2004 22:01, Pete Zaitcev wrote: On Thu, 18 Nov 2004 01:04:48 +0100, Christian Iversen [EMAIL PROTECTED] wrote: The new bug is http://bugme.osdl.org/show_bug.cgi?id=3761, which I marked as blocking because it's just too easy to bring the whole system down. usb 4-2: USB disconnect, address 2 usb 4-2.3: USB disconnect, address 5 target5:0:0: Illegal state transition NULL-cancel Unfortunately, the patch I sent before was not correct. The SCSI folks work on a solution though, see this: http://marc.theaimsgroup.com/?l=linux-scsim=109886580930570w=2 I'm not sure why it helped then. I just posted to this list about some new and interesting problems I get when using the patch you sent. Could I be experiencing these problems _because_ of the patch, rather than in spite of it? -- Regards, Christian Iversen --- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] usb-storage crashes on 2.6.10-rc2 (SMP) in a NEW and INTERESTING way
It's me again. I previously wrote about problems with http://bugme.osdl.org/show_bug.cgi?id=3728, which has now been fixed. However, the world is not trouble-free yet, as linux still crashes in certain situations on 2.6.10-rc2 with SMP systems. (UP systems are fine). The new bug is http://bugme.osdl.org/show_bug.cgi?id=3761, which I marked as blocking because it's just too easy to bring the whole system down. Could someone smart (Greg Kroah? :) please take a look at the dmesg I attached to the bug post? Particularly, what in the name of dingos kidneys is going on here? usb 4-2: USB disconnect, address 2 usb 4-2.3: USB disconnect, address 5 target5:0:0: Illegal state transition NULL-cancel Badness in scsi_device_set_state at drivers/scsi/scsi_lib.c:1717 [b0324d16] scsi_device_set_state+0xc6/0x130 [b031fcaa] scsi_device_cancel+0x2a/0x106 [b031fe10] scsi_device_cancel_cb+0x0/0x20 [b02f128e] device_for_each_child+0x3e/0x70 [b031fe61] scsi_host_cancel+0x31/0xc0 [b031fe10] scsi_device_cancel_cb+0x0/0x20 [b026765e] kobject_put+0x1e/0x30 [b026765e] kobject_put+0x1e/0x30 [b0267630] kobject_release+0x0/0x10 [b032726d] scsi_remove_device+0x7d/0xb0 [b032641d] scsi_forget_host+0x3d/0x60 [b031ff13] scsi_remove_host+0x23/0x80 [b0378aa6] storage_disconnect+0x86/0x9e [b035cdb8] usb_unbind_interface+0x88/0x90 [b02f21ef] device_release_driver+0x7f/0x90 [b02f2435] bus_remove_device+0x65/0xb0 [b02f11cf] device_del+0x5f/0xb0 [b0364006] usb_disable_device+0xb6/0x100 [b035f25f] usb_disconnect+0x9f/0x150 [b035f2db] usb_disconnect+0x11b/0x150 [b036053a] hub_port_connect_change+0x3ba/0x3f0 [b035df38] clear_port_feature+0x58/0x60 [b03607bc] hub_events+0x24c/0x370 [b0360915] hub_thread+0x35/0x110 [b01325c0] autoremove_wake_function+0x0/0x60 [b01030b2] ret_from_fork+0x6/0x14 [b01325c0] autoremove_wake_function+0x0/0x60 [b03608e0] hub_thread+0x0/0x110 [b01012d1] kernel_thread_helper+0x5/0x14 I hope somebody can help me, and I apologize if I seem impatient. I really would like this issue to be resolved, not just for my own sake. I'd be more than happy to help in any way I can, just say what you need, and I'll get it. More debug info? Other kinds of log? Hardware information? -- Regards, Christian Iversen --- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] usb.ids patch [1/3]
I saw some other guy getting a usb.ids patch accepted here, so I'd though I'd try. I already mailed these 3 to the maintainer, but he didn't react to them at all. This adds the HP Color LaserJet 2500 to usb.ids. I'm fairly certain the id is not shared with other printers, but I'm not entirely sure. --- /usr/share/usb.ids~ 2003-10-19 17:18:13.0 +0200 +++ /usr/share/usb.ids 2003-11-20 15:52:34.0 +0100 @@ -58,6 +58,7 @@ 0605 ScanJet 2200c 0701 ScanJet 5300c/5370c 0705 ScanJet 4400c + 0717 Color LaserJet 2500 0804 DeskJet 816c 0901 ScanJet 2300c 1004 DeskJet 970c/970cse -- Regards, Christian Iversen --- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_idU88alloc_id065op=click ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] usb.ids patch [2/3]
I have 3 quick changes: - Removed the (?), don't know why it was there. - Solid Year - Solid Year Keyboard looked funny, so it's replaced with Keyboard (it's probably has the model number ACK-xyz, but I don't know which.) - My keyboard is added (ACK-571U) --- usb.ids.old 2004-05-01 10:02:06.0 +0200 +++ usb.ids 2004-08-09 16:09:34.0 +0200 @@ -1393,9 +1393,10 @@ 0607 Bridge Information Co., Ltd 0609 SMK Manufacturing, Inc. 060a Worthington Data Solutions, Inc. -060b Solid Year (?) +060b Solid Year 0001 MacAlly Keyboard - 2101 Solid Year Keyboard + 2101 Keyboard + 5811 ACK-571U Wireless USB-Keyboard 060c EEH Datalink GmbH 060f Joinsoon Electronics Mfg. Co., Ltd 0611 Totoku Electric Co., Ltd -- Regards, Christian Iversen --- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_idU88alloc_id065op=click ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] usb.ids patch [3/3]
--- usb.ids.old 2004-06-11 23:28:41.0 +0200 +++ usb.ids 2004-08-09 15:59:36.0 +0200 @@ -2342,7 +2347,8 @@ 0a7e Octagon Systems Corp. 0a80 Rexon Technology Corp., Ltd 0a81 Chesen Electronics Corp. - 0101 Keyboard + 0101 Keyboard + 0205 PS/2 to USB Keyboard+Mouse converter 0a82 Syscan 4600 TravelScan 460/464 0a83 NextComm, Inc. -- Regards, Christian Iversen --- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588alloc_id=12065op=click ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] usb.ids patch [3/3]
On Thursday 11 November 2004 13:00, Christian Iversen wrote: --- usb.ids.old 2004-06-11 23:28:41.0 +0200 +++ usb.ids 2004-08-09 15:59:36.0 +0200 @@ -2342,7 +2347,8 @@ 0a7e Octagon Systems Corp. 0a80 Rexon Technology Corp., Ltd 0a81 Chesen Electronics Corp. - 0101 Keyboard + 0101 Keyboard + 0205 PS/2 to USB Keyboard+Mouse converter 0a82 Syscan 4600 TravelScan 460/464 0a83 NextComm, Inc. Oh yeah, and Signed-off-by: Christian Iversen [EMAIL PROTECTED] there, now I feel important.. :-) -- Regards, Christian Iversen --- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588alloc_id=12065op=click ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
Re: [linux-usb-devel] Fatal, 100% reproducible hard lockup on kernels 2.6.6-2.6.9 with 3 different USB controllers
On Wednesday 10 November 2004 17:14, David Brownell wrote: I looked at two of those dmesg logs and found several different errors: - Something killing EHCI right after it started up. I've not seen that with ALI myself, but some other folk seem to have that problem (mostly with ALI). I see. The lockup definately happens on both EHCI, UHCI and OHCI, but this issue may be a seperate one. - The usb-storage device seems to have spontaneously disconnected itself. Those problems seem to be getting a lot of reports lately; it's unclear why. Can I do something to help track this down? I really have no idea either, but maybe the (el cheapo) controller does something a little out-of-standard? - Yet another version of the problems SCSI has with disconnecting devices. Given the spontaneous disconnect, this is trouble. Indeed. I just tried inserting the very same external case on my notebook (running 2.6.8-rc1 UP), and it was fine. I plugged the usb connector in and out of my notebook as fast as I could, and it still wouldn't crash. Yet, on my server (dual AMD SMP) that would be a sure way to kill it. It seems like an SMP-only issue, at least to be. - Some bogus diagnostics on non-error situations. To do with having a cheap controller, or just random spoutings from the driver? I think the last two issues are better in current BK kernels (SCSI and bogus diagnostics). As for the first two, nobody's yet provided any clues as to what's going on. I'd be happy to help, if only I knew how :-) And btw, 2.6.10-rc1 seems a little better, although the lockups still come at some point (maybe not on first unplug, but then on second... race?) - Dave p.s. Cool, you're using a very recent version of usbutils! More folk should be that current. Thanks :) (although, it's just standard Sarge goodness. thanks to Aurelien Jarno of the Debian project) -- Regards, Christian Iversen --- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588alloc_id=12065op=click ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] unneeded SubClass and Protocol entries
I would like to inform you that my ALLNet IDE-USB bridge gives the following warning when connecting: usb-storage: This device (05ab,0060,1106 S 06 P 50) has unneeded SubClass and Protocol entries in unusual_devs.h Please send a copy of this message to [EMAIL PROTECTED] Please CC me with any comments, as I am not subscribed to this list -- Regards, Christian Iversen --- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721alloc_id=10040op=click ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
