[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Bug Watch Updater]

Launchpad has imported 28 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=194825.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2017-03-09T11:15:45+00:00 fiedzia wrote:

Created attachment 255151
kernel config

I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
and it has a load of problems, starting with not being able to boot normally.

During normal boot, on 16.10 as well as 17.04 beta:
system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
messages displayed.

Following advice from various places, I've tried to:

1. add "acpi=off" to boot params

That helps, allowing me to boot into recovery mode, though it leaves me
with system seeing only one core, is really slow and still only boots in
recovery mode.

2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and
cpu handling in acpi settings. Boot with "quiet loglevel=3" option.

That gets me even further - system sees all cores now. Still only recovery mode 
though,
but its enough to get info for this bug report.

Some observed problems:

1. dmesg reports *a lot* of messages like this all the time:

[ 163.362068] ->handle_irq(): 87a7e090,
[ 163.362081] bad_chained_irq+0x0/0x40
[ 163.362089] ->handle_irq(): 87a7e090,
[ 163.362090] amd_gpio_irq_handler+0x0/0x200
[ 163.362090] ->irq_data.chip(): 88587e20,
[ 163.362090] ioapic_ir_chip+0x0/0x120
[ 163.362090] ->action(): 884601c0
[ 163.362091] IRQ_NOPROBE set
[ 163.362099] ->handle_irq(): 87a7e090,
[ 163.362099] amd_gpio_irq_handler+0x0/0x200
[ 163.362100] ->irq_data.chip(): 88587e20,
[ 163.362100] ioapic_ir_chip+0x0/0x120
[ 163.362101] ->action(): 884601c0

I've tried to redirect dmesg to a file, stopped after a short while, it
generated 400M of those.

2. Systemd cannot start journald. Perhaps because it cannot cope with
amount of kernel logs?

3. Looking at pci, I've noticed something called AMDI0040
(/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel
and google are completely silent about AMDI0040.

Phoronix tested ryzen using different motherboard, and it worked better (though 
not well),
so I suspect it is an issue with motherboard.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/3


On 2017-03-09T11:17:14+00:00 fiedzia wrote:

Created attachment 255153
lspci_vv_nn

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/4


On 2017-03-09T11:17:58+00:00 fiedzia wrote:

Created attachment 255155
dmidecode

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/5


On 2017-03-09T11:18:41+00:00 fiedzia wrote:

Created attachment 255157
find_sys_bus_acpi

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/6


On 2017-03-09T11:19:23+00:00 fiedzia wrote:

Created attachment 255159
content of /sys/bus/acpi/devices/AMDI0040

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/7


On 2017-03-10T09:25:21+00:00 fiedzia wrote:

I've found a workaround (requires compiling own kernel, tested on 4.11
and r4.11rc1):

When configuring kernel (I used make menuconfig) disable following
things:

Everything under device drivers/gpio support, especially:
memory mapped files/amd promontory support (GPIO_AMDPT)
and pci gpio expanders / amd 8111 gpio driver (GPIO_AMD8111)
but I've turned of everything to make sure nothing is using gpio.

device drivers / pin controllers / amd gpio pin control (PINCTRL_AMD)

Perhaps only one of them could be really necessary, but I didn't tested
that.

System boots normally, no problems with journald and no weird messages
from dmesg.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/13


On 2017-03-13T09:04:55+00:00 fiedzia wrote:

>tested on 4.11 and r4.11rc1

Should be "tested on 4.10 and r4.11rc"

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/comments/28


On 2017-05-09T21:02:38+00:00 jonnyboysmithy wrote:

Link to what appears to be the same bug over at the ubuntu launchpad
site: 

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Bug Watch Updater]

** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[LCID Fire]

I encountered a similar or same problem on Gigabyte AB350 with Ubuntu 16.04 
running `4.13.0-21-generic #24~16.04.1-Ubuntu SMP Mon Dec 18 19:39:31 UTC 
2017`. It even shows up on 18.04 Alpha.
Only thing that makes it halfway work is setting `acpi=off`.

Isn't this supposed to be fixed by now?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Kai-Heng Feng]

Ok, Artful live image (the pending one) uses 4.10.0-26.30 now. If you
still can't boot, then it should be another issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Kai-Heng Feng]

Artful should switch to linux kernel 4.11 pretty soon.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-26.30

