From: Len Brown <len.brown@intel.com>
To: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
Cc: Micha Feigin <michf@post.tau.ac.il>,
linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: oops with 2.6.1-rc1 and rc-3
Date: 02 Feb 2004 13:59:32 -0500 [thread overview]
Message-ID: <1075748372.2398.117.camel@dhcppc4> (raw)
In-Reply-To: <401E0E2C.8020708@gmx.de>
>> handlers:
>> [<c02a6b50>] (ide_intr+0x0/0x190)
>> [<c03248c0>] (snd_intel8x0_interrupt+0x0/0x210)
>> Disabling IRQ #11
>> irq 11: nobody cared!
> If you find that it goes away when you boot with pci=noacpi, or
> > acpi=off, then it is likely an ACPI issue -- otherwise it is likely
> > something else -- so give those a try and let me know.
>
> Ok, I tried rc3 without acpi compiled in, and yes, it booted. So I guess
> acpi is really breaking up stuff. If you want me to test patches, let me
> know.
Need more info before sending you test patches, please open up a new bug
report and put the info there:
http://bugzilla.kernel.org/ Category: Power Management, Component: ACPI
For the same (ACPI enabled) kernel, both with and without "acpi=off",
please attach
dmesg -s40000 output (or serial console log if dmesg unavailable)
/proc/interrupts
If you can run the latest release, and clarify which release this last
worked properly in, that would be helpful.
Also, please attach the output from acpidmp, available in /usr/sbin/, or
in pmtools:
http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/
Please attach the output from dmidecode, available in /usr/sbin/, or
here:
http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/
and attach a copy of your .config
thanks,
-Len
next prev parent reply other threads:[~2004-02-02 18:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BF1FE1855350A0479097B3A0D2A80EE0020AEB18@hdsmsx402.hd.intel.com>
2004-02-01 19:49 ` oops with 2.6.1-rc1 and rc-3 Len Brown
2004-02-02 8:45 ` Prakash K. Cheemplavam
2004-02-02 18:59 ` Len Brown [this message]
2004-02-02 20:51 ` Prakash K. Cheemplavam
2004-02-02 20:54 ` Prakash K. Cheemplavam
2004-01-31 7:28 [Swsusp-devel] Software Suspend 2.0 Nigel Cunningham
2004-01-31 7:38 ` Joseph Pingenot
2004-01-31 8:32 ` Nigel Cunningham
2004-01-31 9:03 ` Prakash K. Cheemplavam
2004-01-31 9:08 ` Nigel Cunningham
2004-01-31 9:19 ` Prakash K. Cheemplavam
2004-01-31 9:51 ` Nigel Cunningham
2004-01-31 10:43 ` Prakash K. Cheemplavam
2004-01-31 13:25 ` Måns Rullgård
2004-01-31 23:11 ` Joseph Pingenot
2004-02-01 0:26 ` Micha Feigin
2004-02-01 1:48 ` oops with 2.6.1-rc1 and rc-3 Prakash K. Cheemplavam
2004-02-01 2:54 ` Micha Feigin
2004-02-01 10:36 ` Prakash K. Cheemplavam
2004-02-01 11:37 ` Prakash K. Cheemplavam
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=1075748372.2398.117.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=PrakashKC@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=michf@post.tau.ac.il \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox