linux-latest_79_multi.changes is NEW

binary:linux-image-4kc-malta-dbgsym is NEW. binary:linux-image-5kc-malta-dbgsym is NEW. binary:linux-image-686-dbgsym is NEW. binary:linux-image-686-pae-dbgsym is NEW. binary:linux-image-amd64-dbgsym is NEW. binary:linux-image-arm64-dbgsym is NEW. binary:linux-image-armmp-dbgsym is NEW. binary:linu

Processing of linux-latest_79_multi.changes

linux-latest_79_multi.changes uploaded successfully to localhost along with the files: linux-latest_79.dsc linux-latest_79.tar.xz linux-latest_79_source.buildinfo linux-doc_4.9+79_all.deb linux-perf_4.9+79_all.deb linux-source_4.9+79_all.deb linux-tools_4.9+79_all.deb Greetings,

[PATCH initramfs-tools 5/5] scripts/local-premount/resume: Use local_device_setup for resume device

Currently we don't wait for the resume device to appear, and will boot without resuming if it is too slow to appear (e.g. USB storage or, in the reported case, an NVMe device!). Use local_device_setup to wait for the device, the same as we do for the root and /usr devices. This also takes care of

[PATCH initramfs-tools 3/5] scripts/local: Add option for local_device_setup to return failure

If the root or /usr filesystem is missing, we cannot continue booting and must panic. This is not true for the resume device, and a missing resume device has not been a fatal error up until now. Signed-off-by: Ben Hutchings --- scripts/local | 6 ++ 1 file changed, 6 insertions(+) diff --g

[PATCH initramfs-tools 4/5] scripts/local-premount/resume: Check for kernel resume interface earlier

There is no point in looking for the resume device if the kernel doesn't support resuming from disk. Signed-off-by: Ben Hutchings --- scripts/local-premount/resume | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/scripts/local-premount/resume b/scripts/local-premount/resume

[PATCH initramfs-tools 2/5] scripts/local: Apply a single time limit to all device discovery

Instead of counting how many times we wait and poll for each critical device (root or /usr) to appear, use /proc/uptime to tell how long we have waited in total. Signed-off-by: Ben Hutchings --- scripts/local | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/scripts/local

[PATCH initramfs-tools 1/5] scripts/local: local_device_setup should not assume devices hold file systems

Move the 'file system' name suffix into the callers. Signed-off-by: Ben Hutchings --- scripts/local | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/scripts/local b/scripts/local index 3558f7a04b1f..a4ddcea73a38 100644 --- a/scripts/local +++ b/scripts/local @@ -71,7 +71

[PATCH initramfs-tools 0/5] Wait for resume devices

This series changes the local_device_setup function and the resume script so that we wait for a resume device to appear, same as for the root and /usr devices. However, it is not a fatal error if the resume device doesn't appear (which would be a regression). Also, it makes the time limit global

linux-latest_79_source.changes REJECTED

Source-only uploads to NEW are not allowed. binary:linux-image-4kc-malta-dbgsym is NEW. binary:linux-image-5kc-malta-dbgsym is NEW. binary:linux-image-686-dbgsym is NEW. binary:linux-image-686-pae-dbgsym is NEW. binary:linux-image-amd64-dbgsym is NEW. binary:linux-image-arm64-dbgsym is NEW. bina

Processing of linux-latest_79_source.changes

linux-latest_79_source.changes uploaded successfully to localhost along with the files: linux-latest_79.dsc linux-latest_79.tar.xz linux-latest_79_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Processed: severity of 854791 is important

Processing commands for cont...@bugs.debian.org: > severity 854791 important Bug #854791 [initramfs-tools] initramfs-tools: does not wait for "resume" device to come up Severity set to 'important' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 8547

initramfs-tools_0.120+deb8u3_multi.changes ACCEPTED into proposed-updates->stable-new, proposed-updates

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 18 Feb 2017 20:43:30 + Source: initramfs-tools Binary: initramfs-tools Architecture: all source Version: 0.120+deb8u3 Distribution: jessie Urgency: medium Maintainer: Debian kernel team Changed-By: Ben Hutchin

Bug#845581: marked as done (initramfs built in a chroot may lack /etc/mtab)

Your message dated Sat, 18 Feb 2017 23:32:08 + with message-id and subject line Bug#845581: fixed in initramfs-tools 0.120+deb8u3 has caused the Debian Bug report #845581, regarding initramfs built in a chroot may lack /etc/mtab to be marked as done. This means that you claim that the problem

Bug#825687: marked as done (initramfs-tools: Must include I2C drivers when MODULES=most)

Your message dated Sat, 18 Feb 2017 23:32:08 + with message-id and subject line Bug#825687: fixed in initramfs-tools 0.120+deb8u3 has caused the Debian Bug report #825687, regarding initramfs-tools: Must include I2C drivers when MODULES=most to be marked as done. This means that you claim tha

Bug#762634: marked as done ([armhf] mounting rootfs on USB disk fails / some USB host controller drivers missing in initramfs)

Your message dated Sat, 18 Feb 2017 23:32:08 + with message-id and subject line Bug#762634: fixed in initramfs-tools 0.120+deb8u3 has caused the Debian Bug report #762634, regarding [armhf] mounting rootfs on USB disk fails / some USB host controller drivers missing in initramfs to be marked

Bug#772578: marked as done ([initramfs-tools] Missing keyboard modules i2c_designware_* in initramfs)

