Bug#675093: linux-image-3.2.0-2-amd64: USB "timeout initializing reports" with Eaton UPS

2012-05-29 Thread Manu Benoît
Package: linux-2.6
Version: 3.2.18-1
Severity: normal

It would seem that the kernel is doing something wrong when trying to
initalise an USB connection to an Eaton (formerly Merlin Gerin) Ellipse
Max UPS.

When the box is booting, the device's initialisation adds a ~15s delay,
then some USB error is reported (at timestamp 18.319789 in the kernel
log below).
Strangely enough, the device appears to work after that.

I am reporting this error for the kernel on this computer (which is a
x86-64 and includes various tainted modules), however it also occurs on
a much older x86 box running a Debian Squeeze with
linux-image-2.6.32-5-686 (no proprietary drivers loaded, either). The
device connected to that box is a different model of Eaton Ellipse Max
UPS. Both UPS's are brand new.

-- Package-specific info:
** Version:
Linux version 3.2.0-2-amd64 (Debian 3.2.18-1)
(debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) )
#1 SMP Mon May 21 17:45:41 UTC 2012

** Command line:
BOOT_IMAGE=/vmlinuz-3.2.0-2-amd64 root=/dev/mapper/Cthugha-Root ro quiet

** Tainted: PO (4097)
 * Proprietary module has been loaded.
 * Out-of-tree module has been loaded.

** Kernel log:
[4.010036] scsi 6:0:0:0: CD-ROMSMI  USB DISK
 1100 PQ: 0 ANSI: 2
[4.012007] sr1: scsi3-mmc drive: 0x/0x caddy
[4.012198] sr 6:0:0:0: Attached scsi CD-ROM sr1
[4.075071] usb 2-2.2: New USB device found, idVendor=090c,
idProduct=1000
[4.075076] usb 2-2.2: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[4.075079] usb 2-2.2: Product: USB DISK
[4.075082] usb 2-2.2: Manufacturer: SMI Corporation
[4.075084] usb 2-2.2: SerialNumber: 1
[4.075578] scsi7 : usb-storage 2-2.2:1.0
[4.144561] usb 2-1.2: reset high-speed USB device number 6 using
ehci_hcd
[4.312492] usb 2-2.4: new low-speed USB device number 10 using ehci_hcd
[4.684396] usb 2-1.2: reset high-speed USB device number 6 using
ehci_hcd
[4.860338] usb 2-1.2: reset high-speed USB device number 6 using
ehci_hcd
[5.036122] usb 2-1.2: reset high-speed USB device number 6 using
ehci_hcd
[5.073680] scsi 7:0:0:0: CD-ROMSMI  USB DISK
 1100 PQ: 0 ANSI: 2
[5.076692] sr2: scsi3-mmc drive: 0x/0x caddy
[5.076925] sr 7:0:0:0: Attached scsi CD-ROM sr2
[5.167483] usb 2-2.4: New USB device found, idVendor=0463,
idProduct=
[5.167488] usb 2-2.4: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[5.167491] usb 2-2.4: Product: Ellipse MAX
[5.167493] usb 2-2.4: Manufacturer: EATON
[5.167496] usb 2-2.4: SerialNumber: ADKM25014
[5.208346] usb 2-1.2: reset high-speed USB device number 6 using
ehci_hcd
[5.384134] usb 2-1.2: reset high-speed USB device number 6 using
ehci_hcd
[5.560072] usb 2-1.2: reset high-speed USB device number 6 using
ehci_hcd
[5.736015] usb 2-1.2: reset high-speed USB device number 6 using
ehci_hcd
[5.869976] PM: Starting manual resume from disk
[5.869979] PM: Hibernation image partition 254:1 present
[5.869980] PM: Looking for hibernation image.
[5.870175] PM: Image not found (code -22)
[5.870178] PM: Hibernation image not present or could not be loaded.
[5.910554] EXT4-fs (dm-0): mounted filesystem with ordered data
mode. Opts: (null)
[   18.319789] generic-usb 0003:0463:.0003: usb_submit_urb(ctrl) failed
[   18.319850] generic-usb 0003:0463:.0003: timeout initializing reports
[   18.320070] generic-usb 0003:0463:.0003: hiddev0,hidraw2: USB HID
v1.10 Device [EATON Ellipse MAX] on usb-:00:1d.7-2.4/input0
[   19.362918] udevd[417]: starting version 175
[   19.696373] input: Power Button as
/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2
[   19.696378] ACPI: Power Button [PWRB]
[   19.696442] input: Power Button as
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
[   19.696446] ACPI: Power Button [PWRF]
[   19.845300] wmi: Mapper loaded
[   19.953638] iTCO_vendor_support: vendor-support=0
[   19.961081] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07
[   19.961154] iTCO_wdt: Found a ICH10R TCO device (Version=2,
TCOBASE=0x0860)
[   19.961245] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   19.989060] input: PC Speaker as /devices/platform/pcspkr/input/input4
[   20.008091] EDAC MC: Ver: 2.1.0
[   20.114735] Error: Driver 'pcspkr' is already registered, aborting...
[   20.116254] i801_smbus :00:1f.3: PCI INT C -> GSI 18 (level, low)
-> IRQ 18
[   20.116258] ACPI: resource :00:1f.3 [io  0x0400-0x041f] conflicts
with ACPI region SMRG [io 0x400-0x40f]
[   20.116260] ACPI: If an ACPI driver is available for this device, you
should use it instead of the native driver
[   20.210611] snd_hda_intel :00:1b.0: PCI INT A -> GSI 22 (level,
low) -> IRQ 22
[   20.210651] snd_hda_intel :00:1b.0: irq 70 for MSI/MSI-X
[   20.210671] snd_hda_intel :00:1b.0: setting latency timer to 64
[   20.541311] nvidia: module license 'NVIDIA' taints kernel.
[   20.541314] Disabling lock debugging due to kerne

