Processed: severity of 750360 is critical

Processing commands for cont...@bugs.debian.org: severity 750360 critical Bug #750360 [initramfs-tools] initramfs-tools: nfs mount script check for /sbin/init incomplete Severity set to 'critical' from 'important' thanks Stopping processing here. Please contact me if you need assistance. --

Bug#748615: linux-image-3.14-0.bpo.1-amd64: the system reboot after mounting the partitions

This bug is fixed in kernel 3.16.1 from upstream. -- Alain Rpnpif -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140814171250.d55cb5a2...@chro.home

Bug#758158: Alx AR8161 - ifdown eth - hard crash

Package: linux-image-3.2.0-4-amd64 Version: 3.2.57-3+deb7u2 Mainboard: Gigabyte Z77X-D3H 07:00.0 Ethernet controller: Atheros Communications Inc. AR8161 Gigabit Ethernet (rev 10) The interface stopped working(frequent disconnects, and finally no dhcp to my laptop) Command: ifdown eth1 crashed

Re: Plan of action for Secure Boot support

Hi Ben, Ben Hutchings b...@decadent.org.uk (2013-08-13): Colin Watson and Stefano Rivera talked about how Ubuntu had implemented Secure Boot and what they believed were the requirements. Apparently, the Secure Boot spec requires each stage of the boot code to validate signatures only until

unble to re-enable wifi/bt after hardware or software disable

tags 756947 - moreinfo reassign 756947 firmware-ipw2x00 found 756947 0.36+wheezy.1 thanks Hey, A quick summary of the problem: Alan is using '02:04.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)' with ipw2200 driver and correctly loaded

Processed: unble to re-enable wifi/bt after hardware or software disable

Processing commands for cont...@bugs.debian.org: tags 756947 - moreinfo Bug #756947 [general] general: unble to re-enable wifi/bt after hardware or software disable Removed tag(s) moreinfo. reassign 756947 firmware-ipw2x00 Bug #756947 [general] general: unble to re-enable wifi/bt after

Processed: System Power Management: System re-enters Suspend-to-RAM after waking up

Processing commands for cont...@bugs.debian.org: tags 755881 + wontfix Bug #755881 [src:linux] base: System Power Management: System re-enters Suspend-to-RAM after waking up Added tag(s) wontfix. thanks Stopping processing here. Please contact me if you need assistance. -- 755881:

Bug#755881: marked as done (base: System Power Management: System re-enters Suspend-to-RAM after waking up)

Your message dated Fri, 15 Aug 2014 02:00:55 +0200 with message-id 53ed4db7.8060...@tnnn.pl and subject line System Power Management: System re-enters Suspend-to-RAM after waking up has caused the Debian Bug report #755881, regarding base: System Power Management: System re-enters Suspend-to-RAM

Bug#758170: linux-image-3.14-1-amd64: read() cannot return more than 0x7ffff000, even on a regular file, breaking POSIX compliance

Package: src:linux Version: 3.14.12-1 Severity: normal Consider the following program: #include stdio.h #include stdlib.h #include limits.h #include unistd.h #include sys/types.h #include sys/stat.h #include fcntl.h int main (void) {

Bug#725714:

Any updates on this bug?