[Bug 1372169] Re: random reboot with MSI A78M-E45

2014-11-27 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1372169

[Bug 1372169] Re: random reboot with MSI A78M-E45

2014-09-28 Thread Christopher M. Penalver
Steffen Eibicht, the next step is to fully commit bisect the kernel in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ? ** Tags added: regression-release ** Tags added: needs-bisect ** Changed in: linux (Ubuntu)

[Bug 1372169] Re: random reboot with MSI A78M-E45

2014-09-25 Thread Steffen Eibicht
thanks to User tomtomtom at ubuntuusers.de I got a .iso image of Ubuntu 14.04 with Kernel 3.17-rc6 and could test it in a live environment. The Bug is NOT fixed with Kernel 3.17-rc6. The machine still reboots randomly when using the free radeon driver. ** Tags added: kernel-bug-exists-upstream

[Bug 1372169] Re: random reboot with MSI A78M-E45

2014-09-23 Thread Christopher M. Penalver
Steffen Eibicht, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional

[Bug 1372169] Re: random reboot with MSI A78M-E45

2014-09-23 Thread Steffen Eibicht
unfortunatetly I can't do that. The affected machine is a production machine. It is now running fine since the fglrx module is installed. Installing the new Kernel means a risk of breaking it for other reasons and it means uninstalling the fglrx module for testing (otherwise it wouldn't make

[Bug 1372169] Re: random reboot with MSI A78M-E45

2014-09-21 Thread Steffen Eibicht
after having thought about this a little bit, I would like to write down as much information as I can. I wrote randomly because it really is randomly. This means, the user can not determine a reason for these reboots. There is no obvious connection between something the user does and the