Processed: found 624343 in linux-2.6/2.6.38-3

Processing commands for cont...@bugs.debian.org: > # try to fix the BTS graph information > found 624343 linux-2.6/2.6.38-3 Bug #624343 {Done: Salvatore Bonaccorso } [src:linux] linux-image-2.6.38-2-amd64: frequent message "bio too big device md0 (248 > 240)" in kern.log Marked as found in versi

Bug#808266: marked as done (linux-image-3.2.0-4-686-pae: i386 Wheezy JFS broken in 3.2.73-2+deb7u1 security update)

Your message dated Mon, 28 Dec 2015 08:46:23 +0100 with message-id <20151228074623.GA9531@eldamar.local> and subject line Re: Bug#808266: linux-image-3.2.0-4-686-pae: i386 Wheezy JFS broken in 3.2.73-2+deb7u1 security update has caused the Debian Bug report #808266, regarding linux-image-3.2.0-4-6

Processed: found 624343 in 2.6.38-3

Processing commands for cont...@bugs.debian.org: > found 624343 2.6.38-3 Bug #624343 [src:linux] linux-image-2.6.38-2-amd64: frequent message "bio too big device md0 (248 > 240)" in kern.log The source 'linux' and version '2.6.38-3' do not appear to match any binary packages Marked as found in v

Processed: closing 624343

Processing commands for cont...@bugs.debian.org: > close 624343 4.3-1~exp1 Bug #624343 [src:linux] linux-image-2.6.38-2-amd64: frequent message "bio too big device md0 (248 > 240)" in kern.log Ignoring request to alter fixed versions of bug #624343 to the same values previously set Bug #624343 [

Bug#783410: marked as done (Please add support for fsck.mode= parameters as known by systemd-fsck)

Your message dated Sun, 27 Dec 2015 23:00:15 + with message-id and subject line Bug#783410: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #783410, regarding Please add support for fsck.mode= parameters as known by systemd-fsck to be marked as done. This means that you cl

initramfs-tools_0.121~rc2_multi.changes ACCEPTED into experimental, experimental

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 22 Dec 2015 22:07:42 + Source: initramfs-tools Binary: initramfs-tools initramfs-tools-core Architecture: all source Version: 0.121~rc2 Distribution: experimental Urgency: medium Maintainer: Debian kernel team

Bug#807000: marked as done (initramfs-tools: module nvme not included in block modules on kernel > 4.2)

Your message dated Sun, 27 Dec 2015 23:00:16 + with message-id and subject line Bug#807000: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #807000, regarding initramfs-tools: module nvme not included in block modules on kernel > 4.2 to be marked as done. This means that

Bug#807004: marked as done (initramfs-tools: Breaks when installing kdump-tools with bcache rootfs)

Your message dated Sun, 27 Dec 2015 23:00:17 + with message-id and subject line Bug#807004: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #807004, regarding initramfs-tools: Breaks when installing kdump-tools with bcache rootfs to be marked as done. This means that you c

Bug#807256: marked as done (dep_add_modules_mount missing support for bcache)

Your message dated Sun, 27 Dec 2015 23:00:17 + with message-id and subject line Bug#807256: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #807256, regarding dep_add_modules_mount missing support for bcache to be marked as done. This means that you claim that the problem

Bug#797361: marked as done (initramfs-tools: hooks/fsck includes too many tools)

Your message dated Sun, 27 Dec 2015 23:00:16 + with message-id and subject line Bug#797361: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #797361, regarding initramfs-tools: hooks/fsck includes too many tools to be marked as done. This means that you claim that the probl

Bug#795837: marked as done (initramfs-tools: calls dpkg with obsolete relation operator '>')

Your message dated Sun, 27 Dec 2015 23:00:16 + with message-id and subject line Bug#795837: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #795837, regarding initramfs-tools: calls dpkg with obsolete relation operator '>' to be marked as done. This means that you claim th

Bug#795831: marked as done (initramfs-tools: ensure error output from switch_root/run-init are on the console)

Your message dated Sun, 27 Dec 2015 23:00:16 + with message-id and subject line Bug#795831: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #795831, regarding initramfs-tools: ensure error output from switch_root/run-init are on the console to be marked as done. This mean

Bug#792041: marked as done (initramfs-tools: Broken fixfsck boot flag?)

