From: Vojtech Pavlik <vojtech@suse.cz>
To: Frank Peters <frank.peters@comcast.net>
Cc: Andrew Morton <akpm@osdl.org>,
mkrufky@m1k.net, linux-kernel@vger.kernel.org
Subject: Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems
Date: Sun, 31 Jul 2005 20:45:32 +0200 [thread overview]
Message-ID: <20050731184532.GA9026@ucw.cz> (raw)
In-Reply-To: <20050730023453.196a7477.frank.peters@comcast.net>
On Sat, Jul 30, 2005 at 02:34:53AM -0400, Frank Peters wrote:
> On Fri, 29 Jul 2005 21:37:24 -0700
> Andrew Morton <akpm@osdl.org> wrote:
>
> >
> > So I dunno, sorry. Brute-force it with a git bisection search, perhaps?
>
> I compiled 2.6.13-rc4 with ACPI debugging enabled.
>
> During a failed boot, when the keyboard was unresponsive, I managed
> to capture a kernel log of this failure. Here are the lines that caught
> my attention:
>
> kernel: i8042.c: Can't read CTR while initializing i8042.
> kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
> kernel: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> kernel: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> kernel: ACPI: PCI Interrupt 0000:02:0a.0[A] -> GSI 22 (level, low) -> IRQ 16
> kernel: ttyS2 at I/O 0xb800 (irq = 16) is a 16550A
>
> This error/warning message does not occur all the time, but it
> has appeared at least twice during my brief experimentation and
> I would consider it something that can be duplicated.
>
> So far it is the only anomoly that I have seen anywhere, but it may
> be more a result of the problem rather than the cause.
Please try 'usb-handoff' on the kernel command line. This looks like an
usual symptom on machines that need it.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2005-07-31 18:45 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
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 [this message]
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=20050731184532.GA9026@ucw.cz \
--to=vojtech@suse.cz \
--cc=akpm@osdl.org \
--cc=frank.peters@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mkrufky@m1k.net \
/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