[Bug 230807] if_alc(4): Driver not working for Killer Networking E2200
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 15 Apr 2022 09:36:00 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230807
Ross McKelvie <ross@exitzero.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ross@exitzero.uk
--- Comment #12 from Ross McKelvie <ross@exitzero.uk> ---
I am experiencing an intermittent bug with the alc(4) driver with the Killer
E2200 Gigabit Ethernet NIC on FreeBSD-12.3-RELEASE-p5 for amd64 that may be
related. Network connectivity drops, the CPU load increases rapidly, the same
set of messages are logged repeatedly and the system cannot be restarted or
powered down using shutdown(8). The behaviour may occur shortly after a cold
start of the system but I need to observe more instances to confirm this.
uname -mv:
FreeBSD 12.3-RELEASE-p5 GENERIC amd64
pciconf -lv alc0:
alc0@pci0:8:0:0: class=0x020000 card=0x05ad1028 chip=0xe0911969 rev=0x10
hdr=0x00
vendor = 'Qualcomm Atheros'
device = 'Killer E220x Gigabit Ethernet Controller'
class = network
subclass = ethernet
dmesg | grep alc (when working correctly):
alc0: <Killer E2200 Gigabit Ethernet> port 0x3000-0x307f mem
0xd2400000-0xd243ffff at device 0.0 on pci2
alc0: 11776 Tx FIFO, 12032 Rx FIFO
alc0: Using 1 MSIX message(s).
miibus0: <MII bus> on alc0
alc0: Using defaults for TSO: 65518/35/2048
alc0: Ethernet address: f0:1f:af:30:ae:eb
alc0: link state changed to DOWN
alc0: link state changed to UP
Messages in /var/log/messages from today's occurrence:
Apr 15 09:51:11 redacted-hostname kernel: alc0: <Killer E2200 Gigabit Ethernet>
port 0x3000-0x307f mem 0xd2400000-0xd243ffff at device 0.0 on pci2
[6/1850]
Apr 15 09:51:11 redacted-hostname kernel: alc0: 11776 Tx FIFO, 12032 Rx FIFO
Apr 15 09:51:11 redacted-hostname kernel: alc0: Using 1 MSIX message(s).
Apr 15 09:51:11 redacted-hostname kernel: miibus0: <MII bus> on alc0
Apr 15 09:51:11 redacted-hostname kernel: alc0: Using defaults for TSO:
65518/35/2048
Apr 15 09:51:11 redacted-hostname kernel: alc0: Ethernet address:
f0:1f:af:30:ae:eb
Apr 15 09:51:11 redacted-hostname kernel: alc0: link state changed to DOWN
Apr 15 09:51:11 redacted-hostname kernel: alc0: link state changed to UP
Apr 15 09:51:30 redacted-hostname kernel: alc0: phy read timeout : 1
Apr 15 09:51:30 redacted-hostname kernel: alc0: phy read timeout : 0
Apr 15 09:51:30 redacted-hostname kernel: alc0: phy read timeout : 17
Apr 15 09:51:30 redacted-hostname kernel: alc0: could not disable RxQ/TxQ
(0xffffffff)!
Apr 15 09:51:30 redacted-hostname kernel: alc0: could not disable Rx/Tx
MAC(0xffffffff)!
Apr 15 09:51:30 redacted-hostname kernel: alc0: link state changed to DOWN
Apr 15 09:51:30 redacted-hostname kernel: alc0: phy read timeout : 1
Apr 15 09:51:30 redacted-hostname kernel: alc0: phy read timeout : 0
Apr 15 09:51:30 redacted-hostname kernel: alc0: phy read timeout : 17
Apr 15 09:51:30 redacted-hostname kernel: alc0: DMA read error! -- resetting
Apr 15 09:51:30 redacted-hostname kernel: alc0: DMA write error! -- resetting
Apr 15 09:51:30 redacted-hostname kernel: alc0: TxQ reset! -- resetting
Apr 15 09:51:31 redacted-hostname kernel: alc0: could not disable RxQ/TxQ
(0xffffffff)!
Apr 15 09:51:31 redacted-hostname kernel: alc0: could not disable Rx/Tx
MAC(0xffffffff)!
Apr 15 09:51:31 redacted-hostname kernel: alc0: MAC reset timeout!
Apr 15 09:51:31 redacted-hostname kernel: alc0: master reset timeout!
Apr 15 09:51:31 redacted-hostname kernel: alc0: reset timeout(0xffffffff)!
Apr 15 09:51:31 redacted-hostname kernel: alc0: phy write timeout : 29
Apr 15 09:51:31 redacted-hostname kernel: alc0: phy write timeout : 30
Apr 15 09:51:31 redacted-hostname kernel: alc0: phy read timeout : 16
Apr 15 09:51:31 redacted-hostname kernel: alc0: phy write timeout : 16
Apr 15 09:51:31 redacted-hostname kernel: alc0: phy write timeout : 4
Apr 15 09:51:31 redacted-hostname kernel: alc0: phy write timeout : 9
Apr 15 09:51:31 redacted-hostname kernel: alc0: phy write timeout : 0
Apr 15 09:51:31 redacted-hostname kernel: alc0: phy read timeout : 0
Apr 15 09:51:31 redacted-hostname kernel: alc0: phy write timeout : 4
Apr 15 09:51:31 redacted-hostname kernel: alc0: phy write timeout : 9
Apr 15 09:51:31 redacted-hostname kernel: alc0: phy write timeout : 0
Apr 15 09:51:31 redacted-hostname kernel: alc0: phy read timeout : 1
Apr 15 09:51:31 redacted-hostname kernel: alc0: phy read timeout : 0
Apr 15 09:51:32 redacted-hostname kernel: alc0: phy read timeout : 17
Apr 15 09:51:32 redacted-hostname kernel: alc0: could not disable RxQ/TxQ
(0xffffffff)!
Apr 15 09:51:32 redacted-hostname kernel: alc0: could not disable Rx/Tx
MAC(0xffffffff)!
Apr 15 09:51:32 redacted-hostname kernel: alc0: DMA read error! -- resetting
Apr 15 09:51:32 redacted-hostname kernel: alc0: DMA write error! -- resetting
Apr 15 09:51:32 redacted-hostname kernel: alc0: TxQ reset! -- resetting
Apr 15 09:51:32 redacted-hostname kernel: alc0: could not disable RxQ/TxQ
(0xffffffff)!
Apr 15 09:51:32 redacted-hostname kernel: alc0: could not disable Rx/Tx
MAC(0xffffffff)!
Apr 15 09:51:32 redacted-hostname kernel: alc0: MAC reset timeout!
Apr 15 09:51:32 redacted-hostname kernel: alc0: master reset timeout!
Apr 15 09:51:32 redacted-hostname kernel: alc0: reset timeout(0xffffffff)!
Apr 15 09:51:32 redacted-hostname kernel: alc0: phy write timeout : 29
[...continues until removing power...]
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.