[Kernel-packages] [Bug 1209503] [NEW] [Acer Extensa 5220] suspend/resume failure
Public bug reported: After boot it's appeared.. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.10.0-6-generic 3.10.0-6.17 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bogdan 1776 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) Date: Tue Aug 6 12:27:33 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=29645983-b508-4fa3-95df-26be802a8c59 InstallationDate: Installed on 2013-08-04 (3 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130804) InterpreterPath: /usr/bin/python3.3 MachineType: Acer Extensa 5220 MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=c92f5314-e9e0-4c87-a6bb-c478701a0127 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware1.113 SourcePackage: linux Title: [Acer Extensa 5220] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 07/03/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.35 dmi.board.name: Columbia dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.asset.tag: None dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Extensa 5220 dmi.product.version: 0100 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops i386 resume saucy suspend -- 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/1209503 Title: [Acer Extensa 5220] suspend/resume failure Status in “linux” package in Ubuntu: New Bug description: After boot it's appeared.. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.10.0-6-generic 3.10.0-6.17 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bogdan 1776 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) Date: Tue Aug 6 12:27:33 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=29645983-b508-4fa3-95df-26be802a8c59 InstallationDate: Installed on 2013-08-04 (3 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130804) InterpreterPath: /usr/bin/python3.3 MachineType: Acer Extensa 5220 MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=c92f5314-e9e0-4c87-a6bb-c478701a0127 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware1.113 SourcePackage: linux Title: [Acer Extensa 5220] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 07/03/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.35 dmi.board.name: Columbia dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.asset.tag: None dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Extensa
[Kernel-packages] [Bug 1144322] Re: [Toshiba Satellite A80] Kernel 3.8.x Panic when disconnecting from network manager via ppp0
Also, I did test several mainline kernels and test kernels as you can see from the previous comments and I don't think that this bug has been resolved, people aren't complaining as not many connect to the internet using the mobile phone modem over bluetooth. ** 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/1144322 Title: [Toshiba Satellite A80] Kernel 3.8.x Panic when disconnecting from network manager via ppp0 Status in “linux” package in Ubuntu: Confirmed Status in “linux” package in Arch Linux: New Status in Gentoo Linux: New Bug description: Using: Ubuntu 12.04 (precise) 32-bit Machine: Laptop / old Toshiba / Celeron processor Installing Kernel from: http://kernel.ubuntu.com/~kernel-ppa/mainline/; Apport disabled and uninstalled, so can't provide debug/log details (this to make the machine run a bit faster, have been doing so since 10.04). Have no problem with Kernel upto 3.7.10 (have been upgrading to Kernel 3.5/3.6/3.7/3.8, when ever new builds are available) But when using Kernel 3.8.0/3.8.1/3.8.2, get Kernel Panic machine crashes freezes, have to hard boot. Machine connects to net using ppp0 (modem on phone), then if you disconnect the modem ppp0 try to reconnect, the Kernel Panics crashes, or then if you disconnect by unchecking Enable Networking then rechecking Enable Networking, the Kernel Panics crashes. First faced this problem with Kernel 3.8.0 so went back to using 3.7.9, then same story repeated with Kernel 3.8.1 3.8.2, currently using Kernel 3.7.10. Think there is some REGRESSION in Kernel 3.8 below details are provided using HardInfo 0.5.1 : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322/+attachment/3761201/+files/hardinfo --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1880 F pulseaudio /dev/snd/seq:timidity 1424 F timidity Card0.Amixer.info: Card hw:0 'ICH6'/'Intel ICH6 with ALC250 at irq 17' Mixer name : 'Realtek ALC250 rev 2' Components : 'AC97a:414c4752' Controls : 33 Simple ctrls : 21 DistroRelease: Ubuntu 12.04 MachineType: TOSHIBA Satellite A80 MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-51-generic-pae root=UUID=4dda5c0a-3583-45f5-b6c4-b5aef19935c8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.2.0-51.77-generic-pae 3.2.48 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/ubuntu not ours. No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.2.0-51-generic-pae N/A linux-backports-modules-3.2.0-51-generic-pae N/A linux-firmware1.79.6 Tags: precise Uname: Linux 3.2.0-51-generic-pae i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/25/2006 dmi.bios.vendor: TOSHIBA dmi.bios.version: V2.80 dmi.board.name: EAT10/EAT20 dmi.board.vendor: TOSHIBA dmi.board.version: Null dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV2.80:bd10/25/2006:svnTOSHIBA:pnSatelliteA80:pvrPSA80L-043003:rvnTOSHIBA:rnEAT10/EAT20:rvrNull:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite A80 dmi.product.version: PSA80L-043003 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322/+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 1209503] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New = 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/1209503 Title: [Acer Extensa 5220] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: After boot it's appeared.. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.10.0-6-generic 3.10.0-6.17 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bogdan 1776 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) Date: Tue Aug 6 12:27:33 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=29645983-b508-4fa3-95df-26be802a8c59 InstallationDate: Installed on 2013-08-04 (3 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130804) InterpreterPath: /usr/bin/python3.3 MachineType: Acer Extensa 5220 MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=c92f5314-e9e0-4c87-a6bb-c478701a0127 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware1.113 SourcePackage: linux Title: [Acer Extensa 5220] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 07/03/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.35 dmi.board.name: Columbia dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.asset.tag: None dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Extensa 5220 dmi.product.version: 0100 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1209503/+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 1203415] Re: package linux-image-3.8.0-26-generic 3.8.0-26.38 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
mehdi@MehdiRM-PC:~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-image-extra-3.8.0-21-generic linux-image-extra-3.8.0-22-generic linux-image-extra-3.8.0-27-generic 0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded. 4 not fully installed or removed. After this operation, 388 MB disk space will be freed. Do you want to continue [Y/n]? y (Reading database ... 303993 files and directories currently installed.) Removing linux-image-extra-3.8.0-21-generic ... Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.8.0-21-generic /boot/vmlinuz-3.8.0-21-generic /etc/kernel/postrm.d/initramfs-tools: 33: /etc/kernel/postrm.d/initramfs-tools: update-initramfs: not found run-parts: /etc/kernel/postrm.d/initramfs-tools exited with return code 127 Failed to process /etc/kernel/postrm.d at /var/lib/dpkg/info/linux-image-extra-3.8.0-21-generic.postrm line 328. dpkg: error processing linux-image-extra-3.8.0-21-generic (--remove): subprocess installed post-removal script returned error exit status 1 No apport report written because MaxReports is reached already Removing linux-image-extra-3.8.0-22-generic ... Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.8.0-22-generic /boot/vmlinuz-3.8.0-22-generic /etc/kernel/postrm.d/initramfs-tools: 33: /etc/kernel/postrm.d/initramfs-tools: update-initramfs: not found run-parts: /etc/kernel/postrm.d/initramfs-tools exited with return code 127 Failed to process /etc/kernel/postrm.d at /var/lib/dpkg/info/linux-image-extra-3.8.0-22-generic.postrm line 328. dpkg: error processing linux-image-extra-3.8.0-22-generic (--remove): subprocess installed post-removal script returned error exit status 1 No apport report written because MaxReports is reached already Removing linux-image-extra-3.8.0-27-generic ... Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.8.0-27-generic /boot/vmlinuz-3.8.0-27-generic /etc/kernel/postrm.d/initramfs-tools: 33: /etc/kernel/postrm.d/initramfs-tools: update-initramfs: not found run-parts: /etc/kernel/postrm.d/initramfs-tools exited with return code 127 Failed to process /etc/kernel/postrm.d at /var/lib/dpkg/info/linux-image-extra-3.8.0-27-generic.postrm line 328. dpkg: error processing linux-image-extra-3.8.0-27-generic (--remove): subprocess installed post-removal script returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: linux-image-extra-3.8.0-21-generic linux-image-extra-3.8.0-22-generic linux-image-extra-3.8.0-27-generic E: Sub-process /usr/bin/dpkg returned an error code (1) -- 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/1203415 Title: package linux-image-3.8.0-26-generic 3.8.0-26.38 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in “linux” package in Ubuntu: Confirmed Bug description: errorr during upgrading 12.10 to 13.04 ProblemType: Package DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-26-generic ProcVersionSignature: Ubuntu 3.5.0-36.57-generic 3.5.7.14 Uname: Linux 3.5.0-36-generic i686 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: balqis 2283 F pulseaudio CRDA: country GB: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS Date: Sun Jul 21 01:35:43 2013 DuplicateSignature: package:linux-image-3.8.0-26-generic:3.8.0-26.38:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=0cc2e41b-310b-42a3-ac23-1c8550cd0198 InstallationDate: Installed on 2013-02-22 (148 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MachineType: Dell Inc. Inspiron 1525 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-36-generic root=UUID=64a3f902-f9b1-4075-b621-1e91fe4a8e85 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.00-13ubuntu3 SourcePackage: linux Title: package linux-image-3.8.0-26-generic 3.8.0-26.38
[Kernel-packages] [Bug 1210018] Re: Hauppauge NOVA-T500 card does not with Ubuntu on VIA EPIA12000EG motherboard
apport report ** Attachment added: apport-bug.report https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210018/+attachment/3764516/+files/apport-bug.report -- 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/1210018 Title: Hauppauge NOVA-T500 card does not with Ubuntu on VIA EPIA12000EG motherboard Status in “linux” package in Ubuntu: New Bug description: I have VIA EPIA12000EG motherboard and Hauppauge NOVA-T500 dual DVB-T tuner PCI card. Internally the NOVA-T500 card has two USB tuners connected to an internal USB hub. For some reason Ubuntu kernel identifies the USB hub as USB1.1 hub when it is USB2.0 hub. The DVB-T cards refuse to work with USB1.1 hub and become inoperable. I have Debian on another disk on the same machine, and Debian kernel (and also Fedora kernel) correctly identifies the USB hub and the tuner cards work. I have also installed Debian kernel package to the Ubuntu system, and if I boot to debian kernel in my Ubuntu system, then the cards work. For some reason ubuntu-bug refuses to work on this machine and I also cannot attach files (in both cases the upload freeses and times out), so I will try to attach apport file from other computer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210018/+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 1210018] [NEW] Hauppauge NOVA-T500 card does not with Ubuntu on VIA EPIA12000EG motherboard
Public bug reported: I have VIA EPIA12000EG motherboard and Hauppauge NOVA-T500 dual DVB-T tuner PCI card. Internally the NOVA-T500 card has two USB tuners connected to an internal USB hub. For some reason Ubuntu kernel identifies the USB hub as USB1.1 hub when it is USB2.0 hub. The DVB-T cards refuse to work with USB1.1 hub and become inoperable. I have Debian on another disk on the same machine, and Debian kernel (and also Fedora kernel) correctly identifies the USB hub and the tuner cards work. I have also installed Debian kernel package to the Ubuntu system, and if I boot to debian kernel in my Ubuntu system, then the cards work. For some reason ubuntu-bug refuses to work on this machine and I also cannot attach files (in both cases the upload freeses and times out), so I will try to attach apport file from other computer. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1210018 Title: Hauppauge NOVA-T500 card does not with Ubuntu on VIA EPIA12000EG motherboard Status in “linux” package in Ubuntu: New Bug description: I have VIA EPIA12000EG motherboard and Hauppauge NOVA-T500 dual DVB-T tuner PCI card. Internally the NOVA-T500 card has two USB tuners connected to an internal USB hub. For some reason Ubuntu kernel identifies the USB hub as USB1.1 hub when it is USB2.0 hub. The DVB-T cards refuse to work with USB1.1 hub and become inoperable. I have Debian on another disk on the same machine, and Debian kernel (and also Fedora kernel) correctly identifies the USB hub and the tuner cards work. I have also installed Debian kernel package to the Ubuntu system, and if I boot to debian kernel in my Ubuntu system, then the cards work. For some reason ubuntu-bug refuses to work on this machine and I also cannot attach files (in both cases the upload freeses and times out), so I will try to attach apport file from other computer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210018/+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 1210018] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1210018 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New = Incomplete -- 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/1210018 Title: Hauppauge NOVA-T500 card does not with Ubuntu on VIA EPIA12000EG motherboard Status in “linux” package in Ubuntu: Incomplete Bug description: I have VIA EPIA12000EG motherboard and Hauppauge NOVA-T500 dual DVB-T tuner PCI card. Internally the NOVA-T500 card has two USB tuners connected to an internal USB hub. For some reason Ubuntu kernel identifies the USB hub as USB1.1 hub when it is USB2.0 hub. The DVB-T cards refuse to work with USB1.1 hub and become inoperable. I have Debian on another disk on the same machine, and Debian kernel (and also Fedora kernel) correctly identifies the USB hub and the tuner cards work. I have also installed Debian kernel package to the Ubuntu system, and if I boot to debian kernel in my Ubuntu system, then the cards work. For some reason ubuntu-bug refuses to work on this machine and I also cannot attach files (in both cases the upload freeses and times out), so I will try to attach apport file from other computer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210018/+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 1210026] Re: CVE-2013-4205
CVE-2013-4205 ** Also affects: linux (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-ec2 (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-mvl-dove (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-ti-omap4 (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Precise) Status: New = Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Saucy) Status: New = Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-fsl-imx51 (Ubuntu Raring) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-raring (Ubuntu Saucy) Status: New = Invalid **
[Kernel-packages] [Bug 1173725] Re: [Acer Aspire V5-171] Backlight cannot be adjusted unless passing acpi_backlight=vendor
That is, I'm hoping the brightness keys will work (e.g. under KDE) when using the commit ACPI / video / i915: No ACPI backlight if firmware expects Windows 8. With the non-working acpi_backlight removed, KDE would use the working intel_backlight instead. -- 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/1173725 Title: [Acer Aspire V5-171] Backlight cannot be adjusted unless passing acpi_backlight=vendor Status in “linux” package in Ubuntu: Incomplete Bug description: The boot parameter is suggested as a fix for this model by http://www.linlap.com/acer_aspire_v5-171 (so if it would help, I would suggest classing this bug as confirmed). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.29 [modified: boot/vmlinuz-3.8.0-19-generic] ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alan 1919 F pulseaudio Date: Sat Apr 27 19:59:23 2013 InstallationDate: Installed on 2013-04-27 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer V5-171 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic.efi.signed root=UUID=ad03cbd3-39e0-4f7e-b0ab-e1ef3abaa88e ro acpi_backlight=vendor quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.04 dmi.modalias: dmi:bvnAcer:bvrV2.04:bd09/14/2012:svnAcer:pnV5-171:pvrV2.04:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.04: dmi.product.name: V5-171 dmi.product.version: V2.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1173725/+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 1173725] Re: [Acer Aspire V5-171] Backlight cannot be adjusted unless passing acpi_backlight=vendor
Sorry I've been neglecting this (and my original report may have fluffed the detail). This is Windows 8 hardware. Manually poking the intel_backlight driver in sysfs (echo 100 | sudo tee /sys/class/intel_backlight/brightness) works fine. So for now I'm assuming the problem is what's referred to here: http://permalink.gmane.org/gmane.linux.kernel.commits.head/396675 (I first saw this referred to when it was reverted in 3.11-rc3. Linus' release announcement says But never fear, we have top people looking at it). That should be nice easy to test compared to the _other_ bug I'm tracking on this laptop. So I'll see if I can get there feedback to upstream. -- 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/1173725 Title: [Acer Aspire V5-171] Backlight cannot be adjusted unless passing acpi_backlight=vendor Status in “linux” package in Ubuntu: Incomplete Bug description: The boot parameter is suggested as a fix for this model by http://www.linlap.com/acer_aspire_v5-171 (so if it would help, I would suggest classing this bug as confirmed). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.29 [modified: boot/vmlinuz-3.8.0-19-generic] ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alan 1919 F pulseaudio Date: Sat Apr 27 19:59:23 2013 InstallationDate: Installed on 2013-04-27 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer V5-171 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic.efi.signed root=UUID=ad03cbd3-39e0-4f7e-b0ab-e1ef3abaa88e ro acpi_backlight=vendor quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.04 dmi.modalias: dmi:bvnAcer:bvrV2.04:bd09/14/2012:svnAcer:pnV5-171:pvrV2.04:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.04: dmi.product.name: V5-171 dmi.product.version: V2.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1173725/+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 1099098] Re: Mainline Kernel 3.8.0 , black screen after boot with acer v3-771g
yes , I have the same problem . -- 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/1099098 Title: Mainline Kernel 3.8.0 , black screen after boot with acer v3-771g Status in “linux” package in Ubuntu: Expired Bug description: Hello, the problem only occurs with kernel 3.8.0. After installing mainline kernel 3.8.0, i get immediately after boot a black screen ( display turns off ). The problem also occurs with the ubuntu- livecd 13.04 daily (with kernel 3.8.0). Ubuntu 13.04 daily cd work with kernel 3.7 without problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1099098/+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 1173725] Re: [Acer Aspire V5-171] Backlight cannot be adjusted unless passing acpi_backlight=vendor
** Bug watch added: Linux Kernel Bug Tracker #51231 http://bugzilla.kernel.org/show_bug.cgi?id=51231 ** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=51231 Importance: Unknown Status: Unknown -- 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/1173725 Title: [Acer Aspire V5-171] Backlight cannot be adjusted unless passing acpi_backlight=vendor Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Incomplete Bug description: The boot parameter is suggested as a fix for this model by http://www.linlap.com/acer_aspire_v5-171 (so if it would help, I would suggest classing this bug as confirmed). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.29 [modified: boot/vmlinuz-3.8.0-19-generic] ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alan 1919 F pulseaudio Date: Sat Apr 27 19:59:23 2013 InstallationDate: Installed on 2013-04-27 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer V5-171 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic.efi.signed root=UUID=ad03cbd3-39e0-4f7e-b0ab-e1ef3abaa88e ro acpi_backlight=vendor quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.04 dmi.modalias: dmi:bvnAcer:bvrV2.04:bd09/14/2012:svnAcer:pnV5-171:pvrV2.04:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.04: dmi.product.name: V5-171 dmi.product.version: V2.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1173725/+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 751689] Re: ThinkPads overheat due to slow fans when on 'auto'
Updating the BIOS on my X201s seems to have reduced the system temperature. Not sure why since the changelog for 1.40-1.15 only says Embedded Controller update will modify battery charge algorithms to balance battery charging and lifespan. http://support.lenovo.com/en_US/detail.page?LegacyDocID=MIGR-74983 -- 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/751689 Title: ThinkPads overheat due to slow fans when on 'auto' Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Maverick: Won't Fix Status in “linux” source package in Natty: Won't Fix Status in “linux” source package in Precise: Confirmed Status in “thinkfan” package in Debian: Fix Released Status in “linux” package in Fedora: Unknown Bug description: On my Thinkpad x201s with an i7, if I utilize all of the CPUs/hyperthreads, the machine can be made to overheat very quickly. This is because of the default level setting of 'auto' in /proc/acpi/ibm/fan. On 'auto', the fan only ever goes up to around 4500rpm, while in 'disengaged' mode it can go as high as 6400rpm. At 4500rpm, the CPU continues to climb until the system is forcibly shutdown at 100C. If I reload thinkpad_acpi like so: $ sudo rmmod thinkpad_acpi $ sudo modprobe thinkpad_acpi fan_control=1 Then I can set the fan to disengaged mode manually: echo level disengaged /proc/acpi/ibm/fan With this setting, I can utilize all of the CPUs for an extended time and not surpass 85C, still pretty hot but well under the 100C range. Furthermore, setting to level '7' (the supposed max fan speed) runs the fan at ~5300, well below the maximum fan speed. In maverick this did not seem to be as much of a problem (perhaps because of the lack of the big kernel lock in natty?). Related bugs: https://bugzilla.redhat.com/show_bug.cgi?id=675433 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610722 (against thinkfan package, but demonstrates that other x201 users are having the same problem) ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.38-7-generic 2.6.38-7.39 Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic x86_64 AcpiTables: Error: command ['gksu', '-D', 'Apport', '--', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 1: GNOME_SUDO_PASS Sorry, try again. sudo: 3 incorrect password attempts AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jamie 2641 F pulseaudio /dev/snd/pcmC0D0p: jamie 2641 F...m pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf252 irq 43' Mixer name : 'Intel IbexPeak HDMI' Components : 'HDA:14f15069,17aa2156,00100302 HDA:80862804,17aa21b5,0010' Controls : 12 Simple ctrls : 6 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 6QHT28WW-1.09' Mixer name : 'ThinkPad EC 6QHT28WW-1.09' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Tue Apr 5 11:56:28 2011 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=58280e6e-d161-43ea-8593-a89fb7b6851a InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100427.1) MachineType: LENOVO 5129CTO ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-7-generic root=UUID=82571cfb-fdda-4d2f-b708-f8924aa0fe21 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-2.6.38-7-generic N/A linux-backports-modules-2.6.38-7-generic N/A linux-firmware1.49 SourcePackage: linux UpgradeStatus: Upgraded to natty on 2011-02-24 (39 days ago) dmi.bios.date: 04/20/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6QET44WW (1.14 ) dmi.board.name: 5129CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6QET44WW(1.14):bd04/20/2010:svnLENOVO:pn5129CTO:pvrThinkPadX201s:rvnLENOVO:rn5129CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 5129CTO dmi.product.version: ThinkPad X201s dmi.sys.vendor: LENOVO
[Kernel-packages] [Bug 1204604] Re: panic during boot – 3.8.0-26
apport information ** Tags added: apport-collected raring ** Description changed: Hi, I attached screenshots of the panic. on 13.04 during boot, somewhere during starting of /etc/init/ services kernel 3.8.0-19 and 3.8.0-26 panics. I made a quick search but didn't found a related report. Though I found a quick fix in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322 I installed 3.7.0 as mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322/comments/23 to keep on working. I can't use `ubuntu-bug linux` cause I can't boot with the panicing kernel. * Boot never succeeds * but sometimes it shows a panic trace * sometimes it flickers to black or to frozen mouse pointer like shown in vid.mp4 * once it showed a panic trace and after some seconds it printed even more screen filling stack trace, and when again even more Though I spotted panics with 3.8.0-19, I only did screenshots and multiple boots with 3.8.0-26. This is new, introduced since do-release-upgrade from 12.10 to 13.04 yesterday. Please contact me when I can provide more information. + --- + ApportVersion: 2.9.2-0ubuntu8 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: this 3156 F pulseaudio + CRDA: + country DE: + (2400 - 2483 @ 40), (N/A, 20) + (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR + (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS + (5470 - 5725 @ 40), (N/A, 26), DFS + CasperVersion: 1.331 + DistroRelease: Ubuntu 13.04 + LiveMediaBuild: This + MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/532U3C + MarkForUpload: True + Package: linux (not installed) + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: cdrom-detect/try-usb=true noprompt boot=casper floppy.allowed_drive_mask=0 ignore_uuid live-media-path=/multiboot/ubuntu130464/casper/ file=/multiboot/ubuntu130464/preseed/ubuntu.seed initrd=/multiboot/ubuntu130464/casper/initrd.lz splash -- BOOT_IMAGE=/multiboot/ubuntu130464/casper/vmlinuz.efi + ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 + RelatedPackageVersions: + linux-restricted-modules-3.8.0-19-generic N/A + linux-backports-modules-3.8.0-19-generic N/A + linux-firmware1.106 + Tags: raring + Uname: Linux 3.8.0-19-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + dmi.bios.date: 09/20/2012 + dmi.bios.vendor: Phoenix Technologies Ltd. + dmi.bios.version: P03ABH + dmi.board.asset.tag: Base Board Asset Tag + dmi.board.name: NP530U3C-A0MDE + dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. + dmi.board.version: FAB1 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 9 + dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. + dmi.chassis.version: 0.1 + dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03ABH:bd09/20/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C/532U3C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP530U3C-A0MDE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: + dmi.product.name: 530U3C/530U4C/532U3C + dmi.product.version: 0.1 + dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Attachment added: AlsaInfo.txt https://bugs.launchpad.net/bugs/1204604/+attachment/3764643/+files/AlsaInfo.txt -- 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/1204604 Title: panic during boot – 3.8.0-26 Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I attached screenshots of the panic. on 13.04 during boot, somewhere during starting of /etc/init/ services kernel 3.8.0-19 and 3.8.0-26 panics. I made a quick search but didn't found a related report. Though I found a quick fix in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322 I installed 3.7.0 as mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322/comments/23 to keep on working. I can't use `ubuntu-bug linux` cause I can't boot with the panicing kernel. * Boot never succeeds * but sometimes it shows a panic trace * sometimes it flickers to black or to frozen mouse pointer like shown in vid.mp4 * once it showed a panic trace and after some seconds it printed even more screen filling stack trace, and when again even more Though I spotted panics with 3.8.0-19, I only did screenshots and multiple boots with 3.8.0-26. This is new, introduced since do-release-upgrade from 12.10 to 13.04 yesterday. Please contact me when I can provide more information. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: this 3156 F pulseaudio CRDA: country DE: (2400 - 2483 @ 40),
[Kernel-packages] [Bug 1204604] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1204604/+attachment/3764648/+files/Lspci.txt -- 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/1204604 Title: panic during boot – 3.8.0-26 Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I attached screenshots of the panic. on 13.04 during boot, somewhere during starting of /etc/init/ services kernel 3.8.0-19 and 3.8.0-26 panics. I made a quick search but didn't found a related report. Though I found a quick fix in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322 I installed 3.7.0 as mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322/comments/23 to keep on working. I can't use `ubuntu-bug linux` cause I can't boot with the panicing kernel. * Boot never succeeds * but sometimes it shows a panic trace * sometimes it flickers to black or to frozen mouse pointer like shown in vid.mp4 * once it showed a panic trace and after some seconds it printed even more screen filling stack trace, and when again even more Though I spotted panics with 3.8.0-19, I only did screenshots and multiple boots with 3.8.0-26. This is new, introduced since do-release-upgrade from 12.10 to 13.04 yesterday. Please contact me when I can provide more information. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: this 3156 F pulseaudio CRDA: country DE: (2400 - 2483 @ 40), (N/A, 20) (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS (5470 - 5725 @ 40), (N/A, 26), DFS CasperVersion: 1.331 DistroRelease: Ubuntu 13.04 LiveMediaBuild: This MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/532U3C MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: cdrom-detect/try-usb=true noprompt boot=casper floppy.allowed_drive_mask=0 ignore_uuid live-media-path=/multiboot/ubuntu130464/casper/ file=/multiboot/ubuntu130464/preseed/ubuntu.seed initrd=/multiboot/ubuntu130464/casper/initrd.lz splash -- BOOT_IMAGE=/multiboot/ubuntu130464/casper/vmlinuz.efi ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/20/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03ABH dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP530U3C-A0MDE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03ABH:bd09/20/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C/532U3C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP530U3C-A0MDE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C/532U3C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1204604/+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 1204604] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/1204604/+attachment/3764647/+files/IwConfig.txt -- 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/1204604 Title: panic during boot – 3.8.0-26 Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I attached screenshots of the panic. on 13.04 during boot, somewhere during starting of /etc/init/ services kernel 3.8.0-19 and 3.8.0-26 panics. I made a quick search but didn't found a related report. Though I found a quick fix in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322 I installed 3.7.0 as mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322/comments/23 to keep on working. I can't use `ubuntu-bug linux` cause I can't boot with the panicing kernel. * Boot never succeeds * but sometimes it shows a panic trace * sometimes it flickers to black or to frozen mouse pointer like shown in vid.mp4 * once it showed a panic trace and after some seconds it printed even more screen filling stack trace, and when again even more Though I spotted panics with 3.8.0-19, I only did screenshots and multiple boots with 3.8.0-26. This is new, introduced since do-release-upgrade from 12.10 to 13.04 yesterday. Please contact me when I can provide more information. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: this 3156 F pulseaudio CRDA: country DE: (2400 - 2483 @ 40), (N/A, 20) (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS (5470 - 5725 @ 40), (N/A, 26), DFS CasperVersion: 1.331 DistroRelease: Ubuntu 13.04 LiveMediaBuild: This MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/532U3C MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: cdrom-detect/try-usb=true noprompt boot=casper floppy.allowed_drive_mask=0 ignore_uuid live-media-path=/multiboot/ubuntu130464/casper/ file=/multiboot/ubuntu130464/preseed/ubuntu.seed initrd=/multiboot/ubuntu130464/casper/initrd.lz splash -- BOOT_IMAGE=/multiboot/ubuntu130464/casper/vmlinuz.efi ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/20/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03ABH dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP530U3C-A0MDE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03ABH:bd09/20/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C/532U3C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP530U3C-A0MDE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C/532U3C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1204604/+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 1204604] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1204604/+attachment/3764649/+files/Lsusb.txt -- 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/1204604 Title: panic during boot – 3.8.0-26 Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I attached screenshots of the panic. on 13.04 during boot, somewhere during starting of /etc/init/ services kernel 3.8.0-19 and 3.8.0-26 panics. I made a quick search but didn't found a related report. Though I found a quick fix in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322 I installed 3.7.0 as mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322/comments/23 to keep on working. I can't use `ubuntu-bug linux` cause I can't boot with the panicing kernel. * Boot never succeeds * but sometimes it shows a panic trace * sometimes it flickers to black or to frozen mouse pointer like shown in vid.mp4 * once it showed a panic trace and after some seconds it printed even more screen filling stack trace, and when again even more Though I spotted panics with 3.8.0-19, I only did screenshots and multiple boots with 3.8.0-26. This is new, introduced since do-release-upgrade from 12.10 to 13.04 yesterday. Please contact me when I can provide more information. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: this 3156 F pulseaudio CRDA: country DE: (2400 - 2483 @ 40), (N/A, 20) (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS (5470 - 5725 @ 40), (N/A, 26), DFS CasperVersion: 1.331 DistroRelease: Ubuntu 13.04 LiveMediaBuild: This MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/532U3C MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: cdrom-detect/try-usb=true noprompt boot=casper floppy.allowed_drive_mask=0 ignore_uuid live-media-path=/multiboot/ubuntu130464/casper/ file=/multiboot/ubuntu130464/preseed/ubuntu.seed initrd=/multiboot/ubuntu130464/casper/initrd.lz splash -- BOOT_IMAGE=/multiboot/ubuntu130464/casper/vmlinuz.efi ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/20/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03ABH dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP530U3C-A0MDE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03ABH:bd09/20/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C/532U3C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP530U3C-A0MDE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C/532U3C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1204604/+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 1204604] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1204604/+attachment/3764644/+files/BootDmesg.txt -- 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/1204604 Title: panic during boot – 3.8.0-26 Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I attached screenshots of the panic. on 13.04 during boot, somewhere during starting of /etc/init/ services kernel 3.8.0-19 and 3.8.0-26 panics. I made a quick search but didn't found a related report. Though I found a quick fix in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322 I installed 3.7.0 as mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322/comments/23 to keep on working. I can't use `ubuntu-bug linux` cause I can't boot with the panicing kernel. * Boot never succeeds * but sometimes it shows a panic trace * sometimes it flickers to black or to frozen mouse pointer like shown in vid.mp4 * once it showed a panic trace and after some seconds it printed even more screen filling stack trace, and when again even more Though I spotted panics with 3.8.0-19, I only did screenshots and multiple boots with 3.8.0-26. This is new, introduced since do-release-upgrade from 12.10 to 13.04 yesterday. Please contact me when I can provide more information. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: this 3156 F pulseaudio CRDA: country DE: (2400 - 2483 @ 40), (N/A, 20) (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS (5470 - 5725 @ 40), (N/A, 26), DFS CasperVersion: 1.331 DistroRelease: Ubuntu 13.04 LiveMediaBuild: This MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/532U3C MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: cdrom-detect/try-usb=true noprompt boot=casper floppy.allowed_drive_mask=0 ignore_uuid live-media-path=/multiboot/ubuntu130464/casper/ file=/multiboot/ubuntu130464/preseed/ubuntu.seed initrd=/multiboot/ubuntu130464/casper/initrd.lz splash -- BOOT_IMAGE=/multiboot/ubuntu130464/casper/vmlinuz.efi ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/20/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03ABH dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP530U3C-A0MDE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03ABH:bd09/20/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C/532U3C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP530U3C-A0MDE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C/532U3C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1204604/+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 1204604] RfKill.txt
apport information ** Attachment added: RfKill.txt https://bugs.launchpad.net/bugs/1204604/+attachment/3764654/+files/RfKill.txt -- 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/1204604 Title: panic during boot – 3.8.0-26 Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I attached screenshots of the panic. on 13.04 during boot, somewhere during starting of /etc/init/ services kernel 3.8.0-19 and 3.8.0-26 panics. I made a quick search but didn't found a related report. Though I found a quick fix in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322 I installed 3.7.0 as mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322/comments/23 to keep on working. I can't use `ubuntu-bug linux` cause I can't boot with the panicing kernel. * Boot never succeeds * but sometimes it shows a panic trace * sometimes it flickers to black or to frozen mouse pointer like shown in vid.mp4 * once it showed a panic trace and after some seconds it printed even more screen filling stack trace, and when again even more Though I spotted panics with 3.8.0-19, I only did screenshots and multiple boots with 3.8.0-26. This is new, introduced since do-release-upgrade from 12.10 to 13.04 yesterday. Please contact me when I can provide more information. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: this 3156 F pulseaudio CRDA: country DE: (2400 - 2483 @ 40), (N/A, 20) (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS (5470 - 5725 @ 40), (N/A, 26), DFS CasperVersion: 1.331 DistroRelease: Ubuntu 13.04 LiveMediaBuild: This MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/532U3C MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: cdrom-detect/try-usb=true noprompt boot=casper floppy.allowed_drive_mask=0 ignore_uuid live-media-path=/multiboot/ubuntu130464/casper/ file=/multiboot/ubuntu130464/preseed/ubuntu.seed initrd=/multiboot/ubuntu130464/casper/initrd.lz splash -- BOOT_IMAGE=/multiboot/ubuntu130464/casper/vmlinuz.efi ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/20/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03ABH dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP530U3C-A0MDE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03ABH:bd09/20/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C/532U3C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP530U3C-A0MDE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C/532U3C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1204604/+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 1204604] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1204604/+attachment/3764650/+files/ProcCpuinfo.txt -- 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/1204604 Title: panic during boot – 3.8.0-26 Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I attached screenshots of the panic. on 13.04 during boot, somewhere during starting of /etc/init/ services kernel 3.8.0-19 and 3.8.0-26 panics. I made a quick search but didn't found a related report. Though I found a quick fix in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322 I installed 3.7.0 as mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322/comments/23 to keep on working. I can't use `ubuntu-bug linux` cause I can't boot with the panicing kernel. * Boot never succeeds * but sometimes it shows a panic trace * sometimes it flickers to black or to frozen mouse pointer like shown in vid.mp4 * once it showed a panic trace and after some seconds it printed even more screen filling stack trace, and when again even more Though I spotted panics with 3.8.0-19, I only did screenshots and multiple boots with 3.8.0-26. This is new, introduced since do-release-upgrade from 12.10 to 13.04 yesterday. Please contact me when I can provide more information. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: this 3156 F pulseaudio CRDA: country DE: (2400 - 2483 @ 40), (N/A, 20) (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS (5470 - 5725 @ 40), (N/A, 26), DFS CasperVersion: 1.331 DistroRelease: Ubuntu 13.04 LiveMediaBuild: This MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/532U3C MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: cdrom-detect/try-usb=true noprompt boot=casper floppy.allowed_drive_mask=0 ignore_uuid live-media-path=/multiboot/ubuntu130464/casper/ file=/multiboot/ubuntu130464/preseed/ubuntu.seed initrd=/multiboot/ubuntu130464/casper/initrd.lz splash -- BOOT_IMAGE=/multiboot/ubuntu130464/casper/vmlinuz.efi ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/20/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03ABH dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP530U3C-A0MDE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03ABH:bd09/20/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C/532U3C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP530U3C-A0MDE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C/532U3C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1204604/+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 1204604] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1204604/+attachment/3764652/+files/ProcModules.txt -- 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/1204604 Title: panic during boot – 3.8.0-26 Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I attached screenshots of the panic. on 13.04 during boot, somewhere during starting of /etc/init/ services kernel 3.8.0-19 and 3.8.0-26 panics. I made a quick search but didn't found a related report. Though I found a quick fix in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322 I installed 3.7.0 as mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322/comments/23 to keep on working. I can't use `ubuntu-bug linux` cause I can't boot with the panicing kernel. * Boot never succeeds * but sometimes it shows a panic trace * sometimes it flickers to black or to frozen mouse pointer like shown in vid.mp4 * once it showed a panic trace and after some seconds it printed even more screen filling stack trace, and when again even more Though I spotted panics with 3.8.0-19, I only did screenshots and multiple boots with 3.8.0-26. This is new, introduced since do-release-upgrade from 12.10 to 13.04 yesterday. Please contact me when I can provide more information. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: this 3156 F pulseaudio CRDA: country DE: (2400 - 2483 @ 40), (N/A, 20) (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS (5470 - 5725 @ 40), (N/A, 26), DFS CasperVersion: 1.331 DistroRelease: Ubuntu 13.04 LiveMediaBuild: This MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/532U3C MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: cdrom-detect/try-usb=true noprompt boot=casper floppy.allowed_drive_mask=0 ignore_uuid live-media-path=/multiboot/ubuntu130464/casper/ file=/multiboot/ubuntu130464/preseed/ubuntu.seed initrd=/multiboot/ubuntu130464/casper/initrd.lz splash -- BOOT_IMAGE=/multiboot/ubuntu130464/casper/vmlinuz.efi ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/20/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03ABH dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP530U3C-A0MDE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03ABH:bd09/20/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C/532U3C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP530U3C-A0MDE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C/532U3C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1204604/+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 1204604] HookError_cloud_archive.txt
apport information ** Attachment added: HookError_cloud_archive.txt https://bugs.launchpad.net/bugs/1204604/+attachment/3764646/+files/HookError_cloud_archive.txt -- 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/1204604 Title: panic during boot – 3.8.0-26 Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I attached screenshots of the panic. on 13.04 during boot, somewhere during starting of /etc/init/ services kernel 3.8.0-19 and 3.8.0-26 panics. I made a quick search but didn't found a related report. Though I found a quick fix in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322 I installed 3.7.0 as mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322/comments/23 to keep on working. I can't use `ubuntu-bug linux` cause I can't boot with the panicing kernel. * Boot never succeeds * but sometimes it shows a panic trace * sometimes it flickers to black or to frozen mouse pointer like shown in vid.mp4 * once it showed a panic trace and after some seconds it printed even more screen filling stack trace, and when again even more Though I spotted panics with 3.8.0-19, I only did screenshots and multiple boots with 3.8.0-26. This is new, introduced since do-release-upgrade from 12.10 to 13.04 yesterday. Please contact me when I can provide more information. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: this 3156 F pulseaudio CRDA: country DE: (2400 - 2483 @ 40), (N/A, 20) (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS (5470 - 5725 @ 40), (N/A, 26), DFS CasperVersion: 1.331 DistroRelease: Ubuntu 13.04 LiveMediaBuild: This MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/532U3C MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: cdrom-detect/try-usb=true noprompt boot=casper floppy.allowed_drive_mask=0 ignore_uuid live-media-path=/multiboot/ubuntu130464/casper/ file=/multiboot/ubuntu130464/preseed/ubuntu.seed initrd=/multiboot/ubuntu130464/casper/initrd.lz splash -- BOOT_IMAGE=/multiboot/ubuntu130464/casper/vmlinuz.efi ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/20/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03ABH dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP530U3C-A0MDE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03ABH:bd09/20/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C/532U3C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP530U3C-A0MDE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C/532U3C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1204604/+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 1204604] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/1204604/+attachment/3764653/+files/PulseList.txt -- 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/1204604 Title: panic during boot – 3.8.0-26 Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I attached screenshots of the panic. on 13.04 during boot, somewhere during starting of /etc/init/ services kernel 3.8.0-19 and 3.8.0-26 panics. I made a quick search but didn't found a related report. Though I found a quick fix in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322 I installed 3.7.0 as mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322/comments/23 to keep on working. I can't use `ubuntu-bug linux` cause I can't boot with the panicing kernel. * Boot never succeeds * but sometimes it shows a panic trace * sometimes it flickers to black or to frozen mouse pointer like shown in vid.mp4 * once it showed a panic trace and after some seconds it printed even more screen filling stack trace, and when again even more Though I spotted panics with 3.8.0-19, I only did screenshots and multiple boots with 3.8.0-26. This is new, introduced since do-release-upgrade from 12.10 to 13.04 yesterday. Please contact me when I can provide more information. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: this 3156 F pulseaudio CRDA: country DE: (2400 - 2483 @ 40), (N/A, 20) (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS (5470 - 5725 @ 40), (N/A, 26), DFS CasperVersion: 1.331 DistroRelease: Ubuntu 13.04 LiveMediaBuild: This MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/532U3C MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: cdrom-detect/try-usb=true noprompt boot=casper floppy.allowed_drive_mask=0 ignore_uuid live-media-path=/multiboot/ubuntu130464/casper/ file=/multiboot/ubuntu130464/preseed/ubuntu.seed initrd=/multiboot/ubuntu130464/casper/initrd.lz splash -- BOOT_IMAGE=/multiboot/ubuntu130464/casper/vmlinuz.efi ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/20/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03ABH dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP530U3C-A0MDE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03ABH:bd09/20/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C/532U3C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP530U3C-A0MDE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C/532U3C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1204604/+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 1204604] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1204604/+attachment/3764651/+files/ProcInterrupts.txt -- 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/1204604 Title: panic during boot – 3.8.0-26 Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I attached screenshots of the panic. on 13.04 during boot, somewhere during starting of /etc/init/ services kernel 3.8.0-19 and 3.8.0-26 panics. I made a quick search but didn't found a related report. Though I found a quick fix in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322 I installed 3.7.0 as mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322/comments/23 to keep on working. I can't use `ubuntu-bug linux` cause I can't boot with the panicing kernel. * Boot never succeeds * but sometimes it shows a panic trace * sometimes it flickers to black or to frozen mouse pointer like shown in vid.mp4 * once it showed a panic trace and after some seconds it printed even more screen filling stack trace, and when again even more Though I spotted panics with 3.8.0-19, I only did screenshots and multiple boots with 3.8.0-26. This is new, introduced since do-release-upgrade from 12.10 to 13.04 yesterday. Please contact me when I can provide more information. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: this 3156 F pulseaudio CRDA: country DE: (2400 - 2483 @ 40), (N/A, 20) (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS (5470 - 5725 @ 40), (N/A, 26), DFS CasperVersion: 1.331 DistroRelease: Ubuntu 13.04 LiveMediaBuild: This MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/532U3C MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: cdrom-detect/try-usb=true noprompt boot=casper floppy.allowed_drive_mask=0 ignore_uuid live-media-path=/multiboot/ubuntu130464/casper/ file=/multiboot/ubuntu130464/preseed/ubuntu.seed initrd=/multiboot/ubuntu130464/casper/initrd.lz splash -- BOOT_IMAGE=/multiboot/ubuntu130464/casper/vmlinuz.efi ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/20/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03ABH dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP530U3C-A0MDE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03ABH:bd09/20/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C/532U3C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP530U3C-A0MDE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C/532U3C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1204604/+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 1204604] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1204604/+attachment/3764657/+files/WifiSyslog.txt -- 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/1204604 Title: panic during boot – 3.8.0-26 Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I attached screenshots of the panic. on 13.04 during boot, somewhere during starting of /etc/init/ services kernel 3.8.0-19 and 3.8.0-26 panics. I made a quick search but didn't found a related report. Though I found a quick fix in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322 I installed 3.7.0 as mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322/comments/23 to keep on working. I can't use `ubuntu-bug linux` cause I can't boot with the panicing kernel. * Boot never succeeds * but sometimes it shows a panic trace * sometimes it flickers to black or to frozen mouse pointer like shown in vid.mp4 * once it showed a panic trace and after some seconds it printed even more screen filling stack trace, and when again even more Though I spotted panics with 3.8.0-19, I only did screenshots and multiple boots with 3.8.0-26. This is new, introduced since do-release-upgrade from 12.10 to 13.04 yesterday. Please contact me when I can provide more information. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: this 3156 F pulseaudio CRDA: country DE: (2400 - 2483 @ 40), (N/A, 20) (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS (5470 - 5725 @ 40), (N/A, 26), DFS CasperVersion: 1.331 DistroRelease: Ubuntu 13.04 LiveMediaBuild: This MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/532U3C MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: cdrom-detect/try-usb=true noprompt boot=casper floppy.allowed_drive_mask=0 ignore_uuid live-media-path=/multiboot/ubuntu130464/casper/ file=/multiboot/ubuntu130464/preseed/ubuntu.seed initrd=/multiboot/ubuntu130464/casper/initrd.lz splash -- BOOT_IMAGE=/multiboot/ubuntu130464/casper/vmlinuz.efi ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/20/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03ABH dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP530U3C-A0MDE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03ABH:bd09/20/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C/532U3C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP530U3C-A0MDE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C/532U3C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1204604/+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 1204604] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1204604/+attachment/3764656/+files/UdevLog.txt -- 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/1204604 Title: panic during boot – 3.8.0-26 Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I attached screenshots of the panic. on 13.04 during boot, somewhere during starting of /etc/init/ services kernel 3.8.0-19 and 3.8.0-26 panics. I made a quick search but didn't found a related report. Though I found a quick fix in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322 I installed 3.7.0 as mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322/comments/23 to keep on working. I can't use `ubuntu-bug linux` cause I can't boot with the panicing kernel. * Boot never succeeds * but sometimes it shows a panic trace * sometimes it flickers to black or to frozen mouse pointer like shown in vid.mp4 * once it showed a panic trace and after some seconds it printed even more screen filling stack trace, and when again even more Though I spotted panics with 3.8.0-19, I only did screenshots and multiple boots with 3.8.0-26. This is new, introduced since do-release-upgrade from 12.10 to 13.04 yesterday. Please contact me when I can provide more information. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: this 3156 F pulseaudio CRDA: country DE: (2400 - 2483 @ 40), (N/A, 20) (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS (5470 - 5725 @ 40), (N/A, 26), DFS CasperVersion: 1.331 DistroRelease: Ubuntu 13.04 LiveMediaBuild: This MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/532U3C MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: cdrom-detect/try-usb=true noprompt boot=casper floppy.allowed_drive_mask=0 ignore_uuid live-media-path=/multiboot/ubuntu130464/casper/ file=/multiboot/ubuntu130464/preseed/ubuntu.seed initrd=/multiboot/ubuntu130464/casper/initrd.lz splash -- BOOT_IMAGE=/multiboot/ubuntu130464/casper/vmlinuz.efi ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/20/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03ABH dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP530U3C-A0MDE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03ABH:bd09/20/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C/532U3C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP530U3C-A0MDE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C/532U3C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1204604/+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 1204604] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1204604/+attachment/3764655/+files/UdevDb.txt -- 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/1204604 Title: panic during boot – 3.8.0-26 Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I attached screenshots of the panic. on 13.04 during boot, somewhere during starting of /etc/init/ services kernel 3.8.0-19 and 3.8.0-26 panics. I made a quick search but didn't found a related report. Though I found a quick fix in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322 I installed 3.7.0 as mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322/comments/23 to keep on working. I can't use `ubuntu-bug linux` cause I can't boot with the panicing kernel. * Boot never succeeds * but sometimes it shows a panic trace * sometimes it flickers to black or to frozen mouse pointer like shown in vid.mp4 * once it showed a panic trace and after some seconds it printed even more screen filling stack trace, and when again even more Though I spotted panics with 3.8.0-19, I only did screenshots and multiple boots with 3.8.0-26. This is new, introduced since do-release-upgrade from 12.10 to 13.04 yesterday. Please contact me when I can provide more information. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: this 3156 F pulseaudio CRDA: country DE: (2400 - 2483 @ 40), (N/A, 20) (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS (5470 - 5725 @ 40), (N/A, 26), DFS CasperVersion: 1.331 DistroRelease: Ubuntu 13.04 LiveMediaBuild: This MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/532U3C MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: cdrom-detect/try-usb=true noprompt boot=casper floppy.allowed_drive_mask=0 ignore_uuid live-media-path=/multiboot/ubuntu130464/casper/ file=/multiboot/ubuntu130464/preseed/ubuntu.seed initrd=/multiboot/ubuntu130464/casper/initrd.lz splash -- BOOT_IMAGE=/multiboot/ubuntu130464/casper/vmlinuz.efi ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/20/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03ABH dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP530U3C-A0MDE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03ABH:bd09/20/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C/532U3C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP530U3C-A0MDE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C/532U3C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1204604/+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 1204604] Re: panic during boot – 3.8.0-26
live 13.04 works :( note, this log isnt quantal, its raring, but from a live usb image. ** 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/1204604 Title: panic during boot – 3.8.0-26 Status in “linux” package in Ubuntu: Confirmed Bug description: Hi, I attached screenshots of the panic. on 13.04 during boot, somewhere during starting of /etc/init/ services kernel 3.8.0-19 and 3.8.0-26 panics. I made a quick search but didn't found a related report. Though I found a quick fix in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322 I installed 3.7.0 as mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322/comments/23 to keep on working. I can't use `ubuntu-bug linux` cause I can't boot with the panicing kernel. * Boot never succeeds * but sometimes it shows a panic trace * sometimes it flickers to black or to frozen mouse pointer like shown in vid.mp4 * once it showed a panic trace and after some seconds it printed even more screen filling stack trace, and when again even more Though I spotted panics with 3.8.0-19, I only did screenshots and multiple boots with 3.8.0-26. This is new, introduced since do-release-upgrade from 12.10 to 13.04 yesterday. Please contact me when I can provide more information. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: this 3156 F pulseaudio CRDA: country DE: (2400 - 2483 @ 40), (N/A, 20) (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS (5470 - 5725 @ 40), (N/A, 26), DFS CasperVersion: 1.331 DistroRelease: Ubuntu 13.04 LiveMediaBuild: This MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/532U3C MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: cdrom-detect/try-usb=true noprompt boot=casper floppy.allowed_drive_mask=0 ignore_uuid live-media-path=/multiboot/ubuntu130464/casper/ file=/multiboot/ubuntu130464/preseed/ubuntu.seed initrd=/multiboot/ubuntu130464/casper/initrd.lz splash -- BOOT_IMAGE=/multiboot/ubuntu130464/casper/vmlinuz.efi ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/20/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03ABH dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP530U3C-A0MDE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03ABH:bd09/20/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C/532U3C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP530U3C-A0MDE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C/532U3C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1204604/+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 1098961] Re: PAE regression: OOM with just a few sleeps
Dear Christopher, Thanks for the hint about the BIOS. I updated it, the BIOS version went from 2.2.1 to 2.4.0. With the new BIOS and running non-PAE kernel: psz@DellE520:~$ uname -a Linux DellE520 3.2.0-51-generic #77-Ubuntu SMP Wed Jul 24 20:21:10 UTC 2013 i686 i686 i386 GNU/Linux psz@DellE520:~$ free -l total used free sharedbuffers cached Mem: 308796011285041959456 0 152800 705708 Low:861452 213880 647572 High: 2226508 9146241311884 -/+ buffers/cache: 2699962817964 Swap: 2920 0 2920 it handled the sleep test bash -c 'n=0; while [ $n -lt 33000 ]; do sleep 600 ((n=n+1)); ((m=n%500)); if [ $m -lt 1 ]; then echo -n $n - ; date; free -l; sleep 1; fi; done' just fine (as expected), running out of max user processes because of default setting of ulimit -u 23964. Installing the PAE kernel and rebooting (of course with new BIOS): psz@DellE520:~$ uname -a Linux DellE520 3.2.0-51-generic-pae #77-Ubuntu SMP Wed Jul 24 20:40:32 UTC 2013 i686 i686 i386 GNU/Linux psz@DellE520:~$ free -l total used free sharedbuffers cached Mem: 3087592 6107402476852 0 112796 344216 Low:865180 160496 704684 High: 412 4502441772168 -/+ buffers/cache: 1537282933864 Swap: 2920 0 2920 (has default setting ulimit -u 23960) and re-trying the sleep test, things went bad after 22500 processes. The graphics console crashed, with X saying your graphics device is running in low-resolution mode or somesuch, and with no mouse or keyboard response so could not click the OK button. Hitting Alt-Ctrl-F2 worked and got a getty login. Looking with ps, there were no sleep processes left running. In /var/log/syslog I found: Aug 8 20:01:48 DellE520 kernel: [ 341.000570] oom_kill_process: 39 callbacks suppressed Aug 8 20:01:48 DellE520 kernel: [ 341.000578] bash invoked oom-killer: gfp_mask=0x84d0, order=0, oom_adj=0, oom_score_adj=0 Aug 8 20:01:48 DellE520 kernel: [ 341.000584] bash cpuset=/ mems_allowed=0 Aug 8 20:01:48 DellE520 kernel: [ 341.000589] Pid: 2375, comm: bash Not tainted 3.2.0-51-generic-pae #77-Ubuntu Aug 8 20:01:48 DellE520 kernel: [ 341.000593] Call Trace: Aug 8 20:01:48 DellE520 kernel: [ 341.000605] [c10fa6c5] dump_header.isra.6+0x85/0xc0 Aug 8 20:01:48 DellE520 kernel: [ 341.000612] [c10fa8fc] oom_kill_process+0x5c/0x80 Aug 8 20:01:48 DellE520 kernel: [ 341.000617] [c10fad15] out_of_memory+0xc5/0x1c0 Aug 8 20:01:48 DellE520 kernel: [ 341.000623] [c10febcc] __alloc_pages_nodemask+0x72c/0x740 Aug 8 20:01:48 DellE520 kernel: [ 341.000630] [c10fec5c] __get_free_pages+0x1c/0x30 Aug 8 20:01:48 DellE520 kernel: [ 341.000636] [c103af54] pgd_alloc+0x74/0x250 Aug 8 20:01:48 DellE520 kernel: [ 341.000642] [c10440ca] ? place_entity+0x9a/0x160 Aug 8 20:01:48 DellE520 kernel: [ 341.000648] [c1058487] mm_init+0xc7/0x100 Aug 8 20:01:48 DellE520 kernel: [ 341.000653] [c1058f23] dup_mm+0xa3/0x230 Aug 8 20:01:48 DellE520 kernel: [ 341.000658] [c10597fd] copy_process.part.23+0x71d/0xc10 Aug 8 20:01:48 DellE520 kernel: [ 341.000663] [c1059d6e] copy_process+0x7e/0x90 Aug 8 20:01:48 DellE520 kernel: [ 341.000668] [c1059eb4] do_fork+0xf4/0x2c0 Aug 8 20:01:48 DellE520 kernel: [ 341.000675] [c1019874] sys_clone+0x34/0x40 Aug 8 20:01:48 DellE520 kernel: [ 341.000682] [c15b21d9] ptregs_clone+0x15/0x3c Aug 8 20:01:48 DellE520 kernel: [ 341.000687] [c15b209f] ? sysenter_do_call+0x12/0x28 Aug 8 20:01:48 DellE520 kernel: [ 341.000691] Mem-Info: Aug 8 20:01:48 DellE520 kernel: [ 341.000694] DMA per-cpu: Aug 8 20:01:48 DellE520 kernel: [ 341.000699] CPU0: hi:0, btch: 1 usd: 0 Aug 8 20:01:48 DellE520 kernel: [ 341.000702] CPU1: hi:0, btch: 1 usd: 0 Aug 8 20:01:48 DellE520 kernel: [ 341.000705] Normal per-cpu: Aug 8 20:01:48 DellE520 kernel: [ 341.000708] CPU0: hi: 186, btch: 31 usd: 0 Aug 8 20:01:48 DellE520 kernel: [ 341.000711] CPU1: hi: 186, btch: 31 usd: 29 Aug 8 20:01:48 DellE520 kernel: [ 341.000714] HighMem per-cpu: Aug 8 20:01:48 DellE520 kernel: [ 341.000717] CPU0: hi: 186, btch: 31 usd: 0 Aug 8 20:01:48 DellE520 kernel: [ 341.000720] CPU1: hi: 186, btch: 31 usd: 167 Aug 8 20:01:48 DellE520 kernel: [ 341.000726] active_anon:326331 inactive_anon:81629 isolated_anon:0 Aug 8 20:01:48 DellE520 kernel: [ 341.000728] active_file:11586 inactive_file:8659 isolated_file:0 Aug 8 20:01:48 DellE520 kernel: [ 341.000729] unevictable:0 dirty:0 writeback:2 unstable:0 Aug 8 20:01:48 DellE520 kernel: [ 341.000730] free:25897 slab_reclaimable:2285 slab_unreclaimable:60037 Aug 8 20:01:48 DellE520 kernel: [ 341.000732] mapped:14875 shmem:32942 pagetables:111532 bounce:0 Aug 8 20:01:48 DellE520 kernel: [ 341.000740]
[Kernel-packages] [Bug 1210091] [NEW] Laptop lid closure suspends ongoing shutdown; later resumes shutdown
Public bug reported: On a laptop set to suspend on lid close, when the lid is closed within seconds of initiating shutdown, the shutdown process is interrupted and suspended. On later re-opening the laptop, the system resumes and then continues the previously initiated shutdown process. While this is at some level logical, it is undesirable and likely confusing to an ordinary user. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1210091 Title: Laptop lid closure suspends ongoing shutdown; later resumes shutdown Status in “linux” package in Ubuntu: New Bug description: On a laptop set to suspend on lid close, when the lid is closed within seconds of initiating shutdown, the shutdown process is interrupted and suspended. On later re-opening the laptop, the system resumes and then continues the previously initiated shutdown process. While this is at some level logical, it is undesirable and likely confusing to an ordinary user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210091/+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 814894] Re: [Fit-PC2i] Kernel hangs on high network throughput
After the latest crash apport asked if I wanted to send a problem
report. Since it appears apport cannot attach the new information to an
existing report, the additional information is in bug report number
1210092. Does this provide the information you need?
--
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/814894
Title:
[Fit-PC2i] Kernel hangs on high network throughput
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
If A Fit-PC2i receives more than 200Mbit/s of network traffic the
kernel will hang. Cursor stops blinking, machine doesn't respond to
keyboard and mouse input, no longer responds to ARP requests or any
other network traffic.
The problem is triggered every time a 10.04.3 system with kernel
version 2.6.32-33-generic receives more than 200Mbit/s of network
traffic. The bug affects both live system as well as fully installed
system.
The bug can be reproduced by downloading a 1GB file from a server on
the LAN. The bug is only triggered if more than 200Mbit/s is
transfered. If any link on the path between client and server is
100Mbit/s or less the bug cannot be reproduced.
The 8.04.4 live system is not affected by this problem and can receive
600Mbit/s without problems on the same hardware.
Marking this as a security problem because it can in principle be used
to perform a DoS attack.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image (not installed)
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-33.70-generic 2.6.32.41+drm33.18
Uname: Linux 2.6.32-33-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: MID [HDA Intel MID], device 0: ALC662 rev1 Analog [ALC662 rev1
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kasperd1453 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'MID'/'HDA Intel MID at 0xb005 irq 22'
Mixer name : 'Realtek ALC662 rev1'
Components : 'HDA:10ec0662,10ec0662,00100101'
Controls : 33
Simple ctrls : 19
Date: Sat Jul 23 01:43:06 2011
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=e14584e1-caed-4150-9e25-e364d27bebe3
InstallationMedia: Ubuntu 10.04.3 LTS Lucid Lynx - Release i386 (20110720.1)
MachineType: CompuLab CM-iAM/SBC-FITPC2i
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-33-generic
root=UUID=8bf29c49-594d-41b8-8513-ac3cf4bf4e1b ro rootdir=lucid
ProcEnviron:
LANG=en_DK.utf8
SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.7
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
StagingDrivers: rt2870sta
Title: [STAGING]
dmi.bios.date: 09/14/2010
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: NAPA0001.86C..D.1009141059
dmi.board.name: CM-iAM/SBC-FITPC2i
dmi.board.vendor: Intel Corporation
dmi.board.version: 1.x
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: OEM
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvrNAPA0001.86C..D.1009141059:bd09/14/2010:svnCompuLab:pnCM-iAM/SBC-FITPC2i:pvrNotApplicable:rvnIntelCorporation:rnCM-iAM/SBC-FITPC2i:rvr1.x:cvnOEM:ct1:cvrN/A:
dmi.product.name: CM-iAM/SBC-FITPC2i
dmi.product.version: Not Applicable
dmi.sys.vendor: CompuLab
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/814894/+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 1210091] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1210091 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New = Incomplete -- 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/1210091 Title: Laptop lid closure suspends ongoing shutdown; later resumes shutdown Status in “linux” package in Ubuntu: Incomplete Bug description: On a laptop set to suspend on lid close, when the lid is closed within seconds of initiating shutdown, the shutdown process is interrupted and suspended. On later re-opening the laptop, the system resumes and then continues the previously initiated shutdown process. While this is at some level logical, it is undesirable and likely confusing to an ordinary user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210091/+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 1210091] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/1210091/+attachment/3764765/+files/CRDA.txt -- 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/1210091 Title: Laptop lid closure suspends ongoing shutdown; later resumes shutdown Status in “linux” package in Ubuntu: Confirmed Bug description: On a laptop set to suspend on lid close, when the lid is closed within seconds of initiating shutdown, the shutdown process is interrupted and suspended. On later re-opening the laptop, the system resumes and then continues the previously initiated shutdown process. While this is at some level logical, it is undesirable and likely confusing to an ordinary user. --- ApportVersion: 2.12-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brendan1982 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=e0a92eed-b725-41aa-b334-f520bf0db05f InstallationDate: Installed on 2011-08-23 (715 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: Dell Inc. Latitude D630 MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=18e1ae66-bd38-4b66-a77e-f600df660f19 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware1.113 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.10.0-6-generic i686 UpgradeStatus: Upgraded to saucy on 2013-05-14 (85 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 06/07/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd06/07/2007:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210091/+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 1210091] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1210091/+attachment/3764766/+files/CurrentDmesg.txt -- 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/1210091 Title: Laptop lid closure suspends ongoing shutdown; later resumes shutdown Status in “linux” package in Ubuntu: Confirmed Bug description: On a laptop set to suspend on lid close, when the lid is closed within seconds of initiating shutdown, the shutdown process is interrupted and suspended. On later re-opening the laptop, the system resumes and then continues the previously initiated shutdown process. While this is at some level logical, it is undesirable and likely confusing to an ordinary user. --- ApportVersion: 2.12-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brendan1982 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=e0a92eed-b725-41aa-b334-f520bf0db05f InstallationDate: Installed on 2011-08-23 (715 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: Dell Inc. Latitude D630 MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=18e1ae66-bd38-4b66-a77e-f600df660f19 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware1.113 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.10.0-6-generic i686 UpgradeStatus: Upgraded to saucy on 2013-05-14 (85 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 06/07/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd06/07/2007:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210091/+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 1210091] Re: Laptop lid closure suspends ongoing shutdown; later resumes shutdown
apport information ** Tags added: apport-collected saucy ** Description changed: On a laptop set to suspend on lid close, when the lid is closed within seconds of initiating shutdown, the shutdown process is interrupted and suspended. On later re-opening the laptop, the system resumes and then continues the previously initiated shutdown process. While this is at some level logical, it is undesirable and likely confusing to an ordinary user. + --- + ApportVersion: 2.12-0ubuntu3 + Architecture: i386 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: brendan1982 F pulseaudio + DistroRelease: Ubuntu 13.10 + HibernationDevice: RESUME=UUID=e0a92eed-b725-41aa-b334-f520bf0db05f + InstallationDate: Installed on 2011-08-23 (715 days ago) + InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) + MachineType: Dell Inc. Latitude D630 + MarkForUpload: True + Package: linux (not installed) + PccardctlIdent: + Socket 0: +no product info available + PccardctlStatus: + Socket 0: +no card + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=18e1ae66-bd38-4b66-a77e-f600df660f19 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 + RelatedPackageVersions: + linux-restricted-modules-3.10.0-6-generic N/A + linux-backports-modules-3.10.0-6-generic N/A + linux-firmware1.113 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: saucy + Uname: Linux 3.10.0-6-generic i686 + UpgradeStatus: Upgraded to saucy on 2013-05-14 (85 days ago) + UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare + dmi.bios.date: 06/07/2007 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A02 + dmi.board.name: 0KU184 + dmi.board.vendor: Dell Inc. + dmi.chassis.type: 8 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvrA02:bd06/07/2007:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: + dmi.product.name: Latitude D630 + dmi.sys.vendor: Dell Inc. ** Attachment added: AlsaInfo.txt https://bugs.launchpad.net/bugs/1210091/+attachment/3764763/+files/AlsaInfo.txt -- 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/1210091 Title: Laptop lid closure suspends ongoing shutdown; later resumes shutdown Status in “linux” package in Ubuntu: Confirmed Bug description: On a laptop set to suspend on lid close, when the lid is closed within seconds of initiating shutdown, the shutdown process is interrupted and suspended. On later re-opening the laptop, the system resumes and then continues the previously initiated shutdown process. While this is at some level logical, it is undesirable and likely confusing to an ordinary user. --- ApportVersion: 2.12-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brendan1982 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=e0a92eed-b725-41aa-b334-f520bf0db05f InstallationDate: Installed on 2011-08-23 (715 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: Dell Inc. Latitude D630 MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=18e1ae66-bd38-4b66-a77e-f600df660f19 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware1.113 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.10.0-6-generic i686 UpgradeStatus: Upgraded to saucy on 2013-05-14 (85 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 06/07/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd06/07/2007:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210091/+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 1210091] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/1210091/+attachment/3764767/+files/IwConfig.txt -- 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/1210091 Title: Laptop lid closure suspends ongoing shutdown; later resumes shutdown Status in “linux” package in Ubuntu: Confirmed Bug description: On a laptop set to suspend on lid close, when the lid is closed within seconds of initiating shutdown, the shutdown process is interrupted and suspended. On later re-opening the laptop, the system resumes and then continues the previously initiated shutdown process. While this is at some level logical, it is undesirable and likely confusing to an ordinary user. --- ApportVersion: 2.12-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brendan1982 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=e0a92eed-b725-41aa-b334-f520bf0db05f InstallationDate: Installed on 2011-08-23 (715 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: Dell Inc. Latitude D630 MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=18e1ae66-bd38-4b66-a77e-f600df660f19 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware1.113 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.10.0-6-generic i686 UpgradeStatus: Upgraded to saucy on 2013-05-14 (85 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 06/07/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd06/07/2007:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210091/+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 1210091] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1210091/+attachment/3764771/+files/ProcEnviron.txt -- 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/1210091 Title: Laptop lid closure suspends ongoing shutdown; later resumes shutdown Status in “linux” package in Ubuntu: Confirmed Bug description: On a laptop set to suspend on lid close, when the lid is closed within seconds of initiating shutdown, the shutdown process is interrupted and suspended. On later re-opening the laptop, the system resumes and then continues the previously initiated shutdown process. While this is at some level logical, it is undesirable and likely confusing to an ordinary user. --- ApportVersion: 2.12-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brendan1982 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=e0a92eed-b725-41aa-b334-f520bf0db05f InstallationDate: Installed on 2011-08-23 (715 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: Dell Inc. Latitude D630 MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=18e1ae66-bd38-4b66-a77e-f600df660f19 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware1.113 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.10.0-6-generic i686 UpgradeStatus: Upgraded to saucy on 2013-05-14 (85 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 06/07/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd06/07/2007:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210091/+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 1210091] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1210091/+attachment/3764764/+files/BootDmesg.txt -- 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/1210091 Title: Laptop lid closure suspends ongoing shutdown; later resumes shutdown Status in “linux” package in Ubuntu: Confirmed Bug description: On a laptop set to suspend on lid close, when the lid is closed within seconds of initiating shutdown, the shutdown process is interrupted and suspended. On later re-opening the laptop, the system resumes and then continues the previously initiated shutdown process. While this is at some level logical, it is undesirable and likely confusing to an ordinary user. --- ApportVersion: 2.12-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brendan1982 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=e0a92eed-b725-41aa-b334-f520bf0db05f InstallationDate: Installed on 2011-08-23 (715 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: Dell Inc. Latitude D630 MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=18e1ae66-bd38-4b66-a77e-f600df660f19 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware1.113 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.10.0-6-generic i686 UpgradeStatus: Upgraded to saucy on 2013-05-14 (85 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 06/07/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd06/07/2007:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210091/+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 1210091] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1210091/+attachment/3764770/+files/ProcCpuinfo.txt -- 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/1210091 Title: Laptop lid closure suspends ongoing shutdown; later resumes shutdown Status in “linux” package in Ubuntu: Confirmed Bug description: On a laptop set to suspend on lid close, when the lid is closed within seconds of initiating shutdown, the shutdown process is interrupted and suspended. On later re-opening the laptop, the system resumes and then continues the previously initiated shutdown process. While this is at some level logical, it is undesirable and likely confusing to an ordinary user. --- ApportVersion: 2.12-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brendan1982 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=e0a92eed-b725-41aa-b334-f520bf0db05f InstallationDate: Installed on 2011-08-23 (715 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: Dell Inc. Latitude D630 MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=18e1ae66-bd38-4b66-a77e-f600df660f19 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware1.113 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.10.0-6-generic i686 UpgradeStatus: Upgraded to saucy on 2013-05-14 (85 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 06/07/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd06/07/2007:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210091/+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 1210091] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1210091/+attachment/3764768/+files/Lspci.txt -- 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/1210091 Title: Laptop lid closure suspends ongoing shutdown; later resumes shutdown Status in “linux” package in Ubuntu: Confirmed Bug description: On a laptop set to suspend on lid close, when the lid is closed within seconds of initiating shutdown, the shutdown process is interrupted and suspended. On later re-opening the laptop, the system resumes and then continues the previously initiated shutdown process. While this is at some level logical, it is undesirable and likely confusing to an ordinary user. --- ApportVersion: 2.12-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brendan1982 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=e0a92eed-b725-41aa-b334-f520bf0db05f InstallationDate: Installed on 2011-08-23 (715 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: Dell Inc. Latitude D630 MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=18e1ae66-bd38-4b66-a77e-f600df660f19 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware1.113 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.10.0-6-generic i686 UpgradeStatus: Upgraded to saucy on 2013-05-14 (85 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 06/07/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd06/07/2007:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210091/+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 1210091] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1210091/+attachment/3764769/+files/Lsusb.txt -- 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/1210091 Title: Laptop lid closure suspends ongoing shutdown; later resumes shutdown Status in “linux” package in Ubuntu: Confirmed Bug description: On a laptop set to suspend on lid close, when the lid is closed within seconds of initiating shutdown, the shutdown process is interrupted and suspended. On later re-opening the laptop, the system resumes and then continues the previously initiated shutdown process. While this is at some level logical, it is undesirable and likely confusing to an ordinary user. --- ApportVersion: 2.12-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brendan1982 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=e0a92eed-b725-41aa-b334-f520bf0db05f InstallationDate: Installed on 2011-08-23 (715 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: Dell Inc. Latitude D630 MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=18e1ae66-bd38-4b66-a77e-f600df660f19 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware1.113 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.10.0-6-generic i686 UpgradeStatus: Upgraded to saucy on 2013-05-14 (85 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 06/07/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd06/07/2007:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210091/+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 1210091] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1210091/+attachment/3764772/+files/ProcInterrupts.txt -- 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/1210091 Title: Laptop lid closure suspends ongoing shutdown; later resumes shutdown Status in “linux” package in Ubuntu: Confirmed Bug description: On a laptop set to suspend on lid close, when the lid is closed within seconds of initiating shutdown, the shutdown process is interrupted and suspended. On later re-opening the laptop, the system resumes and then continues the previously initiated shutdown process. While this is at some level logical, it is undesirable and likely confusing to an ordinary user. --- ApportVersion: 2.12-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brendan1982 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=e0a92eed-b725-41aa-b334-f520bf0db05f InstallationDate: Installed on 2011-08-23 (715 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: Dell Inc. Latitude D630 MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=18e1ae66-bd38-4b66-a77e-f600df660f19 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware1.113 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.10.0-6-generic i686 UpgradeStatus: Upgraded to saucy on 2013-05-14 (85 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 06/07/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd06/07/2007:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210091/+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 1210091] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/1210091/+attachment/3764774/+files/PulseList.txt -- 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/1210091 Title: Laptop lid closure suspends ongoing shutdown; later resumes shutdown Status in “linux” package in Ubuntu: Confirmed Bug description: On a laptop set to suspend on lid close, when the lid is closed within seconds of initiating shutdown, the shutdown process is interrupted and suspended. On later re-opening the laptop, the system resumes and then continues the previously initiated shutdown process. While this is at some level logical, it is undesirable and likely confusing to an ordinary user. --- ApportVersion: 2.12-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brendan1982 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=e0a92eed-b725-41aa-b334-f520bf0db05f InstallationDate: Installed on 2011-08-23 (715 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: Dell Inc. Latitude D630 MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=18e1ae66-bd38-4b66-a77e-f600df660f19 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware1.113 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.10.0-6-generic i686 UpgradeStatus: Upgraded to saucy on 2013-05-14 (85 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 06/07/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd06/07/2007:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210091/+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 1210091] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1210091/+attachment/3764777/+files/WifiSyslog.txt ** 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/1210091 Title: Laptop lid closure suspends ongoing shutdown; later resumes shutdown Status in “linux” package in Ubuntu: Confirmed Bug description: On a laptop set to suspend on lid close, when the lid is closed within seconds of initiating shutdown, the shutdown process is interrupted and suspended. On later re-opening the laptop, the system resumes and then continues the previously initiated shutdown process. While this is at some level logical, it is undesirable and likely confusing to an ordinary user. --- ApportVersion: 2.12-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brendan1982 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=e0a92eed-b725-41aa-b334-f520bf0db05f InstallationDate: Installed on 2011-08-23 (715 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: Dell Inc. Latitude D630 MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=18e1ae66-bd38-4b66-a77e-f600df660f19 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware1.113 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.10.0-6-generic i686 UpgradeStatus: Upgraded to saucy on 2013-05-14 (85 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 06/07/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd06/07/2007:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210091/+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 1210091] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1210091/+attachment/3764776/+files/UdevLog.txt -- 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/1210091 Title: Laptop lid closure suspends ongoing shutdown; later resumes shutdown Status in “linux” package in Ubuntu: Confirmed Bug description: On a laptop set to suspend on lid close, when the lid is closed within seconds of initiating shutdown, the shutdown process is interrupted and suspended. On later re-opening the laptop, the system resumes and then continues the previously initiated shutdown process. While this is at some level logical, it is undesirable and likely confusing to an ordinary user. --- ApportVersion: 2.12-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brendan1982 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=e0a92eed-b725-41aa-b334-f520bf0db05f InstallationDate: Installed on 2011-08-23 (715 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: Dell Inc. Latitude D630 MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=18e1ae66-bd38-4b66-a77e-f600df660f19 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware1.113 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.10.0-6-generic i686 UpgradeStatus: Upgraded to saucy on 2013-05-14 (85 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 06/07/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd06/07/2007:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210091/+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 1210091] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1210091/+attachment/3764775/+files/UdevDb.txt -- 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/1210091 Title: Laptop lid closure suspends ongoing shutdown; later resumes shutdown Status in “linux” package in Ubuntu: Confirmed Bug description: On a laptop set to suspend on lid close, when the lid is closed within seconds of initiating shutdown, the shutdown process is interrupted and suspended. On later re-opening the laptop, the system resumes and then continues the previously initiated shutdown process. While this is at some level logical, it is undesirable and likely confusing to an ordinary user. --- ApportVersion: 2.12-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brendan1982 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=e0a92eed-b725-41aa-b334-f520bf0db05f InstallationDate: Installed on 2011-08-23 (715 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: Dell Inc. Latitude D630 MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=18e1ae66-bd38-4b66-a77e-f600df660f19 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware1.113 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.10.0-6-generic i686 UpgradeStatus: Upgraded to saucy on 2013-05-14 (85 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 06/07/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd06/07/2007:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210091/+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 1210091] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1210091/+attachment/3764773/+files/ProcModules.txt -- 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/1210091 Title: Laptop lid closure suspends ongoing shutdown; later resumes shutdown Status in “linux” package in Ubuntu: Confirmed Bug description: On a laptop set to suspend on lid close, when the lid is closed within seconds of initiating shutdown, the shutdown process is interrupted and suspended. On later re-opening the laptop, the system resumes and then continues the previously initiated shutdown process. While this is at some level logical, it is undesirable and likely confusing to an ordinary user. --- ApportVersion: 2.12-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brendan1982 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=e0a92eed-b725-41aa-b334-f520bf0db05f InstallationDate: Installed on 2011-08-23 (715 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: Dell Inc. Latitude D630 MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=18e1ae66-bd38-4b66-a77e-f600df660f19 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware1.113 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.10.0-6-generic i686 UpgradeStatus: Upgraded to saucy on 2013-05-14 (85 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 06/07/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd06/07/2007:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210091/+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 1171251] Re: 174f:5a31 Webcam is no longer detected
Sezer Yalcin, the next step is to perform a bisect from the last known
good kernel, and the first bad one, in order to identify the offending
commit. Could you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection ?
** Tags removed: kernel-bug-exists-upstream
** Tags added: kernel-bug-exists-upstream-v3.11-rc4
** Tags removed: needs-upstream-testing
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
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/1171251
Title:
174f:5a31 Webcam is no longer detected
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
My webcam started acting weird in recent kernel updates and now I notice that
it's completely undetected.
Bus 002 Device 003: ID 174f:5a31 Syntek Sonix USB 2.0 Camera
/dev/video* does not exist.
I will try older kernels and update this ticket.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-40-generic 3.2.0-40.64
ProcVersionSignature: Ubuntu 3.2.0-40.64-generic 3.2.40
Uname: Linux 3.2.0-40-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.2
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sezer 2537 F xfce4-volumed
sezer 2554 F pulseaudio
/dev/snd/controlC0: sezer 2537 F xfce4-volumed
sezer 2554 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfcdf8000 irq 48'
Mixer name : 'Realtek ALC662 rev1'
Components : 'HDA:10ec0662,104319c3,00100101
HDA:11c11040,10431636,00100200'
Controls : 26
Simple ctrls : 14
Card1.Amixer.info:
Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfceec000 irq 49'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,0010'
Controls : 6
Simple ctrls : 1
Card1.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Sun Apr 21 18:08:38 2013
HibernationDevice: RESUME=UUID=d42e2415-0ae7-4fe9-b1fb-7a17f045968b
InstallationMedia: Xubuntu 12.04.1 LTS Precise Pangolin - Release amd64
(20120817.3)
MachineType: ASUSTeK Computer Inc. F8Va
MarkForUpload: True
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-40-generic
root=UUID=1f39f034-a2a5-421d-814b-1b7298477f09 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-3.2.0-40-generic N/A
linux-backports-modules-3.2.0-40-generic N/A
linux-firmware1.79.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/09/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 209
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: F8Va
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr209:bd02/09/2009:svnASUSTeKComputerInc.:pnF8Va:pvr1.0:rvnASUSTeKComputerInc.:rnF8Va:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: F8Va
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1171251/+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 1209032] Re: [LENOVO 4298CTO] suspend/resume failure
Richard Brown, did this problem not occur in a release prior to Saucy? ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- 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/1209032 Title: [LENOVO 4298CTO] suspend/resume failure Status in “linux” package in Ubuntu: Incomplete Bug description: Got this message at bootup. My system has been failing to suspend when I close the lid, but suspending fine when I use the shortcut keys. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.10.0-6-generic 3.10.0-6.17 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.11-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: richard1785 F pulseaudio CRDA: country NZ: (2402 - 2482 @ 40), (N/A, 30) (5170 - 5250 @ 20), (3, 23) (5250 - 5330 @ 20), (3, 23), DFS (5735 - 5835 @ 20), (3, 30) Date: Thu Aug 8 00:15:27 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=9b154dfe-feca-4014-913a-d31e266ae707 InstallationDate: Installed on 2013-05-01 (98 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterpreterPath: /usr/bin/python3.3 MachineType: LENOVO 4298CTO MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=1a2d01bd-0948-4b7e-b868-8b29e6b068f6 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware1.112 SourcePackage: linux Title: [LENOVO 4298CTO] suspend/resume failure UpgradeStatus: Upgraded to saucy on 2013-07-26 (12 days ago) UserGroups: dmi.bios.date: 07/19/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET63WW (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 4298CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET63WW(1.33):bd07/19/2012:svnLENOVO:pn4298CTO:pvrThinkPadX220Tablet:rvnLENOVO:rn4298CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4298CTO dmi.product.version: ThinkPad X220 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1209032/+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 1208257] Re: [HP ProBook 4540s] brightness control problems
BondCreat, could you please provide the information following https://wiki.ubuntu.com/Kernel/Debugging/Backlight ? ** Tags removed: regression-potential ** Tags added: regression-release -- 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/1208257 Title: [HP ProBook 4540s] brightness control problems Status in “linux” package in Ubuntu: Incomplete Bug description: I bought a laptop in December 2012, immediately tried to put Ubuntu 12.10, got broken wi-fi and non-working graphics acceleration. Updated kernel to version 3.6, with graphic acceleration was all right, even partially earned wi-fi. After some time wi-fi hang, helped only restart the network subsystem. Updated kernel to 3.7, with the wi-fi was all became normal, but stopped working brightness control with the Fn keys. Progress bar indicates that the brightness changes, but in fact nothing happens. Tried the new distribution 13.04, on 3.8 kernels, 3.9, 3.10, nothing changes. Upon adjustment has broken in 3.7 kernel. It turns out that this is a regression. Hardware Configuration: Intel Core I5 3210M Intel HD 4000 8 gigs of ram Ralink corp. RT3290 Ubuntu 13.04 x64 --- ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country UA: (2402 - 2482 @ 40), (N/A, 20) DistroRelease: Ubuntu 13.04 InstallationDate: Installed on 2013-08-04 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Hewlett-Packard HP ProBook 4540s MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=f5b4658c-870e-449d-a9d7-5caaa6eec2f3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/20/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRR Ver. F.41 dmi.board.name: 17F6 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 58.1E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRRVer.F.41:bd05/20/2013:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1E:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4540s dmi.product.version: A1018C1100 dmi.sys.vendor: Hewlett-Packard --- ApportVersion: 2.12-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 3887 F pulseaudio ubuntu14062 F pulseaudio CRDA: country UA: (2400 - 2483 @ 40), (N/A, 20), NO-OUTDOOR (5150 - 5350 @ 40), (N/A, 20), NO-OUTDOOR (57240 - 65880 @ 2160), (N/A, 40), NO-OUTDOOR CasperVersion: 1.336 DistroRelease: Ubuntu 13.10 LiveMediaBuild: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130807) MachineType: Hewlett-Packard HP ProBook 4540s MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/username.seed boot=casper persistent initrd=/casper/initrd.lz splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware1.113 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.10.0-6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/20/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRR Ver. F.41 dmi.board.name: 17F6 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 58.1E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRRVer.F.41:bd05/20/2013:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1E:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4540s dmi.product.version: A1018C1100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to:
[Kernel-packages] [Bug 1209390] Re: [LENOVO Ideapad Z570 1024] suspend/resume failure
** Summary changed: - [LENOVO 1024D9U] suspend/resume failure + [LENOVO Ideapad Z570 1024] suspend/resume failure -- 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/1209390 Title: [LENOVO Ideapad Z570 1024] suspend/resume failure Status in “linux” package in Ubuntu: Incomplete Bug description: Apport Check; Turning on laptop after not using for a couple hours ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.10.0-6-generic 3.10.0-6.17 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: henry 1950 F pulseaudio /dev/snd/pcmC0D0p: henry 1950 F...m pulseaudio Date: Wed Aug 7 15:28:32 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=68e4f182-ac7a-4794-a3a8-161edd1de6df InstallationDate: Installed on 2013-07-13 (25 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterpreterPath: /usr/bin/python3.3 MachineType: LENOVO 1024D9U MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=0371477c-a8f9-4b51-8400-6cf993471def ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware1.113 SourcePackage: linux StagingDrivers: rts5139 Title: [LENOVO 1024D9U] suspend/resume failure UpgradeStatus: Upgraded to saucy on 2013-08-05 (1 days ago) UserGroups: dmi.bios.date: 02/15/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 45CN47WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr45CN47WW:bd02/15/2012:svnLENOVO:pn1024D9U:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.name: 1024D9U dmi.product.version: Ideapad Z570 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1209390/+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 1144322] Re: [Toshiba Satellite A80] Kernel 3.8.x Panic when disconnecting from network manager via ppp0
Gurvender.Bahia, a test of the live environment would be helpful instead of a full install. ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- 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/1144322 Title: [Toshiba Satellite A80] Kernel 3.8.x Panic when disconnecting from network manager via ppp0 Status in “linux” package in Ubuntu: Incomplete Status in “linux” package in Arch Linux: New Status in Gentoo Linux: New Bug description: Using: Ubuntu 12.04 (precise) 32-bit Machine: Laptop / old Toshiba / Celeron processor Installing Kernel from: http://kernel.ubuntu.com/~kernel-ppa/mainline/; Apport disabled and uninstalled, so can't provide debug/log details (this to make the machine run a bit faster, have been doing so since 10.04). Have no problem with Kernel upto 3.7.10 (have been upgrading to Kernel 3.5/3.6/3.7/3.8, when ever new builds are available) But when using Kernel 3.8.0/3.8.1/3.8.2, get Kernel Panic machine crashes freezes, have to hard boot. Machine connects to net using ppp0 (modem on phone), then if you disconnect the modem ppp0 try to reconnect, the Kernel Panics crashes, or then if you disconnect by unchecking Enable Networking then rechecking Enable Networking, the Kernel Panics crashes. First faced this problem with Kernel 3.8.0 so went back to using 3.7.9, then same story repeated with Kernel 3.8.1 3.8.2, currently using Kernel 3.7.10. Think there is some REGRESSION in Kernel 3.8 below details are provided using HardInfo 0.5.1 : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322/+attachment/3761201/+files/hardinfo --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1880 F pulseaudio /dev/snd/seq:timidity 1424 F timidity Card0.Amixer.info: Card hw:0 'ICH6'/'Intel ICH6 with ALC250 at irq 17' Mixer name : 'Realtek ALC250 rev 2' Components : 'AC97a:414c4752' Controls : 33 Simple ctrls : 21 DistroRelease: Ubuntu 12.04 MachineType: TOSHIBA Satellite A80 MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-51-generic-pae root=UUID=4dda5c0a-3583-45f5-b6c4-b5aef19935c8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.2.0-51.77-generic-pae 3.2.48 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/ubuntu not ours. No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.2.0-51-generic-pae N/A linux-backports-modules-3.2.0-51-generic-pae N/A linux-firmware1.79.6 Tags: precise Uname: Linux 3.2.0-51-generic-pae i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/25/2006 dmi.bios.vendor: TOSHIBA dmi.bios.version: V2.80 dmi.board.name: EAT10/EAT20 dmi.board.vendor: TOSHIBA dmi.board.version: Null dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV2.80:bd10/25/2006:svnTOSHIBA:pnSatelliteA80:pvrPSA80L-043003:rvnTOSHIBA:rnEAT10/EAT20:rvrNull:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite A80 dmi.product.version: PSA80L-043003 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322/+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 1093999] Re: ip route src not working
Sets, would you need a backport to a release prior to Saucy, or may we close this as Status Invalid? -- 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/1093999 Title: ip route src not working Status in “linux” package in Ubuntu: Incomplete Bug description: I need to use several IPs on interface in Linux, and switch it, but it's not working.br for example: # ifconfig eth0 Link encap:Ethernet HWaddr 90:2b:34:33:80:65 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::922b:34ff:fe33:8065/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:13220652 errors:0 dropped:32864 overruns:0 frame:0 TX packets:8296620 errors:0 dropped:0 overruns:0 carrier:1 collisions:0 txqueuelen:1000 RX bytes:16166162509 (16.1 GB) TX bytes:2186645852 (2.1 GB) Interrupt:48 eth0:1Link encap:Ethernet HWaddr 90:2b:34:33:80:65 inet addr:192.168.1.99 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:48 loLink encap:Локальная петля (Loopback) inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:276685 errors:0 dropped:0 overruns:0 frame:0 TX packets:276685 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:21387439 (21.3 MB) TX bytes:21387439 (21.3 MB) # ip route 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 scope link src 192.168.1.99 # ping 192.168.1.50 PING 192.168.1.50 (192.168.1.50) 56(84) bytes of data. 64 bytes from 192.168.1.50: icmp_req=1 ttl=255 time=1.21 ms 64 bytes from 192.168.1.50: icmp_req=2 ttl=255 time=1.07 ms 64 bytes from 192.168.1.50: icmp_req=3 ttl=255 time=1.05 ms and then i use Curl # curl 192.168.1.50 and tcpdump: 13:24:02.009094 IP 192.168.1.1 192.168.1.50: ICMP echo request, id 8919, seq 347, length 64 E..T..@.@..%...2...s..[...Pq#.. !#$%'()*+,-./01234567 13:24:02.010087 IP 192.168.1.50 192.168.1.1: ICMP echo reply, id 8919, seq 347, length 64 E..T...2...s..[...Pq#.. !#$%'()*+,-./01234567 13:43:40.006264 IP 192.168.1.1.48275 192.168.1.50.80: Flags [S], seq 3496592766, win 14600, options [mss 1460,sackOK,TS val 15698502 ecr 0,nop,wscale 7], length 0 E..O8@.@.h2...P.i.~..9 ...F 13:43:40.007663 IP 192.168.1.50.80 192.168.1.1.48275: Flags [S.], seq 3006420619, ack 3496592767, win 5792, options [mss 1460,sackOK,TS val 151247914 ecr 15698502,nop,wscale 0], length 0 E@.@..8...2.P...2V..i. ..*...F and source ip is still 192.168.1.1, what am i doing wrong? UPD: BTW, just tryed same thing on Ubuntu 10.04 with 2.6.32 kernel, everything works good, and you even dont need to add -I to ping command, it seams in my kernel (3.2.0) somebody broken this feature. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: kernel-package (not installed) ProcVersionSignature: Ubuntu 3.2.0-34.53-generic 3.2.33 Uname: Linux 3.2.0-34-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu15 Architecture: amd64 Date: Thu Dec 27 14:29:48 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True SourcePackage: kernel-package UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sets 2893 F pulseaudio /dev/snd/controlC0: sets 2893 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. DistroRelease: Ubuntu 12.10 InstallationDate: Installed on 2012-08-01 (147 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-21-generic root=UUID=56bd663f-860b-4d3d-b9f7-af02f9129847 ro ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 RelatedPackageVersions: linux-restricted-modules-3.5.0-21-generic N/A linux-backports-modules-3.5.0-21-generic N/A linux-firmware1.95
[Kernel-packages] [Bug 1204604] Re: panic during boot – 3.8.0-26
payload, could you please provide the full computer model as noted on the sticker? ** Tags added: needs-full-computer-model ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- 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/1204604 Title: panic during boot – 3.8.0-26 Status in “linux” package in Ubuntu: Incomplete Bug description: Hi, I attached screenshots of the panic. on 13.04 during boot, somewhere during starting of /etc/init/ services kernel 3.8.0-19 and 3.8.0-26 panics. I made a quick search but didn't found a related report. Though I found a quick fix in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322 I installed 3.7.0 as mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1144322/comments/23 to keep on working. I can't use `ubuntu-bug linux` cause I can't boot with the panicing kernel. * Boot never succeeds * but sometimes it shows a panic trace * sometimes it flickers to black or to frozen mouse pointer like shown in vid.mp4 * once it showed a panic trace and after some seconds it printed even more screen filling stack trace, and when again even more Though I spotted panics with 3.8.0-19, I only did screenshots and multiple boots with 3.8.0-26. This is new, introduced since do-release-upgrade from 12.10 to 13.04 yesterday. Please contact me when I can provide more information. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: this 3156 F pulseaudio CRDA: country DE: (2400 - 2483 @ 40), (N/A, 20) (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS (5470 - 5725 @ 40), (N/A, 26), DFS CasperVersion: 1.331 DistroRelease: Ubuntu 13.04 LiveMediaBuild: This MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/532U3C MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: cdrom-detect/try-usb=true noprompt boot=casper floppy.allowed_drive_mask=0 ignore_uuid live-media-path=/multiboot/ubuntu130464/casper/ file=/multiboot/ubuntu130464/preseed/ubuntu.seed initrd=/multiboot/ubuntu130464/casper/initrd.lz splash -- BOOT_IMAGE=/multiboot/ubuntu130464/casper/vmlinuz.efi ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/20/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P03ABH dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP530U3C-A0MDE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03ABH:bd09/20/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C/532U3C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP530U3C-A0MDE:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C/532U3C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1204604/+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 1099098] Re: Mainline Kernel 3.8.0 , black screen after boot with acer v3-771g
=KK=, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal: ubuntu-bug linux For more on this, please see the Ubuntu Kernel team article: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports the Ubuntu Bug Control team and Ubuntu Bug Squad team article: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue and Ubuntu Community article: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette When opening up the new report, please feel free to subscribe me to it. Please note, not filing a new report would delay your problem being addressed as quickly as possible. Thank you for your understanding. -- 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/1099098 Title: Mainline Kernel 3.8.0 , black screen after boot with acer v3-771g Status in “linux” package in Ubuntu: Expired Bug description: Hello, the problem only occurs with kernel 3.8.0. After installing mainline kernel 3.8.0, i get immediately after boot a black screen ( display turns off ). The problem also occurs with the ubuntu- livecd 13.04 daily (with kernel 3.8.0). Ubuntu 13.04 daily cd work with kernel 3.7 without problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1099098/+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 1173725] Re: [Acer Aspire V5-171] Backlight cannot be adjusted unless passing acpi_backlight=vendor
** Tags added: regression-potential -- 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/1173725 Title: [Acer Aspire V5-171] Backlight cannot be adjusted unless passing acpi_backlight=vendor Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Incomplete Bug description: The boot parameter is suggested as a fix for this model by http://www.linlap.com/acer_aspire_v5-171 (so if it would help, I would suggest classing this bug as confirmed). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.29 [modified: boot/vmlinuz-3.8.0-19-generic] ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alan 1919 F pulseaudio Date: Sat Apr 27 19:59:23 2013 InstallationDate: Installed on 2013-04-27 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer V5-171 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic.efi.signed root=UUID=ad03cbd3-39e0-4f7e-b0ab-e1ef3abaa88e ro acpi_backlight=vendor quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.04 dmi.modalias: dmi:bvnAcer:bvrV2.04:bd09/14/2012:svnAcer:pnV5-171:pvrV2.04:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.04: dmi.product.name: V5-171 dmi.product.version: V2.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1173725/+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 1210104] Re: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51
3.2.0-51 kernel log ** Attachment added: Kernel log from 3.2.0-51 (that fails to start FakeRAID) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210104/+attachment/3764809/+files/3.2.0-51.log -- 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/1210104 Title: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51 Status in “linux” package in Ubuntu: Incomplete Bug description: I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu 12.04 for months. I'm using the MDADM version and not DMRAID. It has been working fine other than a couple minor issues with clean shutdowns that I fixed by tweaking a couple of the scripts under /etc. I upgraded to the latest Linux kernel (3.2.0-51) and my FakeRAID stopped working, probably because auto-detection failed to see the RAID array. Everything works fine with the previous kernel image, 3.2.0-49. Here is /proc/mdstat with the 3.2.0-49 generic kernel image: Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sdb[1] sdc[0] 976758784 blocks super external:/md127/0 [2/2] [UU] md127 : inactive sdb[1](S) sdc[0](S) 6306 blocks super external:imsm The /proc/mdstat file is empty (other than listing personalities) in 3.2.0-51. Note that the sdb and sdc drives are recognized by 3.2.0-51, and their partition tables look reasonable, so I don't see any issues with 3.2.0-51 actually seeing the physical drives. The problem appears to be that the MD driver doesn't detect the external RAID (aka 'imsm') metadata created by Intel fakeraid. Here's the additional data requested for new bug reports: lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 apt-cache policy linux-image-3.2.0-51-generic linux-image-3.2.0-51-generic: Installed: 3.2.0-51.77 Candidate: 3.2.0-51.77 Version table: *** 3.2.0-51.77 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status FWIW, here's the apt-cache data on the previous kernel where fakeraid worked correctly: apt-cache policy linux-image-3.2.0-49-generic linux-image-3.2.0-49-generic: Installed: 3.2.0-49.75 Candidate: 3.2.0-49.75 Version table: *** 3.2.0-49.75 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status I will attach the kernel.log for booting 3.2.0-49 and 3.2.0-51. I've looked at them and all I see is that 3.2.0-49 'binds' the RAID array components and 3.2.0-51 doesn't. Here's a snippet from 3.2.0-49 where it starts my RAID. This is absent in 3.2.0-51. Aug 6 06:53:46 canopus kernel: [2.088509] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.150987] md: bindsdc Aug 6 06:53:46 canopus kernel: [2.151022] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.151746] md: raid1 personality registered for level 1 Aug 6 06:53:46 canopus kernel: [2.152167] bio: create slab bio-1 at 1 Aug 6 06:53:46 canopus kernel: [2.152239] md/raid1:md126: active with 2 out of 2 mirrors Aug 6 06:53:46 canopus kernel: [2.152249] md126: detected capacity change from 0 to 1000200994816 Aug 6 06:53:46 canopus kernel: [2.153111] md126: p1 p2 p3 p4 p5 p6 p7 Any suggestions on how to troubleshoot and/or fix this? There's no point bisecting the kernel images given the regression has just appeared in 3.2.0-51 and, AFAIK, there was never a release of a '3.2.0-50' kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210104/+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 1210104] [NEW] Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51
Public bug reported: I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu 12.04 for months. I'm using the MDADM version and not DMRAID. It has been working fine other than a couple minor issues with clean shutdowns that I fixed by tweaking a couple of the scripts under /etc. I upgraded to the latest Linux kernel (3.2.0-51) and my FakeRAID stopped working, probably because auto-detection failed to see the RAID array. Everything works fine with the previous kernel image, 3.2.0-49. Here is /proc/mdstat with the 3.2.0-49 generic kernel image: Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sdb[1] sdc[0] 976758784 blocks super external:/md127/0 [2/2] [UU] md127 : inactive sdb[1](S) sdc[0](S) 6306 blocks super external:imsm The /proc/mdstat file is empty (other than listing personalities) in 3.2.0-51. Note that the sdb and sdc drives are recognized by 3.2.0-51, and their partition tables look reasonable, so I don't see any issues with 3.2.0-51 actually seeing the physical drives. The problem appears to be that the MD driver doesn't detect the external RAID (aka 'imsm') metadata created by Intel fakeraid. Here's the additional data requested for new bug reports: lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 apt-cache policy linux-image-3.2.0-51-generic linux-image-3.2.0-51-generic: Installed: 3.2.0-51.77 Candidate: 3.2.0-51.77 Version table: *** 3.2.0-51.77 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status FWIW, here's the apt-cache data on the previous kernel where fakeraid worked correctly: apt-cache policy linux-image-3.2.0-49-generic linux-image-3.2.0-49-generic: Installed: 3.2.0-49.75 Candidate: 3.2.0-49.75 Version table: *** 3.2.0-49.75 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status I will attach the kernel.log for booting 3.2.0-49 and 3.2.0-51. I've looked at them and all I see is that 3.2.0-49 'binds' the RAID array components and 3.2.0-51 doesn't. Here's a snippet from 3.2.0-49 where it starts my RAID. This is absent in 3.2.0-51. Aug 6 06:53:46 canopus kernel: [2.088509] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.150987] md: bindsdc Aug 6 06:53:46 canopus kernel: [2.151022] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.151746] md: raid1 personality registered for level 1 Aug 6 06:53:46 canopus kernel: [2.152167] bio: create slab bio-1 at 1 Aug 6 06:53:46 canopus kernel: [2.152239] md/raid1:md126: active with 2 out of 2 mirrors Aug 6 06:53:46 canopus kernel: [2.152249] md126: detected capacity change from 0 to 1000200994816 Aug 6 06:53:46 canopus kernel: [2.153111] md126: p1 p2 p3 p4 p5 p6 p7 Any suggestions on how to troubleshoot and/or fix this? There's no point bisecting the kernel images given the regression has just appeared in 3.2.0-51 and, AFAIK, there was never a release of a '3.2.0-50' kernel. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: needs-kernel-logs needs-upstream-testing regression-release ** Attachment added: Kernel.log from 3.2.0-49 (that works) https://bugs.launchpad.net/bugs/1210104/+attachment/3764808/+files/3.2.0-49.log -- 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/1210104 Title: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51 Status in “linux” package in Ubuntu: Incomplete Bug description: I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu 12.04 for months. I'm using the MDADM version and not DMRAID. It has been working fine other than a couple minor issues with clean shutdowns that I fixed by tweaking a couple of the scripts under /etc. I upgraded to the latest Linux kernel (3.2.0-51) and my FakeRAID stopped working, probably because auto-detection failed to see the RAID array. Everything works fine with the previous kernel image, 3.2.0-49. Here is /proc/mdstat with the 3.2.0-49 generic kernel image: Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sdb[1] sdc[0] 976758784 blocks super external:/md127/0 [2/2] [UU] md127 : inactive sdb[1](S) sdc[0](S) 6306 blocks super external:imsm The /proc/mdstat file is empty (other than listing personalities) in 3.2.0-51. Note that the sdb and sdc drives are recognized by 3.2.0-51, and their partition tables look reasonable, so I don't see any issues with 3.2.0-51 actually seeing the physical drives. The problem appears to be that the MD driver doesn't detect the external RAID (aka 'imsm') metadata created by Intel fakeraid.
[Kernel-packages] [Bug 1210104] Re: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51
Ben McCann, thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1210104 When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags added: needs-kernel-logs needs-upstream-testing regression- release ** Changed in: linux (Ubuntu) Status: New = Incomplete -- 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/1210104 Title: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51 Status in “linux” package in Ubuntu: Incomplete Bug description: I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu 12.04 for months. I'm using the MDADM version and not DMRAID. It has been working fine other than a couple minor issues with clean shutdowns that I fixed by tweaking a couple of the scripts under /etc. I upgraded to the latest Linux kernel (3.2.0-51) and my FakeRAID stopped working, probably because auto-detection failed to see the RAID array. Everything works fine with the previous kernel image, 3.2.0-49. Here is /proc/mdstat with the 3.2.0-49 generic kernel image: Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sdb[1] sdc[0] 976758784 blocks super external:/md127/0 [2/2] [UU] md127 : inactive sdb[1](S) sdc[0](S) 6306 blocks super external:imsm The /proc/mdstat file is empty (other than listing personalities) in 3.2.0-51. Note that the sdb and sdc drives are recognized by 3.2.0-51, and their partition tables look reasonable, so I don't see any issues with 3.2.0-51 actually seeing the physical drives. The problem appears to be that the MD driver doesn't detect the external RAID (aka 'imsm') metadata created by Intel fakeraid. Here's the additional data requested for new bug reports: lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 apt-cache policy linux-image-3.2.0-51-generic linux-image-3.2.0-51-generic: Installed: 3.2.0-51.77 Candidate: 3.2.0-51.77 Version table: *** 3.2.0-51.77 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status FWIW, here's the apt-cache data on the previous kernel where fakeraid worked correctly: apt-cache policy linux-image-3.2.0-49-generic linux-image-3.2.0-49-generic: Installed: 3.2.0-49.75 Candidate: 3.2.0-49.75 Version table: *** 3.2.0-49.75 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status I will attach the kernel.log for booting 3.2.0-49 and 3.2.0-51. I've looked at them and all I see is that 3.2.0-49 'binds' the RAID array components and 3.2.0-51 doesn't. Here's a snippet from 3.2.0-49 where it starts my RAID. This is absent in 3.2.0-51. Aug 6 06:53:46 canopus kernel: [2.088509] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.150987] md: bindsdc Aug 6 06:53:46 canopus kernel: [2.151022] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.151746] md: raid1 personality registered for level 1 Aug 6 06:53:46 canopus kernel: [2.152167] bio: create slab bio-1 at 1 Aug 6 06:53:46 canopus kernel: [2.152239] md/raid1:md126: active with 2 out of 2 mirrors Aug 6 06:53:46 canopus kernel: [2.152249] md126: detected capacity change from 0 to 1000200994816 Aug 6 06:53:46 canopus kernel: [2.153111] md126: p1 p2 p3 p4 p5 p6 p7 Any suggestions on how to troubleshoot and/or fix this? There's no point bisecting the kernel images given the regression has just appeared in 3.2.0-51 and, AFAIK, there was never a release of a '3.2.0-50' kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210104/+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 814894] Re: [Fit-PC2i] Kernel hangs on high network throughput
Kasper Dupont, I was unable to find a bug report with number 1210092 as it
notes:
Lost something?
This page does not exist, or you may not have permission to see it.
Would it be marked Private? If not, could you please provide a URL?
--
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/814894
Title:
[Fit-PC2i] Kernel hangs on high network throughput
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
If A Fit-PC2i receives more than 200Mbit/s of network traffic the
kernel will hang. Cursor stops blinking, machine doesn't respond to
keyboard and mouse input, no longer responds to ARP requests or any
other network traffic.
The problem is triggered every time a 10.04.3 system with kernel
version 2.6.32-33-generic receives more than 200Mbit/s of network
traffic. The bug affects both live system as well as fully installed
system.
The bug can be reproduced by downloading a 1GB file from a server on
the LAN. The bug is only triggered if more than 200Mbit/s is
transfered. If any link on the path between client and server is
100Mbit/s or less the bug cannot be reproduced.
The 8.04.4 live system is not affected by this problem and can receive
600Mbit/s without problems on the same hardware.
Marking this as a security problem because it can in principle be used
to perform a DoS attack.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image (not installed)
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-33.70-generic 2.6.32.41+drm33.18
Uname: Linux 2.6.32-33-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: MID [HDA Intel MID], device 0: ALC662 rev1 Analog [ALC662 rev1
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kasperd1453 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'MID'/'HDA Intel MID at 0xb005 irq 22'
Mixer name : 'Realtek ALC662 rev1'
Components : 'HDA:10ec0662,10ec0662,00100101'
Controls : 33
Simple ctrls : 19
Date: Sat Jul 23 01:43:06 2011
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=e14584e1-caed-4150-9e25-e364d27bebe3
InstallationMedia: Ubuntu 10.04.3 LTS Lucid Lynx - Release i386 (20110720.1)
MachineType: CompuLab CM-iAM/SBC-FITPC2i
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-33-generic
root=UUID=8bf29c49-594d-41b8-8513-ac3cf4bf4e1b ro rootdir=lucid
ProcEnviron:
LANG=en_DK.utf8
SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.7
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
StagingDrivers: rt2870sta
Title: [STAGING]
dmi.bios.date: 09/14/2010
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: NAPA0001.86C..D.1009141059
dmi.board.name: CM-iAM/SBC-FITPC2i
dmi.board.vendor: Intel Corporation
dmi.board.version: 1.x
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: OEM
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvrNAPA0001.86C..D.1009141059:bd09/14/2010:svnCompuLab:pnCM-iAM/SBC-FITPC2i:pvrNotApplicable:rvnIntelCorporation:rnCM-iAM/SBC-FITPC2i:rvr1.x:cvnOEM:ct1:cvrN/A:
dmi.product.name: CM-iAM/SBC-FITPC2i
dmi.product.version: Not Applicable
dmi.sys.vendor: CompuLab
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/814894/+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 1209503] Re: [Acer Extensa 5220] suspend/resume failure
Bogdan Arabadzhi, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. For example: kernel-fixed-upstream-v3.11-rc4 This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag: needs-upstream-testing If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER As well, please remove the tag: needs-upstream-testing If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags: kernel-unable-to-test-upstream kernel-unable-to-test-upstream-VERSION-NUMBER Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Tags added: latest-bios-v1.35 needs-upstream-testing regression- potential -- 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/1209503 Title: [Acer Extensa 5220] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: After boot it's appeared.. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.10.0-6-generic 3.10.0-6.17 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bogdan 1776 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) Date: Tue Aug 6 12:27:33 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=29645983-b508-4fa3-95df-26be802a8c59 InstallationDate: Installed on 2013-08-04 (3 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130804) InterpreterPath: /usr/bin/python3.3 MachineType: Acer Extensa 5220 MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=c92f5314-e9e0-4c87-a6bb-c478701a0127 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware1.113 SourcePackage: linux Title: [Acer Extensa 5220] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 07/03/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.35 dmi.board.name: Columbia dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.asset.tag: None dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Extensa 5220 dmi.product.version: 0100 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1209503/+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 1208455] Re: general protection fault running apt-get inside double nested kvm VM
Testing with linux-image-3.11.0-0-generic from -proposed with nested=Y in all 3 environments does appear to solve this issue. -- 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/1208455 Title: general protection fault running apt-get inside double nested kvm VM Status in “linux” package in Ubuntu: Incomplete Status in “qemu-kvm” package in Ubuntu: New Bug description: Attempting to run apt-get in a nested vm hosted in OpenStack results in a general protection fault in the kernel in the nested VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1173725] Re: [Acer Aspire V5-171] Backlight cannot be adjusted unless passing acpi_backlight=vendor
Sorry, I don't think the backlight problem on the V5-171 is a regression. I've never had it work as expected. I've now tried the acpi_osi=!Windows 2012 test, to see if this machine could be added to the temporary blacklist. I.e. whether my bug was a regression caused when Linux added the Windows 2012 OSI string.[1] Unfortunately that boot option didn't help. [1] https://bugzilla.kernel.org/show_bug.cgi?id=51231#c137 The result from testing v3.11-rc2 is that it does fix the problem. And as expected, the revert in v3.11-rc3 breaks it again. To answer the question about firmware upgrades, I'm not going to try that unless it helps upstream. It's not worth reflashing at my own risk just to avoid passing acpi_backlight=vendor. -- 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/1173725 Title: [Acer Aspire V5-171] Backlight cannot be adjusted unless passing acpi_backlight=vendor Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Incomplete Bug description: The boot parameter is suggested as a fix for this model by http://www.linlap.com/acer_aspire_v5-171 (so if it would help, I would suggest classing this bug as confirmed). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.29 [modified: boot/vmlinuz-3.8.0-19-generic] ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alan 1919 F pulseaudio Date: Sat Apr 27 19:59:23 2013 InstallationDate: Installed on 2013-04-27 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer V5-171 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic.efi.signed root=UUID=ad03cbd3-39e0-4f7e-b0ab-e1ef3abaa88e ro acpi_backlight=vendor quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.04 dmi.modalias: dmi:bvnAcer:bvrV2.04:bd09/14/2012:svnAcer:pnV5-171:pvrV2.04:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.04: dmi.product.name: V5-171 dmi.product.version: V2.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1173725/+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 1210104] Card0.Codecs.codec.0.txt
apport information ** Attachment added: Card0.Codecs.codec.0.txt https://bugs.launchpad.net/bugs/1210104/+attachment/3764828/+files/Card0.Codecs.codec.0.txt -- 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/1210104 Title: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51 Status in “linux” package in Ubuntu: Confirmed Bug description: I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu 12.04 for months. I'm using the MDADM version and not DMRAID. It has been working fine other than a couple minor issues with clean shutdowns that I fixed by tweaking a couple of the scripts under /etc. I upgraded to the latest Linux kernel (3.2.0-51) and my FakeRAID stopped working, probably because auto-detection failed to see the RAID array. Everything works fine with the previous kernel image, 3.2.0-49. Here is /proc/mdstat with the 3.2.0-49 generic kernel image: Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sdb[1] sdc[0] 976758784 blocks super external:/md127/0 [2/2] [UU] md127 : inactive sdb[1](S) sdc[0](S) 6306 blocks super external:imsm The /proc/mdstat file is empty (other than listing personalities) in 3.2.0-51. Note that the sdb and sdc drives are recognized by 3.2.0-51, and their partition tables look reasonable, so I don't see any issues with 3.2.0-51 actually seeing the physical drives. The problem appears to be that the MD driver doesn't detect the external RAID (aka 'imsm') metadata created by Intel fakeraid. Here's the additional data requested for new bug reports: lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 apt-cache policy linux-image-3.2.0-51-generic linux-image-3.2.0-51-generic: Installed: 3.2.0-51.77 Candidate: 3.2.0-51.77 Version table: *** 3.2.0-51.77 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status FWIW, here's the apt-cache data on the previous kernel where fakeraid worked correctly: apt-cache policy linux-image-3.2.0-49-generic linux-image-3.2.0-49-generic: Installed: 3.2.0-49.75 Candidate: 3.2.0-49.75 Version table: *** 3.2.0-49.75 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status I will attach the kernel.log for booting 3.2.0-49 and 3.2.0-51. I've looked at them and all I see is that 3.2.0-49 'binds' the RAID array components and 3.2.0-51 doesn't. Here's a snippet from 3.2.0-49 where it starts my RAID. This is absent in 3.2.0-51. Aug 6 06:53:46 canopus kernel: [2.088509] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.150987] md: bindsdc Aug 6 06:53:46 canopus kernel: [2.151022] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.151746] md: raid1 personality registered for level 1 Aug 6 06:53:46 canopus kernel: [2.152167] bio: create slab bio-1 at 1 Aug 6 06:53:46 canopus kernel: [2.152239] md/raid1:md126: active with 2 out of 2 mirrors Aug 6 06:53:46 canopus kernel: [2.152249] md126: detected capacity change from 0 to 1000200994816 Aug 6 06:53:46 canopus kernel: [2.153111] md126: p1 p2 p3 p4 p5 p6 p7 Any suggestions on how to troubleshoot and/or fix this? There's no point bisecting the kernel images given the regression has just appeared in 3.2.0-51 and, AFAIK, there was never a release of a '3.2.0-50' kernel. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bmccann2893 F pulseaudio /dev/snd/controlC0: bmccann2893 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf743 irq 51' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104384fb,00100302' Controls : 44 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17' Mixer name : 'Nvidia GPU 41 HDMI/DP' Components : 'HDA:10de0041,14622871,00100100' Controls : 24 Simple ctrls : 4 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=ce0ec46d-5a8e-4ba4-9049-ed08a896696b InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120424) MachineType: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine:
[Kernel-packages] [Bug 1210104] Re: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51
apport information ** Tags added: apport-collected precise staging ** Description changed: I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu 12.04 for months. I'm using the MDADM version and not DMRAID. It has been working fine other than a couple minor issues with clean shutdowns that I fixed by tweaking a couple of the scripts under /etc. I upgraded to the latest Linux kernel (3.2.0-51) and my FakeRAID stopped working, probably because auto-detection failed to see the RAID array. Everything works fine with the previous kernel image, 3.2.0-49. Here is /proc/mdstat with the 3.2.0-49 generic kernel image: Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sdb[1] sdc[0] 976758784 blocks super external:/md127/0 [2/2] [UU] md127 : inactive sdb[1](S) sdc[0](S) 6306 blocks super external:imsm The /proc/mdstat file is empty (other than listing personalities) in 3.2.0-51. Note that the sdb and sdc drives are recognized by 3.2.0-51, and their partition tables look reasonable, so I don't see any issues with 3.2.0-51 actually seeing the physical drives. The problem appears to be that the MD driver doesn't detect the external RAID (aka 'imsm') metadata created by Intel fakeraid. Here's the additional data requested for new bug reports: lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 apt-cache policy linux-image-3.2.0-51-generic linux-image-3.2.0-51-generic: Installed: 3.2.0-51.77 Candidate: 3.2.0-51.77 Version table: *** 3.2.0-51.77 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status FWIW, here's the apt-cache data on the previous kernel where fakeraid worked correctly: apt-cache policy linux-image-3.2.0-49-generic linux-image-3.2.0-49-generic: Installed: 3.2.0-49.75 Candidate: 3.2.0-49.75 Version table: *** 3.2.0-49.75 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status I will attach the kernel.log for booting 3.2.0-49 and 3.2.0-51. I've looked at them and all I see is that 3.2.0-49 'binds' the RAID array components and 3.2.0-51 doesn't. Here's a snippet from 3.2.0-49 where it starts my RAID. This is absent in 3.2.0-51. Aug 6 06:53:46 canopus kernel: [2.088509] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.150987] md: bindsdc Aug 6 06:53:46 canopus kernel: [2.151022] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.151746] md: raid1 personality registered for level 1 Aug 6 06:53:46 canopus kernel: [2.152167] bio: create slab bio-1 at 1 Aug 6 06:53:46 canopus kernel: [2.152239] md/raid1:md126: active with 2 out of 2 mirrors Aug 6 06:53:46 canopus kernel: [2.152249] md126: detected capacity change from 0 to 1000200994816 Aug 6 06:53:46 canopus kernel: [2.153111] md126: p1 p2 p3 p4 p5 p6 p7 - Any suggestions on how to troubleshoot and/or fix this? There's no point - bisecting the kernel images given the regression has just appeared in - 3.2.0-51 and, AFAIK, there was never a release of a '3.2.0-50' kernel. + Any suggestions on how to troubleshoot and/or fix this? There's no point bisecting the kernel images given the regression has just appeared in 3.2.0-51 and, AFAIK, there was never a release of a '3.2.0-50' kernel. + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. + ApportVersion: 2.0.1-0ubuntu17.3 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: bmccann2893 F pulseaudio + /dev/snd/controlC0: bmccann2893 F pulseaudio + CRDA: Error: [Errno 2] No such file or directory + Card0.Amixer.info: + Card hw:0 'PCH'/'HDA Intel PCH at 0xf743 irq 51' +Mixer name : 'Realtek ALC892' +Components : 'HDA:10ec0892,104384fb,00100302' +Controls : 44 +Simple ctrls : 21 + Card1.Amixer.info: + Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17' +Mixer name : 'Nvidia GPU 41 HDMI/DP' +Components : 'HDA:10de0041,14622871,00100100' +Controls : 24 +Simple ctrls : 4 + DistroRelease: Ubuntu 12.04 + HibernationDevice: RESUME=UUID=ce0ec46d-5a8e-4ba4-9049-ed08a896696b + InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120424) + MachineType: System manufacturer System Product Name + MarkForUpload: True + NonfreeKernelModules: nvidia + Package: linux (not installed) + ProcEnviron: + LANGUAGE= + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/tcsh + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-49-generic root=UUID=90c7fb84-e571-4f25-b91a-0a8e9915763f ro quiet splash nomodeset vt.handoff=7 +
[Kernel-packages] [Bug 1210104] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1210104/+attachment/3764826/+files/BootDmesg.txt -- 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/1210104 Title: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51 Status in “linux” package in Ubuntu: Confirmed Bug description: I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu 12.04 for months. I'm using the MDADM version and not DMRAID. It has been working fine other than a couple minor issues with clean shutdowns that I fixed by tweaking a couple of the scripts under /etc. I upgraded to the latest Linux kernel (3.2.0-51) and my FakeRAID stopped working, probably because auto-detection failed to see the RAID array. Everything works fine with the previous kernel image, 3.2.0-49. Here is /proc/mdstat with the 3.2.0-49 generic kernel image: Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sdb[1] sdc[0] 976758784 blocks super external:/md127/0 [2/2] [UU] md127 : inactive sdb[1](S) sdc[0](S) 6306 blocks super external:imsm The /proc/mdstat file is empty (other than listing personalities) in 3.2.0-51. Note that the sdb and sdc drives are recognized by 3.2.0-51, and their partition tables look reasonable, so I don't see any issues with 3.2.0-51 actually seeing the physical drives. The problem appears to be that the MD driver doesn't detect the external RAID (aka 'imsm') metadata created by Intel fakeraid. Here's the additional data requested for new bug reports: lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 apt-cache policy linux-image-3.2.0-51-generic linux-image-3.2.0-51-generic: Installed: 3.2.0-51.77 Candidate: 3.2.0-51.77 Version table: *** 3.2.0-51.77 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status FWIW, here's the apt-cache data on the previous kernel where fakeraid worked correctly: apt-cache policy linux-image-3.2.0-49-generic linux-image-3.2.0-49-generic: Installed: 3.2.0-49.75 Candidate: 3.2.0-49.75 Version table: *** 3.2.0-49.75 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status I will attach the kernel.log for booting 3.2.0-49 and 3.2.0-51. I've looked at them and all I see is that 3.2.0-49 'binds' the RAID array components and 3.2.0-51 doesn't. Here's a snippet from 3.2.0-49 where it starts my RAID. This is absent in 3.2.0-51. Aug 6 06:53:46 canopus kernel: [2.088509] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.150987] md: bindsdc Aug 6 06:53:46 canopus kernel: [2.151022] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.151746] md: raid1 personality registered for level 1 Aug 6 06:53:46 canopus kernel: [2.152167] bio: create slab bio-1 at 1 Aug 6 06:53:46 canopus kernel: [2.152239] md/raid1:md126: active with 2 out of 2 mirrors Aug 6 06:53:46 canopus kernel: [2.152249] md126: detected capacity change from 0 to 1000200994816 Aug 6 06:53:46 canopus kernel: [2.153111] md126: p1 p2 p3 p4 p5 p6 p7 Any suggestions on how to troubleshoot and/or fix this? There's no point bisecting the kernel images given the regression has just appeared in 3.2.0-51 and, AFAIK, there was never a release of a '3.2.0-50' kernel. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bmccann2893 F pulseaudio /dev/snd/controlC0: bmccann2893 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf743 irq 51' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104384fb,00100302' Controls : 44 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17' Mixer name : 'Nvidia GPU 41 HDMI/DP' Components : 'HDA:10de0041,14622871,00100100' Controls : 24 Simple ctrls : 4 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=ce0ec46d-5a8e-4ba4-9049-ed08a896696b InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120424) MachineType: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine:
[Kernel-packages] [Bug 1210104] AplayDevices.txt
apport information ** Attachment added: AplayDevices.txt https://bugs.launchpad.net/bugs/1210104/+attachment/3764824/+files/AplayDevices.txt -- 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/1210104 Title: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51 Status in “linux” package in Ubuntu: Confirmed Bug description: I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu 12.04 for months. I'm using the MDADM version and not DMRAID. It has been working fine other than a couple minor issues with clean shutdowns that I fixed by tweaking a couple of the scripts under /etc. I upgraded to the latest Linux kernel (3.2.0-51) and my FakeRAID stopped working, probably because auto-detection failed to see the RAID array. Everything works fine with the previous kernel image, 3.2.0-49. Here is /proc/mdstat with the 3.2.0-49 generic kernel image: Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sdb[1] sdc[0] 976758784 blocks super external:/md127/0 [2/2] [UU] md127 : inactive sdb[1](S) sdc[0](S) 6306 blocks super external:imsm The /proc/mdstat file is empty (other than listing personalities) in 3.2.0-51. Note that the sdb and sdc drives are recognized by 3.2.0-51, and their partition tables look reasonable, so I don't see any issues with 3.2.0-51 actually seeing the physical drives. The problem appears to be that the MD driver doesn't detect the external RAID (aka 'imsm') metadata created by Intel fakeraid. Here's the additional data requested for new bug reports: lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 apt-cache policy linux-image-3.2.0-51-generic linux-image-3.2.0-51-generic: Installed: 3.2.0-51.77 Candidate: 3.2.0-51.77 Version table: *** 3.2.0-51.77 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status FWIW, here's the apt-cache data on the previous kernel where fakeraid worked correctly: apt-cache policy linux-image-3.2.0-49-generic linux-image-3.2.0-49-generic: Installed: 3.2.0-49.75 Candidate: 3.2.0-49.75 Version table: *** 3.2.0-49.75 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status I will attach the kernel.log for booting 3.2.0-49 and 3.2.0-51. I've looked at them and all I see is that 3.2.0-49 'binds' the RAID array components and 3.2.0-51 doesn't. Here's a snippet from 3.2.0-49 where it starts my RAID. This is absent in 3.2.0-51. Aug 6 06:53:46 canopus kernel: [2.088509] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.150987] md: bindsdc Aug 6 06:53:46 canopus kernel: [2.151022] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.151746] md: raid1 personality registered for level 1 Aug 6 06:53:46 canopus kernel: [2.152167] bio: create slab bio-1 at 1 Aug 6 06:53:46 canopus kernel: [2.152239] md/raid1:md126: active with 2 out of 2 mirrors Aug 6 06:53:46 canopus kernel: [2.152249] md126: detected capacity change from 0 to 1000200994816 Aug 6 06:53:46 canopus kernel: [2.153111] md126: p1 p2 p3 p4 p5 p6 p7 Any suggestions on how to troubleshoot and/or fix this? There's no point bisecting the kernel images given the regression has just appeared in 3.2.0-51 and, AFAIK, there was never a release of a '3.2.0-50' kernel. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bmccann2893 F pulseaudio /dev/snd/controlC0: bmccann2893 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf743 irq 51' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104384fb,00100302' Controls : 44 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17' Mixer name : 'Nvidia GPU 41 HDMI/DP' Components : 'HDA:10de0041,14622871,00100100' Controls : 24 Simple ctrls : 4 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=ce0ec46d-5a8e-4ba4-9049-ed08a896696b InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120424) MachineType: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine:
[Kernel-packages] [Bug 1210104] AlsaDevices.txt
apport information ** Attachment added: AlsaDevices.txt https://bugs.launchpad.net/bugs/1210104/+attachment/3764823/+files/AlsaDevices.txt -- 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/1210104 Title: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51 Status in “linux” package in Ubuntu: Confirmed Bug description: I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu 12.04 for months. I'm using the MDADM version and not DMRAID. It has been working fine other than a couple minor issues with clean shutdowns that I fixed by tweaking a couple of the scripts under /etc. I upgraded to the latest Linux kernel (3.2.0-51) and my FakeRAID stopped working, probably because auto-detection failed to see the RAID array. Everything works fine with the previous kernel image, 3.2.0-49. Here is /proc/mdstat with the 3.2.0-49 generic kernel image: Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sdb[1] sdc[0] 976758784 blocks super external:/md127/0 [2/2] [UU] md127 : inactive sdb[1](S) sdc[0](S) 6306 blocks super external:imsm The /proc/mdstat file is empty (other than listing personalities) in 3.2.0-51. Note that the sdb and sdc drives are recognized by 3.2.0-51, and their partition tables look reasonable, so I don't see any issues with 3.2.0-51 actually seeing the physical drives. The problem appears to be that the MD driver doesn't detect the external RAID (aka 'imsm') metadata created by Intel fakeraid. Here's the additional data requested for new bug reports: lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 apt-cache policy linux-image-3.2.0-51-generic linux-image-3.2.0-51-generic: Installed: 3.2.0-51.77 Candidate: 3.2.0-51.77 Version table: *** 3.2.0-51.77 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status FWIW, here's the apt-cache data on the previous kernel where fakeraid worked correctly: apt-cache policy linux-image-3.2.0-49-generic linux-image-3.2.0-49-generic: Installed: 3.2.0-49.75 Candidate: 3.2.0-49.75 Version table: *** 3.2.0-49.75 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status I will attach the kernel.log for booting 3.2.0-49 and 3.2.0-51. I've looked at them and all I see is that 3.2.0-49 'binds' the RAID array components and 3.2.0-51 doesn't. Here's a snippet from 3.2.0-49 where it starts my RAID. This is absent in 3.2.0-51. Aug 6 06:53:46 canopus kernel: [2.088509] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.150987] md: bindsdc Aug 6 06:53:46 canopus kernel: [2.151022] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.151746] md: raid1 personality registered for level 1 Aug 6 06:53:46 canopus kernel: [2.152167] bio: create slab bio-1 at 1 Aug 6 06:53:46 canopus kernel: [2.152239] md/raid1:md126: active with 2 out of 2 mirrors Aug 6 06:53:46 canopus kernel: [2.152249] md126: detected capacity change from 0 to 1000200994816 Aug 6 06:53:46 canopus kernel: [2.153111] md126: p1 p2 p3 p4 p5 p6 p7 Any suggestions on how to troubleshoot and/or fix this? There's no point bisecting the kernel images given the regression has just appeared in 3.2.0-51 and, AFAIK, there was never a release of a '3.2.0-50' kernel. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bmccann2893 F pulseaudio /dev/snd/controlC0: bmccann2893 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf743 irq 51' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104384fb,00100302' Controls : 44 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17' Mixer name : 'Nvidia GPU 41 HDMI/DP' Components : 'HDA:10de0041,14622871,00100100' Controls : 24 Simple ctrls : 4 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=ce0ec46d-5a8e-4ba4-9049-ed08a896696b InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120424) MachineType: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine:
[Kernel-packages] [Bug 1210104] Card1.Amixer.values.txt
apport information ** Attachment added: Card1.Amixer.values.txt https://bugs.launchpad.net/bugs/1210104/+attachment/3764829/+files/Card1.Amixer.values.txt -- 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/1210104 Title: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51 Status in “linux” package in Ubuntu: Confirmed Bug description: I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu 12.04 for months. I'm using the MDADM version and not DMRAID. It has been working fine other than a couple minor issues with clean shutdowns that I fixed by tweaking a couple of the scripts under /etc. I upgraded to the latest Linux kernel (3.2.0-51) and my FakeRAID stopped working, probably because auto-detection failed to see the RAID array. Everything works fine with the previous kernel image, 3.2.0-49. Here is /proc/mdstat with the 3.2.0-49 generic kernel image: Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sdb[1] sdc[0] 976758784 blocks super external:/md127/0 [2/2] [UU] md127 : inactive sdb[1](S) sdc[0](S) 6306 blocks super external:imsm The /proc/mdstat file is empty (other than listing personalities) in 3.2.0-51. Note that the sdb and sdc drives are recognized by 3.2.0-51, and their partition tables look reasonable, so I don't see any issues with 3.2.0-51 actually seeing the physical drives. The problem appears to be that the MD driver doesn't detect the external RAID (aka 'imsm') metadata created by Intel fakeraid. Here's the additional data requested for new bug reports: lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 apt-cache policy linux-image-3.2.0-51-generic linux-image-3.2.0-51-generic: Installed: 3.2.0-51.77 Candidate: 3.2.0-51.77 Version table: *** 3.2.0-51.77 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status FWIW, here's the apt-cache data on the previous kernel where fakeraid worked correctly: apt-cache policy linux-image-3.2.0-49-generic linux-image-3.2.0-49-generic: Installed: 3.2.0-49.75 Candidate: 3.2.0-49.75 Version table: *** 3.2.0-49.75 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status I will attach the kernel.log for booting 3.2.0-49 and 3.2.0-51. I've looked at them and all I see is that 3.2.0-49 'binds' the RAID array components and 3.2.0-51 doesn't. Here's a snippet from 3.2.0-49 where it starts my RAID. This is absent in 3.2.0-51. Aug 6 06:53:46 canopus kernel: [2.088509] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.150987] md: bindsdc Aug 6 06:53:46 canopus kernel: [2.151022] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.151746] md: raid1 personality registered for level 1 Aug 6 06:53:46 canopus kernel: [2.152167] bio: create slab bio-1 at 1 Aug 6 06:53:46 canopus kernel: [2.152239] md/raid1:md126: active with 2 out of 2 mirrors Aug 6 06:53:46 canopus kernel: [2.152249] md126: detected capacity change from 0 to 1000200994816 Aug 6 06:53:46 canopus kernel: [2.153111] md126: p1 p2 p3 p4 p5 p6 p7 Any suggestions on how to troubleshoot and/or fix this? There's no point bisecting the kernel images given the regression has just appeared in 3.2.0-51 and, AFAIK, there was never a release of a '3.2.0-50' kernel. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bmccann2893 F pulseaudio /dev/snd/controlC0: bmccann2893 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf743 irq 51' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104384fb,00100302' Controls : 44 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17' Mixer name : 'Nvidia GPU 41 HDMI/DP' Components : 'HDA:10de0041,14622871,00100100' Controls : 24 Simple ctrls : 4 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=ce0ec46d-5a8e-4ba4-9049-ed08a896696b InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120424) MachineType: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine:
[Kernel-packages] [Bug 1210104] ArecordDevices.txt
apport information ** Attachment added: ArecordDevices.txt https://bugs.launchpad.net/bugs/1210104/+attachment/3764825/+files/ArecordDevices.txt -- 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/1210104 Title: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51 Status in “linux” package in Ubuntu: Confirmed Bug description: I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu 12.04 for months. I'm using the MDADM version and not DMRAID. It has been working fine other than a couple minor issues with clean shutdowns that I fixed by tweaking a couple of the scripts under /etc. I upgraded to the latest Linux kernel (3.2.0-51) and my FakeRAID stopped working, probably because auto-detection failed to see the RAID array. Everything works fine with the previous kernel image, 3.2.0-49. Here is /proc/mdstat with the 3.2.0-49 generic kernel image: Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sdb[1] sdc[0] 976758784 blocks super external:/md127/0 [2/2] [UU] md127 : inactive sdb[1](S) sdc[0](S) 6306 blocks super external:imsm The /proc/mdstat file is empty (other than listing personalities) in 3.2.0-51. Note that the sdb and sdc drives are recognized by 3.2.0-51, and their partition tables look reasonable, so I don't see any issues with 3.2.0-51 actually seeing the physical drives. The problem appears to be that the MD driver doesn't detect the external RAID (aka 'imsm') metadata created by Intel fakeraid. Here's the additional data requested for new bug reports: lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 apt-cache policy linux-image-3.2.0-51-generic linux-image-3.2.0-51-generic: Installed: 3.2.0-51.77 Candidate: 3.2.0-51.77 Version table: *** 3.2.0-51.77 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status FWIW, here's the apt-cache data on the previous kernel where fakeraid worked correctly: apt-cache policy linux-image-3.2.0-49-generic linux-image-3.2.0-49-generic: Installed: 3.2.0-49.75 Candidate: 3.2.0-49.75 Version table: *** 3.2.0-49.75 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status I will attach the kernel.log for booting 3.2.0-49 and 3.2.0-51. I've looked at them and all I see is that 3.2.0-49 'binds' the RAID array components and 3.2.0-51 doesn't. Here's a snippet from 3.2.0-49 where it starts my RAID. This is absent in 3.2.0-51. Aug 6 06:53:46 canopus kernel: [2.088509] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.150987] md: bindsdc Aug 6 06:53:46 canopus kernel: [2.151022] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.151746] md: raid1 personality registered for level 1 Aug 6 06:53:46 canopus kernel: [2.152167] bio: create slab bio-1 at 1 Aug 6 06:53:46 canopus kernel: [2.152239] md/raid1:md126: active with 2 out of 2 mirrors Aug 6 06:53:46 canopus kernel: [2.152249] md126: detected capacity change from 0 to 1000200994816 Aug 6 06:53:46 canopus kernel: [2.153111] md126: p1 p2 p3 p4 p5 p6 p7 Any suggestions on how to troubleshoot and/or fix this? There's no point bisecting the kernel images given the regression has just appeared in 3.2.0-51 and, AFAIK, there was never a release of a '3.2.0-50' kernel. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bmccann2893 F pulseaudio /dev/snd/controlC0: bmccann2893 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf743 irq 51' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104384fb,00100302' Controls : 44 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17' Mixer name : 'Nvidia GPU 41 HDMI/DP' Components : 'HDA:10de0041,14622871,00100100' Controls : 24 Simple ctrls : 4 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=ce0ec46d-5a8e-4ba4-9049-ed08a896696b InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120424) MachineType: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine:
[Kernel-packages] [Bug 1210104] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/1210104/+attachment/3764832/+files/IwConfig.txt -- 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/1210104 Title: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51 Status in “linux” package in Ubuntu: Confirmed Bug description: I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu 12.04 for months. I'm using the MDADM version and not DMRAID. It has been working fine other than a couple minor issues with clean shutdowns that I fixed by tweaking a couple of the scripts under /etc. I upgraded to the latest Linux kernel (3.2.0-51) and my FakeRAID stopped working, probably because auto-detection failed to see the RAID array. Everything works fine with the previous kernel image, 3.2.0-49. Here is /proc/mdstat with the 3.2.0-49 generic kernel image: Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sdb[1] sdc[0] 976758784 blocks super external:/md127/0 [2/2] [UU] md127 : inactive sdb[1](S) sdc[0](S) 6306 blocks super external:imsm The /proc/mdstat file is empty (other than listing personalities) in 3.2.0-51. Note that the sdb and sdc drives are recognized by 3.2.0-51, and their partition tables look reasonable, so I don't see any issues with 3.2.0-51 actually seeing the physical drives. The problem appears to be that the MD driver doesn't detect the external RAID (aka 'imsm') metadata created by Intel fakeraid. Here's the additional data requested for new bug reports: lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 apt-cache policy linux-image-3.2.0-51-generic linux-image-3.2.0-51-generic: Installed: 3.2.0-51.77 Candidate: 3.2.0-51.77 Version table: *** 3.2.0-51.77 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status FWIW, here's the apt-cache data on the previous kernel where fakeraid worked correctly: apt-cache policy linux-image-3.2.0-49-generic linux-image-3.2.0-49-generic: Installed: 3.2.0-49.75 Candidate: 3.2.0-49.75 Version table: *** 3.2.0-49.75 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status I will attach the kernel.log for booting 3.2.0-49 and 3.2.0-51. I've looked at them and all I see is that 3.2.0-49 'binds' the RAID array components and 3.2.0-51 doesn't. Here's a snippet from 3.2.0-49 where it starts my RAID. This is absent in 3.2.0-51. Aug 6 06:53:46 canopus kernel: [2.088509] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.150987] md: bindsdc Aug 6 06:53:46 canopus kernel: [2.151022] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.151746] md: raid1 personality registered for level 1 Aug 6 06:53:46 canopus kernel: [2.152167] bio: create slab bio-1 at 1 Aug 6 06:53:46 canopus kernel: [2.152239] md/raid1:md126: active with 2 out of 2 mirrors Aug 6 06:53:46 canopus kernel: [2.152249] md126: detected capacity change from 0 to 1000200994816 Aug 6 06:53:46 canopus kernel: [2.153111] md126: p1 p2 p3 p4 p5 p6 p7 Any suggestions on how to troubleshoot and/or fix this? There's no point bisecting the kernel images given the regression has just appeared in 3.2.0-51 and, AFAIK, there was never a release of a '3.2.0-50' kernel. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bmccann2893 F pulseaudio /dev/snd/controlC0: bmccann2893 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf743 irq 51' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104384fb,00100302' Controls : 44 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17' Mixer name : 'Nvidia GPU 41 HDMI/DP' Components : 'HDA:10de0041,14622871,00100100' Controls : 24 Simple ctrls : 4 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=ce0ec46d-5a8e-4ba4-9049-ed08a896696b InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120424) MachineType: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine:
[Kernel-packages] [Bug 1210104] Card0.Amixer.values.txt
apport information ** Attachment added: Card0.Amixer.values.txt https://bugs.launchpad.net/bugs/1210104/+attachment/3764827/+files/Card0.Amixer.values.txt -- 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/1210104 Title: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51 Status in “linux” package in Ubuntu: Confirmed Bug description: I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu 12.04 for months. I'm using the MDADM version and not DMRAID. It has been working fine other than a couple minor issues with clean shutdowns that I fixed by tweaking a couple of the scripts under /etc. I upgraded to the latest Linux kernel (3.2.0-51) and my FakeRAID stopped working, probably because auto-detection failed to see the RAID array. Everything works fine with the previous kernel image, 3.2.0-49. Here is /proc/mdstat with the 3.2.0-49 generic kernel image: Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sdb[1] sdc[0] 976758784 blocks super external:/md127/0 [2/2] [UU] md127 : inactive sdb[1](S) sdc[0](S) 6306 blocks super external:imsm The /proc/mdstat file is empty (other than listing personalities) in 3.2.0-51. Note that the sdb and sdc drives are recognized by 3.2.0-51, and their partition tables look reasonable, so I don't see any issues with 3.2.0-51 actually seeing the physical drives. The problem appears to be that the MD driver doesn't detect the external RAID (aka 'imsm') metadata created by Intel fakeraid. Here's the additional data requested for new bug reports: lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 apt-cache policy linux-image-3.2.0-51-generic linux-image-3.2.0-51-generic: Installed: 3.2.0-51.77 Candidate: 3.2.0-51.77 Version table: *** 3.2.0-51.77 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status FWIW, here's the apt-cache data on the previous kernel where fakeraid worked correctly: apt-cache policy linux-image-3.2.0-49-generic linux-image-3.2.0-49-generic: Installed: 3.2.0-49.75 Candidate: 3.2.0-49.75 Version table: *** 3.2.0-49.75 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status I will attach the kernel.log for booting 3.2.0-49 and 3.2.0-51. I've looked at them and all I see is that 3.2.0-49 'binds' the RAID array components and 3.2.0-51 doesn't. Here's a snippet from 3.2.0-49 where it starts my RAID. This is absent in 3.2.0-51. Aug 6 06:53:46 canopus kernel: [2.088509] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.150987] md: bindsdc Aug 6 06:53:46 canopus kernel: [2.151022] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.151746] md: raid1 personality registered for level 1 Aug 6 06:53:46 canopus kernel: [2.152167] bio: create slab bio-1 at 1 Aug 6 06:53:46 canopus kernel: [2.152239] md/raid1:md126: active with 2 out of 2 mirrors Aug 6 06:53:46 canopus kernel: [2.152249] md126: detected capacity change from 0 to 1000200994816 Aug 6 06:53:46 canopus kernel: [2.153111] md126: p1 p2 p3 p4 p5 p6 p7 Any suggestions on how to troubleshoot and/or fix this? There's no point bisecting the kernel images given the regression has just appeared in 3.2.0-51 and, AFAIK, there was never a release of a '3.2.0-50' kernel. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bmccann2893 F pulseaudio /dev/snd/controlC0: bmccann2893 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf743 irq 51' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104384fb,00100302' Controls : 44 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17' Mixer name : 'Nvidia GPU 41 HDMI/DP' Components : 'HDA:10de0041,14622871,00100100' Controls : 24 Simple ctrls : 4 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=ce0ec46d-5a8e-4ba4-9049-ed08a896696b InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120424) MachineType: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine:
[Kernel-packages] [Bug 1210104] Card1.Codecs.codec.0.txt
apport information ** Attachment added: Card1.Codecs.codec.0.txt https://bugs.launchpad.net/bugs/1210104/+attachment/3764830/+files/Card1.Codecs.codec.0.txt -- 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/1210104 Title: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51 Status in “linux” package in Ubuntu: Confirmed Bug description: I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu 12.04 for months. I'm using the MDADM version and not DMRAID. It has been working fine other than a couple minor issues with clean shutdowns that I fixed by tweaking a couple of the scripts under /etc. I upgraded to the latest Linux kernel (3.2.0-51) and my FakeRAID stopped working, probably because auto-detection failed to see the RAID array. Everything works fine with the previous kernel image, 3.2.0-49. Here is /proc/mdstat with the 3.2.0-49 generic kernel image: Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sdb[1] sdc[0] 976758784 blocks super external:/md127/0 [2/2] [UU] md127 : inactive sdb[1](S) sdc[0](S) 6306 blocks super external:imsm The /proc/mdstat file is empty (other than listing personalities) in 3.2.0-51. Note that the sdb and sdc drives are recognized by 3.2.0-51, and their partition tables look reasonable, so I don't see any issues with 3.2.0-51 actually seeing the physical drives. The problem appears to be that the MD driver doesn't detect the external RAID (aka 'imsm') metadata created by Intel fakeraid. Here's the additional data requested for new bug reports: lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 apt-cache policy linux-image-3.2.0-51-generic linux-image-3.2.0-51-generic: Installed: 3.2.0-51.77 Candidate: 3.2.0-51.77 Version table: *** 3.2.0-51.77 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status FWIW, here's the apt-cache data on the previous kernel where fakeraid worked correctly: apt-cache policy linux-image-3.2.0-49-generic linux-image-3.2.0-49-generic: Installed: 3.2.0-49.75 Candidate: 3.2.0-49.75 Version table: *** 3.2.0-49.75 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status I will attach the kernel.log for booting 3.2.0-49 and 3.2.0-51. I've looked at them and all I see is that 3.2.0-49 'binds' the RAID array components and 3.2.0-51 doesn't. Here's a snippet from 3.2.0-49 where it starts my RAID. This is absent in 3.2.0-51. Aug 6 06:53:46 canopus kernel: [2.088509] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.150987] md: bindsdc Aug 6 06:53:46 canopus kernel: [2.151022] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.151746] md: raid1 personality registered for level 1 Aug 6 06:53:46 canopus kernel: [2.152167] bio: create slab bio-1 at 1 Aug 6 06:53:46 canopus kernel: [2.152239] md/raid1:md126: active with 2 out of 2 mirrors Aug 6 06:53:46 canopus kernel: [2.152249] md126: detected capacity change from 0 to 1000200994816 Aug 6 06:53:46 canopus kernel: [2.153111] md126: p1 p2 p3 p4 p5 p6 p7 Any suggestions on how to troubleshoot and/or fix this? There's no point bisecting the kernel images given the regression has just appeared in 3.2.0-51 and, AFAIK, there was never a release of a '3.2.0-50' kernel. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bmccann2893 F pulseaudio /dev/snd/controlC0: bmccann2893 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf743 irq 51' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104384fb,00100302' Controls : 44 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17' Mixer name : 'Nvidia GPU 41 HDMI/DP' Components : 'HDA:10de0041,14622871,00100100' Controls : 24 Simple ctrls : 4 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=ce0ec46d-5a8e-4ba4-9049-ed08a896696b InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120424) MachineType: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine:
[Kernel-packages] [Bug 1210104] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1210104/+attachment/3764840/+files/UdevDb.txt -- 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/1210104 Title: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51 Status in “linux” package in Ubuntu: Confirmed Bug description: I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu 12.04 for months. I'm using the MDADM version and not DMRAID. It has been working fine other than a couple minor issues with clean shutdowns that I fixed by tweaking a couple of the scripts under /etc. I upgraded to the latest Linux kernel (3.2.0-51) and my FakeRAID stopped working, probably because auto-detection failed to see the RAID array. Everything works fine with the previous kernel image, 3.2.0-49. Here is /proc/mdstat with the 3.2.0-49 generic kernel image: Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sdb[1] sdc[0] 976758784 blocks super external:/md127/0 [2/2] [UU] md127 : inactive sdb[1](S) sdc[0](S) 6306 blocks super external:imsm The /proc/mdstat file is empty (other than listing personalities) in 3.2.0-51. Note that the sdb and sdc drives are recognized by 3.2.0-51, and their partition tables look reasonable, so I don't see any issues with 3.2.0-51 actually seeing the physical drives. The problem appears to be that the MD driver doesn't detect the external RAID (aka 'imsm') metadata created by Intel fakeraid. Here's the additional data requested for new bug reports: lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 apt-cache policy linux-image-3.2.0-51-generic linux-image-3.2.0-51-generic: Installed: 3.2.0-51.77 Candidate: 3.2.0-51.77 Version table: *** 3.2.0-51.77 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status FWIW, here's the apt-cache data on the previous kernel where fakeraid worked correctly: apt-cache policy linux-image-3.2.0-49-generic linux-image-3.2.0-49-generic: Installed: 3.2.0-49.75 Candidate: 3.2.0-49.75 Version table: *** 3.2.0-49.75 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status I will attach the kernel.log for booting 3.2.0-49 and 3.2.0-51. I've looked at them and all I see is that 3.2.0-49 'binds' the RAID array components and 3.2.0-51 doesn't. Here's a snippet from 3.2.0-49 where it starts my RAID. This is absent in 3.2.0-51. Aug 6 06:53:46 canopus kernel: [2.088509] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.150987] md: bindsdc Aug 6 06:53:46 canopus kernel: [2.151022] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.151746] md: raid1 personality registered for level 1 Aug 6 06:53:46 canopus kernel: [2.152167] bio: create slab bio-1 at 1 Aug 6 06:53:46 canopus kernel: [2.152239] md/raid1:md126: active with 2 out of 2 mirrors Aug 6 06:53:46 canopus kernel: [2.152249] md126: detected capacity change from 0 to 1000200994816 Aug 6 06:53:46 canopus kernel: [2.153111] md126: p1 p2 p3 p4 p5 p6 p7 Any suggestions on how to troubleshoot and/or fix this? There's no point bisecting the kernel images given the regression has just appeared in 3.2.0-51 and, AFAIK, there was never a release of a '3.2.0-50' kernel. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bmccann2893 F pulseaudio /dev/snd/controlC0: bmccann2893 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf743 irq 51' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104384fb,00100302' Controls : 44 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17' Mixer name : 'Nvidia GPU 41 HDMI/DP' Components : 'HDA:10de0041,14622871,00100100' Controls : 24 Simple ctrls : 4 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=ce0ec46d-5a8e-4ba4-9049-ed08a896696b InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120424) MachineType: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-49-generic
[Kernel-packages] [Bug 1210104] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1210104/+attachment/3764831/+files/CurrentDmesg.txt -- 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/1210104 Title: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51 Status in “linux” package in Ubuntu: Confirmed Bug description: I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu 12.04 for months. I'm using the MDADM version and not DMRAID. It has been working fine other than a couple minor issues with clean shutdowns that I fixed by tweaking a couple of the scripts under /etc. I upgraded to the latest Linux kernel (3.2.0-51) and my FakeRAID stopped working, probably because auto-detection failed to see the RAID array. Everything works fine with the previous kernel image, 3.2.0-49. Here is /proc/mdstat with the 3.2.0-49 generic kernel image: Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sdb[1] sdc[0] 976758784 blocks super external:/md127/0 [2/2] [UU] md127 : inactive sdb[1](S) sdc[0](S) 6306 blocks super external:imsm The /proc/mdstat file is empty (other than listing personalities) in 3.2.0-51. Note that the sdb and sdc drives are recognized by 3.2.0-51, and their partition tables look reasonable, so I don't see any issues with 3.2.0-51 actually seeing the physical drives. The problem appears to be that the MD driver doesn't detect the external RAID (aka 'imsm') metadata created by Intel fakeraid. Here's the additional data requested for new bug reports: lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 apt-cache policy linux-image-3.2.0-51-generic linux-image-3.2.0-51-generic: Installed: 3.2.0-51.77 Candidate: 3.2.0-51.77 Version table: *** 3.2.0-51.77 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status FWIW, here's the apt-cache data on the previous kernel where fakeraid worked correctly: apt-cache policy linux-image-3.2.0-49-generic linux-image-3.2.0-49-generic: Installed: 3.2.0-49.75 Candidate: 3.2.0-49.75 Version table: *** 3.2.0-49.75 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status I will attach the kernel.log for booting 3.2.0-49 and 3.2.0-51. I've looked at them and all I see is that 3.2.0-49 'binds' the RAID array components and 3.2.0-51 doesn't. Here's a snippet from 3.2.0-49 where it starts my RAID. This is absent in 3.2.0-51. Aug 6 06:53:46 canopus kernel: [2.088509] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.150987] md: bindsdc Aug 6 06:53:46 canopus kernel: [2.151022] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.151746] md: raid1 personality registered for level 1 Aug 6 06:53:46 canopus kernel: [2.152167] bio: create slab bio-1 at 1 Aug 6 06:53:46 canopus kernel: [2.152239] md/raid1:md126: active with 2 out of 2 mirrors Aug 6 06:53:46 canopus kernel: [2.152249] md126: detected capacity change from 0 to 1000200994816 Aug 6 06:53:46 canopus kernel: [2.153111] md126: p1 p2 p3 p4 p5 p6 p7 Any suggestions on how to troubleshoot and/or fix this? There's no point bisecting the kernel images given the regression has just appeared in 3.2.0-51 and, AFAIK, there was never a release of a '3.2.0-50' kernel. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bmccann2893 F pulseaudio /dev/snd/controlC0: bmccann2893 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf743 irq 51' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104384fb,00100302' Controls : 44 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17' Mixer name : 'Nvidia GPU 41 HDMI/DP' Components : 'HDA:10de0041,14622871,00100100' Controls : 24 Simple ctrls : 4 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=ce0ec46d-5a8e-4ba4-9049-ed08a896696b InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120424) MachineType: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine:
[Kernel-packages] [Bug 1210104] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1210104/+attachment/3764833/+files/Lspci.txt -- 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/1210104 Title: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51 Status in “linux” package in Ubuntu: Confirmed Bug description: I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu 12.04 for months. I'm using the MDADM version and not DMRAID. It has been working fine other than a couple minor issues with clean shutdowns that I fixed by tweaking a couple of the scripts under /etc. I upgraded to the latest Linux kernel (3.2.0-51) and my FakeRAID stopped working, probably because auto-detection failed to see the RAID array. Everything works fine with the previous kernel image, 3.2.0-49. Here is /proc/mdstat with the 3.2.0-49 generic kernel image: Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sdb[1] sdc[0] 976758784 blocks super external:/md127/0 [2/2] [UU] md127 : inactive sdb[1](S) sdc[0](S) 6306 blocks super external:imsm The /proc/mdstat file is empty (other than listing personalities) in 3.2.0-51. Note that the sdb and sdc drives are recognized by 3.2.0-51, and their partition tables look reasonable, so I don't see any issues with 3.2.0-51 actually seeing the physical drives. The problem appears to be that the MD driver doesn't detect the external RAID (aka 'imsm') metadata created by Intel fakeraid. Here's the additional data requested for new bug reports: lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 apt-cache policy linux-image-3.2.0-51-generic linux-image-3.2.0-51-generic: Installed: 3.2.0-51.77 Candidate: 3.2.0-51.77 Version table: *** 3.2.0-51.77 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status FWIW, here's the apt-cache data on the previous kernel where fakeraid worked correctly: apt-cache policy linux-image-3.2.0-49-generic linux-image-3.2.0-49-generic: Installed: 3.2.0-49.75 Candidate: 3.2.0-49.75 Version table: *** 3.2.0-49.75 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status I will attach the kernel.log for booting 3.2.0-49 and 3.2.0-51. I've looked at them and all I see is that 3.2.0-49 'binds' the RAID array components and 3.2.0-51 doesn't. Here's a snippet from 3.2.0-49 where it starts my RAID. This is absent in 3.2.0-51. Aug 6 06:53:46 canopus kernel: [2.088509] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.150987] md: bindsdc Aug 6 06:53:46 canopus kernel: [2.151022] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.151746] md: raid1 personality registered for level 1 Aug 6 06:53:46 canopus kernel: [2.152167] bio: create slab bio-1 at 1 Aug 6 06:53:46 canopus kernel: [2.152239] md/raid1:md126: active with 2 out of 2 mirrors Aug 6 06:53:46 canopus kernel: [2.152249] md126: detected capacity change from 0 to 1000200994816 Aug 6 06:53:46 canopus kernel: [2.153111] md126: p1 p2 p3 p4 p5 p6 p7 Any suggestions on how to troubleshoot and/or fix this? There's no point bisecting the kernel images given the regression has just appeared in 3.2.0-51 and, AFAIK, there was never a release of a '3.2.0-50' kernel. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bmccann2893 F pulseaudio /dev/snd/controlC0: bmccann2893 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf743 irq 51' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104384fb,00100302' Controls : 44 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17' Mixer name : 'Nvidia GPU 41 HDMI/DP' Components : 'HDA:10de0041,14622871,00100100' Controls : 24 Simple ctrls : 4 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=ce0ec46d-5a8e-4ba4-9049-ed08a896696b InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120424) MachineType: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-49-generic
[Kernel-packages] [Bug 1210104] Re: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51
OK. I added the apport data. Note that I am currently running 3.2.0-49, which works, because my machine is almost useless with 3.2.0-51. ** Changed in: linux (Ubuntu) Status: Incomplete = New -- 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/1210104 Title: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51 Status in “linux” package in Ubuntu: Confirmed Bug description: I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu 12.04 for months. I'm using the MDADM version and not DMRAID. It has been working fine other than a couple minor issues with clean shutdowns that I fixed by tweaking a couple of the scripts under /etc. I upgraded to the latest Linux kernel (3.2.0-51) and my FakeRAID stopped working, probably because auto-detection failed to see the RAID array. Everything works fine with the previous kernel image, 3.2.0-49. Here is /proc/mdstat with the 3.2.0-49 generic kernel image: Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sdb[1] sdc[0] 976758784 blocks super external:/md127/0 [2/2] [UU] md127 : inactive sdb[1](S) sdc[0](S) 6306 blocks super external:imsm The /proc/mdstat file is empty (other than listing personalities) in 3.2.0-51. Note that the sdb and sdc drives are recognized by 3.2.0-51, and their partition tables look reasonable, so I don't see any issues with 3.2.0-51 actually seeing the physical drives. The problem appears to be that the MD driver doesn't detect the external RAID (aka 'imsm') metadata created by Intel fakeraid. Here's the additional data requested for new bug reports: lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 apt-cache policy linux-image-3.2.0-51-generic linux-image-3.2.0-51-generic: Installed: 3.2.0-51.77 Candidate: 3.2.0-51.77 Version table: *** 3.2.0-51.77 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status FWIW, here's the apt-cache data on the previous kernel where fakeraid worked correctly: apt-cache policy linux-image-3.2.0-49-generic linux-image-3.2.0-49-generic: Installed: 3.2.0-49.75 Candidate: 3.2.0-49.75 Version table: *** 3.2.0-49.75 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status I will attach the kernel.log for booting 3.2.0-49 and 3.2.0-51. I've looked at them and all I see is that 3.2.0-49 'binds' the RAID array components and 3.2.0-51 doesn't. Here's a snippet from 3.2.0-49 where it starts my RAID. This is absent in 3.2.0-51. Aug 6 06:53:46 canopus kernel: [2.088509] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.150987] md: bindsdc Aug 6 06:53:46 canopus kernel: [2.151022] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.151746] md: raid1 personality registered for level 1 Aug 6 06:53:46 canopus kernel: [2.152167] bio: create slab bio-1 at 1 Aug 6 06:53:46 canopus kernel: [2.152239] md/raid1:md126: active with 2 out of 2 mirrors Aug 6 06:53:46 canopus kernel: [2.152249] md126: detected capacity change from 0 to 1000200994816 Aug 6 06:53:46 canopus kernel: [2.153111] md126: p1 p2 p3 p4 p5 p6 p7 Any suggestions on how to troubleshoot and/or fix this? There's no point bisecting the kernel images given the regression has just appeared in 3.2.0-51 and, AFAIK, there was never a release of a '3.2.0-50' kernel. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bmccann2893 F pulseaudio /dev/snd/controlC0: bmccann2893 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf743 irq 51' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104384fb,00100302' Controls : 44 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17' Mixer name : 'Nvidia GPU 41 HDMI/DP' Components : 'HDA:10de0041,14622871,00100100' Controls : 24 Simple ctrls : 4 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=ce0ec46d-5a8e-4ba4-9049-ed08a896696b InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120424) MachineType: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0
[Kernel-packages] [Bug 1210104] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1210104/+attachment/3764838/+files/ProcModules.txt -- 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/1210104 Title: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51 Status in “linux” package in Ubuntu: Confirmed Bug description: I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu 12.04 for months. I'm using the MDADM version and not DMRAID. It has been working fine other than a couple minor issues with clean shutdowns that I fixed by tweaking a couple of the scripts under /etc. I upgraded to the latest Linux kernel (3.2.0-51) and my FakeRAID stopped working, probably because auto-detection failed to see the RAID array. Everything works fine with the previous kernel image, 3.2.0-49. Here is /proc/mdstat with the 3.2.0-49 generic kernel image: Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sdb[1] sdc[0] 976758784 blocks super external:/md127/0 [2/2] [UU] md127 : inactive sdb[1](S) sdc[0](S) 6306 blocks super external:imsm The /proc/mdstat file is empty (other than listing personalities) in 3.2.0-51. Note that the sdb and sdc drives are recognized by 3.2.0-51, and their partition tables look reasonable, so I don't see any issues with 3.2.0-51 actually seeing the physical drives. The problem appears to be that the MD driver doesn't detect the external RAID (aka 'imsm') metadata created by Intel fakeraid. Here's the additional data requested for new bug reports: lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 apt-cache policy linux-image-3.2.0-51-generic linux-image-3.2.0-51-generic: Installed: 3.2.0-51.77 Candidate: 3.2.0-51.77 Version table: *** 3.2.0-51.77 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status FWIW, here's the apt-cache data on the previous kernel where fakeraid worked correctly: apt-cache policy linux-image-3.2.0-49-generic linux-image-3.2.0-49-generic: Installed: 3.2.0-49.75 Candidate: 3.2.0-49.75 Version table: *** 3.2.0-49.75 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status I will attach the kernel.log for booting 3.2.0-49 and 3.2.0-51. I've looked at them and all I see is that 3.2.0-49 'binds' the RAID array components and 3.2.0-51 doesn't. Here's a snippet from 3.2.0-49 where it starts my RAID. This is absent in 3.2.0-51. Aug 6 06:53:46 canopus kernel: [2.088509] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.150987] md: bindsdc Aug 6 06:53:46 canopus kernel: [2.151022] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.151746] md: raid1 personality registered for level 1 Aug 6 06:53:46 canopus kernel: [2.152167] bio: create slab bio-1 at 1 Aug 6 06:53:46 canopus kernel: [2.152239] md/raid1:md126: active with 2 out of 2 mirrors Aug 6 06:53:46 canopus kernel: [2.152249] md126: detected capacity change from 0 to 1000200994816 Aug 6 06:53:46 canopus kernel: [2.153111] md126: p1 p2 p3 p4 p5 p6 p7 Any suggestions on how to troubleshoot and/or fix this? There's no point bisecting the kernel images given the regression has just appeared in 3.2.0-51 and, AFAIK, there was never a release of a '3.2.0-50' kernel. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bmccann2893 F pulseaudio /dev/snd/controlC0: bmccann2893 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf743 irq 51' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104384fb,00100302' Controls : 44 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17' Mixer name : 'Nvidia GPU 41 HDMI/DP' Components : 'HDA:10de0041,14622871,00100100' Controls : 24 Simple ctrls : 4 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=ce0ec46d-5a8e-4ba4-9049-ed08a896696b InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120424) MachineType: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine:
[Kernel-packages] [Bug 1210104] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1210104/+attachment/3764834/+files/Lsusb.txt -- 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/1210104 Title: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51 Status in “linux” package in Ubuntu: Confirmed Bug description: I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu 12.04 for months. I'm using the MDADM version and not DMRAID. It has been working fine other than a couple minor issues with clean shutdowns that I fixed by tweaking a couple of the scripts under /etc. I upgraded to the latest Linux kernel (3.2.0-51) and my FakeRAID stopped working, probably because auto-detection failed to see the RAID array. Everything works fine with the previous kernel image, 3.2.0-49. Here is /proc/mdstat with the 3.2.0-49 generic kernel image: Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sdb[1] sdc[0] 976758784 blocks super external:/md127/0 [2/2] [UU] md127 : inactive sdb[1](S) sdc[0](S) 6306 blocks super external:imsm The /proc/mdstat file is empty (other than listing personalities) in 3.2.0-51. Note that the sdb and sdc drives are recognized by 3.2.0-51, and their partition tables look reasonable, so I don't see any issues with 3.2.0-51 actually seeing the physical drives. The problem appears to be that the MD driver doesn't detect the external RAID (aka 'imsm') metadata created by Intel fakeraid. Here's the additional data requested for new bug reports: lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 apt-cache policy linux-image-3.2.0-51-generic linux-image-3.2.0-51-generic: Installed: 3.2.0-51.77 Candidate: 3.2.0-51.77 Version table: *** 3.2.0-51.77 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status FWIW, here's the apt-cache data on the previous kernel where fakeraid worked correctly: apt-cache policy linux-image-3.2.0-49-generic linux-image-3.2.0-49-generic: Installed: 3.2.0-49.75 Candidate: 3.2.0-49.75 Version table: *** 3.2.0-49.75 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status I will attach the kernel.log for booting 3.2.0-49 and 3.2.0-51. I've looked at them and all I see is that 3.2.0-49 'binds' the RAID array components and 3.2.0-51 doesn't. Here's a snippet from 3.2.0-49 where it starts my RAID. This is absent in 3.2.0-51. Aug 6 06:53:46 canopus kernel: [2.088509] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.150987] md: bindsdc Aug 6 06:53:46 canopus kernel: [2.151022] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.151746] md: raid1 personality registered for level 1 Aug 6 06:53:46 canopus kernel: [2.152167] bio: create slab bio-1 at 1 Aug 6 06:53:46 canopus kernel: [2.152239] md/raid1:md126: active with 2 out of 2 mirrors Aug 6 06:53:46 canopus kernel: [2.152249] md126: detected capacity change from 0 to 1000200994816 Aug 6 06:53:46 canopus kernel: [2.153111] md126: p1 p2 p3 p4 p5 p6 p7 Any suggestions on how to troubleshoot and/or fix this? There's no point bisecting the kernel images given the regression has just appeared in 3.2.0-51 and, AFAIK, there was never a release of a '3.2.0-50' kernel. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bmccann2893 F pulseaudio /dev/snd/controlC0: bmccann2893 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf743 irq 51' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104384fb,00100302' Controls : 44 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17' Mixer name : 'Nvidia GPU 41 HDMI/DP' Components : 'HDA:10de0041,14622871,00100100' Controls : 24 Simple ctrls : 4 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=ce0ec46d-5a8e-4ba4-9049-ed08a896696b InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120424) MachineType: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-49-generic
[Kernel-packages] [Bug 1210104] UserAsoundrcAsoundconf.txt
apport information ** Attachment added: UserAsoundrcAsoundconf.txt https://bugs.launchpad.net/bugs/1210104/+attachment/3764842/+files/UserAsoundrcAsoundconf.txt -- 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/1210104 Title: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51 Status in “linux” package in Ubuntu: Confirmed Bug description: I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu 12.04 for months. I'm using the MDADM version and not DMRAID. It has been working fine other than a couple minor issues with clean shutdowns that I fixed by tweaking a couple of the scripts under /etc. I upgraded to the latest Linux kernel (3.2.0-51) and my FakeRAID stopped working, probably because auto-detection failed to see the RAID array. Everything works fine with the previous kernel image, 3.2.0-49. Here is /proc/mdstat with the 3.2.0-49 generic kernel image: Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sdb[1] sdc[0] 976758784 blocks super external:/md127/0 [2/2] [UU] md127 : inactive sdb[1](S) sdc[0](S) 6306 blocks super external:imsm The /proc/mdstat file is empty (other than listing personalities) in 3.2.0-51. Note that the sdb and sdc drives are recognized by 3.2.0-51, and their partition tables look reasonable, so I don't see any issues with 3.2.0-51 actually seeing the physical drives. The problem appears to be that the MD driver doesn't detect the external RAID (aka 'imsm') metadata created by Intel fakeraid. Here's the additional data requested for new bug reports: lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 apt-cache policy linux-image-3.2.0-51-generic linux-image-3.2.0-51-generic: Installed: 3.2.0-51.77 Candidate: 3.2.0-51.77 Version table: *** 3.2.0-51.77 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status FWIW, here's the apt-cache data on the previous kernel where fakeraid worked correctly: apt-cache policy linux-image-3.2.0-49-generic linux-image-3.2.0-49-generic: Installed: 3.2.0-49.75 Candidate: 3.2.0-49.75 Version table: *** 3.2.0-49.75 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status I will attach the kernel.log for booting 3.2.0-49 and 3.2.0-51. I've looked at them and all I see is that 3.2.0-49 'binds' the RAID array components and 3.2.0-51 doesn't. Here's a snippet from 3.2.0-49 where it starts my RAID. This is absent in 3.2.0-51. Aug 6 06:53:46 canopus kernel: [2.088509] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.150987] md: bindsdc Aug 6 06:53:46 canopus kernel: [2.151022] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.151746] md: raid1 personality registered for level 1 Aug 6 06:53:46 canopus kernel: [2.152167] bio: create slab bio-1 at 1 Aug 6 06:53:46 canopus kernel: [2.152239] md/raid1:md126: active with 2 out of 2 mirrors Aug 6 06:53:46 canopus kernel: [2.152249] md126: detected capacity change from 0 to 1000200994816 Aug 6 06:53:46 canopus kernel: [2.153111] md126: p1 p2 p3 p4 p5 p6 p7 Any suggestions on how to troubleshoot and/or fix this? There's no point bisecting the kernel images given the regression has just appeared in 3.2.0-51 and, AFAIK, there was never a release of a '3.2.0-50' kernel. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bmccann2893 F pulseaudio /dev/snd/controlC0: bmccann2893 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf743 irq 51' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104384fb,00100302' Controls : 44 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17' Mixer name : 'Nvidia GPU 41 HDMI/DP' Components : 'HDA:10de0041,14622871,00100100' Controls : 24 Simple ctrls : 4 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=ce0ec46d-5a8e-4ba4-9049-ed08a896696b InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120424) MachineType: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine:
[Kernel-packages] [Bug 1210104] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/1210104/+attachment/3764839/+files/PulseList.txt -- 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/1210104 Title: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51 Status in “linux” package in Ubuntu: Confirmed Bug description: I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu 12.04 for months. I'm using the MDADM version and not DMRAID. It has been working fine other than a couple minor issues with clean shutdowns that I fixed by tweaking a couple of the scripts under /etc. I upgraded to the latest Linux kernel (3.2.0-51) and my FakeRAID stopped working, probably because auto-detection failed to see the RAID array. Everything works fine with the previous kernel image, 3.2.0-49. Here is /proc/mdstat with the 3.2.0-49 generic kernel image: Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sdb[1] sdc[0] 976758784 blocks super external:/md127/0 [2/2] [UU] md127 : inactive sdb[1](S) sdc[0](S) 6306 blocks super external:imsm The /proc/mdstat file is empty (other than listing personalities) in 3.2.0-51. Note that the sdb and sdc drives are recognized by 3.2.0-51, and their partition tables look reasonable, so I don't see any issues with 3.2.0-51 actually seeing the physical drives. The problem appears to be that the MD driver doesn't detect the external RAID (aka 'imsm') metadata created by Intel fakeraid. Here's the additional data requested for new bug reports: lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 apt-cache policy linux-image-3.2.0-51-generic linux-image-3.2.0-51-generic: Installed: 3.2.0-51.77 Candidate: 3.2.0-51.77 Version table: *** 3.2.0-51.77 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status FWIW, here's the apt-cache data on the previous kernel where fakeraid worked correctly: apt-cache policy linux-image-3.2.0-49-generic linux-image-3.2.0-49-generic: Installed: 3.2.0-49.75 Candidate: 3.2.0-49.75 Version table: *** 3.2.0-49.75 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status I will attach the kernel.log for booting 3.2.0-49 and 3.2.0-51. I've looked at them and all I see is that 3.2.0-49 'binds' the RAID array components and 3.2.0-51 doesn't. Here's a snippet from 3.2.0-49 where it starts my RAID. This is absent in 3.2.0-51. Aug 6 06:53:46 canopus kernel: [2.088509] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.150987] md: bindsdc Aug 6 06:53:46 canopus kernel: [2.151022] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.151746] md: raid1 personality registered for level 1 Aug 6 06:53:46 canopus kernel: [2.152167] bio: create slab bio-1 at 1 Aug 6 06:53:46 canopus kernel: [2.152239] md/raid1:md126: active with 2 out of 2 mirrors Aug 6 06:53:46 canopus kernel: [2.152249] md126: detected capacity change from 0 to 1000200994816 Aug 6 06:53:46 canopus kernel: [2.153111] md126: p1 p2 p3 p4 p5 p6 p7 Any suggestions on how to troubleshoot and/or fix this? There's no point bisecting the kernel images given the regression has just appeared in 3.2.0-51 and, AFAIK, there was never a release of a '3.2.0-50' kernel. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bmccann2893 F pulseaudio /dev/snd/controlC0: bmccann2893 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf743 irq 51' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104384fb,00100302' Controls : 44 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17' Mixer name : 'Nvidia GPU 41 HDMI/DP' Components : 'HDA:10de0041,14622871,00100100' Controls : 24 Simple ctrls : 4 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=ce0ec46d-5a8e-4ba4-9049-ed08a896696b InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120424) MachineType: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine:
[Kernel-packages] [Bug 1210104] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1210104/+attachment/3764841/+files/UdevLog.txt -- 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/1210104 Title: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51 Status in “linux” package in Ubuntu: Confirmed Bug description: I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu 12.04 for months. I'm using the MDADM version and not DMRAID. It has been working fine other than a couple minor issues with clean shutdowns that I fixed by tweaking a couple of the scripts under /etc. I upgraded to the latest Linux kernel (3.2.0-51) and my FakeRAID stopped working, probably because auto-detection failed to see the RAID array. Everything works fine with the previous kernel image, 3.2.0-49. Here is /proc/mdstat with the 3.2.0-49 generic kernel image: Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sdb[1] sdc[0] 976758784 blocks super external:/md127/0 [2/2] [UU] md127 : inactive sdb[1](S) sdc[0](S) 6306 blocks super external:imsm The /proc/mdstat file is empty (other than listing personalities) in 3.2.0-51. Note that the sdb and sdc drives are recognized by 3.2.0-51, and their partition tables look reasonable, so I don't see any issues with 3.2.0-51 actually seeing the physical drives. The problem appears to be that the MD driver doesn't detect the external RAID (aka 'imsm') metadata created by Intel fakeraid. Here's the additional data requested for new bug reports: lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 apt-cache policy linux-image-3.2.0-51-generic linux-image-3.2.0-51-generic: Installed: 3.2.0-51.77 Candidate: 3.2.0-51.77 Version table: *** 3.2.0-51.77 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status FWIW, here's the apt-cache data on the previous kernel where fakeraid worked correctly: apt-cache policy linux-image-3.2.0-49-generic linux-image-3.2.0-49-generic: Installed: 3.2.0-49.75 Candidate: 3.2.0-49.75 Version table: *** 3.2.0-49.75 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status I will attach the kernel.log for booting 3.2.0-49 and 3.2.0-51. I've looked at them and all I see is that 3.2.0-49 'binds' the RAID array components and 3.2.0-51 doesn't. Here's a snippet from 3.2.0-49 where it starts my RAID. This is absent in 3.2.0-51. Aug 6 06:53:46 canopus kernel: [2.088509] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.150987] md: bindsdc Aug 6 06:53:46 canopus kernel: [2.151022] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.151746] md: raid1 personality registered for level 1 Aug 6 06:53:46 canopus kernel: [2.152167] bio: create slab bio-1 at 1 Aug 6 06:53:46 canopus kernel: [2.152239] md/raid1:md126: active with 2 out of 2 mirrors Aug 6 06:53:46 canopus kernel: [2.152249] md126: detected capacity change from 0 to 1000200994816 Aug 6 06:53:46 canopus kernel: [2.153111] md126: p1 p2 p3 p4 p5 p6 p7 Any suggestions on how to troubleshoot and/or fix this? There's no point bisecting the kernel images given the regression has just appeared in 3.2.0-51 and, AFAIK, there was never a release of a '3.2.0-50' kernel. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bmccann2893 F pulseaudio /dev/snd/controlC0: bmccann2893 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf743 irq 51' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104384fb,00100302' Controls : 44 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17' Mixer name : 'Nvidia GPU 41 HDMI/DP' Components : 'HDA:10de0041,14622871,00100100' Controls : 24 Simple ctrls : 4 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=ce0ec46d-5a8e-4ba4-9049-ed08a896696b InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120424) MachineType: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-49-generic
Re: [Kernel-packages] [Bug 1174893] Re: 10de:0427 Display remains blank when waking up from suspend
Hi, + If you install the nvidia drivers in Raring it works? it does work, it was flagged in a similar bug's comments as a solution But it is very laggy and overheating, HD videos collapse, it worked fine till 12.04 + What previous release specifically did this work in, and were you using nvidia drivers or nouveau? till 12.04 it was ok with both on 12.04 i used nvidia and on 12.10 i tried both but used xorg because nvidia was less responsive and heating was serious and 13.04 as described above rgds A 2013/8/8 Christopher M. Penalver christopher.m.penal...@gmail.com Api, just to clarify: + If you install the nvidia drivers in Raring it works? + What previous release specifically did this work in, and were you using nvidia drivers or nouveau? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1174893 Title: 10de:0427 Display remains blank when waking up from suspend Status in “linux” package in Ubuntu: Incomplete Bug description: Display remains blank when waking up from suspend ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Apr 30 21:47:36 2013 DistUpgraded: 2013-04-28 00:01:53,452 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G86M [GeForce 8400M GS] [10de:0427] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0209] MachineType: Dell Inc. XPS M1330 MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=4e20b92e-d916-4d63-a4d7-9f2f0dc4b1f1 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to raring on 2013-04-27 (2 days ago) dmi.bios.date: 12/26/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd12/26/2008:svnDellInc.:pnXPSM1330:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1330 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1174893/+subscriptions -- 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/1174893 Title: 10de:0427 Display remains blank when waking up from suspend Status in “linux” package in Ubuntu: Incomplete Bug description: Display remains blank when waking up from suspend ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Apr 30 21:47:36 2013 DistUpgraded: 2013-04-28 00:01:53,452 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G86M [GeForce 8400M GS] [10de:0427] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0209] MachineType: Dell Inc. XPS M1330
[Kernel-packages] [Bug 1210104] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New = 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/1210104 Title: Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51 Status in “linux” package in Ubuntu: Confirmed Bug description: I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu 12.04 for months. I'm using the MDADM version and not DMRAID. It has been working fine other than a couple minor issues with clean shutdowns that I fixed by tweaking a couple of the scripts under /etc. I upgraded to the latest Linux kernel (3.2.0-51) and my FakeRAID stopped working, probably because auto-detection failed to see the RAID array. Everything works fine with the previous kernel image, 3.2.0-49. Here is /proc/mdstat with the 3.2.0-49 generic kernel image: Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md126 : active raid1 sdb[1] sdc[0] 976758784 blocks super external:/md127/0 [2/2] [UU] md127 : inactive sdb[1](S) sdc[0](S) 6306 blocks super external:imsm The /proc/mdstat file is empty (other than listing personalities) in 3.2.0-51. Note that the sdb and sdc drives are recognized by 3.2.0-51, and their partition tables look reasonable, so I don't see any issues with 3.2.0-51 actually seeing the physical drives. The problem appears to be that the MD driver doesn't detect the external RAID (aka 'imsm') metadata created by Intel fakeraid. Here's the additional data requested for new bug reports: lsb_release -rd Description:Ubuntu 12.04.2 LTS Release:12.04 apt-cache policy linux-image-3.2.0-51-generic linux-image-3.2.0-51-generic: Installed: 3.2.0-51.77 Candidate: 3.2.0-51.77 Version table: *** 3.2.0-51.77 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status FWIW, here's the apt-cache data on the previous kernel where fakeraid worked correctly: apt-cache policy linux-image-3.2.0-49-generic linux-image-3.2.0-49-generic: Installed: 3.2.0-49.75 Candidate: 3.2.0-49.75 Version table: *** 3.2.0-49.75 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status I will attach the kernel.log for booting 3.2.0-49 and 3.2.0-51. I've looked at them and all I see is that 3.2.0-49 'binds' the RAID array components and 3.2.0-51 doesn't. Here's a snippet from 3.2.0-49 where it starts my RAID. This is absent in 3.2.0-51. Aug 6 06:53:46 canopus kernel: [2.088509] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.150987] md: bindsdc Aug 6 06:53:46 canopus kernel: [2.151022] md: bindsdb Aug 6 06:53:46 canopus kernel: [2.151746] md: raid1 personality registered for level 1 Aug 6 06:53:46 canopus kernel: [2.152167] bio: create slab bio-1 at 1 Aug 6 06:53:46 canopus kernel: [2.152239] md/raid1:md126: active with 2 out of 2 mirrors Aug 6 06:53:46 canopus kernel: [2.152249] md126: detected capacity change from 0 to 1000200994816 Aug 6 06:53:46 canopus kernel: [2.153111] md126: p1 p2 p3 p4 p5 p6 p7 Any suggestions on how to troubleshoot and/or fix this? There's no point bisecting the kernel images given the regression has just appeared in 3.2.0-51 and, AFAIK, there was never a release of a '3.2.0-50' kernel. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bmccann2893 F pulseaudio /dev/snd/controlC0: bmccann2893 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf743 irq 51' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,104384fb,00100302' Controls : 44 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17' Mixer name : 'Nvidia GPU 41 HDMI/DP' Components : 'HDA:10de0041,14622871,00100100' Controls : 24 Simple ctrls : 4 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=ce0ec46d-5a8e-4ba4-9049-ed08a896696b InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120424) MachineType: System manufacturer System Product Name MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-49-generic
[Kernel-packages] [Bug 1209423] Re: [STAGING] 2.6.32-47 kernel update on 10.04 breaks software RAID at boot
Lucid server is supported until 2015 and I would tend to see this as a server issue. So since this can be reduced to md problems, the fact that /proc/mdstat is empty would lead to assume that something during the assembly failed completely. Despite the weird output of mdadm --examine (sounds really like some tool failure back in lucid) does looking at the other mirror half produce the same/similar output (assume that would be on sdc)? Maybe also remove the quiet command line option in grub before booting (if that still hides too much output, experiment with removing splash as well, though I think to remember that may cause the question about skipping or manual recovery not to appear on screen on some older releases (thoug not remembering which one)). -- 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/1209423 Title: [STAGING] 2.6.32-47 kernel update on 10.04 breaks software RAID at boot Status in “linux” package in Ubuntu: Incomplete Bug description: After update from 2.6.32-46 to 2.6.32-47 one of the md arrays does not start anymore at boot time. The RAID 1 md0 now causes message Continue to wait; or Press S to skip mounting or M for manual recovery at boot. I used S to create this report as requested in a similar bug report (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1190295) by user penalvch Booting back into 2.6.32-46 the md devices are correctly set up and the system boots normally. See the linked bug for further details, such as: The array that does not start anymore has the following config: level=raid1 metadata=1.2 num-devices=2 While a second array with metadata=1.0 seems to be recognized and started correctly. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-50-generic 2.6.32-50.112 Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-50.112-generic 2.6.32.61+drm33.26 Uname: Linux 2.6.32-50-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alan 1991 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf622 irq 22' Mixer name : 'Realtek ALC888' Components : 'HDA:10ec0888,80860034,00100202' Controls : 28 Simple ctrls : 16 Date: Thu Aug 8 02:01:09 2013 HibernationDevice: RESUME=UUID=b1649a13-fffd-4e98-b42b-a5e9ea98f9fc InstallationMedia: Ubuntu 10.04.4 LTS Lucid Lynx - Release amd64 (20120214.2) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-50-generic root=UUID=e69dddfa-14a0-499f-9267-edca27fbd7a4 ro quiet splash ProcEnviron: PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.34.14 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: r8192s_usb Title: [STAGING] dmi.bios.date: 04/19/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: WBIBX10J.86A.0293.2010.0419.1819 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WB dmi.board.vendor: Intel Corporation dmi.board.version: AAE64798-207 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrWBIBX10J.86A.0293.2010.0419.1819:bd04/19/2010:svn:pn:pvr:rvnIntelCorporation:rnDP55WB:rvrAAE64798-207:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1209423/+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 1074110] Re: wakeonlan fails if pm-hibernate used
Still present in yesterday's build. E-mail sent. -- 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/1074110 Title: wakeonlan fails if pm-hibernate used Status in “linux” package in Ubuntu: Triaged Bug description: After issuing halt -p, wakeonlan works fine. after issuing pm- hibernate, the machine will not wake up. interfaces: auto eth0 iface eth0 inet dhcp up ethtool -s eth0 wol g down ethtool -s eth0 wol g Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Link partner advertised pause frame use: Symmetric Link partner advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 32 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x0007 (7) drv probe link Link detected: yes 01:03.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) Not sure what else might be needed here, but apport-bug refuses to collect data for some reason. https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1073830 Same is true of the latest upstream kernel: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc3-raring/ --- Architecture: i386 DistroRelease: Ubuntu 12.04 LiveMediaBuild: Ubuntu 7.10 Gutsy Gibbon - Release i386 (20071016) Package: linux 3.2.0.32.35 PackageArchitecture: i386 ProcEnviron: TERM=xterm LANG=en_GB.UTF-8 SHELL=/bin/bash Uname: Linux 3.7.0-030700rc3-generic i686 UnreportableReason: The running kernel is not an Ubuntu kernel UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1074110/+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
Re: [Kernel-packages] [Bug 1208132] Re: [Z68MX-UD2H-B3] When suspending: Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS, ..
Christopher, I am quite happy with my 12.04 and want to use it as long Time Stable. I think also 12.04 should be supported carefully. My intention was, as you know, to give you some information related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1167669 which is the same as Bug 1208132 to my mind. As I said: Something changed between Kernel 3.2.0.39 and 3.2.0.40. I would be happy to help fixing the bug in 12.04 and can do whatever test you want me to do. But I do not want to upgrade to the next non LTS version of Ubuntu. best regards, Bernhard -- 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/1208132 Title: [Z68MX-UD2H-B3] When suspending: Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS,.. Status in “linux” package in Ubuntu: Incomplete Bug description: I have a Gigabyte Z68MS-UD2H-B3 Motherboard with Precise and I got this error when coming back from suspend. The latest kernel version not affected is 3.2.0.39 All other version show this issue. I also tried with linux-image-3.2.49-030249-generic-pae. This did not show the message, but I am not so sure, because there where a lot of other message, maybe masking this Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS,.. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-51-generic-pae 3.2.0-51.77 ProcVersionSignature: Ubuntu 3.2.0-51.77-generic-pae 3.2.48 Uname: Linux 3.2.0-51-generic-pae i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bernhard 1858 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xfbff4000 irq 47' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:10ec0889,1458a132,0014 HDA:80862805,80860101,0010' Controls : 59 Simple ctrls : 25 Date: Sun Aug 4 11:47:00 2013 HibernationDevice: RESUME=UUID=0ca5d59a-dba8-4819-ae27-e2efa637b473 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Z68MX-UD2H-B3 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-51-generic-pae root=UUID=7a254583-f501-4481-8ee5-43e2a690ae49 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-51-generic-pae N/A linux-backports-modules-3.2.0-51-generic-pae N/A linux-firmware1.79.6 RfKill: SourcePackage: linux StagingDrivers: mei UpgradeStatus: Upgraded to precise on 2012-05-05 (455 days ago) dmi.bios.date: 10/12/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F12 dmi.board.name: Z68MX-UD2H-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF12:bd10/12/2011:svnGigabyteTechnologyCo.,Ltd.:pnZ68MX-UD2H-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68MX-UD2H-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: Z68MX-UD2H-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208132/+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 1210136] [NEW] Excessive power management makes HDD tickling when idle
Public bug reported: When the laptop is idle the HDD makes tickling noises every 5 or 10 seconds, this is an excessive power down management issue, the toshiba HDD is brand new and reports full health under SMART and it passes all tests ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-28-generic 3.8.0-28.41 ProcVersionSignature: Ubuntu 3.8.0-28.41-generic 3.8.13.5 Uname: Linux 3.8.0-28-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem1547 F pulseaudio CRDA: country EC: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 20), (3, 17) (5250 - 5330 @ 20), (3, 23), DFS (5735 - 5835 @ 20), (3, 30) Date: Thu Aug 8 15:34:33 2013 HibernationDevice: RESUME=UUID=b9513ceb-c39e-4370-b164-a4e1bb2e9e30 InstallationDate: Installed on 2013-08-08 (0 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) Lsusb: Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 19d2:0167 ZTE WCDMA Technologies MSM MachineType: Notebook W24xCZ MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-28-generic root=UUID=a0c5ecb8-8a17-424a-a0a4-00d38bb68e0a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-28-generic N/A linux-backports-modules-3.8.0-28-generic N/A linux-firmware1.106 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W24xCZ dmi.board.vendor: Notebook dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd03/15/2013:svnNotebook:pnW24xCZ:pvrNotApplicable:rvnNotebook:rnW24xCZ:rvrV3.0:cvnNotebook:ct10:cvrN/A: dmi.product.name: W24xCZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed raring -- 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/1210136 Title: Excessive power management makes HDD tickling when idle Status in “linux” package in Ubuntu: New Bug description: When the laptop is idle the HDD makes tickling noises every 5 or 10 seconds, this is an excessive power down management issue, the toshiba HDD is brand new and reports full health under SMART and it passes all tests ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-28-generic 3.8.0-28.41 ProcVersionSignature: Ubuntu 3.8.0-28.41-generic 3.8.13.5 Uname: Linux 3.8.0-28-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem1547 F pulseaudio CRDA: country EC: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 20), (3, 17) (5250 - 5330 @ 20), (3, 23), DFS (5735 - 5835 @ 20), (3, 30) Date: Thu Aug 8 15:34:33 2013 HibernationDevice: RESUME=UUID=b9513ceb-c39e-4370-b164-a4e1bb2e9e30 InstallationDate: Installed on 2013-08-08 (0 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) Lsusb: Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 19d2:0167 ZTE WCDMA Technologies MSM MachineType: Notebook W24xCZ MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-28-generic root=UUID=a0c5ecb8-8a17-424a-a0a4-00d38bb68e0a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-28-generic N/A linux-backports-modules-3.8.0-28-generic N/A linux-firmware1.106 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W24xCZ dmi.board.vendor: Notebook dmi.board.version:
[Kernel-packages] [Bug 795239] Re: eject: unable to find or open device for: `cdrom' - but my cd is /dev/cdrom1
** Bug watch added: Debian Bug tracker #719110 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719110 ** Also affects: eject (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719110 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to eject in Ubuntu. https://bugs.launchpad.net/bugs/795239 Title: eject: unable to find or open device for: `cdrom' - but my cd is /dev/cdrom1 Status in “eject” package in Ubuntu: In Progress Status in “eject” package in Debian: Unknown Bug description: Binary package hint: eject The eject command does not actually eject my cdrom, unless called as 'eject /dev/cdrom1' The problem seems to be that the eject command's default device is set to /dev/cdrom specifically. Yet, udev will increment the drive name if new cdroms are added or even if you change the cable that the cdrom is connected to. See https://bugzilla.redhat.com/show_bug.cgi?id=570490. udev now assigns permanent names to devices in case they're being hotplugged, which obviously makes sense for servers but a bit sub-optimal for desktops where you generally have no more than one cd... Anyway, as a workaround, I can set up a /media/cdrom symlink to the proper device and then it works. But that's a brittle solution since if I switched my cable back or changed cdroms, I'd have to manually adjust that link again. Possibly eject could be modified to determine the default device by looking first for /dev/cdrom, and then if that's missing, look for /dev/cdrom[0-9]. (Make sure /dev/cdroms is not included in that list obviously.) If there's more than one cd device in the system, either bail out or bravely select the lowest numbered one. The file /proc/sys/dev/cdrom/info could also be read to discover the available devices. This might be preferable to looking for /dev/cdrom*, I'm not sure. This udev change is a generic problem that affects all utilities that interact with the cdrom. It is possible that this could be solved in a more general purpose way by some sort of little lib shared with xine and other cdrom users. In any case, those other tools may have already solved this problem and could be worth examining for code reuse. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eject/+bug/795239/+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 1209179] Re: [Dell inspiron 5323] Atheros AR9485 Wireless Network Adapter [168c:0032] is not enabled for 12.04.2
** Changed in: linux (Ubuntu)
Importance: Undecided = High
--
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/1209179
Title:
[Dell inspiron 5323] Atheros AR9485 Wireless Network Adapter
[168c:0032] is not enabled for 12.04.2
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
CID: 201208-11455
Description:
Atheros AR9485 Wireless Network Adapter [168c:0032] is not enabled for
12.04.2 on Dell inspiron 5323
System Info:
Collected by ubuntu-bug linux
Steps to reproduce the bug:
1. install stock 12.04.2 on Dell inspiron 5323
2. installation is done. check wireless[1]. wireless is not enabled.
3. upgrade system by sudo apt-get dist-upgrade
4. check wireless, still not enabled.
[1]: wireless is not enabled means here when:
a. rfkill list shows Hard blocked:yes
b. sudo showkey -k keycode 240 press/release
c. check the LED indicator of wireless. No light.
d. up-right desktop indicator shows the Enable Wireless is dim
e. lspci shows there is such device
Expected result:
There should be wireless enabled.
Actual result:
No wireless is enabled
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.5.0-36-generic 3.5.0-36.57~precise1
ProcVersionSignature: Ubuntu 3.5.0-36.57~precise1-generic 3.5.7.14
Uname: Linux 3.5.0-36-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu17.3
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1573 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf7f1 irq 46'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:111d76e0,1028057e,00100102
HDA:80862806,80860101,0010'
Controls : 23
Simple ctrls : 10
Date: Wed Aug 7 18:36:47 2013
HibernationDevice: RESUME=UUID=3a3eb018-bf38-4bb5-b2a4-adb450f575c2
InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64
(20130213)
MachineType: Dell Inc. Inspiron 5423
MarkForUpload: True
ProcEnviron:
LANGUAGE=en_US:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
0 inteldrmfb
1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-36-generic
root=UUID=02c41084-3697-47e6-876f-46f6343a36a1 ro quiet splash initcall_debug
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.5.0-36-generic N/A
linux-backports-modules-3.5.0-36-generic N/A
linux-firmware1.79.4
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
SourcePackage: linux
StagingDrivers: rts5139
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/26/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.vendor: Dell Inc.
dmi.board.version: A08
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvrA08:bd11/26/2012:svnDellInc.:pnInspiron5423:pvrNotSpecified:rvnDellInc.:rn:rvrA08:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 5423
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1209179/+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 1210136] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New = 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/1210136 Title: Excessive power management makes HDD tickling when idle Status in “linux” package in Ubuntu: Confirmed Bug description: When the laptop is idle the HDD makes tickling noises every 5 or 10 seconds, this is an excessive power down management issue, the toshiba HDD is brand new and reports full health under SMART and it passes all tests ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-28-generic 3.8.0-28.41 ProcVersionSignature: Ubuntu 3.8.0-28.41-generic 3.8.13.5 Uname: Linux 3.8.0-28-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem1547 F pulseaudio CRDA: country EC: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 20), (3, 17) (5250 - 5330 @ 20), (3, 23), DFS (5735 - 5835 @ 20), (3, 30) Date: Thu Aug 8 15:34:33 2013 HibernationDevice: RESUME=UUID=b9513ceb-c39e-4370-b164-a4e1bb2e9e30 InstallationDate: Installed on 2013-08-08 (0 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) Lsusb: Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 19d2:0167 ZTE WCDMA Technologies MSM MachineType: Notebook W24xCZ MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-28-generic root=UUID=a0c5ecb8-8a17-424a-a0a4-00d38bb68e0a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-28-generic N/A linux-backports-modules-3.8.0-28-generic N/A linux-firmware1.106 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W24xCZ dmi.board.vendor: Notebook dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd03/15/2013:svnNotebook:pnW24xCZ:pvrNotApplicable:rvnNotebook:rnW24xCZ:rvrV3.0:cvnNotebook:ct10:cvrN/A: dmi.product.name: W24xCZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210136/+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 1207970] Re: i915 device or resource busy in some 3D apps
Christopher, I'm not sure what you mean by steps 1 and 2: 1. Check that the bug is fixed in the current development release, and that its bug task is Fix Released This is already done and you've marked it as Fix Released 2. Ensure that the bug report for this issue is public. I'm pretty sure it is. Did you mean some other steps 1 2? -- 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/1207970 Title: i915 device or resource busy in some 3D apps Status in “linux” package in Ubuntu: Fix Released Bug description: How to reproduce: 1. Install wine 2. Install GTAVC in wine 3. Try starting GTAVC in 1280x1024 resolution, press Enter twice to skip non-working intro videos, and when the menu appears, try moving mouse cursor to select New Game 4. See GTAVC crash with Deivce or resource busy in the terminal. Dmesg suggests that it's i915 driver bug. This has worked correctly in e.g. Ubuntu Lucid. Mainline kernel bisect revealed: 3.4.56 good 3.4.55 bad ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-51-generic-pae 3.2.0-51.77 ProcVersionSignature: Ubuntu 3.2.0-51.77-generic-pae 3.2.48 Uname: Linux 3.2.0-51-generic-pae i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruslan 1473 F kded4 ruslan 1669 F kmix CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf20c irq 40' Mixer name : 'Realtek ALC880' Components : 'HDA:10ec0880,0880,00090500' Controls : 39 Simple ctrls : 22 Date: Sat Aug 3 12:54:19 2013 HibernationDevice: RESUME=UUID=ad008e92-9144-4dca-b2cc-b9af0b200051 InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) IwConfig: lono wireless extensions. eth1 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MarkForUpload: True ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-51-generic-pae root=UUID=67cea86f-7ed6-4be5-b574-afde6eb9e831 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.2.0-51-generic-pae N/A linux-backports-modules-3.2.0-51-generic-pae N/A linux-firmware1.79.6 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2005 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: 8I915GMF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd09/27/2005:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn8I915GMF:rvrx.x:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1207970/+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 1208455] Re: general protection fault running apt-get inside double nested kvm VM
Serge mentioned today on IRC that this may be also a glibc issue, but I am not sure what exactly he was looking at and why he thinks so. Apparently ftracing (I guess the qemu process) and some partially inlining clone function (those with .isra extention) were involved. -- 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/1208455 Title: general protection fault running apt-get inside double nested kvm VM Status in “linux” package in Ubuntu: Incomplete Status in “qemu-kvm” package in Ubuntu: New Bug description: Attempting to run apt-get in a nested vm hosted in OpenStack results in a general protection fault in the kernel in the nested VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 814894] Re: [Fit-PC2i] Kernel hangs on high network throughput
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210092
--
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/814894
Title:
[Fit-PC2i] Kernel hangs on high network throughput
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
If A Fit-PC2i receives more than 200Mbit/s of network traffic the
kernel will hang. Cursor stops blinking, machine doesn't respond to
keyboard and mouse input, no longer responds to ARP requests or any
other network traffic.
The problem is triggered every time a 10.04.3 system with kernel
version 2.6.32-33-generic receives more than 200Mbit/s of network
traffic. The bug affects both live system as well as fully installed
system.
The bug can be reproduced by downloading a 1GB file from a server on
the LAN. The bug is only triggered if more than 200Mbit/s is
transfered. If any link on the path between client and server is
100Mbit/s or less the bug cannot be reproduced.
The 8.04.4 live system is not affected by this problem and can receive
600Mbit/s without problems on the same hardware.
Marking this as a security problem because it can in principle be used
to perform a DoS attack.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image (not installed)
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-33.70-generic 2.6.32.41+drm33.18
Uname: Linux 2.6.32-33-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: MID [HDA Intel MID], device 0: ALC662 rev1 Analog [ALC662 rev1
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kasperd1453 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'MID'/'HDA Intel MID at 0xb005 irq 22'
Mixer name : 'Realtek ALC662 rev1'
Components : 'HDA:10ec0662,10ec0662,00100101'
Controls : 33
Simple ctrls : 19
Date: Sat Jul 23 01:43:06 2011
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=e14584e1-caed-4150-9e25-e364d27bebe3
InstallationMedia: Ubuntu 10.04.3 LTS Lucid Lynx - Release i386 (20110720.1)
MachineType: CompuLab CM-iAM/SBC-FITPC2i
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-33-generic
root=UUID=8bf29c49-594d-41b8-8513-ac3cf4bf4e1b ro rootdir=lucid
ProcEnviron:
LANG=en_DK.utf8
SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.7
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
StagingDrivers: rt2870sta
Title: [STAGING]
dmi.bios.date: 09/14/2010
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: NAPA0001.86C..D.1009141059
dmi.board.name: CM-iAM/SBC-FITPC2i
dmi.board.vendor: Intel Corporation
dmi.board.version: 1.x
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: OEM
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvrNAPA0001.86C..D.1009141059:bd09/14/2010:svnCompuLab:pnCM-iAM/SBC-FITPC2i:pvrNotApplicable:rvnIntelCorporation:rnCM-iAM/SBC-FITPC2i:rvr1.x:cvnOEM:ct1:cvrN/A:
dmi.product.name: CM-iAM/SBC-FITPC2i
dmi.product.version: Not Applicable
dmi.sys.vendor: CompuLab
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/814894/+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 795239] Re: eject: unable to find or open device for: `cdrom' - but my cd is /dev/cdrom1
** Changed in: eject (Debian) Status: Unknown = New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to eject in Ubuntu. https://bugs.launchpad.net/bugs/795239 Title: eject: unable to find or open device for: `cdrom' - but my cd is /dev/cdrom1 Status in “eject” package in Ubuntu: In Progress Status in “eject” package in Debian: New Bug description: Binary package hint: eject The eject command does not actually eject my cdrom, unless called as 'eject /dev/cdrom1' The problem seems to be that the eject command's default device is set to /dev/cdrom specifically. Yet, udev will increment the drive name if new cdroms are added or even if you change the cable that the cdrom is connected to. See https://bugzilla.redhat.com/show_bug.cgi?id=570490. udev now assigns permanent names to devices in case they're being hotplugged, which obviously makes sense for servers but a bit sub-optimal for desktops where you generally have no more than one cd... Anyway, as a workaround, I can set up a /media/cdrom symlink to the proper device and then it works. But that's a brittle solution since if I switched my cable back or changed cdroms, I'd have to manually adjust that link again. Possibly eject could be modified to determine the default device by looking first for /dev/cdrom, and then if that's missing, look for /dev/cdrom[0-9]. (Make sure /dev/cdroms is not included in that list obviously.) If there's more than one cd device in the system, either bail out or bravely select the lowest numbered one. The file /proc/sys/dev/cdrom/info could also be read to discover the available devices. This might be preferable to looking for /dev/cdrom*, I'm not sure. This udev change is a generic problem that affects all utilities that interact with the cdrom. It is possible that this could be solved in a more general purpose way by some sort of little lib shared with xine and other cdrom users. In any case, those other tools may have already solved this problem and could be worth examining for code reuse. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eject/+bug/795239/+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
Re: [Kernel-packages] [Bug 1208455] Re: general protection fault running apt-get inside double nested kvm VM
Quoting Stefan Bader (stefan.ba...@canonical.com): Serge mentioned today on IRC that this may be also a glibc issue, but I am not sure what exactly he was looking at and why he thinks so. Apparently ftracing (I guess the qemu process) and some partially inlining clone function (those with .isra extention) were involved. Right, ftrace seems the most likely culprit. In any case, since a newer kernel is confirmed to fix it, disregard anything I said about libc :) -- 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/1208455 Title: general protection fault running apt-get inside double nested kvm VM Status in “linux” package in Ubuntu: Incomplete Status in “qemu-kvm” package in Ubuntu: New Bug description: Attempting to run apt-get in a nested vm hosted in OpenStack results in a general protection fault in the kernel in the nested VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208455/+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 1105900] Re: Latest Kernel Version 3.2.0-36 Causing EXT4-fs Errors
Presently have updated to kernel 3.2.0-49-generic-pae and have monitored over two weeks and not a single ext4 buddy error has been created. Can others move up to this kernel and validate. This seems to have cured my issue. Think I'll lock myself down at this one. -- 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/1105900 Title: Latest Kernel Version 3.2.0-36 Causing EXT4-fs Errors Status in “linux” package in Ubuntu: Confirmed Bug description: System: Ubuntu 12.04.1 x64 Unity desktop --- lsb_release -rd; uname -a Description: Ubuntu 12.04.1 LTS Release: 12.04 Linux Voyager 3.2.0-36-generic #57-Ubuntu SMP Tue Jan 8 21:44:52 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux -- Have not experienced any severe problems with this system from Aug 2012 till Jan 20 2013, when kernel 3.2.0-35 was still the active kernel. 2013-01-20 21:01 kernel 3.2.0-36 was installed by the Ubuntu updater. No installation problems occurred. Ever since K3.2.0-36 was the active kernel, the following problem occurred: On every restart error messages like these could be read in /var/log/syslog: syslog:Jan 22 00:44:37 Voyager kernel: [3.624421] EXT4-fs (sda5): orphan cleanup on readonly fs syslog:Jan 22 00:44:37 Voyager kernel: [3.652470] EXT4-fs (sda5): ext4_orphan_cleanup: deleting unreferenced inode 2886456 syslog:Jan 22 00:44:37 Voyager kernel: [3.652671] EXT4-fs (sda5): ext4_orphan_cleanup: deleting unreferenced inode 2886232 syslog:Jan 22 00:44:37 Voyager kernel: [3.652688] EXT4-fs (sda5): ext4_orphan_cleanup: deleting unreferenced inode 2886450 syslog:Jan 22 00:44:37 Voyager kernel: [3.678434] EXT4-fs (sda5): ext4_orphan_cleanup: deleting unreferenced inode 2369342 syslog:Jan 22 00:44:37 Voyager kernel: [3.689458] EXT4-fs (sda5): 4 orphan inodes deleted syslog:Jan 22 00:44:37 Voyager kernel: [3.689462] EXT4-fs (sda5): recovery complete This happens no matter whether the system is rebooted (warm reboot) or shutdown and restarted later (cold reboot). The relevant thing is that in the session which is shutdown the active kernel has to be K3.2.0-36. The error will be detected in the next session started after reboot. The workaround was going back to K3.2.0-35. During the first reboot the errors left behind by the previous K3.2.0-36 session were cleaned up. From then on sticking with K3.2.0-35 the errors would not return after any reboot. Conclusion: Telling from the symptoms Ubuntu 12.04.1 with K3.2.0-36 does not umount the root filesystem properly or does some other bad thing to leave behind orphaned inodes. Returning to K3.2.0-35 will work around the problem Note: --- (1) I have seen this problem on 3 different machines (different hardware) running Ubuntu 12.04.1 x64 and Ubuntu 12.04.1 x86. So it is not a problem caused by a flaw of one special machine. (2) I have seen the same problem after updating Ubuntu 12.10 from K3.5.0-17 to K3.5.0-22. This suggests some change in the latest kernel editions which is common to the current Ubuntu kernels may be involved. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-36-generic 3.2.0-36.57 ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35 Uname: Linux 3.2.0-36-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: karl 2234 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfdff4000 irq 44' Mixer name : 'Realtek ALC888' Components : 'HDA:10ec0888,1462735b,0011' Controls : 45 Simple ctrls : 21 Date: Sat Jan 26 10:50:56 2013 HibernationDevice: RESUME=UUID=20f6167d-0136-4d21-a1d9-fb36954a0815 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: MEDIONPC MS-7358 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-36-generic root=UUID=7eb4fefd-d144-4bdb-9848-199970e85265 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/karl not ours. No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.2.0-36-generic N/A linux-backports-modules-3.2.0-36-generic N/A linux-firmware1.79.1 RfKill: SourcePackage: linux
[Kernel-packages] [Bug 1153252] Re: 14e4:4727 [Samsung NP-RF511-S03SE] wifi stops working when laptop lid is closed
Tested out with 10.04.4, the behaviour is similar to saucy (gives out ping: sendmsg: No buffer space available, recovers after that). ** Tags added: lucid -- 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/1153252 Title: 14e4:4727 [Samsung NP-RF511-S03SE] wifi stops working when laptop lid is closed Status in “linux” package in Ubuntu: Incomplete Bug description: In Ubuntu 12.10, when I close the laptop lid, the wlan connection is closed. Wired (ethernet) connections keep working normally. This prevents using only external monitor in places where wired connections are not accessible and forces the user to keep the laptop display on even if it is not needed. Changing the power manager settings to Do nothing does not affect this. It also does not matter if the laptop is plugged in or not. Apparently, at some point, disabling the screen saver would fix this issue. However, there is no such setting on Ubuntu 12.10. --- ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: unksi 2255 F pulseaudio /dev/snd/pcmC0D0p: unksi 2255 F...m pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. DistroRelease: Ubuntu 12.10 InstallationDate: Installed on 2013-03-01 (16 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711 MarkForUpload: True NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-generic root=UUID=a7bbcbf4-2e43-442d-a6e9-c22e2a1016c0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.5.0-25.39-generic 3.5.7.4 RelatedPackageVersions: linux-restricted-modules-3.5.0-25-generic N/A linux-backports-modules-3.5.0-25-generic N/A linux-firmware1.95 Tags: quantal running-unity Uname: Linux 3.5.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 11/27/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 17HX.M045.20121127.SSH dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: RF511/RF411/RF711 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 17HX dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr17HX.M045.20121127.SSH:bd11/27/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pnRF511/RF411/RF711:pvr17HX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnRF511/RF411/RF711:rvr17HX:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: RF511/RF411/RF711 dmi.product.version: 17HX dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1153252/+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 1153627] Re: Kernel hangs while booting if there is a monitor connected to DP2
I've tried patch in comment #5 and it solves this issue in 12.04. Also, I've tested latest development release and I can confirm that this issues is solved. -- 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/1153627 Title: Kernel hangs while booting if there is a monitor connected to DP2 Status in “linux” package in Ubuntu: Incomplete Bug description: I'm trying triple monitor configuration on HD4000: - 1650x1050 on VGA1 - 1920x1080 on DP2 - 1920x1080 on DP3 Kernel hangs on boot if there is a monitor attached to DP2. If I attach monitor after boot, changing resolution on DP2 one CPU core becomes 100% busy with continuous errors: [drm:intel_dp_start_link_train], training pattern 1 signal levels [drm:intel_dp_start_link_train], training pattern 1 signal levels 0200 [drm:intel_dp_start_link_train], training pattern 1 signal levels 0400 BTW, Same triple monitor configuration works fine in Windows 7 so I assume that hardware is ok. Please advise what can be done next? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-25-generic 3.5.0-25.39~precise1 ProcVersionSignature: Ubuntu 3.5.0-25.39~precise1-generic 3.5.7.4 Uname: Linux 3.5.0-25-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.0.1-0ubuntu17.1 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: [Errno 2] No such file or directory CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory Date: Mon Feb 6 15:34:43 2012 IwConfig: Error: [Errno 2] No such file or directory Lspci: Error: [Errno 2] No such file or directory MachineType: ICP/iEi B207 MarkForUpload: True PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-generic root=UUID=0cccb37a-5761-45a8-b9db-1e5f6eebbb80 ro drm.debug=0x06 RelatedPackageVersions: linux-restricted-modules-3.5.0-25-generic N/A linux-backports-modules-3.5.0-25-generic N/A linux-firmware1.79.2 RfKill: Error: [Errno 2] No such file or directory SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B207 dmi.board.vendor: ICP/iEi dmi.board.version: V1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/10/2012:svnICP/iEi:pnB207:pvrV1.0:rvnICP/iEi:rnB207:rvrV1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: B207 dmi.product.version: V1.0 dmi.sys.vendor: ICP/iEi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1153627/+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 1208568] Re: [LENOVO 20081] hibernate/resume failure
Ok, Christopher? I'll try it. -- 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/1208568 Title: [LENOVO 20081] hibernate/resume failure Status in “linux” package in Ubuntu: Incomplete Bug description: lenovo g575 does not wake up after hibernation. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.10.0-6-generic 3.10.0-6.17 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 Annotation: This occured during a previous hibernate and prevented it from resuming properly. ApportVersion: 2.12-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alien 1809 F pulseaudio Date: Mon Aug 5 18:54:05 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=1eb90013-804e-4f5d-a6ea-b4102a13357e InstallationDate: Installed on 2013-05-23 (73 days ago) InstallationMedia: Kubuntu 13.04 Raring Ringtail - Release i386 (20130424) InterpreterPath: /usr/bin/python3.3 MachineType: LENOVO 20081 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=UUID=7274445d-de7d-46bc-8cc8-8bf54e2f3749 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware1.113 SourcePackage: linux Title: [LENOVO 20081] hibernate/resume failure UpgradeStatus: Upgraded to saucy on 2013-08-03 (1 days ago) UserGroups: dmi.bios.date: 05/03/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 41CN28WW(V2.04) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Inagua dmi.board.vendor: LENOVO dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvr41CN28WW(V2.04):bd05/03/2012:svnLENOVO:pn20081:pvrLenovoG575:rvnLENOVO:rnInagua:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: 20081 dmi.product.version: Lenovo G575 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208568/+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
