Processing control commands:
> reassign -1 src:linux 4.19.118-2
Bug #961130 [ethtool] ethtool can read DOM values
Bug reassigned from package 'ethtool' to 'src:linux'.
No longer marked as found in versions ethtool/1:4.19-1.
Ignoring request to alter fixed versions of bug #961130 to the same values
Control: reassign -1 src:linux 4.19.118-2
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.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 20 May 2020 15:03:00 +0100
Source: linux-latest
Binary: linux-source linux-doc linux-perf linux-image-alpha-generic
linux-headers-alpha-generic linux-image-alpha-generic-dbg linux-image-alpha-smp
linux-headers-a
binary:acpi-modules-4.19.0-0.bpo.9-686-di is NEW.
binary:acpi-modules-4.19.0-0.bpo.9-686-pae-di is NEW.
binary:acpi-modules-4.19.0-0.bpo.9-amd64-di is NEW.
binary:affs-modules-4.19.0-0.bpo.9-4kc-malta-di is NEW.
binary:affs-modules-4.19.0-0.bpo.9-5kc-malta-di is NEW.
binary:affs-modules-4.19.0-0.bp
linux-latest_105+deb10u4~bpo9+1_source.changes uploaded successfully to
localhost
along with the files:
linux-latest_105+deb10u4~bpo9+1.dsc
linux-latest_105+deb10u4~bpo9+1.tar.xz
linux-latest_105+deb10u4~bpo9+1_source.buildinfo
Greetings,
Your Debian queue daemon (running on host u
linux_4.19.118-2~bpo9+1_source.changes uploaded successfully to localhost
along with the files:
linux_4.19.118-2~bpo9+1.dsc
linux_4.19.118-2~bpo9+1.debian.tar.xz
linux_4.19.118-2~bpo9+1_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Package: ethtool
Version: 1:4.19-1
Severity: important
The command ethtool -m is unable to read the transceiver DOM values.
Here is a transcript:
root@localhost:~# ethtool -i ens2f0
driver: mlx5_core
version: 5.0-0
firmware-version: 14.25.8000 (DEL2420110034)
expansion-rom-version:
bus-info: 00
On 5/20/20 1:18 PM, Philipp Kern wrote:
> But then I keep wondering how representative qemu is. Is VT220 SCLP even
> something you get on a real z machine? Not that we shouldn't fix qemu,
> of course. But Hercules might be closer to the real thing in this regard.
Hercules shows the exact same beha
On 20.05.20 12:42, Valentin Vidić wrote:
> On Wed, May 20, 2020 at 11:19:53AM +0200, John Paul Adrian Glaubitz wrote:
>> Ah, sorry. I was seeing the cached version of the thread, refreshing helped.
>>
>> In any case, the SPARC kernel maintainer (Dave Miller) had the same argument
>> that it would p
Processing commands for cont...@bugs.debian.org:
> reassign 961056 src:linux,rootskel
Bug #961056 [rootskel] debian-installer: qemu-system-s390x installation fails
due to incorrect serial device
Bug reassigned from package 'rootskel' to 'src:linux,rootskel'.
Ignoring request to alter found versio
Processing commands for cont...@bugs.debian.org:
> merge 961056 926539
Bug #961056 [rootskel] debian-installer: qemu-system-s390x installation fails
due to incorrect serial device
Unable to merge bugs because:
severity of #926539 is 'serious' not 'important'
package of #926539 is 'src:linux,roots
On 5/20/20 12:42 PM, Valentin Vidić wrote:
> It is hard to tell, but it seems the current state is hardcoded
> in different places:
>
> https://www.redhat.com/archives/libguestfs/2017-May/msg00068.html
This wouldn't cause breakage as with your change, the console name
would actually be ttysclp0.
On Wed, May 20, 2020 at 11:19:53AM +0200, John Paul Adrian Glaubitz wrote:
> Ah, sorry. I was seeing the cached version of the thread, refreshing helped.
>
> In any case, the SPARC kernel maintainer (Dave Miller) had the same argument
> that it would potentially break existing setups but eventuall
On 5/20/20 11:17 AM, John Paul Adrian Glaubitz wrote:
> I don't see any discussion in this thread. I would like to know the reasoning
> why kernel upstream thinks that this naming inconsistency is correct. It
> makes no sense, in my opinion and it can potentially trigger more problems.
Ah, sorry.
Hi!
On 5/20/20 11:00 AM, Valentin Vidić wrote:
> Similar change for console name on s390x was not accepted:
>
> https://lkml.org/lkml/2020/5/19/854
>
> so please fix in rootskel.
I don't see any discussion in this thread. I would like to know the reasoning
why kernel upstream thinks that this
Similar change for console name on s390x was not accepted:
https://lkml.org/lkml/2020/5/19/854
so please fix in rootskel.
--
Valentin
It froze again:
May 20 11:48:03 eldfell kernel: general protection fault: [#1] SMP PTI
May 20 11:48:03 eldfell kernel: CPU: 1 PID: 1393 Comm: Xorg Not tainted
5.5.0-0.bpo.2-amd64 #1 Debian 5.5.17-1~bpo10+1
May 20 11:48:03 eldfell kernel: Hardware name: ASUS All Series/Z97-A, BIOS 2501
04/27
17 matches
Mail list logo
