linux_5.5.13-1_source.changes is NEW

[Debian FTP Masters]

binary:acpi-modules-5.5.0-1-686-di is NEW.
binary:acpi-modules-5.5.0-1-686-pae-di is NEW.
binary:acpi-modules-5.5.0-1-amd64-di is NEW.
binary:affs-modules-5.5.0-1-4kc-malta-di is NEW.
binary:affs-modules-5.5.0-1-5kc-malta-di is NEW.
binary:affs-modules-5.5.0-1-loongson-3-di is NEW.
binary:affs-modules-5.5.0-1-octeon-di is NEW.
binary:ata-modules-5.5.0-1-4kc-malta-di is NEW.
binary:ata-modules-5.5.0-1-5kc-malta-di is NEW.
binary:ata-modules-5.5.0-1-686-di is NEW.
binary:ata-modules-5.5.0-1-686-pae-di is NEW.
binary:ata-modules-5.5.0-1-amd64-di is NEW.
binary:ata-modules-5.5.0-1-arm64-di is NEW.
binary:ata-modules-5.5.0-1-armmp-di is NEW.
binary:ata-modules-5.5.0-1-loongson-3-di is NEW.
binary:ata-modules-5.5.0-1-powerpc64le-di is NEW.
binary:btrfs-modules-5.5.0-1-4kc-malta-di is NEW.
binary:btrfs-modules-5.5.0-1-5kc-malta-di is NEW.
binary:btrfs-modules-5.5.0-1-686-di is NEW.
binary:btrfs-modules-5.5.0-1-686-pae-di is NEW.
binary:btrfs-modules-5.5.0-1-amd64-di is NEW.
binary:btrfs-modules-5.5.0-1-arm64-di is NEW.
binary:btrfs-modules-5.5.0-1-armmp-di is NEW.
binary:btrfs-modules-5.5.0-1-loongson-3-di is NEW.
binary:btrfs-modules-5.5.0-1-marvell-di is NEW.
binary:btrfs-modules-5.5.0-1-octeon-di is NEW.
binary:btrfs-modules-5.5.0-1-powerpc64le-di is NEW.
binary:btrfs-modules-5.5.0-1-s390x-di is NEW.
binary:cdrom-core-modules-5.5.0-1-4kc-malta-di is NEW.
binary:cdrom-core-modules-5.5.0-1-5kc-malta-di is NEW.
binary:cdrom-core-modules-5.5.0-1-686-di is NEW.
binary:cdrom-core-modules-5.5.0-1-686-pae-di is NEW.
binary:cdrom-core-modules-5.5.0-1-amd64-di is NEW.
binary:cdrom-core-modules-5.5.0-1-arm64-di is NEW.
binary:cdrom-core-modules-5.5.0-1-armmp-di is NEW.
binary:cdrom-core-modules-5.5.0-1-loongson-3-di is NEW.
binary:cdrom-core-modules-5.5.0-1-marvell-di is NEW.
binary:cdrom-core-modules-5.5.0-1-octeon-di is NEW.
binary:cdrom-core-modules-5.5.0-1-powerpc64le-di is NEW.
binary:cdrom-core-modules-5.5.0-1-s390x-di is NEW.
binary:compress-modules-5.5.0-1-4kc-malta-di is NEW.
binary:compress-modules-5.5.0-1-5kc-malta-di is NEW.
binary:compress-modules-5.5.0-1-686-di is NEW.
binary:compress-modules-5.5.0-1-686-pae-di is NEW.
binary:compress-modules-5.5.0-1-amd64-di is NEW.
binary:compress-modules-5.5.0-1-arm64-di is NEW.
binary:compress-modules-5.5.0-1-armmp-di is NEW.
binary:compress-modules-5.5.0-1-loongson-3-di is NEW.
binary:compress-modules-5.5.0-1-marvell-di is NEW.
binary:compress-modules-5.5.0-1-octeon-di is NEW.
binary:compress-modules-5.5.0-1-powerpc64le-di is NEW.
binary:compress-modules-5.5.0-1-s390x-di is NEW.
binary:crc-modules-5.5.0-1-4kc-malta-di is NEW.
binary:crc-modules-5.5.0-1-5kc-malta-di is NEW.
binary:crc-modules-5.5.0-1-686-di is NEW.
binary:crc-modules-5.5.0-1-686-pae-di is NEW.
binary:crc-modules-5.5.0-1-amd64-di is NEW.
binary:crc-modules-5.5.0-1-arm64-di is NEW.
binary:crc-modules-5.5.0-1-armmp-di is NEW.
binary:crc-modules-5.5.0-1-loongson-3-di is NEW.
binary:crc-modules-5.5.0-1-marvell-di is NEW.
binary:crc-modules-5.5.0-1-octeon-di is NEW.
binary:crc-modules-5.5.0-1-powerpc64le-di is NEW.
binary:crc-modules-5.5.0-1-s390x-di is NEW.
binary:crypto-dm-modules-5.5.0-1-4kc-malta-di is NEW.
binary:crypto-dm-modules-5.5.0-1-5kc-malta-di is NEW.
binary:crypto-dm-modules-5.5.0-1-686-di is NEW.
binary:crypto-dm-modules-5.5.0-1-686-pae-di is NEW.
binary:crypto-dm-modules-5.5.0-1-amd64-di is NEW.
binary:crypto-dm-modules-5.5.0-1-arm64-di is NEW.
binary:crypto-dm-modules-5.5.0-1-armmp-di is NEW.
binary:crypto-dm-modules-5.5.0-1-loongson-3-di is NEW.
binary:crypto-dm-modules-5.5.0-1-marvell-di is NEW.
binary:crypto-dm-modules-5.5.0-1-octeon-di is NEW.
binary:crypto-dm-modules-5.5.0-1-powerpc64le-di is NEW.
binary:crypto-dm-modules-5.5.0-1-s390x-di is NEW.
binary:crypto-modules-5.5.0-1-4kc-malta-di is NEW.
binary:crypto-modules-5.5.0-1-5kc-malta-di is NEW.
binary:crypto-modules-5.5.0-1-686-di is NEW.
binary:crypto-modules-5.5.0-1-686-pae-di is NEW.
binary:crypto-modules-5.5.0-1-amd64-di is NEW.
binary:crypto-modules-5.5.0-1-arm64-di is NEW.
binary:crypto-modules-5.5.0-1-armmp-di is NEW.
binary:crypto-modules-5.5.0-1-loongson-3-di is NEW.
binary:crypto-modules-5.5.0-1-marvell-di is NEW.
binary:crypto-modules-5.5.0-1-octeon-di is NEW.
binary:crypto-modules-5.5.0-1-powerpc64le-di is NEW.
binary:crypto-modules-5.5.0-1-s390x-di is NEW.
binary:dasd-extra-modules-5.5.0-1-s390x-di is NEW.
binary:dasd-modules-5.5.0-1-s390x-di is NEW.
binary:efi-modules-5.5.0-1-686-di is NEW.
binary:efi-modules-5.5.0-1-686-pae-di is NEW.
binary:efi-modules-5.5.0-1-amd64-di is NEW.
binary:efi-modules-5.5.0-1-arm64-di is NEW.
binary:efi-modules-5.5.0-1-armmp-di is NEW.
binary:event-modules-5.5.0-1-4kc-malta-di is NEW.
binary:event-modules-5.5.0-1-5kc-malta-di is NEW.
binary:event-modules-5.5.0-1-686-di is NEW.
binary:event-modules-5.5.0-1-686-pae-di is NEW.
binary:event-modules-5.5.0-1-amd64-di is NEW.
binary:event-modules-5.5.0-1-arm64-di is NEW.
binary:event-modules-5.5.0-1-armmp-di is NEW.

