lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 22 Sep 2006 22:53:43 +0400
From:	Andrey Borzenkov <arvidjaar@...l.ru>
To:	David Brownell <david-b@...bell.net>
Cc:	linux-usb-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: 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/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.
>


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 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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFFDE4R6LMutpd94wRAjhpAJ4+gsOgdQT8V83QPgbMXa6AVH2WQgCgh4nM
V0GQyKHQylBIrFQwcVGcaEs=
=dlTM
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