Bug 3308 - hard reset after accessing /proc/acpi/battery/C132/state - Evo N800c
Summary: hard reset after accessing /proc/acpi/battery/C132/state - Evo N800c
Status: CLOSED PATCH_ALREADY_AVAILABLE
Alias: None
Product: ACPI
Classification: Unclassified
Component: Power-Battery (show other bugs)
Hardware: i386 Linux
: P2 high
Assignee: Shaohua
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-29 17:30 UTC by jeff
Modified: 2004-11-16 23:02 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.9-rc1-bk4
Subsystem:
Regression: ---
Bisected commit-id:


Attachments
Output of acpidmp (111.89 KB, text/plain)
2004-08-29 17:44 UTC, jeff
Details
Output of dmesg -s40000 (38.46 KB, text/plain)
2004-08-29 17:45 UTC, jeff
Details
Output of dmidecode (9.04 KB, text/plain)
2004-08-29 17:46 UTC, jeff
Details
Output of cat /proc/interrupts (549 bytes, text/plain)
2004-08-29 17:46 UTC, jeff
Details
Output of lspci -vv (8.29 KB, text/plain)
2004-08-29 17:48 UTC, jeff
Details
.config for kernel 2.6.8-1.541 (49.20 KB, text/plain)
2004-09-02 21:36 UTC, jeff
Details

Description jeff 2004-08-29 17:30:36 UTC
Distribution: Fedora Core (development)
Hardware Environment: Compaq Evo N800c
Software Environment:
Problem Description:

Accessing /proc/acpi/battery/C132/state causes laptop to reset.  Tried under
Fedora 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

Laptop does not reset if you boot Windows XP (completely updated except SP2). 
No oops messages or anything in the log.

Steps to reproduce:
As any user (even non-root):

1. cat /proc/acpi/battery/C132/state
2. Wait a few seconds.
3. Laptop resets

Started out as a bug in Red Hat's bugzilla:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=131062
Comment 1 jeff 2004-08-29 17:44:41 UTC
Created attachment 3590 [details]
Output of acpidmp
Comment 2 jeff 2004-08-29 17:45:37 UTC
Created attachment 3591 [details]
Output of dmesg -s40000
Comment 3 jeff 2004-08-29 17:46:17 UTC
Created attachment 3592 [details]
Output of dmidecode
Comment 4 jeff 2004-08-29 17:46:59 UTC
Created attachment 3593 [details]
Output of cat /proc/interrupts
Comment 5 jeff 2004-08-29 17:48:14 UTC
Created attachment 3594 [details]
Output of lspci -vv
Comment 6 Len Brown 2004-09-02 18:54:27 UTC
if you do the access with no window system running,
do you see anything on the (LCD) console?

I don't suppose this model has a serial debug console?

any chance you can reproduce with the latest kernel.org kernel?

please attach the .config being used.
Comment 7 jeff 2004-09-02 21:36:33 UTC
Created attachment 3626 [details]
.config for kernel 2.6.8-1.541
Comment 8 jeff 2004-09-02 21:44:32 UTC
> if you do the access with no window system running,
> do you see anything on the (LCD) console?

No, there's nothing.

> I don't suppose this model has a serial debug console?

No, there's no serial port built in.  I do have a USB->serial converter,
but I haven't seen any evidence that I could use that to debug the kernel.

> any chance you can reproduce with the latest kernel.org kernel?

I'll take a look tomorrow, but the kernel from Fedora Development I'm using is
based upon a very recent kernel snapshot.

> please attach the .config being used.

See previous post.
Comment 9 Len Brown 2004-11-16 22:50:16 UTC
same with 2.6.9-based kernel?
Comment 10 jeff 2004-11-16 23:02:38 UTC
No, the problem does not appear with recent 2.6.9-based kernels from Fedora
Development or the kernel released with Fedora Core 3.

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