Processing of linux_5.5.13-1_source.changes

[Debian FTP Masters]

linux_5.5.13-1_source.changes uploaded successfully to localhost
along with the files:
  linux_5.5.13-1.dsc
  linux_5.5.13.orig.tar.xz
  linux_5.5.13-1.debian.tar.xz
  linux_5.5.13-1_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Bug#952108: Cloud variant: please enable CONFIG_VHOST_SCSI

[Ben Hutchings]

On Mon, 2020-03-02 at 22:50 -0800, Josh Triplett wrote:
> On Mon, Mar 02, 2020 at 10:26:35PM -0800, Noah Meyerhans wrote:
> > On Sun, Feb 23, 2020 at 12:28:53AM -0800, Josh Triplett wrote:
> > > The normal Debian kernel configuration has CONFIG_VHOST_SCSI enabled,
> > > but the cloud configuration does not seem to have it enabled. Please
> > > enable CONFIG_VHOST_SCSI=m on the cloud configuration as well.
> > 
> > Out of curiosity, where is this actually needed?
> 
> Nested virtualization; vhost-scsi is needed on the host to serve disks
> to a nested guest.

I think that might be out-of-scope for the cloud flavour, as I think
the idea is to provide a smaller package that doesn't do everything.

But as someone who has very little experience in cloudy stuff, I don't
feel qualified to make a final decision on this myself.

Ben.

-- 
Ben Hutchings
It is impossible to make anything foolproof
because fools are so ingenious.




signature.asc
Description: This is a digitally signed message part

Bug#954088: Please enable GVT-g support

[Ben Hutchings]

On Mon, 2020-03-16 at 16:25 +0100, Lee Garrett wrote:
> Package: linux-image-amd64
> Version: 5.4.19-1
> Severity: wishlist
> 
> Hi Ben,
> 
> please consider enabling the following settings in the Debian kernel:
> 
> (mediated devices, needed to enable the lower settings)
> CONFIG_VFIO_MDEV=m
> CONFIG_VFIO_MDEV_DEVICE=m
> 
> (enable kvm/xen support for gvt)
> CONFIG_DRM_I915_GVT=y
> CONFIG_DRM_I915_GVT_KVMGT=m

Done, except that this doesn't exist yet:

> CONFIG_DRM_I915_GVT_XENGT=m
[...]

Ben.

-- 
Ben Hutchings
It is impossible to make anything foolproof
because fools are so ingenious.




signature.asc
Description: This is a digitally signed message part

