Bug#854613: linux-image-4.8.0-2-amd64: System hangs at "Loading initial ramdisk" after upgrading to 4.9
On Wed, Feb 8, 2017 at 1:19 PM, Ben Hutchings <b...@decadent.org.uk> wrote: > Control: notfound -1 4.8.15-2 > Control: tag -1 moreinfo > > On Wed, 2017-02-08 at 09:17 -0800, Jonathan Yu wrote: > > Package: src:linux > > Version: 4.8.15-2 > [...] > Hey Ben, Forgot to say: Thank you very much for your great work! I've never had any trouble upgrading in the past, which is a testament to your hard work :) > > But this is the working version, not the broken versin. Which 4.9.x > version did you install? If it is 4.9.2-2 (current in testing), please > try 4.9.6-3 (current in unstable). > I'm using: ii linux-image-4.9.0-1-amd644.9.2-2 amd64Linux 4.9 for 64-bit PCs (signed) I will upgrade to the version in unstable and try again, thanks for the tip! Here's my apt policy (I guess it might be helpful if this was included in reportbug reports) - I use packages mostly from testing :) $ apt policy Package files: 100 /var/lib/dpkg/status release a=now 500 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages release v=1.0,o=Google, Inc.,a=stable,n=stable,l=Google,c=main,b=amd64 origin dl.google.com -10 http://ftp.us.debian.org/debian experimental/non-free i386 Packages release o=Debian,a=experimental,n=experimental,l=Debian,c=non-free,b=i386 origin ftp.us.debian.org -10 http://ftp.us.debian.org/debian experimental/non-free amd64 Packages release o=Debian,a=experimental,n=experimental,l=Debian,c=non-free,b=amd64 origin ftp.us.debian.org -10 http://ftp.us.debian.org/debian experimental/main i386 Packages release o=Debian,a=experimental,n=experimental,l=Debian,c=main,b=i386 origin ftp.us.debian.org -10 http://ftp.us.debian.org/debian experimental/main amd64 Packages release o=Debian,a=experimental,n=experimental,l=Debian,c=main,b=amd64 origin ftp.us.debian.org -10 http://ftp.us.debian.org/debian unstable/non-free i386 Packages release o=Debian,a=unstable,n=sid,l=Debian,c=non-free,b=i386 origin ftp.us.debian.org -10 http://ftp.us.debian.org/debian unstable/non-free amd64 Packages release o=Debian,a=unstable,n=sid,l=Debian,c=non-free,b=amd64 origin ftp.us.debian.org -10 http://ftp.us.debian.org/debian unstable/main i386 Packages release o=Debian,a=unstable,n=sid,l=Debian,c=main,b=i386 origin ftp.us.debian.org -10 http://ftp.us.debian.org/debian unstable/main amd64 Packages release o=Debian,a=unstable,n=sid,l=Debian,c=main,b=amd64 origin ftp.us.debian.org 900 http://ftp.us.debian.org/debian testing/contrib i386 Packages release o=Debian,a=testing,n=stretch,l=Debian,c=contrib,b=i386 origin ftp.us.debian.org 900 http://ftp.us.debian.org/debian testing/contrib amd64 Packages release o=Debian,a=testing,n=stretch,l=Debian,c=contrib,b=amd64 origin ftp.us.debian.org 900 http://ftp.us.debian.org/debian testing/non-free i386 Packages release o=Debian,a=testing,n=stretch,l=Debian,c=non-free,b=i386 origin ftp.us.debian.org 900 http://ftp.us.debian.org/debian testing/non-free amd64 Packages release o=Debian,a=testing,n=stretch,l=Debian,c=non-free,b=amd64 origin ftp.us.debian.org 900 http://ftp.us.debian.org/debian testing/main i386 Packages release o=Debian,a=testing,n=stretch,l=Debian,c=main,b=i386 origin ftp.us.debian.org 900 http://ftp.us.debian.org/debian testing/main amd64 Packages release o=Debian,a=testing,n=stretch,l=Debian,c=main,b=amd64 origin ftp.us.debian.org Pinned packages:
Bug#854613: linux-image-4.8.0-2-amd64: System hangs at "Loading initial ramdisk" after upgrading to 4.9
Package: src:linux Version: 4.8.15-2 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? After upgrading my system (Debian testing) and rebooting, the system hangs at "Loading initial ramdisk". * What exactly did you do (or not do) that was effective (or ineffective)? I also tried editing the Grub boot parameters to remove "quiet splash", but this did not produce any additional output. I'm happy to help troubleshoot the problem and provide other diagnostics that you may need. I didn't see anything useful in the systemd journal or dmesg for a successful boot. I'm currently booted with an older kernel that I had installed (4.8) and that works fine. * What was the outcome of this action? The system hangs. * What outcome did you expect instead? I expected the system to boot normally. Here are the contents of my /boot folder. I should be using Debian packages for everything, except for Chrome Beta which I have installed via Google's repository. $ ls -al /boot total 72M drwxr-xr-x. 5 root root 1.0K Jan 25 12:08 . drwxr-xr-x. 22 root root 4.0K Jan 25 11:52 .. -rw-r--r-- 1 root root 180K Nov 12 20:38 config-4.8.0-1-amd64 -rw-r--r-- 1 root root 180K Jan 4 11:39 config-4.8.0-2-amd64 -rw-r--r-- 1 root root 182K Jan 12 07:52 config-4.9.0-1-amd64 drwx-- 3 root root 4.0K Dec 31 1969 efi drwxr-xr-x. 5 root root 1.0K Feb 8 08:56 grub -rw---. 1 root root 13M Jun 12 2016 initramfs-4.6.0-1-amd64.img -rw--- 1 root root 13M Feb 8 08:56 initrd.img-4.8.0-1-amd64 -rw--- 1 root root 13M Feb 8 08:56 initrd.img-4.8.0-2-amd64 -rw--- 1 root root 13M Feb 8 08:56 initrd.img-4.9.0-1-amd64 drwx--. 2 root root 12K Feb 10 2016 lost+found -rw-r--r-- 1 root root 3.1M Nov 12 20:38 System.map-4.8.0-1-amd64 -rw-r--r-- 1 root root 3.0M Jan 4 11:39 System.map-4.8.0-2-amd64 -rw-r--r-- 1 root root 3.1M Jan 12 07:52 System.map-4.9.0-1-amd64 -rw-r--r-- 1 root root 4.0M Nov 16 09:13 vmlinuz-4.8.0-1-amd64 -rw-r--r-- 1 root root 4.0M Jan 5 20:14 vmlinuz-4.8.0-2-amd64 -rw-r--r-- 1 root root 4.0M Jan 13 06:51 vmlinuz-4.9.0-1-amd64 *** End of the template - remove these template lines *** -- Package-specific info: ** Version: Linux version 4.8.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 5.4.1 20161202 (Debian 5.4.1-4) ) #1 SMP Debian 4.8.15-2 (2017-01-04) ** Command line: BOOT_IMAGE=/vmlinuz-4.8.0-2-amd64 root=/dev/mapper/theory--vg-theory--root ro quiet splash ** Not tainted ** Kernel log: [ 10.089155] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' [ 10.089690] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 10.090060] iwlwifi :03:00.0 wlp3s0: renamed from wlan0 [ 10.226610] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.226611] Bluetooth: BNEP filters: protocol multicast [ 10.226614] Bluetooth: BNEP socket layer initialized [ 10.550151] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready [ 10.566160] psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4758] [ 10.595881] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1096..] [ 10.653481] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xf003a3/0x943300/0x12e800/0x1, board id: 3053, fw id: 2560 [ 10.653488] psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0 [ 10.690881] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input8 [ 10.793849] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready [ 10.797434] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 10.799530] iwlwifi :03:00.0: L1 Enabled - LTR Enabled [ 10.799784] iwlwifi :03:00.0: L1 Enabled - LTR Enabled [ 11.013734] iwlwifi :03:00.0: L1 Enabled - LTR Enabled [ 11.013995] iwlwifi :03:00.0: L1 Enabled - LTR Enabled [ 11.035325] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 11.045690] iwlwifi :03:00.0: L1 Enabled - LTR Enabled [ 11.045976] iwlwifi :03:00.0: L1 Enabled - LTR Enabled [ 11.257971] iwlwifi :03:00.0: L1 Enabled - LTR Enabled [ 11.258233] iwlwifi :03:00.0: L1 Enabled - LTR Enabled [ 11.273130] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 11.281949] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this. [ 11.299334] IPv6: ADDRCONF(NETDEV_UP): vmnat: link is not ready [ 11.355302] Ebtables v2.0 registered [ 11.436688] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready [ 12.817758] thinkpad_acpi: docked into hotplug port replicator [ 13.693745] usb 4-5: new SuperSpeed USB device number 2 using xhci_hcd [ 13.719705] usb 4-5: New USB device found, idVendor=17ef, idProduct=1010 [ 13.719710] usb 4-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 13.719713] usb 4-5: Product:
Bug#563134: RFP: libobject-insideout-perl -- Comprehensive inside-out object support module
Forwarding this as I sent it to the wrong address before. -- Forwarded message -- From: Jonathan Yu jaw...@cpan.org Date: Sat, Jan 2, 2010 at 2:42 PM Subject: RFP: libobject-insideout-perl -- Comprehensive inside-out object support module To: Tom Jones tom.jo...@oucs.ox.ac.uk Cc: 56...@bugs.debian.org Hi: I was looking at clearing some old RFP bugs, and I noticed that Object::InsideOut provides similar functionality to Class::InsideOut, and I'm not sure what the differences are, as I use neither of them, and it wasn't clear in the POD. Are you still interested in this module, or can I just close this bug as resolved? Cheers, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org