[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200704152154.09212.rjw@sisk.pl>
Date: Sun, 15 Apr 2007 21:54:07 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Tobias Diedrich <ranma+kernel@...edrich.de>
Cc: David Brownell <david-b@...bell.net>,
linux-pm@...ts.linux-foundation.org, pavel@...e.cz,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Maxim Levitsky <maximlevitsky@...il.com>,
linux-pm@...ts.osdl.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Adrian Bunk <bunk@...sta.de>
Subject: Re: [linux-pm] Linux 2.6.21-rc6
On Sunday, 15 April 2007 21:40, Tobias Diedrich wrote:
> Rafael J. Wysocki wrote:
> > On Sunday, 15 April 2007 17:14, David Brownell wrote:
> > > On Sunday 15 April 2007 4:16 am, Rafael J. Wysocki wrote:
> > > > On Sunday, 15 April 2007 10:02, Tobias Diedrich wrote:
> > >
> > > > > > > > Yes, it's a Asus M2N-SLI-Deluxe Mainboard with a Athlon64 3200+
> > > > > > > > single core CPU.
> > >
> > > And NVidia southbridge, so OHCI not UHCI (plus EHCI) ... one experiment
> > > would be to disable the EHCI (high speed USB) support in BIOS, to make
> > > for a simpler hardware configuration, and see if that makes BIOS happier.
> > > (Or better, just take EHCI out of your Linux config.) Likewise, taking
> > > the 8042 drivers out of Linux.
> > >
> > > I wouldn't be surprised if those factors didn't matter, but it'd be good
> > > to rule them out.
> >
> > I think the disabling of i8042 support might help.
>
> Still hangs with "# CONFIG_SERIO_I8042 is not set".
>
> > > > Dmitry, could you please have a look?
> > > >
> > > > > And I can now confirm that unpatched 2.6.21-rc6 works fine as long
> > > > > as USB legacy support is disabled (however without legacy support I
> > > > > can't use the USB keyboard to control grub).
> > > >
> > > > I think using the 'shutdown' mode of suspend would be better. There's a little
> > > > point in using 'platform' on desktop systems anyway.
> > > >
> > > > Frankly, I don't know what to do about it. If we move platform_finish() after
> > > > device_resume(), some systems may be broken ...
> > >
> > > What I'm curious about is exactly why the patch matters. What ACPI
> > > magic is being invoked to confuse, or unconfuse, those controllers?
> >
> > I think the patch helps, because it makes the ACPI magic be done while the
> > i8042's .resume() is being executed.
> >
> > Which makes me think the following patch might help:
>
> Unfortunately not, I tried this before disabling CONFIG_SERIO_I8042.
Well, this means i8042 can be ruled out, so the problem probably is related
to the ACPI resume which makes it _much_ more difficult to debug.
Can you compile the ACPI drivers: processor, thermal, fan, battery, etc. as
modules, boot the kernel with init=/bin/bash and see if the problem is still
present (please keep CONFIG_SERIO_I8042 unset just in case)?
Rafael
-
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