Bug#779515: Should enable the qxl kernel driver when installed

On Sat, 2015-11-07 at 00:24 +0100, Laurent Bigonville wrote: > reassign 779515 linux-image-4.2.0-1-amd64 > severity 779515 important > thanks > > On Sun, 01 Mar 2015 18:47:54 + Ben Hutchings > wrote: > >  > I've enabled the kernel's qxl driver, but disabled by default

Processed: Re: Should enable the qxl kernel driver when installed

Processing commands for cont...@bugs.debian.org: > reassign 779515 linux-image-4.2.0-1-amd64 Bug #779515 [src:xserver-xorg-video-qxl] Should enable the qxl kernel driver when installed Bug reassigned from package 'src:xserver-xorg-video-qxl' to 'linux-image-4.2.0-1-amd64'. No longer marked as

Bug#804295: initramfs-tools: doesn't warn/fail when dpkg triggers for update-initramfs don't actually update

Package: initramfs-tools Version: 0.120 Severity: normal Hi. I've just noted the following: Processing triggers for initramfs-tools (0.120) ... update-initramfs: /boot/initrd.img-4.2.0-1-amd64 has been altered. update-initramfs: Cannot update. Override with -t option. Not sure what caused it

Bug#803159: linux: Enable DT support for armel/orion5x arch

Patch appended, to avoid any misunderstanding. - 0001 is both OK for sid and jessie - 0002 is only necessary for sid, or other 4.x kernel series (e.g. jessie-backport) Thank you! Cheers, Roger From ecc1733be537bf5c2583b50a0664b583cf294b37 Mon Sep 17 00:00:00 2001 From: Roger Shimizu

Processed: affects 779515

Processing commands for cont...@bugs.debian.org: > affects 779515 xserver-xorg-video-qxl Bug #779515 [linux-image-4.2.0-1-amd64] Should enable the qxl kernel driver when installed Added indication that 779515 affects xserver-xorg-video-qxl > thanks Stopping processing here. Please contact me if

Bug#802432: fixed, can be closed.

Dear Maintainer, Issue fixed in version linux-image-4.3.0-trunk-amd64 (4.3-1~exp1). Bug #802432 can be closed. -- System Information: Debian Release: sid + experimental Architecture: amd64 (x86_64) Kernel: linux-image-4.3.0-trunk-amd64 Systemd: 227-2 Kind regards, Jos v.Wolput

Processed: Re: [Pkg-xen-devel] Bug#799122: xen-hypervisor-4.4-amd64: Networking of domUs stops working after a few minutes

Processing control commands: > reassign -1 src:linux 3.16.7-ckt11-1+deb8u5 Bug #799122 [xen-hypervisor-4.4-amd64] xen-hypervisor-4.4-amd64: Networking of domUs stops working after a few minutes Bug reassigned from package 'xen-hypervisor-4.4-amd64' to 'src:linux'. No longer marked as found in

Bug#803899: marked as done (linux-image-4.2.0-1-amd64: Intel NUC built-in SD card reader requires PINCTRL module support)

Your message dated Fri, 06 Nov 2015 11:00:40 + with message-id and subject line Bug#797949: fixed in linux 4.3-1~exp1 has caused the Debian Bug report #797949, regarding linux-image-4.2.0-1-amd64: Intel NUC built-in SD card reader requires PINCTRL module

Bug#803370: marked as done (linux: missing netfilter modules)

Your message dated Fri, 06 Nov 2015 11:00:40 + with message-id and subject line Bug#803370: fixed in linux 4.3-1~exp1 has caused the Debian Bug report #803370, regarding linux: missing netfilter modules to be marked as done. This means that you claim that

Bug#803323: marked as done (linux: postinst: typo "dangling linkto")

Your message dated Fri, 06 Nov 2015 11:00:40 + with message-id and subject line Bug#803323: fixed in linux 4.3-1~exp1 has caused the Debian Bug report #803323, regarding linux: postinst: typo "dangling linkto" to be marked as done. This means that you

Bug#797949: marked as done (linux: CONFIG_PINCTRL_BAYTRAIL=y needed for microSD slot to function on Intel Compute Stick)

Your message dated Fri, 06 Nov 2015 11:00:40 + with message-id and subject line Bug#797949: fixed in linux 4.3-1~exp1 has caused the Debian Bug report #797949, regarding linux: CONFIG_PINCTRL_BAYTRAIL=y needed for microSD slot to function on Intel Compute

Bug#804079: linux-image-3.16.0-4-amd64: Kernel panic on Xen virtualisation in Debian