Processed: Re: Bug#954245: Fresh installed debian stucks in 'Load initramfs' screen on lenovo x230 due to missing module

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:linux 4.19.98-1
Bug #954245 [initramfs-tools] Fresh installed debian stucks in 'Load initramfs' 
screen on lenovo x230 due to missing module
Bug reassigned from package 'initramfs-tools' to 'src:linux'.
No longer marked as found in versions initramfs-tools/0.133+deb10u1.
Ignoring request to alter fixed versions of bug #954245 to the same values 
previously set
Bug #954245 [src:linux] Fresh installed debian stucks in 'Load initramfs' 
screen on lenovo x230 due to missing module
Marked as found in versions linux/4.19.98-1.
> tag -1 moreinfo
Bug #954245 [src:linux] Fresh installed debian stucks in 'Load initramfs' 
screen on lenovo x230 due to missing module
Added tag(s) moreinfo.

-- 
954245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#954245: Fresh installed debian stucks in 'Load initramfs' screen on lenovo x230 due to missing module

[Ben Hutchings]

Control: reassign -1 src:linux 4.19.98-1
Control: tag -1 moreinfo

On Thu, 2020-03-19 at 10:27 +0100, Dimitri Schwarz wrote:
> Package: initramfs-tools
> Version: 0.133+deb10u1
> 
> To reproduce the issue described in the subject:
>   1.) Download a recent debian-netinst.iso (tested with debian-
> 10.3.0-amd64-netinst.iso)
>   2.) Run into installation-process
>   3.) Let the network-configuration fail
>   4.) Continue without network
>   5.) Choose encrypted lvm
>   6.) Install the base-system only (no mirrors)
>   7.) Finish the installation and reboot
> 
> After the reboot the system freezes in grubs 'Loading initramfs'
> screen, because the i915 mode setting driver is missing in the
> initramfs.
[...]

It should not be needed.  On PCs, the system firmware sets up the
display and the kernel (like GRUB) will use a generic graphics driver
until the i915 or other hardware-specific driver is loaded.

I have an X230 here and tried removing plymouth, and it was still able
to prompt for my disk encryption password.  However, it's been upgraded
from an earlier release and is booting in BIOS mode.

* Does your system boot in BIOS or UEFI mode?  (You can tell by
checking whether grub-pc or grub-efi-amd64 is installed.)

* Does it make any difference if you use the "recovery mode" entry in
the GRUB menu?

Ben.

-- 
Ben Hutchings
It is impossible to make anything foolproof
because fools are so ingenious.



signature.asc
Description: This is a digitally signed message part

Processed: fixed 954817 in 5.5~rc5-1~exp1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 954817 5.5~rc5-1~exp1
Bug #954817 [src:linux] linux-image-5.4.0-4-amd64: NULL pointer dereference in 
i915_active_acquire since Linux 5.4
Marked as fixed in versions linux/5.5~rc5-1~exp1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
954817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#954817: marked as done (linux-image-5.4.0-4-amd64: NULL pointer dereference in i915_active_acquire since Linux 5.4)

[Debian Bug Tracking System]

Your message dated Mon, 30 Mar 2020 01:49:34 +0100
with message-id <466abaa4a1e687e8ce8c0bb6d36cdbd1b9aa30c8.ca...@decadent.org.uk>
and subject line Re: Bug#954817: linux-image-5.4.0-4-amd64: NULL pointer 
dereference in i915_active_acquire since Linux 5.4
has caused the Debian Bug report #954817,
regarding linux-image-5.4.0-4-amd64: NULL pointer dereference in 
i915_active_acquire since Linux 5.4
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.)


-- 
954817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.4.19-1
Severity: important
Tags: patch

Dear Maintainer,

Since kernel 5.4.x I am getting crashes during some graphic rendering poccess 
like playing videos. I found the following patch might fix this problem. 
The patch already got into kernel 5.5.x but still not into 5.4.x. Could you 
patch it into kernel 5.4.x? Or release the kernel 5.5 version? Thanks!

Patchwork: https://patchwork.freedesktop.org/patch/345789/?series=70930=3
See also: 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.5.y=e85ade1f50aae464ce196672faa7a099fd1721ed

-- Package-specific info:
** Version:
Linux version 5.4.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 9.2.1 
20200203 (Debian 9.2.1-28)) #1 SMP Debian 5.4.19-1 (2020-02-13)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.4.0-4-amd64 
root=UUID=bc9fa405-daee-4f2a-a27a-44e1c0513187 ro quiet

** Tainted: OE (12288)
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
Mar 16 18:39:24 Server kernel: [606320.517436] BUG: kernel NULL pointer 
dereference, address: 0040

Mar 16 18:39:24 Server kernel: [606320.517453] #PF: supervisor read access in 
kernel mode

Mar 16 18:39:24 Server kernel: [606320.517454] #PF: error_code(0x) - 
not-present page

Mar 16 18:39:24 Server kernel: [606320.517455] PGD 0 P4D 0