---
linux (4.10.0-26.30) zesty; urgency=low

  * linux: 4.10.0-26.30 -proposed tracker (LP: #1700528)

  * CVE-2017-1000364
- Revert "UBUNTU: SAUCE: mm: Only expand stack if guard area is hit"
- Revert "mm: do not collapse stack gap into THP"
- Revert "mm: enlarge stack guard gap"
- mm: larger stack guard gap, between vmas
- mm: fix new crash in unmapped_area_topdown()
- Allow stack to grow up to address space limit

linux (4.10.0-25.29) zesty; urgency=low

  * linux: 4.10.0-25.29 -proposed tracker (LP: #1699028)

  * CVE-2017-1000364
- SAUCE: mm: Only expand stack if guard area is hit

  * CVE-2017-9074
- ipv6: Prevent overrun when parsing v6 header options
- ipv6: Check ip6_find_1stfragopt() return value properly.

  * [Zesty] QDF2400 ARM64 server - NMI watchdog: BUG: soft lockup - CPU#8 stuck
for 22s!  (LP: #1680549)
- iommu/dma: Stop getting dma_32bit_pfn wrong
- iommu/dma: Implement PCI allocation optimisation
- iommu/dma: Convert to address-based allocation
- iommu/dma: Clean up MSI IOVA allocation
- iommu/dma: Plumb in the per-CPU IOVA caches
- iommu/iova: Fix underflow bug in __alloc_and_insert_iova_range

  * Zesty update to 4.10.17 stable release (LP: #1692898)
- xen: adjust early dom0 p2m handling to xen hypervisor behavior
- target: Fix compare_and_write_callback handling for non GOOD status
- target/fileio: Fix zero-length READ and WRITE handling
- iscsi-target: Set session_fall_back_to_erl0 when forcing reinstatement
- usb: xhci: bInterval quirk for TI TUSB73x0
- usb: host: xhci: print correct command ring address
- USB: serial: ftdi_sio: add device ID for Microsemi/Arrow SF2PLUS Dev Kit
- USB: Proper handling of Race Condition when two USB class drivers try to
  call init_usb_class simultaneously
- USB: Revert "cdc-wdm: fix "out-of-sync" due to missing notifications"
- staging: vt6656: use off stack for in buffer USB transfers.
- staging: vt6656: use off stack for out buffer USB transfers.
- staging: gdm724x: gdm_mux: fix use-after-free on module unload
- staging: wilc1000: Fix problem with wrong vif index
- staging: comedi: jr3_pci: fix possible null pointer dereference
- staging: comedi: jr3_pci: cope with jiffies wraparound
- usb: misc: add missing continue in switch
- usb: gadget: legacy gadgets are optional
- usb: Make sure usb/phy/of gets built-in
- usb: hub: Fix error loop seen after hub communication errors
- usb: hub: Do not attempt to autosuspend disconnected devices
- x86/boot: Fix BSS corruption/overwrite bug in early x86 kernel startup
- selftests/x86/ldt_gdt_32: Work around a glibc sigaction() bug
- x86, pmem: Fix cache flushing for iovec write < 8 bytes
- um: Fix PTRACE_POKEUSER on x86_64
- perf/x86: Fix Broadwell-EP DRAM RAPL events
- KVM: x86: fix user triggerable warning in kvm_apic_accept_events()
- KVM: arm/arm64: fix races in kvm_psci_vcpu_on
- arm64: KVM: Fix decoding of Rt/Rt2 when trapping AArch32 CP accesses
- block: fix blk_integrity_register to use template's interval_exp if not 0
- crypto: s5p-sss - Close possible race for completed requests
- crypto: algif_aead - Require setkey before accept(2)
- crypto: ccp - Use only the relevant interrupt bits
- crypto: ccp - Disable interrupts early on unload
- crypto: ccp - Change ISR handler method for a v3 CCP
- crypto: ccp - Change ISR handler method for a v5 CCP
- dm crypt: rewrite (wipe) key in crypto layer using random data
- dm era: save spacemap metadata root after the pre-commit
- dm rq: check blk_mq_register_dev() return value in
  dm_mq_init_request_queue()
- dm thin: fix a memory leak when passing discard bio down
- vfio/type1: Remove locked page accounting workqueue
- iov_iter: don't revert iov buffer if csum error
- IB/core: Fix sysfs registration error flow
- IB/core: For multicast functions, verify that LIDs are multicast LIDs
- IB/IPoIB: ibX: failed to create mcg debug file
- IB/mlx4: Fix ib device initialization error flow
- IB/mlx4: Reduce SRIOV multicast cleanup warning message to debug level
- IB/hfi1: Prevent kernel QP post send hard lockups
- perf auxtrace: Fix no_size logic in addr_filter__resolve_kernel_syms()
- perf annotate s390: Fix perf annotate error -95 (4.10 regression)
- perf annotate s390: Implement jump types for perf annotate
- jbd2: fix dbench4 performance regression for 'nobarrier' mounts
- ext4: evict inline data when writing to memory map
- orangefs: fix bounds check for listxattr
- orangefs: clean up oversize xattr validation
- orangefs: do not set getattr_time on orangefs_lookup
- orangefs: do not check possibly stale size on truncate
- fs/xattr.c: zero out memory copied to userspace in getxattr
- ceph: fix memory 

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Kai-Heng Feng]

When Artful (17.10) switch to 4.11, the daily image will also get new
kernel.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Christos]

Will this fix be implemented in the downloadable daily images? I have
downloaded the most recently modified (29/06/2017) and kernel 4.10.0-22
is still in use.

Thanks

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-26.30

---
linux (4.10.0-26.30) zesty; urgency=low

  * linux: 4.10.0-26.30 -proposed tracker (LP: #1700528)

  * CVE-2017-1000364
- Revert "UBUNTU: SAUCE: mm: Only expand stack if guard area is hit"
- Revert "mm: do not collapse stack gap into THP"
- Revert "mm: enlarge stack guard gap"
- mm: larger stack guard gap, between vmas
- mm: fix new crash in unmapped_area_topdown()
- Allow stack to grow up to address space limit

linux (4.10.0-25.29) zesty; urgency=low

  * linux: 4.10.0-25.29 -proposed tracker (LP: #1699028)

  * CVE-2017-1000364
- SAUCE: mm: Only expand stack if guard area is hit

  * CVE-2017-9074
- ipv6: Prevent overrun when parsing v6 header options
- ipv6: Check ip6_find_1stfragopt() return value properly.

  * [Zesty] QDF2400 ARM64 server - NMI watchdog: BUG: soft lockup - CPU#8 stuck
for 22s!  (LP: #1680549)
- iommu/dma: Stop getting dma_32bit_pfn wrong
- iommu/dma: Implement PCI allocation optimisation
- iommu/dma: Convert to address-based allocation
- iommu/dma: Clean up MSI IOVA allocation
- iommu/dma: Plumb in the per-CPU IOVA caches
- iommu/iova: Fix underflow bug in __alloc_and_insert_iova_range

  * Zesty update to 4.10.17 stable release (LP: #1692898)
- xen: adjust early dom0 p2m handling to xen hypervisor behavior
- target: Fix compare_and_write_callback handling for non GOOD status
- target/fileio: Fix zero-length READ and WRITE handling
- iscsi-target: Set session_fall_back_to_erl0 when forcing reinstatement
- usb: xhci: bInterval quirk for TI TUSB73x0
- usb: host: xhci: print correct command ring address
- USB: serial: ftdi_sio: add device ID for Microsemi/Arrow SF2PLUS Dev Kit
- USB: Proper handling of Race Condition when two USB class drivers try to
  call init_usb_class simultaneously
- USB: Revert "cdc-wdm: fix "out-of-sync" due to missing notifications"
- staging: vt6656: use off stack for in buffer USB transfers.
- staging: vt6656: use off stack for out buffer USB transfers.
- staging: gdm724x: gdm_mux: fix use-after-free on module unload
- staging: wilc1000: Fix problem with wrong vif index
- staging: comedi: jr3_pci: fix possible null pointer dereference
- staging: comedi: jr3_pci: cope with jiffies wraparound
- usb: misc: add missing continue in switch
- usb: gadget: legacy gadgets are optional
- usb: Make sure usb/phy/of gets built-in
- usb: hub: Fix error loop seen after hub communication errors
- usb: hub: Do not attempt to autosuspend disconnected devices
- x86/boot: Fix BSS corruption/overwrite bug in early x86 kernel startup
- selftests/x86/ldt_gdt_32: Work around a glibc sigaction() bug
- x86, pmem: Fix cache flushing for iovec write < 8 bytes
- um: Fix PTRACE_POKEUSER on x86_64
- perf/x86: Fix Broadwell-EP DRAM RAPL events
- KVM: x86: fix user triggerable warning in kvm_apic_accept_events()
- KVM: arm/arm64: fix races in kvm_psci_vcpu_on
- arm64: KVM: Fix decoding of Rt/Rt2 when trapping AArch32 CP accesses
- block: fix blk_integrity_register to use template's interval_exp if not 0
- crypto: s5p-sss - Close possible race for completed requests
- crypto: algif_aead - Require setkey before accept(2)
- crypto: ccp - Use only the relevant interrupt bits
- crypto: ccp - Disable interrupts early on unload
- crypto: ccp - Change ISR handler method for a v3 CCP
- crypto: ccp - Change ISR handler method for a v5 CCP
- dm crypt: rewrite (wipe) key in crypto layer using random data
- dm era: save spacemap metadata root after the pre-commit
- dm rq: check blk_mq_register_dev() return value in
  dm_mq_init_request_queue()
- dm thin: fix a memory leak when passing discard bio down
- vfio/type1: Remove locked page accounting workqueue
- iov_iter: don't revert iov buffer if csum error
- IB/core: Fix sysfs registration error flow
- IB/core: For multicast functions, verify that LIDs are multicast LIDs
- IB/IPoIB: ibX: failed to create mcg debug file
- IB/mlx4: Fix ib device initialization error flow
- IB/mlx4: Reduce SRIOV multicast cleanup warning message to debug level
- IB/hfi1: Prevent kernel QP post send hard lockups
- perf auxtrace: Fix no_size logic in addr_filter__resolve_kernel_syms()
- perf annotate s390: Fix perf annotate error -95 (4.10 regression)
- perf annotate s390: Implement jump types for perf annotate
- jbd2: fix dbench4 performance regression for 'nobarrier' mounts
- ext4: evict inline data when writing to memory map
- orangefs: fix bounds check for listxattr
- orangefs: clean up oversize xattr validation
- orangefs: do not set getattr_time on orangefs_lookup
- orangefs: do not check possibly stale size on truncate
- fs/xattr.c: zero out memory copied to userspace in getxattr
- ceph: fix memory 

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-26.30

---
linux (4.10.0-26.30) zesty; urgency=low

  * linux: 4.10.0-26.30 -proposed tracker (LP: #1700528)

  * CVE-2017-1000364
- Revert "UBUNTU: SAUCE: mm: Only expand stack if guard area is hit"
- Revert "mm: do not collapse stack gap into THP"
- Revert "mm: enlarge stack guard gap"
- mm: larger stack guard gap, between vmas
- mm: fix new crash in unmapped_area_topdown()
- Allow stack to grow up to address space limit

linux (4.10.0-25.29) zesty; urgency=low

  * linux: 4.10.0-25.29 -proposed tracker (LP: #1699028)

  * CVE-2017-1000364
- SAUCE: mm: Only expand stack if guard area is hit

  * CVE-2017-9074
- ipv6: Prevent overrun when parsing v6 header options
- ipv6: Check ip6_find_1stfragopt() return value properly.

  * [Zesty] QDF2400 ARM64 server - NMI watchdog: BUG: soft lockup - CPU#8 stuck
for 22s!  (LP: #1680549)
- iommu/dma: Stop getting dma_32bit_pfn wrong
- iommu/dma: Implement PCI allocation optimisation
- iommu/dma: Convert to address-based allocation
- iommu/dma: Clean up MSI IOVA allocation
- iommu/dma: Plumb in the per-CPU IOVA caches
- iommu/iova: Fix underflow bug in __alloc_and_insert_iova_range

  * Zesty update to 4.10.17 stable release (LP: #1692898)
- xen: adjust early dom0 p2m handling to xen hypervisor behavior
- target: Fix compare_and_write_callback handling for non GOOD status
- target/fileio: Fix zero-length READ and WRITE handling
- iscsi-target: Set session_fall_back_to_erl0 when forcing reinstatement
- usb: xhci: bInterval quirk for TI TUSB73x0
- usb: host: xhci: print correct command ring address
- USB: serial: ftdi_sio: add device ID for Microsemi/Arrow SF2PLUS Dev Kit
- USB: Proper handling of Race Condition when two USB class drivers try to
  call init_usb_class simultaneously
- USB: Revert "cdc-wdm: fix "out-of-sync" due to missing notifications"
- staging: vt6656: use off stack for in buffer USB transfers.
- staging: vt6656: use off stack for out buffer USB transfers.
- staging: gdm724x: gdm_mux: fix use-after-free on module unload
- staging: wilc1000: Fix problem with wrong vif index
- staging: comedi: jr3_pci: fix possible null pointer dereference
- staging: comedi: jr3_pci: cope with jiffies wraparound
- usb: misc: add missing continue in switch
- usb: gadget: legacy gadgets are optional
- usb: Make sure usb/phy/of gets built-in
- usb: hub: Fix error loop seen after hub communication errors
- usb: hub: Do not attempt to autosuspend disconnected devices
- x86/boot: Fix BSS corruption/overwrite bug in early x86 kernel startup
- selftests/x86/ldt_gdt_32: Work around a glibc sigaction() bug
- x86, pmem: Fix cache flushing for iovec write < 8 bytes
- um: Fix PTRACE_POKEUSER on x86_64
- perf/x86: Fix Broadwell-EP DRAM RAPL events
- KVM: x86: fix user triggerable warning in kvm_apic_accept_events()
- KVM: arm/arm64: fix races in kvm_psci_vcpu_on
- arm64: KVM: Fix decoding of Rt/Rt2 when trapping AArch32 CP accesses
- block: fix blk_integrity_register to use template's interval_exp if not 0
- crypto: s5p-sss - Close possible race for completed requests
- crypto: algif_aead - Require setkey before accept(2)
- crypto: ccp - Use only the relevant interrupt bits
- crypto: ccp - Disable interrupts early on unload
- crypto: ccp - Change ISR handler method for a v3 CCP
- crypto: ccp - Change ISR handler method for a v5 CCP
- dm crypt: rewrite (wipe) key in crypto layer using random data
- dm era: save spacemap metadata root after the pre-commit
- dm rq: check blk_mq_register_dev() return value in
  dm_mq_init_request_queue()
- dm thin: fix a memory leak when passing discard bio down
- vfio/type1: Remove locked page accounting workqueue
- iov_iter: don't revert iov buffer if csum error
- IB/core: Fix sysfs registration error flow
- IB/core: For multicast functions, verify that LIDs are multicast LIDs
- IB/IPoIB: ibX: failed to create mcg debug file
- IB/mlx4: Fix ib device initialization error flow
- IB/mlx4: Reduce SRIOV multicast cleanup warning message to debug level
- IB/hfi1: Prevent kernel QP post send hard lockups
- perf auxtrace: Fix no_size logic in addr_filter__resolve_kernel_syms()
- perf annotate s390: Fix perf annotate error -95 (4.10 regression)
- perf annotate s390: Implement jump types for perf annotate
- jbd2: fix dbench4 performance regression for 'nobarrier' mounts
- ext4: evict inline data when writing to memory map
- orangefs: fix bounds check for listxattr
- orangefs: clean up oversize xattr validation
- orangefs: do not set getattr_time on orangefs_lookup
- orangefs: do not check possibly stale size on truncate
- fs/xattr.c: zero out memory copied to userspace in getxattr
- ceph: fix memory 

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Christos]

Hi Kai,

Kernel version for the image I'm using is: 4.10.0-22-generic.

I downloaded the image from the following URL:

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

Should I download again as I see it was modified today, where as I
downloaded it on the 26th.

Thanks

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Kai-Heng Feng]

Christos,

What's the kernel version of 17.10 live USB?
Linux version 4.10.0-25 has the fix but 4.10.0-24 does not.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Christos]

Hi Kai,

Sorry for the late reply.

Kernel v4.11.3

More info of the iso:
https://www.archlinux.org/releng/releases/2017.06.01/

Hope this helps!

Christos

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Kai-Heng Feng]

What's the version of Arch's kernel?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Christos]

BIOS version I have installed - F5
Latest release - F6

Have others installed F6 when testing?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Christos]

Hi Kai,

I've just tested pending 17.10 and have the same results. Are there any
specific BIOS options required?

My system is currently using IOMMU for my 16GB ECC RAM. This is the only
option I have changed in the BIOS.

Arch can successfully boot on the machine.

If you need anything testing, I can try it on my machine if needed, will
use another SSD for Windows.

Thanks,

Christos

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Kai-Heng Feng]

Christos,

Try the "pending" one instead of "current".

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[John Kelly]

nickleplated, Thanks you I missed the link somehow. 4.10.0.-25 from
proposed solved the issue for me with the Gigabyte AB350 Gaming 3 with
bios 7.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Christos]

Hi,

My machine uses the Gigabyte X370 Gaming 5 with the 1800X. No OS on the
SSD.

I'm unable to boot from USB using:

- 17.04 live usb
- 17.10 daily live usb

IRQ 07 errors and the system hangs without entering the installer.

I've tried the above grub parameters acpi=off with no luck.

What are the steps needed to boot into a live usb and get ubuntu
installed to then enter -proposed and get the upgraded kernel packages
for full usage?


Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[nickleplated]

John, I used the link mentioned above
(https://wiki.ubuntu.com/Testing/EnableProposed), but replaced xenial
with zesty.

In aptitude, I looked through all the upgradable packages and only
selected the ones with the new kernal version number.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[John Kelly]

I'm using: 4.10.0-24-generic and only able to use Ubuntu with acp=off
nickleplated.

I'm unclear about how to fetch the versions that people are mentioning
in the last few posts. Can someone clue me in on how to fetch `linux-
generic-hwe-16.04-edge=4.10.0.23.16.10.0` or `4.10.0-25 from -proposed`
with aptitude? Google is failing me. I'd be very happy to test them out
and see if it solves the gigabyte motherboard issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[nickleplated]

Does the recent security related release (4.10.0-24) also include this
fix, or should I skip it and get 4.10.0-25 from -proposed?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Adie]

I confirm package linux-generic-hwe-16.04-edge=4.10.0.23.16.10.0 fix
this bug for me on my gigabyte motherboard and Zesty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Richard]

I can confirm that 4.10.0-23-generic #25~16.04.1-Ubuntu SMP Fri Jun 9 10:45:17 
UTC 2017 works
with a Gigabyte GA-AX370-Gaming 5 and UEFI version F5. (Ubuntu 16.04)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Woody]

