Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#14823 - [kernel26] panic due apci

Attached to Project: Arch Linux
Opened by F. Bogo the III. (fogobogo) - Monday, 25 May 2009, 11:13 GMT
Last edited by Allan McRae (Allan) - Sunday, 26 July 2009, 14:23 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

kernel .29 causes kernel panic. I'd love to provide a log but when it happens I have: 1. no Input at all. this includes the power button. 2. AC *and* battery need to be removed to get that damn thing off. Of course that isnt particularly helpful to get a log.

However, lucky me I was on a vc when it happened and thourougly reading the kernel message there whilst ignoring the blinking leds lead to the following result:

as it seems acpi_battery_full_state fails for some reason. this would explain the seemingly random panics as well.

battery full > acpi fails > panic!

on this occasion i'd like to point out that that the changelog for the kernel build wasnt very helpful here, and this is the reason the bug is here and not upstream. I have no idea if or not some work was done on kernel compilation.

Additional info:
Name : kernel26
Version : 2.6.29.4-1
kernel: Linux kirin 2.6.29-ARCH #1 SMP PREEMPT Wed May 20 07:06:02 UTC 2009 i686 Mobile AMD Sempron(tm) Processor 2600+ AuthenticAMD GNU/Linux

note: i had the same trouble with 2.6.29.3

lspci:
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 760/M760 Host (rev 03)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SG86C202
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS963 [MuTIOL Media IO] (rev 25)
00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
00:02.6 Modem: Silicon Integrated Systems [SiS] AC'97 Modem Controller (rev a0)
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] AC'97 Sound Controller (rev a0)
00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f)
00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f)
00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 91)
00:06.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link)
00:09.0 CardBus bridge: O2 Micro, Inc. OZ711M1/MC1 4-in-1 MemoryCardBus Controller (rev 20)
00:09.1 CardBus bridge: O2 Micro, Inc. OZ711M1/MC1 4-in-1 MemoryCardBus Controller (rev 20)
00:09.2 System peripheral: O2 Micro, Inc. OZ711Mx 4-in-1 MemoryCardBus Accelerator
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter

Steps to reproduce: wait until battery is fully charged and hope for a kernel panic. ensure you are not using X. kernel panic might let LED blink in beautiful patterns

to be honest I doubt anyone else has that trouble. feel free to close/delete that bug then

This task depends upon

Closed by  Allan McRae (Allan)
Sunday, 26 July 2009, 14:23 GMT
Reason for closing:  Upstream
Additional comments about closing:  No response from submitter to requests for further information
Comment by F. Bogo the III. (fogobogo) - Monday, 25 May 2009, 11:18 GMT
WORKAROUNDS:

1. this is kinda important. running acpid seems to prevent it by leaving the battery state to charging all the time. i have no idea why.
2. downgrade kernel
3. havent tested it yet but acpi=off in the kernel line should help
4. use no battery at all (?)
Comment by F. Bogo the III. (fogobogo) - Monday, 25 May 2009, 11:20 GMT
oh yes. if you need any additional info say so. i might need a bit to fulfill requests there though.
if this is better reported upstream say so too
Comment by F. Bogo the III. (fogobogo) - Monday, 25 May 2009, 13:03 GMT
update: updating the kernel headers to 2.6.29.3-1 _seems_ to have fixed it. why? i dont know! rebooted without acpid and cat /proc/acpi/battery/BAT0/state reports charged. only time will prove whether it this caused the issue
Comment by Jan de Groot (JGC) - Monday, 25 May 2009, 15:42 GMT
The headers don't change anything on a running system, they only affect the compilation of programs.
Comment by F. Bogo the III. (fogobogo) - Tuesday, 26 May 2009, 12:15 GMT
indeed. was a bit of a desperate hope. kernel panicked > downgraded to .28 and hoping for better times. (.30)
Comment by Thomas Bächler (brain0) - Wednesday, 27 May 2009, 13:27 GMT
Possible workaround would be to blacklist the battery module in rc.conf (although you have no battery charge info then). Also, you have to capture the panic log using a camera or write it down when it's on screen, otherwise there is nothing anyone can do.
Comment by Jan de Groot (JGC) - Monday, 15 June 2009, 19:15 GMT
What's the status with 2.6.30?

Loading...