Mar 16 18:39:24 Server kernel: [606320.517461] Oops:  [#1] SMP PTI

Mar 16 18:39:24 Server kernel: [606320.517469] CPU: 3 PID: 2072967 Comm: xfwm4 
Tainted: G  OE5.4.0-4-amd64 #1 Debian 5.4.19-1

Mar 16 18:39:24 Server kernel: [606320.517471] Hardware name: To Be Filled By 
O.E.M. To Be Filled By O.E.M./H310M-ITX/ac, BIOS P3.10 09/27>

Mar 16 18:39:24 Server kernel: [606320.517745] RIP: 
0010:i915_active_acquire+0x9/0x70 [i915]

Mar 16 18:39:24 Server kernel: [606320.517751] Code: 00 00 00 48 c7 46 58 00 00 
00 00 c7 46 38 00 00 00 00 48 c7 c6 0a a0 65 c0 e9 33 90 7>

Mar 16 18:39:24 Server kernel: [606320.517753] RSP: 0018:a06400e07a40 
EFLAGS: 00010286

Mar 16 18:39:24 Server kernel: [606320.517757] RAX:  RBX: 
8da74554f480 RCX: 

Mar 16 18:39:24 Server kernel: [606320.517759] RDX: 8da642d61200 RSI: 
8da74554f480 RDI: 0008

Mar 16 18:39:24 Server kernel: [606320.517760] RBP: 8da642d61200 R08: 
8da74a4db988 R09: 8da74a4db988

Mar 16 18:39:24 Server kernel: [606320.517761] R10: a000 R11: 
 R12: 0008

Mar 16 18:39:24 Server kernel: [606320.517763] R13: 0004 R14: 
8da642d61200 R15: 401c

Mar 16 18:39:24 Server kernel: [606320.517765] FS: 7f5f29303f00() 
GS:8da8a5f8() knlGS:

Mar 16 18:39:24 Server kernel: [606320.517767] CS: 0010 DS:  ES:  CR0: 
80050033

Mar 16 18:39:24 Server kernel: [606320.517767] CR2: 0040 CR3: 
79d4a006 CR4: 003606e0

Mar 16 18:39:24 Server kernel: [606320.517768] Call Trace:

Mar 16 18:39:24 Server kernel: [606320.517910] i915_active_ref+0x21/0x210 [i915]

Mar 16 18:39:24 Server kernel: [606320.518049] ? intel_fbc_deactivate+0x38/0x60 
[i915]

Mar 16 18:39:24 Server kernel: [606320.518182] 
i915_vma_move_to_active+0x6e/0xf0 [i915]

Mar 16 18:39:24 Server kernel: [606320.518371] 
i915_gem_do_execbuffer+0xc62/0x1520 [i915]

Mar 16 18:39:24 Server kernel: [606320.518404] ? _cond_resched+0x15/0x30

Mar 16 18:39:24 Server kernel: [606320.518416] ? mutex_lock+0xe/0x30

Mar 16 18:39:24 Server kernel: [606320.518439] ? 
unix_stream_read_generic+0x1f7/0x8f0

Mar 16 18:39:24 Server kernel: [606320.518456] ? __kmalloc_node+0x1f5/0x300

Mar 16 18:39:24 Server kernel: [606320.518636] 
i915_gem_execbuffer2_ioctl+0x1df/0x3d0 [i915]

Mar 16 18:39:24 Server kernel: [606320.518764] ? 
i915_gem_madvise_ioctl+0x13a/0x290 [i915]

Mar 16 18:39:24 Server kernel: [606320.518874] ? 
i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915]

Mar 16 18:39:24 Server 

Bug#955022: marked as done (i915: Frequent graphics lockups; GPU HANG: ecode 9:1:0x00000000, hang on rcs0)

[Debian Bug Tracking System]

Your message dated Mon, 30 Mar 2020 01:45:04 +0100
with message-id 
and subject line Re: Bug#955022: i915: Frequent graphics lockups; GPU HANG: 
ecode 9:1:0x, hang on rcs0
has caused the Debian Bug report #955022,
regarding i915: Frequent graphics lockups; GPU HANG: ecode 9:1:0x, hang 
on rcs0
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.)


-- 
955022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955022
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.4.19-1
Severity: important

Multiple times a day, my graphical session will freeze. If I'm in a video call,
sometimes the audio continues, other times it breaks into a loop. Sometimes
recoverable with SAK, so I can continue without rebooting after waiting a bit. 

I don't have a definite reproduction case; sometimes it will be fine for a day
or so, or today, where it happened twice, most recently <45m after boot.
Appears to be more likely when switching virtual workspaces in SwayWM
(Wayland), and always appears to be mid-render of a graphics effect from a
video or an image transition.

I believe this started with 5.4.0-4-amd64[1], I don't recall it happening
before I updated from 5.4.0-3-amd64 earlier this month.

I suspect this is the same issue as this upstream bug[3], which indicates it's
fixed in 5.5, and it looks like Ubuntu backported this to 5.4[4].

Attached are ``/sys/class/drm/card0/error`` for the last two crashes. 

[1]: 5.4.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 9.2.1 20200203 
(Debian 9.2.1-28)) #1 SMP Debian 5.4.19-1 (2020-02-13)
[2]: 5.4.0-3-amd64 (debian-kernel@lists.debian.org) (gcc version 9.2.1 20200117 
(Debian 9.2.1-24)) #1 SMP Debian 5.4.13-1 (2020-01-19)
[3]: https://gitlab.freedesktop.org/drm/intel/issues/673
[4]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395

Please let me know if there's any additional information I can provide.

Cheers,
Luke Faraone

-- Package-specific info:
** Version:
Linux version 5.4.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 9.2.1 
20200203 (Debian 9.2.1-28)) #1 SMP Debian 5.4.19-1 (2020-02-13)

** Command line:
BOOT_IMAGE=/vmlinuz-5.4.0-4-amd64 root=/dev/mapper/debvg-root ro quiet 
cgroup_enable=memory

** Not tainted