Hi I have installed the kernel, I'm running it on Xenial now and it
works good. No IRQ07 issues what so ever. Thanks everyone involved!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Kleber Sacilotto de Souza]

Hi @tekkla,

Yes, kernel 4.10.0-23 is the one in -proposed for Zesty. So thank you
for verifying it!

The tags are located just below the bug description. I will update it
myself.

Thanks you.

** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Tekkla]

Hi @all,

I tested it and I'm not sure that I did it right. The wiki link is
somewhat outdated, because it relys on aptitude, which seems not to be
installed with Zesty. Nevermind. I now have installed a kernel named

4.10.0-23-generic #25-Ubuntu SMP Fri Jun 9 09:39:09 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux

It works flawless. Is this the proposed kernel to test? Any if yes,
where do I have to add the needed 'verification-done-zesty' tag?

Thank you.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Kleber Sacilotto de Souza]

Hi @wo0dy,

You can verify the bug on Xenial by installing linux-generic-
hwe-16.04-edge=4.10.0.23.16 which is currently on -proposed pocket. This
kernel also have the fix for this bug.

Thank you.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Woody]

Must verification/testing be done in Zesty? I have Xenial on my machine.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Kleber Sacilotto de Souza]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-zesty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Kai-Heng Feng]

Unfortunately no. I don't think image for Zesty will get any updates.