Control: found -1 3.16.7-ckt11-1+deb8u5 Control: notfound -1 3.16.7-ckt11-1 Thanks for your report. On Wed, 2015-11-04 at 18:53 +0100, Jan Prunk wrote: > Package: src:linux > Version: 3.16.7-ckt11-1 >From your text and the screenshot I think this should really be +deb8u5. I've updated the bug

Processed: Re: Bug#804079: linux-image-3.16.0-4-amd64: Kernel panic on Xen virtualisation in Debian

Processing control commands: > found -1 3.16.7-ckt11-1+deb8u5 Bug #804079 [src:linux] linux-image-3.16.0-4-amd64: Kernel panic on Xen virtualisation in Debian The source 'linux' and version '3.16.7-ckt11-1+deb8u5' do not appear to match any binary packages Marked as found in versions

Bug#803159: linux: Enable DT support for armel/orion5x arch

I have good news. > If you can figure out why the LS-WTGL doesn't work and that can be > fixed (i.e. it turns out to be something other than the size) then I > see no problem with adding support for the LS-WTGL platform. I finished "git bisect" and good commit is 1553282b11e and bad one is

Bug#803159: linux: Enable DT support for armel/orion5x arch

On Fri, 2015-11-06 at 23:53 +0900, Roger Shimizu wrote: > So I think it's now safe to turn on DEBUG_LL_UART_8250 and merge my > patch. Great, thanks for tracking that down.  It's a bit odd that DEBUG_LL_UART_NONE fails (after all it should be doing nothing) but given that this flavour supports a

Bug#803159: linux: Enable DT support for armel/orion5x arch

Thanks for the feedback! > It's a bit odd that DEBUG_LL_UART_NONE fails (after all it should be > doing nothing) but given that this flavour supports a single SOC which > all have the same UART (AFAICT, it's on in upstream orion5x defconfig > at least) I think there's no reason not to do this.

Bug#797779:

You can get the .txt file from this EFI variable: /sys/firmware/efi/efivars/nvram-74b00bd9-805a-4d61-b51f-43268123d113 as explained in the kernel documentation: https://wireless.wiki.kernel.org/en/users/Drivers/brcm80211#firmware_installation1 Problem is brcmfmac does not do that automatically

Bug#802598: marked as done (linux-image-4.2.0-1-powerpc64le: Please include MLX5 again)

Your message dated Fri, 06 Nov 2015 17:08:59 + with message-id <1446829739.6006.3.ca...@decadent.org.uk> and subject line Re: Bug#802598: Acknowledgement (linux-image-4.2.0-1-powerpc64le: Please include MLX5 again) has caused the Debian Bug report #802598, regarding

linux_4.3-1~exp1_multi.changes ACCEPTED into experimental, experimental

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 04 Nov 2015 07:45:13 + Source: linux Binary: linux-source-4.3 linux-doc-4.3 linux-manual-4.3 linux-support-4.3.0-trunk linux-libc-dev linux-headers-4.3.0-trunk-all linux-headers-4.3.0-trunk-all-alpha

Bug#804260: linux-image-4.2.0-1-amd64 fails to boot with IOMMU enabled in BIOS

Package: src:linux Version: 4.2.5-1 Severity: normal Dear Maintainer, after upgrading to linux-image-4.2.0-1-amd64 from linux-image-4.1.0-2-amd64 system could not boot with new kernel during boot these messages are displayed: Loading, please wait... [1.417184] AMD-Vi: Event logged

Bug#799122: [Pkg-xen-devel] Bug#799122: xen-hypervisor-4.4-amd64: Networking of domUs stops working after a few minutes

On Thu, 2015-11-05 at 19:16 +0100, Arne Klein wrote: > Thank you. The tested versions on dom0 and domU in which the problem > occurs are: > 4.1.3-1~bpo8+1 > 3.16.7-ckt11-1+deb8u5 I've asked around upstream and it was suggested that "xen-netback: require fewer guest Rx slots when not using GSO"

Bug#799122: [Pkg-xen-devel] Bug#799122: xen-hypervisor-4.4-amd64: Networking of domUs stops working after a few minutes

On Fri, 2015-11-06 at 11:23 +, Ian Campbell wrote: > Please could you try 4.3~rc7-1~exp1 from experimental in dom0 and see > if that helps? 4.3-1~exp1 was just uploaded, so you may as well try that instead. Thanks, Ian.

Bug#782641: initramfs-tools: nfs booting requires /usr to be present on the nfs root filesystem

Hi, On Wed, Apr 15, 2015 at 03:01:44PM +0100, fc3452-00 wrote: > Package: initramfs-tools > Version: 0.120 > Severity: normal > > Dear Maintainer, > > Problem occurs when attempting to do an nfs network boot with no /usr > directory > present on the nfs root partition. > > At