[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
I still have this or a similar issue. How do apply the patch? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: ===SRU Justification=== [Impact] Systems with acpi-lpss can't do S3/S4 on Bionic. [Test] Users confirmed these patches work for them. [Fix] Commit a192aa923b66a (ACPI / LPSS: Consolidate runtime PM and system sleep handling) applies quirks for both runtime and system suspend. This causes problems for some systems, so avoid using quirks on S3 and S4. [Regression Potential] Low. These patches are in upstream stable, and it brings back driver's old behavior. ===Original Bug Report=== I have installed Kubuntu 18.04 on 3 different machines (my friend's and my own) with no suspend problems but my HP Pavilion 11 x360 does not suspend. It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse, Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu 18.04. I have also tried suspend using a live USB of 18.04 on this machine and it fails in the same way, so does not appear to be caused by any additional programs that I had installed. By installing an older kernel (4.14) on Kubuntu 18.04 the suspend function works as expected. Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the suspend failure that freezes the machine and requires a hard reset. Correct behaviour is - Screen goes blank, fan goes off, power LED flashes to show machine is in suspend. Pressing power button triggers 'resume' function. What happens - Screen goes blank, fan stays on, power LED stays on. Machine stays in this state and does not respond to any keyboard interaction, mouse movement or power button presses. Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response. The only way to use the machine is to shut down by holding down the power button. Checking the logs suggests that the machine believes it is in suspend mode sleep [deep] when it isn't. Having to hard reset to get any response means that the kernel logs say no more than sleep [deep] pm-suspend also results in the same problems with kernels 4.15 and 4.16, but works fine with 4.14. It is curious that a machine that suspends fine on an earlier 4.14 kernel no longer works with 4.15 and above, whilst 3 other machines (including one with pretty similar hardware) do not exhibit this problem. There are only a handful of questions about it on the forums but at least 3 other people have the same problem: https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on- resuming-from-suspend https://askubuntu.com/questions/1041369/after-upgrading- from-17-10-ubuntu-18-04-wont-sleep-suspend I am attempting to round up anyone else with the same issue and point them to this bug report. My laptop is HP Pavilion x360 11-n013na Matalaks is Acer Aspire ES1-511 collisionTwo has XPS 9560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
I think I had the same problem on zesty. It started occurring AFTER I used nvidia-settings to switch to integrated intel graphics on a Dell XPS-15 9560 (GTX1050) and completely uninstalled nvidia drivers to get back to a working laptop. Indeed it seems to happen while using chromium. My machine was nog completely crashed though, I could still ssh into it. But restarting X or even rebooting was impossible, I did need to force power off. I installed the upstream kernel, to be precise: linux- image-4.12.0-041200rc3-generic_4.12.0-041200rc3.201705282131_amd64.deb For about a day now the laptop is very stable and VERY cool. No fan noise and battery usage seems to be much better than ever before without nvidia drivers. Can't wait to get this kernel fully supported. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1680904 Title: zesty unable to handle kernel NULL pointer dereference Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: Upgraded to zesty about a week ago. Ran into this on latest kernel. (during high load, nothing in particular seems to cause it to happen). Did not happen with previous (4.10.0.14.16) kernel. Only after update to 4.10.0.15.17, has happened about 3 times since then (or other crashes), this is the one I could capture. kern.log entries below. Let me know if you need anything else from me. Thanks! Apr 7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL pointer dereference at 0018 Apr 7 11:20:28 doe kernel: [26003.796375] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.796404] PGD 0 Apr 7 11:20:28 doe kernel: [26003.796405] Apr 7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP Apr 7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 hid_multitouch joydev i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core asus_nb_wmi Apr 7 11:20:28 doe kernel: [26003.796722] snd_hwdep asus_wmi sparse_keymap snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless parport_pc ppdev lp parport ip_tables Apr 7 11:20:28 doe kernel: [26003.797026] x_tables autofs4 algif_skcipher af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes Apr 7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: chromium-browse Tainted: P O4.10.0-15-generic #17-Ubuntu Apr 7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015 Apr 7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: c25b5ea8c000 Apr 7 11:20:28 doe kernel: [26003.797250] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 00010246 Apr 7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 0003 RCX: 0003 Apr 7 11:20:28 doe kernel: [26003.797325] RDX: RSI: 9bbae7c0a000 RDI: 9bbba0418000 Apr 7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: R09: Apr 7 11:20:28 doe kernel: [26003.797378] R10:
[Kernel-packages] [Bug 1291969] Re: No usb on resume from suspend
confirmed, still exists after sudo apt-get dist-upgrade. All USB devices stop working, but I noticed also internet cable connection stopped working. so it is even broader then USB. Reconnecting devices does not help! ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1291969 Title: No usb on resume from suspend Status in “linux” package in Ubuntu: Confirmed Bug description: My XPS13 running 14.04 sometimes loses its USB ports after resume from suspend. When this happens the entire bus seems dead - both external ports do not work, and internal USB devices (webcam, touchscreen) are also non-functional. Furthermore lsusb shows no devices attached. Rebooting or performing another suspend/resume cycle will clear the problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-17-generic 3.13.0-17.37 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 2868 F pulseaudio /dev/snd/controlC0: steve 2868 F pulseaudio CurrentDesktop: Unity Date: Thu Mar 13 08:36:46 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=79084358-087f-4cee-a0be-e2f78361873f InstallationDate: Installed on 2013-12-02 (100 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS13 9333 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-17-generic N/A linux-backports-modules-3.13.0-17-generic N/A linux-firmware 1.126 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-02-12 (28 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1291969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1291969] Re: No usb on resume from suspend
Problem seems related to Nouveau drivers. After installing Nvidea binary drivers the problem was fixed. So still exists for nouveau drivers -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1291969 Title: No usb on resume from suspend Status in “linux” package in Ubuntu: Confirmed Bug description: My XPS13 running 14.04 sometimes loses its USB ports after resume from suspend. When this happens the entire bus seems dead - both external ports do not work, and internal USB devices (webcam, touchscreen) are also non-functional. Furthermore lsusb shows no devices attached. Rebooting or performing another suspend/resume cycle will clear the problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-17-generic 3.13.0-17.37 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 2868 F pulseaudio /dev/snd/controlC0: steve 2868 F pulseaudio CurrentDesktop: Unity Date: Thu Mar 13 08:36:46 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=79084358-087f-4cee-a0be-e2f78361873f InstallationDate: Installed on 2013-12-02 (100 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS13 9333 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-17-generic N/A linux-backports-modules-3.13.0-17-generic N/A linux-firmware 1.126 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-02-12 (28 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1291969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1291969] Re: No usb on resume from suspend
I have the same problem here after a fresh install of Ubuntu 14.04. When I suspend I can still wake up de computer with my USB mouse or keyboard, but they no longer function correctly. For instance the mouse cursor will still move but clicking no longer works. I can wake up with the keyboard but then it stops working. USB memory stick also seems frozen. Reconnecting devices does not help. My keyboard lights up briefly but that is all. The mouse completely stops working after reconnect. On another partition I first did an upgrade from 13.10 to 14.04. Suspend works fine here. I did a fresh install on another partition bescause it would not boot. After the new install the grub menu was updated and it works fine now. But then I noticed the suspend problem on the fresh install. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1291969 Title: No usb on resume from suspend Status in “linux” package in Ubuntu: Confirmed Bug description: My XPS13 running 14.04 sometimes loses its USB ports after resume from suspend. When this happens the entire bus seems dead - both external ports do not work, and internal USB devices (webcam, touchscreen) are also non-functional. Furthermore lsusb shows no devices attached. Rebooting or performing another suspend/resume cycle will clear the problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-17-generic 3.13.0-17.37 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 2868 F pulseaudio /dev/snd/controlC0: steve 2868 F pulseaudio CurrentDesktop: Unity Date: Thu Mar 13 08:36:46 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=79084358-087f-4cee-a0be-e2f78361873f InstallationDate: Installed on 2013-12-02 (100 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS13 9333 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-17-generic N/A linux-backports-modules-3.13.0-17-generic N/A linux-firmware 1.126 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-02-12 (28 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1291969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1237392] Re: kernels following version 3.8.0-27 do not start
Hi Joseph, I installed the image files and tested and it runs. However, as before I could not install all: specifically the tools file gave a problem. Not sure if it matters for you or not, so I copy the last part of the messages, so you can see it seems to be a dependency error. COPY: Generating grub.cfg ... Found linux image: /boot/vmlinuz-3.11.0-13-generic Found initrd image: /boot/initrd.img-3.11.0-13-generic Found linux image: /boot/vmlinuz-3.8.13-03081304-generic Found initrd image: /boot/initrd.img-3.8.13-03081304-generic Found linux image: /boot/vmlinuz-3.8.0-32-generic Found initrd image: /boot/initrd.img-3.8.0-32-generic Found linux image: /boot/vmlinuz-3.8.0-31-generic Found initrd image: /boot/initrd.img-3.8.0-31-generic Found linux image: /boot/vmlinuz-3.8.0-19-generic Found initrd image: /boot/initrd.img-3.8.0-19-generic Found memtest86+ image: /boot/memtest86+.bin done dpkg: dependency problems prevent configuration of linux-tools-3.11.0-13-generic: linux-tools-3.11.0-13-generic depends on linux-tools-3.11.0-13; however: Package linux-tools-3.11.0-13 is not installed. dpkg: error processing linux-tools-3.11.0-13-generic (--install): dependency problems - leaving unconfigured Errors were encountered while processing: linux-tools-3.11.0-13-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1237392 Title: kernels following version 3.8.0-27 do not start Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Raring: In Progress Status in “linux” source package in Saucy: In Progress Bug description: All kernel updates on ubuntu following kernel 3.8.0-27 result in an empty screen with no indication of startup, no response to the keyboard. I can only start up using kernel version 3.8.0-27-generic. All following numbers (up to and including 3.8.0-31-generic) do not result in a running system. Also, the display no message at all when starting up (after grub). I checked the logfiles with grep -n Linux version 3.8.0- * and found only 27 to be logged, nothing for the other kernels. I am at a loss how to continue. I am running the most recent version of Ubuntu server. Two days ago I reinstalled Ubuntu with essentially the same result. The installation kernel version 3.8.0-19 works fine. The updated kernel 3.8.0-31 does not work. The following is the situation: When I let the machine start on itself I get no output at all. When I manually tell ubuntu to start the most recent kernel, I get 2 lines: Loading Linux-3.8.0-31-generic ... Loading initial ramdisk ... that's it. When I manually start the recovery kernel, I get a lot of information. Finally it drops to a terminal and indicates it could not load the LVM partition /dev/mapper/Server-Root. This is why I never see any result in my message or dmesg on disk. The problem seems to be with the Areca Raid controller. It does a reset of the scsi bus eh until it finally gives up and drops to a terminal. A while after the system goes berserk with messages of non responding scsi bus. As I cannot reach my harddisk, is there a way to find out what is wrong? Why does everything work fine up to and including kernel 27 and starts to malfunction after that? Did the Areca software change in some way? P.S. When I start kernel version 3.8.0-19, everything works fine. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubuntu-release-upgrader-core 1:0.192.13 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CrashDB: ubuntu Date: Wed Oct 9 14:53:03 2013 InstallationDate: Installed on 2013-10-07 (1 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130423.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1237392] Re: kernels following version 3.8.0-27 do not start
Yep, bug resolved. Thank you very much for your effort and time. Do you know in what ubuntu update it will be? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1237392 Title: kernels following version 3.8.0-27 do not start Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Raring: In Progress Status in “linux” source package in Saucy: In Progress Bug description: All kernel updates on ubuntu following kernel 3.8.0-27 result in an empty screen with no indication of startup, no response to the keyboard. I can only start up using kernel version 3.8.0-27-generic. All following numbers (up to and including 3.8.0-31-generic) do not result in a running system. Also, the display no message at all when starting up (after grub). I checked the logfiles with grep -n Linux version 3.8.0- * and found only 27 to be logged, nothing for the other kernels. I am at a loss how to continue. I am running the most recent version of Ubuntu server. Two days ago I reinstalled Ubuntu with essentially the same result. The installation kernel version 3.8.0-19 works fine. The updated kernel 3.8.0-31 does not work. The following is the situation: When I let the machine start on itself I get no output at all. When I manually tell ubuntu to start the most recent kernel, I get 2 lines: Loading Linux-3.8.0-31-generic ... Loading initial ramdisk ... that's it. When I manually start the recovery kernel, I get a lot of information. Finally it drops to a terminal and indicates it could not load the LVM partition /dev/mapper/Server-Root. This is why I never see any result in my message or dmesg on disk. The problem seems to be with the Areca Raid controller. It does a reset of the scsi bus eh until it finally gives up and drops to a terminal. A while after the system goes berserk with messages of non responding scsi bus. As I cannot reach my harddisk, is there a way to find out what is wrong? Why does everything work fine up to and including kernel 27 and starts to malfunction after that? Did the Areca software change in some way? P.S. When I start kernel version 3.8.0-19, everything works fine. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubuntu-release-upgrader-core 1:0.192.13 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CrashDB: ubuntu Date: Wed Oct 9 14:53:03 2013 InstallationDate: Installed on 2013-10-07 (1 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130423.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1237392] Re: kernels following version 3.8.0-27 do not start
This one shows the error. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1237392 Title: kernels following version 3.8.0-27 do not start Status in “linux” package in Ubuntu: Confirmed Bug description: All kernel updates on ubuntu following kernel 3.8.0-27 result in an empty screen with no indication of startup, no response to the keyboard. I can only start up using kernel version 3.8.0-27-generic. All following numbers (up to and including 3.8.0-31-generic) do not result in a running system. Also, the display no message at all when starting up (after grub). I checked the logfiles with grep -n Linux version 3.8.0- * and found only 27 to be logged, nothing for the other kernels. I am at a loss how to continue. I am running the most recent version of Ubuntu server. Two days ago I reinstalled Ubuntu with essentially the same result. The installation kernel version 3.8.0-19 works fine. The updated kernel 3.8.0-31 does not work. The following is the situation: When I let the machine start on itself I get no output at all. When I manually tell ubuntu to start the most recent kernel, I get 2 lines: Loading Linux-3.8.0-31-generic ... Loading initial ramdisk ... that's it. When I manually start the recovery kernel, I get a lot of information. Finally it drops to a terminal and indicates it could not load the LVM partition /dev/mapper/Server-Root. This is why I never see any result in my message or dmesg on disk. The problem seems to be with the Areca Raid controller. It does a reset of the scsi bus eh until it finally gives up and drops to a terminal. A while after the system goes berserk with messages of non responding scsi bus. As I cannot reach my harddisk, is there a way to find out what is wrong? Why does everything work fine up to and including kernel 27 and starts to malfunction after that? Did the Areca software change in some way? P.S. When I start kernel version 3.8.0-19, everything works fine. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubuntu-release-upgrader-core 1:0.192.13 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CrashDB: ubuntu Date: Wed Oct 9 14:53:03 2013 InstallationDate: Installed on 2013-10-07 (1 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130423.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1237392] Re: kernels following version 3.8.0-27 do not start
It Works!! I can't help but feel victory when it works only, though I think I understand how a bisect works: like a binary search right? Anyway: it works!!! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1237392 Title: kernels following version 3.8.0-27 do not start Status in “linux” package in Ubuntu: Confirmed Bug description: All kernel updates on ubuntu following kernel 3.8.0-27 result in an empty screen with no indication of startup, no response to the keyboard. I can only start up using kernel version 3.8.0-27-generic. All following numbers (up to and including 3.8.0-31-generic) do not result in a running system. Also, the display no message at all when starting up (after grub). I checked the logfiles with grep -n Linux version 3.8.0- * and found only 27 to be logged, nothing for the other kernels. I am at a loss how to continue. I am running the most recent version of Ubuntu server. Two days ago I reinstalled Ubuntu with essentially the same result. The installation kernel version 3.8.0-19 works fine. The updated kernel 3.8.0-31 does not work. The following is the situation: When I let the machine start on itself I get no output at all. When I manually tell ubuntu to start the most recent kernel, I get 2 lines: Loading Linux-3.8.0-31-generic ... Loading initial ramdisk ... that's it. When I manually start the recovery kernel, I get a lot of information. Finally it drops to a terminal and indicates it could not load the LVM partition /dev/mapper/Server-Root. This is why I never see any result in my message or dmesg on disk. The problem seems to be with the Areca Raid controller. It does a reset of the scsi bus eh until it finally gives up and drops to a terminal. A while after the system goes berserk with messages of non responding scsi bus. As I cannot reach my harddisk, is there a way to find out what is wrong? Why does everything work fine up to and including kernel 27 and starts to malfunction after that? Did the Areca software change in some way? P.S. When I start kernel version 3.8.0-19, everything works fine. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubuntu-release-upgrader-core 1:0.192.13 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CrashDB: ubuntu Date: Wed Oct 9 14:53:03 2013 InstallationDate: Installed on 2013-10-07 (1 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130423.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1237392] Re: kernels following version 3.8.0-27 do not start
Indeed the kernel runs again. Are we getting closer to the culprit? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1237392 Title: kernels following version 3.8.0-27 do not start Status in “linux” package in Ubuntu: Confirmed Bug description: All kernel updates on ubuntu following kernel 3.8.0-27 result in an empty screen with no indication of startup, no response to the keyboard. I can only start up using kernel version 3.8.0-27-generic. All following numbers (up to and including 3.8.0-31-generic) do not result in a running system. Also, the display no message at all when starting up (after grub). I checked the logfiles with grep -n Linux version 3.8.0- * and found only 27 to be logged, nothing for the other kernels. I am at a loss how to continue. I am running the most recent version of Ubuntu server. Two days ago I reinstalled Ubuntu with essentially the same result. The installation kernel version 3.8.0-19 works fine. The updated kernel 3.8.0-31 does not work. The following is the situation: When I let the machine start on itself I get no output at all. When I manually tell ubuntu to start the most recent kernel, I get 2 lines: Loading Linux-3.8.0-31-generic ... Loading initial ramdisk ... that's it. When I manually start the recovery kernel, I get a lot of information. Finally it drops to a terminal and indicates it could not load the LVM partition /dev/mapper/Server-Root. This is why I never see any result in my message or dmesg on disk. The problem seems to be with the Areca Raid controller. It does a reset of the scsi bus eh until it finally gives up and drops to a terminal. A while after the system goes berserk with messages of non responding scsi bus. As I cannot reach my harddisk, is there a way to find out what is wrong? Why does everything work fine up to and including kernel 27 and starts to malfunction after that? Did the Areca software change in some way? P.S. When I start kernel version 3.8.0-19, everything works fine. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubuntu-release-upgrader-core 1:0.192.13 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CrashDB: ubuntu Date: Wed Oct 9 14:53:03 2013 InstallationDate: Installed on 2013-10-07 (1 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130423.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1237392] Re: kernels following version 3.8.0-27 do not start
Right. This one runs ok! I will just keep it running and await your next kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1237392 Title: kernels following version 3.8.0-27 do not start Status in “linux” package in Ubuntu: Confirmed Bug description: All kernel updates on ubuntu following kernel 3.8.0-27 result in an empty screen with no indication of startup, no response to the keyboard. I can only start up using kernel version 3.8.0-27-generic. All following numbers (up to and including 3.8.0-31-generic) do not result in a running system. Also, the display no message at all when starting up (after grub). I checked the logfiles with grep -n Linux version 3.8.0- * and found only 27 to be logged, nothing for the other kernels. I am at a loss how to continue. I am running the most recent version of Ubuntu server. Two days ago I reinstalled Ubuntu with essentially the same result. The installation kernel version 3.8.0-19 works fine. The updated kernel 3.8.0-31 does not work. The following is the situation: When I let the machine start on itself I get no output at all. When I manually tell ubuntu to start the most recent kernel, I get 2 lines: Loading Linux-3.8.0-31-generic ... Loading initial ramdisk ... that's it. When I manually start the recovery kernel, I get a lot of information. Finally it drops to a terminal and indicates it could not load the LVM partition /dev/mapper/Server-Root. This is why I never see any result in my message or dmesg on disk. The problem seems to be with the Areca Raid controller. It does a reset of the scsi bus eh until it finally gives up and drops to a terminal. A while after the system goes berserk with messages of non responding scsi bus. As I cannot reach my harddisk, is there a way to find out what is wrong? Why does everything work fine up to and including kernel 27 and starts to malfunction after that? Did the Areca software change in some way? P.S. When I start kernel version 3.8.0-19, everything works fine. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubuntu-release-upgrader-core 1:0.192.13 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CrashDB: ubuntu Date: Wed Oct 9 14:53:03 2013 InstallationDate: Installed on 2013-10-07 (1 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130423.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1237392] Re: kernels following version 3.8.0-27 do not start
Nope, didn't work. Looking forward to your next kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1237392 Title: kernels following version 3.8.0-27 do not start Status in “linux” package in Ubuntu: Confirmed Bug description: All kernel updates on ubuntu following kernel 3.8.0-27 result in an empty screen with no indication of startup, no response to the keyboard. I can only start up using kernel version 3.8.0-27-generic. All following numbers (up to and including 3.8.0-31-generic) do not result in a running system. Also, the display no message at all when starting up (after grub). I checked the logfiles with grep -n Linux version 3.8.0- * and found only 27 to be logged, nothing for the other kernels. I am at a loss how to continue. I am running the most recent version of Ubuntu server. Two days ago I reinstalled Ubuntu with essentially the same result. The installation kernel version 3.8.0-19 works fine. The updated kernel 3.8.0-31 does not work. The following is the situation: When I let the machine start on itself I get no output at all. When I manually tell ubuntu to start the most recent kernel, I get 2 lines: Loading Linux-3.8.0-31-generic ... Loading initial ramdisk ... that's it. When I manually start the recovery kernel, I get a lot of information. Finally it drops to a terminal and indicates it could not load the LVM partition /dev/mapper/Server-Root. This is why I never see any result in my message or dmesg on disk. The problem seems to be with the Areca Raid controller. It does a reset of the scsi bus eh until it finally gives up and drops to a terminal. A while after the system goes berserk with messages of non responding scsi bus. As I cannot reach my harddisk, is there a way to find out what is wrong? Why does everything work fine up to and including kernel 27 and starts to malfunction after that? Did the Areca software change in some way? P.S. When I start kernel version 3.8.0-19, everything works fine. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubuntu-release-upgrader-core 1:0.192.13 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CrashDB: ubuntu Date: Wed Oct 9 14:53:03 2013 InstallationDate: Installed on 2013-10-07 (1 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130423.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1237392] Re: kernels following version 3.8.0-27 do not start
Nope, not working. same same. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1237392 Title: kernels following version 3.8.0-27 do not start Status in “linux” package in Ubuntu: Confirmed Bug description: All kernel updates on ubuntu following kernel 3.8.0-27 result in an empty screen with no indication of startup, no response to the keyboard. I can only start up using kernel version 3.8.0-27-generic. All following numbers (up to and including 3.8.0-31-generic) do not result in a running system. Also, the display no message at all when starting up (after grub). I checked the logfiles with grep -n Linux version 3.8.0- * and found only 27 to be logged, nothing for the other kernels. I am at a loss how to continue. I am running the most recent version of Ubuntu server. Two days ago I reinstalled Ubuntu with essentially the same result. The installation kernel version 3.8.0-19 works fine. The updated kernel 3.8.0-31 does not work. The following is the situation: When I let the machine start on itself I get no output at all. When I manually tell ubuntu to start the most recent kernel, I get 2 lines: Loading Linux-3.8.0-31-generic ... Loading initial ramdisk ... that's it. When I manually start the recovery kernel, I get a lot of information. Finally it drops to a terminal and indicates it could not load the LVM partition /dev/mapper/Server-Root. This is why I never see any result in my message or dmesg on disk. The problem seems to be with the Areca Raid controller. It does a reset of the scsi bus eh until it finally gives up and drops to a terminal. A while after the system goes berserk with messages of non responding scsi bus. As I cannot reach my harddisk, is there a way to find out what is wrong? Why does everything work fine up to and including kernel 27 and starts to malfunction after that? Did the Areca software change in some way? P.S. When I start kernel version 3.8.0-19, everything works fine. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubuntu-release-upgrader-core 1:0.192.13 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CrashDB: ubuntu Date: Wed Oct 9 14:53:03 2013 InstallationDate: Installed on 2013-10-07 (1 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130423.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1237392] Re: kernels following version 3.8.0-27 do not start
Well: it works! The kernel start, I can logon, and do stuff!! Very encouraging. Let me know when you have the next kernel to do according to the bisect. And thank you for your effort -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1237392 Title: kernels following version 3.8.0-27 do not start Status in “linux” package in Ubuntu: Confirmed Bug description: All kernel updates on ubuntu following kernel 3.8.0-27 result in an empty screen with no indication of startup, no response to the keyboard. I can only start up using kernel version 3.8.0-27-generic. All following numbers (up to and including 3.8.0-31-generic) do not result in a running system. Also, the display no message at all when starting up (after grub). I checked the logfiles with grep -n Linux version 3.8.0- * and found only 27 to be logged, nothing for the other kernels. I am at a loss how to continue. I am running the most recent version of Ubuntu server. Two days ago I reinstalled Ubuntu with essentially the same result. The installation kernel version 3.8.0-19 works fine. The updated kernel 3.8.0-31 does not work. The following is the situation: When I let the machine start on itself I get no output at all. When I manually tell ubuntu to start the most recent kernel, I get 2 lines: Loading Linux-3.8.0-31-generic ... Loading initial ramdisk ... that's it. When I manually start the recovery kernel, I get a lot of information. Finally it drops to a terminal and indicates it could not load the LVM partition /dev/mapper/Server-Root. This is why I never see any result in my message or dmesg on disk. The problem seems to be with the Areca Raid controller. It does a reset of the scsi bus eh until it finally gives up and drops to a terminal. A while after the system goes berserk with messages of non responding scsi bus. As I cannot reach my harddisk, is there a way to find out what is wrong? Why does everything work fine up to and including kernel 27 and starts to malfunction after that? Did the Areca software change in some way? P.S. When I start kernel version 3.8.0-19, everything works fine. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubuntu-release-upgrader-core 1:0.192.13 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CrashDB: ubuntu Date: Wed Oct 9 14:53:03 2013 InstallationDate: Installed on 2013-10-07 (1 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130423.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1237392] Re: kernels following version 3.8.0-27 do not start
I must choose my words more carefully: I did dpkg -i *.deb (without the header file this time). It did not work for this kernel. Before I compile a new kernel, I remove the old one. Let me know. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1237392 Title: kernels following version 3.8.0-27 do not start Status in “linux” package in Ubuntu: Confirmed Bug description: All kernel updates on ubuntu following kernel 3.8.0-27 result in an empty screen with no indication of startup, no response to the keyboard. I can only start up using kernel version 3.8.0-27-generic. All following numbers (up to and including 3.8.0-31-generic) do not result in a running system. Also, the display no message at all when starting up (after grub). I checked the logfiles with grep -n Linux version 3.8.0- * and found only 27 to be logged, nothing for the other kernels. I am at a loss how to continue. I am running the most recent version of Ubuntu server. Two days ago I reinstalled Ubuntu with essentially the same result. The installation kernel version 3.8.0-19 works fine. The updated kernel 3.8.0-31 does not work. The following is the situation: When I let the machine start on itself I get no output at all. When I manually tell ubuntu to start the most recent kernel, I get 2 lines: Loading Linux-3.8.0-31-generic ... Loading initial ramdisk ... that's it. When I manually start the recovery kernel, I get a lot of information. Finally it drops to a terminal and indicates it could not load the LVM partition /dev/mapper/Server-Root. This is why I never see any result in my message or dmesg on disk. The problem seems to be with the Areca Raid controller. It does a reset of the scsi bus eh until it finally gives up and drops to a terminal. A while after the system goes berserk with messages of non responding scsi bus. As I cannot reach my harddisk, is there a way to find out what is wrong? Why does everything work fine up to and including kernel 27 and starts to malfunction after that? Did the Areca software change in some way? P.S. When I start kernel version 3.8.0-19, everything works fine. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubuntu-release-upgrader-core 1:0.192.13 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CrashDB: ubuntu Date: Wed Oct 9 14:53:03 2013 InstallationDate: Installed on 2013-10-07 (1 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130423.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1237392] Re: kernels following version 3.8.0-27 do not start
Sorry, said compile again: mean dpkg -i. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1237392 Title: kernels following version 3.8.0-27 do not start Status in “linux” package in Ubuntu: Confirmed Bug description: All kernel updates on ubuntu following kernel 3.8.0-27 result in an empty screen with no indication of startup, no response to the keyboard. I can only start up using kernel version 3.8.0-27-generic. All following numbers (up to and including 3.8.0-31-generic) do not result in a running system. Also, the display no message at all when starting up (after grub). I checked the logfiles with grep -n Linux version 3.8.0- * and found only 27 to be logged, nothing for the other kernels. I am at a loss how to continue. I am running the most recent version of Ubuntu server. Two days ago I reinstalled Ubuntu with essentially the same result. The installation kernel version 3.8.0-19 works fine. The updated kernel 3.8.0-31 does not work. The following is the situation: When I let the machine start on itself I get no output at all. When I manually tell ubuntu to start the most recent kernel, I get 2 lines: Loading Linux-3.8.0-31-generic ... Loading initial ramdisk ... that's it. When I manually start the recovery kernel, I get a lot of information. Finally it drops to a terminal and indicates it could not load the LVM partition /dev/mapper/Server-Root. This is why I never see any result in my message or dmesg on disk. The problem seems to be with the Areca Raid controller. It does a reset of the scsi bus eh until it finally gives up and drops to a terminal. A while after the system goes berserk with messages of non responding scsi bus. As I cannot reach my harddisk, is there a way to find out what is wrong? Why does everything work fine up to and including kernel 27 and starts to malfunction after that? Did the Areca software change in some way? P.S. When I start kernel version 3.8.0-19, everything works fine. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubuntu-release-upgrader-core 1:0.192.13 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CrashDB: ubuntu Date: Wed Oct 9 14:53:03 2013 InstallationDate: Installed on 2013-10-07 (1 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130423.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1237392] Re: kernels following version 3.8.0-27 do not start
Not sure what went wrong. First I compiled the kernel, and I saw that the name was the same as an existing kernel. It didnt work, same error. However, to be sure I uninstalled all the handmade kernels using synaptic and now I cannot compile the kernel. Also, I am missing one deb if I compare with the other kernels: they all had 3 files: 2 header files (one AMD64, one all) and one kernel image. The error message I get is simply : Errors were encountered while processing: linux-headers-3.8.13-03081304-generic Do I need the 3rd header file? I want to be sure it is indeed not working using this kernel, because as 4 works, it would be weird if this one doesn't (would mean this patch is to blame I guess). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1237392 Title: kernels following version 3.8.0-27 do not start Status in “linux” package in Ubuntu: Confirmed Bug description: All kernel updates on ubuntu following kernel 3.8.0-27 result in an empty screen with no indication of startup, no response to the keyboard. I can only start up using kernel version 3.8.0-27-generic. All following numbers (up to and including 3.8.0-31-generic) do not result in a running system. Also, the display no message at all when starting up (after grub). I checked the logfiles with grep -n Linux version 3.8.0- * and found only 27 to be logged, nothing for the other kernels. I am at a loss how to continue. I am running the most recent version of Ubuntu server. Two days ago I reinstalled Ubuntu with essentially the same result. The installation kernel version 3.8.0-19 works fine. The updated kernel 3.8.0-31 does not work. The following is the situation: When I let the machine start on itself I get no output at all. When I manually tell ubuntu to start the most recent kernel, I get 2 lines: Loading Linux-3.8.0-31-generic ... Loading initial ramdisk ... that's it. When I manually start the recovery kernel, I get a lot of information. Finally it drops to a terminal and indicates it could not load the LVM partition /dev/mapper/Server-Root. This is why I never see any result in my message or dmesg on disk. The problem seems to be with the Areca Raid controller. It does a reset of the scsi bus eh until it finally gives up and drops to a terminal. A while after the system goes berserk with messages of non responding scsi bus. As I cannot reach my harddisk, is there a way to find out what is wrong? Why does everything work fine up to and including kernel 27 and starts to malfunction after that? Did the Areca software change in some way? P.S. When I start kernel version 3.8.0-19, everything works fine. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubuntu-release-upgrader-core 1:0.192.13 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CrashDB: ubuntu Date: Wed Oct 9 14:53:03 2013 InstallationDate: Installed on 2013-10-07 (1 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130423.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1237392] Re: kernels following version 3.8.0-27 do not start
thanks, did that. The kernel does not work. It displays the same problems. Does that mean this is the offending patch? Do we need more installs to find the commit that did it? Let me know. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1237392 Title: kernels following version 3.8.0-27 do not start Status in “linux” package in Ubuntu: Confirmed Bug description: All kernel updates on ubuntu following kernel 3.8.0-27 result in an empty screen with no indication of startup, no response to the keyboard. I can only start up using kernel version 3.8.0-27-generic. All following numbers (up to and including 3.8.0-31-generic) do not result in a running system. Also, the display no message at all when starting up (after grub). I checked the logfiles with grep -n Linux version 3.8.0- * and found only 27 to be logged, nothing for the other kernels. I am at a loss how to continue. I am running the most recent version of Ubuntu server. Two days ago I reinstalled Ubuntu with essentially the same result. The installation kernel version 3.8.0-19 works fine. The updated kernel 3.8.0-31 does not work. The following is the situation: When I let the machine start on itself I get no output at all. When I manually tell ubuntu to start the most recent kernel, I get 2 lines: Loading Linux-3.8.0-31-generic ... Loading initial ramdisk ... that's it. When I manually start the recovery kernel, I get a lot of information. Finally it drops to a terminal and indicates it could not load the LVM partition /dev/mapper/Server-Root. This is why I never see any result in my message or dmesg on disk. The problem seems to be with the Areca Raid controller. It does a reset of the scsi bus eh until it finally gives up and drops to a terminal. A while after the system goes berserk with messages of non responding scsi bus. As I cannot reach my harddisk, is there a way to find out what is wrong? Why does everything work fine up to and including kernel 27 and starts to malfunction after that? Did the Areca software change in some way? P.S. When I start kernel version 3.8.0-19, everything works fine. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubuntu-release-upgrader-core 1:0.192.13 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CrashDB: ubuntu Date: Wed Oct 9 14:53:03 2013 InstallationDate: Installed on 2013-10-07 (1 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130423.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1237392] Re: kernels following version 3.8.0-27 do not start
Right. Done that. Not sure how you got to these 2 kernels, but you are absolutely right! 3.8.13.4 works: just booted, logged on and rebooted. No problem there. 3.8.13.5 had the same symptoms as the non-working kernels. i checked with the recovery kernel and got largely the same output. It had the same problem. So, what do we do now? ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1237392 Title: kernels following version 3.8.0-27 do not start Status in “linux” package in Ubuntu: Confirmed Bug description: All kernel updates on ubuntu following kernel 3.8.0-27 result in an empty screen with no indication of startup, no response to the keyboard. I can only start up using kernel version 3.8.0-27-generic. All following numbers (up to and including 3.8.0-31-generic) do not result in a running system. Also, the display no message at all when starting up (after grub). I checked the logfiles with grep -n Linux version 3.8.0- * and found only 27 to be logged, nothing for the other kernels. I am at a loss how to continue. I am running the most recent version of Ubuntu server. Two days ago I reinstalled Ubuntu with essentially the same result. The installation kernel version 3.8.0-19 works fine. The updated kernel 3.8.0-31 does not work. The following is the situation: When I let the machine start on itself I get no output at all. When I manually tell ubuntu to start the most recent kernel, I get 2 lines: Loading Linux-3.8.0-31-generic ... Loading initial ramdisk ... that's it. When I manually start the recovery kernel, I get a lot of information. Finally it drops to a terminal and indicates it could not load the LVM partition /dev/mapper/Server-Root. This is why I never see any result in my message or dmesg on disk. The problem seems to be with the Areca Raid controller. It does a reset of the scsi bus eh until it finally gives up and drops to a terminal. A while after the system goes berserk with messages of non responding scsi bus. As I cannot reach my harddisk, is there a way to find out what is wrong? Why does everything work fine up to and including kernel 27 and starts to malfunction after that? Did the Areca software change in some way? P.S. When I start kernel version 3.8.0-19, everything works fine. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubuntu-release-upgrader-core 1:0.192.13 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CrashDB: ubuntu Date: Wed Oct 9 14:53:03 2013 InstallationDate: Installed on 2013-10-07 (1 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130423.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1237392] Re: kernels following version 3.8.0-27 do not start
I installed the kernel, but it shows the same errors. Weird though, if this is the only commit related to Areca Raid Controller. What I notice is that the messages are mostly from arcmsr2 like: arcmsr2: executing hw bus reset and arcmsr: scsi bus reset eh returns with success and also: Areca Raid Controller2: F/W v1.46 ...(etc)... Could the problem be a different patch / commit as the driver names differ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1237392 Title: kernels following version 3.8.0-27 do not start Status in “linux” package in Ubuntu: Confirmed Bug description: All kernel updates on ubuntu following kernel 3.8.0-27 result in an empty screen with no indication of startup, no response to the keyboard. I can only start up using kernel version 3.8.0-27-generic. All following numbers (up to and including 3.8.0-31-generic) do not result in a running system. Also, the display no message at all when starting up (after grub). I checked the logfiles with grep -n Linux version 3.8.0- * and found only 27 to be logged, nothing for the other kernels. I am at a loss how to continue. I am running the most recent version of Ubuntu server. Two days ago I reinstalled Ubuntu with essentially the same result. The installation kernel version 3.8.0-19 works fine. The updated kernel 3.8.0-31 does not work. The following is the situation: When I let the machine start on itself I get no output at all. When I manually tell ubuntu to start the most recent kernel, I get 2 lines: Loading Linux-3.8.0-31-generic ... Loading initial ramdisk ... that's it. When I manually start the recovery kernel, I get a lot of information. Finally it drops to a terminal and indicates it could not load the LVM partition /dev/mapper/Server-Root. This is why I never see any result in my message or dmesg on disk. The problem seems to be with the Areca Raid controller. It does a reset of the scsi bus eh until it finally gives up and drops to a terminal. A while after the system goes berserk with messages of non responding scsi bus. As I cannot reach my harddisk, is there a way to find out what is wrong? Why does everything work fine up to and including kernel 27 and starts to malfunction after that? Did the Areca software change in some way? P.S. When I start kernel version 3.8.0-19, everything works fine. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubuntu-release-upgrader-core 1:0.192.13 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CrashDB: ubuntu Date: Wed Oct 9 14:53:03 2013 InstallationDate: Installed on 2013-10-07 (1 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130423.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1237392] Re: kernels following version 3.8.0-27 do not start
As stated, using the recovery kernel, I drop to a terminal. The prompt
is {initramfs} and does not contain the program apport-collect. It is
not possible to run this command.
I am sorry. Will set the status to Confirmed as requested by the
previous note.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1237392
Title:
kernels following version 3.8.0-27 do not start
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
All kernel updates on ubuntu following kernel 3.8.0-27 result in an
empty screen with no indication of startup, no response to the
keyboard. I can only start up using kernel version 3.8.0-27-generic.
All following numbers (up to and including 3.8.0-31-generic) do not
result in a running system. Also, the display no message at all when
starting up (after grub).
I checked the logfiles with grep -n Linux version 3.8.0- * and
found only 27 to be logged, nothing for the other kernels. I am at a
loss how to continue.
I am running the most recent version of Ubuntu server.
Two days ago I reinstalled Ubuntu with essentially the same result.
The installation kernel version 3.8.0-19 works fine. The updated
kernel 3.8.0-31 does not work.
The following is the situation:
When I let the machine start on itself I get no output at all.
When I manually tell ubuntu to start the most recent kernel, I get 2
lines:
Loading Linux-3.8.0-31-generic ... Loading initial ramdisk ...
that's it.
When I manually start the recovery kernel, I get a lot of
information. Finally it drops to a terminal and indicates it could not
load the LVM partition /dev/mapper/Server-Root. This is why I never
see any result in my message or dmesg on disk.
The problem seems to be with the Areca Raid controller. It does a
reset of the scsi bus eh until it finally gives up and drops to a
terminal. A while after the system goes berserk with messages of non
responding scsi bus.
As I cannot reach my harddisk, is there a way to find out what is
wrong? Why does everything work fine up to and including kernel 27 and
starts to malfunction after that? Did the Areca software change in
some way?
P.S. When I start kernel version 3.8.0-19, everything works fine.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: ubuntu-release-upgrader-core 1:0.192.13
ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
CrashDB: ubuntu
Date: Wed Oct 9 14:53:03 2013
InstallationDate: Installed on 2013-10-07 (1 days ago)
InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64
(20130423.1)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237392/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