Your message dated Sat, 18 Feb 2017 23:32:08 + with message-id and subject line Bug#639876: fixed in initramfs-tools 0.120+deb8u3 has caused the Debian Bug report #639876, regarding [initramfs-tools] Missing keyboard modules i2c_designware_* in initramfs to be marked as done. This means that

Bug#639876: marked as done (MODULES=dep does not include input drivers)

Your message dated Sat, 18 Feb 2017 23:32:08 + with message-id and subject line Bug#639876: fixed in initramfs-tools 0.120+deb8u3 has caused the Debian Bug report #639876, regarding MODULES=dep does not include input drivers to be marked as done. This means that you claim that the problem has

Bug#701656: marked as done (Include current input drivers when MODULES=dep, to support rescue shell)

Your message dated Sat, 18 Feb 2017 23:32:08 + with message-id and subject line Bug#639876: fixed in initramfs-tools 0.120+deb8u3 has caused the Debian Bug report #639876, regarding Include current input drivers when MODULES=dep, to support rescue shell to be marked as done. This means that

linux-signed_4.2_multi.changes ACCEPTED into unstable, unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 18 Feb 2017 15:45:19 + Source: linux-signed Binary: kernel-image-4.9.0-2-amd64-di nic-modules-4.9.0-2-amd64-di nic-wireless-modules-4.9.0-2-amd64-di nic-shared-modules-4.9.0-2-amd64-di serial-modules-4.9.0-2-

initramfs-tools_0.120+deb8u3_multi.changes ACCEPTED into proposed-updates->stable-new

Mapping jessie to stable. Mapping stable to proposed-updates. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 18 Feb 2017 20:43:30 + Source: initramfs-tools Binary: initramfs-tools Architecture: all source Version: 0.120+deb8u3 Distribution: jessie Urgency: m

Processing of initramfs-tools_0.120+deb8u3_multi.changes

initramfs-tools_0.120+deb8u3_multi.changes uploaded successfully to localhost along with the files: initramfs-tools_0.120+deb8u3.dsc initramfs-tools_0.120+deb8u3.tar.xz initramfs-tools_0.120+deb8u3_source.buildinfo initramfs-tools_0.120+deb8u3_all.deb Greetings, Your Debian queue

Bug#853100: linux-image-4.9.0-1-amd64: Blocked tasks and no X on Latitude E6530

On Thu, 2017-02-16 at 20:17 -0700, Thomas Vaughan wrote: > I have attached the output both for linux-3.16 (which seems to have no > problem) and for linux-4.9. OK, so you have the VirtalBox and Broadcom wl modules loaded.  I doubt that they are involved in this bug. Can you look through /var/log/

Bug#854677: linux-image-amd64 - patches from kernel source required

On Fri, 2017-02-17 at 09:03 +0530, Narayanan R S wrote: > Hi Ben, > > I can try (re)running the 4.9 backport and see if the issue resurfaces. > > What is the correlation between the debian kernel (backported) and the > mainline one (it says version 4.9.2-2~bpo8+1 - so is it essentially > _EXACTLY

Processed: tagging 855472, severity of 855472 is important

Processing commands for cont...@bugs.debian.org: > tags 855472 - upstream Bug #855472 [src:linux] display drivers missing for gta04 board Removed tag(s) upstream. > severity 855472 important Bug #855472 [src:linux] display drivers missing for gta04 board Severity set to 'important' from 'normal' >

Bug#855472: (no subject)

This is about linux-image-4.9.0-1-armmp in stretch, armhf.

Bug#855472: display drivers missing for gta04 board

Package: src:linux Version: 4.9.6-3 Severity: normal Tags: upstream Dear Maintainers, Please enable following set of configs to support the display on GTA04 phone: CONFIG_DRM_OMAP_PANEL_TPO_TD028TTEC1=m CONFIG_PWM_OMAP_DMTIMER=m This enables the driver for the connected display, and the pwm driv

linux-signed_4.2_multi.changes is NEW

binary:acpi-modules-4.9.0-2-686-di is NEW. binary:acpi-modules-4.9.0-2-686-pae-di is NEW. binary:acpi-modules-4.9.0-2-amd64-di is NEW. binary:affs-modules-4.9.0-2-powerpc-di is NEW. binary:affs-modules-4.9.0-2-powerpc64-di is NEW. binary:ata-modules-4.9.0-2-686-di is NEW. binary:ata-modules-4.9.0-2

Processing of linux-signed_4.2_multi.changes

linux-signed_4.2_multi.changes uploaded successfully to localhost along with the files: linux-signed_4.2.dsc linux-signed_4.2.tar.xz linux-signed_4.2_source.buildinfo acpi-modules-4.9.0-2-686-di_4.9.10-1_i386.udeb acpi-modules-4.9.0-2-686-pae-di_4.9.10-1_i386.udeb ata-modules-4.9.0-2-68

Re: Give back linux (4.9.10-1) on i386

On 18/02/17 04:56, Ben Hutchings wrote: > linux 4.9.10-1 failed to build on x86-csail-01 due to a full disk. > Please give it back to another buildd or free up more disk space there. Space has been freed on that buildd, and the package has been given back. Cheers, Emilio

Bug#854231: Fwd: Re: Fwd: Kernel 4.9 traces

Additional information: Just checked this: setserial -g /dev/ttyS* /dev/ttyS0, UART: unknown, Port: 0x03f8, IRQ: 4 /dev/ttyS1, UART: 16550A, Port: 0xcc00, IRQ: 17 /dev/ttyS2, UART: 16550A, Port: 0xc880, IRQ: 17 /dev/ttyS3, UART: 16550A, Port: 0x02e8, IRQ: 3 Are we opening a non exsisting port?