If you want to do a fresh install, you need to use parameters like
"apci=off" to install. You can remove "acpi=off" after upgrading the
system.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Navdeep Singh]

@kaihengfeng

Will your update be available on June26 on
http://releases.ubuntu.com/17.04/ ? Those seems to be stuck on date when
zesty was released. Do they files get updated as bugs get fixed?

e.g.
ubuntu-17.04-desktop-amd64.iso 2017-04-12 03:46

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Tony Brobston]

buzuk56's solution worked for me. I'm using Ryzen 5 1500X with Gigabyte
GA-AB350-gaming-3.

Thanks! So glad to have Ubuntu on this machine.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Kai-Heng Feng]

@Woody

According to [1], it will be released to -updates at 26-June.

It will be at -proposed before that.

[1] https://wiki.ubuntu.com/KernelTeam/Newsletter/2017-05-31

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Stefan Bader]

** Changed in: linux (Ubuntu Zesty)
   Status: Fix Released => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Woody]

When should we expect the update with the fix to be available in Xenial?
I have linux-generic-hwe-16.04-edge installed, but haven't seen any
improvement.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Gabi Dumi]

I noticed a new beta BIOS ( version F5c) has appeared for AB350m G3, has anyone 
tried it yet?
Does it now properly boot from a live Ubuntu image?
I just got a new power supply, I think I will also try the new BIOS on the 
coming weekend.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[windblow]

** Changed in: linux (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Kleber Sacilotto de Souza]

** Changed in: linux (Ubuntu Zesty)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Leonardo Varuzza]

I had the same problem with my Aorus X370, changed for a ASUS prime,
everything is working, even the overclock.


On Wed, May 31, 2017 at 4:21 PM Gabi Dumi <1671...@bugs.launchpad.net>
wrote:

