Processed: Re: Bug#916899: linux-image-4.18.0-0.bpo.3-amd64: NULL pointer dereference in i915

Processing control commands: > forcemerge 914495 -1 Bug #914495 {Done: Salvatore Bonaccorso } [src:linux] linux-image-4.18.0-3-amd64: does not boot here [i915 gen4/gen5] Bug #914980 {Done: Salvatore Bonaccorso } [src:linux] linux-image-4.18.0-3-amd64: does not boot here [i915 gen4/gen5] Bug #915

Bug#916899: linux-image-4.18.0-0.bpo.3-amd64: NULL pointer dereference in i915

Control: forcemerge 914495 -1 This is fixed in Linux 4.19, currently available in unstable. 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#917234: [initramfs-tools] Unable to detect root device

Control: tag -1 moreinfo On Mon, 2018-12-24 at 15:05 +0100, Paul Menzel wrote: > Package: initramfs-tools > Version: 0.132 > Severity: normal > > Dear Debian folks, > > > Updating the Linux kernel package fails with the error below. [...] I think this is bug #917124. Try downgrading udev to v

Bug#917261: linux-image-4.19.0-1-amd64: /dev/mapper symlink for dm-crypt volume containing / not created on system startup

Control: reassign -1 udev 240-1 Control: forcemerge 917124 -1 This seems to be a bug in udev, not the kernel. You will only have noticed it once you rebooted for the kernel upgrade. Ben. -- Ben Hutchings It is impossible to make anything foolproof because fools are so ingenious. signature.a

Processed: Re: Bug#917261: linux-image-4.19.0-1-amd64: /dev/mapper symlink for dm-crypt volume containing / not created on system startup

Processing control commands: > reassign -1 udev 240-1 Bug #917261 [src:linux] linux-image-4.19.0-1-amd64: /dev/mapper symlink for dm-crypt volume containing / not created on system startup Bug reassigned from package 'src:linux' to 'udev'. No longer marked as found in versions linux/4.19.12-1. Ig

Processed: Re: Bug#917234: [initramfs-tools] Unable to detect root device

Processing control commands: > tag -1 moreinfo Bug #917234 [initramfs-tools] [initramfs-tools] Unable to detect root device Added tag(s) moreinfo. -- 917234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917234 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: forcibly merging 916816 917272

Processing commands for cont...@bugs.debian.org: > forcemerge 916816 917272 Bug #916816 [firmware-amd-graphics] firmware-amd-graphics: AMDGPU lacks recent firmwares fro 4.19 based kernel, not usable. Bug #917272 [firmware-amd-graphics] Kernel module failed to load on 4.19 kernel. Severity set to

Processed: reassign 917280 to src:linux, forcibly merging 914495 917280

Processing commands for cont...@bugs.debian.org: > reassign 917280 src:linux Bug #917280 [linux-image-amd64] Linux-4.18.20 fail to boot on old intel gfx card Bug reassigned from package 'linux-image-amd64' to 'src:linux'. No longer marked as found in versions linux-latest/100~bpo9+1. Ignoring requ

Processed (with 1 error): forcibly merging 914495 917280

Processing commands for cont...@bugs.debian.org: > forcemerge 914495 917280 Bug #914495 {Done: Salvatore Bonaccorso } [src:linux] linux-image-4.18.0-3-amd64: does not boot here [i915 gen4/gen5] Bug #914980 {Done: Salvatore Bonaccorso } [src:linux] linux-image-4.18.0-3-amd64: does not boot here [

Bug#917280: kernel panic on intel gen4 gfx card

On Tue, 2018-12-25 at 15:45 +, ? ? wrote: > Hi, Greg > > I found on Debian testing with kernel 4.18.20 fail boot, kernel panic > on i915. and reported it to Debian bug 917280 [0], with panic log[1]. > > after revert: > > commit 06e562e7f515292ea7721475950f23554214adde > Author: Chris Wilson

Bug#903778: marked as done (linux-image-amd64-signed-template: copyright file missing (policy 12.5))

