Bug#992886: r8169: no dedicated PHY driver found for PHY ID 0xc1071002

2021-09-08 Thread Roger Lynn

On 05/09/2021 09:07, Salvatore Bonaccorso wrote:

On Wed, Sep 01, 2021 at 10:59:19PM +0100, Roger Lynn wrote:

On Wed, 25 Aug 2021 08:07:48 +0200 Heiner Kallweit 
wrote:
> A number of Gigabyte boards from ~2009 have broken BIOS support, resulting in 
the PHY
> reporting an invalid PHY ID. Realtek / Gigabyte don't release errata 
information,
> therefore there's not much that can be done. In bugzilla.kernel.org you can 
find
> workarounds that helped for some users, else use the r8168 driver.

In https://bugzilla.kernel.org/show_bug.cgi?id=207203 it was suggested to
enable the boot ROM in the BIOS and/or reinsert the r8169 kernel module.
Neither of these worked for me. Fortunately the r8168-dkms package does
work. Thank you for the suggestion, as I was not aware of this driver.


According to the discussion, there is not something to patch on the
kernel side and rather likely a BIOS bug. So closing the bug.


The r8168-dkms package asks for bugs to be filed when it works but the 
in-kernel driver doesn't. I guess this bug already counts for that.




Bug#992886: r8169: no dedicated PHY driver found for PHY ID 0xc1071002

2021-09-01 Thread Roger Lynn
On Wed, 25 Aug 2021 08:07:48 +0200 Heiner Kallweit  
wrote:

A number of Gigabyte boards from ~2009 have broken BIOS support, resulting in 
the PHY
reporting an invalid PHY ID. Realtek / Gigabyte don't release errata 
information,
therefore there's not much that can be done. In bugzilla.kernel.org you can find
workarounds that helped for some users, else use the r8168 driver.


In https://bugzilla.kernel.org/show_bug.cgi?id=207203 it was suggested to 
enable the boot ROM in the BIOS and/or reinsert the r8169 kernel module. 
Neither of these worked for me. Fortunately the r8168-dkms package does 
work. Thank you for the suggestion, as I was not aware of this driver.


Roger



Bug#992886: r8169: no dedicated PHY driver found for PHY ID 0xc1071002

2021-08-24 Thread Roger Lynn
Package: src:linux
Version: 5.10.46-4
Severity: normal
File: /lib/modules/5.10.0-8-amd64/kernel/drivers/net/ethernet/realtek/r8169.ko

I've just upgraded this machine to Bullseye and it seems unable to load the
ethernet driver:

[6.548031] r8169 :02:00.0: can't disable ASPM; OS doesn't have ASPM 
control
[6.566607] libphy: r8169: probed
[6.566613] r8169 :02:00.0: no dedicated PHY driver found for PHY ID 
0xc1071002, maybe realtek.ko needs to be added to initramfs?
[6.590372] r8169: probe of :02:00.0 failed with error -49
[6.590412] r8169 :03:00.0: can't disable ASPM; OS doesn't have ASPM 
control
[6.592984] libphy: r8169: probed
[6.592987] r8169 :03:00.0: no dedicated PHY driver found for PHY ID 
0xc1071002, maybe realtek.ko needs to be added to initramfs?
[6.626342] r8169: probe of :03:00.0 failed with error -49

This is long after the filesystem has been mounted, so the initramfs should be
irrelevant, but I tried adding the realtek and r8169 modules to the initramfs
and the only difference was that the error was earlier in the boot sequence.

The machine is 12 years old and has worked with every stable Debian release in
that time. The old Buster kernel, 4.19.0-17-amd64, running with Bullseye
reports:

[   10.604259] r8169 :02:00.0: can't disable ASPM; OS doesn't have ASPM 
control
[   10.616071] libphy: r8169: probed
[   10.616222] r8169 :02:00.0 eth0: RTL8168d/8111d, 00:24:1d:1e:99:33, XID 
281000c0, IRQ 25
[   10.616223] r8169 :02:00.0 eth0: jumbo features [frames: 9200 bytes, tx 
checksumming: ko]
[   10.616921] r8169 :03:00.0: can't disable ASPM; OS doesn't have ASPM 
control
[   10.619251] libphy: r8169: probed
[   10.619384] r8169 :03:00.0 eth1: RTL8168d/8111d, 00:24:1d:1e:99:31, XID 
281000c0, IRQ 26
[   10.619385] r8169 :03:00.0 eth1: jumbo features [frames: 9200 bytes, tx 
checksumming: ko]
...
[   17.134036] r8169 :02:00.0: firmware: direct-loading firmware 
rtl_nic/rtl8168d-1.fw
[   17.134559] Generic PHY r8169-200:00: attached PHY driver [Generic PHY] 
(mii_bus:phy_addr=r8169-200:00, irq=IGNORE)
[   17.285430] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   17.286173] Generic PHY r8169-300:00: attached PHY driver [Generic PHY] 
(mii_bus:phy_addr=r8169-300:00, irq=IGNORE)
[   17.437417] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[   20.009162] r8169 :02:00.0 eth0: Link is Up - 100Mbps/Full - flow 
control rx/tx
[   20.009180] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

