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!
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!
FS#32837 - [linux] 3.6.7 freezes
Attached to Project:
Arch Linux
Opened by Neil Darlow (neildarlow) - Sunday, 25 November 2012, 09:19 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 23 January 2013, 17:42 GMT
Opened by Neil Darlow (neildarlow) - Sunday, 25 November 2012, 09:19 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 23 January 2013, 17:42 GMT
|
DetailsDescription:
linux-3.6.7-1 freezes without warning. Examining the systemd journal gives no clue. Operation appears normal until the freeze and the only resolution is a power-off of the affected system. I don't think this is Arch-specific as it occurs on Fedora 18 also with the same symptoms. It appears to be one of those bad kernels. Additional info: linux-3.6.7-1 Steps to reproduce: 1) Just run system as normal and it will freeze. |
This task depends upon
video card: This system runs headless and KMS is disabled so we're talking text consoles only. Graphics is ATI Radeon 6310 so it's not bleeding edge.
bad memory: I don't think so. I have used branded memory and it's behaved perfectly during the initial 3 month system burn-in period.
earlier kernels: It has run previous 3.6.x releases without any problems. I've just switched to 3.0.x-lts and it's running that quite happily with no freezes.
I'll also add disk to the equation but we're talking about a software RAID10 mirror. OK there's LVM and Ext4 on top but that's been flawless too.
No, I am more inclined to believe that this is a regression introduced in linux-3.6.7 especially as I see the same thing on the same version of kernel, from a different vendor, on different hardware. The Arch system is AMD Dual Core x86_64 and the other system is Intel Single Core i686.
We shouldn't jump to conclusions that this is hardware related when there is a huge body of code (that is the kernel) which could be causing this.
Anyhow, I'm OK with 3.0.x-lts for now but someone else may be experiencing the same problem so this report should, at least, provide some form of documentation.
I think it was just that particular kernel version. Your kernels are generally rock-solid so I would close this.