Your message dated Sun, 27 Dec 2015 23:00:16 + with message-id and subject line Bug#792557: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #792557, regarding initramfs-tools: Broken fixfsck boot flag? to be marked as done. This means that you claim that the problem has be

Bug#804446: marked as done (initramfs-tools: Do not include fsck tools for non-fscable filesystems)

Your message dated Sun, 27 Dec 2015 23:00:16 + with message-id and subject line Bug#797361: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #797361, regarding initramfs-tools: Do not include fsck tools for non-fscable filesystems to be marked as done. This means that you c

Bug#795839: marked as done (initramfs-tools: When adding i8042 also add psmouse as some keyboards are behind the mouse)

Your message dated Sun, 27 Dec 2015 23:00:16 + with message-id and subject line Bug#795839: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #795839, regarding initramfs-tools: When adding i8042 also add psmouse as some keyboards are behind the mouse to be marked as done.

Bug#585897: marked as done (initramfs-tools: allow multiple break points)

Your message dated Sun, 27 Dec 2015 23:00:16 + with message-id and subject line Bug#795832: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #795832, regarding initramfs-tools: allow multiple break points to be marked as done. This means that you claim that the problem has

Bug#799443: marked as done (initramfs-tools: avoid executing firmware and maintain symlinks)

Your message dated Sun, 27 Dec 2015 23:00:16 + with message-id and subject line Bug#799443: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #799443, regarding initramfs-tools: avoid executing firmware and maintain symlinks to be marked as done. This means that you claim th

Bug#793786: marked as done (initramfs-tools: fix the broken netconsole feature in initramfs-tools)

Your message dated Sun, 27 Dec 2015 23:00:16 + with message-id and subject line Bug#793786: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #793786, regarding initramfs-tools: fix the broken netconsole feature in initramfs-tools to be marked as done. This means that you cl

Bug#801154: marked as done ([debian] initramfs-tools: add PARTUUID to resolve_device)

Your message dated Sun, 27 Dec 2015 23:00:16 + with message-id and subject line Bug#801154: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #801154, regarding [debian] initramfs-tools: add PARTUUID to resolve_device to be marked as done. This means that you claim that the

Bug#795832: marked as done (initramfs-tools: allow the specificication of multiple break points using a comma delimiter)

Your message dated Sun, 27 Dec 2015 23:00:16 + with message-id and subject line Bug#795832: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #795832, regarding initramfs-tools: allow the specificication of multiple break points using a comma delimiter to be marked as done.

Bug#785564: marked as done (initramfs-tools: Boot fails do to missing switch_root)

Your message dated Sun, 27 Dec 2015 23:00:16 + with message-id and subject line Bug#785564: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #785564, regarding initramfs-tools: Boot fails do to missing switch_root to be marked as done. This means that you claim that the pro

Bug#790095: marked as done (lsinitramfs(8): multiple-segmented initramfs supported)

Your message dated Sun, 27 Dec 2015 23:00:16 + with message-id and subject line Bug#790095: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #790095, regarding lsinitramfs(8): multiple-segmented initramfs supported to be marked as done. This means that you claim that the pr

Bug#803322: marked as done (initramfs-tools: gives wrong warnings about fsck.btrfs)

Your message dated Sun, 27 Dec 2015 23:00:16 + with message-id and subject line Bug#784234: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #784234, regarding initramfs-tools: gives wrong warnings about fsck.btrfs to be marked as done. This means that you claim that the pr

Bug#792557: marked as done (initramfs-tools functions doesn't honour "fsckfix" kernel command line option)

Your message dated Sun, 27 Dec 2015 23:00:16 + with message-id and subject line Bug#792557: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #792557, regarding initramfs-tools functions doesn't honour "fsckfix" kernel command line option to be marked as done. This means th

Bug#784368: marked as done (initramfs-tools: update-initramfs tries to use /sbin/fsck.btrfs instead of /bin/fsck.btrfs)

Your message dated Sun, 27 Dec 2015 23:00:16 + with message-id and subject line Bug#784234: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #784234, regarding initramfs-tools: update-initramfs tries to use /sbin/fsck.btrfs instead of /bin/fsck.btrfs to be marked as done.

Bug#784234: marked as done (initramfs-tools: searches for fsck.btrfs in the wrong directory)