Bug#675093: linux-image-3.2.0-2-amd64: USB "timeout initializing reports" with Eaton UPS

2012-05-31 Thread Manu Benoît
On 31/05/12 09:52, Jiri Kosina wrote:
> Hmm, that's odd. This device has been on 'HID_QUIRK_NOGET' list for very 
> long time already (even before 2.6.32). Could you please apply the patch 
> below, modprobe hid module with 'debug=1' parameter, and send me the 
> output?
> 
> diff --git a/drivers/hid/usbhid/hid-core.c b/drivers/hid/usbhid/hid-core.c
> index 482f936..25ebf54 100644
> --- a/drivers/hid/usbhid/hid-core.c
> +++ b/drivers/hid/usbhid/hid-core.c
> @@ -397,6 +397,7 @@ static int hid_submit_ctrl(struct hid_device *hid)
>   r = usb_submit_urb(usbhid->urbctrl, GFP_ATOMIC);
>   if (r < 0) {
>   hid_err(hid, "usb_submit_urb(ctrl) failed: %d\n", r);
> + dump_stack();
>   return r;
>   }
>   usbhid->last_ctrl = jiffies;
>

This patch could not be applied to the Debian kernel source, somehow. I
have assumed the code I should modify is this:

if (usb_submit_urb(usbhid->urbctrl, GFP_ATOMIC)) {
usb_autopm_put_interface_async(usbhid->intf);
hid_err(hid, "usb_submit_urb(ctrl) failed\n");
return -1;
}

(line 382 of drivers/hid/usbhid/hid-core.c) instead of what the patch
originally modifies.

Kernel is being compiled at the moment. Sorry for taking so long, it's
been a while since I had to do that.

-- 
Manu Benoît



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4fc73091.2080...@nocternity.net



Bug#675093: linux-image-3.2.0-2-amd64: USB "timeout initializing reports" with Eaton UPS

2012-05-31 Thread Manu Benoît
2.18/debian/build/source_amd64_none/drivers/hid/usbhid/hid-core.c:
submitting ctrl urb: Get_Report wValue=0x0101 wIndex=0x wLength=6
[8.533386]
/usr/src/linux-2.6-3.2.18/debian/build/source_amd64_none/drivers/hid/usbhid/hid-core.c:
submitting ctrl urb: Get_Report wValue=0x010f wIndex=0x wLength=2
[8.575868]
/usr/src/linux-2.6-3.2.18/debian/build/source_amd64_none/drivers/hid/usbhid/hid-core.c:
submitting ctrl urb: Get_Report wValue=0x0102 wIndex=0x wLength=6
[8.627101]
/usr/src/linux-2.6-3.2.18/debian/build/source_amd64_none/drivers/hid/usbhid/hid-core.c:
submitting ctrl urb: Get_Report wValue=0x0106 wIndex=0x wLength=6
[8.678835]
/usr/src/linux-2.6-3.2.18/debian/build/source_amd64_none/drivers/hid/usbhid/hid-core.c:
submitting ctrl urb: Get_Report wValue=0x0320 wIndex=0x wLength=2
[8.721446]
/usr/src/linux-2.6-3.2.18/debian/build/source_amd64_none/drivers/hid/usbhid/hid-core.c:
submitting ctrl urb: Get_Report wValue=0x03ff wIndex=0x wLength=24
[8.769056]
/usr/src/linux-2.6-3.2.18/debian/build/source_amd64_none/drivers/hid/usbhid/hid-core.c:
submitting ctrl urb: Get_Report wValue=0x03fe wIndex=0x wLength=11
[   18.342860]
/usr/src/linux-2.6-3.2.18/debian/build/source_amd64_none/drivers/hid/usbhid/hid-core.c:
timeout waiting for ctrl or out queue to clear
[   18.342955]
/usr/src/linux-2.6-3.2.18/debian/build/source_amd64_none/drivers/hid/usbhid/hid-core.c:
submitting ctrl urb: Get_Report wValue=0x030d wIndex=0x wLength=4
[   18.342966] generic-usb 0003:0463:.0003: usb_submit_urb(ctrl) failed
[   18.343017] Pid: 0, comm: swapper/0 Tainted: P   O
3.2.0-2-amd64 #1
[   18.343020] Call Trace:
[   18.343022][] ?
hid_submit_ctrl+0x21e/0x244 [usbhid]
[   18.343040]  [] ? swiotlb_tbl_unmap_single+0x50/0xb7
[   18.343046]  [] ? hid_ctrl+0xca/0x14f [usbhid]
[   18.343058]  [] ? usb_hcd_giveback_urb+0x76/0xaa
[usbcore]
[   18.343062]  [] ? ehci_urb_done+0x6b/0x7b [ehci_hcd]
[   18.343066]  [] ? qh_completions+0x30a/0x39d [ehci_hcd]
[   18.343070]  [] ? end_unlink_async+0x46/0xbd [ehci_hcd]
[   18.343074]  [] ? ehci_irq+0x90/0x1ee [ehci_hcd]
[   18.343078]  [] ? __rcu_process_callbacks+0x72/0x2c0
[   18.343084]  [] ? usb_hcd_irq+0x37/0x6a [usbcore]
[   18.343086]  [] ? handle_irq_event_percpu+0x50/0x180
[   18.343089]  [] ? __do_softirq+0x13e/0x177
[   18.343092]  [] ? __setup_APIC_LVTT+0x4a/0x66
[   18.343095]  [] ? handle_irq_event+0x34/0x53
[   18.343098]  [] ? arch_local_irq_save+0x11/0x17
[   18.343100]  [] ? handle_fasteoi_irq+0x7c/0xaf
[   18.343103]  [] ? handle_irq+0x1d/0x21
[   18.343106]  [] ? do_IRQ+0x42/0x98
[   18.343109]  [] ? common_interrupt+0x6e/0x6e
[   18.343110][] ? intel_idle+0xea/0x119
[   18.343114]  [] ? intel_idle+0xc9/0x119
[   18.343118]  [] ? cpuidle_idle_call+0xec/0x179
[   18.343120]  [] ? cpu_idle+0xa5/0xf2
[   18.343124]  [] ? start_kernel+0x3bd/0x3c8
[   18.343127]  [] ? early_idt_handlers+0x140/0x140
[   18.343129]  [] ? x86_64_start_kernel+0x104/0x111
[   18.343183] generic-usb 0003:0463:.0003: timeout initializing reports
[   18.343565] generic-usb 0003:0463:.0003: hiddev0,hidraw2: USB HID
v1.10 Device [EATON Ellipse MAX] on usb-:00:1d.7-2.4/input0


-- 
Manu Benoît



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4fc74da4.2070...@nocternity.net



Bug#675093: linux-image-3.2.0-2-amd64: USB "timeout initializing reports" with Eaton UPS

2012-06-21 Thread Manu Benoît
On 08/06/12 13:55, Jiri Kosina wrote:
> Ok, thanks. I will have to think about this whole thing a little bit more, 
> but as a first step, could you please try with the patch below to see if 
> it makes any difference and makes the device behave correctly? Thanks.

No, it didn't change anything (I'd left the debugging mode active and
the stack dump, it's still the exact same log).

Sorry it took so long for me to respond.

-- 
Manu Benoît



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4fe32741.5030...@nocternity.net