** Kernel log:
[ 1647.162227] hid-generic 0003:1050:0116.0013: input,hidraw4: USB HID v1.10 
Keyboard [Yubico Yubikey NEO OTP+U2F+CCID] on usb-:00:14.0-8.1/input0
[ 1647.163235] hid-generic 0003:1050:0116.0014: hiddev1,hidraw5: USB HID v1.10 
Device [Yubico Yubikey NEO OTP+U2F+CCID] on usb-:00:14.0-8.1/input1
[ 1652.879527] usb 1-8.1: USB disconnect, device number 13
[ 2548.286765] usb 1-8.1: new full-speed USB device number 14 using xhci_hcd
[ 2548.397134] usb 1-8.1: New USB device found, idVendor=1050, idProduct=0116, 
bcdDevice= 3.42
[ 2548.397136] usb 1-8.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[ 2548.397137] usb 1-8.1: Product: Yubikey NEO OTP+U2F+CCID
[ 2548.397138] usb 1-8.1: Manufacturer: Yubico
[ 2548.414445] input: Yubico Yubikey NEO OTP+U2F+CCID as 
/devices/pci:00/:00:14.0/usb1/1-8/1-8.1/1-8.1:1.0/0003:1050:0116.0015/input/input31
[ 2548.471349] hid-generic 0003:1050:0116.0015: input,hidraw4: USB HID v1.10 
Keyboard [Yubico Yubikey NEO OTP+U2F+CCID] on usb-:00:14.0-8.1/input0
[ 2548.472439] hid-generic 0003:1050:0116.0016: hiddev1,hidraw5: USB HID v1.10 
Device [Yubico Yubikey NEO OTP+U2F+CCID] on usb-:00:14.0-8.1/input1
[ 2558.098065] usb 1-8.1: USB disconnect, device number 14
[ 2564.230766] usb 1-2: new full-speed USB device number 15 using xhci_hcd
[ 2564.380688] usb 1-2: New USB device found, idVendor=1050, idProduct=0407, 
bcdDevice= 4.37
[ 2564.380694] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2564.380697] usb 1-2: Product: Yubikey 4 OTP+U2F+CCID
[ 2564.380700] usb 1-2: Manufacturer: Yubico
[ 2564.386624] input: Yubico Yubikey 4 OTP+U2F+CCID as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:1050:0407.0017/input/input32
[ 2564.443522] hid-generic 0003:1050:0407.0017: input,hidraw4: USB HID v1.10 
Keyboard [Yubico Yubikey 4 OTP+U2F+CCID] on usb-:00:14.0-2/input0
[ 2564.444788] hid-generic 0003:1050:0407.0018: hiddev1,hidraw5: USB HID v1.10 
Device [Yubico Yubikey 4 OTP+U2F+CCID] on usb-:00:14.0-2/input1
[ 2576.846425] usb 1-2: USB disconnect, device number 15
[ 2782.143185] i915 :00:02.0: GPU HANG: ecode 9:1:0x, hang on rcs0
[ 2782.144195] i915 :00:02.0: Resetting rcs0 for hang on rcs0
[ 2782.144965] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed 

Bug#955232: Please add 9p kernel module to the cloud image.

[Ben Hutchings]

Control: tag -1 moreinfo

On Sat, 2020-03-28 at 23:02 +0600, Albert Akchurin wrote:
> Package: linux-image-cloud-amd64
> Severity: wishlist
> 
> Please consider adding kernel module '9p' to the cloud image. It is
> impossible to passthrough filesystem from hypervisor with the current cloud
> image and there are no additional packages to install it. The only way that
> I know to passthrough filesystem currently is to remove
> linux-image-cloud-amd64 and install linux-image-amd64.

The "cloud" images are specifically meant for running on public clouds,
and don't support everything that could possibly be exposed to a VM.

Is there a public cloud that supports 9p passthrough?

Ben.

-- 
Ben Hutchings
It is impossible to make anything foolproof
because fools are so ingenious.




signature.asc
Description: This is a digitally signed message part

Bug#954778: Patch: Suppress irrelevant warning when generating a debian package

[Masahiro Yamada]

On Mon, Mar 30, 2020 at 12:01 AM Reinhard Karcher
 wrote:
>
> There was a blank line missing between the package definitions.
> Sorry for late testing.
>
> --
> Best regards
> Reinhard Karcher


The attached patch is not in a correct patch format.

This time, I manually crufted the format, and applied.

But, next time, please send it to ML instead of attachment,
in a correct format.

git supports useful commands to do this.

  [1]  "git format-patch"  to create a patch
  [2]  "git send-email" to send it to ML


I reworded the log as follows:

-->8---
kbuild: deb-pkg: fix warning when CONFIG_DEBUG_INFO is unset

Creating a Debian package without CONFIG_DEBUG_INFO produces
a warning that no debug package was created.

This patch excludes the debug package from the control file,
if no debug package is created by this configuration.

Signed-off-by: Reinhard Karcher 
Signed-off-by: Masahiro Yamada 
-->8---


-- 
Best Regards
Masahiro Yamada

Processed: Re: Bug#955232: Please add 9p kernel module to the cloud image.

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #955232 [linux-image-cloud-amd64] Please add 9p kernel module to the cloud 
image.
Added tag(s) moreinfo.