Your message dated Sun, 27 Dec 2015 23:00:16 + with message-id and subject line Bug#784234: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #784234, regarding initramfs-tools: searches for fsck.btrfs in the wrong directory to be marked as done. This means that you claim th

Bug#785147: marked as done (initramfs-tools: NVMe boot drives not supported)

Your message dated Sun, 27 Dec 2015 23:00:16 + with message-id and subject line Bug#785147: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #785147, regarding initramfs-tools: NVMe boot drives not supported to be marked as done. This means that you claim that the problem h

Bug#783620: marked as done (initramfs-tools: initramfs broken on first boot into Jessie, "Unable to mount root fs on unknown-block(0, 0)")

Your message dated Sun, 27 Dec 2015 23:00:15 + with message-id and subject line Bug#783620: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #783620, regarding initramfs-tools: initramfs broken on first boot into Jessie, "Unable to mount root fs on unknown-block(0, 0)" to b

Bug#783291: marked as done (/bin/touch is missing if built with BUSYBOX=n or busybox package not installed)

Your message dated Sun, 27 Dec 2015 23:00:15 + with message-id and subject line Bug#783291: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #783291, regarding /bin/touch is missing if built with BUSYBOX=n or busybox package not installed to be marked as done. This means t

Bug#785435: marked as done (init: touch not found)

Your message dated Sun, 27 Dec 2015 23:00:15 + with message-id and subject line Bug#783291: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #783291, regarding init: touch not found to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#766920: marked as done (produces unbootable initramfs with lilo hexadecimal syntax (root=803))

Your message dated Sun, 27 Dec 2015 23:00:15 + with message-id and subject line Bug#766920: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #766920, regarding produces unbootable initramfs with lilo hexadecimal syntax (root=803) to be marked as done. This means that you cl

Bug#786385: marked as done (/init: touch not found)

Your message dated Sun, 27 Dec 2015 23:00:15 + with message-id and subject line Bug#783291: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #783291, regarding /init: touch not found to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#782641: marked as done (initramfs-tools: nfs booting requires /usr to be present on the nfs root filesystem)

Your message dated Sun, 27 Dec 2015 23:00:15 + with message-id and subject line Bug#782641: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #782641, regarding initramfs-tools: nfs booting requires /usr to be present on the nfs root filesystem to be marked as done. This me

Bug#770394: marked as done (initramfs-tools: Sorting rc versions)

Your message dated Sun, 27 Dec 2015 23:00:15 + with message-id and subject line Bug#770394: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #770394, regarding initramfs-tools: Sorting rc versions to be marked as done. This means that you claim that the problem has been dea

Bug#747871: marked as done (mkinitramfs: breaks with LUKS root on MMC ("mkinitramfs: for root /dev/dm-0 missing mmcblk /sys/block/ entry") and MODULES=dep)

Your message dated Sun, 27 Dec 2015 23:00:15 + with message-id and subject line Bug#747871: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #747871, regarding mkinitramfs: breaks with LUKS root on MMC ("mkinitramfs: for root /dev/dm-0 missing mmcblk /sys/block/ entry") and

Bug#782785: marked as done (initramfs-tools: allow URI/server:/path root= arguments)

Your message dated Sun, 27 Dec 2015 23:00:15 + with message-id and subject line Bug#697017: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #697017, regarding initramfs-tools: allow URI/server:/path root= arguments to be marked as done. This means that you claim that the p

Bug#697017: marked as done (root=compute fails at parse_numeric() for lilo compatibility)

Your message dated Sun, 27 Dec 2015 23:00:15 + with message-id and subject line Bug#697017: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #697017, regarding root=compute fails at parse_numeric() for lilo compatibility to be marked as done. This means that you claim that

Bug#633582: marked as done (initramfs-tools: All files in initrd owned by root)

Your message dated Sun, 27 Dec 2015 23:00:15 + with message-id and subject line Bug#633582: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #633582, regarding initramfs-tools: All files in initrd owned by root to be marked as done. This means that you claim that the proble

Bug#620814: marked as done (initramfs-tools: fails to include essential module for other leg of md0)

Your message dated Sun, 27 Dec 2015 23:00:15 + with message-id and subject line Bug#620814: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #620814, regarding initramfs-tools: fails to include essential module for other leg of md0 to be marked as done. This means that you

