From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: "Martin MOKREJŠ" <mmokrejs-V2lp6ZUObelkZyP8+xg2CQ@public.gmane.org>
Cc: "Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI kernel crash with 2.4.22-pre7 on ASUS L3800C
Date: Thu, 4 Sep 2003 11:26:27 +0200 [thread overview]
Message-ID: <20030904092627.GA29604@hell.org.pl> (raw)
In-Reply-To: <Pine.OSF.4.51.0309040921460.337830-xveqDVFKMsx2wEp5G055aaVXKuFTiq87@public.gmane.org>
Thus wrote Martin MOKREJŠ:
> I cannot say much about 2.4.22. On my laptop I got very slow response, it
> seems because of the very high interrupt rate generated by my network
> card(seen in 2.4.22 in /proc/interrupts).
Strange, I have not observerd such an issue with my (limited so far)
testing of 2.4.22.
> I attach 3 files from my running instance 2.4.22-pre7. Below is also
> output from /proc/interrupts (2.4.22-pre7). Ithat expected that no IO-APIC
> is found on my laptop? I used to have bios 1.21a but I downgraded to see if
There is no IO-APIC, and moreover, the LAPIC (disabled by BIOS by default)
is buggy and does not interact well with ACPI. Wasn't this particular
laptop blacklisted a while ago?
> the problem with FAN goes off. I've rebooted only once or twice, so cannot
> say if that helped at all. But 1.18 is my original BIOS version and I
> believe I had even with that version FAN problems.
The fan problem occurs at least in 1.18, 1.19 and 1.21. I did not test
others.
> mokrejs@vrapenec$ cat /proc/interrupts
> CPU0
> 0: 8221410 XT-PIC timer
> 1: 140910 XT-PIC keyboard
> 2: 0 XT-PIC cascade
> 5: 513521 XT-PIC usb-uhci
> 8: 2 XT-PIC rtc
> 9: 3588933 XT-PIC acpi, usb-uhci, eth0
> 11: 0 XT-PIC Intel ICH3
> 12: 23994 XT-PIC PS/2 Mouse
> 14: 484418 XT-PIC ide0
> 15: 24 XT-PIC ide1
> NMI: 0
> LOC: 0
> ERR: 1
> MIS: 0
Do not compile neither IO-APIC nor UP-APIC. It's useless on this laptop.
BTW: under 2.4.22 (and recent 2.6.0, AFAIR), the above listing is the same,
except that the uhci-hcd goes from IRQ 9 to 11.
Best regards,
--
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-09-04 9:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 4:04 ACPI kernel crash with 2.4.22-pre7 on ASUS L3800C Brown, Len
[not found] ` <BF1FE1855350A0479097B3A0D2A80EE009FCFB-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
2003-09-04 8:53 ` [ACPI] " Karol Kozimor
[not found] ` <20030904085315.GA29773-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2003-09-04 9:25 ` Nils Faerber
[not found] ` <1062667556.13465.37.camel-65LrUGLyukAb1SvskN2V4Q@public.gmane.org>
2003-09-04 9:33 ` Karol Kozimor
[not found] ` <Pine.OSF.4.51.0309040921460.337830@tao.natur.cuni.cz>
[not found] ` <Pine.OSF.4.51.0309040921460.337830-xveqDVFKMsx2wEp5G055aaVXKuFTiq87@public.gmane.org>
2003-09-04 9:26 ` Karol Kozimor [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-21 16:15 Martin Mokrejs
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=20030904092627.GA29604@hell.org.pl \
--to=sziwan-detuoxkzssqrdjvtcaxf/a@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=mmokrejs-V2lp6ZUObelkZyP8+xg2CQ@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