From: Matthew Harrell <lists-sender-12e533-bmWjYudjZeGERhycZ4x6Ig@public.gmane.org>
To: Faye Pearson <faye-6JSjyQ0Qj1ReoWH0uzbU5w@public.gmane.org>
Cc: ACPI List <acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Re: odd irq routing errors?
Date: Fri, 14 Mar 2003 08:34:46 -0500 [thread overview]
Message-ID: <20030314133446.GA546@bittwiddlers.com> (raw)
In-Reply-To: <20030314103049.GB19277-6JSjyQ0Qj1ReoWH0uzbU5w@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2344 bytes --]
: > : > PCI: No IRQ known for interrupt pin A of device 00:1f.1 - using IRQ 255
:
: The message is (mis)informational rather than destructive for me.
BTW, when I tried some of your suggestions I saw that I was, in fact, getting
the exact same error message. I was never able to see it before since the
laptop became totally unuseable.
: Try removing acpid from your startup scripts before booting into 2.5.6x
: then check your /proc/interrupts and see if there are a large number
: being generated quickly.
Not sure what a large number really is anymore since I haven't really watched
it in a long time. Once I removed acpid from the startup it then died on
starting alsa but when I booted it into single user mode I saw the message
about pci=noacpi. So, I am now operating under it with acpi on, pci=noacpi,
and no acpid. If I turn on acpid it hangs the system again so this is kind of
a pointless configuration to run in. I don't see an unusual amount of
interrupts in this state except on timer and I assume that is normal
CPU0
0: 405906 XT-PIC timer
1: 14 XT-PIC i8042
2: 0 XT-PIC cascade
8: 4 XT-PIC rtc
9: 740 XT-PIC acpi, VIA8233
10: 17175 XT-PIC uhci-hcd, eth0
11: 25 XT-PIC eth1
12: 35 XT-PIC i8042
14: 8644 XT-PIC ide0
15: 1 XT-PIC ide1
NMI: 0
LOC: 0
ERR: 0
MIS: 0
: This could cause laptop slowdown and perhaps overheating which can
: introduce instability. It's a known problem that I've seen
: mentioned on the list. I expect that the developers will need much more
: information from you if they are to help.
If anyone would like to look into it just let me know what info I can provide.
I can work like this for a while but it's not optimal - 50% of the time I don't
have pcmcia support on bootup like this (and don't really need it) and 50%
of the time I don't have USB.
Boot messages are attached below
--
Matthew Harrell Any sufficiently advanced technology
Bit Twiddlers, Inc. is indistinguishable from a rigged
mharrell-bmWjYudjZeGERhycZ4x6Ig@public.gmane.org demo.
[-- Attachment #2: boot.log.bz2 --]
[-- Type: application/octet-stream, Size: 5213 bytes --]
prev parent reply other threads:[~2003-03-14 13:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 22:13 odd irq routing errors? Matthew Harrell
[not found] ` <20030313221321.GA21296-bmWjYudjZeGERhycZ4x6Ig@public.gmane.org>
2003-03-14 10:30 ` Faye Pearson
[not found] ` <20030314103049.GB19277-6JSjyQ0Qj1ReoWH0uzbU5w@public.gmane.org>
2003-03-14 13:34 ` Matthew Harrell [this message]
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=20030314133446.GA546@bittwiddlers.com \
--to=lists-sender-12e533-bmwjyudjzegerhycz4x6ig@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=faye-6JSjyQ0Qj1ReoWH0uzbU5w@public.gmane.org \
--cc=mharrell-dated-1048080890.82da7a-bmWjYudjZeGERhycZ4x6Ig@public.gmane.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