Ubuntu

[Gigabyte GA-870A-USB3] Unable to boot without workarounds

Reported by Grzegorz G. on 2012-06-01
30
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned

Bug Description

My system won't boot. As a side effect of using workaround 1 described below it detects only one CPU core and won't shut down completely, I have to hold power button for few seconds to power PC off. Tested F5g BIOS but no change.

Upstream URL: http://marc.info/?l=linux-acpi&m=136069746628268&w=2

WORKAROUND 1: Boot with acpi=off and nolapic.

WORKAROUND 2: Turn off AMD C1E in the BIOS.

According to https://wiki.ubuntu.com/DebuggingACPI I tried booting it with acpi=ht (also with acpi=ht AND nolapic), but not to avail. Quote: 'If acpi=off works and acpi=ht fails, then the issue is in the ACPI table parsing code itself, or perhaps the SMP code. '

I will also attach files mentioned on the DebuggingACPI wiki page.
---
AcpiTables:

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: elgregor 2200 F.... pulseaudio
 /dev/snd/controlC0: elgregor 2200 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 7'
   Mixer name : 'Realtek ALC889'
   Components : 'HDA:10ec0889,1458a002,00100004'
   Controls : 48
   Simple ctrls : 22
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xfbffc000 irq 11'
   Mixer name : 'Nvidia GPU 16 HDMI/DP'
   Components : 'HDA:10de0016,10de0101,00100100'
   Controls : 24
   Simple ctrls : 4
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=5c04833b-d470-4324-b361-fee89f01b6ba
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
MachineType: Gigabyte Technology Co., Ltd. GA-870A-USB3
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic root=UUID=8d061eaf-912d-4ecf-b035-fd2f8f47c686 ro acpi=off nolapic quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-29-generic N/A
 linux-backports-modules-3.2.0-29-generic N/A
 linux-firmware 1.79
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: precise
Uname: Linux 3.2.0-29-generic x86_64
UpgradeStatus: Upgraded to precise on 2012-04-29 (108 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 10/21/2011
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F5d
dmi.board.name: GA-870A-USB3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5d:bd10/21/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-870A-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-870A-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-870A-USB3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Brad Figg (brad-figg) on 2012-06-01
Changed in linux (Ubuntu):
status: New → Confirmed
tags: added: precise
irrational John (ijohn) wrote :

Not sure if it is relevent or not, but the following messages appear in the attached '/var/log/kern.log.0':

[Firmware Bug]: powernow-k8: No PSB or ACPI _PSS objects
powernow-k8: Make sure that your BIOS is up to date and Cool'N'Quiet support is enabled in BIOS setup

irrational John (ijohn) wrote :

Your attached dmidecode.txt says

BIOS Information
 Vendor: Award Software International, Inc.
 Version: F5d
 Release Date: 10/21/2011

According the Gigabyte web site
http://www.gigabyte.com/products/product-page.aspx?pid=3754#bios
most recent BIOS for GA-870A-USB3 (rev. 3.0) is F4 (2011/03/09)

According the Gigabyte web site
http://www.gigabyte.com/products/product-page.aspx?pid=3788#bios
most recent BIOS for GA-870A-USB3 (rev. 3.1) is F5g (2012/04/30)

I assume your motherboard is revision 3.1, but if you haven't already done so you should verify this.
http://www.gigabyte.com/support-downloads/faq-page.aspx?fid=864

Grzegorz G. (grzesiek1e5) wrote :

Yes, I have revision 3.1. When I checked last time (~2 monts ago) newest bios was F5d. In F5g description it states "Beta BIOS". I'm not sure if upgrading BIOS to beta release is a good idea...

Yes, I saw powernow-k8 warning too. Cool'N'Quiet can't be forced to be enabled. There are only two options: disabled and auto; I have it set to auto.

tags: added: acpi
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.5kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc1-quantal/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-bug-exists-upstream
removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → Confirmed

Grzegorz G., thank you for reporting this and helping make Ubuntu better. With your WORKAROUND in place, could you please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1007508

description: updated
tags: added: needs-kernel-logs
tags: added: kernel-bug-exists-upstream-v3.5-rc1-quantal
Changed in linux (Ubuntu):
status: Confirmed → Incomplete

apport information

tags: added: apport-collected
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

I did it with current Ubuntu kernel. If you want me to do it with 3.2.0.24.26 or newest unstable kernel, tell me.

Grzegorz G., thank you for apport-collect'ing.

Did this problem not happen in a release prior to Precise?

Grzegorz G. (grzesiek1e5) wrote :

It did happen in Oneiric. Other releases not tested. (But it also did happen in Fedora 15 LiveCD and Rescatux.)

Grzegorz G., could you please test for this in Lucid via http://cdimage.ubuntu.com/lucid/daily-live/current/ ?

Grzegorz G. (grzesiek1e5) wrote :

You mean to check if it happens, or you want me to run this command again? Yes, it happens:
- no additional parameters -> won't boot
- acpi=off AND nolapic -> boots (wifi and resolution errors, but it doesn't matter).

Grzegorz G., regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1007508/comments/40 , this problem does happen in Lucid, and requires the WORKAROUNDs acpi=off and nolapic to boot correct?

Grzegorz G. (grzesiek1e5) wrote :

Yes.

tags: added: lucid
removed: needs-kernel-logs

Grzegorz G., anything change if you update your BIOS to F5G via http://www.gigabyte.com/products/product-page.aspx?pid=3788#bios ?

Grzegorz G. (grzesiek1e5) wrote :

I can try, but it's marked as beta.

Rovano (rovano) wrote :

Hi Grzegorz,
dont panic with Gigabyte beta BIOS.
Google translator:
I very much flashed Gigabyte beta bios itself never was a problem, though bios minded, go back to the stable bios.
Go for it. :-)
The truth is that the Gigabyte beta BIOS disclaims responsibility that a person can not complain about errors in the BIOS. On the other hand, beat the BIOS in older boards only way to fix something.

Grzegorz G. (grzesiek1e5) wrote :

It didn't help. I tried booting without any special parameters and it doesn't work. (But I didn't try with only acpi=off or with only nolapic.) I thought photo of screen can help, because kernel complains about some incorrect checksum (as it did before).

Grzegorz G., could you please try with only acpi=off, with only nolapic, and comment on the results?

Grzegorz G. (grzesiek1e5) wrote :

I tried, both doesn't work.

Grzegorz G. (grzesiek1e5) wrote :

Hm, look at this:
http://ubuntuforums.org/showthread.php?p=11414032#post11414032
https://bbs.archlinux.org/viewtopic.php?id=117717
And other, found by Google.

Some people are actually running Linux on this mainboard. IDK if with workarounds or not, maybe we should ask them?

But I've also found threads (in Polish and English) about Linux not booting with this mainboard.

And there is a thread (in Polish) where someone says that he was able to boot linux without any additional params, only by using nomodeset for LiveCD: http://forum.dobreprogramy.pl/instalator-ubuntu-nie-uruchamia-sie-t487193.html (System installed and no GRUB editing was necessary.) I'll try to boot my PC without my workaround, only with nomodeset.

Grzegorz G., regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1007508/comments/49 , this bug report is only focused on your hardware. Hence, what someone said on a forum or a link found from Google is not terribly helpful.

Could you please provide the information following https://wiki.ubuntu.com/DebuggingACPI ?

Grzegorz G. (grzesiek1e5) wrote :

"is not terribly helpful"
Sorry.

"Could you please provide the information following https://wiki.ubuntu.com/DebuggingACPI ?"
Do you mean submitting outputs of those commands? I did. See attachments. Or I have to do this again?

Sorry for not understanding you, but my English isn't very good.

Grzegorz G. (grzesiek1e5) wrote :

Status of this bug is still incomplete. What else do I have to provide?

BTW with this beta BIOS the longest part of boot is displaying BIOS screen :/

summary: - ACPI bug in Precise (generic kernel 3.2.0.24.26)
+ Precise will not boot (generic kernel 3.2.0.24.26)

Grzegorz G., thank you for testing the beta BIOS F5G.

Just to clarify, using the beta BIOS F5G, you undid the WORKAROUND but the computer still hung while booting?

description: updated
Grzegorz G. (grzesiek1e5) wrote :

Yes. Just like it did with previous BIOS.

description: updated
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Grzegorz G. (grzesiek1e5) wrote :

Important info! There is another (perhaps better) workaround: to turn AMD C1E off in BIOS.

So this seems like issue with C1E support under Linux... :(

description: updated
description: updated
Michael Harvey (mcharvey) wrote :

I've been struggling with this for the past 8 months. My setup is very similar:

Mainboard: Gigabyte GA-870A-USB3 rev 3.0
BIOS firmware: F4
Processor: Phenon II X6 1055T
Memory: 8 Gb

I've been experiencing the problem since 11.10. Originally it was intermitent and if I rebooted the system 20+ times I could eventially boot without using "acpi=off". Since upgrading to 12.04 I'm unable to boot without passing the acpi=off parameter. Tried booting with older 2.6.x and 3.X kernels to no avail. Since it was intermitent I assumed it was hardware related but am unable to fix by disabling C1E support.

Grzegorz G. (grzesiek1e5) wrote :

What about changing other power management options? Cool&Quiet, etc.
Also: I have revision 3.1 and bios F5g, so stuff may work differently.
You can register on Gigabyte forum and search (or ask) for help. I found this C1E tip there.

Maybe unrelated, but anyway: kernel complains that it can't load microcode for AMD fam15h processors. I thought about installing amd64-microcode (or amd64-microcodes, I don't remember ATM) package, but I don't really know what are microcodes. Are they loaded into processor (like firmware) or they are only used by kernel until reboot?

Michael Harvey, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

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

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

Michael Harvey (mcharvey) wrote :

I'll file a report and post all the standard files if you think it will help, but this issue happens with other distros as well. Tried to boot into gentoo-2012-minimal boot disc and locks up at same ACPI location. Only way to start is passing the "acpi=off" parameter.

I've tried the bios "fail-safe" settings to no avail, and can't find any combination of bios parameters that works. Looks like I'm hosed for now....

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Grzegorz G. (grzesiek1e5) wrote :

Still not fixed. Won't boot without workarounds.

tags: added: kernel-bug-exists-upstream-v3.8-rc1
removed: kernel-bug-exists-upstream-v3.5-rc1-quantal
tags: added: oneiric
description: updated

Grzegorz G., the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream ?

Thank you for your understanding.

Marking Triaged as newest mainline tested, regression tested through Lucid, and newest BIOS tested.

Changed in linux (Ubuntu):
status: Incomplete → Triaged
summary: - Precise will not boot (generic kernel 3.2.0.24.26)
+ Unable to boot without workarounds

Grzegorz G., regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1007508/comments/63 :
>"OK, if I understand correctly, I should I send mail to this list? http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=MAINTAINERS#l236"

Using the kernel.org format noted in https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Kernel.org_Format you should send a mail to the mailing list <email address hidden> .

Grzegorz G. (grzesiek1e5) wrote :

I was really busy. I will probably do it tomorrow or day after tomorrow.

Grzegorz G., before you send the e-mail out, could you please test the newest mainline kernel available via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc6-raring/ ?

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Grzegorz G. (grzesiek1e5) wrote :

RC6 tested, bug is still present. I have just sent the e-mail.

Grzegorz G., thank you for testing RC6. Could you please test http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc7-raring/ ?

Grzegorz G. (grzesiek1e5) wrote :

OK, but what about the e-mail I've sent? I have CCed it to <email address hidden>. Shouldn't some info about it appear here?

Also can you estimate how long do I have to wait for an answer before filling bug at kernel's bugzilla (as in instructions on Ubuntu wiki).

Grzegorz G. (grzesiek1e5) wrote :

Oh, it has expired one day ago? Good I've thought about visiting this bug report.

*bump to avoid expiration*

IDK when I'll find time to finally do it (maybe somewhere between 29.04 and 05.05), but I'll use newest mainline kernel, so you don't have to link me to it every time. :)

And can you answer questions in my comment above?

tags: added: needs-upstream-testing
removed: acpi kernel-bug-exists-upstream
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
tags: added: outdated-bios-f5g
Grzegorz G. (grzesiek1e5) wrote :

"outdated-bios-f5g"? According to http://www.gigabyte.com/products/product-page.aspx?pid=3788#bios f5g is still the newest version.

Grzegorz G., could you please post the result of the following terminal commands:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Grzegorz G. (grzesiek1e5) wrote :

F5g
04/30/2012

Grzegorz G., thank you for providing the requested information. Could you please undo your WORKAROUNDs, and test the newest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-rc7-saucy/ ?

tags: added: latest-bios-f5g
removed: outdated-bios-f5g
Changed in linux (Ubuntu):
status: Expired → Incomplete
Grzegorz G. (grzesiek1e5) wrote :

I have exams, I'll do it after few days. (And yes, if newer kernel show up in this PPA, I'll use newer one.)

Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Grzegorz G. (grzesiek1e5) wrote :

I have finally forced myself to go back to this bug. Tested with Linux 3.12 rc3 from mainline ppa. AMD C1E set to auto -> can't boot. AMD C1E set to disabled -> boots normally.

I probably should send a mail to the maintainers, but last time I did it, I got no response from them. Maybe I've screwed something with this mail? Can you give me exact mail to send the info?

tags: added: kernel-bug-exists-upstream-v3.12-rc3
removed: kernel-bug-exists-upstream-v3.8-rc1 needs-upstream-testing
summary: - Unable to boot without workarounds
+ [Gigabyte GA-870A-USB3] Unable to boot without workarounds

Grzegorz G., could you please provide a direct URL to your original upstream mailinglist post noted in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1007508/comments/67 ?

Changed in linux (Ubuntu):
status: Expired → Incomplete
description: updated
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Grzegorz G. (grzesiek1e5) wrote :

Post to the mailing list is from more than half of year ago. Should we wait or repost?

Grzegorz G., given how you already mailed what appeared to be the appropriate mailing list with no response, you are welcome to either make a bug report on kernel.org or repost to the mailing list with latest mainline kernel tested (3.12-rc4).

Changed in linux (Ubuntu):
status: Confirmed → Triaged
MicWit (michaelwitten82) wrote :

Can you try a disk for 12.04.3? (http://old-releases.ubuntu.com/releases/precise/) I had a similar issue, and found it happened on Ubuntu 12.04.4 and later, as well as new versions of Lubuntu, but not on Lubuntu 12.04. Tested Ubuntu 12.04.3, and it seems to work. Im guessing it is something in the kernel upgrade that happened 12.04.3 -> 12.04.4. Hope this can help, I would love to get the supported version of 12.04 running on my old sony vaio.

Grzegorz G. (grzesiek1e5) wrote :

@MicWit: I had problems even with 11.10, as you can see in the automatically generated part of the description. Perhaps I should test the newer kernels, but I totally got bored with it and I just use workaround 2: disable AMD C1E. Maybe you should open a separate bug report?

MicWit, 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

To post a comment you must log in.