> My Gigabyte AB350m G3 decided to play dead today. In the morning it
> started OK, and after a few light browsing and a little coding I shut it
> down. After about an hour, when I tried powering it on, it was dead. No fan
> spin, no LED-s, no sign of life whatsoever. After troubleshooting all day
> swapping parts, power supplies, removing RAM, re-seating the CPU, I was
> about ready to start a warranty claim. I still could not believe a month
> and a half old motherboard could just die without any prior symptoms. It
> wasn't even overclocked, even the ram was running at only 2133mhz - ultra
> durable my a**. As a last resort I tried removing the BIOS battery and
> shorting the clr_cmos jumper with the battery removed and it came back to
> life.
> After all the problems I had with Ubuntu support, when things started to
> look like they were improving, this made me think seriously about ordering
> an Asus or even AsRock replacement board for when it decides to have some
> other annoying problem. I would not recommend this board in the current
> state, especially not for an Ubuntu Linux system.
> Sorry for not being exactly on topic since this is probably not Linux or
> Ubuntu related. Unless Ubuntu  does something strange on shutdown?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1671360
>
> Title:
>   System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Launchpad Bug Tracker]

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

** Changed in: linux (Ubuntu Zesty)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Kai-Heng Feng]

I remember someone mentioned there's no such issue on 4.4 kernel?
Anyway, you can use Zesty's kernel in Xenial.
Install package "linux-generic-hwe-16.04-edge" will do.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Woody]

Will the fix get backported or become available on Xenial? (16.04)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Tekkla]

Yay!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Seth Forshee]

** Also affects: linux (Ubuntu Artful)
   Importance: Medium
   Status: Confirmed

** Also affects: linux (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

** Changed in: linux (Ubuntu Zesty)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

** Changed in: linux (Ubuntu Artful)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Gabi Dumi]

@Woody
I also have a Gigabyte Z68-ud3h-b3 in another computer (i5 2500k) and event 
though it's approaching 10 years old, and it's overclocked, it never did that 
(there were times when it would not cold boot, but at least the fans moved and 
you could reset the bios via clr_cmos, no problem). My brother has a Gigabyte 
z97 board and this never happened to him. I will try replacing the power supply 
since it is quite old, maybe it's related? I measured all the rails with a DMM 
though and they were in spec but there could be something a multimeter can't 
detect like noise on the lines or too much delay on startup signal. Thanks for 
the info anyway!

@buzuk56
The board would not turn on at all, no fans ,no power supply start, nothing. 
And when it did start, it booted the normal bios no problem so it seems to me 
it wasn't bios corruption.

Anyway, it works OK now, hopefully it was just an isolated event.
While I was troubleshooting yesterday, I noticed on the back of the board there 
were very fine traces of silver colored residue. It looked like the board was 
soldered with solder paste and some of it spilled and flowed down on the PCB. I 
cleaned it as best as I could but I'm still worried about it. Any of you had 
this, or am I just being paranoid?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Kai-Heng Feng]

** Description changed:

+ [Impact]
+ Gigabyte AM4 boards users cannot boot Ubuntu successfully.
+ Commit linux-gpio/fixes babdc22b0ccf4ef5a3075ce6e4afc26b7a279faf 
"pinctrl/amd: Use regular interrupt instead of chained" can fix the issue. 
+ 
+ [Test Case]
+ All Gigabyte AM4 boards can reproduce the issue.
+ With the patch, the issue is resolved, per comment #170.
+ 
+ [Regression Potential] 
+ Regression Potential is low. It limits to rather new AMD platform which has 
pinctrl-amd. 
+ As the commit log says, use chained interrupt is not a good idea. Use regular 
interrupt is the correct way.
+ 
+ I also test the patch on an AMD laptop, where its touchpad depends on
+ pinctrl-amd. No regression found.
+ 
+ Original bug report:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.
  
  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.
  
- 
- Following advice from various places, I've tried:disable cpu freq governor 
and cpu handling in acpi settings
+ Following advice from various places, I've tried:disable cpu freq
+ governor and cpu handling in acpi settings
  
  1. add "acpi=off" to boot params
  
  That helps, allowing me to boot into recovery mode, though it leaves me
  with system seeing only one core, is really slow and still only boots in
  recovery mode.
  
  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and
  cpu handling in acpi settings. Boot with "quiet loglevel=3" option.
  
  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.
  
  Some observed problems:
  
  1. dmesg reports *a lot* of messages like this all the time:
  
- [  163.362068] ->handle_irq():  87a7e090, 
+ [  163.362068] ->handle_irq():  87a7e090,
  [  163.362081] bad_chained_irq+0x0/0x40
- [  163.362089] ->handle_irq():  87a7e090, 
+ [  163.362089] ->handle_irq():  87a7e090,
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
- [  163.362090] ->irq_data.chip(): 88587e20, 
+ [  163.362090] ->irq_data.chip(): 88587e20,
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
- [  163.362099] ->handle_irq():  87a7e090, 
+ [  163.362099] ->handle_irq():  87a7e090,
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
- [  163.362100] ->irq_data.chip(): 88587e20, 
+ [  163.362100] ->irq_data.chip(): 88587e20,
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0
  
  I've tried to redirect dmesg to a file, stopped after a short while, it
  generated 400M of those.
  
  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?
  
  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel
  and google are completely silent about AMDI0040.
  
- 
  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
- --- 
+ ---
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
-  LANGUAGE=en_US:en
-  TERM=linux
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_US:en
+  TERM=linux
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:
-  
+ 
  _MarkForUpload: True

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[buzuk56]

@Gabi, 
I faced a similar issue with my Gigabyte mother board Z68 a couple of month ago 
and I sorted out the problem by applying the [2] below.

May be you could have a go with [1] or [2]

[1] https://www.youtube.com/watch?v=HhI-t5lh_38
[2] 
https://forums.tweaktown.com/gigabyte/57335-dual-bios-dead-corrupted-blue-screen-bios-freeze-lga-2011-ga-x79-ud3.html

Good luck.

B.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Woody]

@Gabi Its a known issue with the gigabyte boards. It is known as coldboot issue 
I believe. The reset procedure is to take the cmos battery out, leave the pc 
unplugged and batteryless for about 10 minutes and then it will work again. I 
had the same first reaction as you when I had the issue first time. Not fun.
 Typically it happens when the machine is left powered down for a while.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[OdelPasso]

Hi,

I would like to buy the Gigabyte AB350M-gaming 3 + AMD Ryzen 5 1600X and
do you know if this issue exist on Debian Stretch/Sid ?

Thanks for your help,

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Gabi Dumi]

My Gigabyte AB350m G3 decided to play dead today. In the morning it started OK, 
and after a few light browsing and a little coding I shut it down. After about 
an hour, when I tried powering it on, it was dead. No fan spin, no LED-s, no 
sign of life whatsoever. After troubleshooting all day swapping parts, power 
supplies, removing RAM, re-seating the CPU, I was about ready to start a 
warranty claim. I still could not believe a month and a half old motherboard 
could just die without any prior symptoms. It wasn't even overclocked, even the 
ram was running at only 2133mhz - ultra durable my a**. As a last resort I 
tried removing the BIOS battery and shorting the clr_cmos jumper with the 
battery removed and it came back to life.
After all the problems I had with Ubuntu support, when things started to look 
like they were improving, this made me think seriously about ordering an Asus 
or even AsRock replacement board for when it decides to have some other 
annoying problem. I would not recommend this board in the current state, 
especially not for an Ubuntu Linux system.
Sorry for not being exactly on topic since this is probably not Linux or Ubuntu 
related. Unless Ubuntu  does something strange on shutdown?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[edward]

