ubuntu-eee-coders team mailing list archive

[Adam McDaniel <adam@xxxxxxxxx>]

Are you still getting spammed by pciehp with that message?

By removing both options, pciehp may not be loading (or at least not
doing its job) which is allowing for Fn-F2 wireless toggle commands to
work.  It is safe to leave "pciehp_debug=1" off.

I've already updated the new 'eeepc-config' package to disable that
debug option; however I'm not sure if there's much I can do if those
"Card (not) present on Slot..." messages are spamming.

I cannot actually recreate your problem on my 900, but I do have a
different wireless card (which uses the atl2 module) than yours on the
901. Perhaps it's hardware specific.

-- 
PCIEHP errors when ethernet disabled on eee 901
https://bugs.launchpad.net/bugs/274505
You received this bug notification because you are a member of Ubuntu
Eee Coders, which is subscribed to Ubuntu Eee.

Status in Ubuntu Eee: Incomplete

Bug description:
I recently installed Ubuntu eee 8.04.1 on my Asus eee 901, and as I try to save the battery life as much as possible, I typically keep the ethernet disabled in the BIOS. However, I believe I had it enabled when I installed the OS on it. After about a day of use with everything but the wireless disabled, I got errors when trying to download files because the disk was full. I had put /home on the 16gb partition and the rest of / on the 4gb. When investigating this, I discovered that three log files in /var/log were enormous, syslog, kern.log and messages. I also noticed a repeating pciehp error when starting the notebook, but didn't originally worry about it since it didn't seem to affect anything. After I deleted those log files and reset the machine to get smaller ones (they were each about 700mb) I looked into them and noticed the same errors repeating. I have done some experimentation and determined that the errors only occur when the ethernet is disabled. Those three log files (but much smaller, I copied them very soon after I booted in order to get small ones) are attached to this bug report in a tar.gz.