-- 
955232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955232
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#955329: linux-image-4.9.0-12-amd64: cryptsetup (sda3_crypt) : unknown fstype, bad password or options

[David Christensen]

Package: src:linux
Version: 4.9.210-1
Severity: important

Dear Maintainer,

When I upgrade the kernel:

2020-03-29 16:48:15 root@po ~
# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  linux-image-4.9.0-12-amd64
The following packages will be upgraded:
  linux-image-amd64
1 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 39.3 MB of archives.
After this operation, 193 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ftp.us.debian.org/debian stretch/main amd64 
linux-image-4.9.0-12-amd64 amd64 4.9.210-1 [39.3 MB]
Get:2 http://ftp.us.debian.org/debian stretch/main amd64 
linux-image-amd64 amd64 4.9+80+deb9u10 [7158 B]
Fetched 39.3 MB in 28s (1381 kB/s)  
   
Reading changelogs... Done
Selecting previously unselected package linux-image-4.9.0-12-amd64.
(Reading database ... 106066 files and directories currently installed.)
Preparing to unpack .../linux-image-4.9.0-12-amd64_4.9.210-1_amd64.deb 
...
Unpacking linux-image-4.9.0-12-amd64 (4.9.210-1) ...
Preparing to unpack .../linux-image-amd64_4.9+80+deb9u10_amd64.deb ...
Unpacking linux-image-amd64 (4.9+80+deb9u10) over (4.9+80+deb9u9) ...
Setting up linux-image-4.9.0-12-amd64 (4.9.210-1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.9.0-11-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-4.9.0-11-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-4.9.0-12-amd64
I: /initrd.img is now a symlink to boot/initrd.img-4.9.0-12-amd64
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.9.0-12-amd64
cryptsetup: WARNING: target sda2_crypt has a random key, skipped
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found background image: .background_cache.png
Found linux image: /boot/vmlinuz-4.9.0-12-amd64
Found initrd image: /boot/initrd.img-4.9.0-12-amd64
Found linux image: /boot/vmlinuz-4.9.0-11-amd64
Found initrd image: /boot/initrd.img-4.9.0-11-amd64
Found linux image: /boot/vmlinuz-4.9.0-9-amd64
Found initrd image: /boot/initrd.img-4.9.0-9-amd64
done
Setting up linux-image-amd64 (4.9+80+deb9u10) ...

And then reboot:

Please unlock disk /dev/disk/by-partuuid/-xx (sda3_crypt):
cryptsetup (sda3_crypt) : unknown fstype, bad password or options?
Please unlock disk /dev/disk/by-partuuid/-xx (sda3_crypt):
cryptsetup (sda3_crypt) : unknown fstype, bad password or options?
Please unlock disk /dev/disk/by-partuuid/-xx (sda3_crypt):
cryptsetup (sda3_crypt) : unknown fstype, bad password or options?
cryptsetup (sda3_crypt) : maximum number of tries exceeded
cryptsetup: going to sleep for 60 seconds...


The root LUKS container will not unlock with the correct key.


My work-around is to boot the previous kernel.  LUKS then works.


David



-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: 
product_name: 
product_version: 
chassis_vendor: 
chassis_version: 
bios_vendor: Intel Corp.
bios_version: SWQ6710H.86A.0068.2017.0601.1423
board_vendor: Intel Corporation
board_name: DQ67SW
board_version: AAG12527-310

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor 
Family DRAM Controller [8086:0100] (rev 09)
Subsystem: Intel Corporation 2nd Generation Core Processor Family DRAM 
Controller [8086:2008]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snb_uncore

00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port [8086:0101] (rev 09) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 
00 [VGA controller])
Subsystem: Intel Corporation 2nd Generation Core Processor Family 
Integrated 

Re: apply patch from master branch also to sid

[Florian La Roche]

Hello Ben,

I look forward to 5.5.13 in unstable and hopefully soon testing.

Only for the RT variants it would make sense to also keep the 5.4.y kernels
around and also update them to newer 5.4.y releases. (But yeah, that's
not really
mainstream usage, I know...)

best regards,

Florian La Roche


Am So., 29. März 2020 um 20:43 Uhr schrieb Ben Hutchings :
>
> On Sun, 2020-03-29 at 18:23 +0200, Florian La Roche wrote:
> > Hello,
> >
> > I think the following patch from the master branch should also go into
> > the sid branch on salsa:
> >
> > https://salsa.debian.org/kernel-team/linux/-/commit/7a54cc60ba9fb2c1d018e7eed61fe6cbe0c055e4
>
> master will be merged to sid soon.
>
> Ben.
>
> --
> Ben Hutchings
> I'm always amazed by the number of people who take up solipsism because
> they heard someone else explain it. - E*Borg on alt.fan.pratchett
>
>

Bug#930527: linux-image-4.19.0-5-amd64: when logging out, not the whole screen is erased, leaving private information

[Vincent Lefevre]

On 2020-03-29 19:10:30 +0200, Ivo De Decker wrote:
> On Fri, Jun 14, 2019 at 04:31:16PM +0200, Vincent Lefevre wrote:
> > When logging out, a part of the previous session is still visible.
> > This might be used to compromise the user's account or leak other
> > private information, depending on what was written on the screen.
> 
> What do you mean exactly? Is the screen only erased partially, or not at all?

It was partially erased.

> Is there something specific about your setup that you think might be relevant
> here?

