[linux-usb-devel] 2.6.22-rc2: regression: STD fails with pci_device_suspend(): usb_hcd_pci_suspend+0x0/0x160 [usbcore]() returns -16
This works just fine up to and including 2.6.21.
{pts/0}% lspci
00:00.0 Host bridge: ALi Corporation M1644/M1644T Northbridge+Trident (rev 01)
00:01.0 PCI bridge: ALi Corporation PCI to AGP Controller
00:02.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:04.0 IDE interface: ALi Corporation M5229 IDE (rev c3)
00:06.0 Multimedia audio controller: ALi Corporation M5451 PCI AC-Link
Controller Audio Device (rev 01)
00:07.0 ISA bridge: ALi Corporation M1533/M1535 PCI to ISA Bridge [Aladdin
IV/V/V+]
00:08.0 Bridge: ALi Corporation M7101 Power Management Controller [PMU]
00:0a.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100]
(rev 08)
00:10.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller
(rev 01)
00:11.0 CardBus bridge: Toshiba America Info Systems ToPIC100 PCI to Cardbus
Bridge with ZV Support (rev 32)
00:11.1 CardBus bridge: Toshiba America Info Systems ToPIC100 PCI to Cardbus
Bridge with ZV Support (rev 32)
00:12.0 System peripheral: Toshiba America Info Systems SD TypA Controller
(rev 03)
01:00.0 VGA compatible controller: Trident Microsystems CyberBlade XPAi1 (rev
82)
unfortunatelt dmesg got truncated; if required I can rebuild with larger
buffer; the part around suspend is
swsusp: Marking nosave pages: 0009f000 - 0010
swsusp: Basic memory bitmaps created
Stopping tasks ... done.
Shrinking memory... done (14553 pages freed)
Freed 58212 kbytes in 0.30 seconds (194.04 MB/s)
Suspending console(s)
sd 0:0:0:0: [sda] Synchronizing SCSI cache
pnp: Device 00:09 disabled.
ACPI: PCI interrupt for device :00:0a.0 disabled
Trying to free already-free IRQ 11
ACPI: PCI interrupt for device :00:06.0 disabled
ACPI: Unable to derive IRQ for device :00:04.0
pci_device_suspend(): usb_hcd_pci_suspend+0x0/0x160 [usbcore]() returns -16
suspend_device(): pci_device_suspend+0x0/0x70() returns -16
Could not suspend device :00:02.0: error -16
PM: Writing back config space on device :00:04.0 at offset 1 (was 291,
writing 295)
ACPI: Unable to derive IRQ for device :00:04.0
ACPI: PCI Interrupt :00:04.0[A]: no GSI
ACPI: PCI Interrupt :00:06.0[A] - Link [LNKH] - GSI 11 (level, low) -
IRQ 11
ata1.00: ata_hpa_resize 1: sectors = 39070080, hpa_sectors = 39070080
ata1.00: ata_hpa_resize 1: sectors = 39070080, hpa_sectors = 39070080
ata1.00: configured for UDMA/33
sd 0:0:0:0: [sda] 39070080 512-byte hardware sectors (20004 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
PM: Writing back config space on device :00:0a.0 at offset f (was
38080100, writing 3808010b)
PM: Writing back config space on device :00:0a.0 at offset 6 (was 0,
writing f7d0)
PM: Writing back config space on device :00:0a.0 at offset 5 (was 1,
writing eb41)
PM: Writing back config space on device :00:0a.0 at offset 4 (was 0,
writing f7efd000)
PM: Writing back config space on device :00:0a.0 at offset 3 (was 0,
writing 4008)
PM: Writing back config space on device :00:0a.0 at offset 1 (was 290,
writing 297)
ata2.00: configured for UDMA/33
pnp: Failed to activate device 00:05.
pnp: Failed to activate device 00:06.
pnp: Device 00:09 activated.
sd 0:0:0:0: [sda] Starting disk
eth1: PRI 31 variant 2 version 9.48
eth1: NIC 5 variant 2 version 1.02
Restarting tasks ... done.
swsusp: Basic memory bitmaps freed
input: Power Button (FF) as /class/input/input4
ACPI: Power Button (FF) [PWRF]
input: Lid Switch as /class/input/input5
ACPI: Lid Switch [LID]
eth1: PRI 31 variant 2 version 9.48
eth1: NIC 5 variant 2 version 1.02
eth1: PRI 31 variant 2 version 9.48
eth1: NIC 5 variant 2 version 1.02
eth1: PRI 31 variant 2 version 9.48
eth1: NIC 5 variant 2 version 1.02
.config:
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.22-rc2-cfs-v13
# Sat May 19 12:21:46 2007
#
CONFIG_X86_32=y
CONFIG_GENERIC_TIME=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_QUICKLIST=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y
CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_INIT_ENV_ARG_LIMIT=32
#
# General setup
#
CONFIG_LOCALVERSION=
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_IPC_NS is not set
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
# CONFIG_TASKSTATS is not set
# CONFIG_UTS_NS is not set
CONFIG_AUDIT=y
CONFIG_AUDITSYSCALL=y
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=14
# CONFIG_SYSFS_DEPRECATED is not set
Re: [linux-usb-devel] [Bugme-new] [Bug 8510] New: OHCI constantly attempts suspending root hub on ALi motherboard
On Sunday 20 May 2007, David Brownell wrote:
On Saturday 19 May 2007, David Brownell wrote:
On Saturday 19 May 2007, Andrew Morton wrote:
On Sat, 19 May 2007 10:08:40 -0700 [EMAIL PROTECTED]
wrote:
http://bugzilla.kernel.org/show_bug.cgi?id=8510
A regression.
From 2.6.16, yes... this has been around for a while, but nobody
came up with a patch.
I suggest someone with the hardware just provide an update to the
drivers/usb/host/ohci-pci.c file using the
PCI_DEVICE(PCI_VENDOR_ID_ITE, 0x8152),
quirk table entry as a model.
Grr, better yet: find out why the existing quirk entry for this
particular laptop doesn't trigger.
Because it is usig wrong subvendor. Runtime tested:
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
ohci_hcd: block sizes: ed 64 td 64
ACPI: PCI Interrupt :00:02.0[A] - Link [LNKG] - GSI 11 (level, low) -
IRQ 11
ohci_hcd :00:02.0: OHCI Host Controller
/home/bor/src/linux-git/drivers/usb/core/inode.c: creating file 'devices'
/home/bor/src/linux-git/drivers/usb/core/inode.c: creating file '001'
ohci_hcd :00:02.0: new USB bus registered, assigned bus number 1
ohci_hcd :00:02.0: created debug files
ohci_hcd :00:02.0: irq 11, io mem 0xf7eff000
ohci_hcd :00:02.0: enabling initreset quirk
ohci_hcd :00:02.0: OHCI controller state
ohci_hcd :00:02.0: OHCI 1.0, NO legacy support registers
ohci_hcd :00:02.0: control 0x083 HCFS=operational CBSR=3
ohci_hcd :00:02.0: cmdstatus 0x0 SOC=0
ohci_hcd :00:02.0: intrstatus 0x0044 RHSC SF
ohci_hcd :00:02.0: intrenable 0x800a MIE RD WDH
ohci_hcd :00:02.0: hcca frame #0003
ohci_hcd :00:02.0: roothub.a 01000203 POTPGT=1 NPS NDP=3(3)
ohci_hcd :00:02.0: roothub.b PPCM= DR=
ohci_hcd :00:02.0: roothub.status 8000 DRWE
ohci_hcd :00:02.0: roothub.portstatus [0] 0x0100 PPS
ohci_hcd :00:02.0: roothub.portstatus [1] 0x0100 PPS
ohci_hcd :00:02.0: roothub.portstatus [2] 0x0100 PPS
usb usb1: default language 0x0409
usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: OHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.22-rc2-cfs-v13-1avb ohci_hcd
usb usb1: SerialNumber: :00:02.0
usb usb1: uevent
usb usb1: usb_probe_device
usb usb1: configuration #1 chosen from 1 choice
usb usb1: adding 1-0:1.0 (config #1, interface 0)
usb 1-0:1.0: uevent
usb 1-0:1.0: uevent
hub 1-0:1.0: usb_probe_interface
hub 1-0:1.0: usb_probe_interface - got id
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
hub 1-0:1.0: standalone hub
hub 1-0:1.0: no power switching (usb 1.0)
hub 1-0:1.0: global over-current protection
hub 1-0:1.0: power on to power good time: 2ms
hub 1-0:1.0: local power source is good
hub 1-0:1.0: no over-current condition exists
hub 1-0:1.0: trying to enable port power on non-switchable hub
hub 1-0:1.0: state 7 ports 3 chg evt
/home/bor/src/linux-git/drivers/usb/core/inode.c: creating file '001'
usb usb1: remote wakeup needed for autosuspend
---
Subject: [PATCH] Fix USB OHCI Subvendor for Toshiba Portege 4000
From: Andrey Borzenkov [EMAIL PROTECTED]
For Portege 4000 Subvendor is 1179 (PCI_VENDOR_ID_TOSHIBA) not
0x102f (PCI_VENDOR_ID_TOSHIBA_2)
00:02.0 USB Controller [0c03]: ALi Corporation USB 1.1 Controller
[10b9:5237] (rev 03) (prog-if 10 [OHCI])
Subsystem: Toshiba America Info Systems Unknown device [1179:0004]
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at f7eff000 (32-bit, non-prefetchable) [size=4K]
Capabilities: access denied
Signed-off-by: Andrey Borzenkov [EMAIL PROTECTED]
---
drivers/usb/host/ohci-pci.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/host/ohci-pci.c b/drivers/usb/host/ohci-pci.c
index 7970560..ca62cb5 100644
--- a/drivers/usb/host/ohci-pci.c
+++ b/drivers/usb/host/ohci-pci.c
@@ -137,7 +137,7 @@ static const struct pci_device_id ohci_pci_quirks[] = {
/* Toshiba portege 4000 */
.vendor = PCI_VENDOR_ID_AL,
.device = 0x5237,
- .subvendor = PCI_VENDOR_ID_TOSHIBA_2,
+ .subvendor = PCI_VENDOR_ID_TOSHIBA,
.subdevice = 0x0004,
.driver_data= (unsigned long) broken_suspend,
},
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
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] [Bugme-new] [Bug 8510] New: OHCI constantly attempts suspending root hub on ALi motherboard
On Sunday 20 May 2007, Alan Stern wrote: On Sun, 20 May 2007, Andrey Borzenkov wrote: On Sunday 20 May 2007, David Brownell wrote: On Saturday 19 May 2007, David Brownell wrote: On Saturday 19 May 2007, Andrew Morton wrote: On Sat, 19 May 2007 10:08:40 -0700 [EMAIL PROTECTED] wrote: http://bugzilla.kernel.org/show_bug.cgi?id=8510 A regression. From 2.6.16, yes... this has been around for a while, but nobody came up with a patch. I suggest someone with the hardware just provide an update to the drivers/usb/host/ohci-pci.c file using the PCI_DEVICE(PCI_VENDOR_ID_ITE, 0x8152), quirk table entry as a model. Grr, better yet: find out why the existing quirk entry for this particular laptop doesn't trigger. Because it is usig wrong subvendor. Runtime tested: Does this fix the regression described in your email 2.6.22-rc2: regression: STD fails with pci_device_suspend(): usb_hcd_pci_suspend+0x0/0x160 [usbcore]() returns -16 ? No. Unfortunately. Here is dmesg with patch and USB_DEBUG swsusp: Marking nosave pages: 0009f000 - 0010 swsusp: Basic memory bitmaps created Stopping tasks ... done. Shrinking memory... done (61536 pages freed) Freed 246144 kbytes in 1.99 seconds (123.69 MB/s) Suspending console(s) hub 1-0:1.0: hub_suspend ohci_hcd :00:02.0: suspend root hub usb usb1: usb suspend usb usb1: usb resume usb usb1: finish resume hub 1-0:1.0: hub_resume ohci_hcd :00:02.0: wakeup root hub sd 0:0:0:0: [sda] Synchronizing SCSI cache pnp: Device 00:09 disabled. Trying to free already-free IRQ 11 ACPI: PCI interrupt for device :00:06.0 disabled ACPI: Unable to derive IRQ for device :00:04.0 pci_device_suspend(): usb_hcd_pci_suspend+0x0/0x230 [usbcore]() returns -16 suspend_device(): pci_device_suspend+0x0/0x70() returns -16 Could not suspend device :00:02.0: error -16 PM: Writing back config space on device :00:04.0 at offset 1 (was 291, writing 295) ACPI: Unable to derive IRQ for device :00:04.0 ACPI: PCI Interrupt :00:04.0[A]: no GSI ACPI: PCI Interrupt :00:06.0[A] - Link [LNKH] - GSI 11 (level, low) - IRQ 11 ata1.00: ata_hpa_resize 1: sectors = 39070080, hpa_sectors = 39070080 ata1.00: ata_hpa_resize 1: sectors = 39070080, hpa_sectors = 39070080 ata1.00: configured for UDMA/33 sd 0:0:0:0: [sda] 39070080 512-byte hardware sectors (20004 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA PM: Writing back config space on device :00:0a.0 at offset f (was 38080100, writing 3808010b) PM: Writing back config space on device :00:0a.0 at offset 6 (was 0, writing f7d0) PM: Writing back config space on device :00:0a.0 at offset 5 (was 1, writing eb41) PM: Writing back config space on device :00:0a.0 at offset 4 (was 0, writing f7efd000) PM: Writing back config space on device :00:0a.0 at offset 3 (was 0, writing 4008) PM: Writing back config space on device :00:0a.0 at offset 1 (was 290, writing 297) ata2.00: configured for UDMA/33 pnp: Failed to activate device 00:05. pnp: Failed to activate device 00:06. pnp: Device 00:09 activated. sd 0:0:0:0: [sda] Starting disk eth1: PRI 31 variant 2 version 9.48 eth1: NIC 5 variant 2 version 1.02 Restarting tasks ... 7hub 1-0:1.0: state 7 ports 3 chg evt usb usb1: remote wakeup needed for autosuspend done. swsusp: Basic memory bitmaps freed input: Power Button (FF) as /class/input/input8 ACPI: Power Button (FF) [PWRF] input: Lid Switch as /class/input/input9 ACPI: Lid Switch [LID] eth1: PRI 31 variant 2 version 9.48 eth1: NIC 5 variant 2 version 1.02 eth1: PRI 31 variant 2 version 9.48 eth1: NIC 5 variant 2 version 1.02 eth1: PRI 31 variant 2 version 9.48 eth1: NIC 5 variant 2 version 1.02 - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ 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] 2.6.20-rc5: BUG: lock held at task exit time! (pm_mutex){--..}, at: [c013bfff] enter_state+0x3f/0x170
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 16 January 2007 23:29, Len Brown wrote:
On Tuesday 16 January 2007 13:22, Andrey Borzenkov wrote:
I have Toshiba Portege 4000 that almost always hangs dead resuming from
STR. This was better before 2.6.18, since then STR is unusable. Sometimes
it manages to resume; yesterday I got on console and in dmesg:
=
[ BUG: lock held at task exit time! ]
-
echo/28793 is exiting with locks still held!
1 lock held by echo/28793:
#0: (pm_mutex){--..}, at: [c013bfff] enter_state+0x3f/0x170
stack backtrace:
[c0103fea] show_trace_log_lvl+0x1a/0x30
[c01045f2] show_trace+0x12/0x20
[c01046a6] dump_stack+0x16/0x20
[c0132377] debug_check_no_locks_held+0x87/0x90
[c011c8bb] do_exit+0x4db/0x820
[c011cc29] do_group_exit+0x29/0x70
[c011cc7f] sys_exit_group+0xf/0x20
[c010300e] sysenter_past_esp+0x5f/0x99
===
the global pm_mutex that this refers to is used in generic PM code, not USB
code.
enter_state() grabs it at the beginning of the suspend, and releases it
when resume is completed.
The mystery is why echo is exiting before enter_state() completes.
if ! (/bin/echo $PARAM $FILE ) ;then
ret=1
fi
Same if you don't put the echo in the background here?
I just tried once more on 2.6.20-rc5 with
boot ... init=/bin/sh
mount -t sysfs sysfs /sys
echo mem /proc/power/state
this hung dead on resume - not a single message (kernel was compiled with
PM_DEBUG).
I usually do not get any messages at all. I believe it was two times I got
anything; one is quoted in bug report and second here.
- -andrey
I have a bug report about resume issue but I may have wrongly attributed
it to ACPI: http://bugzilla.kernel.org/show_bug.cgi?id=7499
hard to say if the failure is related to ACPI or not at this point --
though it is not unusual for people to assume that STR and ACPI
are synonyms, so that if STR doesn't work it must be due to ACPI
rather than generic PM code or drivers.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFs2heR6LMutpd94wRAqS7AJ0TMRb12cEgKrH0o/mW/sF1oNJ9CwCglx3z
HhzT2c3bAjBbNT7pOyCbATE=
=pp1M
-END PGP SIGNATURE-
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
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] 2.6.20-rc5: BUG: lock held at task exit time! (pm_mutex){--..}, at: [c013bfff] enter_state+0x3f/0x170
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 16 January 2007 23:31, Alan Stern wrote:
On Tue, 16 Jan 2007, Andrey Borzenkov wrote:
I have Toshiba Portege 4000 that almost always hangs dead resuming from
STR. This was better before 2.6.18, since then STR is unusable. Sometimes
it manages to resume; yesterday I got on console and in dmesg:
=
[ BUG: lock held at task exit time! ]
- -
echo/28793 is exiting with locks still held!
1 lock held by echo/28793:
#0: (pm_mutex){--..}, at: [c013bfff] enter_state+0x3f/0x170
stack backtrace:
[c0103fea] show_trace_log_lvl+0x1a/0x30
[c01045f2] show_trace+0x12/0x20
[c01046a6] dump_stack+0x16/0x20
[c0132377] debug_check_no_locks_held+0x87/0x90
[c011c8bb] do_exit+0x4db/0x820
[c011cc29] do_group_exit+0x29/0x70
[c011cc7f] sys_exit_group+0xf/0x20
[c010300e] sysenter_past_esp+0x5f/0x99
===
Have you tried using 2.6.19? There was a bug which got fixed in that
release.
Yes I did. It had the same problem.
Sorry for posting to wrong list, but I hit USB pm_mutex before other one.
- -andrey
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFrmrWR6LMutpd94wRAr6eAKCVhFTsgtrrxlPWcY/kCa6hAq8sWACgkUrK
SA8GeytfzwD38IOrVCIkAXU=
=Me0j
-END PGP SIGNATURE-
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
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] 2.6.20-rc5: BUG: lock held at task exit time! (pm_mutex){--..}, at: [c013bfff] enter_state+0x3f/0x170
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have Toshiba Portege 4000 that almost always hangs dead resuming from STR.
This was better before 2.6.18, since then STR is unusable. Sometimes it
manages to resume; yesterday I got on console and in dmesg:
=
[ BUG: lock held at task exit time! ]
- -
echo/28793 is exiting with locks still held!
1 lock held by echo/28793:
#0: (pm_mutex){--..}, at: [c013bfff] enter_state+0x3f/0x170
stack backtrace:
[c0103fea] show_trace_log_lvl+0x1a/0x30
[c01045f2] show_trace+0x12/0x20
[c01046a6] dump_stack+0x16/0x20
[c0132377] debug_check_no_locks_held+0x87/0x90
[c011c8bb] do_exit+0x4db/0x820
[c011cc29] do_group_exit+0x29/0x70
[c011cc7f] sys_exit_group+0xf/0x20
[c010300e] sysenter_past_esp+0x5f/0x99
===
I have a bug report about resume issue but I may have wrongly attributed it to
ACPI: http://bugzilla.kernel.org/show_bug.cgi?id=7499
echo mentioned here comes from echo ... /sys/power/state
I have been suspecting ACPI because another permanent bug I have is lockup
using acpi_cpufreq and ondemand governor ... but it may be red herring
(although it is annoying).
{pts/0}% lspci
00:00.0 Host bridge: ALi Corporation M1644/M1644T Northbridge+Trident (rev 01)
00:01.0 PCI bridge: ALi Corporation PCI to AGP Controller
00:02.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:04.0 IDE interface: ALi Corporation M5229 IDE (rev c3)
00:06.0 Multimedia audio controller: ALi Corporation M5451 PCI AC-Link
Controller Audio Device (rev 01)
00:07.0 ISA bridge: ALi Corporation M1533/M1535 PCI to ISA Bridge [Aladdin
IV/V/V+]
00:08.0 Bridge: ALi Corporation M7101 Power Management Controller [PMU]
00:0a.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100]
(rev 08)
00:10.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller
(rev 01)
00:11.0 CardBus bridge: Toshiba America Info Systems ToPIC100 PCI to Cardbus
Bridge with ZV Support (rev 32)
00:11.1 CardBus bridge: Toshiba America Info Systems ToPIC100 PCI to Cardbus
Bridge with ZV Support (rev 32)
00:12.0 System peripheral: Toshiba America Info Systems SD TypA Controller
(rev 03)
01:00.0 VGA compatible controller: Trident Microsystems CyberBlade XPAi1 (rev
82)
{pts/0}% lsmod
Module Size Used by
snd_seq_dummy 3556 0
snd_seq_oss32176 0
snd_seq_midi_event 7496 1 snd_seq_oss
snd_seq50808 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 8180 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss43168 0
snd_mixer_oss 16104 1 snd_pcm_oss
snd_ali545123644 0
snd_ac97_codec 97116 1 snd_ali5451
snd_pcm79564 3 snd_pcm_oss,snd_ali5451,snd_ac97_codec
snd_timer 23164 2 snd_seq,snd_pcm
snd_page_alloc 9832 1 snd_pcm
snd53956 9
snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_ali5451,snd_ac97_codec,snd_pcm,snd_timer
soundcore 7776 1 snd
e100 35968 0
mii 5472 1 e100
nls_iso8859_1 3968 0
nls_cp866 5056 0
vfat 12672 0
fat52436 1 vfat
sg 35716 0
usb_storage78816 0
bluetooth 54916 0
autofs421524 0
af_packet 21872 4
ac97_bus2496 1 snd_ac97_codec
smsc_ircc2 17828 0
irnet 24532 0
ppp_generic29188 1 irnet
slhc6624 1 ppp_generic
irtty_sir 6016 0
sir_dev14476 1 irtty_sir
ircomm_tty 24784 0
ircomm 13828 1 ircomm_tty
irda 119528 5 smsc_ircc2,irnet,sir_dev,ircomm_tty,ircomm
crc_ccitt 1984 1 irda
binfmt_misc12072 1
loop 16504 0
dm_mod 58452 0
video 15460 0
toshiba_acpi6328 0
backlight 6176 1 toshiba_acpi
thermal13704 0
sbs14840 0
processor 23372 1 thermal
i2c_ec 4704 1 sbs
i2c_core 22608 1 i2c_ec
fan 4516 0
container 4160 0
button 7632 0
battery 9604 0
ac 4900 0
wlags49_h1_cs 181844 1
pcmcia 38496 1 wlags49_h1_cs
firmware_class 9728 1 pcmcia
yenta_socket 26764 5
tsdev 7648 0
mousedev 11752 1
evdev 9952 2
rsrc_nonstatic 11456 1 yenta_socket
pcmcia_core40344 3 pcmcia,yenta_socket,rsrc_nonstatic
ali_agp 6976 1
agpgart32068 1 ali_agp
nvram 8904 0
toshiba 4472 0
psmouse38472 0
Re: [linux-usb-devel] [PATCH] OHCI: disallow autostop when wakeup is not available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 04 January 2007 00:50, David Brownell wrote: On Tuesday 02 January 2007 7:16 am, Alan Stern wrote: On Mon, 1 Jan 2007, Andrey Borzenkov wrote: Is the original problem (OHCI constantly attempting and failing to suspend root hub) supposed to be fixed in 2.6.20? No. It can't be fixed in the kernel because it is a hardware bug. I'm curious though: did older kernels, say 2.6.18, have such issues? Yes. It is hardware problem all right. [...] Not just that ... it also fixed the problem where quirk entries saying don't even try using remote wakeup stopped working. Exactly. I am sorry for being unclear - actually the question was, whether quirks are implemented in 2.6.20 (because I remember them being mentioned before). Once some pending PPC-related OHCI patches merge (support for PS3 and other CELL systems), there will be infrastructure that makes it easier to add quirk entries that say this board can't do remote wakeup properly. At that point, we can start to collect quirks for boards like this one. OK so this answers the question - it is not yet being implemented. thank you - -andrey -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFnMQ1R6LMutpd94wRAqayAKDQrqfpERc4F5LjqWMQgI6oxqqOmACdH++H r6aDgoAQDw2SHRq+2yLaoyw= =95Oh -END PGP SIGNATURE- - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ 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] OHCI: disallow autostop when wakeup is not available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 15 November 2006 00:28, Alan Stern wrote: This patch (as822) prevents the OHCI autostop mechanism from kicking in if the root hub is not able or not allowed to issue wakeup requests. Signed-off-by: Alan Stern [EMAIL PROTECTED] --- Greg: This patch should go into 2.6.19-rc ASAP. It does solve a real problem. The larger-scale changes Dave and I have been discussing will be submitted separately, for inclusion in 2.6.20. Is the original problem (OHCI constantly attempting and failing to suspend root hub) supposed to be fixed in 2.6.20? Currently in rc3 I have ohci_hcd :00:02.0: new USB bus registered, assigned bus number 1 ohci_hcd :00:02.0: created debug files ohci_hcd :00:02.0: irq 11, io mem 0xf7eff000 ohci_hcd :00:02.0: resetting from state 'reset', control = 0x0 ohci_hcd :00:02.0: enabling initreset quirk ohci_hcd :00:02.0: OHCI controller state ohci_hcd :00:02.0: OHCI 1.0, NO legacy support registers ohci_hcd :00:02.0: control 0x083 HCFS=operational CBSR=3 ohci_hcd :00:02.0: cmdstatus 0x0 SOC=0 ohci_hcd :00:02.0: intrstatus 0x0044 RHSC SF ohci_hcd :00:02.0: intrenable 0x800a MIE RD WDH ohci_hcd :00:02.0: hcca frame #0003 ohci_hcd :00:02.0: roothub.a 01000203 POTPGT=1 NPS NDP=3(3) ohci_hcd :00:02.0: roothub.b PPCM= DR= ohci_hcd :00:02.0: roothub.status 8000 DRWE ohci_hcd :00:02.0: roothub.portstatus [0] 0x0100 PPS ohci_hcd :00:02.0: roothub.portstatus [1] 0x0100 PPS ohci_hcd :00:02.0: roothub.portstatus [2] 0x0100 PPS usb usb1: default language 0x0409 usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1 usb usb1: Product: OHCI Host Controller usb usb1: Manufacturer: Linux 2.6.20-rc3-1avb ohci_hcd usb usb1: SerialNumber: :00:02.0 usb usb1: uevent usb usb1: usb_probe_device usb usb1: configuration #1 chosen from 1 choice usb usb1: adding 1-0:1.0 (config #1, interface 0) usb 1-0:1.0: uevent hub 1-0:1.0: usb_probe_interface hub 1-0:1.0: usb_probe_interface - got id hub 1-0:1.0: USB hub found hub 1-0:1.0: 3 ports detected hub 1-0:1.0: standalone hub hub 1-0:1.0: no power switching (usb 1.0) hub 1-0:1.0: global over-current protection hub 1-0:1.0: power on to power good time: 2ms hub 1-0:1.0: local power source is good hub 1-0:1.0: no over-current condition exists hub 1-0:1.0: trying to enable port power on non-switchable hub hub 1-0:1.0: state 7 ports 3 chg evt /home/bor/src/linux-git/drivers/usb/core/inode.c: creating file '001' ohci_hcd :00:02.0: auto-stop root hub ohci_hcd :00:02.0: auto-wakeup root hub ohci_hcd :00:02.0: auto-stop root hub ohci_hcd :00:02.0: auto-wakeup root hub ... and it goes on and on until I stop it manually by usual method: usb usb1: remote wakeup needed for autosuspend Welcome to new year :) - -andrey -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFmT/oR6LMutpd94wRAtqLAJ4yNCupGqAC8G6hkAxvuXrW7Jr7KQCgrgyE ZZ5Sd4qeeVy+NiGHjNZ6yR8= =Gwng -END PGP SIGNATURE- - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ 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] 2.6.19-rc5: modular USB rebuilds vmlinux?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I was under impression that I have fully modular USB. Still:
{pts/1}% make -C ~/src/linux-git O=$HOME/build/linux-2.6.19
make: Entering directory `/home/bor/src/linux-git'
GEN /home/bor/build/linux-2.6.19/Makefile
scripts/kconfig/conf -s arch/i386/Kconfig
Using /home/bor/src/linux-git as source for kernel
GEN /home/bor/build/linux-2.6.19/Makefile
CHK include/linux/version.h
CHK include/linux/utsrelease.h
CHK include/linux/compile.h
CC [M] drivers/usb/core/usb.o
CC [M] drivers/usb/core/hub.o
CC [M] drivers/usb/core/hcd.o
CC [M] drivers/usb/core/urb.o
CC [M] drivers/usb/core/message.o
CC [M] drivers/usb/core/driver.o
CC [M] drivers/usb/core/config.o
CC [M] drivers/usb/core/file.o
CC [M] drivers/usb/core/buffer.o
CC [M] drivers/usb/core/sysfs.o
CC [M] drivers/usb/core/endpoint.o
CC [M] drivers/usb/core/devio.o
CC [M] drivers/usb/core/notify.o
CC [M] drivers/usb/core/generic.o
CC [M] drivers/usb/core/hcd-pci.o
CC [M] drivers/usb/core/inode.o
CC [M] drivers/usb/core/devices.o
LD [M] drivers/usb/core/usbcore.o
CC drivers/usb/host/pci-quirks.o
LD drivers/usb/host/built-in.o
Sorry? How comes it still compiles something into main kernel?
{pts/0}% grep USB build/linux-2.6.19/.config | grep -v '^#'
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=m
CONFIG_USB_DEBUG=y
CONFIG_USB_DEVICEFS=y
CONFIG_USB_BANDWIDTH=y
CONFIG_USB_DYNAMIC_MINORS=y
CONFIG_USB_SUSPEND=y
CONFIG_USB_OHCI_HCD=m
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_ACM=m
CONFIG_USB_PRINTER=m
CONFIG_USB_STORAGE=m
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_ISD200=y
CONFIG_USB_STORAGE_DPCM=y
CONFIG_USB_STORAGE_USBAT=y
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y
CONFIG_USB_KBD=m
CONFIG_USB_MOUSE=m
CONFIG_USB_SERIAL=m
CONFIG_USB_SERIAL_GENERIC=y
CONFIG_USB_SERIAL_PL2303=m
- -andrey
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFZJrnR6LMutpd94wRAh3DAJ97nMrIHG3pG4ZBaB8b6svZNm/39ACgt4Yd
19FExn1dKtTtFtyriNpP9dU=
=q9YV
-END PGP SIGNATURE-
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
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] 2.6.19-rc5: modular USB rebuilds vmlinux?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 22 November 2006 21:54, Randy Dunlap wrote:
On Wed, 22 Nov 2006 21:45:55 +0300 Andrey Borzenkov wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I was under impression that I have fully modular USB. Still:
{pts/1}% make -C ~/src/linux-git O=$HOME/build/linux-2.6.19
make: Entering directory `/home/bor/src/linux-git'
GEN /home/bor/build/linux-2.6.19/Makefile
scripts/kconfig/conf -s arch/i386/Kconfig
Using /home/bor/src/linux-git as source for kernel
GEN /home/bor/build/linux-2.6.19/Makefile
CHK include/linux/version.h
CHK include/linux/utsrelease.h
CHK include/linux/compile.h
CC [M] drivers/usb/core/usb.o
CC [M] drivers/usb/core/hub.o
CC [M] drivers/usb/core/hcd.o
CC [M] drivers/usb/core/urb.o
CC [M] drivers/usb/core/message.o
CC [M] drivers/usb/core/driver.o
CC [M] drivers/usb/core/config.o
CC [M] drivers/usb/core/file.o
CC [M] drivers/usb/core/buffer.o
CC [M] drivers/usb/core/sysfs.o
CC [M] drivers/usb/core/endpoint.o
CC [M] drivers/usb/core/devio.o
CC [M] drivers/usb/core/notify.o
CC [M] drivers/usb/core/generic.o
CC [M] drivers/usb/core/hcd-pci.o
CC [M] drivers/usb/core/inode.o
CC [M] drivers/usb/core/devices.o
LD [M] drivers/usb/core/usbcore.o
CC drivers/usb/host/pci-quirks.o
LD drivers/usb/host/built-in.o
Sorry? How comes it still compiles something into main kernel?
It's just a quirk of the build machinery.
The built-in.o file should be 8 bytes or so, with nothing
really in it.
yes, but it still costs extra vmlinuz build when just to rebuild of a single
module (or subsystem as was in this case) is needed. And this implies also
reboot - how should one know if this is safe to leave current kernel with new
modules?
{pts/0}% grep USB build/linux-2.6.19/.config | grep -v '^#'
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=m
CONFIG_USB_DEBUG=y
CONFIG_USB_DEVICEFS=y
CONFIG_USB_BANDWIDTH=y
CONFIG_USB_DYNAMIC_MINORS=y
CONFIG_USB_SUSPEND=y
CONFIG_USB_OHCI_HCD=m
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_ACM=m
CONFIG_USB_PRINTER=m
CONFIG_USB_STORAGE=m
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_ISD200=y
CONFIG_USB_STORAGE_DPCM=y
CONFIG_USB_STORAGE_USBAT=y
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y
CONFIG_USB_KBD=m
CONFIG_USB_MOUSE=m
CONFIG_USB_SERIAL=m
CONFIG_USB_SERIAL_GENERIC=y
CONFIG_USB_SERIAL_PL2303=m
---
~Randy
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFZKEsR6LMutpd94wRAugsAJ9aGrMgXmRXwSHPsg7CVPHXLUSc2QCdFoij
akMXiiVn6VJJ653qvL8w0f8=
=qvQ4
-END PGP SIGNATURE-
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
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] 2.6.19-rc5: possible regression - OHCI dead after several STD/resume cycles
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Using 2.6.9-rc5 + Alan Stern fix for can't disable OHCI wakeup via sysfs. I
started noticing strange messages after resume:
ACPI: PCI Interrupt :00:06.0[A] - Link [LNKH] - GSI 11 (level, low) -
IRQ 11
ACPI: PCI interrupt for device :00:06.0 disabled
ACPI: PCI interrupt for device :00:0a.0 disabled
pccard: card ejected from slot 0
Stopping tasks...
===done.
Shrinking memory... done (27344 pages freed)
Suspending console(s)
usbdev1.1_ep81: PM: suspend 0-1, parent 1-0:1.0 already 1
hub 1-0:1.0: PM: suspend 1-1, parent usb1 already 1
usbdev1.1_ep00: PM: suspend 0-1, parent usb1 already 1
usb usb1: PM: suspend 1-1, parent :00:02.0 already 2
ACPI: PCI interrupt for device :00:11.1 disabled
ACPI: PCI interrupt for device :00:11.0 disabled
ACPI: PCI interrupt for device :00:10.0 disabled
swsusp: Need to copy 58705 pages
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
ACPI: Transitioning device [FAN] to D3
ACPI: Transitioning device [FAN] to D3
PCI: Setting latency timer of device :00:01.0 to 64
PM: Writing back config space on device :00:06.0 at offset 1 (was
c297, writing c293)
PM: Writing back config space on device :00:0a.0 at offset 1 (was 297,
writing 293)
PM: Writing back config space on device :00:10.0 at offset f (was 34001ff,
writing 5c001ff)
PM: Writing back config space on device :00:10.0 at offset 3 (was 24008,
writing 2a808)
ACPI: PCI Interrupt :00:10.0[A] - Link [LNKC] - GSI 11 (level, low) -
IRQ 11
pccard: PCMCIA card inserted into slot 0
pcmcia: registering new device pcmcia0.0
eth0: PRI 31 variant 2 version 9.48
eth0: NIC 5 variant 2 version 1.02
eth0: Wireless, io_addr 0x100, irq 11, mac_address 00:02:2D:26:95:6C
PM: Writing back config space on device :00:11.0 at offset f (was 10001ff,
writing 58001ff)
PM: Writing back config space on device :00:11.0 at offset 3 (was 824000,
writing 82a800)
ACPI: PCI Interrupt :00:11.0[A] - Link [LNKA] - GSI 11 (level, low) -
IRQ 11
PM: Writing back config space on device :00:11.1 at offset f (was 10002ff,
writing 58002ff)
PM: Writing back config space on device :00:11.1 at offset 3 (was 824000,
writing 82a800)
ACPI: PCI Interrupt :00:11.1[B] - Link [LNKB] - GSI 11 (level, low) -
IRQ 11
pnp: Failed to activate device 00:05.
pnp: Failed to activate device 00:06.
usbdev1.1_ep00: PM: resume from 0, parent usb1 still 1
usbdev1.1_ep81: PM: resume from 0, parent 1-0:1.0 still 1
Restarting tasks... done.
those strange are usbdev1.1_ep00/81.
Now I needed to read from USB stick - it was not detected. Actually even HUB
itself has not been shown in lsusb output. Reloading ohci did fix it.
This never happend to me in all previous versions (since 2.6.15 I guess). Also
it did not start immediately after Alan's patch so I do not believe it is
related.
Please tell me what can I sensibly test and which input info should I collect.
Thank you. Configuration, dmesg etc available on request. lspci:
{pts/2}% lspci
00:00.0 Host bridge: ALi Corporation M1644/M1644T Northbridge+Trident (rev 01)
00:01.0 PCI bridge: ALi Corporation PCI to AGP Controller
00:02.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:04.0 IDE interface: ALi Corporation M5229 IDE (rev c3)
00:06.0 Multimedia audio controller: ALi Corporation M5451 PCI AC-Link
Controller Audio Device (rev 01)
00:07.0 ISA bridge: ALi Corporation M1533/M1535 PCI to ISA Bridge [Aladdin
IV/V/V+]
00:08.0 Bridge: ALi Corporation M7101 Power Management Controller [PMU]
00:0a.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100]
(rev 08)
00:10.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller
(rev 01)
00:11.0 CardBus bridge: Toshiba America Info Systems ToPIC100 PCI to Cardbus
Bridge with ZV Support (rev 32)
00:11.1 CardBus bridge: Toshiba America Info Systems ToPIC100 PCI to Cardbus
Bridge with ZV Support (rev 32)
00:12.0 System peripheral: Toshiba America Info Systems SD TypA Controller
(rev 03)
01:00.0 VGA compatible controller: Trident Microsystems CyberBlade XPAi1 (rev
82)
- -andrey
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFY0CcR6LMutpd94wRAgkQAJ47iMkbfXcS+W3DLuYbQcVNBQwnhwCfZbNc
SO8/36kh+XNDWh5miWt5oLo=
=6Nk7
-END PGP SIGNATURE-
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
Re: [linux-usb-devel] 2.6.19-rc5 regression: can't disable OHCI wakeup via sysfs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 13 November 2006 22:58, Alan Stern wrote: Andrey: Try this patch for 2.6.19-rc5. Although it doesn't make all the changes Dave and I have discussed, it ought to fix your problem. It did. Thank you - -andrey Alan Stern Index: 2.6.19-rc5/drivers/usb/host/ohci-hub.c === --- 2.6.19-rc5.orig/drivers/usb/host/ohci-hub.c +++ 2.6.19-rc5/drivers/usb/host/ohci-hub.c @@ -422,7 +422,8 @@ ohci_hub_status_data (struct usb_hcd *hc ohci-autostop = 0; ohci-next_statechange = jiffies + STATECHANGE_DELAY; - } else if (time_after_eq (jiffies, + } else if (device_may_wakeup(hcd-self.root_hub-dev) + time_after_eq(jiffies, ohci-next_statechange) !ohci-ed_rm_list !(ohci-hc_control -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFWiueR6LMutpd94wRAu9JAKC/IXuGi+NvXx+O9zwDwaJI3AXqXQCfTF/I jzkfD8gsU+JgYlqWkzQ2Pis= =ckCE -END PGP SIGNATURE- - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ 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] 2.6.17: dmesg flooded with ohci_hcd 0000:00:02.0: wakeup
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 18 June 2006 22:16, David Brownell wrote: On Sunday 18 June 2006 10:29 am, Andrey Borzenkov wrote: On Sunday 18 June 2006 20:29, David Brownell wrote: An alternative (but post-boot) workaround _should_ be echo disabled /sys/bus/pci/devices/:00:02.0/power/wakeup Did that work? This is Tohiba Portege 4000 notebook. So far I did not have any USB related issues at least since 2.6.12. And true, I do not have any devices plugged in. It's the usual case of fixing one bug triggering another, in your case because the fix ran into a previously unseen hardware bug. One other way to work around that bug would be disabling CONFIG_PM, but I suspect you don't want to go that route... Here you are. I am still puzzled where all these suspends come from - I did not try any suspend in the meantime ... It's the driver putting the controller into a low power state. Your hardware seems to have a bug whereby that doesn't work correctly, making it immediately leave that state. (And the driver messaging is fine for what should be an uncommon event; plus it highlighted your hardware bug.) Notice the initreset quirk message -- another bug in that hardware. Workarounds in both cases are simple. When I get a moment, I'll have a patch for you to try. Meanwhile, either workaround I showed above should prevent the attempt to enter that low power mode. this still happens in 2.6.19-rc5 too. In the meantime I have observed that those messages appear after warm reboot (i.e. just reboot from running system) but booting from poweroff state (or resuming) does not show those messages. I am still interested in said patch :) - -andrey - Dave ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI) ohci_hcd: block sizes: ed 64 td 64 ACPI: PCI Interrupt Link [LNKG] enabled at IRQ 11 ACPI: PCI Interrupt :00:02.0[A] - Link [LNKG] - GSI 11 (level, low) - IRQ 11 ohci_hcd :00:02.0: OHCI Host Controller /home/bor/src/linux-git/drivers/usb/core/inode.c: creating file 'devices' /home/bor/src/linux-git/drivers/usb/core/inode.c: creating file '001' ohci_hcd :00:02.0: new USB bus registered, assigned bus number 1 ohci_hcd :00:02.0: created debug files ohci_hcd :00:02.0: irq 11, io mem 0xf7eff000 ohci_hcd :00:02.0: resetting from state 'reset', control = 0x0 ohci_hcd :00:02.0: enabling initreset quirk ohci_hcd :00:02.0: OHCI controller state ohci_hcd :00:02.0: OHCI 1.0, NO legacy support registers ohci_hcd :00:02.0: control 0x083 HCFS=operational CBSR=3 ohci_hcd :00:02.0: cmdstatus 0x0 SOC=0 ohci_hcd :00:02.0: intrstatus 0x0044 RHSC SF ohci_hcd :00:02.0: intrenable 0x800a MIE RD WDH ohci_hcd :00:02.0: hcca frame #0003 ohci_hcd :00:02.0: roothub.a 01000203 POTPGT=1 NPS NDP=3(3) ohci_hcd :00:02.0: roothub.b PPCM= DR= ohci_hcd :00:02.0: roothub.status 8000 DRWE ohci_hcd :00:02.0: roothub.portstatus [0] 0x0100 PPS ohci_hcd :00:02.0: roothub.portstatus [1] 0x0100 PPS ohci_hcd :00:02.0: roothub.portstatus [2] 0x0100 PPS usb usb1: default language 0x0409 usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1 usb usb1: Product: OHCI Host Controller usb usb1: Manufacturer: Linux 2.6.17-2avb ohci_hcd usb usb1: SerialNumber: :00:02.0 usb usb1: uevent usb usb1: configuration #1 chosen from 1 choice usb usb1: adding 1-0:1.0 (config #1, interface 0) usb 1-0:1.0: uevent hub 1-0:1.0: usb_probe_interface hub 1-0:1.0: usb_probe_interface - got id hub 1-0:1.0: USB hub found hub 1-0:1.0: 3 ports detected hub 1-0:1.0: standalone hub hub 1-0:1.0: no power switching (usb 1.0) hub 1-0:1.0: global over-current protection hub 1-0:1.0: power on to power good time: 2ms hub 1-0:1.0: local power source is good hub 1-0:1.0: no over-current condition exists hub 1-0:1.0: state 7 ports 3 chg evt /home/bor/src/linux-git/drivers/usb/core/inode.c: creating file '001' ohci_hcd :00:02.0: suspend root hub hub 1-0:1.0: state 7 ports 3 chg evt , resume root hub 1-0:1.0: state 7 ports 3 chg evt ohci_hcd :00:02.0: suspend root hub hub 1-0:1.0: state 7 ports 3 chg evt , resume root hub 1-0:1.0: state 7 ports 3 chg evt ohci_hcd :00:02.0: suspend root hub hub 1-0:1.0: state 7 ports 3 chg evt , resume root hub 1-0:1.0: state 7 ports 3 chg evt ohci_hcd :00:02.0: suspend root hub etc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFVbOmR6LMutpd94wRAqvhAKCtwi//xhbzR3VtHBjoMTARMd2Q6wCgnZPe 4alxU15SVFHqaenCagCp89E= =NwAB -END PGP SIGNATURE- - Using Tomcat but need to do more? Need to support web services, security? Get stuff done
[linux-usb-devel] 2.6.19-rc5 regression: can't disable OHCI wakeup via sysfs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 20 June 2006 00:12, David Brownell wrote: An alternative (but post-boot) workaround _should_ be echo disabled /sys/bus/pci/devices/:00:02.0/power/wakeup Did that work? No. But echo -n disabled /sys/devices/pci:00/:00:02.0/usb1/power/wakeup That's what I meant ... thanks, and sorry for the confusion. this does not work anymore in current rc5. After writing cat /sys/devices/pci:00/:00:02.0/usb1/power/wakeup shows disabled but messages continue to be logged. Anything I can do to help narrow it down? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFVbQ0R6LMutpd94wRApCwAKCDLKVxGWlE8vyf8sH42wU2RBVxHQCgl0rl 4vRC3bgKflRGboCrzF8YnJY= =nuLl -END PGP SIGNATURE- - 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
[linux-usb-devel] 2.6.18.2: lockdep warnings on rmmod ohci_hcd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I presume this is lockdep; this looks initially truncated, unfortunately this is how it was stored in messages. I will try to get more complete output ig required. - -andrey bor : TTY=pts/1 ; PWD=/tmp ; USER=root ; COMMAND=/sbin/rmmod ohci_hcd +0x5d/0x360 [] 0x0 in-hardirq-W at: [lock_acquire+93/128] lock_acquire+0x5d/0x80 [c0133ccd] lock_acquire+0x5d/0x80 [_spin_lock+44/64] _spin_lock+0x2c/0x40 [c02aedec] _spin_lock+0x2c/0x40 [scheduler_tick+199/768] scheduler_tick+0xc7/0x300 [c0115557] scheduler_tick+0xc7/0x300 [update_process_times+70/112] update_process_times+0x46/0x70 [c0123206] update_process_times+0x46/0x70 [timer_interrupt+65/160] timer_interrupt+0x41/0xa0 [c01067b1] timer_interrupt+0x41/0xa0 [handle_IRQ_event+51/112] handle_IRQ_event+0x33/0x70 [c0146d43] handle_IRQ_event+0x33/0x70 [__do_IRQ+137/272] __do_IRQ+0x89/0x110 [c0146e09] __do_IRQ+0x89/0x110 [do_IRQ+72/160] do_IRQ+0x48/0xa0 [c01054b8] do_IRQ+0x48/0xa0 [common_interrupt+37/44] common_interrupt+0x25/0x2c [c0103a75] common_interrupt+0x25/0x2c [printk+27/32] printk+0x1b/0x20 [c011a0bb] printk+0x1b/0x20 [populate_rootfs+65/256] populate_rootfs+0x41/0x100 [c03bc191] populate_rootfs+0x41/0x100 [init+53/656] init+0x35/0x290 [c01002b5] init+0x35/0x290 [kernel_thread_helper+5/16] kernel_thread_helper+0x5/0x10 [c0101005] kernel_thread_helper+0x5/0x10 in-softirq-W at: [lock_acquire+93/128] lock_acquire+0x5d/0x80 [c0133ccd] lock_acquire+0x5d/0x80 [_spin_lock+44/64] _spin_lock+0x2c/0x40 [c02aedec] _spin_lock+0x2c/0x40 [task_rq_lock+23/32] task_rq_lock+0x17/0x20 [c0115ad7] task_rq_lock+0x17/0x20 [try_to_wake_up+32/288] try_to_wake_up+0x20/0x120 [c0115c20] try_to_wake_up+0x20/0x120 [default_wake_function+11/16] default_wake_function+0xb/0x10 [c0115d2b] default_wake_function+0xb/0x10 [__wake_up_common+57/112] __wake_up_common+0x39/0x70 [c0114dc9] __wake_up_common+0x39/0x70 [complete+61/96] complete+0x3d/0x60 [c01151bd] complete+0x3d/0x60 [wakeme_after_rcu+11/16] wakeme_after_rcu+0xb/0x10 [c012a74b] wakeme_after_rcu+0xb/0x10 [__rcu_process_callbacks+105/448] __rcu_process_callbacks+0x69/0x1c0 [c012a8e9] __rcu_process_callbacks+0x69/0x1c0 [rcu_process_callbacks+18/48] rcu_process_callbacks+0x12/0x30 [c012aa52] rcu_process_callbacks+0x12/0x30 [tasklet_action+64/144] tasklet_action+0x40/0x90 [c011e880] tasklet_action+0x40/0x90 [__do_softirq+85/192] __do_softirq+0x55/0xc0 [c011e785] __do_softirq+0x55/0xc0 [do_softirq+70/80] do_softirq+0x46/0x50 [c011e836] do_softirq+0x46/0x50 [irq_exit+53/64] irq_exit+0x35/0x40 [c011ec65] irq_exit+0x35/0x40 [do_IRQ+77/160] do_IRQ+0x4d/0xa0 [c01054bd] do_IRQ+0x4d/0xa0 [common_interrupt+37/44] common_interrupt+0x25/0x2c [c0103a75] common_interrupt+0x25/0x2c [cpu_idle+57/80] cpu_idle+0x39/0x50 [c0101c59] cpu_idle+0x39/0x50 [rest_init+30/48] rest_init+0x1e/0x30 [c010052e] rest_init+0x1e/0x30 [start_kernel+691/864]
Re: [linux-usb-devel] 2.6.18.2: lockdep warnings on rmmod ohci_hcd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 06 November 2006 17:18, Arjan van de Ven wrote: On Mon, 2006-11-06 at 15:46 +0300, Andrey Borzenkov wrote: I presume this is lockdep; this looks initially truncated, unfortunately this is how it was stored in messages. I will try to get more complete output ig required. the interesting bits are missing unfortunately (the first 10 lines or so). Also this will be in dmesg if your system actually survives... well, dmesg had exactly the same contents. Here full dmesg with increased LOG_SHIFT. Linux version 2.6.18.2-1avb ([EMAIL PROTECTED]) (gcc version 4.1.1 20060724 (prerelease) (4.1.1-3mdk)) #9 Mon Nov 6 18:22:22 MSK 2006 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000e - 000eee00 (reserved) BIOS-e820: 000eee00 - 000ef000 (ACPI NVS) BIOS-e820: 000ef000 - 0010 (reserved) BIOS-e820: 0010 - 1ef6 (usable) BIOS-e820: 1ef6 - 1ef7 (ACPI data) BIOS-e820: 1ef7 - 2000 (reserved) BIOS-e820: fff8 - 0001 (reserved) 495MB LOWMEM available. On node 0 totalpages: 126816 DMA zone: 4096 pages, LIFO batch:0 Normal zone: 122720 pages, LIFO batch:31 DMI 2.3 present. ACPI: RSDP (v000 TOSHIB) @ 0x000f0090 ACPI: RSDT (v001 TOSHIB 750 0x00970814 TASM 0x0401) @ 0x1ef6 ACPI: FADT (v002 TOSHIB 750 0x00970814 TASM 0x0401) @ 0x1ef60054 ACPI: DSDT (v001 TOSHIB 4000 0x20020417 MSFT 0x010a) @ 0x ACPI: PM-Timer IO Port: 0xee08 Allocating PCI resources starting at 3000 (gap: 2000:dff8) Detected 747.771 MHz processor. Built 1 zonelists. Total pages: 126816 Kernel command line: root=/dev/hda2 BOOT_IMAGE=2.6.18.2-1avb-dmesg hdc=ide-cd resume=/dev/hda1 splash=silent vga=791 1 Local APIC disabled by BIOS -- you can enable it with lapic mapped APIC to d000 (013e7000) Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 2048 (order: 11, 8192 bytes) Console: colour dummy device 80x25 Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar ... MAX_LOCKDEP_SUBCLASSES:8 ... MAX_LOCK_DEPTH: 30 ... MAX_LOCKDEP_KEYS:2048 ... CLASSHASH_SIZE: 1024 ... MAX_LOCKDEP_ENTRIES: 8192 ... MAX_LOCKDEP_CHAINS: 8192 ... CHAINHASH_SIZE: 4096 memory used by lock dependency info: 696 kB per task-struct memory footprint: 1200 bytes Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 496628k/507264k available (1735k kernel code, 10056k reserved, 758k data, 184k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 1497.13 BogoMIPS (lpj=748565) Mount-cache hash table entries: 512 CPU: After generic identify, caps: 0383f9ff CPU: After vendor identify, caps: 0383f9ff CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 256K CPU: After all inits, caps: 0383f9ff 0040 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU: Intel Pentium III (Coppermine) stepping 0a Checking 'hlt' instruction... OK. ACPI: Core revision 20060707 ACPI: setting ELCR to 0200 (from 0a00) checking if image is initramfs... it is Freeing initrd memory: 648k freed NET: Registered protocol family 16 ACPI: bus type pci registered PCI: PCI BIOS revision 2.10 entry at 0xfe5ae, last bus=5 PCI: Using configuration type 1 Setting up standard PCI resources ACPI: Interpreter enabled ACPI: Using PIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (:00) PCI: Probing PCI hardware (bus 00) ACPI: Assume root bridge [\_SB_.PCI0] bus is 0 PCI quirk: region ee00-ee3f claimed by ali7101 ACPI PCI quirk: region ef00-ef1f claimed by ali7101 SMB Boot video device is :01:00.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 *11) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 *11) ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 *11) ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 *11) ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT] ACPI: Power Resource [PFAN] (off) Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init pnp: PnP ACPI: found 12 devices PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try pci=routeirq. If it helps, post a report PCI: Bridge
Re: [linux-usb-devel] 2.6.18.2: lockdep warnings on rmmod ohci_hcd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 06 November 2006 19:16, Alan Stern wrote: On Mon, 6 Nov 2006, Andrey Borzenkov wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 06 November 2006 17:18, Arjan van de Ven wrote: On Mon, 2006-11-06 at 15:46 +0300, Andrey Borzenkov wrote: I presume this is lockdep; this looks initially truncated, unfortunately this is how it was stored in messages. I will try to get more complete output ig required. the interesting bits are missing unfortunately (the first 10 lines or so). Also this will be in dmesg if your system actually survives... well, dmesg had exactly the same contents. Here full dmesg with increased LOG_SHIFT. I always find it rather difficult to understand the meaning of lockdep warnings, but this looks a bug that was fixed in 2.6.19-rc1. The patch that fixed it is here: http://marc.theaimsgroup.com/?l=linux-usb-develm=115938807428103w=2 Yes, it has fixed it. Thank you - -andrey -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFT2QzR6LMutpd94wRAh4OAKCZHqj/W3aFgEiXp3puPLhur5Rb9ACff67R oIpIdzM5pMypaqCajAbWLW4= =yHf7 -END PGP SIGNATURE- - 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] 2.6.17: dmesg flooded with ohci_hcd 0000:00:02.0: wakeup
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 18 June 2006 22:16, David Brownell wrote: On Sunday 18 June 2006 10:29 am, Andrey Borzenkov wrote: On Sunday 18 June 2006 20:29, David Brownell wrote: An alternative (but post-boot) workaround _should_ be echo disabled /sys/bus/pci/devices/:00:02.0/power/wakeup Did that work? This is Tohiba Portege 4000 notebook. So far I did not have any USB related issues at least since 2.6.12. And true, I do not have any devices plugged in. It's the usual case of fixing one bug triggering another, in your case because the fix ran into a previously unseen hardware bug. One other way to work around that bug would be disabling CONFIG_PM, but I suspect you don't want to go that route... Here you are. I am still puzzled where all these suspends come from - I did not try any suspend in the meantime ... It's the driver putting the controller into a low power state. Your hardware seems to have a bug whereby that doesn't work correctly, making it immediately leave that state. (And the driver messaging is fine for what should be an uncommon event; plus it highlighted your hardware bug.) Notice the initreset quirk message -- another bug in that hardware. Workarounds in both cases are simple. When I get a moment, I'll have a patch for you to try. Meanwhile, either workaround I showed above should prevent the attempt to enter that low power mode. I updated to 2.6.18 and got the same issue; any patch to try? Thank you - -andrey - Dave ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI) ohci_hcd: block sizes: ed 64 td 64 ACPI: PCI Interrupt Link [LNKG] enabled at IRQ 11 ACPI: PCI Interrupt :00:02.0[A] - Link [LNKG] - GSI 11 (level, low) - IRQ 11 ohci_hcd :00:02.0: OHCI Host Controller /home/bor/src/linux-git/drivers/usb/core/inode.c: creating file 'devices' /home/bor/src/linux-git/drivers/usb/core/inode.c: creating file '001' ohci_hcd :00:02.0: new USB bus registered, assigned bus number 1 ohci_hcd :00:02.0: created debug files ohci_hcd :00:02.0: irq 11, io mem 0xf7eff000 ohci_hcd :00:02.0: resetting from state 'reset', control = 0x0 ohci_hcd :00:02.0: enabling initreset quirk ohci_hcd :00:02.0: OHCI controller state ohci_hcd :00:02.0: OHCI 1.0, NO legacy support registers ohci_hcd :00:02.0: control 0x083 HCFS=operational CBSR=3 ohci_hcd :00:02.0: cmdstatus 0x0 SOC=0 ohci_hcd :00:02.0: intrstatus 0x0044 RHSC SF ohci_hcd :00:02.0: intrenable 0x800a MIE RD WDH ohci_hcd :00:02.0: hcca frame #0003 ohci_hcd :00:02.0: roothub.a 01000203 POTPGT=1 NPS NDP=3(3) ohci_hcd :00:02.0: roothub.b PPCM= DR= ohci_hcd :00:02.0: roothub.status 8000 DRWE ohci_hcd :00:02.0: roothub.portstatus [0] 0x0100 PPS ohci_hcd :00:02.0: roothub.portstatus [1] 0x0100 PPS ohci_hcd :00:02.0: roothub.portstatus [2] 0x0100 PPS usb usb1: default language 0x0409 usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1 usb usb1: Product: OHCI Host Controller usb usb1: Manufacturer: Linux 2.6.17-2avb ohci_hcd usb usb1: SerialNumber: :00:02.0 usb usb1: uevent usb usb1: configuration #1 chosen from 1 choice usb usb1: adding 1-0:1.0 (config #1, interface 0) usb 1-0:1.0: uevent hub 1-0:1.0: usb_probe_interface hub 1-0:1.0: usb_probe_interface - got id hub 1-0:1.0: USB hub found hub 1-0:1.0: 3 ports detected hub 1-0:1.0: standalone hub hub 1-0:1.0: no power switching (usb 1.0) hub 1-0:1.0: global over-current protection hub 1-0:1.0: power on to power good time: 2ms hub 1-0:1.0: local power source is good hub 1-0:1.0: no over-current condition exists hub 1-0:1.0: state 7 ports 3 chg evt /home/bor/src/linux-git/drivers/usb/core/inode.c: creating file '001' ohci_hcd :00:02.0: suspend root hub hub 1-0:1.0: state 7 ports 3 chg evt , resume root hub 1-0:1.0: state 7 ports 3 chg evt ohci_hcd :00:02.0: suspend root hub hub 1-0:1.0: state 7 ports 3 chg evt , resume root hub 1-0:1.0: state 7 ports 3 chg evt ohci_hcd :00:02.0: suspend root hub hub 1-0:1.0: state 7 ports 3 chg evt , resume root hub 1-0:1.0: state 7 ports 3 chg evt ohci_hcd :00:02.0: suspend root hub etc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFFDE4R6LMutpd94wRAjhpAJ4+gsOgdQT8V83QPgbMXa6AVH2WQgCgh4nM V0GQyKHQylBIrFQwcVGcaEs= =dlTM -END PGP SIGNATURE- - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
Re: [linux-usb-devel] 2.6.17: dmesg flooded with ohci_hcd 0000:00:02.0: wakeup
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 18 June 2006 22:16, David Brownell wrote:
On Sunday 18 June 2006 10:29 am, Andrey Borzenkov wrote:
On Sunday 18 June 2006 20:29, David Brownell wrote:
An alternative (but post-boot) workaround _should_ be
echo disabled /sys/bus/pci/devices/:00:02.0/power/wakeup
Did that work?
No. But
echo -n disabled
/sys/devices/pci:00/:00:02.0/usb1/power/wakeup
did.
Now I noticed that when I boot 2.6.16 hub has only 'Self Powered' attribite
(0xc0) while in 2.6.17 it adds 'Remote Wakeup':
Bus 001 Device 001: ID :
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass9 Hub
...
bmAttributes 0xe0
Self Powered
Remote Wakeup
It apparently makes OHCI believe controller can correctly do suspend/wakeup.
The suspend does not come from upper layer - it is ohci_hub itself attempting
to put controller in lower power mode:
ohci_hub_status_data (struct usb_hcd *hcd, char *buf)
{
...
int can_suspend =
device_may_wakeup(hcd-self.root_hub-dev);
...
#ifdef CONFIG_PM
/* save power by suspending idle root hubs;
* INTR_RD wakes us when there's work
*/
if (can_suspend
!changed
!ohci-ed_rm_list
((OHCI_CTRL_HCFS | OHCI_SCHED_ENABLES)
ohci-hc_control)
== OHCI_USB_OPER
time_after (jiffies, ohci-next_statechange)
usb_trylock_device (hcd-self.root_hub) == 0
) {
ohci_vdbg (ohci, autosuspend\n);
(void) ohci_bus_suspend (hcd);
usb_unlock_device (hcd-self.root_hub);
}
#endif
can_suspend is true while it was apparently false in 2.6.16.
- -andrey
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.2 (GNU/Linux)
iD8DBQFElu9JR6LMutpd94wRAv5rAJwO/NZ13duktsD0WsksmFqLtUZufACgkBCS
cOb6y1BG+RjecKtCcua9sNY=
=Rm8d
-END PGP SIGNATURE-
___
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] 2.6.17: dmesg flooded with ohci_hcd 0000:00:02.0: wakeup
usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 3 ports detected ohci_hcd :00:02.0: wakeup ohci_hcd :00:02.0: wakeup ohci_hcd :00:02.0: wakeup ohci_hcd :00:02.0: wakeup ohci_hcd :00:02.0: wakeup ohci_hcd :00:02.0: wakeup Linux agpgart interface v0.101 (c) Dave Jones agpgart: Detected ALi M1644 chipset agpgart: AGP aperture is 64M @ 0xf000 ohci_hcd :00:02.0: wakeup ACPI: PCI Interrupt :00:10.0[A] - Link [LNKC] - GSI 11 (level, low) - IRQ 11 Yenta: CardBus bridge found at :00:10.0 [12a3:ab01] Yenta: Using CSCINT to route CSC interrupts to PCI Yenta: Routing CardBus interrupts to PCI Yenta TI: socket :00:10.0, mfunc 0x0102, devctl 0x60 Yenta: ISA IRQ mask 0x, PCI irq 11 Socket status: 3059 ACPI: PCI Interrupt :00:11.0[A] - Link [LNKA] - GSI 11 (level, low) - IRQ 11 Yenta: CardBus bridge found at :00:11.0 [1179:0001] ohci_hcd :00:02.0: wakeup Yenta: ISA IRQ mask 0x04b8, PCI irq 11 Socket status: 3007 ohci_hcd :00:02.0: wakeup pccard: PCMCIA card inserted into slot 0 ohci_hcd :00:02.0: wakeup cs: memory probe 0x0c-0x0f: excluding 0xc-0xcbfff 0xe-0xf cs: memory probe 0x6000-0x60ff: clean. cs: memory probe 0xa000-0xa0ff: clean. pcmcia: registering new device pcmcia0.0 ACPI: PCI Interrupt :00:11.1[B] - Link [LNKB] - GSI 11 (level, low) - IRQ 11 Yenta: CardBus bridge found at :00:11.1 [1179:0001] wlags49_h1_cs v7.18 for PCMCIA, 03/31/2004 14:31:00 by Agere Systems, http://www.agere.com *** Modified for kernel 2.6 by Andrey Borzenkov [EMAIL PROTECTED] $Revision: 22 $ *** Station Mode (STA) Support: YES *** Access Point Mode (AP) Support: YES ohci_hcd :00:02.0: wakeup eth0: PRI 31 variant 2 version 9.48 eth0: NIC 5 variant 2 version 1.02 eth0: Wireless, io_addr 0x100, irq 11, mac_address 00:02:2D:26:95:6C Yenta: ISA IRQ mask 0x04b8, PCI irq 11 Socket status: 3007 ohci_hcd :00:02.0: wakeup ohci_hcd :00:02.0: wakeup ACPI: AC Adapter [ADP1] (on-line) ACPI: Battery Slot [BAT1] (battery present) ACPI: Battery Slot [BAT2] (battery absent) ACPI: Power Button (FF) [PWRF] ACPI: Lid Switch [LID] ACPI: Fan [FAN] (off) ACPI: CPU0 (power states: C1[C1] C2[C2]) ohci_hcd :00:02.0: wakeup ACPI: Thermal Zone [THRM] (53 C) toshiba_acpi: Toshiba Laptop ACPI Extras version 0.18 toshiba_acpi: HCI method: \_SB_.VALD.GHCI ACPI: Video Device [VGA] (multi-head: yes rom: yes post: no) ohci_hcd :00:02.0: wakeup ohci_hcd :00:02.0: wakeup ohci_hcd :00:02.0: wakeup Adding 500432k swap on /dev/hda1. Priority:-1 extents:1 across:500432k ohci_hcd :00:02.0: wakeup ohci_hcd :00:02.0: wakeup ohci_hcd :00:02.0: wakeup loop: loaded (max 8 devices) ohci_hcd :00:02.0: wakeup ohci_hcd :00:02.0: wakeup ohci_hcd :00:02.0: wakeup ohci_hcd :00:02.0: wakeup ohci_hcd :00:02.0: wakeup ohci_hcd :00:02.0: wakeup ohci_hcd :00:02.0: wakeup hdc: ATAPI 24X DVD-ROM drive, 128kB Cache, UDMA(33) Uniform CD-ROM driver Revision: 3.20 ohci_hcd :00:02.0: wakeup ohci_hcd :00:02.0: wakeup -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFElW8WR6LMutpd94wRApdPAJ45BIDoOzPab3YncJ1MXO0RWyHZeQCfSyli LqZY+QERkJQBKtw/Qr/w5Xg= =nQS6 -END PGP SIGNATURE- ___ 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] 2.6.17: dmesg flooded with ohci_hcd 0000:00:02.0: wakeup
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 18 June 2006 20:29, David Brownell wrote: On Sunday 18 June 2006 8:19 am, Andrey Borzenkov wrote: After reboot with 2.6.17 dmesg is overflowed with the above. 2.6.16.20 was OK. Please let me know what additional information may be useful; for now I simply commented out this printk. dmesg, lsusb and lspci follow. The printk means you're getting more IRQs than would be good. Did you apply any patches to this, e.g. from the MM tree? no. An alternative (but post-boot) workaround _should_ be echo disabled /sys/bus/pci/devices/:00:02.0/power/wakeup Looks like this is an old ALI-based motherboard with only one USB controller; this might be a hardware problem, some others from that era had problems handling USB suspend states. In your case (no USB devices hooked up here, right?) maybe this problem can be automagically detected and worked around. This is Tohiba Portege 4000 notebook. So far I did not have any USB related issues at least since 2.6.12. And true, I do not have any devices plugged in. What would be most useful in this case -- and is ISTR one of the FAQs for how to report USB problems -- is rebuilding with CONFIG_USB_DEBUG and sending the boot log, so I can see how that OHCI controller comes up in more detail than you've provided here. Here you are. I am still puzzled where all these suspends come from - I did not try any suspend in the meantime ... - -andrey ble entries: 32768 (order: 5, 131072 bytes) Memory: 499180k/507264k available (1663k kernel code, 7456k reserved, 795k data, 176k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 1496.80 BogoMIPS (lpj=748402) Mount-cache hash table entries: 512 CPU: After generic identify, caps: 0387f9ff CPU: After vendor identify, caps: 0387f9ff CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 256K CPU serial number disabled. CPU: After all inits, caps: 0383f9ff 0040 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU: Intel Pentium III (Coppermine) stepping 0a Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 0k freed ACPI: setting ELCR to 0200 (from 0a00) checking if image is initramfs... it is Freeing initrd memory: 230k freed NET: Registered protocol family 16 ACPI: bus type pci registered PCI: PCI BIOS revision 2.10 entry at 0xfe5ae, last bus=5 Setting up standard PCI resources ACPI: Subsystem revision 20060127 ACPI: Interpreter enabled ACPI: Using PIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (:00) PCI: Probing PCI hardware (bus 00) ACPI: Assume root bridge [\_SB_.PCI0] bus is 0 PCI quirk: region ee00-ee3f claimed by ali7101 ACPI PCI quirk: region ef00-ef1f claimed by ali7101 SMB Boot video device is :01:00.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 *11) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 *11) ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 *11) ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 *11) ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT] ACPI: Power Resource [PFAN] (off) Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init pnp: PnP ACPI: found 12 devices PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try pci=routeirq. If it helps, post a report TC classifier action (bugs to netdev@vger.kernel.org cc [EMAIL PROTECTED]) PCI: Bridge: :00:01.0 IO window: disabled. MEM window: f7f0-fdff PREFETCH window: 3c00-3c0f PCI: Bus 2, cardbus bridge: :00:10.0 IO window: 1000-10ff IO window: 1400-14ff PREFETCH window: 3000-31ff MEM window: 3200-33ff PCI: Bus 6, cardbus bridge: :00:11.0 IO window: 1800-18ff IO window: 1c00-1cff PREFETCH window: 3400-35ff MEM window: 3600-37ff PCI: Bus 10, cardbus bridge: :00:11.1 IO window: 2000-20ff IO window: 2400-24ff PREFETCH window: 3800-39ff MEM window: 3a00-3bff PCI: Setting latency timer of device :00:01.0 to 64 PCI: Enabling device :00:10.0 ( - 0003) ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 PCI: setting IRQ 11 as level-triggered ACPI: PCI Interrupt :00:10.0[A] - Link [LNKC] - GSI 11 (level, low) - IRQ 11 PCI: Enabling device :00:11.0 ( - 0003) ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 ACPI: PCI Interrupt :00:11.0[A] - Link [LNKA] - GSI 11 (level, low) - IRQ 11 PCI: Enabling device :00:11.1 ( - 0003) ACPI: PCI Interrupt
Re: [linux-usb-devel] 2.6.17: dmesg flooded with ohci_hcd 0000:00:02.0: wakeup
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 18 June 2006 22:16, David Brownell wrote:
On Sunday 18 June 2006 10:29 am, Andrey Borzenkov wrote:
On Sunday 18 June 2006 20:29, David Brownell wrote:
An alternative (but post-boot) workaround _should_ be
echo disabled /sys/bus/pci/devices/:00:02.0/power/wakeup
Did that work?
No.
{pts/1}% LC_ALL=C sudo sh -c 'echo -n disabled
/sys/bus/pci/devices/:00:02.0/power/wakeup'
sh: line 0: echo: write error: Invalid argument
because disabled is apparently spelled right, this means it bails out at
if (!device_can_wakeup(dev))
return -EINVAL;
which is also confirmed by the fact that reading it returns nothing.
This is Tohiba Portege 4000 notebook. So far I did not have any USB
related issues at least since 2.6.12. And true, I do not have any devices
plugged in.
It's the usual case of fixing one bug triggering another, in your case
because the fix ran into a previously unseen hardware bug. One other
way to work around that bug would be disabling CONFIG_PM, but I suspect
you don't want to go that route...
Well, after I have it doing STR just fine, I'd rather keep it :)
Here you are. I am still puzzled where all these suspends come from - I
did not try any suspend in the meantime ...
It's the driver putting the controller into a low power state. Your
hardware seems to have a bug whereby that doesn't work correctly,
making it immediately leave that state. (And the driver messaging is
fine for what should be an uncommon event; plus it highlighted your
hardware bug.) Notice the initreset quirk message -- another bug
in that hardware. Workarounds in both cases are simple.
When I get a moment, I'll have a patch for you to try. Meanwhile,
either workaround I showed above should prevent the attempt to enter
that low power mode.
Unfortunately one of them does not work and another is not really feasible :(
I guess I run 2.6.16 for a while :)
- -andrey
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.2 (GNU/Linux)
iD8DBQFElagVR6LMutpd94wRAkKvAJ9qZcf/fmo3lKAi3l/h0HtAYdVO7wCePfeM
kzJnCu8kzX5PjHFud837ShU=
=s5Wm
-END PGP SIGNATURE-
___
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] init 1 kill khubd on 2.6.11
On Monday 02 May 2005 02:30, Andrew Morton wrote:
Alan Stern [EMAIL PROTECTED] wrote:
On Sun, 1 May 2005, Andrey Borzenkov wrote:
Hub driver is using SIGKILL to terminate khubd. Unfortunately on a
number of distributions switching init levels implicitly does killall
-9, killing khubd. The only way to restart it is to reload USB
subsystem.
Is signal usage in this case really needed? What about replacing it
with simple flag (i.e. will patch be accepted)?
IMO the problem lies in those distributions. They should not
indiscrimately kill processes when switching init levels.
Nevertheless it's better that kernel internals not be exposed to userspace
actions in this manner, and using signals for in-kernel IPC is crufty, IMO.
It's pretty simple to convert khubd to use the kthread API. Something like
this (untested):
Something strange is going on with this patch.
insmod usbcore; insmod uhci-hcd works as expected, finds out all devices,
triggers hotplug etc. But
{pts/2}% sudo insmod ./usbcore.ko
{pts/2}% sudo mount -t usbfs -o devmode=0664,devgid=43 none /proc/bus/usb
{pts/2}% sudo modprobe usb-interface
results in
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v2.2
ACPI: PCI interrupt :00:1f.2[D] - GSI 5 (level, low) - IRQ 5
uhci_hcd :00:1f.2: UHCI Host Controller
PCI: Setting latency timer of device :00:1f.2 to 64
uhci_hcd :00:1f.2: irq 5, io base 0xa400
uhci_hcd :00:1f.2: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ACPI: PCI interrupt :00:1f.4[C] - GSI 9 (level, low) - IRQ 9
uhci_hcd :00:1f.4: UHCI Host Controller
PCI: Setting latency timer of device :00:1f.4 to 64
uhci_hcd :00:1f.4: irq 9, io base 0xa000
usb 1-1: new low speed USB device using uhci_hcd and address 2
uhci_hcd :00:1f.2: Unlink after no-IRQ? Controller is probably using the
wrong IRQ.
usb 1-1: khubd timed out on ep0out
usb 1-1: khubd timed out on ep0out
usb 1-1: device not accepting address 2, error -110
usb 1-1: new low speed USB device using uhci_hcd and address 3
usb 1-1: khubd timed out on ep0out
usb 1-1: khubd timed out on ep0out
usb 1-1: device not accepting address 3, error -110
usb 1-1: new low speed USB device using uhci_hcd and address 4
usb 1-1: khubd timed out on ep0in
usb 1-1: khubd timed out on ep0out
usb 1-1: khubd timed out on ep0out
usb 1-1: device not accepting address 4, error -110
usb 1-1: new low speed USB device using uhci_hcd and address 5
usb 1-1: khubd timed out on ep0in
usb 1-1: khubd timed out on ep0out
usb 1-1: khubd timed out on ep0out
usb 1-1: device not accepting address 5, error -110
usb 1-2: new full speed USB device using uhci_hcd and address 6
usb 1-2: khubd timed out on ep0out
usb 1-2: khubd timed out on ep0out
usb 1-2: device not accepting address 6, error -110
usb 1-2: new full speed USB device using uhci_hcd and address 7
usb 1-2: khubd timed out on ep0out
usb 1-2: khubd timed out on ep0out
usb 1-2: device not accepting address 7, error -110
usb 1-2: new full speed USB device using uhci_hcd and address 8
usb 1-2: khubd timed out on ep0in
usb 1-2: khubd timed out on ep0out
usb 1-2: khubd timed out on ep0out
usb 1-2: device not accepting address 8, error -110
usb 1-2: new full speed USB device using uhci_hcd and address 9
usb 1-2: khubd timed out on ep0in
usb 1-2: khubd timed out on ep0out
usb 1-2: khubd timed out on ep0out
usb 1-2: device not accepting address 9, error -110
uhci_hcd :00:1f.4: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
usb 2-2: new full speed USB device using uhci_hcd and address 2
hub 2-2:1.0: USB hub found
hub 2-2:1.0: 4 ports detected
I do not understand what difference mounting usbfs makes. For reference here
is result of loading the same usbcore without mounting usbfs:
{pts/2}% sudo insmod ./usbcore-new.ko
{pts/2}% sudo modprobe uhci-hcd
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v2.2
ACPI: PCI interrupt :00:1f.2[D] - GSI 5 (level, low) - IRQ 5
uhci_hcd :00:1f.2: UHCI Host Controller
PCI: Setting latency timer of device :00:1f.2 to 64
uhci_hcd :00:1f.2: irq 5, io base 0xa400
uhci_hcd :00:1f.2: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ACPI: PCI interrupt :00:1f.4[C] - GSI 9 (level, low) - IRQ 9
uhci_hcd :00:1f.4: UHCI Host Controller
PCI: Setting latency timer of device :00:1f.4 to 64
uhci_hcd :00:1f.4: irq 9, io base 0xa000
uhci_hcd :00:1f.4: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
usb 1-1: new low speed USB device using uhci_hcd and address 2
usb 1-2: new full speed USB device using uhci_hcd and address 3
usb 2-2: new full speed USB device using uhci_hcd and address 2
hub
Re: [linux-usb-devel] init 1 kill khubd on 2.6.11
On Monday 02 May 2005 13:30, Andrew Morton wrote:
Andrey Borzenkov [EMAIL PROTECTED] wrote:
It's pretty simple to convert khubd to use the kthread API. Something
like this (untested):
Something strange is going on with this patch.
insmod usbcore; insmod uhci-hcd works as expected, finds out all
devices, triggers hotplug etc. But
{pts/2}% sudo insmod ./usbcore.ko
{pts/2}% sudo mount -t usbfs -o devmode=0664,devgid=43 none
/proc/bus/usb {pts/2}% sudo modprobe usb-interface
results in
...
uhci_hcd :00:1f.2: Unlink after no-IRQ? Controller is probably
using the wrong IRQ.
usb 1-1: khubd timed out on ep0out
Does this only happen when the convert-khubd-to-kevent patch is applied?
(Do you mean patch posted in this thread?)
Now I must admit it does happen without patch too. Sometimes it goes through
but most of the time it results in those timeouts.
So I confirm that patch posted in this thread fixes original problem (khubd
killed by SIGKILL).
W.r.t. to timeouts - I appreciate hints where to start debugging. (I am
downloading vanilla kernel + -mm to give it a try).
regards
-andrey
pgpTsz68MmZ0X.pgp
Description: PGP signature
Re: [linux-usb-devel] init 1 kill khubd on 2.6.11
On Monday 02 May 2005 16:18, Andrey Borzenkov wrote:
On Monday 02 May 2005 13:30, Andrew Morton wrote:
Andrey Borzenkov [EMAIL PROTECTED] wrote:
It's pretty simple to convert khubd to use the kthread API.
Something like this (untested):
Something strange is going on with this patch.
insmod usbcore; insmod uhci-hcd works as expected, finds out all
devices, triggers hotplug etc. But
{pts/2}% sudo insmod ./usbcore.ko
{pts/2}% sudo mount -t usbfs -o devmode=0664,devgid=43 none
/proc/bus/usb {pts/2}% sudo modprobe usb-interface
results in
...
uhci_hcd :00:1f.2: Unlink after no-IRQ? Controller is probably
using the wrong IRQ.
usb 1-1: khubd timed out on ep0out
Does this only happen when the convert-khubd-to-kevent patch is applied?
...
(I am
downloading vanilla kernel + -mm to give it a try).
I cannot reproduce it on 2.6.12-rc3[-mm2], with or without patch in this
thread. It looks like whatever it was it was fixed in the meantime.
regards
-andrey
pgpmavbEJ81Ug.pgp
Description: PGP signature
[linux-usb-devel] init 1 kill khubd on 2.6.11
Hub driver is using SIGKILL to terminate khubd. Unfortunately on a number of distributions switching init levels implicitly does killall -9, killing khubd. The only way to restart it is to reload USB subsystem. Is signal usage in this case really needed? What about replacing it with simple flag (i.e. will patch be accepted)? TIA -andrey Please Cc me on reply pgp86ge52PiUi.pgp Description: PGP signature
