From: Andrew Morton <akpm@osdl.org>
To: Wiktor Wodecki <wodecki@gmx.de>
Cc: felipe_alfaro@linuxmail.org, vojtech@ucw.cz,
linux-kernel@vger.kernel.org, vojtech@suse.cz,
linux-acpi@intel.com
Subject: Re: 2.6.0-test3-bk6: hang at i8042.c when booting with no PS/2 mouse attached
Date: Sun, 24 Aug 2003 12:40:20 -0700 [thread overview]
Message-ID: <20030824124020.72a1f03c.akpm@osdl.org> (raw)
In-Reply-To: <20030824131312.GA714@gmx.de>
Wiktor Wodecki <wodecki@gmx.de> wrote:
>
> > > > if (request_irq(values->irq, i8042_interrupt, SA_SHIRQ,
> > > > "i8042", i8042_request_irq_cookie))
> > >
> > > What happens if you remove the SA_SHIRQ and replace with 0?
> >
> > It does nothing: the kernel still hangs there. It seems to be a problem with the new ACPI code
> > changes cause the kernel boots fine with "pci=noacpi".
>
> confirmed here. Although I have it on 2.6.0-test4 and had it since
> al least test3-mm3.
Guys, please send a full report to linux-acpi@intel.com based on
the following:
Regarding how to field these in general...
Bugzilla would be really helpful, because we've got multiple bugs and
multiple people working on them and bugzilla is better than e-mail at
keeping the relevant bits together. bugzilla with component=ACPI and
owner len.brown@intel.com or andrew.grover@intel.com should do the
trick.
The dmesg output of the failing case is really helpful,
As is the output of acpidmp to examine the ACPI tables on the system.
(Red Hat includes both of these in their severn beta1, acpidmp is also
in pmtools on intel's ACPI web page)
dmidecode output is useful to identify the BIOS version.
Of course the 1st thing to check with ACPI failures is that the BIOS
version shown by dmidmp is the latest provided by the vendor... Plus,
if we determine the BIOS is toast, DMI provides what we need to add the
system to the DMI or acpi blacklists.
We're seeting the most problems on VIA chip-sets with no IO-APIC.
The one below is unusual because it is a 2-way system with 3 IO-APICs.
The latest code in linus' tree includes ACPICA 20030813, which is
slightly newer than the one below, it might be a good idea to try that
with CONFIG_ACPI_DEBUG. Note that it will spit out the DMI info upon
the mount root failure automatically.
next prev parent reply other threads:[~2003-08-24 19:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-24 12:06 2.6.0-test3-bk6: hang at i8042.c when booting with no PS/2 mouse attached Felipe Alfaro Solana
2003-08-24 12:10 ` Vojtech Pavlik
2003-08-24 13:13 ` Wiktor Wodecki
2003-08-24 19:40 ` Andrew Morton [this message]
2003-08-24 23:06 ` Felipe Alfaro Solana
[not found] <1061233756.1520.16.camel@teapot.felipe-alfaro.com>
2003-08-24 10:46 ` Vojtech Pavlik
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=20030824124020.72a1f03c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=felipe_alfaro@linuxmail.org \
--cc=linux-acpi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
--cc=vojtech@ucw.cz \
--cc=wodecki@gmx.de \
/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;
as well as URLs for NNTP newsgroup(s).