@Marc,

thanks a lot mate! you are saving the day of all of us. Hope u are not
from the NSA heheheh. thanks a lot mate!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Wenbin Leo]

Tested on AX370-Gaming K5-CF:
http://people.canonical.com/~khfeng/lp1671360-regular-interrupt/
run flowlessly.
And previous report at #158 about ALC1220 audio codec is wrong. Analog audio 
did show up in the audio settings after speaker is plugged in, and 5.1 analog 
output works. Sorry for the misinformation.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Kai-Heng Feng]

Please try [1]. It has [2] which should solve the issue.

[1] http://people.canonical.com/~khfeng/lp1671360-regular-interrupt/
[2] https://patchwork.ozlabs.org/patch/766231/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Woody]

I tested blacklisting as you described in the reddit post and it did not
fix the vector 07 irq trap issue for me on ubuntu 16.04.

Mobo is gigabyte AB350m-HD3

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Say-Tar Goh]

Hi guys, I tried nextized's kernels above at Mint 18.1 and each of them
worked (AX370-Gaming5). However I wanted to keep up with the latest
kernels, and am now running Fedora without a hitch.

I then tried booting OpenSuSE Tumbleweed and got different error
messages/kernel panic that seemed to be caused by the same problem,
which somebody seemed to have fixed by blacklisting pinctrl-amd:

https://www.reddit.com/r/openSUSE/comments/5zu2mo/gigabyte_gaming_5/

Need my current machine for production so can't test this back in
Ubuntu, but can somebody confirm? If so this will save a lot of people
the hassle of eternally patching the kernel.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Hein]

Will @Marc's kernel work with UEFI RAID? I'm trying to build a 2-disk
system with root and boot on an SSD and swap, tmp and home on a RAID10
config consisting of 4 HDDs. I'd prefer the set-up to be UEFI based
because this seems to be the most future proof.

I'm using a GA-AX370-Gaming K3 and an AORUS RX570 graphics card.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Lei Ni]

@Marc, thanks again for the Kernel! It works great on my GA-AB350M-
Gaming 3 + Ryzen 1700 + NVIDIA 381.22. Audio, SATA, NVME SSD all work
fine with the new kernel.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Tekkla]

@Marc

Your kernel works like a charm on my GA-AB350-Gaming3. No problems at
all. NV 381 beta driver works for me too. Thanks for your work!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[DIONYSIS KAPATSORIS]

@Marc
I confirm your kernel works with GA-AB350M-Gaming 3 and the nvidia-381 drivers.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Kai-Heng Feng]

Good to know AMD and Gigabyte are working on this issue.
So I don't need to send the patch to upstream, but as an Ubuntu sauce patch.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Woody]

That is great news Marc, thank you for keeping us posted

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Marc Singer]

Hello Guys

Just compiled a new version (4.11.2) for Ubuntu:

http://www.nextized.net/repo/linux/ubuntu-
linux-4.11.2_ryzen01_amd64_generic.tar.gz

Please test it on your plattform. Confirmed works with nvidia 381

Answer from AMD developers who created this module:

Hi nextized,
This issue has been reported by a few of them, all on the Gigabyte Platform. We 
aren’t seeing this issue on our reference platform. We are working with other 
teams to resolve this issue.
Thanks,
Regards,
-   Ram

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Kai-Heng Feng]

@Marc,
Actually, there are lots of workaround/qurik table in linux kernel itself.

This module is essential for touchpad on AMD laptop. Any distro wants to
have AMD laptop support should enable this.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Wenbin Leo]

Test result of
http://people.canonical.com/~khfeng/lp1671360-artful/
on AX370-Gaming K5-CF:
Boots without IRQ error.
All devices work but ALC1220 audio codec, which is the same as previous 4.10 
kernels.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Marc Singer]

@kaihengfeng I don't think this will be accepted by upstream, since it's
hardcoding hardware descriptors as magic numbers into the module.

@adrailien
Could you try the newest version of the nvidia drivers compatible with 4.11 
http://www.askmetutorials.com/2017/04/install-uninstall-nvidia-driver-38109.html
 

Could someone from Canonical please answer, why this module is enabled
by default on ubuntu? On other distributions it's disabled (maybe for
stability / compatiblity reasons). And we still got no clue about what
the functions of the GPIO Pins even are. I would like to get an answer
to that.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Tekkla]

@kaihengfeng I just tested your latest kernel an ran into serveral
problems. The IRQ error is gone but in exchange my NFS mounts in fstab
won't get mounted and my monitor isn't recognized so I got only a
1024x768 resolution.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Adrian Bolden]

My experience:
Ryzen 7 1700
Gigabyte AB350 Gaming Motherboard
NVIDIA gtx1070
Kubuntu 17.04 installer on USB stick.

Same install problems as others with IRQ mess.

Solved as buzuk56 and Nextized described, however the proprietary NVIDIA
drivers do not work with 4.11 kernel, so used the 4.10.3 version. I
installed both kernels, but had to modify Grub config and run update-
grub. I added a 2 second Grub startup delay so you can get into Grub
easily to mess with boot options.

I set 4.10.3 as default kernel, and have acpi=on

On install of Nvidia drivers, Linux will crash after install (can't
shutdown, lots of application crashes). Forced reboot and it's OK.

System seems to work now, Nvidia drivers are working (GLXgears works),
all cores are showing in system monitor. Screen locking/unlocking works,
and system can restart itself with no problems.

Thank you for all your efforts on this, I've been a Linux user since
486's were a thing and I'm constantly amazed at how things have changed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Kai-Heng Feng]

Here's 4.11 artful linux kernel with the patch below:
http://people.canonical.com/~khfeng/lp1671360-artful/

I don't think upstream will be happy about this patch, but I'll try =)

But first, I need you guys test it for me.

diff --git a/drivers/pinctrl/pinctrl-amd.c b/drivers/pinctrl/pinctrl-amd.c
index d69e357a7a98..f2b3ed33c65a 100644
--- a/drivers/pinctrl/pinctrl-amd.c
+++ b/drivers/pinctrl/pinctrl-amd.c
@@ -29,6 +29,7 @@
 #include 
 #include 
 #include 
+#include 
 #include 
 #include 
 
@@ -739,6 +740,26 @@ static struct pinctrl_desc amd_pinctrl_desc = {
.owner = THIS_MODULE,
 };
 
