Prev: [resend] intel_agp: Don't oops with zero stolen memory
Next: ARM: 6166/1: Proper prefetch abort handling on pre-ARMv6
From: Dmitry Torokhov on 1 Jul 2010 18:50
On Fri, Jul 02, 2010 at 12:28:17AM +0200, Jerome Lacoste wrote:
> On Thu, Jul 1, 2010 at 11:19 PM, Jerome Lacoste
> <jerome.lacoste(a)gmail.com> wrote:
> > On Thu, Jul 1, 2010 at 6:24 PM, Dmitry Torokhov
> > <dmitry.torokhov(a)gmail.com> wrote:
> >> Hi Jerome,
> >>
> > [...]
> >>> * the hardware is a Lenovo 3000 N100
> >>
> >> We already trying to disable MUX mode on Lenovo 3000 N100, see
> >> drivers/input/serio/i8042-x86ia64io.h:
> >>
> >> � � � �{
> >> � � � � � � � �/* Lenovo 3000 n100 */
> >> � � � � � � � �.matches = {
> >> � � � � � � � � � � � �DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
> >> � � � � � � � � � � � �DMI_MATCH(DMI_PRODUCT_NAME, "076804U"),
> >> � � � � � � � �},
> >> � � � �},
> >>
> >> What's in your dmi?
> >
> > System Information
> > � � � �Manufacturer: LENOVO
> > � � � �Product Name: 0768BKG
> > � � � �Version: 3000 N100
> >
> > according to dmidecode
>
> Note: I will try the i8042.nomux option, but can't reboot until tomorrow.

Could you please also try i8042.reset instead of i8042.nomux?

--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Henrique de Moraes Holschuh on 1 Jul 2010 20:50
On Fri, 02 Jul 2010, Jerome Lacoste wrote:
> The discussion is in particular here:
> http://lkml.indiana.edu/hypermail/linux/kernel/0809.0/0316.html

Which lists firmware version 61ET20WW, which according to:
http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-67008

is a *VERY* outdated BIOS.

And it looks like there are two firmware versions (61* and 63*). And many
releases. If the BIOS update program also upgrades the EC, it can very well
fix i8042-related problems, since it is usually emulated by EC firmware.

Doesn't look like a quirk you can tie to just model type. And if you do,
the three last letters usually doesn't mean much on any Lenovo or IBM box.
The first four are the main model type.

--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Henrique de Moraes Holschuh on 4 Jul 2010 01:00
Won't this cause an extra delay on resume to everyone who has a device
with proper firmware?

Would it be possible to reset the i8042 only if failures to bring the
active multiplexer are detected?

--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Dmitry Torokhov on 4 Jul 2010 01:30
Hi Henrique,

On Sun, Jul 04, 2010 at 01:53:15AM -0300, Henrique de Moraes Holschuh wrote:
> Won't this cause an extra delay on resume to everyone who has a device
> with proper firmware?

I do not think that i8042 reset itself takes long time, touchpads are
the ones that need about 1 sec to do a full reset,

>
> Would it be possible to reset the i8042 only if failures to bring the
> active multiplexer are detected?
>

Failure to revive multiplexor is the only issue there is...

--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Dmitry Torokhov on 12 Jul 2010 12:10
On Mon, Jul 12, 2010 at 04:28:41PM +0200, Jerome Lacoste wrote:
> On Sat, Jul 3, 2010 at 11:20 PM, Dmitry Torokhov
> <dmitry.torokhov(a)gmail.com> wrote:
> [...]
> >> > Could you please also try i8042.reset instead of i8042.nomux?
> >>
> >> the i8042.reset works so far after 5 resumes.
> >>
> >> Tested with: Linux expresso2 2.6.32-23-generic #37-Ubuntu SMP Fri Jun
> >> 11 07:54:58 UTC 2010 i686 GNU/Linux
> >>
> >> Should I test something else ?
> >>
> >
> > Coudl you please try the patch below?
> >
> > Thanks.
>
> Patch works ( I adapted it to work for my kernel:
> http://launchpadlibrarian.net/51784930/0001-Input-i8042-reset-keyboard-controller-wehen-resuming.patch
> )
>
> Sorry it took me quite a bit of time to manage to get Ubuntu's git
> repo cloned and build my kernel.
>
> I suspended/resumed 3 times so far after removing the i8042.quiet
> option. There's nothing wrong in the logs. I'll report if I see a
> problem.
>
> I haven't noticed delays in resuming.
>

Great, I will mark it as 'Tested-by:' by you then.

--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [resend] intel_agp: Don't oops with zero stolen memory
Next: ARM: 6166/1: Proper prefetch abort handling on pre-ARMv6