From: David Brownell <david-b@pacbell.net>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] 2.6.17: dmesg flooded with "ohci_hcd 0000:00:02.0: wakeup"
Date: Sun, 18 Jun 2006 11:16:19 -0700 [thread overview]
Message-ID: <200606181116.20815.david-b@pacbell.net> (raw)
In-Reply-To: <200606182129.15712.arvidjaar@mail.ru>
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/0000: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.
- 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 0000:00:02.0[A] -> Link [LNKG] -> GSI 11 (level, low) ->
> IRQ 11
> ohci_hcd 0000: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 0000:00:02.0: new USB bus registered, assigned bus number 1
> ohci_hcd 0000:00:02.0: created debug files
> ohci_hcd 0000:00:02.0: irq 11, io mem 0xf7eff000
> ohci_hcd 0000:00:02.0: resetting from state 'reset', control = 0x0
> ohci_hcd 0000:00:02.0: enabling initreset quirk
> ohci_hcd 0000:00:02.0: OHCI controller state
> ohci_hcd 0000:00:02.0: OHCI 1.0, NO legacy support registers
> ohci_hcd 0000:00:02.0: control 0x083 HCFS=operational CBSR=3
> ohci_hcd 0000:00:02.0: cmdstatus 0x00000 SOC=0
> ohci_hcd 0000:00:02.0: intrstatus 0x00000044 RHSC SF
> ohci_hcd 0000:00:02.0: intrenable 0x8000000a MIE RD WDH
> ohci_hcd 0000:00:02.0: hcca frame #0003
> ohci_hcd 0000:00:02.0: roothub.a 01000203 POTPGT=1 NPS NDP=3(3)
> ohci_hcd 0000:00:02.0: roothub.b 00000000 PPCM=0000 DR=0000
> ohci_hcd 0000:00:02.0: roothub.status 00008000 DRWE
> ohci_hcd 0000:00:02.0: roothub.portstatus [0] 0x00000100 PPS
> ohci_hcd 0000:00:02.0: roothub.portstatus [1] 0x00000100 PPS
> ohci_hcd 0000:00:02.0: roothub.portstatus [2] 0x00000100 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: 0000: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 0000 evt 0000
> /home/bor/src/linux-git/drivers/usb/core/inode.c: creating file '001'
> ohci_hcd 0000:00:02.0: suspend root hub
> hub 1-0:1.0: state 7 ports 3 chg 0000 evt 0000, resume root
> hub 1-0:1.0: state 7 ports 3 chg 0000 evt 0000
> ohci_hcd 0000:00:02.0: suspend root hub
> hub 1-0:1.0: state 7 ports 3 chg 0000 evt 0000, resume root
> hub 1-0:1.0: state 7 ports 3 chg 0000 evt 0000
> ohci_hcd 0000:00:02.0: suspend root hub
> hub 1-0:1.0: state 7 ports 3 chg 0000 evt 0000, resume root
> hub 1-0:1.0: state 7 ports 3 chg 0000 evt 0000
> ohci_hcd 0000:00:02.0: suspend root hub
... etc
next prev parent reply other threads:[~2006-06-18 18:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 15:19 2.6.17: dmesg flooded with "ohci_hcd 0000:00:02.0: wakeup" Andrey Borzenkov
2006-06-18 16:29 ` [linux-usb-devel] " David Brownell
2006-06-18 17:29 ` Andrey Borzenkov
2006-06-18 18:16 ` David Brownell [this message]
2006-06-18 19:22 ` Andrey Borzenkov
2006-06-19 18:39 ` Andrey Borzenkov
2006-06-19 20:12 ` David Brownell
2006-11-11 11:29 ` 2.6.19-rc5 regression: can't disable OHCI wakeup via sysfs Andrey Borzenkov
2006-11-12 16:31 ` [linux-usb-devel] " Alan Stern
2006-11-12 18:00 ` David Brownell
2006-11-12 21:59 ` Alan Stern
2006-11-12 23:21 ` David Brownell
2006-11-13 15:57 ` Alan Stern
2006-11-13 16:39 ` David Brownell
2006-11-13 17:15 ` Alan Stern
2006-11-14 21:18 ` David Brownell
2006-11-14 21:42 ` Alan Stern
2006-11-14 22:56 ` David Brownell
2006-11-13 19:58 ` Alan Stern
2006-11-14 20:48 ` Andrey Borzenkov
2006-11-14 20:54 ` [Bulk] " David Brownell
2006-09-22 18:53 ` [linux-usb-devel] 2.6.17: dmesg flooded with "ohci_hcd 0000:00:02.0: wakeup" Andrey Borzenkov
2006-09-22 20:52 ` Alan Stern
2006-11-11 11:27 ` Andrey Borzenkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200606181116.20815.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=arvidjaar@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox