From: Len Brown <len.brown@intel.com>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.8-rc4-mm1 doesn't boot
Date: 17 Aug 2004 19:48:06 -0400 [thread overview]
Message-ID: <1092786485.25902.28.camel@dhcppc4> (raw)
In-Reply-To: <20040817231119.GB1387@fs.tum.de>
On Tue, 2004-08-17 at 19:11, Adrian Bunk wrote:
> On Fri, Aug 13, 2004 at 10:22:22PM -0400, Len Brown wrote:
> >...
> > Also, it would be helpful to see the lines with LNKD
> > in the dmesg for floppy enabled and floppy disabled cases --
> > a 2.6.7 vintage kernel should work fine:
> >
> > ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 *6 7 10 11 12 14 15)
> > ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 6
>
> I've used 2.6.8.1, and in both cases I got the following (in the
> enabled
> case, no floppy was actually present):
>
> ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 *6 7 10 11 12 14 15)
> ...
> ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 6
> ACPI: PCI interrupt 0000:00:04.0[A] -> GSI 6 (level, low) -> IRQ 6
That's interesting, IRQ6 is being given to PCI, even when the floppy
controller is enabled.
>
> > If you can also run acpidmp in both those scenarios
> > (any kernel version, ACPI enabled or disabled should do)
> > and send me the two output files, that would be great.
> >
> > thanks,
> > -Len
> >
> > ps. you can get acpidmp in /usr/sbin/ or from pmtools here
> > http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/
>
> It didn't compile for me:
>
> <-- snip -->
>
> ...
> gcc -Wall -fno-strength-reduce -fomit-frame-pointer -D__KERNEL__
> -DMODULE -I/usr/src/linux/include -Wall -Wno-unused -Wno-multichar
> -c
> -o pmtest.o pmtest.c
> In file included from /usr/include/asm/system.h:5,
> from /usr/include/asm/processor.h:18,
> from /usr/include/asm/thread_info.h:13,
> from /usr/include/linux/thread_info.h:21,
> from /usr/include/linux/spinlock.h:19,
> from /usr/include/linux/capability.h:45,
> from /usr/include/linux/sched.h:7,
> from /usr/include/linux/module.h:10,
> from pmtest.c:21:
> /usr/include/linux/kernel.h:72: error: parse error before "size_t"
> ...
you don't care about pmtest, just acpidmp.
cd acpidmp
make
thanks,
-Len
next prev parent reply other threads:[~2004-08-17 23:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <566B962EB122634D86E6EE29E83DD808182C2B33@hdsmsx403.hd.intel.com>
2004-08-11 21:32 ` 2.6.8-rc4-mm1 doesn't boot Len Brown
2004-08-11 21:37 ` Bjorn Helgaas
2004-08-11 21:51 ` Adrian Bunk
2004-08-11 22:22 ` Len Brown
2004-08-11 23:15 ` Adrian Bunk
2004-08-12 21:50 ` Bjorn Helgaas
2004-08-12 22:43 ` Len Brown
2004-08-13 0:23 ` Adrian Bunk
2004-08-13 21:15 ` Bjorn Helgaas
2004-08-13 23:55 ` Adrian Bunk
2004-08-14 2:22 ` Len Brown
2004-08-17 23:11 ` Adrian Bunk
2004-08-17 23:48 ` Len Brown [this message]
2004-08-10 7:21 2.6.8-rc4-mm1 Andrew Morton
2004-08-10 15:09 ` 2.6.8-rc4-mm1 doesn't boot Adrian Bunk
2004-08-10 15:59 ` Bjorn Helgaas
2004-08-10 17:32 ` Adrian Bunk
2004-08-10 22:46 ` Bjorn Helgaas
2004-08-10 23:56 ` Adrian Bunk
2004-08-11 20:33 ` Bjorn Helgaas
2004-08-11 23:23 ` Adrian Bunk
2004-08-11 9:56 ` Alan Cox
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=1092786485.25902.28.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.