I don't think so, except the use of the nouveau driver, of course.
But there were no issues for years. I think that problems started
to occur after some kernel upgrade. Now, I haven't had any problem
since December, I think.

> Also, I don't think this bug is really 'grave'. Even if private information
> remains on the screen, the user can see that, and take action to avoid it.

Not if one logs out remotely.

Regards,

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: apply patch from master branch also to sid

[Ben Hutchings]

On Sun, 2020-03-29 at 18:23 +0200, Florian La Roche wrote:
> Hello,
> 
> I think the following patch from the master branch should also go into
> the sid branch on salsa:
> 
> https://salsa.debian.org/kernel-team/linux/-/commit/7a54cc60ba9fb2c1d018e7eed61fe6cbe0c055e4

master will be merged to sid soon.

Ben.

-- 
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett




signature.asc
Description: This is a digitally signed message part

Bug#930527: linux-image-4.19.0-5-amd64: when logging out, not the whole screen is erased, leaving private information

[Ivo De Decker]

Hi,

On Fri, Jun 14, 2019 at 04:31:16PM +0200, Vincent Lefevre wrote:
> When logging out, a part of the previous session is still visible.
> This might be used to compromise the user's account or leak other
> private information, depending on what was written on the screen.

What do you mean exactly? Is the screen only erased partially, or not at all?
Is there something specific about your setup that you think might be relevant
here?

When I try logging in on the console, and then log out, my screen is erased
completely.

Also, I don't think this bug is really 'grave'. Even if private information
remains on the screen, the user can see that, and take action to avoid it.

Cheers,

Ivo

apply patch from master branch also to sid

[Florian La Roche]

Hello,

I think the following patch from the master branch should also go into
the sid branch on salsa:

https://salsa.debian.org/kernel-team/linux/-/commit/7a54cc60ba9fb2c1d018e7eed61fe6cbe0c055e4

Thanks a lot,

Florian La Roche

Bug#954778: Patch: Suppress irrelevant warning when generating a debian package

[Reinhard Karcher]

There was a blank line missing between the package definitions.
Sorry for late testing.

--
Best regards
Reinhard Karcher
from Reinhard.Karcher reinhard.karc...@gmx.net

Creating a Debian package by compiling the kernel
make bindeb-pkg
without creating debug information creates a warning that no
debug package was created
This patch excludes the debug package from the control file,
if no debug package is created by this configuration

Signed-off-by:Reinhard Karcher 

diff --git a/scripts/package/mkdebian b/scripts/package/mkdebian
index 357dc56bcf30..df1adbfb8ead 100755
--- a/scripts/package/mkdebian
+++ b/scripts/package/mkdebian
@@ -198,6 +198,10 @@ Description: Linux support headers for userspace development
  This package provides userspaces headers from the Linux kernel.  These headers
  are used by the installed headers for GNU glibc and other system libraries.
 Multi-Arch: same
+EOF
+
+if is_enabled CONFIG_DEBUG_INFO; then
+cat <> debian/control

 Package: $dbg_packagename
 Section: debug
@@ -206,6 +210,7 @@ Description: Linux kernel debugging symbols for $version
  This package will come in handy if you need to debug the kernel. It provides
  all the necessary debug symbols for the kernel and its modules.
 EOF
+fi

 cat < debian/rules
 #!$(command -v $MAKE) -f

Bug#954778: Patch: Suppress irrelevant warning when generating a debian package

[Reinhard Karcher]

Am Sonntag, 29. März 2020, 15:30 schrieb Masahiro Yamada:
> 
> I want you to directly use
> 
> if is_enabled CONFIG_DEBUG_INFO; then
> ...
> fi
> 

Corrected patch attached

--
Best regards
Reinhard Karcher
from Reinhard.Karcher reinhard.karc...@gmx.net

Creating a Debian package by compiling the kernel
make bindeb-pkg
without creating debug information creates a warning that no
debug package was created
This patch excludes the debug package from the control file,
if no debug package is created by this configuration

Signed-off-by:Reinhard Karcher 

diff --git a/scripts/package/mkdebian b/scripts/package/mkdebian
index 357dc56bcf30..327ea3c2a785 100755
--- a/scripts/package/mkdebian
+++ b/scripts/package/mkdebian
@@ -198,7 +198,10 @@ Description: Linux support headers for userspace development
  This package provides userspaces headers from the Linux kernel.  These headers
  are used by the installed headers for GNU glibc and other system libraries.
 Multi-Arch: same
+EOF

+if is_enabled CONFIG_DEBUG_INFO; then
+cat <> debian/control
 Package: $dbg_packagename
 Section: debug
 Architecture: $debarch
@@ -206,6 +209,7 @@ Description: Linux kernel debugging symbols for $version
  This package will come in handy if you need to debug the kernel. It provides
  all the necessary debug symbols for the kernel and its modules.
 EOF
+fi

 cat < debian/rules
 #!$(command -v $MAKE) -f

Bug#954778: Patch: Suppress irrelevant warning when generating a debian package

[Masahiro Yamada]

On Sun, Mar 29, 2020 at 9:57 PM Reinhard Karcher
 wrote:
