User1: User8 ping
User2: hi there
User2: my ubuntu kernel seems to have problems with acpi - nearly every time when my laptop is under heavy use (e.g. reading big files from my external usb disk or burning a cd) it just hangs up with a kernel panic
User2: a shot of the screen can be found here: http://www.marcreichelt.de/misc/kernelpanic.jpg
User2: I tried to deactivate all modules containing the word "acpi", but this didn't fix the problem
User2: I also tried to deactivate acpi on boot, with "acpi=off" as kernel parameter
User2: the result was that the system frozed after approx. 30 seconds after boot time
User2: do you have any ideas? is this a bug in the ubuntu kernel? what can I do?
User3: marc_learning: "acpi_processor_idle" just means that the system wasn't doing anything at the time
User3: But you can check by unloading the "processor" module
User2: back again
User2: hmm
User2: processor depends on speedstep_centrino, and I can't unload that one, because it is in use
User2: but it doesn't say by which module it is used
User4: it's probably used by powernowd or something similar.
User5: No, you can't unload centrino.  mjg59 and I ran into that a week or two ago.  It's thpethul.
User5: The only way I could "unload" it was to not load it in the first place.
User2: k
User2: how can I deactivate it on boot?
User2: so that "processor" and speedstep_centrino aren't started at boot time?
User5: Blacklist them in modprobe.
User2: Mithrandir, I killed powernowd
User5: Alternately, move the files somewhere else so you're sure nothing can load them. :)
User2: moment...
User2: brb
User2: ok, I created the file /etc/hotplug/blacklist.d/asuslaptop-problems and wrote the line "processor" into it
User2: is this correct?
User2: I think it should be
User2: well, I'm going to reboot now
User2: see you in a few minutes
User2: hello again
User2: my module "processor" is still running
User2: even a line in /etc/hotplug/blacklist did not work
User2: you still mean that it would be good to rename the module?
User2: k, I renamed the processor module
User2: brb
User2: hi again
User2: he still loads the module "processor" - but I renamed processor.ko to processor.ko.old... :-/
User2: maybe I have to create a new initrd?
User2: or kernel?
User2: or is there another way to fix my problem?
User2: I would hack myself into the kernel to solve this problem if I would have the time to
User2: the problem seems to be in processor.c
User2: :-(
User2: brr
User2: again a kernel panic
User6: what ubuntu version are you using
User6: blacklists should be under /etc/modprobe.d
User2: Breezy
User2: Kernel: 2.6.12-10-386
User6: yes put it there
User2: moment
User2: makx, how should the blacklist look like?
User2: just a file containing the line "processor"?
User2: ?
User6: blacklist evbug
User6: for example
User2: k
User2: for me it is blacklist processor, then
User2: ok, brb
User2: no, it didn't work
User2: he is still loading the module "processor"
User2: is there a kernel version which does not contain this bug?
User7: heylo
User8: User2 dpkg-reconfigure linux-image-`uname -r`
User8: that will generate a new initramfs
User1: User8 have you had any problems lately with your ae?
User8: none
User8: other than the weird eth0_clashed thing, but that's not particular to ae
User1: User8 check this out... someone in my apartment installed a wireless router with authentication on the same channel as mine and my ae gets a ton of DEAUTH messages from it
User1: this causes klogd to go crazy and take up like 10% cpu
User8: hmm, sounds like softmac actually
User1: if I switch to another channel, I don't get it
User1: oh, really?
User8: maybe I need to turn down the verbosity
User8: the messages I think come from softmac
User1: yeah, dmesg is full of DEAUTH's
User1: it's quite frustrating... so I switched channels
User8: actually, it's right from ieee80211.ko
User9: User8 can you easily tell me when the last update of the hppa patch in 2.6.15 happened?  (was -13 built with the hppa patchset, or without, to be specific...)
User8: I've never applied an hppa patchset per se
User8: I merely got what was there to work
User8: User9 so it's 99% stock 2.6.15 code for hppa, with just one backport for a compat syscall I can't recall off hand
User9: User8 please consider merging the following patches (minimum) from ftp://ftp.parisc-linux.org/patches
User9: diff-2.6.12-rc3-tulip_21142_phyinit, diff-2.6.3-tulip, diff-2.6.6-tulip_stop_rxtx, diff-tulip_phy_reset-03
User9: all 4 are in akpm's tree
User9: those patches make tulip work on modern hardware...  bug exists on hppa as well as some i386 platforms
User2: User8 just leave the processor blacklisted and generate a new initramfs?
User10: what's the current status of the megaraid newgen/legacy patch?
User10: never mind, found it: it's merged upstream.
User9: User8 I'll start working through the hppa patchset to see what makes sense for us to include
User9: as in, what's low-risk and/or hppa specific
User2: ok, I give up
User2: the module 'processor' is still running
User2: maybe I'm just too stupid for this :-/
User8: User2 rm -f the module
User2: hmm
User2: or better mv module module.bak?
User2: ok
User2: root@tux:/lib/modules/2.6.12-10-386/kernel/drivers/acpi # mv processor.ko processor.ko.bak
User2: now I do dpkg-reconfigure linux-image-`uname -r`
User2: hmm
User2: root@tux:/lib/modules/2.6.12-10-386/kernel/drivers/acpi # dpkg-reconfigure linux-image-`uname -r`
User2: Not touching initrd symlinks since we are being reinstalled (2.6.12-10.26)
User2: Not updating image symbolic links since we are being updated (2.6.12-10.26)
User2: it seems that he didn't noticed anything
User2: I have to go
User2: see you
ubuntu-kernel
Ubuntu IRC