LinuxQuestions.org - kernel 2.4.26 [bareacpi.i] broken [on asus hardware]?

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - kernel 2.4.26 [bareacpi.i] broken [on asus hardware]? (https://www.linuxquestions.org/questions/slackware-14/kernel-2-4-26-%5Bbareacpi-i%5D-broken-%5Bon-asus-hardware%5D-254397/)

kernel 2.4.26 [bareacpi.i] broken [on asus hardware]?

just installed slack 10 using the bareacpi.i kernel image yesterday on my laptop. something interesting happened, the kevend seems to have ramped up in cpu usage, likely to 100%. I cant tell what the actual cpu usage is, since my sessions even on a local tty start shutting down within half an hour, nevermind ssh sessions from another machine.

now a note, im pretty sure that i ran into this problem with a fedora core desktop system under the same kernel. ive been looking for info on the problem, and a potential fix that DOES NOT not involve recompiling the kernel [tried compiling yesterday, bad exit after cpu usage by keventd ramped up], its simply not an option. [i dont know slack as well as i would like to]. is a replacement image avalible? or would it be better for me to wait for slack 10.1 to hit the streets?

At this point im sure that the kernel is broken, at the very least on the hardware that im using.

the laptop hardware layout can be found here: http://www.linuxquestions.org/hcl/sh...p?product=1473

another note - this could have something to do with ASUS options in the kernel. my home desktop has an ASUS mainboard, and as i mentioned i recall a problem with this install under this same kernel [but under FC1]. heres the general layout.

CPU - Intel P3 1.13A [tulatin core voltages]
MBD - Asus TUV4x-WOA

Code:

$ lspci

00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev c4)

00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP]

00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)

00:04.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C/VT8235 PIPC Bus Master IDE (rev 06)

00:04.2 USB Controller: VIA Technologies, Inc. VT6202 [USB 2.0 controller] (rev 1a)

00:04.3 USB Controller: VIA Technologies, Inc. VT6202 [USB 2.0 controller] (rev 1a)

00:04.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)

00:07.0 Ethernet controller: VIA Technologies, Inc. VT86C100A [Rhine] (rev 06)

00:08.0 Ethernet controller: Linksys Network Everywhere Fast Ethernet 10/100 model NC100 (rev 11)

00:09.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10)

00:0a.0 USB Controller: VIA Technologies, Inc. VT6202 [USB 2.0 controller] (rev 50)

00:0a.1 USB Controller: VIA Technologies, Inc. VT6202 [USB 2.0 controller] (rev 50)

00:0a.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 51)

01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev a1)

this also begs the question, why was this kernel used in the 10.0 release [ or any release on any distro] with such a prevalent problem on well known and well used hardware?

note to other z9000 and LQ-HCL users: the ATi 9100 IGP is detected properly under FC3 and Slack 10.

please excuse the rambinling, ive spent a number of hours working on this so far, and have gotten nowhere.

well, i was pretty close. its the acpi.

dropping 'linux acpi=no' or 'linux noapic' seems to fix the issue. acip=no seems to be the more reliable of the two, but you lose auto shutdown upon running 'poweroff' or 'shutdown'.

Hey -Nw- neX.

The following comes from the Changelog for the 2.4.28 kernel: ChangeLog-2.4.28

Quote:

Len Brown:
o [ACPI] fix ASUS boot crash http://bugzilla.kernel.org/show_bug.cgi?id=2755

There were also some ASUS fixes with the kernel 2.4.27, see Changelog-2.4.27.

So I'd guess that compiling the 2.4.28 kernel would give you acpi support. I'm not an expert of any kind though so it may be wise to check it out. Good luck.

yeah. im going to work on pactching some code in the source tree for the latest 2.4.xx series and see how things go. hopefully this will turn out a successful compile.

happilly tho, this seems to be the only problem and its quite manageable. i was expecting more issues with a laptop with slack, but the only other issue is that my mouse wheel doesnt work, and this is something i can live with. :)

so just some further info/update.

in lilo.conf added the line...

Code:

append = acpi=off

and that seems to fix the keventd problems, but leaves you with no power management.
i also tried append = noapic in lilo.conf, but this just delays the inevetable. no good.

ive given a plain vanilla 2.4.28 compile a try, but still have the keventd problem. again 'append = acpi=off' works to fix the problem, but no power management.

im on to patching the 2.4.28 source with this acpi patch: http://ftp.kernel.org/pub/linux/peop.../acpi/patches/
we shall see how this goes.

thanks to z0ng, our resident slack-hack here at the office for all his slack help.