On Wed, 12 Dec 2012 12:28:16 -0800, Frank Schäfer
wrote:
Good information. Attaching device makes hc work abnormally during
entering into s3 since without device it can work, right?
Right.
The system successfully enters S3 (machine switches off = fan stops,
light off etc.) but it resumes im
On Thu, 13 Dec 2012 07:35:55 -0800, Frank Schäfer
wrote:
I write a quirk patch. Can you test?
Yes, that makes it work !
I just find one MCP51 and two MCP79 OHCI id. Can you provide more buggy
hcd id via "lspci -nnvvv"?
Thanks.
I have the MCP61 (rev. A2) with id 10de:03f1.
Further NVIDIA
On Thu, 13 Dec 2012 00:45:05 -0800, Lan Tianyu
wrote:
diff --git a/drivers/usb/core/hcd.c b/drivers/usb/core/hcd.c
index f034716..9335f1b 100644
--- a/drivers/usb/core/hcd.c
+++ b/drivers/usb/core/hcd.c
@@ -2509,7 +2509,8 @@ int usb_add_hcd(struct usb_hcd *hcd,
* they only forward requ
On Wed, 19 Dec 2012 07:29:23 -0800, Alan Stern
wrote:
+ ohci_dbg(ohci, "marked as bad wakeup.\n");
I'd prefer the message to be something more like "enabled nVidia/SiS
wakeup quirk".
To me, the stupid end-user, both messages are useless. I don't know
that that means or implies. I woul
On Wed, 19 Dec 2012 08:57:00 -0800, Alan Stern
wrote:
You, the stupid end-user, would not see this message at all under
normal circumstances. It uses the ohci_dbg macro and therefore will
not appear unless your kernel is built with CONFIG_USB_DEBUG enabled.
Shouldn't it be exposed to dmesg
On Wed, 19 Dec 2012 11:35:50 -0800, Alan Stern
wrote:
As far as the OHCI hardware is concerned, there shouldn't be any
difference between runtime suspend and system suspend. This strongly
suggests that the bug doesn't lie in the controller itself but in the
firmware (BIOS or ACPI).
Is there
On Wed, 26 Dec 2012 09:21:03 -0800, Frank Schäfer
wrote:
Am 24.12.2012 20:23, schrieb Alan Stern:
On Fri, 21 Dec 2012, Frank Schäfer wrote:
Anyway, system still wakes up from S3 immediately.
It just occurred to me that not too long ago we learned about a BIOS
bug in ASUS systems that affect
On Thu, 03 Jan 2013 11:22:19 -0800, Alan Stern
wrote:
On Thu, 3 Jan 2013, [ISO-8859-1] Frank Sch�fer wrote:
Ok, I tried switching the ports to +5VSB.
That makes S3 work (no immediate wakeups).
The problem is, that with this setting, the USB ports are powered ALWAYS
(even when the computer is
Just as a side note, some discussion has been taking place at
https://bugzilla.kernel.org/show_bug.cgi?id=43081
particularly on looking for ways to detect the 5V/5VSB setting via
software, if possible at all.
If this is not possible from the kernel, I'd suggest, setting the
default to whatever
On 10/05/2012 07:56 AM, Alan Stern wrote:
On Mon, 9 Jul 2012, Octavio Alvarez wrote:
What happens if you unplug only the keyboard, or only the mouse?
The only thing I can confirm for now is that with both disconnected
the system consistently suspends and that I have seen the system NOT
Hi, Alan!
So, after about more than a week of bisecting, and thanks to Jonathan
Nieder's
more-than-precise instructions, the results are in.
On Mon, 25 Jun 2012 11:41:31 -0700, Alan Stern
wrote:
On Mon, 25 Jun 2012, Octavio Alvarez wrote:
On Mon, 25 Jun 2012 07:33:11 -0700, Alan
On Sat, 07 Jul 2012 19:23:08 -0700, Alan Stern
wrote:
> Also, what does the "lspci -vv" output show for the controller if you
> run it with superuser permissions?
[Sat Jul 07 12:50:10 -0700 -- alvarezp@octavio:/sys/kernel/debug/usb]
$ sudo lspci -vv -s :00:0b.1
0b.1 is the EHCI control
On Sun, 08 Jul 2012 07:40:49 -0700, Alan Stern
wrote:
On Sat, 7 Jul 2012, Octavio Alvarez wrote:
On Sat, 07 Jul 2012 19:23:08 -0700, Alan Stern
wrote:
>> roothub.portstatus [4] 0x0303 LSDA PPS PES CCS
>> roothub.portstatus [5] 0x0303 LSDA PPS PES CCS
>> roo
On Sun, 08 Jul 2012 17:28:25 -0700, Alan Stern
wrote:
>> Removing my pen drive cleared CCS on [6].
>
> Okay, that explains that. More or less. Is this an old USB-1.1 pen
> drive? If it is USB-2.0 then I would expect it to connect to the EHCI
> controller, not the OHCI controller.
I don't
14 matches
Mail list logo
