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#30112 - [linux] 3.3.8 - 3.4.x Random crashes of the system

Attached to Project: Arch Linux
Opened by left (left) - Saturday, 02 June 2012, 14:18 GMT
Last edited by Tom Gundersen (tomegun) - Thursday, 01 November 2012, 23:40 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture i686
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

While doing standard things (e.g. browsing internet, files managing) the system freezes for no apparent reason and then a 'kernel panic' message appears.

Upgrading a few days ago with 'pacman -Syu' started the problem. Prior upgrade was made on 2012.04.15. I tried rolling back kernel version (from 3.3.7-1 to 3.3.1-1) but it didn't help. I couldn't reproduce the bug by doing something specific.

Additional info:
* package version(s)
linux 3.3.7-1
xorg-server 1.12.2-1
xf86-video-ati 6.14.99-1.20120517

* config and/or log files etc.

kernel.log with two examples of kernel crash and a list of the programs upgraded on last upgrade.

System: Arch on i686.
*-core
description: Motherboard
product: M4A88TD-M EVO
vendor: ASUSTeK Computer INC.
*-cpu:0
product: AMD Athlon(tm) II X2 255 Processor
size: 3100MHz
capacity: 3100MHz
*-memory
size: 4GiB
   kernel.log (70.3 KiB)
This task depends upon

Closed by  Tom Gundersen (tomegun)
Thursday, 01 November 2012, 23:40 GMT
Reason for closing:  Fixed
Comment by asy (asypost) - Monday, 04 June 2012, 01:37 GMT
I have the same problem,but on a x86-64 CPU.
Comment by left (left) - Saturday, 09 June 2012, 17:03 GMT
It happened again several times, with the latest kernel (3.3.8-1) too. I only have pics of the kernel panic screen.
   Immag0634.jpg (519.9 KiB)
   Immag0641.jpg (641.2 KiB)
Comment by Tobias Powalowski (tpowa) - Thursday, 21 June 2012, 06:57 GMT
Status on 3.4.x?
Comment by left (left) - Thursday, 21 June 2012, 07:02 GMT
I'm sorry but I won't be able to test it until the end of the month. As soon as I can I'll post if it's solved or not.
Comment by Karol Błażewicz (karol) - Wednesday, 04 July 2012, 18:51 GMT
Status?
Comment by David K. (dcrabs) - Saturday, 28 July 2012, 12:43 GMT
Same problem here with kernel 3.4.6, x86_64 and radeon graphics but intel i7 cpu. (xf86-video-ati 6.14.99-1.20120517)
Comment by Tobias Powalowski (tpowa) - Wednesday, 08 August 2012, 10:57 GMT
Status on 3.5?
Comment by David K. (dcrabs) - Monday, 13 August 2012, 09:08 GMT
Turns out I had a faulty memory module.
Comment by asy (asypost) - Monday, 13 August 2012, 12:40 GMT
Still have problem with kernel 3.4.8,x86_64,Radeon HD 5000M Series,intel i5 cpu.Some time stuck on booting up GDM,my gnome-shell version is 3.4.2
Comment by left (left) - Monday, 27 August 2012, 13:10 GMT
sorry, couldn't reach the PC until now.

Still have this problem after a recent pacman -Syu. Kernel 3.4.9-1 is installed now.
Comment by left (left) - Wednesday, 05 September 2012, 11:49 GMT
I'm now on 3.5.3-1. I used the pc for a few hours then left the system alone idling for like a day or so and nothing happened, then at the first click I made after that it crashed. See kernel.log attached.
   log.txt (5.5 KiB)
Comment by Greg (dolby) - Tuesday, 16 October 2012, 07:50 GMT
Are you still experiencing this with the 3.6 series? Did you make a bug report to the kernel bug tracker?
Comment by left (left) - Wednesday, 17 October 2012, 11:32 GMT
At the moment I'm still on 3.5.4-1 because it never happened again with this release. I'm going to upgrade to 3.6 to see what happens.
No, I didn't. Should I report the bug I had with 3.5.3 or it would be useless, being an older release?
Comment by left (left) - Thursday, 01 November 2012, 18:12 GMT
It still hasn't happened again since the update to 3.6. Several hours and days of uptime without a crash. I guess this report could be closed.

Loading...