+static bool amd_gpio_is_gigabyte_am4(void)
+{
+   const char *board_name;
+
+   if (!dmi_match(DMI_BOARD_VENDOR, "Gigabyte Technology Co., Ltd."))
+   return false;
+
+   board_name = dmi_get_system_info(DMI_BOARD_NAME);
+
+   if (!board_name)
+   return false;
+
+   if (strstr(board_name, "A320") ||
+   strstr(board_name, "B350") ||
+   strstr(board_name, "X370"))
+   return true;
+
+   return false;
+}
+
 static int amd_gpio_probe(struct platform_device *pdev)
 {
int ret = 0;
@@ -746,6 +767,10 @@ static int amd_gpio_probe(struct platform_device *pdev)
struct resource *res;
struct amd_gpio *gpio_dev;
 
+   /* Don't load this module if it's a Gigabyte AM4 board */
+   if (amd_gpio_is_gigabyte_am4())
+   return -ENODEV;
+
gpio_dev = devm_kzalloc(>dev,
sizeof(struct amd_gpio), GFP_KERNEL);
if (!gpio_dev)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Woody]

http://elixir.free-electrons.com/linux/latest/source/drivers/pinctrl
/pinctrl-amd.c

Looks like I found the author? This is 2014-2015 so may have changed,
but its probably worth a shot. Most likely he'd also know who is or how
to find the current maintainer.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Woody]

Excellent idea Marc Singer.

I did a quick google search. It turned up:
https://www.kernel.org/doc/linux/MAINTAINER

There's 37 entries for pinctrl and none for amd_pinctrl

I think the most relevant one would be the entry for PIN CONTROL
SUBSYSTEML

PIN CONTROL SUBSYSTEM
M:  Linus Walleij 
L:  linux-g...@vger.kernel.org
T:  git 
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git
S:  Maintained
F:  Documentation/devicetree/bindings/pinctrl/
F:  Documentation/pinctrl.txt
F:  drivers/pinctrl/
F:  include/linux/pinctrl/

I suggest we find the maintainer, contact, and attempt to make them
aware of the issue?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Marc Singer]

I would prefer 4.11.0 as it supports most of the mainboards newer ACL
sound codecs:

http://www.nextized.net/repo/linux/ubuntu-
linux-4.11.0_ryzen01_amd64_generic.tar.gz

As I can tell, Gigabyte is not really takling the issue because only a
very small number of people are affected by it. Alternate Operating
Systems are not worth investing time and money (you have to get someone
with good know how in Linux Development to fix this error). Thats just a
fact. If this was an Issue with ASUS or ASRock or whatever brand, we
wouldn't get any support either.

The only thing we can do is 
1) Install custom kernels or disable AMD_PINCTRL
2) Wait until AMD releases a fixed version of the Module; 
It seems like an Issue with a NULLPOINTER on some of the higher PINS, then the 
Kernel gets stuck in a infinite loop, trying to get the Module to load, instead 
of just skipping it. If we get a release where the error is handled and loading 
of the module is fixed (by ignoring / aborting it), we can use Linux under 
Gigabyte Mainboards just fine.

But how do we get it fixed? Who is the maintainer of the Module? AMD
itself? I dont really know.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[buzuk56]

Here is a 4 steps procedures that worked on AB350 Gaming 3 Ryzen 1600
(F4 bios) to get 17.04 with all cores and threads

1)Ubuntu 17.04 install from usb bootable drive with acpi=off (press F6
when display menu)

2)log in and  install sudo dpk -i *deb the kernel compiled by nextized worked:
http://www.nextized.net/repo/linux/ubuntu-linux-4.10.3_ryzen01_amd64_generic.tar.gz
3) push back acpi=on to your 17.04 system to get all core and threads from your 
Ryzen
sudo gedit /etc/default/grub  
Change line GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to 
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=on"
sudo update-grub
4) reboot and you should have all cores and threads on 17.04 new install

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Kai-Heng Feng]

Please try [1].

This should prevent pintctrl-amd to be loaded on any A320/B350/X370.

[1] http://people.canonical.com/~khfeng/gigabyte-am4/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Woody]

I'd return my board if I could, but I can't (had to wait 2+weeks for
other parts to arrive before I started build).

Anyone have a good kernel compilation guide (or even just paste their
commands I would be grateful for) so that I can build up-to-date
official kernels with AMD_PINCTRL disabled? I tried various guides
carefully, all failed. The problem always appears to be that this
debian/ directory does not exist in my kernel source code folder.

Thanks,

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Ondrej Masek]

Make sure you leave a review for your MB. I've already done that on
Amazon UK.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[buzuk56]

Hi there,

I sent out yestaerday an email with the link to this bug report to Gigabyte 
team. 
I received an email response today from Gigabyte team. 
"Thank you for emailing GIGABYTE.
We are delighted with your interest in our products.

GIGABYTE does not support Linux OS.

Linux is  open source, everyone can compile it´s own OS.

We can´t support , sorry.
Please check with the Linux community for newer kernel version..."

Same as Mazek Andrej reported above.
Although this issue is active for more than two month it sounds that there is 
no intend from Gigabyte to tackle it despite it is specific to Gigabyte 
Motherboard. I will send back my AB350 Gaming 3 to the reseller and definitely 
buy another brand. Likely to be an ASUS.

Regards.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Gabi Dumi]

After a few struggles and Internet searches I found out that AMD-V also works 
with my current setup, only problem is it comes disabled by default in BIOS. It 
also doesn't help that it's named SVM and there are 2 related options (SVM 
support, and SVM mode - what the hell does SVM mean?). SVM mode was Disabled so 
I was having trouble launching a Virtualbox x64 mode client.
So I can confirm AMD-V and kernel 4.10.19 work OK.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[RussianNeuroMancer]

Drop letter to level1techs.com/contact-us
I guess their channel on YouTube is big enough to make vendor notice this issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Daniel Harvison]

My last gigabyte motherboard too, I'm pretty damn angry about their lack
of any kind of action on this matter. In fact, I'm going to try to
replace this mobo (GA-AB350 Gaming 3) at some point.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Leonardo Varuzza]

Every linux user should put that linux is not support in their gigabyte
review.

I always bought ASUS motherboards, I gave gigabyte a try because of Ryzen
motherboards shortage, however I was my last gigabyte board.


On Sat, May 13, 2017 at 4:20 PM edward <1671...@bugs.launchpad.net>
wrote:

> Hi guys,
>
> i think we should do something about this gigabyte-situation, kinda of
> writing then a bunch of letters from all of us, there is also a bunch of
> ppl on reddit having this same problem, and still, gigabyte is not
> giving a breath to address this situation... do we really have to accept
> this kinda answers "we do not support linux, see by yourself what u
> do"...
>
> i think we should make us ourselves to a big voice of this thing, so
> that gigabyte stop threating our problem like nothing they have to do
> with...
>
> any suggestions?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1671360
>
> Title:
>   System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[edward]