Thanks,

Roger

-- Package-specific info:
** Version:
Linux version 5.10.0-8-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 
10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP 
Debian 5.10.46-4 (2021-08-03)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.10.0-8-amd64 
root=UUID=cc5ea548-3370-40b7-b244-7fb88e5b310e ro radeon.dpm=1 quiet

** Not tainted

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: Gigabyte Technology Co., Ltd.
product_name: GA-MA790FXT-UD5P
product_version: 
chassis_vendor: Gigabyte Technology Co., Ltd.
chassis_version: 
bios_vendor: Award Software International, Inc.
bios_version: F8n
board_vendor: Gigabyte Technology Co., Ltd.
board_name: GA-MA790FXT-UD5P
board_version: 

** Loaded modules:
udp_diag
tcp_diag
inet_diag
cpufreq_userspace
cpufreq_powersave
cpufreq_conservative
cpufreq_ondemand
uinput
it87
hwmon_vid
loop
msr
i2c_dev
snd_hda_codec_realtek
snd_hda_codec_generic
ledtrig_audio
ax88179_178a
usbnet
snd_hda_codec_hdmi
mii
snd_hda_intel
snd_intel_dspcfg
soundwire_intel
soundwire_generic_allocation
snd_soc_core
edac_mce_amd
snd_compress
soundwire_cadence
kvm_amd
snd_hda_codec
ccp
r8169
rng_core
snd_hda_core
kvm
firewire_ohci
firewire_core
snd_hwdep
wmi_bmof
realtek
soundwire_bus
mdio_devres
libphy
sr_mod
crc_itu_t
irqbypass
snd_pcm
snd_timer
cdrom
pcspkr
ohci_pci
ohci_hcd
ata_generic
snd
sg
ehci_pci
ehci_hcd
sp5100_tco
watchdog
pata_atiixp
usbcore
acpi_cpufreq
soundcore
button
usb_common
wmi
i2c_piix4
k10temp
ext4
crc16
mbcache
jbd2
crc32c_generic
sd_mod
t10_pi
crc_t10dif
crct10dif_generic
crct10dif_common
radeon
i2c_algo_bit
drm_kms_helper
cec
ahci
ttm
libahci
libata
drm
evdev
psmouse
scsi_mod
serio_raw

** Network interface configuration:
*** /etc/network/interfaces:

auto lo
iface lo inet loopback

allow-hotplug eth0
iface eth0 inet static
address 192.168.0.3
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
gateway 192.168.0.2
allow-hotplug eth1
iface eth1 inet static
address 192.168.2.1
netmask 255.255.255.0

** Network status:
*** IP interfaces and addresses:
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft 

Fwd: Re: Bug#889487: linux-image-4.14.0-2-amd64: please enable CONFIG_X86_MCELOG_LEGACY]

2018-02-07 Thread Roger Lynn
Sorry, forwarding a reply I messed up.

- Forwarded message from Roger Lynn <use...@rilynn.me.uk> -

Date: Tue, 6 Feb 2018 23:08:05 +
From: Roger Lynn <use...@rilynn.me.uk>
To: Jon DeVree <n...@vault24.org>, 889...@bugs.debian.org
Newsgroups: linux.debian.kernel
Subject: Re: Bug#889487: linux-image-4.14.0-2-amd64: please enable 
CONFIG_X86_MCELOG_LEGACY
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 
SeaMonkey/2.49.1

On 04/02/18 02:00, Jon DeVree wrote:
> On Sun, Feb 04, 2018 at 01:03:59 +0100, Ben Hutchings wrote:
>> This was unintentional, but I think it's correct.  The Kconfig says to
>> use rasdaemon which is already packaged and in stable.
> 
> rasdaemon has a hard dependency on systemd, it isn't installable on
> machines still running sysvinit.

Yes it is installable. It depends on systemd, not systemd-sysv. systemd is
co-installable with sysvinit-core. I have it installed on a Stretch sysvinit
system (it then complains that it can't find a debugfs).

> Not sure if thats a hard dep or if it only just means rasdaemon is
> missing a sysvinit script.

Roger

- End forwarded message -