Your message dated Tue, 25 Dec 2018 19:41:23 +0100 with message-id <20181225184120.dcwhpullnxoce...@debian.org> and subject line Re: linux-image-amd64-signed-template: copyright file missing (policy 12.5) has caused the Debian Bug report #903778, regarding linux-image-amd64-signed-template: copyri

linux-signed-i386_4.20+1~exp1_source.changes ACCEPTED into experimental, experimental

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Dec 2018 04:26:47 + Source: linux-signed-i386 Binary: kernel-image-4.20.0-trunk-686-di nic-modules-4.20.0-trunk-686-di nic-wireless-modules-4.20.0-trunk-686-di nic-shared-modules-4.20.0-trunk-686-di seria

linux-signed-amd64_4.20+1~exp1_source.changes ACCEPTED into experimental, experimental

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Dec 2018 04:26:47 + Source: linux-signed-amd64 Binary: kernel-image-4.20.0-trunk-amd64-di nic-modules-4.20.0-trunk-amd64-di nic-wireless-modules-4.20.0-trunk-amd64-di nic-shared-modules-4.20.0-trunk-amd64

linux-signed-arm64_4.20+1~exp1_source.changes ACCEPTED into experimental, experimental

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Dec 2018 04:26:47 + Source: linux-signed-arm64 Binary: kernel-image-4.20.0-trunk-arm64-di nic-modules-4.20.0-trunk-arm64-di nic-wireless-modules-4.20.0-trunk-arm64-di nic-shared-modules-4.20.0-trunk-arm64

linux-signed-i386_4.20+1~exp1_source.changes is NEW

binary:linux-image-4.20.0-trunk-686 is NEW. binary:linux-image-4.20.0-trunk-686-pae is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please

linux-signed-arm64_4.20+1~exp1_source.changes is NEW

binary:linux-image-4.20.0-trunk-arm64 is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed

Processing of linux-signed-i386_4.20+1~exp1_source.changes

linux-signed-i386_4.20+1~exp1_source.changes uploaded successfully to localhost along with the files: linux-signed-i386_4.20+1~exp1.dsc linux-signed-i386_4.20+1~exp1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

Processing of linux-signed-arm64_4.20+1~exp1_source.changes

linux-signed-arm64_4.20+1~exp1_source.changes uploaded successfully to localhost along with the files: linux-signed-arm64_4.20+1~exp1.dsc linux-signed-arm64_4.20+1~exp1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

Processing of linux-signed-amd64_4.20+1~exp1_source.changes

linux-signed-amd64_4.20+1~exp1_source.changes uploaded successfully to localhost along with the files: linux-signed-amd64_4.20+1~exp1.dsc linux-signed-amd64_4.20+1~exp1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

linux-signed-amd64_4.20+1~exp1_source.changes is NEW

binary:linux-image-4.20.0-trunk-amd64 is NEW. binary:linux-image-4.20.0-trunk-cloud-amd64 is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so p

Re: [Pkg-sysvinit-devel] Bug#780364: The problem disappeared, when I removed /etc/adjtime file and rebooted

[2018-12-24 03:51] Ben Hutchings > On Fri, 2018-12-21 at 18:54 +, Dmitry Bogatov wrote: > [...] > > * checking of /usr in `checkfs.sh' is performed by `fsck -A'. Any > >ideas, how should we tell it to skip /usr? > > We already do that since: > > commit 155bf5e08de00125ba2612834e747517

Bug#917272: Kernel module failed to load on 4.19 kernel.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Package: firmware-amd-graphics Version: 20180825+dfsg-1 For some reason, from 4.19.0 onward, the kernel refuses to load the AMD modules. The screen defaults to 80*25 text mode and "startx" does not work. Here is what I have tried: linux-image-4.19.

Bug#917261: linux-image-4.19.0-1-amd64: /dev/mapper symlink for dm-crypt volume containing / not created on system startup

Hi! I have the same issue. Not sure the problem is with the kernel package though, because even purging and/or reinstalling linux-image-4.18.0-3 fails (see below). Any suggestion which package may be responsible? The problem started after a dist-upgrade on Dec 24... Thanks! Tiziano # aptitud