Bug#961130: ethtool can read DOM values
On Thu, 2020-05-21 at 11:22 +0200, Bjørn Mork wrote: > Ben Hutchings writes: > > On Wed, 2020-05-20 at 13:09 +, Yannis Aribaud wrote: > > > Package: ethtool > > > Version: 1:4.19-1 > > > Severity: important > > > The command ethtool -m is unable to read the transceiver DOM values. > > > > Again, this is a driver or hardware issue, not a bug in ethtool. > > > > [...] > > > As you can see all mesuring values are zeros. > > > I am using Debian GNU/Linux 10 (buster), kernel 4.19.0-9-amd64 #1 SMP > > > Debian 4.19.118-2 (2020-04-29) x86_64 GNU/Linux and libc6 2.28-10 > > > > > > FYI, I get correct values using SystemRescueCD 6 (ethtool 5.0, kernel > > > 4.19.34-1-lts) on this same hardware, using the same command. > > > > I see no changes to ethtool between 4.19 and 5.0 that would explain > > that. > > I assume you're aware of this, but there are some interesting changes in > that driver between v4.19.34 and v4.19.118 I actually hadn't looked yet, so thanks for doing that. > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit?id=7da11d6a5d85ab3f4d28fa660d8c90566fdaa1e6 > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit?id=935f39807a7e95678e5bda50757af326691a211c > > > The net effect seems to be that they removed the part that actually made > DOM reading work. Yes, these patches don't make sense. If only the real EEPROM is readable then the correct fix would be to change both type and size to the SFF-8079 values. > Makes me wonder what happens if you revert both those > patches? I don't have the hardware, so I can't test.. > > This issue might also be fixed in mainline with the more generic high > page support for QSFP28 and QSFP+? I don't know, I no longer keep track of networking stuff beyond what I read in LWN. Ben. -- Ben Hutchings Reality is just a crutch for people who can't handle science fiction. signature.asc Description: This is a digitally signed message part
Processed: reassign 960870 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 960870 src:linux 5.5.17-1 Bug #960870 [linux-image-armmp] linux-image-armmp: please add patch to support fancontrol on Helios4 Bug reassigned from package 'linux-image-armmp' to 'src:linux'. No longer marked as found in versions linux/5.5.17-1~bpo10+1. Ignoring request to alter fixed versions of bug #960870 to the same values previously set Bug #960870 [src:linux] linux-image-armmp: please add patch to support fancontrol on Helios4 Marked as found in versions linux/5.5.17-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 960870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960870 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960493: linux-image-4.19.0-9-amd64: Audio regression on HP Pavilion laptop
Hi Steven, On Wed, May 13, 2020 at 10:48:27AM +0100, Steven Price wrote: > Package: src:linux > Version: 4.19.118-2 > Severity: important > Tags: upstream > > Dear Maintainer, > > After installing linux-image-4.19-0-9-amd64 my desktop environment no longer > detects the sound card (it reverts to the dummy output) and I get no sound. > However "aplay -l" still lists it. > > I bisected the kernel and found 44cc74947ce02283e4967aa92988b90ec7c25dee is > the > first broken commit. It appears that 6cacf120de65f336d57bdfd41466b65ed1c569c6 > is a follow up commit fixing the problem and indeed v4.19.121 works fine (the > regression is fixed). > > Is it possible to update the package to a later stable release? Yes, we work regularly for the point releases to rebase to latest stable versions in the series, so I would expect this to see in 10.5 at latest. Thanks for the bisecting work, I'm taking note to add a closer for this bug when either picking up the commit or importing 4.19.121. Regards, Salvatore
Bug#905912: marked as done (linux-image-3.16.0-6-amd64: Fails to mount SMB share using mount.cifs)
Your message dated Thu, 21 May 2020 12:00:38 +0200 with message-id <94f05ab0d98dabe6f4e28b03beaf2693ad925228.camel@yoshi.email> and subject line fixed 905912 linux/3.16.81-1 has caused the Debian Bug report #905912, regarding linux-image-3.16.0-6-amd64: Fails to mount SMB share using mount.cifs to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 905912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905912 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 3.16.57-2 Severity: normal Dear Maintainer, With the kernel 3.16.0-6 on Debian jessie I cannot mount my SMB shares anymore using mount.cifs on the command line. It does work fine if I reboot to 3.16.0-5. Mounting fails with "BUG: unable to handle kernel NULL pointer dereference at 0058" in dmesg. -- Package-specific info: ** Version: Linux version 3.16.0-6-amd64 (debian-kernel@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-10+deb8u1) ) #1 SMP Debian 3.16.57-2 (2018-07-14) ** Command line: BOOT_IMAGE=/vmlinuz-3.16.0-6-amd64 root=/dev/mapper/vg01-root ro quiet ** Tainted: D (128) * Kernel has oopsed before. ** Kernel log: [ 18.955350] EXT4-fs (dm-1): re-mounted. Opts: (null) [ 19.094955] EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro [ 19.813136] lp0: using parport0 (interrupt-driven). [ 19.917354] fuse init (API version 7.23) [ 20.212870] Adding 9539580k swap on /dev/mapper/vg01-swap_1. Priority:-1 extents:1 across:9539580k FS [ 20.513526] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [ 20.525119] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) [ 20.557456] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null) [ 21.463205] RPC: Registered named UNIX socket transport module. [ 21.463211] RPC: Registered udp transport module. [ 21.463214] RPC: Registered tcp transport module. [ 21.463217] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 21.503812] FS-Cache: Loaded [ 21.557305] FS-Cache: Netfs 'nfs' registered for caching [ 21.639155] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [ 25.366951] systemd-logind[2022]: New seat seat0. [ 25.382056] systemd-logind[2022]: Watching system buttons on /dev/input/event2 (Power Button) [ 25.382234] systemd-logind[2022]: Watching system buttons on /dev/input/event1 (Power Button) [ 27.490434] systemd-logind[2022]: Failed to start user service: Unknown unit: user@1000.service [ 27.501213] systemd-logind[2022]: New session 1 of user user. [ 50.139474] Key type dns_resolver registered [ 50.193033] FS-Cache: Netfs 'cifs' registered for caching [ 50.193120] Key type cifs.spnego registered [ 50.193136] Key type cifs.idmap registered [ 51.225073] BUG: unable to handle kernel NULL pointer dereference at 0058 [ 51.225196] IP: [] crypto_shash_setkey+0x1c/0xc0 [ 51.225289] PGD 0 [ 51.225322] Oops: [#1] SMP [ 51.225350] Modules linked in: md4 hmac nls_utf8 cifs dns_resolver ctr ccm cpufreq_powersave cpufreq_stats cpufreq_userspace cpufreq_conservative nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc fuse lp arc4 rt61pci rt2x00pci rt2x00mmio rt2x00lib eeprom_93cx6 mac80211 cfg80211 rfkill crc_itu_t iTCO_wdt iTCO_vendor_support ppdev lpc_ich parport_pc mfd_core parport pcspkr rng_core serio_raw evdev snd_intel8x0 snd_ac97_codec shpchp snd_pcm snd_timer snd soundcore ac97_bus acpi_cpufreq processor ext4 crc16 mbcache jbd2 xts gf128mul algif_skcipher af_alg dm_crypt dm_mod nouveau mxm_wmi ttm sd_mod crc_t10dif sg crct10dif_generic sr_mod cdrom crct10dif_common ata_generic ata_piix psmouse libata scsi_mod wmi floppy i915 i2c_algo_bit tg3 video ptp drm_kms_helper pps_core libphy ehci_pci uhci_hcd [ 51.225998] ehci_hcd button drm i2c_core thermal_sys usbcore usb_common [ 51.226053] CPU: 1 PID: 2639 Comm: mount.cifs Not tainted 3.16.0-6-amd64 #1 Debian 3.16.57-2 [ 51.226106] Hardware name: Hewlett-Packard HP Compaq dc7100 CMT(PE224ET)/0968h, BIOS 786C1 v02.15 08/07/2008 [ 51.226168] task: 88007a190cf0 ti: 88007b39c000 task.ti: 88007b39c000 [ 51.226215] RIP: 0010:[] [] crypto_shash_setkey+0x1c/0xc0 [ 51.226274] RSP: 0018:88007b39fa68 EFLAGS: 00010292 [ 51.226309] RAX: 88003697ee00 RBX: 0002 RCX: 88007ace4800 [ 51.226354] RDX: 0010 RSI: 88003697ef18 RDI: [ 51.226400] RBP: R08: 88007adfbf08 R09: [ 51.226445] R10: 756574735c53414e R11: 88007b5cf800 R12: 88003697ef18 [
Bug#961130: ethtool can read DOM values
Ben Hutchings writes: > On Wed, 2020-05-20 at 13:09 +, Yannis Aribaud wrote: >> Package: ethtool >> Version: 1:4.19-1 >> Severity: important >> The command ethtool -m is unable to read the transceiver DOM values. > > Again, this is a driver or hardware issue, not a bug in ethtool. > > [...] >> As you can see all mesuring values are zeros. >> I am using Debian GNU/Linux 10 (buster), kernel 4.19.0-9-amd64 #1 SMP >> Debian 4.19.118-2 (2020-04-29) x86_64 GNU/Linux and libc6 2.28-10 >> >> FYI, I get correct values using SystemRescueCD 6 (ethtool 5.0, kernel >> 4.19.34-1-lts) on this same hardware, using the same command. > > I see no changes to ethtool between 4.19 and 5.0 that would explain > that. I assume you're aware of this, but there are some interesting changes in that driver between v4.19.34 and v4.19.118 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit?id=7da11d6a5d85ab3f4d28fa660d8c90566fdaa1e6 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit?id=935f39807a7e95678e5bda50757af326691a211c The net effect seems to be that they removed the part that actually made DOM reading work. Makes me wonder what happens if you revert both those patches? I don't have the hardware, so I can't test.. This issue might also be fixed in mainline with the more generic high page support for QSFP28 and QSFP+? Bjørn
