Ubuntu 14.04 suddenly reboots when booting from Live USB AMD A8 6600k

[Sangeet Khatri]

*PLEASE READ FIRST BEFORE MAKING COMMENTS*
Please be advised if you are not the original reporter Sangeet Khatri, making comments here (ex. "I also have this problem on Ubuntu..") are not helpful, and will delay your problem from being addressed. This report is not scoped to you, your hardware, or your problem, and will not address it. If you want your problem addressed, instead file a new report via a terminal if possible:
ubuntu-bug linux

Otherwise use https://bugs.launchpad.net/ubuntu/+source/linux/+filebug .
*END*

I have a custom built AMD System with the following hardware currently running on Linux Mint 16 :

AMD A8 6600k with Integrated graphics | MSI-FM2-A55M-E33 Motherboard | Kingston Hyperx Blu 4GB RAM | Corsair VS450 PSU

Today when I tried to install 14.04 amd64 iso using a bootable USB, then the system rebooted. Any further attempts in installing it resulted in the same bug. As soon as I open the "Ubuntu installer" application and click "Continue" button then the system restarts after 2-3 seconds.

I asked the same on AskUbuntu and some more guys reported the same problem with AMD APU, so I believe it to be a genuine bug and not just with me.

The BIOS version is the latest one downloaded from MSI official website which is version 11.5.

Also an Interesting thing is that this bug is common with the latest iso of Arch Linux too, but when booting older distros like Linux Mint 16 from USB, then everything works like it should, so it might have something to do with the newer 3.13 Kernel version.

I am not an expert, but I can surely tell that only the newer distros are affected by this bug as reported by some other guys at AskUbuntu and the fact that Arch which is running the newer Kernel is having the same bug, so it probably has something to do with the newer Kernel, but I could be wrong.

This bug is not letting me install Ubuntu 14.04 on my hardware and it is affecting a few more users too. Here is the AskUbuntu thread : http://askubuntu.com/questions/449391/unable-to-install-ubuntu-14-04-pc-restarts-after-i-click-continue-button-in

I hope this gets fixed soon or with the 14.04.1 upcoming July release.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1309578/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Sangeet Khatri (sangeet-khatri)]

@crichton The problem is that there is no package I know of that is causing this bug. Whenever I boot 14.04 from USB, the Ubuntu itself is very unstable and reloads while doing some little things like changing the settings or Opening the Hard Disk folder and worst of all, while installing. So, this is a bug not related to a specific package but it is affecting the whole Ubuntu 14.04 release.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Marc Panlilio (jugglerobot-deactivatedaccount)]

Not trying to be an expert here, but this might help others too so here I am. So I am having the same issues here as well trying to install Ubuntu 14.04 LTS on a Live USB. I am using an "Trinity" APU model here. I have used a kernel commandline "noacpi" in GRUB edit menu, just get these logs. Here's my hardware, just incase if it's needed:

AMD A6-5400k Trinity APU | AMD Radeon HD 7540D "AMD ARUBA" | MSI FM2-A55M-E33 Motherboard | Kingston DDR3 1333 RAM | Corsair VS450 PSU

[Ader (rasmusrim)]

I am now trying to install Ubuntu on a manually created partition. I am running gparted from the USB, and try to create a new partition. That is not possible, since there are already four primary partitions. I assume that the automatic install (install inside windows 7) also needs to create a partition. Could this be the problem?

[Eric Harris-Braun (zippy)]

I am seeing the same problem using an MSI A88XI motherboard; an AMD A6 5400K processor; patriot DDR3 RAM.

[Sangeet Khatri (sangeet-khatri)]

Looks like this bug primarily affects MSI Motherboards or AMD APUs in general. Some guys from AskUbuntu reported the same.

[Muhfi Asbin Sagala (muhfiasbin)]

This problem affects me too. I am trying to install Ubuntu 14.04 both from USB or DVD and get this experience.

Processor AMD A8-5600K
Motherboard MSI FM2-A75MA-P33
Corsair Vengeance DDR3 8GB (2x4GB) Dual Channel

[Sangeet Khatri (sangeet-khatri)]

It would be safe to assume that this bug primarily affects MSI boards. We all should watch out for a BIOS update from MSI.

[gerst (gerst)]

I got the same problem, running MSI motherboard with AMD A8-5600K CPU

[gerst (gerst)]

I`ve forgot to add It was a 64bit edition of Ubuntu 14.04. Previously I was running Manjaro 64-bit with no problem.

[Sangeet Khatri (sangeet-khatri)]

Something in the 3.13 Kernel and older is affecting MSI boards, because Arch is also a no go. I haven't tested things other than Ubuntu and Arch though. The bug lies in the very Kernel (probably).

[Muhfi Asbin Sagala (muhfiasbin)]

I have tried another workaround, but this cause a lot of pain for me.
First, I install Ubuntu 13.10 Saucy Salamander then upgrade it to Ubuntu 14.04 Trusty Tahr. Upgrade process was succes. But, when my computer boot, it restart after shown Login Screen and it happen over and over.

I tried accessing root console from recovery mode, then run command apt-get update && apt-get upgrade. It's update the kernel from 3.13.0.24.28 to 3.13.0.24.29. I reboot and my computer still restart over and over.

I tried install fglrx-updates from recovery mode and reboot again. Now, my computer is fine.

[gerst (gerst)]

I`ve managed somehow to install 14.04, it didn`t restart itself...I`ve tried about 10 times when finally suceeded :) But after when I reach the login screen it restarts... :(

[Sangeet Khatri (sangeet-khatri)]

Issues like these should be fixed soon in a LTS release since so many people use AMD APUs these days because they are so cheap and are perfect for Linux boxes as they have inbuilt graphics and very good connectivity for A75 and higher chipset boards.

[Marc Panlilio (jugglerobot-deactivatedaccount)]

Well I also have my own workaround, but seems complicated. I finally installed Ubuntu 14.04 successfully using this, but the problem is my PC won't shutdown if this is applied in the kernel boot parameters. I've added "acpi=off" on the GRUB configurations, which is located in /etc/default/grub

Also, when I click Shutdown in the right upper gears button, it will reboot instead! Not shutdown! Lol what the he**!

I can confirm, this is a problem in the kernel. Something with the "ACPI" drivers, or may be not.. Again, I'm not trying to BE an expert here. I also tried using the latest trusty 3.14.0 kernel from Ubuntu Kernel PPA's:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-trusty/

No luck! :(

[gerst (gerst)]

I didn`t expect such a big bug in LTS...

[Алхимов Александр (aleks-nl5)]

This problem affects me too. I am trying to install Ubuntu 14.04 from USB and PC reboot's after 3-5 min work in live mode.

Processor AMD A4-4000
Motherboard MSI FM2-A75IA-E53
Kingstone DDR3 2GB

[Incze GASPAR (inczegaspar)]

Bug appears on MSI A88XM-E35 + AMD A8-5600K 3.60GHz FM2 BOX, older kernel works OK.

[gerst (gerst)]

14.04 LTS fail...

[Sangeet Khatri (sangeet-khatri)]

@gerst : 14.04 is not a fail by any means, it is just that currently we are unable to run it on our hardware, with a bug fix or perhaps a BIOS update from MSI, things would be alright again.

Meanwhile 14.04 flies on my Intel's Core2Duo laptop. It is pretty awesome.

[gerst (gerst)]

We are talking about LTS release, and this is a pretty nasty bug, making 14.04 useless for many people.

[gerst (gerst)]

These kind of a errors should be fixed fast, not waiting for weeks...

[Per Engström (per-10823-n)]

One of my PC:s is also affected by this bug!

I have a PC with MSI FM2-A55-E33 motherboard and a AMD A4-5300 APU, 4GB RAM.

Ubuntu 14.04 LTS 64-bit does not work on it either. Boot from Live-DVD fails after half boot-up, screen goes black and after approx 5-8 seconds the computer reboots and locks at EFI GRUB.

Any other recent Ubuntu works on this computer, the exception being U 14.04 LTS 64-bit. If I do a fresh U13.10 install it all works great, but if I do a dist upgrade from that U 13.10 to U 14.04 LTS the installation process works fine, but after the finalizing reboot it crashes seconds after the 14.04 Login screen appear, reboots and goes into locked mode at EFI GRUB. Hard Power Off is requiered.

I have reverted to U 13.10 on this machine for the time being while a fix is developed by some of you Ubuntu wizards..

/Per in Sweden

ps. I have another PC with a MSI motherboard, FM2-A85XA-G65, a AMD A10-6800K APU and 8GB RAM. But it seems to be working, did a dist upgrade from U 13.10 to U 14.04 LTS and it has not crashed yet after a couple of days. It starts, reboots and functions apparantly as normal.

[Blake (getechdirect)]

I have an ASROCK FM2A88X-ITX+ with a A10-5800k and this has not affected me although I installed the beta 2 from usb, not sure if this helps narrow it down. Yall should try to install one of the betas and see if you still get the same issue, if not compare kernel changes.

[jonathan green (jonathangreen)]

This bug seems to be causing me problems. Updated from 13.10 to 14.04 and now my PC reboots every time I try to boot into Ubuntu. I am running ubuntu server. It seems to pop up randomly, sometimes I only get part way through the boot sequence, and sometimes I even get to the login prompt, but then it always reboots.

It reboots if I choose Kernel 3.13, but not if I choose kernel 3.11 or 3.13 recovery mode. My system configuration:
AMD A8-5500
MSI A88XM-E35

[Sangeet Khatri (sangeet-khatri)]

@Blake : Well.. it is interesting to know that it is not affecting Asrock boards. I doubt that the problem is limited to MSI boards. Unable to install Arch as well which has 3.14 Kernel.

[jonathan green (jonathangreen)]

FYI: I was able to fix this by passing radeon.dpm = 0 to the kernel.

[Sangeet Khatri (sangeet-khatri)]

But the APU graphics are of the 7xxx and 8xxx series. Not 6xxx.

They probably are based on same architecture. Maybe that's why. But the title of that bug should be renamed to "Kernel 3.13 still broken on Radeon HD based desktops and laptops." and removing the 6xxx because they are not the only one affected.

[penalvch (penalvch)]

Sangeet Khatri, could you please boot into a live environment of a release prior to Trusty via http://releases.ubuntu.com/ and advise if this is reproducible?

[Алхимов Александр (aleks-nl5)]

I think I found a solution of this problem - when boot from USB or DVD you must edit boot options & add this:
radeon.dpm=0
Now I can not install the produce, but by the end of the day I think I'll check.

[Sangeet Khatri (sangeet-khatri)]

@Christopher M. Penalver : I am currently running Linux Mint 16 which as we all know is based on 13.10 release of Ubuntu, so it works fine with the 13.10 or say Mint 16. But the problem lies thus far with 14.04 only. As I have stated earlier, I tried to install Arch as a quick alternative, but that wasn't possible either as it was affected by the same rebooting bug.

I am no expert but I am a geek and can work his way around Linux at times with a reasonable amount of guidance, so please guide me on how could I help.

By the way, looks like my Hard Disk is about to fail so installing distros is not really an option at this point of time. Will soon move to SSD though.

[cb (news-v)]

Same Problem here. I moved Kubuntu 12.04 from old PC to this new PC, runs without problem but needed to upgrade to 12.10 because of a softwareproblem. 12.10 also runs without problems.
Because upgrade to 13.10 did not work I installed 14.04 new from USB, install reboots every few seconds, no matter if I press any button, try to install or just wait, a few seconds after boot it reboots.

Adding radeon.dpm=0 to boot options solved installer. After install kubuntu reboots again after a few seconds. Adding radeon.dpm=0 to grub-boot-line starts ok. Now added radeon.dpm=0 to grub-conf

Hardware:
MSI A78M-E35 (MS-7721) and AMD A4-4020 APU with Radeon(tm) HD Graphics

Also addes dmesg.1.gz from first boot without radeon.dpm=0

Hope this helps somehow, have PC only till tomorrow, it's from my neighbour

[Алхимов Александр (aleks-nl5)]

Christopher M. Penalver, et now I finish my testing ;) (talking about x64 assembly)

1. Freshly downloaded image Ubuntu 13.10 & run him from LiveUSB - OK
2. Install from LiveUSB Ubuntu 13.10 - OK
3. Boot, full update & work about 1-2 hour in cleanest Ubntu 13.10 - OK
4. Update from clean 13.10 to 14.04 - OK
5!. Boot in 14.04 - FAIL (constant rebooting)
6. Add to GRUB boot option radeon.dpm=0 & next boot 14.04, work about 1-2 hours - OK
7!. Boot from LiveUSB 14.04 & try to install - FAIL (constant rebooting)
8. Add radeon.dpm=0 in boot option in LiveUSB 14.04 & try to install - OK
9!. Boot to this installation - FAIL (constant rebooting)
10. Add to GRUB boot option radeon.dpm=0 & next boot 14.04, work about 0,5 hour - OK

Remind my accessories: AMD A4-4000, MSI FM2-A75IA-E53, Kingston DDR3 2GB

[jose (o1485726)]

This is a know bug:
http://www.phoronix.com/forums/showthread.php?99344-Canonical-Is-Taking-Over-Linux-3-13-Kernel-Maintenance&p=413333#post413333
https://bugs.freedesktop.org/show_bug.cgi?id=72921
There is a patch there if you want to test.

[jose (o1485726)]

(I'm not completely sure about my previous comment, though)
also, if you want to try another solution, download and install a newer kernel, 3.14 or 3.15 from http://kernel.ubuntu.com/~kernel-ppa/mainline/

[Marc Panlilio (jugglerobot-deactivatedaccount)]

jose,
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309578/comments/22

... I also tried using the latest trusty 3.14.0 kernel from Ubuntu Kernel PPA's:http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-trusty/

No luck! :(

[penalvch (penalvch)]

Алхимов Александр / cb / jose / Marc Panlilio, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Sangeet Khatri (sangeet-khatri)]

@jose (o1485726) : Well.. if you notice closely, then I was the same guy to report this to the Phoronix forums, but currently I am really stuck as my HDD has almost stopped working. Bad Luck as I won't be able to do any testing at this point of time.

[Michael Murphy (mmstick)]

I was also the person who replied and reported the bug twice here on launchpad and once on bugzilla. OP, I have the exact same hardware as you in a Richland APU machine off-site. Richland APU's use Northern Islands graphics chips (Radeon HD 6000 desktop cards) and are of course completely broken with DPM. Kernel maintainers have disabled DPM by default in kernel 3.14+ because they realized it was completely broken, but for some reason they never disabled it during 3.13 development release (you'd think maintainers of the code would have tested their code before they pushed the patches), so those newer kernels will work fine. As long as you edit grub on the ISO and edit etc/default/grub as well as boot/grub/grub.cfg on the install before rebooting after installing it, everything will work fine.

[Sangeet Khatri (sangeet-khatri)]

I hope Mint launches with this bug fixed since it is also going to be based on 14.04

[Ader (rasmusrim)]

I have now tried with radeon.dpm=0, but it did not work :(

[Ader (rasmusrim)]

I now tried with the 32-bit version of Ubuntu. That did not work either.

I also tried upgrading to kernel 3.15, but there were some errors in the upgrade and the USB-stick was not able to boot afterwards.

[penalvch (penalvch)]

Ader, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Ader (rasmusrim)]

What do you mean by repository kernel? What is the difference?

Rasmus

[Sangeet Khatri (sangeet-khatri)]

Why is this bug still marked as incomplete. Don't we have enough detail about the bug and whom it is affecting to?

[penalvch (penalvch)]

Sangeet Khatri, for regression testing purposes, could you please test the initial Precise release (not Mint) via http://old-releases.ubuntu.com/releases/12.04.0/ and advise on if is reproducible in the live environment?

[Ader (rasmusrim)]

Penalvc: If I boot into the live USB as is without changing anything after creating it, do I then have a mainline or a repository kernel?

[Sangeet Khatri (sangeet-khatri)]

@Christoopher M. Penalver : I have already told you guys previously that my hard disk has failed and I am unable to test the distros. I have only two pen drives both of them are being used for something or the other, so currently I am unable to test the dsitros in any way.

Since this bug is affecting many other users, so I think this should be confirmed by now. Many people have reported that 13.10 worked fine but 14.04 isn't. I am really not in a state to test it as my HDD is dead and both of my pen drives are busy. One is running Linux Mint 16 and other is running Puppy Precise 5.7.1, so I just don't have enough resources to test the OS.

[GS (guido86)]

I have the same problem. First time bootscreen told me about some problems with udev. Now he restarts before i can see the screen. Maybe a coincidence. Maybe it helps.

[penalvch (penalvch)]

Guido Schaidl, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Sangeet Khatri (sangeet-khatri)]

Subscribe me too in the new bug report.

[Rick Forberg (rforberg-g)]

Same problem! Here’s the workaround I found. Hopefully my efforts will assist someone else, and point to a permanent fix.

Hardware:
Mobo: MSI A78-E35
BIOS: E77221AMS V30.2
Build Date: 02/21/2014
CPU: AMD A8-5600K APU with Radeon HD Graphics
Mem: ADATA XPG V1.0 DDR3 1600, 8GB
PS: 680W

(Installing Ubuntu 14.04 server from CD but assume the results would be the same via USB load)

After reading a post somewhere where the writer thought that the issue might be related to an “inactivity” timer and said he had some level of success with continuously moving his mouse during boot, I tried some combinations of this and have been able to boot and make a stable environment to work in. Being a complete Noob to all of this, I am not sure exactly why this works, but it is repeatable and might help lead to something that would help sort this out.

I was able to run through the entire server load process by continuously moving my mouse during the entire process. Yes you need to type and make selections to configure your server while constantly moving the mouse, and no I didn’t try stopping because I wanted to get it loaded. It went flawlessly! A real PITA, but it worked.

Next I found that I was able to boot by holding one of the <SHIFT> keys the entire time the system is booting, but I get varying results. Seems like about 4 out of 5 times through the boot process, I am presented with a small font login prompt to my server. As soon as I release the <SHIFT> key the system reloads and it’s time to hold the shift key again.

About the 5th time through, I get a text menu that looks like this:
*Ubuntu
 Advanced options for Ubuntu
 Memory test (memtest86+)
 Memory test (memtest86+, serial console 115200)

When this text menu appears, you can release the shift key and work without holding it throughout the rest of the process. Now, if I just select Ubuntu, I go back into the boot loop. Hold the shift again!

In the Advanced Options menu, I get two options;
*Ubuntu with Linux 3.13.0-24-generic
 Ubuntu with Linux 3.13.0-24-generic (recovery mode)

Selecting the Non-Recovery option takes me back to the boot loop, but selecting the Recovery Mode option gives me a colored text Recovery menu with eight options, all of which seem work with no problem. At this point I select the first option, <resume>, and <ok> on the following screen that warns that “graphic drivers require a full graphical boot and so will fail when resuming from recovery”.

Now my server (RIX-ubuntu1) boots to a large font prompt:
Ubuntu 14.04 LTS RIX-ubuntu1 tty1
RIX-ubuntu1 login:

At this point I am able to login normally and the server will run without issue until it loses power, needs to be reloaded for maintenance, or any other reason you might have. This looks like a work–around, not a fix but it has allowed me to work in 14.04 without any other issues.

I would love to know if this is repeatable for anyone else, and if some of you smarter more experienced users can use this to further refine the quest for a fix. Enjoy!

[penalvch (penalvch)]

Rick Forberg, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Pete Rio (pete-rio-pr)]

Same issue here as reported above, both on Xubuntu 14.04 LTS 64 bit live USB and fully installed desktop, and also Ubuntu 14.04 LTS 64 bit live USB, running on custom MSI A55m-E33 with AMD A6 and 2x4GB DDR 1600.

Fortunately adding "radeon.dpm=0" to GRUB command line seems to have solved the rebooting issue on Xubuntu 14.04 64 bit installed on pc, with latest stable kernel 3.14.4.

Have not tested the live USB versions.

It might be noteworthy that I also have Lubuntu 14.04 32 bit installed on a separate drive and it runs flawlessly - I've had many issues with Xubuntu and graphics in the past, but for some reason Lubuntu never complains.

[penalvch (penalvch)]

Pete Rio, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Kelvin González (kelvin-gonzalezvivas)]

Could this reported bug in Ubuntu 12.04.4 LTS be the same here?

https://bugs.launchpad.net/ubuntu/+source/linux-lts-saucy/+bug/1280668

[magnusfranklin (magnus-f)]

Workaround! For noobs like me, who just need to get the thing to work and don't want to root around obscure system settings, this did the trick: reverting to the Saucy Salamander kernel.

apt-get install linux-image-generic-lts-saucy

... assuming it's in the cache after an upgrade, should be simple.

All the new features in 14.04 seem to work, just stops the eternal restart process.

[penalvch (penalvch)]

Kelvin Gonzalez, regarding your comment:
>"Could this reported bug in Ubuntu 12.04.4 LTS be the same here?"

At this point, because the original reporter hasn't apport-collect'ed, nor attached any debug logs, this report has nothing to do with yours. If you want your problem addressed, you will want to make comments in your own bug report, not someone elses, and provide the information previously requested of you in https://bugs.launchpad.net/ubuntu/+source/linux-lts-saucy/+bug/1280668/comments/3 .

magnusfranklin, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Martin Zuther (mzuther)]

I tried muhfi-asbin's solution (thanks for that!). After booting into recovery mode, I installed "fglrx-updates" and rebooted. So far, my computer seems to be fine.

Martin

CPU: AMD A4-4000
Mainboard: MSI MS-7721
Memory: 2GiB DDR3-1333
Graphics card: ATI Radeon HD 7480D

[penalvch (penalvch)]

Martin Zuther, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Ian (superian)]

I have the problem of 14.04 getting to the desktop then crashing to a reboot after a few seconds.

Both have MSI-FM2-A55M-E33 motherboards but the AMD APUs differ (one's an A8, one an A6).

The cure for me, spotted elsewhere here, is to add

nomodeset

to the boot options.

[penalvch (penalvch)]

Ian, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[michael (mymail21)]

I was also affected by this bug, it is related to some FM2 motherboards , MSI being one of them.
The fix for this bug is to edit your GRUB file BEFORE you restart your system after updating.
If you did a clean install from a live cd you will have to use f6 during boot and select "noapic" and if that fails try again and select"acpi=off"

You will still need to edit your grub file after boot up to make it permanent.
from the terminal type; gedit /etc/default/grub

The file will open in the editor.
edit this line GRUB_CMDLINE_LINUX_DEFAULT="quiet splash '

to look like this; GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"

then save and exit, you are done..., enjoy!

[Soma sundaram (poketmonister)]

Probable FiX..........

problem:
My ubuntu 14.04 installer restarted when i clicked install along side windows.
after some research i wanted to check it i could reproduce it in 12.04, and yes my installer restarted when i clicked install along side windows.
I think it is the same case with Linux Mint 16 as sangeet khatri reported.

Solution:
Ubuntu does not support dynamic disks, please recheck if ur disk is dynamic, and convert it to basic disk.

to minimise data loss,

i created a new ext 4 partition with gparted and installed ubuntu 14.04 there.(gparted only makes Basic disks).
grub was not installed.
so i reinstalled the grub using live cd.

I am posting this from my new ubuntu 14.04..... ;)

[penalvch (penalvch)]

Soma sundaram, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Ian (superian)]

"The problem cannot be reported:

E:Encountered a section with no Package: header, E:Problem with MergeList /var/lib/apt/lists/repository.spotify.com_dists_stable_non-free_i18n_Translation-en%5fGB, E:The package lists or status file could not be parsed or opened."

With the Spotify line commented out of /etc/apt/sources.list it works, and I will add you to it when it finally is ready.

[Rick Robinson (robinsontech)]

Solution to my problem - (Thank you Rick Forberg!)
Linux Mint 17 Qiana won't install - keeps rebooting. It doesn't matter if the installation medium is a flash drive or CD. Once the live version loads it immediately reboots. There isn't enough time to install it. Once I managed to actually install it after dozens of tries. The result was it would get to the login, accept my credentials then reboot before actually loading. Thankfully after reading several of the posts on this page I was able to work out a procedure to install the OS, then fix the issue for my MSI desktops.

Most of the Desktops at work running Linux Mint are custom built MSI boards with the following configurations:
Motherboard: MSI A78M-E45
BIOS: AMI BIOS 25.1 (2013-12-09) & 25.3 (2014-03-19)
APU: AMD A10-5800K (quad core) Trinity 3.8 GHz
RAM: Patriot Viper DDR3 2133 (PC3 17000) 4x4GB

and

Motherboard: MSI FM2-A55M-E33
BIOS: E7721AMS v11.4 (2013-10-23)
APU: AMD A8-5600K (quad core) 3.60GHz
RAM: HyperX DDR3 1600 (PC3 12800) 2x4GB

Both desktop configurations had the same problem. They were running Linux Mint 15 and 16. I have now replaced some of them with Qiana 17. Installing Linux Mint 17 on them had been a problem. Here is what I did to fix it:

Once the live version started to load I kept the mouse constantly moving with one hand. With the other hand, using the keyboard, I started the installation utility and answered all the questions for the installation (I kept the mouse moving the entire time). Once the installation was finished the utility requested a restart. When the OS restarted I kept the mouse moving again, put in my login credentials and when Mint loaded I launched the terminal with <ctr>+<alt>+t.

In the terminal I updated the advanced packaging tool: apt-get update && apt-get upgrade
(This takes quite a while, but it is important to keep the mouse moving the entire time)

Then, I updated the display drivers: apt-get install fglrx-updates
(you will need to prepend these commands with sudo if you are not root when you run them)

After the the two commands (above) finished. I restarted the desktop and installation on the desktop has been stable ever since. This is true of all the desktops (configurations above). I hope this post will be helpful to anyone having problems with MSI motherboards. They are my systemboards of choice and I am very grateful to all the contributors of this forum. Your posts and insights have made this fix possible.

[penalvch (penalvch)]

Rick Robinson, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Matt (mdinger-bugzilla)]

This bug should be here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309578/comments/42 as reported in comment 42 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309578/comments/42).

The bug is marked fixed and a patch has landed in kernel 3.16-rc7 here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=730a336c33a3398d65896e8ee3ef9f5679fe30a9 so this should be fixed in kernel 3.16. I didn't see it fixed in any other kernels.

[Bib (bybeu)]

MSI a88xm-e35 (7721) bios v30.2 (mode legacy+uefi)
The problem was workaround adding nomodeset at install time (F6). I flashed later to v30.3 but didn't try further tests.

[penalvch (penalvch)]

Matt / Bib, thank you for your comment. Unfortunately, this bug report is not scoped to you, or your problem. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Bib (bybeu)]

Thank you Christopher: this is done: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1355044

[Adam Mikitzel (adam-mikitzel)]

I too have the endless boot loop with mythbuntu 14.04 using AMD A6 Radeon HD 8470D
Temporarily fixed to give me a working system by adding acpi=off in grub parameters.

[Adam Mikitzel (adam-mikitzel)]

Just an update, I have upgraded to kernel 3.15.5 and removed grub option acpi=off. The system no longer reboots during a session, but it will not shut down! Instead of shutting down it reboots...

[penalvch (penalvch)]

Adam Mikitzel, thank you for your comment. Unfortunately, this bug report is not scoped to you, or your problem. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you have created another bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Kamil Demecki (skajotde)]

The title of that bug should be renamed to "Kernel 3.13 still broken on Radeon HD based desktops and laptops" like Sangeet is suggesting. I used option "Install new hardware support" on 12.04 LTS and I my system started rebooting because this step installed kernel 3.13. Important side-effect was scanning disc drive everytime after reboot (cancelling didn't help as drive coudn't be mounted).

Similar problem I found during installing fresh 14.04.01 - during starint X server for isntaller my computer is rebooted.

My system - Motherboard: MSI FM2-A55M-E33 (MS-7721), CPU: AMD A10-5700 APU, GPU: [AMD/ATI] Trinity [Radeon HD 7660D]

Bug is opened 4 months for 14.04 but at least user experience it upfront but I don't understand why you are introducing this LEVEL of bug in 12.04 LTS if it is already known.

[Matt (mdinger-bugzilla)]

@Kamil Demecki: Reportedly fixed in Kernel 3.16. See comment #77. So it would be a problem at least for 3.13-3.15.

[Ben Dunn (bdunn)]

I too am currently having the same problem. custom build - MSI FM2-A75IA-E53, A8 6600K apu, 4gb Gskill, and OCZ ssd.
Constant reboot after instalation.
It will not restart as long as my mouse is moving.... weird but true.
Finally installed.
Running 14.04 AMD64

It hasn't restarted in an hour. Hopefully it stays stable :D

[panther44 (billconiston)]

I too have encountered this problem,

Hardware
AMD A6-6400K APU dual core cpu
MSI M'board - A88XM-E35 (FM2)
4gb Corsair value 1600mhz
PNY 120GB SSD

This is a bizarre bug and I have changed RAM and reseated CPU as I thought it was hardware related.

Anyhow following the advice above, I kept the mouse moving throughout the install and managed to get it
installed fine, then reboot I then updated the grub as advised above to:
"GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"
then ran "sudo update-grub"
But I still have the random reboot issues?

Any other ideas? This has been a real headache to solve, I wonder how many boards have been returned as people wrongly assume this is hardware?
Is it possible to upgrade the kernel to 3.16 manually?

Thanks for all the helpful posts above,

I have created a thread here to:
http://ubuntuforums.org/showthread.php?t=2239591

[Ben Dunn (bdunn)]

@panther44
I have no idea... glad the mouse thing worked tho lol.

[Vladimir Skvortsov (vskvortsoff)]

I have a notebook with Intel i5 cpu and Intel HD integrated graphics but I have an issue with sudden restart using live usb as well.

[Matt (mdinger-bugzilla)]

It seems that Ubuntu daily is on kernel 3.16 now so (not certain though). It would be a good test to try installing one of the daily live CD's to see if they still reboot automatically because it's supposed to be fixed with 3.16. Also run `uname -a` in the terminal to check which kernel is being used.

These are daily builds and not meant for production so take care when using them. I found the daily live ISOs linked from http://www.phoronix.com/scan.php?page=news_item&px=MTc2NzI

http://cdimage.ubuntu.com/daily-live/current/

[panther44 (billconiston)]

My issues were fixed by changing the graphics driver under the additional drivers programme to: fglrx
(not updates - that still didn't work for me)

Did not require a reboot to start using and no problems since switching - quick fix for anyone else having the same issues,

[penalvch (penalvch)]

Kamil Demecki / Ben Dunn / panther44 / Vladimir Skvortsov / Matt, thank you for your comment. Unfortunately, this bug report is not scoped to you, or your problem. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Yuv (yuv)]

and another one: bug 1367064

[Ader (rasmusrim)]

Hi!
I just tried to upgrade the kernel on my live USB to 3.16. I then rebooted, but I got an intramfs error "Unable to find a medium containing a live file system". How to get past that problem?

[Ader (rasmusrim)]

Clarification: I did this to test if the rebooting problem persists.

[Ader (rasmusrim)]

I just downloaded the latest build of Saucy Salamander to test that version, and the exact same problem occurs there. So this might actually be an older issue.

[penalvch (penalvch)]

Ader, this is the wrong venue for your issue. Please use the support tracker for troubleshooting -> https://answers.launchpad.net/ubuntu/+addquestion

[Ader (rasmusrim)]

I just tried to install Utoppic Unicorn alpha with kernel 3.16, but the problem persists even there :(

[penalvch (penalvch)]

Ader, thank you for your comment. Unfortunately, this bug report is not scoped to you, or your problem. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Phillip (phil-acomposer)]

I have an AMD A8-6600K/MSI G71 FM2 Board. I was getting the reboot loop when installing 14.04 LTS. I used a workaround for this problem. I will explain below in noob terms.
1. install ubuntu. Keep your mouse moving the whole time and you will get through the install. It's tough but you can do it.
2. Once ubuntu is installed, reboot and press F6 during the motherboard screen to bring up ubuntu boot options
3. boot with low graphics and networking.
4. in low graphics mode, open firefox and download the appropriate graphics drivers from AMD for your PC. Install them and reboot back into low graphics mode with networking
5. open terminal and type: "sudo gedit /etc/default/grub" and Look for this text: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
6. Edit this section of code to read as follows: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic radeon.dpm=0"
7. save changes
8. you should now be able to boot in normal graphics mode.

This workaround took me a while to figure out as I'm newer to ubuntu as an operating system, but it has been stable running constantly at full 1080p graphics for four days now without a single crash or error. Hopefully this works for more than just my system.

[Phillip (phil-acomposer)]

whoops sorry my motherboard is an MSI A78M-E35 FM2/2+ board

[Phillip (phil-acomposer)]

And when I say "low graphics mode" I mean "Ubuntu, with Linux 3.13.0-xx-generic (Recovery Mode)" and then on the next menu with the pink background choose the "network -- Enable networking" option. It should boot into 1024x768 and it shouldn't enter the reboot loop.

[penalvch (penalvch)]

Phillip, thank you for your comment. Unfortunately, this bug report is not scoped to you, or your problem. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Bib (bybeu)]

Bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1355044 fully bissected.
Please Sangeet, do the same with your machine so we have a chance to see a backport in Trusty.

Bye

[asheeq subratty (asheeqsubratty)]

FIXED restarting problems - I think it was a graphics driver Isssue

CPU: AMD APU A86500 3.5ghz
MOBO: MSI A78M-E35
2x4gb DDR3 RAM HyperX blu 1866mhz
Asus HD6670 1GB DDR5 discrete graphics card

OLD HDD:
Ubuntu 12.04 64 bit on Mushkin 60gb SSD
Windows 7 Home Premium 64 bit on Seagate 320 GB HDD 7200rpm

NEW SSHD
SSHD Seagate Hybrid drive 1TB
O/S : Dual boot Windows 7 home premium 64 bit, Ubuntu 14.04 64bit

Hi there, i am a casual user of Ubuntu since 2010 with dual boot of Windows in almost all of my systems. I have used Ubuntu 10.04, 12.04, and now 14.04. I am a newbie in techinical terms, so please excuse the lack of clarity.

Initially i had problems installing Ubuntu 14.04 on the above new built in May 2014 alongside windows 7, both live cd and usb would load to install screen and restart constantly. After a few installation trials i gave up. however i successfully installed Ubuntu 12.04 64bit on the SSD and ran it for months no major issues, and my windows 7 boted fine on the normal hdd Today i wanted to upgrade to 14.04 as i migrated both my OS to my new SSHD Seagate 1TB, my SSD started to fail and i sent it back to Muskin, good after sales service, still waiting for replacement. Had to do boot repair for the old dual boot though, worked fine after that.

It installed fine after a couple of installation trials when it would just restart automatically. Then during the post installation things to do it kept restarting numerous times. So I restarted on safe mode Linux 3.13.0-xx-generic (Recovery Mode), then booted with normal mode, when to additional drivers, unselected 'Using X.org X AMD/ATI display driver wrapper from xerver-xorg-video-ati (open source, tested)', then selected the last option at the bottom 'Using Video driver for the AMD graphics accelarators from fglrx-updates (proprietary)', rebooted and voila, problem fixed so far. I have been using it now for four hours and no restarting at all, cannot speak for longer term, i will post back daily to confirm or correct.

Good luck...

[asheeq subratty (asheeqsubratty)]

ps, no issues with my Windows 7, i use my Asus discrete graphics card as Dual graphics enabled with my APU, so the DVI cable is connected to the MOBO and not the GPU, dunno if this has any significance, jsut thought to mention that.

good luck, and sorry if this isn't the same problem, i couldn't read all the comments, please feel free to advise...

[Steffen Eibicht (steffeneibicht-deactivatedaccount)]

this Bug also affects a customers machine, equipped with a MSI A78M-E45 mainboard with an AMD A4-4000 APU.

This Bug is not in Ubuntu Precise with the 3.2 Kernel. So I first installed Ubuntu 12.04, installed the fglrx-driver via Jockey and then upgraded to Trusty. Up to now, the system runs without random reboot.

Conclusion:

1. the bug occurs in Kernel 3.13 and the free radeon driver

2. the bug does obviously not occur in Kernel 3.13 if fglrx is installed

3. the bug does not occur in Kernel 3.2 with the free radeon driver

4. the bug does not occur in Kernel 3.2 with fglrx installed

Have you talked to MSI and AMD about this issue? Is there any activity going on regarding this ridiculous Bug? Will it ever be fixed or will it survive a whole LTS-cycle and maybe another one (because in Kernel 3.16 it reportedly also occurs)?

Is there anything, we as users can provide to help you fixing this bug? Logfiles? What can we do to help?

[Matt (mdinger-bugzilla)]

Correction: I don't know where you heard but this should be fixed in 3.16. If you are referring to comment #94, he has a different issue. That isn't this bug.

[penalvch (penalvch)]

Steffen Eibicht, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[[e-mail] (mirko-guarnier)]

I am going to add myself to the long list of affected user, maybe more info will help.

I could reproduce the reboot issue in two cases:
1) live xubuntu 14.04 Usb while trying to install but also just trying it out ( always reboot after the login screen)
2) booting directly from the hard disk with xubuntu 14.04 already installed (previous pc) ( reboots after the language selection)

Motherboard: Msi a78m-e35
Cpu+gpu: Amd a8 5600k

[penalvch (penalvch)]

<email address hidden>, adding yourself to affected users is simply not helpful. If you want to be helpful, and so your hardware and problem may be tracked, please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Matt (mdinger-bugzilla)]

Seems fixed for 14.10 which is expected. This will probably be fixed automatically with 14.04.2 so the developers probably won't touch this bug. See the link for more details:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1355044/comments/33

[penalvch (penalvch)]

Matt, please again see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309578/comments/92 . If you an want a fix backported to an earlier release, you would need to follow the directions previously outlined to you, not post "Me too!" comments, or speculate on what you think will or won't be fixed, and by whom. Otherwise, nobody is going to focus on your problem.

[Ed Campbell (jazcam)]

My system similar to those mentioned here:
MB: A55M-E33
cpu: AMD A4 6300
ram: HyperX DDR3 1866 2x4GB

I really didn't have much trouble installing Linux Mint 17 from USB stick. However after install is when the rebooting started. I concur with most of what Rick Robinson said in comment #75. My solution as well was the fglrx-updates driver. However one of the first things I will always do on a new build is to install Google Chrome. I noticed that as long as I had Chrome running there were no reboots. As soon as I would close Chrome, the machine would reboot as if on queue. Possibly the same with the default browser in Mint, Firefox. I don't know that for sure because I only kept it running long enough to download/install Chrome.

I thought maybe that would be true as long as some application was running. I tried running LibreOffice Writer in the background, but it had no effect.

[penalvch (penalvch)]

Ed Campbell, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Ader (rasmusrim)]

Has anyone checked if this bug still persists in kernel 3.18?

[robin Wilkin (wilkinrobin)]

Mint 17.1 does not solve the problem. It is extremely disapointing that this issue has not been solved. Why does 16 work and 17 does not?

[Bay Collie (baycollie)]

Also had this problem with an AMD A8-5600 and MSI A78M-E35 Motherboard. The .iso would reboot before getting to the desktop screen. Finally found a solution.
    When booting the .iso image and the keyboard icon appeared at bottom of screen, I pressed any key to enter the options menu. Selected F6 - other options and then selected acpi=off. The .iso then booted without rebooting itself before it got to the desktop, and installed OK. After 14.04 amd64 was installed, the fact that acpi was set to acpi=off in the grub.cfg file was keeping my computer from shutting down properly, so I set it back to acpi=on in the grub.cfg file. Then my shutdown worked properly.

[Tom Van Nostrand (digitalskillz)]

I was having the endless reboot problem with my USB memory stick installing Ubuntu 14.04.
I forget how I built my bootable USB stick, but I just burned the .ISO to a DVD and booted with that. Problem solved.

So I think it's the certain tool people are using to make their USB sticks from the .ISO that's the culprit here.
Maybe there's a common denominator here?

[Ader (rasmusrim)]

I now tried booting from a DVD without luck. I have also tried acpi=off with no luck. I even tried that hard-to-believe trick with the mouse with no luck. Any chance this bug is fixed any time soon? Is there anything more I can do to help?

[penalvch (penalvch)]

Ader, it would help immensely if you filed a new report with a working prior release via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

If for whatever reason there is no prior release, please use as a last resort https://bugs.launchpad.net/ubuntu/+source/linux/+filebug .

[Ader (rasmusrim)]

Now I tried with radeon.dpm=0 and when the installer rebooted, it gave me the Ubuntu logo with the text "Remove media and press [ENTER]" or something like that. Could it be that the installer thinks that it is actually done with the installation when it has in fact done nothing? I will now install Precise and upgrade to Utopic. Hope that works!

[Ader (rasmusrim)]

Precise did not work either. What on earth can I do to install Ubuntu?

[John Tindle (jwtindle)]

A bit late in the day, but the 14.04LTS install fails on my system too, except if I edit the boot line at CD start up, adding "acpi=off". Then it starts sweet as a nut. Oh my system is a AMD A8 6600k with Integrated graphics | MSI-FM2-A55M-E33 Motherboard

I will add comments on system usability when the install finishes

[Bib (bybeu)]

Same issue with a MSI A88XME35 with latest BIOS (V30.6) in Ubuntu 16.04.3 LTS kernel 4.4.0-112-generic #135-Ubuntu.

Only nomodeset with free driver, or radeon.dpm=0 with proprietary driver prevent boot loop

[penalvch (penalvch)]

Bib (bybeu), it will help immensely if you use the computer the problem is reproducible with, and provide necessary debugging logs by filing a new report with Ubuntu via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

[Bib (bybeu)]

Hi Christopher. Done as you asked.
Have a good day

[Bib (bybeu)]

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746357