Bug 131062 - battery status applet resets laptop
Summary: battery status applet resets laptop
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Dave Jones
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-08-27 01:34 UTC by Jeffrey C. Ollie
Modified: 2015-01-04 22:09 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-04-05 19:08:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
output of 'lshal' on 8/27/04 10:45am CST (37.01 KB, text/plain)
2004-08-27 15:43 UTC, Jeffrey C. Ollie
no flags Details

Description Jeffrey C. Ollie 2004-08-27 01:34:40 UTC
Description of problem:
Adding the battery status applet to panel causes laptop to hard reset.

Version-Release number of selected component (if applicable):
gnome-panel-2.7.91.1-2
kernel-2.6.8-1.526

How reproducible:
100%

Steps to Reproduce:
1. add the battery status applet to the panel
2.
3.
  
Actual results:
Laptop hard resets.

Expected results:
Able to monitor battery status through applet.

Additional info:
Compaq Evo N800c upgraded to latest rawhide as of 8/26/04.

Comment 1 Warren Togami 2004-08-27 07:26:17 UTC
This is a kernel, perhaps ACPI problem.  Can you please provide more
technical specifications about your laptop's chipset, processor,
video, etc.


Comment 2 Jeffrey C. Ollie 2004-08-27 13:28:31 UTC
Processor: Intel Pentium 4 M 2.2Ghz
Chipset: Intel 845 Brookdale
Video: ATI Radeon Mobility M7 LW
Ram: 1GB

Also, I forgot to note that this problem did not occur on 8/25/04,
only after I installed latest rawhide updates from 8/26/04.  SELinux
is disabled as well.

I noticed that there is a BIOS upgrade from HP for the notebook.  I'm
going to give that a try but I have to boot from the Windows XP
partition to install it.

Comment 3 Jeffrey C. Ollie 2004-08-27 13:59:42 UTC
Upgrading the BIOS from F.1D to F.23 and did not fix the problem. 
Going to try and upgrade to rawhide from 8/27/04 to see if that helps.

Comment 4 Jeffrey C. Ollie 2004-08-27 15:40:50 UTC
I upgraded to rawhide as of 8/27/04 and the problem persists.  I also
tried booting into kernel-2.6.8-1.524 and had the same problem.

Comment 5 Jeffrey C. Ollie 2004-08-27 15:43:36 UTC
Created attachment 103167 [details]
output of 'lshal' on 8/27/04 10:45am CST

Comment 6 Jeffrey C. Ollie 2004-08-27 16:01:38 UTC
Hmmm... Running the following command, even as a normal user causes my
laptop to reset:

cat /proc/acpi/battery/C132/state


Comment 7 Jeffrey C. Ollie 2004-08-27 16:20:20 UTC
I also tried the command from a text console to see if I was missing a
kernel oops or something but no luck.  A few seconds after you run the
command the laptop resets, no oops message, no nothin'.

Comment 8 Jeffrey C. Ollie 2004-08-27 16:34:04 UTC
I tried replacing the battery with a battery from a co-worker's laptop
- same problem.

Comment 9 Jeffrey C. Ollie 2004-08-29 19:50:04 UTC
I've now tried with these kernels:

kernel-2.6.7-1.515
kernel-2.6.7-1.517
kernel-2.6.8-1.524
kernel-2.6.8-1.526
kernel-2.6.8-1.532
kernel-2.6.8-1.533

and all will reset the laptop shortly after accessing
"/proc/acpi/battery/C132/state"

I also booted into Windows XP Professional (completely updated except
for SP2) and was able to use XP's battery status panel without any
problems.

Comment 10 Warren Togami 2004-08-29 21:10:17 UTC
Red Hat does not have the time resources to investigate your problem.
 You should go directly to the authors of ACPI on the acpi-devel
mailing list.  Reference this existing report when you report your
problem.

http://acpi.sourceforge.net/
Plenty of details here.

Comment 11 Jeffrey C. Ollie 2004-08-30 00:49:50 UTC
Posted to kernel bugzilla:

http://bugzilla.kernel.org/show_bug.cgi?id=3308

Comment 12 Jeffrey C. Ollie 2005-04-05 19:08:33 UTC
Cleaning up this bug... was resolved with later versions... plus I no longer
have access to the specific laptop that was having the problem.


Note You need to log in before you can comment on or make changes to this bug.