Hi guys,

i think we should do something about this gigabyte-situation, kinda of
writing then a bunch of letters from all of us, there is also a bunch of
ppl on reddit having this same problem, and still, gigabyte is not
giving a breath to address this situation... do we really have to accept
this kinda answers "we do not support linux, see by yourself what u
do"...

i think we should make us ourselves to a big voice of this thing, so
that gigabyte stop threating our problem like nothing they have to do
with...

any suggestions?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Gabi Dumi]

Thanks @Woody!
I managed to install that module and I can now see temps, voltages and fan RPMs.
I tried to do the same a while ago but I could not get it to work. Maybe 
meanwhile something changed or maybe it was a PEBKAC error (problem exists 
between keyboard and chair).
Now, if I also find a method to label all those readings in XSensors I will 
stop tinkering with it(not). :)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Woody]

@Gabi. I hope you're right.

Regarding temperatures: https://github.com/groeck/it87
If you make and modprobe that module, that should get you all fan readings and 
temperature outputs.
Works a charm for me.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Gabi Dumi]

I don't believe that Gigabyte can just say they don't support Linux or even 
just Ubuntu for that matter. Linux is not that small a market anymore and I 
believe Linux as an SO is very well suited for a relatively cheap multi-core 
cpu like Ryzen. I myself bought a Ryzen with the intent of building a nice, 
low-cost server for productivity oriented applications. Yes, if you want a 
gaming platform, Windows is a better platform, but then an Intel I7 is also a 
better choice in that case.
So I think a big company like Gigabyte is not going to just let Linux users 
choose another manufacturer that supports them, it would not be good for 
business. 
Support for temperatures and frequency monitoring tools would also be nice...
Anyone knows if there's progress about this? Since I run my CPU under the stock 
Spire cooler and in an media center case knowing what the temps are under load 
is not entirely unimportant.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Nagy Ákos]

I have a same issue with GA-AB350-Gaming3 and Ryzen 1600.
It's sad Gigabyte response, now I buy a new AsRock AB350M Pro4, and in the 
future I don't chose gigabyte.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Kai-Heng Feng]

** Bug watch added: Linux Kernel Bug Tracker #194825
   http://bugzilla.kernel.org/194825

** Also affects: linux via
   http://bugzilla.kernel.org/194825
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Woody]

Gigabyte says they don't support linux. End of story as far as they're
concerned. I'd really just like to see something happen. A boot
parameter would be fantastic. How would we go about notifying relevant
parties to get something arranged/requested? Is here the right place?

Its been over 2 months since this platform released, would be nice to
see a fix/proper workaround.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Leonardo Varuzza]

I just loaded the stock kernel with the Marc Singer configuration and
changed the preemption mode to low-latency. Running much smoothly now.


On Sun, May 7, 2017 at 9:30 AM Ondrej Masek <1671...@bugs.launchpad.net>
wrote:

> Just got this from Gigabyte Support:
>
> "Hello,
> Sorry but Gigabyte do not guarantee Linux Platform on the desktop
> motherboard.
> It support for Windows 10/7."
>
> Extremely helpful :/
>
> In the meantime, I booted the Kubuntu install ISO with acpi=off setting.
> The same option was required for the first boot after install. Kernel
> version 4.10.0-21 compiled by kaihengfeng on
> http://people.canonical.com/~khfeng/lp1671360-2/ seems to work fine, the
> only thing to report is a long boot time.
>
> Thanks Kai-Heng Feng!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1671360
>
> Title:
>   System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Ondrej Masek]

Just got this from Gigabyte Support:

"Hello,
Sorry but Gigabyte do not guarantee Linux Platform on the desktop motherboard. 
It support for Windows 10/7."

Extremely helpful :/

In the meantime, I booted the Kubuntu install ISO with acpi=off setting.
The same option was required for the first boot after install. Kernel
version 4.10.0-21 compiled by kaihengfeng on
http://people.canonical.com/~khfeng/lp1671360-2/ seems to work fine, the
only thing to report is a long boot time.

Thanks Kai-Heng Feng!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Jaka Jaksic]

If pinctrl causes issues with certain hardware, but is required for
certain other hardware, and if it isn't possible to automatically
determine which is which, then it would make sense to make it
controllable through a boot flag (like acpi=off).

While having to specify a boot flag is still less than ideal, it is far
preferable to having installing a different distro or build a custom
kernel.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[TheLXK]

4.10.0-21 compiled by kaihengfeng on
http://people.canonical.com/~khfeng/lp1671360-2/ working for me without
any additional kernel parameters on a GA-AB350 Gaming 3, with a Ryzen
1700X.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Woody]

Awesome. Thank you Milosz for following up there. Perhaps a patch can be
created specifically for these boards, something along the lines of 'if
board is type am4, vendor==gigabyte: disable pinctrl' Its messy, but
it'd work.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Ondrej Masek]

Submitted a request with Gigabyte support just now. Can't believe this
has been dragging on for two months. Who would have thought to check
whether the chosen motherboard even boots up with the latest OS prior to
purchasing :\ Extremely frustrating.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Milosz Tanski]

I'm trying to follow up with the hardware vendor (Gigabyte) to help us
identify the root cause so we can fix it / work around it in the kernel.
Here's my last conversation with Matt from Gigabyte:
http://forum.gigabyte.us/thread/886/am4-beta-bios-
thread?page=47=4429

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Wenbin Leo]

Testing on AX370-Gaming K5-CF :
4.10.0-21 compiled by kaihengfeng on 
http://people.canonical.com/~khfeng/lp1671360-2/ seems working, using it to 
post result.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Woody]

What will it take to get this bug fixed!?

Upstream most likely is (or will) point at the hardware vendors (I don't
know, thats just me guessing), while the hardware vendor says 'not our
problem, we don't support linux'. What are we to do?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Wenbin Leo]

Tested on AX370-Gaming K5-CF :
Default Ubuntu kernel do not work.
4.10.0-21 compiled by kaihengfeng 
[http://people.canonical.com/~khfeng/lp1671360/]
also shows "unexpected irq trap at vector 07" error message, can not boot to 
desktop.

Both kernel compiled by nextized worked:
http://www.nextized.net/repo/linux/ubuntu-linux-4.10.3_ryzen01_amd64_generic.tar.gz
http://www.nextized.net/repo/linux/ubuntu-linux-4.11.0_ryzen01_amd64_generic.tar.gz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Kai-Heng Feng]

Probably LP: #1674838.
Can you check the /var/log/kern.log and see if it has the same error?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[belgianguy]

@kaihengfeng: I've been experiencing some system freezes. I have a clean
17.04 install except for the kernel (which is your 4.11 custom kernel).
Any idea where I could look for what's causing it?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs