@fishor:
sorry I misunderstood you. Nevertheless, the correct handling in your case is
to issue a command to spin down the disk in the suspend() method of the storage
driver. It needs to be discussed and tested whether this can be done for all
devices, or your device needs a new kind of quirk.
That is not a kernel bug. You can set a default timeout for autosuspend
in the module parameters of usbcore.
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
@Amit
git://www.kernel.org/linux/kernel/git/gregkh/usb-2.6.git
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubu
additional quirks
** Attachment added: "quirk3.diff"
http://launchpadlibrarian.net/8533186/quirk3.diff
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact fo
The most likely devices to fail upon suspension are those that are least
likely attached to laptops. Scanners and printers come foremost to my
mind. To test printers you'll have to unload the usblp module, wait 4
seconds and reload it. Usually you see a disconnect event in the syslog
when the devic
@Renzo Bagnati
Please verify that scanner. I cannot blacklist on a suspicion.
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs m
@Philipp
Please report this to [EMAIL PROTECTED]
@Amit
I am taking all IDs reported in this thread and putting them into Greg's
tree. You can use its latest quirk file.
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification bec
Any further IDs? Everything posted so far is on the way into the
standard kernel.
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bug
> UMax
> Astra Net e3420.
Post vendor:product id
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
Try the "autosuspend" parameter in /etc/modprobe.conf.local
The IDs so far reported have been added to the USB development tree.
** Attachment added: "new_quirks_1.patch"
http://launchpadlibrarian.net/8410141/new_quirks_1.patch
--
some usb_devices fault if usb_suspend enabled
https://bugs.la
Regarding the Braille device I am sorry. Please get me the
vendor:product ids. Or is there a device class?
For the other devices, please post the vendor:product pairs on this page
and I'll include them in 2.6.23
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/854
The kernel does wake up the devices if they are opened through usbfs.
But that exactly is the point the buggy devices crash. Either you never
suspend the scanners at all, or you need a work around.
As for the placement, it must be in kernel space. Some devices that have
kernel drivers have the sam
The increment of the number is consistent with the scanner disconnecting
upon suspension, but the part of your log you posted doesn't show it. Is
it complete?
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are
Ok, if you want to capture debug info.
1. Boot with your scanner switched off
2. Notice the state of /var/log/messages
3. Switch on your scanner
4. Wait half a minute
5. Do "scanimage -L" (or anything that will fail)
6. Send me everything added to /var/log/messages after step 2
--
some usb_devic
Yes, I need the syslog, but I need it for the actual failure case. If
the scanner works I can't fix bugs.
--
some usb_devices fault if usb_suspend enabled
https://bugs.launchpad.net/bugs/85488
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Hi,
the newest USB development trees contain a workaround for some types of
breakage relevant here. However the scanner must be blacklisted for that
to be activated. I need syslogs, preferably with CONFIG_USB_DEBUG, of
your failures to include your scanners in new releases.
Regards
Oliver
usb dev
16 matches
Mail list logo
