From: Michael Krufky <mkrufky@m1k.net>
To: Andrew Morton <akpm@osdl.org>
Cc: frank.peters@comcast.net, vojtech@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems
Date: Fri, 29 Jul 2005 23:48:21 -0400 [thread overview]
Message-ID: <42EAF885.40008@m1k.net> (raw)
In-Reply-To: <20050728225433.6dbfecbe.akpm@osdl.org>
Andrew Morton wrote:
>Michael Krufky <mkrufky@m1k.net> wrote:
>
>
>> Sadly, I must report that yes, the problem still intermittently occurs
>> in 2.6.13-rc4 :-( I'm the one that tested on the Shuttle FT61
>> Motherboard. Never has a problem in windows and never in 2.6.11 and
>> earlier.
>>
>> I first noticed this problem sometime during 2.6.12-rc series.
>>
>>
>
>Sigh. I think it would help if you could generate a new report, please.
>
>We need a super-easy way for people to do bisection searching.
>
>
I dug up the original email that I sent to LKML...
Michael Krufky wrote (5/26/2005 10:16 PM):
> In 2.6.12-rc5-mm1, I can't use my psaux mouse, but it worked perfectly
> fine in both 2.6.12-rc5 and in 2.6.12-rc4-mm2.
>
> In 2.6.12-rc5-mm1 , dmesg says:
>
> PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
> Failed to disable AUX port, but continuing anyway... Is this a SiS?
> If AUX port is really absent please use the 'i8042.noaux' option.
> serio: i8042 KBD port at 0x60,0x64 irq 1
>
> This is what dmesg says in both 2.6.12-rc4-mm2 and 2.6.12-rc5 :
>
> PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
> serio: i8042 AUX port at 0x60,0x64 irq 12
> serio: i8042 KBD port at 0x60,0x64 irq 1
>
> I am using a Shuttle FT61 motherboard. Is there any more information
> necessary to debug this?
>
--
Michael Krufky
next prev parent reply other threads:[~2005-07-30 3:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 15:34 Asus MB and 2.6.12 Problems Frank Peters
2005-06-24 16:10 ` isa0060/serio0 problems -WAS- " Michael Krufky
2005-06-24 16:59 ` Frank Peters
2005-06-24 17:12 ` Michael Krufky
[not found] ` <20050728222838.64517cc9.akpm@osdl.org>
2005-07-29 5:44 ` Michael Krufky
2005-07-29 5:54 ` Andrew Morton
2005-07-30 2:44 ` Zwane Mwaikambo
2005-07-30 3:48 ` Michael Krufky [this message]
2005-07-30 3:52 ` Michael Krufky
2005-07-30 4:18 ` Michael Krufky
2005-07-30 4:37 ` Andrew Morton
2005-07-30 5:57 ` Dmitry Torokhov
2005-07-30 6:34 ` Frank Peters
2005-07-31 18:45 ` Vojtech Pavlik
2005-07-31 19:24 ` Frank Peters
2005-07-31 20:42 ` Andrew Morton
2005-07-31 23:48 ` Frank Peters
2005-07-29 18:33 ` Frank Peters
[not found] ` <20050804162812.29a3f2b2.akpm@osdl.org>
2005-08-05 3:09 ` Frank Peters
2005-08-05 3:20 ` Dmitry Torokhov
2005-08-05 3:54 ` Andrew Morton
2005-08-05 4:07 ` Dmitry Torokhov
2005-08-05 10:40 ` Marc Ballarin
2005-08-05 4:07 ` Michael Krufky
2005-08-05 6:43 ` Vojtech Pavlik
2005-08-04 20:19 ` Andrew Morton
2005-06-27 11:39 ` Michael Krufky
[not found] ` <1119633158.3180.5.camel@home-lap>
2005-06-24 18:07 ` Frank Peters
2005-06-26 19:47 ` Alexey Dobriyan
-- strict thread matches above, loose matches on Subject: below --
2005-07-30 8:33 isa0060/serio0 problems -WAS- " 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=42EAF885.40008@m1k.net \
--to=mkrufky@m1k.net \
--cc=akpm@osdl.org \
--cc=frank.peters@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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