>
> Am Sonntag, 29. März 2020, 14:01 schrieb Masahiro Yamada:
> >
> > > By making a contribution to this project, I certify that:
> > > The contribution was created in whole or in part by me and I have the
> > > right to submit it under the open source license indicated in the file.
> >
> > Please drop this.
> >
> > Signed-off-by implies this.
> > No need to explain this in an individual patch.
>
> Droped in attached new version.
>
> > > +if [ -n "$BUILD_DEBUG" ] ; then
> >
> > This file does not define BUILD_DEBUG.
> > So, this conditional is always false, isn't it?
> >
> > It should be:
> >
> > if is_enabled CONFIG_DEBUG_INFO; then
> >
>
> The definition of BUILD_DEBUG is copied from builddeb too.
> See attached patch.


No.

I want you to directly use

if is_enabled CONFIG_DEBUG_INFO; then
...
fi





I guess builddeb used BUILD_DEBUG
to avoid running grep twice.

It does not apply to mkdebian.



-- 
Best Regards
Masahiro Yamada

Bug#954778: Patch: Suppress irrelevant warning when generating a debian package

[Reinhard Karcher]

Am Sonntag, 29. März 2020, 14:01 schrieb Masahiro Yamada:
> 
> > By making a contribution to this project, I certify that:
> > The contribution was created in whole or in part by me and I have the
> > right to submit it under the open source license indicated in the file.
> 
> Please drop this.
> 
> Signed-off-by implies this.
> No need to explain this in an individual patch.

Droped in attached new version.

> > +if [ -n "$BUILD_DEBUG" ] ; then
> 
> This file does not define BUILD_DEBUG.
> So, this conditional is always false, isn't it?
> 
> It should be:
> 
> if is_enabled CONFIG_DEBUG_INFO; then
> 

The definition of BUILD_DEBUG is copied from builddeb too. 
See attached patch.

--
Best regards
Reinhard Karcher
from Reinhard.Karcher reinhard.karc...@gmx.net

Creating a Debian package by compiling the kernel
make bindeb-pkg
without creating debug information creates a warning that no
debug package was created
This patch excludes the debug package from the control file,
if no debug package is created by this configuration

Signed-off-by:Reinhard Karcher 

diff --git a/scripts/package/mkdebian b/scripts/package/mkdebian
index 357dc56bcf30..572abe5a149e 100755
--- a/scripts/package/mkdebian
+++ b/scripts/package/mkdebian
@@ -96,6 +96,7 @@ fi
 sourcename=$KDEB_SOURCENAME
 packagename=linux-image-$version
 kernel_headers_packagename=linux-headers-$version
+BUILD_DEBUG=$(if_enabled_echo CONFIG_DEBUG_INFO Yes)
 dbg_packagename=$packagename-dbg
 debarch=
 set_debarch
@@ -198,7 +199,10 @@ Description: Linux support headers for userspace development
  This package provides userspaces headers from the Linux kernel.  These headers
  are used by the installed headers for GNU glibc and other system libraries.
 Multi-Arch: same
+EOF

+if [ -n "$BUILD_DEBUG" ] ; then
+cat <> debian/control
 Package: $dbg_packagename
 Section: debug
 Architecture: $debarch
@@ -206,6 +210,7 @@ Description: Linux kernel debugging symbols for $version
  This package will come in handy if you need to debug the kernel. It provides
  all the necessary debug symbols for the kernel and its modules.
 EOF
+fi

 cat < debian/rules
 #!$(command -v $MAKE) -f

Bug#954778: Patch: Suppress irrelevant warning when generating a debian package

[Masahiro Yamada]

On Tue, Mar 24, 2020 at 7:24 PM Reinhard Karcher
 wrote:
>
> Creating a Debian package by compiling the kernel using make bindeb-pkg
> without creating debug information creates a warning that no
> debug package was created.
> This patch excludes the debug package from the control file,
> if no debug package is created by this configuration.

OK, this seems correct.

> By making a contribution to this project, I certify that:
> The contribution was created in whole or in part by me and I have the right to
> submit it under the open source license indicated in the file.

Please drop this.

Signed-off-by implies this.
No need to explain this in an individual patch.


> Signed-off-by: Reinhard Karcher 
> ---
> The condition to include the debug package is copied from the file
> builddeb in the same directory.
>
> diff --git a/scripts/package/mkdebian b/scripts/package/mkdebian
> index 357dc56bcf30..1673b9f84804 100755
> --- a/scripts/package/mkdebian
> +++ b/scripts/package/mkdebian
> @@ -198,7 +198,10 @@ Description: Linux support headers for userspace
> development
>   This package provides userspaces headers from the Linux kernel.  These
> headers
>   are used by the installed headers for GNU glibc and other system libraries.
>  Multi-Arch: same
> +EOF
>
> +if [ -n "$BUILD_DEBUG" ] ; then


This file does not define BUILD_DEBUG.
So, this conditional is always false, isn't it?

It should be:

if is_enabled CONFIG_DEBUG_INFO; then




> +cat <> debian/control
>  Package: $dbg_packagename
>  Section: debug
>  Architecture: $debarch
> @@ -206,6 +209,7 @@ Description: Linux kernel debugging symbols for $version
>   This package will come in handy if you need to debug the kernel. It provides
>   all the necessary debug symbols for the kernel and its modules.
>  EOF
> +fi
>
>  cat < debian/rules
>  #!$(command -v $MAKE) -f
>
>
>


-- 
Best Regards
Masahiro Yamada