Bug#766448: 0.116 to 0.118 makes systems unbootable with 5 second message
Package: initramfs-tools Version: 0.118 Severity: grave On all my systems, 0.116 works fine, 0.118 just gives some message about rebooting in 5 seconds that is not enough time to read. I.e., the system becomes unbootable. 1. Please tell me what steps you would like me to take. Thanks. -- 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/87d29jkzt6@jidanni.org
Bug#766447: add parameter to override the seconds of 'Will restart in 5 seconds.'
Package: src:linux Version: 3.16.5-1 Severity: wishlist Regarding 'Attempt to start maintenance shell failed. Will restart in 5 seconds.' 5 seconds is not long enough to read all but a few of the words on the screen. Please add a boot parameter to control this. Also document it in Documentation/kernel-parameters.txt.gz and perhaps say adjust with xyz= right there in the message. One would think that panic= is the parameter that is used, but it is not. -- 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/87h9yvl040@jidanni.org
Bug#766446: mention what disk when saying Warning: couldn't identify filesystem type
Package: initramfs-tools Version: 0.118 Severity: wishlist Please mention what disk you are talking about in messages like Warning: couldn't identify filesystem type for fsck hook, ignoring. else the user will get very worried that one of his disks are bad and need to test them all. Thanks. Preparing to unpack .../initramfs-tools_0.118_all.deb ... Unpacking initramfs-tools (0.118) over (0.116) ... Processing triggers for man-db (2.7.0.2-2) ... Processing triggers for doc-base (0.10.6) ... Processing 1 changed doc-base file... Registering documents with scrollkeeper... Setting up initramfs-tools (0.118) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.118) ... update-initramfs: Generating /boot/initrd.img-3.16-3-686-pae Warning: couldn't identify filesystem type for fsck hook, ignoring. -- 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/87vbnbb6zn@jidanni.org
Bug#766195: [PATCH] ipv6: reuse ip6_frag_id from ip6_ufo_append_data
Hi, On Wed Oct 22, 2014 at 01:02:07 +0100, Ben Hutchings wrote: I think this is the upstream change which would fix this. Please test this on top of the previous one, in case there are any more cases where ipv6_select_ident() may be called with a rt == NULL. However, it seems that with this change, when a VM offloads UDP/IPv6 fragmentation to us, we will always set the fragmentation ID to 0. I'm not sure whether that's a regression from 3.2.62, but I think it is. We should not be choosing fragment IDs for VMs, but currently they aren't telling us what to use! I've queried this upstream. i have build a new kernel with the above mentioned patches applied. This package is now available on https://people.debian.org/~zobel/linux-image-3.2.0-4-amd64_3.2.63-2a~test_amd64.deb Both machines that i installed the kernel on run for quite some time without any issue now. Before those patches they stayed up only for a few minutes. Cheers, Martin -- Martin Zobel-Helas zo...@debian.orgDebian System Administrator Debian GNU/Linux Developer Debian Listmaster http://about.me/zobel Debian Webmaster GPG Fingerprint: 6B18 5642 8E41 EC89 3D5D BDBB 53B1 AC6D B11B 627B -- 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/20141023141618.ga31...@ftbfs.de
Bug#765685: Acknowledgement (linux-image-3.16-2-amd64: Kernel lockups with r8723au)
I've tested this with v3.17 from experimental and the driver seems vastly more stable with that kernel version so this probably only applies to v3.16, Ben did point out to me that there had been a lot of work on the driver between the two versions. signature.asc Description: Digital signature
Processed: Fix accepted upstream
Processing commands for cont...@bugs.debian.org: fixed 726655 linux/3.13~rc6-1~exp1 Bug #726655 [linux-doc-3.10] linux-doc-3.10: blockdev/floppy.txt.gz incorrectly documents module option syntax Marked as fixed in versions linux/3.13~rc6-1~exp1. -- Stopping processing here. Please contact me if you need assistance. -- 726655: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726655 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.141410334122035.transcr...@bugs.debian.org
Bug#766553: linux-3.17-1: HID: Please enable CONFIG_HID_LENOVO
Source: linux Version: 3.17-1 Severity: normal Dear Maintainer, 3.17 added a config option CONFIG_HID_LENOVO, which replaced CONFIG_HID_LENOVO_TPKBD to support all Lenovo keyboards. Could it be turned on? It would both solve a regression (support for TP keyboard w/ trackpoint would vanish without), and mean I can happily use my bluetooth keyboard. Many thanks, -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.17-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20141023224704.31611.28022.report...@sitea.gonzo.moosefarmer.org
Bug#766447: add parameter to override the seconds of 'Will restart in 5 seconds.'
Control: reassign -1 initramfs-tools 0.118 On Thu, 2014-10-23 at 15:24 +0800, 積丹尼 Dan Jacobson wrote: Package: src:linux Version: 3.16.5-1 Severity: wishlist Regarding 'Attempt to start maintenance shell failed. Will restart in 5 seconds.' 5 seconds is not long enough to read all but a few of the words on the screen. Please add a boot parameter to control this. Also document it in Documentation/kernel-parameters.txt.gz and perhaps say adjust with xyz= right there in the message. One would think that panic= is the parameter that is used, but it is not. This is controlled by the initramfs, not the kernel. Ben. -- Ben Hutchings Kids! Bringing about Armageddon can be dangerous. Do not attempt it in your own home. - Terry Pratchett and Neil Gaiman, `Good Omens' signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#766447: add parameter to override the seconds of 'Will restart in 5 seconds.'
Processing control commands: reassign -1 initramfs-tools 0.118 Bug #766447 [src:linux] add parameter to override the seconds of 'Will restart in 5 seconds.' Bug reassigned from package 'src:linux' to 'initramfs-tools'. No longer marked as found in versions linux/3.16.5-1. Ignoring request to alter fixed versions of bug #766447 to the same values previously set Bug #766447 [initramfs-tools] add parameter to override the seconds of 'Will restart in 5 seconds.' Marked as found in versions initramfs-tools/0.118. -- 766447: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766447 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.b766447.14141110923278.transcr...@bugs.debian.org
Bug#766448: marked as done (0.116 to 0.118 makes systems unbootable with 5 second message)
Your message dated Fri, 24 Oct 2014 01:38:21 +0100 with message-id 141401.5994.27.ca...@decadent.org.uk and subject line Re: Bug#766448: 0.116 to 0.118 makes systems unbootable with 5 second message has caused the Debian Bug report #766448, regarding 0.116 to 0.118 makes systems unbootable with 5 second message to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 766448: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766448 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: initramfs-tools Version: 0.118 Severity: grave On all my systems, 0.116 works fine, 0.118 just gives some message about rebooting in 5 seconds that is not enough time to read. I.e., the system becomes unbootable. 1. Please tell me what steps you would like me to take. Thanks. ---End Message--- ---BeginMessage--- On Thu, 2014-10-23 at 15:31 +0800, 積丹尼 Dan Jacobson wrote: Package: initramfs-tools Version: 0.118 Severity: grave On all my systems, 0.116 works fine, 0.118 just gives some message about rebooting in 5 seconds that is not enough time to read. I.e., the system becomes unbootable. 1. Please tell me what steps you would like me to take. This is a support request, not a bug report. Ben. -- Ben Hutchings Kids! Bringing about Armageddon can be dangerous. Do not attempt it in your own home. - Terry Pratchett and Neil Gaiman, `Good Omens' signature.asc Description: This is a digitally signed message part ---End Message---
Bug#766562: PCMCIA: A 64 k modem blocks output and the keyboard
Package: linux-source-3.2 Version: 3.2.63-1 Severity: normal This is a multi-part MIME message sent by reportbug. --===1378243998== Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Dear Maintainer, * What led up to the situation? When inserting a PCMCIA card (56 k modem) the keyboard becomes locked and the first and a half line (from the 'kernel.log') is shown on the display. After ejecting it the rest follows on the display. The program script does not catch the text. The computer has about 160 MB memory. From the file kern.log: Oct 23 20:59:49 jeti kernel: pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0 Oct 23 20:59:49 jeti kernel: pcmcia_socket pcmcia_socket0: cs: memory probe 0xa000-0xa0ff: excluding 0xa000-0xa0ff Oct 23 20:59:49 jeti kernel: pcmcia_socket pcmcia_socket0: cs: memory probe 0x6000-0x60ff: excluding 0x6000-0x60ff Oct 23 20:59:49 jeti kernel: pcmcia_socket pcmcia_socket0: cs: warning: no high memory space available! Oct 23 20:59:49 jeti kernel: pcmcia_socket pcmcia_socket0: pccard: card ejected from slot 0 Oct 23 20:59:49 jeti kernel: Clocksource tsc unstable (delta = 55285113603 ns) Oct 23 20:59:49 jeti kernel: Switching to clocksource pit The first output to the display ends in the second line after memory probe 0xa000-0xa0ff: The config file is /proc/config.gz and is in the attachment. The whole kern.log file shows: Oct 23 20:49:08 jeti kernel: Linux version 3.2.60-rt87-2 (b...@jeti.jeti.invalid) (gcc version 4.9.0 (Debian 4.9.0-7) ) #2 Thu Jul 3 22:21:20 GMT 2014 Oct 23 20:49:08 jeti kernel: BIOS-provided physical RAM map: Oct 23 20:49:08 jeti kernel: BIOS-e801: - 0009f000 (usable) Oct 23 20:49:08 jeti kernel: BIOS-e801: 0010 - 0a00 (usable) Oct 23 20:49:08 jeti kernel: Notice: NX (Execute Disable) protection missing in CPU! Oct 23 20:49:08 jeti kernel: SMBIOS 2.2 present. Oct 23 20:49:08 jeti kernel: DMI: MiTAC 5033/5033, BIOS Version R3.03 08/10/99 Oct 23 20:49:08 jeti kernel: e820 update range: - 0001 (usable) == (reserved) Oct 23 20:49:08 jeti kernel: e820 remove range: 000a - 0010 (usable) Oct 23 20:49:08 jeti kernel: last_pfn = 0xa000 max_arch_pfn = 0x10 Oct 23 20:49:08 jeti kernel: initial memory mapped : 0 - 0180 Oct 23 20:49:08 jeti kernel: Base memory trampoline at [c009e000] 9e000 size 4096 Oct 23 20:49:08 jeti kernel: init_memory_mapping: -0a00 Oct 23 20:49:08 jeti kernel: 00 - 40 page 4k Oct 23 20:49:08 jeti kernel: 40 - 000a00 page 2M Oct 23 20:49:08 jeti kernel: kernel direct mapping tables up to a00 @ 17f9000-180 Oct 23 20:49:08 jeti kernel: 160MB LOWMEM available. Oct 23 20:49:08 jeti kernel: mapped low ram: 0 - 0a00 Oct 23 20:49:08 jeti kernel: low ram: 0 - 0a00 Oct 23 20:49:08 jeti kernel: Zone PFN ranges: Oct 23 20:49:08 jeti kernel: DMA 0x0010 - 0x1000 Oct 23 20:49:08 jeti kernel: Normal 0x1000 - 0xa000 Oct 23 20:49:08 jeti kernel: Movable zone start PFN for each node Oct 23 20:49:08 jeti kernel: early_node_map[2] active PFN ranges Oct 23 20:49:08 jeti kernel:0: 0x0010 - 0x009f Oct 23 20:49:08 jeti kernel:0: 0x0100 - 0xa000 Oct 23 20:49:08 jeti kernel: On node 0 totalpages: 40847 Oct 23 20:49:08 jeti kernel: free_area_init_node: node 0, pgdat c1388a80, node_mem_map c9ec0200 Oct 23 20:49:08 jeti kernel: DMA zone: 32 pages used for memmap Oct 23 20:49:08 jeti kernel: DMA zone: 0 pages reserved Oct 23 20:49:08 jeti kernel: DMA zone: 3951 pages, LIFO batch:0 Oct 23 20:49:08 jeti kernel: Normal zone: 288 pages used for memmap Oct 23 20:49:08 jeti kernel: Normal zone: 36576 pages, LIFO batch:7 Oct 23 20:49:08 jeti kernel: Allocating PCI resources starting at a00 (gap: a00:f600) Oct 23 20:49:08 jeti kernel: pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 Oct 23 20:49:08 jeti kernel: pcpu-alloc: [0] 0 Oct 23 20:49:08 jeti kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 40527 Oct 23 20:49:08 jeti kernel: Kernel command line: auto BOOT_IMAGE=3.2.60-1 ro root=803 floppy=daring Oct 23 20:49:08 jeti kernel: floppy0: Assuming standard floppy hardware Oct 23 20:49:08 jeti kernel: PID hash table entries: 1024 (order: 0, 4096 bytes) Oct 23 20:49:08 jeti kernel: Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Oct 23 20:49:08 jeti kernel: Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Oct 23 20:49:08 jeti kernel: Initializing CPU#0 Oct 23 20:49:08 jeti kernel: Memory: 157604k/163840k available (2709k kernel code, 5784k reserved, 925k data, 240k init, 0k highmem) Oct 23 20:49:08 jeti kernel: virtual kernel memory layout: Oct 23 20:49:08 jeti kernel:fixmap : 0xfffe5000 -
Bug#766448: root fstype auto in /etc/fstab guaranteed unbootable
reopen 766448 retitle root fstype auto in /etc/fstab guaranteed unbootable thanks Please try these simple steps: Change /etc/fstab making the type for / be auto, not ext4 etc. Now with initramfs-tools Ver: 0.118 installed, run update-initramfs -u and reboot. But first see also #766578. -- 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/87wq7qm3op@jidanni.org
Processed (with 1 errors): root fstype auto in /etc/fstab guaranteed unbootable
Processing commands for cont...@bugs.debian.org:
reopen 766448
Bug #766448 {Done: Ben Hutchings b...@decadent.org.uk} [initramfs-tools]
0.116 to 0.118 makes systems unbootable with 5 second message
Bug reopened
Ignoring request to alter fixed versions of bug #766448 to the same values
previously set
retitle root fstype auto in /etc/fstab guaranteed unbootable
Unknown command or malformed arguments to command.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
766448: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766448
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
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/handler.s.c.141412885710584.transcr...@bugs.debian.org
Processed: retitle 766448 to root fstype auto in /etc/fstab guaranteed unbootable
Processing commands for cont...@bugs.debian.org: retitle 766448 root fstype auto in /etc/fstab guaranteed unbootable Bug #766448 [initramfs-tools] 0.116 to 0.118 makes systems unbootable with 5 second message Changed Bug title to 'root fstype auto in /etc/fstab guaranteed unbootable' from '0.116 to 0.118 makes systems unbootable with 5 second message' thanks Stopping processing here. Please contact me if you need assistance. -- 766448: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766448 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.141412907012487.transcr...@bugs.debian.org