Bug#696632: marked as done (initramfs-tools: Patches to clean up /run handling for jessie)

Your message dated Sun, 27 Dec 2015 23:00:15 + with message-id and subject line Bug#696632: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #696632, regarding initramfs-tools: Patches to clean up /run handling for jessie to be marked as done. This means that you claim that

Bug#588452: marked as done ("softdep" modules not included in initramfs when MODULES=dep is specified)

Your message dated Sun, 27 Dec 2015 23:00:15 + with message-id and subject line Bug#588452: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #588452, regarding "softdep" modules not included in initramfs when MODULES=dep is specified to be marked as done. This means that y

Bug#602331: marked as done (plymouth does not allow to enter maintenance shell)

Your message dated Sun, 27 Dec 2015 23:00:15 + with message-id and subject line Bug#602331: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #602331, regarding plymouth does not allow to enter maintenance shell to be marked as done. This means that you claim that the proble

Bug#772335: marked as done (initramfs-tools: bashism in /bin/sh script)

Your message dated Sun, 27 Dec 2015 23:00:15 + with message-id and subject line Bug#633582: fixed in initramfs-tools 0.121~rc2 has caused the Debian Bug report #633582, regarding initramfs-tools: bashism in /bin/sh script to be marked as done. This means that you claim that the problem has be

Broadcom Corporation Device 43a3 kernel 4.4 debian jessie

Hello list, i have buyed a dell xps 13 laptop, and i find that i can't configure my wifi Now i'm using debian jessie, with kernel 4.2l The output of uname -a gives it : Linux XPS13 4.2.0-0.bpo.1-amd64 #1 SMP Debian 4.2.6-3~bpo8+2 (2015-12-14) x86_64 GNU/Linux lspci output is it : root@XPS13

Bug#808916: linux-image-4.3.0-1-amd64: non-blocking stack trace crash during startup (drm/i915) in drm_atomic_check_only+0x46f/0x540

On 2015-12-24 12:48 +0100, Christophe wrote: > Package: src:linux > Version: 4.3.3-2 > Severity: normal > Tags: upstream > > Dear Maintainer, > > Having just updated my Debian Testing to the 4.3 kernel from 3.16, I > have noticed the stack trace below during boot, which does not seem to > disturb

Bug#808563: really should be serious bug: data loss

Will try Wednesday. Actually better to have the raid people test. I only have one disk... too risky.

Processed: Re: linux-image-4.3.0-1-amd64: Microcode SW error detected / Hardware became unavailable during restart

Processing commands for cont...@bugs.debian.org: > retitle 809149 linux-image-4.3.0-1-amd64: iwlwifi: Microcode SW error > detected / Hardware became unavailable during restart Bug #809149 [src:linux] linux-image-4.3.0-1-amd64: Microcode SW error detected / Hardware became unavailable during res

Bug#809149: linux-image-4.3.0-1-amd64: Microcode SW error detected / Hardware became unavailable during restart

Package: src:linux Version: 4.3.3-2 Severity: normal I sometimes have wifi disconnections, and automatic reconnections, but this time, wicd constantly said "No wireless networks found.". Restarting the wicd daemon and the GUI did not solve this problem. There are 8 visible wifi access points, so t

Bug#808973: radeon crash after security upgrade on wheezy

On Sun, 2015-12-27 at 13:46 +, dili...@lineone.net wrote: > I also have the same problem. I am only able to boot the system with > rescue CD. > > Is there any way to roll back the security upgrade? 1. Boot with 'nomodeset' kernel parameter added. 2. Install the previous package from /var/cac

Bug#808973: radeon crash after security upgrade on wheezy

I also have the same problem. I am only able to boot the system with rescue CD. Is there any way to roll back the security upgrade?

Re: [pkg-cryptsetup-devel] Bug#783297: breaks initramfs if BUSYBOX=n

Am 25.12.2015 um 14:46 schrieb Jonas Meurer: > Am 26.04.2015 um 01:35 schrieb Michael Biebl: >> On Sat, 25 Apr 2015 16:22:13 +0200 Michael Biebl wrote: >>> if the cryptsetup package is installed, it also installed a >>> initramfs-tools hook. >>> >>> I use BUSYBOX=no in initramfs.conf, but the cry