[Kernel-packages] [Bug 1098016] Re: Kernel Oops with bluetooth/SDP browse (Unable to handle kernel paging request)
I got what looks to be this crash running bluez 4.101 on a Gumstix device using a custom Yocto build. I'm not sure it is the exact same crash, but it looks about the same. See attachment for dump. ** Attachment added: crash.log https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1098016/+attachment/3918881/+files/crash.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1098016 Title: Kernel Oops with bluetooth/SDP browse (Unable to handle kernel paging request) Status in “bluez” package in Ubuntu: Confirmed Bug description: Running a Pandaboard rev A3 with Ubuntu 12.04.1 LTS with the ti-omap4 kernel. Have set up bluetooth (bluez) and was able to see the pandaboard via bluetooth in the Mac's Set up Bluetooth Device. Linux crashed with: [12178.608489] Unable to handle kernel paging request at virtual address 00100104 [12178.617156] pgd = c0004000 [12178.621459] [00100104] *pgd=nt 00 [12178.628173] Internal error: Oops: 817 [#1] PREEMPT SMP ARM [12178.635406] Modules linked in: btwilink dm_crypt wl12xx wlcore mac80211 cfg80211 rfcomm bnep bluetooth omapdce(C) rpmsg_omx omaprpc(C) ppdev omap_remoteproc rpmsg_resmgr_common remoteproc lp omap_rpmsg_resmgr parport rpmsg_resmgr virtio_rpmsg_bus virtio virtio_ring dm_multipath wlcore_sdio gpio_keys leds_gpio dm_mirror dm_region_hash dm_log btrfs zlib_deflate libcrc32c [12178.671234] CPU: 0Tainted: G C(3.4.0-1489-omap4 #18-Ubuntu) [12178.678955] PC is at l2cap_chan_destroy+0x2c/0x88 [bluetooth] [12178.685180] LR is at get_parent_ip+0x14/0x30 [12178.689819] pc : [bf1b4314]lr : [c0075b70]psr: 600f0113 [12178.689849] sp : ed069d58 ip : ed069cf8 fp : ed069d6c [12178.702209] r10: eaa06e20 r9 : 0001 r8 : 007b [12178.707855] r7 : ea9ed1c4 r6 : eb515400 r5 : eaa06c00 r4 : eaa06c00 [12178.714904] r3 : 00200200 r2 : 00100100 r1 : r0 : bf1c1728 [12178.721954] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel [12178.729858] Control: 10c5387d Table: ab4d804a DAC: 0015 [12178.736053] [12178.736053] LR: 0xc0075af0: ... I'm running the following kernel: 3.4.0-1489-omap4 #18-Ubuntu SMP PREEMPT Tue Dec 11 10:06:12 UTC 2012 armv7l armv7l armv7l GNU/Linux I happened to have hcidump -X running on the console, it looks like the Mac was doing a SDP browse. Here's the full output of the hcidump -X followed by the kernel oops (actually, there's a second oops following the first). HCI Event: Connect Request (0x04) plen 10 bdaddr 00:11:22:33:44:55 class 0x3a010c type ACL HCI Command: Accept Connection Request (0x01|0x0009) plen 7 bdaddr 00:11:22:33:44:55 role 0x00 Role: Master HCI Event: Command Status (0x0f) plen 4 Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1 HCI Event: Role Change (0x12) plen 8 status 0x21 bdaddr 00:11:22:33:44:55 role 0x01 Error: Role Change Not Allowed HCI Event: Connect Complete (0x03) plen 11 status 0x00 handle 1 bdaddr 00:11:22:33:44:55 type ACL encrypt 0x00 HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2 handle 1 HCI Event: Page Scan Repetition Mode Change (0x20) plen 7 bdaddr 00:11:22:33:44:55 mode 0 HCI Event: Max Slots Change (0x1b) plen 3 handle 1 slots 5 HCI Event: Command Status (0x0f) plen 4 Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1 HCI Event: Read Remote Supported Features (0x0b) plen 11 status 0x00 handle 1 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 HCI Command: Read Remote Extended Features (0x01|0x001c) plen 3 handle 1 page 1 HCI Event: Command Status (0x0f) plen 4 Read Remote Extended Features (0x01|0x001c) status 0x00 ncmd 1 HCI Event: Read Remote Extended Features (0x23) plen 13 status 0x00 handle 1 page 1 max 1 Features: 0x07 0x00 0x00 0x00 0x00 0x00 0x00 0x00 HCI Command: Remote Name Request (0x01|0x0019) plen 10 bdaddr 00:11:22:33:44:55 mode 2 clkoffset 0x HCI Event: Command Status (0x0f) plen 4 Remote Name Request (0x01|0x0019) status 0x00 ncmd 1 HCI Event: Remote Name Req Complete (0x07) plen 255 status 0x00 bdaddr 00:11:22:33:44:55 name 'mbp' HCI Event: IO Capability Response (0x32) plen 9 bdaddr 00:11:22:33:44:55 capability 0x01 oob 0x00 auth 0x03 Capability: DisplayYesNo (OOB data not present) Authentication: Dedicated Bonding (MITM Protection) HCI Event: IO Capability Request (0x31) plen 6 bdaddr 00:11:22:33:44:55 HCI Command: IO Capability Request Reply (0x01|0x002b) plen 9 bdaddr 00:11:22:33:44:55 capability 0x03 oob 0x00 auth 0x02 Capability: NoInputNoOutput (OOB data not present) Authentication: Dedicated Bonding (No MITM Protection) HCI Event: Command Complete (0x0e) plen 10 IO
[Kernel-packages] [Bug 1255797] Re: Ubuntu
I saw some errors in dmesg about your NICs, but I don't know if these are why you've filed the bug report; can you add some details about what you're seeing? Thanks -- 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/1255797 Title: Ubuntu Status in “linux” package in Ubuntu: New Bug description: Server actually have Postfix ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-25-generic-pae 2.6.32-25.44 Regression: No Reproducible: No ProcVersionSignature: Ubuntu 2.6.32-25.44-generic-pae 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic-pae i686 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: aplay: device_list:223: no soundcards found... Architecture: i386 ArecordDevices: arecord: device_list:223: no soundcards found... Date: Wed Nov 27 19:39:25 2013 Frequency: Once every few days. InstallationMedia: Ubuntu-Server 10.04 LTS Lucid Lynx - Release i386 (20100427) Lsusb: Bus 001 Device 002: ID 059b:0370 Iomega Corp. Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: IBM eserver xSeries 345 -[8670M1X]- PciMultimedia: ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-25-generic-pae root=UUID=e3fd61ac-4c1b-45c1-a86e-6b43969e860e ro quiet ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=es_MX.UTF-8 SourcePackage: linux dmi.bios.date: 06/30/2004 dmi.bios.vendor: IBM dmi.bios.version: -[GEE157CUS-1.17]- dmi.board.vendor: IBM dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: IBM dmi.modalias: dmi:bvnIBM:bvr-[GEE157CUS-1.17]-:bd06/30/2004:svnIBM:pneserverxSeries345-[8670M1X]-:pvr:rvnIBM:rn:rvr:cvnIBM:ct17:cvr: dmi.product.name: eserver xSeries 345 -[8670M1X]- dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255797/+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 1255797] Re: Ubuntu
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a regular (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1255797 Title: Ubuntu Status in “linux” package in Ubuntu: New Bug description: Server actually have Postfix ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-25-generic-pae 2.6.32-25.44 Regression: No Reproducible: No ProcVersionSignature: Ubuntu 2.6.32-25.44-generic-pae 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic-pae i686 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: aplay: device_list:223: no soundcards found... Architecture: i386 ArecordDevices: arecord: device_list:223: no soundcards found... Date: Wed Nov 27 19:39:25 2013 Frequency: Once every few days. InstallationMedia: Ubuntu-Server 10.04 LTS Lucid Lynx - Release i386 (20100427) Lsusb: Bus 001 Device 002: ID 059b:0370 Iomega Corp. Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: IBM eserver xSeries 345 -[8670M1X]- PciMultimedia: ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-25-generic-pae root=UUID=e3fd61ac-4c1b-45c1-a86e-6b43969e860e ro quiet ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=es_MX.UTF-8 SourcePackage: linux dmi.bios.date: 06/30/2004 dmi.bios.vendor: IBM dmi.bios.version: -[GEE157CUS-1.17]- dmi.board.vendor: IBM dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: IBM dmi.modalias: dmi:bvnIBM:bvr-[GEE157CUS-1.17]-:bd06/30/2004:svnIBM:pneserverxSeries345-[8670M1X]-:pvr:rvnIBM:rn:rvr:cvnIBM:ct17:cvr: dmi.product.name: eserver xSeries 345 -[8670M1X]- dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255797/+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 1107150] Re: B75 Chipset I/O Problems
Great to finally see this bug being worked on... I found a bunch of similar bug reports that were finally closed (and supposedly solved) because the original bug reporter ended up installing a 64-bit kernel instead. Here's what I found out so far: * This bug only affects writing to block devices. Read speeds are absolutely fine. It would be nice if the other people could confirm this! * This bug isn't related to the B75 chipset. I'm also experiencing this bug on a somewhat older chipset. I believe I'm using an Intel Q57 Express chipset but I doubt whether this is really relevant. * It will only trigger with the x86 kernel, not the amd64 kernel. * This bug _probably_ isn't limited to Ubuntu, Ubuntu is just the only distro that triggers it. I tested the following distributions: + Fedora 19 (32 bit) live cd (3.9.x kernel) - works fine + OpenSuSe 13.1 (32 bit) live cd (3.11 kernel) - works fine + Ubuntu 13.10 (32 bit) live cd (3.11 kernel) - doesn't work + Ubuntu 13.10 (64 bit) live cd (3.11 kernel) - works fine + Linux Mint 16 (32 bit) live cd (3.11 kernel) - doesn't work + Debian 7.2 (32 bit) live cd (3.2 kernel) - works fine I then went back to Ubuntu 12.10 32 bit (3.5.5 kernel) and confirmed that: + Running with only 8 Gigs of RAM gives me write speeds of 180-200Mb/sec + Running with 16 Gigs of RAM gives me write speeds of 160-180Mb/sec + Running with 32 Gigs of RAM gives me write speeds of 1.5-5.5Mb/sec I downloaded a stock 3.5.5 kernel tarball and compiled it with the ubuntu kernel config. The problem persists. There is a similar bug where pc's suddenly get terrible write speeds to block devices after waking up from suspend. This bug is caused by the fact that on some pc's MTRR registers change after waking up. After comparing Ubuntu, Fedora and Suse kernel configs, I noticed that Ubuntu is the only distro using the MTRR sanitizer. I disabled it but the problem persists. This definitely seems like an mm problem to me. I'd like to test the latest test kernel you've built but it's only available for amd64 (which never had the problem anyway). -- 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/1107150 Title: B75 Chipset I/O Problems Status in “linux” package in Ubuntu: Confirmed Bug description: I built a new system and installed Ubuntu 12.10. The system has the following specifications: Samsung 840 Pro 128 GB Gigabyte P75-D3 Intel i7 3770 32 GB Ram Western Digital 1 TB Black (mounted as /home) Western Digital 3 TB Green (mounted as /media/data_drive) The initial Ubuntu 12.10 install took almost 6 hours as transfer rates were very slow. After reboot everything appeared very fast. However when I did an apt-get update the download took 20 seconds and the processing of lists took 19 minutes. I had 12.10 installed on another computer which was working great (older Althon system) so I installed the drive and tested the new machine. It suffered the same performance problems. I installed Windows 7 and performed speeds tests, it reported great results. I installed 12.04 onto the 1 TB drive and it did not suffer the same performance problems. Everything ran great. I then upgraded 12.10 to 13.04 (January 27, 2013) and it too suffered from the performance issue. It appears that a change between 12.04 to 12.10 impacts AHCI based systems specifically running the Intel B75 chipset. I am not certain but I think that either the motherboard is misrepresenting something (that 12.04 ignores but it impacts 12.10) or the kernel is not detecting the system correctly. I created a couple of pastebins with data collected: 12.10 Install: http://pastebin.ubuntu.com/1561660/ 12.04 Live Disk (was checked against installed version and data is mostly the same): http://paste.ubuntu.com/1565140/ I have a thread on the ubuntu forums that may provide additional details: http://ubuntuforums.org/showthread.php?t=2104709 I also started an e-mail thread to the ubuntu-users mailing list: http://ubuntu.5.n6.nabble.com/Seeking-Help-td5010422.html I have done a lot of troubleshooting and I feel that the problem must either be the kernel or the bios misrepresenting information. In either case I am stuck without any idea of where to go next with the debuging and diagnoses path. If any additional information needs to be collected, please let me know and I will work to assist. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bakers 1729 F pulseaudio /dev/snd/controlC0: bakers 1729 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
[Kernel-packages] [Bug 1255797] 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/1255797 Title: Ubuntu Status in “linux” package in Ubuntu: Confirmed Bug description: Server actually have Postfix ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-25-generic-pae 2.6.32-25.44 Regression: No Reproducible: No ProcVersionSignature: Ubuntu 2.6.32-25.44-generic-pae 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic-pae i686 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: aplay: device_list:223: no soundcards found... Architecture: i386 ArecordDevices: arecord: device_list:223: no soundcards found... Date: Wed Nov 27 19:39:25 2013 Frequency: Once every few days. InstallationMedia: Ubuntu-Server 10.04 LTS Lucid Lynx - Release i386 (20100427) Lsusb: Bus 001 Device 002: ID 059b:0370 Iomega Corp. Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: IBM eserver xSeries 345 -[8670M1X]- PciMultimedia: ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-25-generic-pae root=UUID=e3fd61ac-4c1b-45c1-a86e-6b43969e860e ro quiet ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=es_MX.UTF-8 SourcePackage: linux dmi.bios.date: 06/30/2004 dmi.bios.vendor: IBM dmi.bios.version: -[GEE157CUS-1.17]- dmi.board.vendor: IBM dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: IBM dmi.modalias: dmi:bvnIBM:bvr-[GEE157CUS-1.17]-:bd06/30/2004:svnIBM:pneserverxSeries345-[8670M1X]-:pvr:rvnIBM:rn:rvr:cvnIBM:ct17:cvr: dmi.product.name: eserver xSeries 345 -[8670M1X]- dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255797/+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 1089413] Re: Touchpad not recognised on Dell Latitude E6230, 6330, 6430, 6530, 5430, 5530
** Changed in: oem-priority/precise
Status: Fix Committed = Fix Released
** Changed in: oem-priority/precise
Assignee: James M. Leddy (jm-leddy) = (unassigned)
** Changed in: linux-lts-quantal (Ubuntu Precise)
Status: Fix Committed = Fix Released
--
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/1089413
Title:
Touchpad not recognised on Dell Latitude E6230, 6330, 6430, 6530,
5430, 5530
Status in The Linux Kernel:
Confirmed
Status in OEM Priority Project:
Fix Released
Status in OEM Priority Project precise series:
Fix Released
Status in OEM Priority Project quantal series:
Fix Released
Status in OEM Priority Project raring series:
Fix Released
Status in “linux” package in Ubuntu:
Fix Released
Status in “linux-lts-quantal” package in Ubuntu:
Invalid
Status in “linux” source package in Precise:
Invalid
Status in “linux-lts-quantal” source package in Precise:
Fix Released
Status in “linux” source package in Quantal:
Fix Released
Status in “linux” source package in Raring:
Fix Released
Bug description:
lsinput just shows a PS/2 mouse.
This would be important to fix because the touchpad isn't configurable and is
hard to use because it's
so close to kb can't configure to ignore touches coinciding with keypresses.
It looks like similar bugs were recently fixed in Precise for some
other Dell models: #606238 and #978807
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-34-generic 3.2.0-34.53
ProcVersionSignature: Ubuntu 3.2.0-34.53-generic 3.2.33
Uname: Linux 3.2.0-34-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu15
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: erno 11662 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf7e3 irq 48'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:111d76df,10280532,00100203
HDA:80862806,80860101,0010'
Controls : 38
Simple ctrls : 14
Date: Wed Dec 12 16:36:19 2012
HibernationDevice: RESUME=UUID=c6e93863-3d4b-45af-9443-4bbaa3228533
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64
(20120425)
MachineType: Dell Inc. Latitude E6230
MarkForUpload: True
ProcEnviron:
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-34-generic
root=UUID=cf99adf8-a273-41e1-a40d-d65b6d9e1f21 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-34-generic N/A
linux-backports-modules-3.2.0-34-generic N/A
linux-firmware1.79.1
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/25/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A01
dmi.board.name: 0R6V5Y
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA01:bd04/25/2012:svnDellInc.:pnLatitudeE6230:pvr01:rvnDellInc.:rn0R6V5Y:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6230
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1089413/+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 1252422] Re: CVE-2013-4579
** Description changed: - ath9k_htc improperly updates MAC address + The ath9k_htc_set_bssid_mask function in + drivers/net/wireless/ath/ath9k/htc_drv_main.c in the Linux kernel + through 3.12 uses a BSSID masking approach to determine the set of MAC + addresses on which a Wi-Fi device is listening, which allows remote + attackers to discover the original MAC address after spoofing by sending + a series of packets to MAC addresses with certain bit manipulations. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1252422 Title: CVE-2013-4579 Status in “linux” package in Ubuntu: New Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: New Status in “linux” source package in Lucid: New Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: New Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: New Status in “linux-armadaxp” source package in Precise: New Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: New Status in “linux-lts-raring” source package in Precise: New Status in “linux-lts-saucy” source package in Precise: New Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New Status in “linux” source package in Quantal: New Status in “linux-armadaxp” source package in Quantal: New Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: New Status in “linux-lts-backport-natty” source package in Quantal: New Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: New Status in “linux” source package in Raring: New Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: New Status in “linux-lts-backport-natty” source package in Raring: New Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: New Status in “linux” source package in Saucy: New Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: New Status in “linux-lts-backport-natty” source package in Saucy: New Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: New Status in “linux” source package in Trusty: New Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid Status in “linux-fsl-imx51” source package in Trusty: Invalid Status in
[Kernel-packages] [Bug 1244438] Re: EOL notification system required for HWE kernels in LTSs
** Changed in: linux (Ubuntu) Assignee: Canonical Kernel Team (canonical-kernel-team) = Andy Whitcroft (apw) -- 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/1244438 Title: EOL notification system required for HWE kernels in LTSs Status in Release Notes for Ubuntu: New Status in “landscape” package in Ubuntu: New Status in “linux” package in Ubuntu: Triaged Status in “unattended-upgrades” package in Ubuntu: New Status in “update-manager” package in Ubuntu: New Status in “update-motd” package in Ubuntu: New Bug description: We need to have some mechanism to allow us to record that you have an EOL kernel installed which will no longer recieve updates. For example for the kernel when a kernel is going EOL the last upload should include an appropriate file: /var/lib/update-notifier/kernel-eol We need to coordinate this with the notifier itself to ensure it is displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1244438/+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 1252424] Re: CVE-2013-4588
** Description changed: - Linux kernel built with the IP Virtual Server(CONFIG_IP_VS) support is - vulnerable to a buffer overflow flaw. It could occur while setting or - retrieving socket options via setsockopt(2) or getsockopt(2) calls. - Though a user needs to have CAP_NET_ADMIN privileges to perform these - IP_VS operations. A user/program with CAP_NET_ADMIN privileges could use - this flaw to further escalate their privileges on a system. + Multiple stack-based buffer overflows in net/netfilter/ipvs/ip_vs_ctl.c + in the Linux kernel before 2.6.33, when CONFIG_IP_VS is used, allow + local users to gain privileges by leveraging the CAP_NET_ADMIN + capability for (1) a getsockopt system call, related to the + do_ip_vs_get_ctl function, or (2) a setsockopt system call, related to + the do_ip_vs_set_ctl function. A user/program with CAP_NET_ADMIN + privileges could use this flaw to further escalate their privileges on a + system. Break-Fix: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 04bcef2a83f40c6db24222b27a52892cba39dffb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1252424 Title: CVE-2013-4588 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: New Status in “linux” source package in Lucid: Fix Committed Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: Fix Committed Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: Invalid Status in “linux-armadaxp” source package in Precise: Invalid Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: Invalid Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Fix Committed Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: Invalid Status in “linux” source package in Quantal: Invalid Status in “linux-armadaxp” source package in Quantal: Invalid Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: New Status in “linux-lts-backport-natty” source package in Quantal: New Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: Invalid Status in “linux” source package in Raring: Invalid Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: New Status in “linux-lts-backport-natty” source package in Raring: New Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: Invalid Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy:
[Kernel-packages] [Bug 1255522] Re: [Acer Aspire 5943G] Slow copy transfer rates by bad USB 2.0 detection in external usb storage devices
Christopher, as far I can tell, I see this slow copy transfer rates since Raring at least, but I didn't know then why was the cause for that. Now it seems the bad detection of USB 2.0. But this could be failing since 2007 if you read the comments of bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/177235 -- 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/1255522 Title: [Acer Aspire 5943G] Slow copy transfer rates by bad USB 2.0 detection in external usb storage devices Status in “linux” package in Ubuntu: Incomplete Bug description: Confirmed issue with slow transfer rates (1.5 MB/s) for 3 different external USB 2.0 hardisk (toshiba 1 TB, SAMSUNG 512 GB, Hitachi 1 TB) with 3.12.0-4-generic from trusty. It is mainly a bad detection as USB 1.0 instead of USB 2.0 in dmesg (check_highspeed is indeed bogus). Copy 20 GB takes days, instead of hours for this issue. The issue is mainly to copy or move files to a USB external storage device from the laptop or desktop. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-4-generic 3.12.0-4.10 ProcVersionSignature: Ubuntu 3.12.0-4.10-generic 3.12.1 Uname: Linux 3.12.0-4-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.12.7-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shakaran 3667 F pulseaudio /dev/snd/controlC0: shakaran 3667 F pulseaudio /dev/snd/pcmC0D0p: shakaran 3667 F...m pulseaudio CurrentDesktop: Unity Date: Wed Nov 27 13:19:24 2013 HibernationDevice: RESUME=UUID=ca085202-e6f9-4736-b311-6d9a361ec3d6 InstallationDate: Installed on 2013-02-03 (297 days ago) InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) MachineType: Acer Aspire 5943G ProcFB: 0 simple ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-4-generic root=UUID=7f18d659-ec06-4afe-b3be-13b15de376b2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.12.0-4-generic N/A linux-backports-modules-3.12.0-4-generic N/A linux-firmware1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-10-31 (27 days ago) dmi.bios.date: 10/21/2010 dmi.bios.vendor: Acer dmi.bios.version: V1.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5943G dmi.board.vendor: Acer dmi.board.version: V1.15 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.15 dmi.modalias: dmi:bvnAcer:bvrV1.15:bd10/21/2010:svnAcer:pnAspire5943G:pvrV1.15:rvnAcer:rnAspire5943G:rvrV1.15:cvnAcer:ct10:cvrV1.15: dmi.product.name: Aspire 5943G dmi.product.version: V1.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255522/+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 1028137] Re: [Acer Aspire 5943G] hid-generic 0003:046D:C315.001E: can't reset device, status -71
when it stops to work I have to unplug the device and plug it in again. However there are still kernel messages. Maybe s it is useful if we can know what means the hid-generic status codes (-71) or a more detailed message explaining why can't reset the device or because it needs reset the device. I find this bug also related https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1103164 -- 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/1028137 Title: [Acer Aspire 5943G] hid-generic 0003:046D:C315.001E: can't reset device, status -71 Status in “linux” package in Ubuntu: Incomplete Bug description: I don't know if it is the right package for report but anyway. I have a keyboard and mouse connected to a base platform for laptops with a fan and a USB hub (4 spaces) (it helps to avoid hot restarts by heat on summer and get more USB spaces for plug gadgets). $ lsusb Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0020 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 036: ID 0a05:7220 Bus 001 Device 008: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth Bus 001 Device 004: ID 1c7a:0801 LighTuning Technology Inc. Fingerprint Reader Bus 002 Device 004: ID 064e:a219 Suyin Corp. 1.3M WebCam (notebook emachines E730, Acer sub-brand) Bus 001 Device 038: ID 046d:c045 Logitech, Inc. Optical Mouse Bus 001 Device 037: ID 046d:c315 Logitech, Inc. Classic New Touch Keyboard If I plug/unplug the only difference line is for 0a05:7220: $ lsusb -D 0a05:7220 Cannot open 0a05:7220 When I plug/unplug the base always show the same on dmesg: [1003500.857258] hid-generic 0003:046D:C045.001D: can't reset device, :00:1d.0-1.1.1/input0, status -71 [1003500.858251] hid-generic 0003:046D:C315.001E: can't reset device, :00:1d.0-1.1.4/input0, status -71 [1003500.861183] usb 2-1.1: clear tt 1 (0160) error -71 [1003500.865210] hid-generic 0003:046D:C045.001D: can't reset device, :00:1d.0-1.1.1/input0, status -71 [1003500.865301] usb 2-1.1: clear tt 1 (0170) error -71 [1003500.869430] usb 2-1.1: clear tt 1 (0160) error -71 [1003500.873579] hid-generic 0003:046D:C315.001E: can't reset device, :00:1d.0-1.1.4/input0, status -71 [1003500.877580] usb 2-1.1: clear tt 1 (0170) error -71 [1003500.880567] hid-generic 0003:046D:C045.001D: can't reset device, :00:1d.0-1.1.1/input0, status -71 [1003500.881931] hid-generic 0003:046D:C315.001E: can't reset device, :00:1d.0-1.1.4/input0, status -71 [1003500.884565] usb 2-1.1: clear tt 1 (0160) error -71 [1003500.888711] usb 2-1.1: clear tt 1 (0170) error -71 [1003500.888963] hid-generic 0003:046D:C045.001D: can't reset device, :00:1d.0-1.1.1/input0, status -71 [1003500.892914] usb 2-1.1: clear tt 1 (0160) error -71 [1003500.896927] hid-generic 0003:046D:C045.001D: can't reset device, :00:1d.0-1.1.1/input0, status -71 [1003500.897546] hid-generic 0003:046D:C315.001E: can't reset device, :00:1d.0-1.1.4/input0, status -71 [1003500.900893] usb 2-1.1: clear tt 1 (0160) error -71 [1003500.905018] usb 2-1.1: clear tt 1 (0170) error -71 [1003500.912665] hid-generic 0003:046D:C045.001D: can't reset device, :00:1d.0-1.1.1/input0, status -71 [1003500.913567] hid-generic 0003:046D:C315.001E: can't reset device, :00:1d.0-1.1.4/input0, status -71 [1003500.916630] usb 2-1.1: clear tt 1 (0160) error -71 [1003500.920766] usb 2-1.1: clear tt 1 (0170) error -71 [1003500.920942] hid-generic 0003:046D:C045.001D: can't reset device, :00:1d.0-1.1.1/input0, status -71 [1003500.924914] usb 2-1.1: clear tt 1 (0160) error -71 [1003500.928902] hid-generic 0003:046D:C045.001D: can't reset device, :00:1d.0-1.1.1/input0, status -71 [1003500.929516] hid-generic 0003:046D:C315.001E: can't reset device, :00:1d.0-1.1.4/input0, status -71 [1003500.932865] usb 2-1.1: clear tt 1 (0160) error -71 [1003500.937209] usb 2-1.1: clear tt 1 (0170) error -71 [1003500.941012] usb 2-1.1: USB disconnect, device number 21 [1003500.941018] usb 2-1.1.1: USB disconnect, device number 22 [1003500.944612] hid-generic 0003:046D:C045.001D: can't reset device, :00:1d.0-1.1.1/input0, status -71 [1003500.944621] usb 2-1.1: clear tt 1 (0160) error -19 [1003500.956250] usb 2-1.1.4: USB disconnect, device number 23 [1003505.051309] usb 2-1.1: new high-speed USB device number 24 using ehci_hcd [1003505.143985] hub 2-1.1:1.0: USB hub found [1003505.144253] hub 2-1.1:1.0: 4 ports detected [1003505.506884] usb 2-1.1.1: new low-speed USB device number 25 using ehci_hcd [1003505.609274] input: Logitech USB-PS/2 Optical Mouse as
[Kernel-packages] [Bug 1089105] Re: [Lenovo V480c Notebook]: System fails to resume properly from suspend or trackpad doesn't work after resume
Also affects 'lightdm' as it might be used for replace gnome-screensaver
in 14.04
(https://wiki.ubuntu.com/Unity/Desktop/14.04/Unity7GreeterPolish/LockScreen)
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lightdm (Ubuntu Precise)
Status: New = Invalid
** Changed in: lightdm (Ubuntu Quantal)
Status: New = Invalid
** Changed in: lightdm (Ubuntu Raring)
Status: New = 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/1089105
Title:
[Lenovo V480c Notebook]: System fails to resume properly from suspend
or trackpad doesn't work after resume
Status in “lightdm” package in Ubuntu:
New
Status in “linux” package in Ubuntu:
Confirmed
Status in “pm-utils” package in Ubuntu:
New
Status in “lightdm” source package in Precise:
Invalid
Status in “linux” source package in Precise:
In Progress
Status in “pm-utils” source package in Precise:
New
Status in “lightdm” source package in Quantal:
Invalid
Status in “linux” source package in Quantal:
Confirmed
Status in “pm-utils” source package in Quantal:
New
Status in “lightdm” source package in Raring:
Invalid
Status in “linux” source package in Raring:
Confirmed
Status in “pm-utils” source package in Raring:
New
Bug description:
Problem:
System does not resume from suspend properly. The issue is intermitent.
However most of the time the system will exhibit three problematic symptoms:
1.) System will fail to resume and start x altogether
2.) System will resume with applications in frozen state and unity
unresponsive to mouse-clicks.
3.) System will resume however trackpad will be disabled.
kernel tested: 3.2.0-29-generic #46-Ubuntu
Release: Ubuntu 12.04.1
Can reproduce? Yes
Steps:
1.) Close laptop lid
2.) wait approx 5 minutes
3.) open laptop lid for system to resume.
Expected result:
System is able to suspend state and applications and resume when lid is
opened in a proper and timely fashion.
Command to recreate:
fwts_test -s s3 --s3-sleep-delay=30 --s3-device-check | tee
suspend_single_times.log
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-29-generic 3.2.0-29.46
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic x86_64
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1579 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 0x9b61 irq 46'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:10ec0269,17aa500f,00100202
HDA:80862806,80860101,0010'
Controls : 26
Simple ctrls : 12
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
unknown'
Mixer name : 'ThinkPad EC (unknown)'
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 Dec 11 15:38:03 2012
HibernationDevice: RESUME=UUID=98d6d8c6-aa75-4069-9714-4f972d11aa61
InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64
(20120823.1)
MachineType: LENOVO 814TF01
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
0 inteldrmfb
1 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic
root=UUID=c1701df9-c6b6-4425-b6ec-5fede7c00ad6 ro quiet splash initcall_debug
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-29-generic N/A
linux-backports-modules-3.2.0-29-generic N/A
linux-firmware1.79
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/29/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: H5ET26WW (0.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 814TF01
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:bvrH5ET26WW(0.26):bd03/29/2012:svnLENOVO:pn814TF01:pvrLenovoV480c:rvnLENOVO:rn814TF01:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 814TF01
dmi.product.version: Lenovo V480c
[Kernel-packages] [Bug 1248270] Re: Please set CONFIG_EXT3_FS=n and CONFIG_EXT2_FS=n and CONFIG_EXT4_USE_FOR_EXT23=y
I just came across this bug report which seems to be relevant for this bug: https://lkml.org/lkml/2013/11/27/321 -- 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/1248270 Title: Please set CONFIG_EXT3_FS=n and CONFIG_EXT2_FS=n and CONFIG_EXT4_USE_FOR_EXT23=y Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Trusty: In Progress Bug description: When the old code is disabled the ext4 driver takes over and does a better job and gives a smaller kernel. Specifically the ext4 driver does a better job of resisting fragmentation since it uses delayed allocation, and supports online resize, whereas the ext2 driver does not. Config changes requested: CONFIG_EXT3_FS=y - n CONFIG_EXT2_FS=y - n CONFIG_EXT4_USE_FOR_EXT23 (NEW) - y To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248270/+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 1255700] Re: [Hewlett-Packard HP EliteBook 8740w] suspend/resume failure
Tested with 3.12.0-031200-generic #201311031935, same issue exists. No difference. Also attached cat /proc/acpi/wakeup wakeup ** Attachment added: wakeup https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255700/+attachment/3919107/+files/wakeup -- 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/1255700 Title: [Hewlett-Packard HP EliteBook 8740w] suspend/resume failure Status in “linux” package in Ubuntu: Confirmed Bug description: This crash happened as follows: System put in suspend. Quickly wake it up via sleep button on the keyboard. (within about 3 to 5 seconds) System goes on briefly (about 3 to 5 seconds) ,crashes and reboots. This crash happened with the lid closed all the time and a seperate keyboard connected. This issue also happens with the lid open, but mostly I don't have a seperate keyboard connected. In that case it will only wake up by pushing the power button. Lid opening doesn't trigger a wake, but I guess I will have to file a seperate bug report for that. If I wait much longer (say a minute or longer) before waking the system, resume works perfectly. I will try kernel 3.12.0-031200.201311031935 and see if I still can reproduce this issue. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michiel2740 F pulseaudio /dev/snd/controlC0: michiel2740 F pulseaudio Date: Wed Nov 27 22:04:05 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=9d9a11d9-b882-4b87-9926-e8da9e04d900 InstallationDate: Installed on 2013-10-27 (31 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) InterpreterPath: /usr/bin/python3.3 MachineType: Hewlett-Packard HP EliteBook 8740w MarkForUpload: True PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver pata_pcmcia ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash radeon.dpm=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 SourcePackage: linux Title: [Hewlett-Packard HP EliteBook 8740w] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/13/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CAD Ver. F.22 dmi.board.name: 1520 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 33.31 dmi.chassis.asset.tag: CNU1152Q9W dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CADVer.F.22:bd06/13/2012:svnHewlett-Packard:pnHPEliteBook8740w:pvr:rvnHewlett-Packard:rn1520:rvrKBCVersion33.31:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8740w dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255700/+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 1253734] Re: HP EliteBook 6930p: scaling_max_freq is less than highest frequencies in scaling_available_frequencies
Maybe - I noticed that just after booting scaling_max_freq was 2534000, but it dropped down soon after. I can provide the same logs as before again and you can check them to make sure that a.) I enabled ignore_ppc properly and b.) it had the expected effect. Sound ok? -- 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/1253734 Title: HP EliteBook 6930p: scaling_max_freq is less than highest frequencies in scaling_available_frequencies Status in “linux” package in Ubuntu: Incomplete Bug description: brendand@brendand-6930p:/sys/devices/system/cpu/cpu0/cpufreq$ cat scaling_max_freq 1520400 brendand@brendand-6930p:/sys/devices/system/cpu/cpu0/cpufreq$ cat scaling_available_frequencies 2534000 2533000 160 80 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1253734/+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 1107150] Re: B75 Chipset I/O Problems
Yes, as Stjin says, the provided URL doesn't contain an x86 kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1107150 Title: B75 Chipset I/O Problems Status in “linux” package in Ubuntu: Confirmed Bug description: I built a new system and installed Ubuntu 12.10. The system has the following specifications: Samsung 840 Pro 128 GB Gigabyte P75-D3 Intel i7 3770 32 GB Ram Western Digital 1 TB Black (mounted as /home) Western Digital 3 TB Green (mounted as /media/data_drive) The initial Ubuntu 12.10 install took almost 6 hours as transfer rates were very slow. After reboot everything appeared very fast. However when I did an apt-get update the download took 20 seconds and the processing of lists took 19 minutes. I had 12.10 installed on another computer which was working great (older Althon system) so I installed the drive and tested the new machine. It suffered the same performance problems. I installed Windows 7 and performed speeds tests, it reported great results. I installed 12.04 onto the 1 TB drive and it did not suffer the same performance problems. Everything ran great. I then upgraded 12.10 to 13.04 (January 27, 2013) and it too suffered from the performance issue. It appears that a change between 12.04 to 12.10 impacts AHCI based systems specifically running the Intel B75 chipset. I am not certain but I think that either the motherboard is misrepresenting something (that 12.04 ignores but it impacts 12.10) or the kernel is not detecting the system correctly. I created a couple of pastebins with data collected: 12.10 Install: http://pastebin.ubuntu.com/1561660/ 12.04 Live Disk (was checked against installed version and data is mostly the same): http://paste.ubuntu.com/1565140/ I have a thread on the ubuntu forums that may provide additional details: http://ubuntuforums.org/showthread.php?t=2104709 I also started an e-mail thread to the ubuntu-users mailing list: http://ubuntu.5.n6.nabble.com/Seeking-Help-td5010422.html I have done a lot of troubleshooting and I feel that the problem must either be the kernel or the bios misrepresenting information. In either case I am stuck without any idea of where to go next with the debuging and diagnoses path. If any additional information needs to be collected, please let me know and I will work to assist. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bakers 1729 F pulseaudio /dev/snd/controlC0: bakers 1729 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 0xf711 irq 45' Mixer name : 'Realtek ALC887-VD' Components : 'HDA:10ec0887,1458a002,00100302' Controls : 39 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583553,00100100' Controls : 18 Simple ctrls : 3 DistroRelease: Ubuntu 12.04 IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-36-generic-pae root=UUID=4f30252c-fa56-4d53-be78-117cddab55f4 ro quiet splash ProcVersionSignature: Ubuntu 3.2.0-36.57-generic-pae 3.2.35 RelatedPackageVersions: linux-restricted-modules-3.2.0-36-generic-pae N/A linux-backports-modules-3.2.0-36-generic-pae N/A linux-firmware1.79.1 RfKill: StagingDrivers: mei Tags: precise running-unity staging Uname: Linux 3.2.0-36-generic-pae i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/21/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P75-D3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias:
[Kernel-packages] [Bug 1253734] Re: HP EliteBook 6930p: scaling_max_freq is less than highest frequencies in scaling_available_frequencies
Either load the machine and check to see the scaling frequencies by hand, or run: sudo fwts cpufreq -- 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/1253734 Title: HP EliteBook 6930p: scaling_max_freq is less than highest frequencies in scaling_available_frequencies Status in “linux” package in Ubuntu: Incomplete Bug description: brendand@brendand-6930p:/sys/devices/system/cpu/cpu0/cpufreq$ cat scaling_max_freq 1520400 brendand@brendand-6930p:/sys/devices/system/cpu/cpu0/cpufreq$ cat scaling_available_frequencies 2534000 2533000 160 80 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1253734/+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 1237336] Re: linux-image-3.11.0-12-generic doesn't boot
Any update on this? My current workaround consists of booting 3.11.0-11-generic x84_64 and setting GRUB_DEFAULT=saved in /etc/default/grub. -- 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/1237336 Title: linux-image-3.11.0-12-generic doesn't boot Status in “linux” package in Ubuntu: In Progress Bug description: I made a fresh install of Ubuntu Ringtail and Upgraded to Saucy. Turns out that the machine won't boot with linux-image-3.11.0-12-generic, but *will* boot with the old ringtail kernel linux-image-3.8.0-31-generic! I created two screenshots, one shows the point where the boot process with the Saucy kernel stops (after enabling the swap), and another picture of the boot process with the ringtail kernel AFTER successfully enabling the swap. This bug report was generated on 3.8.0-31, since I can't get 3.11 to boot... ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image (not installed) ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic i686 ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guest-vLutlY 1977 F pulseaudio CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Wed Oct 9 12:40:08 2013 InstallationDate: Installed on 2013-10-08 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MachineType: Acer Extensa 5230 MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic root=UUID=5a5a0960-705c-4925-88fa-bcb05eb87c12 ro crashkernel=384M-2G:64M,2G-:128M noquiet nosplash SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-09 (0 days ago) WifiSyslog: dmi.bios.date: 02/02/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.28 dmi.board.name: Homa dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.28:bd02/02/2009:svnAcer:pnExtensa5230:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Extensa 5230 dmi.product.version: 0100 dmi.sys.vendor: Acer --- ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1518 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=765ea940-a006-4825-a979-c4ec48d81572 InstallationDate: Installed on 2013-10-08 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MachineType: Acer Extensa 5230 MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=5a5a0960-705c-4925-88fa-bcb05eb87c12 ro crashkernel=384M-2G:64M,2G-:128M noquiet nosplash ProcVersionSignature: Ubuntu 3.11.0-12.18-generic 3.11.3 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.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-12-generic i686 UpgradeStatus: Upgraded to saucy on 2013-10-09 (0 days ago) UserGroups: dmi.bios.date: 10/30/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.36 dmi.board.name: Homa dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.36:bd10/30/2009:svnAcer:pnExtensa5230:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Extensa 5230 dmi.product.version: 0100 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237336/+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 1249758] Re: 12.04 freezing after update to 3.2.0-55/56
Having put some effort into testing I am unable to make the problem recur.
I have to conclude that I had some transient hardware problem with this machine
that just happened to occur a few hours after the upgrade to 3.2.0-56 was made.
As of the next day nothing like it has happened again.
I have reseated the ram cards as a precautionary measure.
--
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/1249758
Title:
12.04 freezing after update to 3.2.0-55/56
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
After the most recent kernel upgrade to 12.04 released on or about
November 8th 2013 my machine started to freeze after a variable period
of use but only a few minutes in each case. The only thing I could
then do was to power down and reboot - file system errors were usually
found on restart. fsck was able to fix those. I have never previously
had any such problems.
Two full passes with Memcheck found no errors and disk utility reports
no disk errors - read error rate is 0, reallocated sector count is 0.
I have enabled the Grub menu and am now using 3.2.0-54 with no
problems at all.
The kernel and system logs do appear to show call stack dumps and
'BUG' messages.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-54-generic-pae 3.2.0-54.82
ProcVersionSignature: Ubuntu 3.2.0-54.82-generic-pae 3.2.50
Uname: Linux 3.2.0-54-generic-pae i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: VT1708B 8-Ch Analog [VT1708B 8-Ch
Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: tim1653 F pulseaudio
/dev/snd/pcmC0D0p: tim1653 F...m 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
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf9ffc000 irq 44'
Mixer name : 'VIA VT1708B 8-Ch'
Components : 'HDA:1106e721,104382ea,00100100'
Controls : 45
Simple ctrls : 20
Date: Sun Nov 10 11:13:07 2013
HibernationDevice: RESUME=UUID=0eec47a6-66e1-4ebf-9bbd-06f927a182f3
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386
(20120423)
MachineType: System manufacturer System Product Name
MarkForUpload: True
ProcEnviron:
LANGUAGE=en_GB:en
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-54-generic-pae
root=UUID=3750354b-b3b5-411f-ad7f-62fbedf289f4 ro quiet splash
RelatedPackageVersions:
linux-restricted-modules-3.2.0-54-generic-pae N/A
linux-backports-modules-3.2.0-54-generic-pae N/A
linux-firmware1.79.7
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/10/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0511
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5KPL-AM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0511:bd04/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-AM:rvrx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1249758/+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 1245938] Re: Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10
** Attachment added: lspci -vv https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245938/+attachment/3919133/+files/lspci-3.5.0-44-generic.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/1245938 Title: Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10 Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Quantal: Confirmed Status in “linux” source package in Raring: Confirmed Status in “linux” source package in Saucy: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: We have a server (Dell R715) with two Intel x520 NIC's. If we run Ubuntu 12.04 on it, the NIC's works flawlessly (with stock kernel driver or with Intel compiled one), but if we upgrade release to 12.10, 13.04 or 13.10, the NIC's stop working: either stock or Intel drivers fails with error: [ 226.395766] Intel(R) 10 Gigabit PCI Express Network Driver - version 3.18.7 [ 226.395770] Copyright (c) 1999-2013 Intel Corporation. [ 226.395980] ixgbe: probe of :22:00.0 failed with error -5 [ 226.396092] ixgbe: probe of :22:00.1 failed with error -5 [ 226.396203] ixgbe: probe of :23:00.0 failed with error -5 [ 226.396311] ixgbe: probe of :23:00.1 failed with error -5 I contacted Intel developers and they responded: Hey Fernando, We (ixgbe) only returns EIO (error 5) for a couple of reasons. 1) When we fail to io map (ioremap) 2) If the eeprom checksum is incorrect. 3) If the MAC address from the checksum is invalid Reasons 2 and 3 are related to the NIC's eeprom so if they worked with another system they should still be fine now. If you really wanted to verify you could try out the NIC's on a known good system again to see if the eeprom somehow got corrupted. That pretty much leaves us with ioremap returning an error. I'm not at all sure why your Ubuntu release would not like the way we are calling ioremap, but it might give you a place to start looking in Ubuntu changes. Thanks, -Don If the server boot with kernel 3.2.0-55 (from grub menu) both NIC's works fine. Please let me know how can I help! Regards Fernando To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245938/+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 1245938] Re: Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10
** Attachment added: dmesg-3.5.0-44-generic.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245938/+attachment/3919130/+files/dmesg-3.5.0-44-generic.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/1245938 Title: Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10 Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Quantal: Confirmed Status in “linux” source package in Raring: Confirmed Status in “linux” source package in Saucy: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: We have a server (Dell R715) with two Intel x520 NIC's. If we run Ubuntu 12.04 on it, the NIC's works flawlessly (with stock kernel driver or with Intel compiled one), but if we upgrade release to 12.10, 13.04 or 13.10, the NIC's stop working: either stock or Intel drivers fails with error: [ 226.395766] Intel(R) 10 Gigabit PCI Express Network Driver - version 3.18.7 [ 226.395770] Copyright (c) 1999-2013 Intel Corporation. [ 226.395980] ixgbe: probe of :22:00.0 failed with error -5 [ 226.396092] ixgbe: probe of :22:00.1 failed with error -5 [ 226.396203] ixgbe: probe of :23:00.0 failed with error -5 [ 226.396311] ixgbe: probe of :23:00.1 failed with error -5 I contacted Intel developers and they responded: Hey Fernando, We (ixgbe) only returns EIO (error 5) for a couple of reasons. 1) When we fail to io map (ioremap) 2) If the eeprom checksum is incorrect. 3) If the MAC address from the checksum is invalid Reasons 2 and 3 are related to the NIC's eeprom so if they worked with another system they should still be fine now. If you really wanted to verify you could try out the NIC's on a known good system again to see if the eeprom somehow got corrupted. That pretty much leaves us with ioremap returning an error. I'm not at all sure why your Ubuntu release would not like the way we are calling ioremap, but it might give you a place to start looking in Ubuntu changes. Thanks, -Don If the server boot with kernel 3.2.0-55 (from grub menu) both NIC's works fine. Please let me know how can I help! Regards Fernando To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245938/+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 1245938] Re: Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10
** Attachment added: dmesg-3.11-2-amd64.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245938/+attachment/3919131/+files/dmesg-3.11-2-amd64.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/1245938 Title: Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10 Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Quantal: Confirmed Status in “linux” source package in Raring: Confirmed Status in “linux” source package in Saucy: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: We have a server (Dell R715) with two Intel x520 NIC's. If we run Ubuntu 12.04 on it, the NIC's works flawlessly (with stock kernel driver or with Intel compiled one), but if we upgrade release to 12.10, 13.04 or 13.10, the NIC's stop working: either stock or Intel drivers fails with error: [ 226.395766] Intel(R) 10 Gigabit PCI Express Network Driver - version 3.18.7 [ 226.395770] Copyright (c) 1999-2013 Intel Corporation. [ 226.395980] ixgbe: probe of :22:00.0 failed with error -5 [ 226.396092] ixgbe: probe of :22:00.1 failed with error -5 [ 226.396203] ixgbe: probe of :23:00.0 failed with error -5 [ 226.396311] ixgbe: probe of :23:00.1 failed with error -5 I contacted Intel developers and they responded: Hey Fernando, We (ixgbe) only returns EIO (error 5) for a couple of reasons. 1) When we fail to io map (ioremap) 2) If the eeprom checksum is incorrect. 3) If the MAC address from the checksum is invalid Reasons 2 and 3 are related to the NIC's eeprom so if they worked with another system they should still be fine now. If you really wanted to verify you could try out the NIC's on a known good system again to see if the eeprom somehow got corrupted. That pretty much leaves us with ioremap returning an error. I'm not at all sure why your Ubuntu release would not like the way we are calling ioremap, but it might give you a place to start looking in Ubuntu changes. Thanks, -Don If the server boot with kernel 3.2.0-55 (from grub menu) both NIC's works fine. Please let me know how can I help! Regards Fernando To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245938/+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 1245938] Re: Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10
Is there a way to add multiple files on launchpad? Thomas ** Attachment added: lspci-vv-3.11-2-amd64.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245938/+attachment/3919146/+files/lspci-3.11-2-amd64.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/1245938 Title: Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10 Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Quantal: Confirmed Status in “linux” source package in Raring: Confirmed Status in “linux” source package in Saucy: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: We have a server (Dell R715) with two Intel x520 NIC's. If we run Ubuntu 12.04 on it, the NIC's works flawlessly (with stock kernel driver or with Intel compiled one), but if we upgrade release to 12.10, 13.04 or 13.10, the NIC's stop working: either stock or Intel drivers fails with error: [ 226.395766] Intel(R) 10 Gigabit PCI Express Network Driver - version 3.18.7 [ 226.395770] Copyright (c) 1999-2013 Intel Corporation. [ 226.395980] ixgbe: probe of :22:00.0 failed with error -5 [ 226.396092] ixgbe: probe of :22:00.1 failed with error -5 [ 226.396203] ixgbe: probe of :23:00.0 failed with error -5 [ 226.396311] ixgbe: probe of :23:00.1 failed with error -5 I contacted Intel developers and they responded: Hey Fernando, We (ixgbe) only returns EIO (error 5) for a couple of reasons. 1) When we fail to io map (ioremap) 2) If the eeprom checksum is incorrect. 3) If the MAC address from the checksum is invalid Reasons 2 and 3 are related to the NIC's eeprom so if they worked with another system they should still be fine now. If you really wanted to verify you could try out the NIC's on a known good system again to see if the eeprom somehow got corrupted. That pretty much leaves us with ioremap returning an error. I'm not at all sure why your Ubuntu release would not like the way we are calling ioremap, but it might give you a place to start looking in Ubuntu changes. Thanks, -Don If the server boot with kernel 3.2.0-55 (from grub menu) both NIC's works fine. Please let me know how can I help! Regards Fernando To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245938/+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 1069357] Re: [Dell Vostro V131] Hardware keys change backlight brightness in much larger increments/steps than expected
Jalon, so your hardware may be tracked, and how this is similar problem, different hardware, please file a new report via a terminal: ubuntu-bug linux -- 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/1069357 Title: [Dell Vostro V131] Hardware keys change backlight brightness in much larger increments/steps than expected Status in “linux” package in Ubuntu: Incomplete Bug description: SInce the upgrade to Ubuntu 12.10, hardware keys for regulating backlight brightness (fn+f4, fn+f5) change brightness in large increments, even though much finer control is available both through the Brightness and Lock dialog in Settings and by just setting the value in /sys/class/backlight/acpi_video0/brightness, for example: # echo 1 /sys/class/backlight/acpi_video0/brightness /sys/class/backlight/acpi_video0/brightness accepts values 0-15, the default step seems to be 3 instead of 1 as expected, and as it was in Ubuntu 12.04. Partial workaround is to disable brightness switch # echo -n 0 /sys/module/video/parameters/brightness_switch_enabled which cuts the step to 2. Moreover, adding kernel parameters acpi_osi=Linux acpi_backlight=legacy allows for even finer control in the Brightness and Lock dialog in Settings (finer than those 16 settings, including completely turning the backlight via the brightness slider) but breaks the hardware keys functionality completely. # lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 --- ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rmo1897 F pulseaudio DistroRelease: Ubuntu 12.10 HibernationDevice: RESUME=UUID=7c82e11d-4211-4789-90b6-7a20abd8aa82 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Dell Inc. Vostro V131 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=/dev/mapper/ubuntu-root ro ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 Tags: quantal running-unity Uname: Linux 3.5.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/24/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0X3GJK dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd10/24/2011:svnDellInc.:pnVostroV131:pvrNotSpecified:rvnDellInc.:rn0X3GJK:rvrA03:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro V131 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/1069357/+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 1255797] Re: Ubuntu
Actually don't know, the server just display this message (img attached) and it froze so we have to restart it in order to access the server again, this bug occurs in random days (it could pass 5 days or 2 weeks to occur again), We're using this server as email so you can imagine how critical has become this issue Thanks in advance for the help ** Attachment added: error server https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255797/+attachment/3919170/+files/error-server.jpeg -- 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/1255797 Title: Ubuntu Status in “linux” package in Ubuntu: Confirmed Bug description: Server actually have Postfix ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-25-generic-pae 2.6.32-25.44 Regression: No Reproducible: No ProcVersionSignature: Ubuntu 2.6.32-25.44-generic-pae 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic-pae i686 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: aplay: device_list:223: no soundcards found... Architecture: i386 ArecordDevices: arecord: device_list:223: no soundcards found... Date: Wed Nov 27 19:39:25 2013 Frequency: Once every few days. InstallationMedia: Ubuntu-Server 10.04 LTS Lucid Lynx - Release i386 (20100427) Lsusb: Bus 001 Device 002: ID 059b:0370 Iomega Corp. Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: IBM eserver xSeries 345 -[8670M1X]- PciMultimedia: ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-25-generic-pae root=UUID=e3fd61ac-4c1b-45c1-a86e-6b43969e860e ro quiet ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=es_MX.UTF-8 SourcePackage: linux dmi.bios.date: 06/30/2004 dmi.bios.vendor: IBM dmi.bios.version: -[GEE157CUS-1.17]- dmi.board.vendor: IBM dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: IBM dmi.modalias: dmi:bvnIBM:bvr-[GEE157CUS-1.17]-:bd06/30/2004:svnIBM:pneserverxSeries345-[8670M1X]-:pvr:rvnIBM:rn:rvr:cvnIBM:ct17:cvr: dmi.product.name: eserver xSeries 345 -[8670M1X]- dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255797/+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 1255522] Re: [Acer Aspire 5943G] Slow copy transfer rates by bad USB 2.0 detection in external usb storage devices
Angel Guzman Maeso, it would be best not to conclude too much from similar problem, different hardware, as they can have differing root causes. Hence, for your hardware, and regression testing purposes, could you please test for this in Lucid via http://old- releases.ubuntu.com/releases/lucid/ and advise to the results? ** Tags added: 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/1255522 Title: [Acer Aspire 5943G] Slow copy transfer rates by bad USB 2.0 detection in external usb storage devices Status in “linux” package in Ubuntu: Incomplete Bug description: Confirmed issue with slow transfer rates (1.5 MB/s) for 3 different external USB 2.0 hardisk (toshiba 1 TB, SAMSUNG 512 GB, Hitachi 1 TB) with 3.12.0-4-generic from trusty. It is mainly a bad detection as USB 1.0 instead of USB 2.0 in dmesg (check_highspeed is indeed bogus). Copy 20 GB takes days, instead of hours for this issue. The issue is mainly to copy or move files to a USB external storage device from the laptop or desktop. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-4-generic 3.12.0-4.10 ProcVersionSignature: Ubuntu 3.12.0-4.10-generic 3.12.1 Uname: Linux 3.12.0-4-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.12.7-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shakaran 3667 F pulseaudio /dev/snd/controlC0: shakaran 3667 F pulseaudio /dev/snd/pcmC0D0p: shakaran 3667 F...m pulseaudio CurrentDesktop: Unity Date: Wed Nov 27 13:19:24 2013 HibernationDevice: RESUME=UUID=ca085202-e6f9-4736-b311-6d9a361ec3d6 InstallationDate: Installed on 2013-02-03 (297 days ago) InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) MachineType: Acer Aspire 5943G ProcFB: 0 simple ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-4-generic root=UUID=7f18d659-ec06-4afe-b3be-13b15de376b2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.12.0-4-generic N/A linux-backports-modules-3.12.0-4-generic N/A linux-firmware1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-10-31 (27 days ago) dmi.bios.date: 10/21/2010 dmi.bios.vendor: Acer dmi.bios.version: V1.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5943G dmi.board.vendor: Acer dmi.board.version: V1.15 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.15 dmi.modalias: dmi:bvnAcer:bvrV1.15:bd10/21/2010:svnAcer:pnAspire5943G:pvrV1.15:rvnAcer:rnAspire5943G:rvrV1.15:cvnAcer:ct10:cvrV1.15: dmi.product.name: Aspire 5943G dmi.product.version: V1.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255522/+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 1034002] Re: 1002:9641 1002:9641 [Lenovo ThinkPad E525] Screen black on resume
** Summary changed:
- 1002:9641 [Lenovo ThinkPad E525] Screen black on resume
+ 1002:9641 1002:9641 [Lenovo ThinkPad E525] Screen black on resume
--
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/1034002
Title:
1002:9641 1002:9641 [Lenovo ThinkPad E525] Screen black on resume
Status in Direct Rendering Infrastructure:
Confirmed
Status in The Linux Kernel:
Fix Released
Status in “linux” package in Ubuntu:
Triaged
Bug description:
I did the kernel smoke test for the quantal kernel on precise.
I can suspend and resume however when I resume I the screen stays
black. It looks like the backlight isn't coming on, but it's
noteable that I don't see anything on my external screen either.I
can see consoles on my external monitor (over HDMI) and if I
disconnect the HDMI cable and reconnect it then I am also able to see
my Unity session on that screen.
This issue is present with both the quantal kernel and the stock 12.04
one.
My setup is a Lenovo Thinkpad E525, AMD A8-3500m.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: Generic_1 [HD-Audio Generic], device 0: CONEXANT Analog [CONEXANT
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tealeg 2861 F pulseaudio
/dev/snd/controlC0: tealeg 2861 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Generic'/'HD-Audio Generic at 0xf0b44000 irq 48'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100200'
Controls : 6
Simple ctrls : 1
Card0.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Card1.Amixer.info:
Card hw:1 'Generic_1'/'HD-Audio Generic at 0xf0b4 irq 16'
Mixer name : 'Conexant CX20590'
Components : 'HDA:14f1506e,17aa21ea,0012'
Controls : 18
Simple ctrls : 10
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
unknown'
Mixer name : 'ThinkPad EC (unknown)'
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]
DistroRelease: Ubuntu 12.04
HibernationDevice:
# RESUME=/dev/sda5
RESUME='UUID=61453936-e394-41de-8b00-5ee8f17023b3'
InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Alpha amd64
(2029)
MachineType: LENOVO 12002KG
Package: linux 3.2.0.27.29
PackageArchitecture: amd64
ProcEnviron:
LANGUAGE=en_GB:en
TERM=xterm
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-7-generic
root=UUID=c2742c1e-158f-446d-9884-d6f037d7fa8c ro quiet splash elevator=deadline
ProcVersionSignature: Ubuntu 3.5.0-7.7~precise1-generic 3.5.0
RelatedPackageVersions:
linux-restricted-modules-3.5.0-7-generic N/A
linux-backports-modules-3.5.0-7-generic N/A
linux-firmware 1.79
Tags: precise running-unity
Uname: Linux 3.5.0-7-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
WifiSyslog:
dmi.bios.date: 07/28/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8IET34WW(1.07)
dmi.board.asset.tag: Not Available
dmi.board.name: 12002KG
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:bvr8IET34WW(1.07):bd07/28/2011:svnLENOVO:pn12002KG:pvrThinkPadE525:rvnLENOVO:rn12002KG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 12002KG
dmi.product.version: ThinkPad E525
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1034002/+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 1245327] Re: [Acer Aspire 5750-9668] Laptop shuts down when the power cord is adjusted
** Description changed: What is expected to happen is when one adjusts the power cord slightly is the computer doesn't shutdown. What happens instead is looks like it received a shutdown event. Previously, when I was using an HDD, a message would pop up asking if I wanted to shutdown, which I didn't. However, now that I'm using an SSD, it just immediately starts shutting down without my being able to either - prevent the event altogether, or say no. As well, no configuration - option exists to adjust this in Power Options, etc. + prevent the event altogether, or say no. This also occurs when pressing + the power button. + + This is despite having the following set: + Applications Menu - Settings Manager - Power Manager - General - + When power button is pressed: Ask + When power button is pressed: Do nothing ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: moniker1982 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: moniker1982 F pulseaudio Date: Sun Oct 27 23:33:42 2013 HibernationDevice: RESUME=UUID=2acfb304-f013-4949-80e4-1ecdd0cb0632 InstallationDate: Installed on 2013-09-14 (43 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Alpha amd64 (20130902.1) MachineType: Acer Aspire 5750 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=60912c9c-2d5a-4031-89a4-184a797fe53f ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-3.11.0-12-generic N/A - linux-backports-modules-3.11.0-12-generic N/A - linux-firmware 1.116 + linux-restricted-modules-3.11.0-12-generic N/A + linux-backports-modules-3.11.0-12-generic N/A + linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2012 dmi.bios.vendor: Acer dmi.bios.version: V1.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JE50_HR dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.21 dmi.modalias: dmi:bvnAcer:bvrV1.21:bd08/09/2012:svnAcer:pnAspire5750:pvrV1.21:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.21: dmi.product.name: Aspire 5750 dmi.product.version: V1.21 dmi.sys.vendor: Acer ** Summary changed: - [Acer Aspire 5750-9668] Laptop shuts down when the power cord is adjusted + [Acer Aspire 5750-9668] Laptop shuts down immediately when the power cord is adjusted or power button pressed despite set otherwise ** Description changed: What is expected to happen is when one adjusts the power cord slightly is the computer doesn't shutdown. What happens instead is looks like it received a shutdown event. - Previously, when I was using an HDD, a message would pop up asking if I - wanted to shutdown, which I didn't. However, now that I'm using an SSD, - it just immediately starts shutting down without my being able to either - prevent the event altogether, or say no. This also occurs when pressing - the power button. + Previously, when I was using Raring with an HDD i386, a message would + pop up asking if I wanted to shutdown, which I didn't. However, now that + I'm using an SSD, it just immediately starts shutting down without my + being able to either prevent the event altogether, or say no. This also + occurs when pressing the power button. This is despite having the following set: Applications Menu - Settings Manager - Power Manager - General - When power button is pressed: Ask When power button is pressed: Do nothing ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: moniker1982 F pulseaudio Date: Sun Oct 27 23:33:42 2013 HibernationDevice: RESUME=UUID=2acfb304-f013-4949-80e4-1ecdd0cb0632 InstallationDate: Installed on 2013-09-14 (43 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Alpha amd64 (20130902.1) MachineType: Acer Aspire 5750 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=60912c9c-2d5a-4031-89a4-184a797fe53f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116
[Kernel-packages] [Bug 1251946] Re: Network related kernel panic on Atom 64bit system using saucy backport stack on precise
Same thing as your previous kernel, PPPoE doesn't work so my machine is essentially useless and the panicing code path doesn't get exercised. So the result is no idea. -- 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/1251946 Title: Network related kernel panic on Atom 64bit system using saucy backport stack on precise Status in “linux” package in Ubuntu: Confirmed Bug description: I can't report this through ubuntu-bug as the system is a firewall with restricted connectivity and the kernel bug prevents me from using the system for more than a couple minutes anyway. I recently deployed the saucy kernel on that precise system, after the first reboot things looked fine but just a few minutes later, the whole system hang. I reproduced this very reliably 3-4 times, then hooked up a console cable and extracted the following kernel panic: [ 124.428031] [ cut here ] [ 124.432656] Kernel BUG at 81629ce8 [verbose debug info unavailable] [ 124.439622] invalid opcode: [#1] SMP [ 124.443766] Modules linked in: authenc(F) esp6(F) xfrm6_mode_transport(F) ipcomp6(F) xfrm6_tunnel(F) tunnel6(F) xfrm4_mode_tunnel(F) xfrm6_mode_tunnel(F) v) [ 124.577657] CPU: 0 PID: 12800 Comm: samba Tainted: GF WC 3.11.0-13-generic #20~precise2-Ubuntu [ 124.586962] Hardware name: /D2500CC, BIOS CCCDT10N.86A.0039.2013.0425.1625 04/25/2013 [ 124.596268] task: 8800cd711770 ti: 8800bfde2000 task.ti: 8800bfde2000 [ 124.603752] RIP: 0010:[81629ce8] [81629ce8] pskb_expand_head+0x288/0x2d0 [ 124.612305] RSP: 0018:88012fc03688 EFLAGS: 00010202 [ 124.617621] RAX: 0003 RBX: 8800cd44d000 RCX: 0020 [ 124.624762] RDX: RSI: 0050 RDI: 06c0 [ 124.631900] RBP: 88012fc036c8 R08: 3f2c68050060 R09: 3f2c68050060 [ 124.639037] R10: bfcb2ffeff3e1602 R11: 20270ff0c0f20726 R12: 0050 [ 124.646175] R13: 0020 R14: 0001 R15: 81709280 [ 124.653317] FS: 7f81c5448740() GS:88012fc0() knlGS: [ 124.661407] CS: 0010 DS: ES: CR0: 80050033 [ 124.667158] CR2: 0330e780 CR3: bfdc9000 CR4: 07f0 [ 124.674295] Stack: [ 124.676318] e8c00640 000180400040 8801264d6d40 8800cd44d000 [ 124.683792] 880126ddc000 880126919180 0001 81709280 [ 124.691262] 88012fc036f8 816caac0 8800cd44d000 0001 [ 124.698729] Call Trace: [ 124.701187] IRQ [ 124.703121] [81709280] ? xfrm6_extract_output+0x50/0x50 [ 124.709525] [816caac0] xfrm_output_one+0x90/0x230 [ 124.715189] [816cad26] xfrm_output_resume+0xc6/0x170 [ 124.721112] [816cade3] xfrm_output2+0x13/0x20 [ 124.726429] [816cae2f] xfrm_output+0x3f/0x100 [ 124.731747] [81709299] xfrm6_output_finish+0x19/0x20 [ 124.737669] [816d5729] ip6_fragment+0x929/0xab0 [ 124.743160] [81709280] ? xfrm6_extract_output+0x50/0x50 [ 124.749344] [81708ed0] ? xfrm6_local_rxpmtu+0x70/0x70 [ 124.755356] [81708fa2] __xfrm6_output+0xd2/0x180 [ 124.760933] [817092ca] xfrm6_output+0x2a/0x70 [ 124.766250] [816d4a03] ip6_forward+0x243/0x640 [ 124.771654] [816d5a20] ? ip6_output+0xb0/0xb0 [ 124.776971] [816d5aa8] ip6_rcv_finish+0x88/0x90 [ 124.782460] [816d5a20] ? ip6_output+0xb0/0xb0 [ 124.787787] [a027783d] __ipv6_conntrack_in+0xdd/0x180 [nf_conntrack_ipv6] [ 124.795539] [a0277905] ipv6_conntrack_in+0x25/0x30 [nf_conntrack_ipv6] [ 124.803027] [816660df] nf_iterate+0x8f/0xd0 [ 124.808172] [816d5a20] ? ip6_output+0xb0/0xb0 [ 124.813488] [8166619d] nf_hook_slow+0x7d/0x150 [ 124.818891] [816d5a20] ? ip6_output+0xb0/0xb0 [ 124.824210] [816d5a20] ? ip6_output+0xb0/0xb0 [ 124.829532] [a021b3e2] nf_ct_frag6_output+0xf2/0x100 [nf_defrag_ipv6] [ 124.836932] [816d5a20] ? ip6_output+0xb0/0xb0 [ 124.842255] [a021a0a8] ipv6_defrag.part.2+0x98/0xe0 [nf_defrag_ipv6] [ 124.849577] [a021a11c] ipv6_defrag+0x2c/0x30 [nf_defrag_ipv6] [ 124.856284] [816660df] nf_iterate+0x8f/0xd0 [ 124.861429] [816d5a20] ? ip6_output+0xb0/0xb0 [ 124.866743] [8166619d] nf_hook_slow+0x7d/0x150 [ 124.872146] [816d5a20] ? ip6_output+0xb0/0xb0 [ 124.877467] [816d6213] ipv6_rcv+0x313/0x3f0 [ 124.882609] [81636cba] __netif_receive_skb_core+0x5ca/0x720 [ 124.889140] [81636e31] __netif_receive_skb+0x21/0x70 [ 124.895063] [81636ea3]
[Kernel-packages] [Bug 1024147] Re: 12.04 install cd freezes on mid-2012 13 inch MacBookPro
Andrew Merrill, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If it remains an issue, could you please make a comment to this? ** Tags added: regression-release ** Changed in: linux (Ubuntu) Status: Triaged = 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/1024147 Title: 12.04 install cd freezes on mid-2012 13 inch MacBookPro Status in “linux” package in Ubuntu: Incomplete Bug description: I have several mid-2012 13 inch MacBook Pros (MacBookPro9,2) and am trying to boot from the Ubuntu 12.04 desktop 64 bit install/live cd. All I see is a black screen with a blinking underline cursor in the top left corner. I don't get the usual boot menu. I never see ISOLinux on the screen. I have tried Ubuntu 11.04 (desktop 64bit) on the same computers, and then I do get to the boot menu. Booting then results in a kernel panic, unless the noapic boot option is specified, in which case it appears to work normally. A colleague tried Ubuntu 10.04 on the same computers and found that it worked fine. Summary: On brand new MacBook Pros, 10.04 works, 11.04 works with noapic, and 12.04 freezes immediately prior to the boot menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1024147/+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 1027368] Re: Samsung NP530U3B laptop does not suspend on lid close
Pat Robinson, could you please provide the full computer model as noted on the sticker (ex. NP530U3B-A01UK)? ** Tags added: needs-full-computer-model needs-upstream-testing regression-potential ** Description changed: - Hi, - - I've installed Ubuntu 12.04 on my wife's laptop, (a Samsung NP530U3B), - all goes well except when I close the lid it does not suspend. - - I've checked the settings and it is set to suspend on lid close, though - does not. - - I'm relatively new to Ubuntu, though have some exposure to Linux through - my job as an embedded developer. - - Things I've noticed are + I've installed Ubuntu 12.04 on my wife's laptop, (a Samsung NP530U3B), all goes well except when I close the lid it does not suspend. I've checked the settings and it is set to suspend on lid close, though does not. Things I've noticed are: 1 - Clicking suspend in the power menu works fine. - - 2 - When I cat /proc/acpi/button/lid/LID0/state it always returns open, - even when closed, (I ran a script that looped the cat then closed the - lid) - + 2 - When I cat /proc/acpi/button/lid/LID0/state it always returns open, even when closed, (I ran a script that looped the cat then closed the lid) 3 - Running the latest Ubuntu 12.10 alpha 2 does not work either. - - 4 - The latest mainstream kernel 'linux- - image-3.5.0-999-generic_3.5.0-999.201207190406_i386' does not work - either. - - 5 - One odd thing was that after installing the latest bios on the - laptop using Windows 7, then restarting into Ubuntu worked once, then it - never worked again. I tried booting in to Windows then rebooting back in - to Ubuntu to see if that is what changed something but it did not work - that time. - - Any help would be much appreciated as she has already once put it back - in her laptop bag with it still running, it got very hot! - - We both like Ubuntu over Windows, but I'm not sure it's safe to keep it - on with this bug. - - I'm wiling to try anything that will help give clues to why it is not - working - - Thanks - - Pat + 4 - The latest mainstream kernel 'linux-image-3.5.0-999-generic_3.5.0-999.201207190406_i386' does not work either. + 5 - One odd thing was that after installing the latest bios on the laptop using Windows 7, then restarting into Ubuntu worked once, then it never worked again. I tried booting in to Windows then rebooting back in to Ubuntu to see if that is what changed something but it did not work that time. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-26-generic-pae 3.2.0-26.41 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic-pae 3.2.19 Uname: Linux 3.2.0-26-generic-pae i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu11 Architecture: i386 ArecordDevices: - List of CAPTURE Hardware Devices - card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog] -Subdevices: 1/1 -Subdevice #0: subdevice #0 + List of CAPTURE Hardware Devices + card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog] + Subdevices: 1/1 + Subdevice #0: subdevice #0 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: lou2512 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: lou2512 F pulseaudio Card0.Amixer.info: - Card hw:0 'PCH'/'HDA Intel PCH at 0xf070 irq 50' -Mixer name : 'Intel CougarPoint HDMI' -Components : 'HDA:10ec0269,144dc0c7,00100202 HDA:80862805,80860101,0010' -Controls : 24 -Simple ctrls : 11 + Card hw:0 'PCH'/'HDA Intel PCH at 0xf070 irq 50' + Mixer name : 'Intel CougarPoint HDMI' + Components : 'HDA:10ec0269,144dc0c7,00100202 HDA:80862805,80860101,0010' + Controls : 24 + Simple ctrls : 11 Date: Sat Jul 21 09:37:25 2012 HibernationDevice: RESUME=UUID=3c27803e-5c58-4d5f-b649-d7357db99120 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3BI/530U4BI/530U4BH ProcEnviron: - LANGUAGE=en_GB:en - TERM=xterm - PATH=(custom, no user) - LANG=en_GB.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_GB:en + TERM=xterm + PATH=(custom, no user) + LANG=en_GB.UTF-8 + SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-26-generic-pae root=UUID=36b0eced-301e-4fa8-a3e4-2c1466de4955 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-3.2.0-26-generic-pae N/A - linux-backports-modules-3.2.0-26-generic-pae N/A - linux-firmware1.79 + linux-restricted-modules-3.2.0-26-generic-pae N/A + linux-backports-modules-3.2.0-26-generic-pae N/A + linux-firmware1.79 SourcePackage: linux StagingDrivers: mei UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2012 dmi.bios.vendor:
[Kernel-packages] [Bug 1165965] Re: External display stopped working
I can also confirm that it works more reliable with 3.12.0-031200rc6-generic (and 3.12.0-031200-generic), but it is still not perfect. I would have to ability to test it on two cases where it does not work. Both are beamers (different models, I have to check which one exactly) and both are connected over very long VGA cables. This is still an annoying bug, at least there was some progress so that it started to work again for most monitors I tried. Now it would be nice to get it working on beamers too. Can I do something to test this? I have checked the dmesg messages and there are no messages like [drm:intel_dp_i2c_aux_ch] *ERROR* too many retries, giving up what happened before kernel 3.12 (and maybe kernel 3.11.4). From xrandr output I noticed, that the DP1 connector is shown as disconnected and also no modes are shown (before kernel 3.12 there was sometimes a resolution of the external monitor detected). -- 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/1165965 Title: External display stopped working Status in “linux” package in Ubuntu: Confirmed Bug description: After upgrading to 13.04 beta, my external monitor is no longer detected/driven. This works perfectly under 12.10, and is therefore a major regression impacting common use cases. When the Display Port/VGA adapter is plugged in dmesg reports 15 instances of: [drm:intel_dp_i2c_aux_ch] *ERROR* too many retries, giving up Hardware: MacBook Air 2012 Display configuration: Apple Display Port to VGA adaptor Ubuntu version: 13.04 beta. --- ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes InstallationDate: Installed on 2012-07-24 (258 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True Package: linux (not installed) Tags: raring Uname: Linux 3.9.0-030900rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to raring on 2013-04-07 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mwp3892 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes InstallationDate: Installed on 2012-07-24 (453 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: Apple Inc. MacBookAir5,2 MarkForUpload: True NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic root=UUID=6556813f-c877-4988-bde5-24ac4ec7 ro nointremap quiet splash i915.i915_enable_rc6=1 vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-21 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/22/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA51.88Z.00EF.B00.1205221442 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-2E6FAB96566FE58C dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir5,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-2E6FAB96566FE58C dmi.modalias: dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B00.1205221442:bd05/22/2012:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C: dmi.product.name: MacBookAir5,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1165965/+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 1033410] Re: [Samsung NP530U3B-A02SE] samsung-laptop module kernel panic 3.2.0-27
** Summary changed: - samsung-laptop module kernel panic 3.2.0-27 + [Samsung NP530U3B-A02SE] samsung-laptop module kernel panic 3.2.0-27 ** Description changed: update to linux-image 3.2.0-27 results in system not booting on Samsung 5 Series laptop (NP530U3B-A02SE) there is a entry in changelog: * samsung-laptop: make the dmi check less strict - - LP: #1012284 + - LP: #1012284 on kernel 3.2.0-26 modprobe samsung-laptop says no such device, but on 3.2.0-27 it tries to load it automatically and causes instant kernel panic and system hangs - blacklisting samsung-laptop solves the issue for this system, but this should not happen by default - --- + WORKAROUND: blacklisting samsung-laptop. + --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu11 Architecture: amd64 ArecordDevices: - List of CAPTURE Hardware Devices - card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog] -Subdevices: 1/1 -Subdevice #0: subdevice #0 + List of CAPTURE Hardware Devices + card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog] + Subdevices: 1/1 + Subdevice #0: subdevice #0 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: jarkkot2067 F pulseaudio - /dev/snd/pcmC0D0p: jarkkot2067 F...m pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: jarkkot2067 F pulseaudio + /dev/snd/pcmC0D0p: jarkkot2067 F...m pulseaudio Card0.Amixer.info: - Card hw:0 'PCH'/'HDA Intel PCH at 0xf070 irq 50' -Mixer name : 'Intel CougarPoint HDMI' -Components : 'HDA:10ec0269,144dc0c7,00100202 HDA:80862805,80860101,0010' -Controls : 24 -Simple ctrls : 11 + Card hw:0 'PCH'/'HDA Intel PCH at 0xf070 irq 50' + Mixer name : 'Intel CougarPoint HDMI' + Components : 'HDA:10ec0269,144dc0c7,00100202 HDA:80862805,80860101,0010' + Controls : 24 + Simple ctrls : 11 DistroRelease: Ubuntu 12.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=5ce42c18-9f02-44fe-b82d-e1070195b1c5 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3BI/530U4BI/530U4BH Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-27-generic root=UUID=ecbc5b60-4608-4aec-b5c5-08c2c9f6aaa3 ro i915.semaphores=1 i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21 RelatedPackageVersions: - linux-restricted-modules-3.2.0-27-generic N/A - linux-backports-modules-3.2.0-27-generic N/A - linux-firmware1.79 + linux-restricted-modules-3.2.0-27-generic N/A + linux-backports-modules-3.2.0-27-generic N/A + linux-firmware1.79 StagingDrivers: mei Tags: precise running-unity staging Uname: Linux 3.2.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 03/16/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 06XK dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 530U3BI/530U4BI/530U4BH dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr06XK:bd03/16/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3BI/530U4BI/530U4BH:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn530U3BI/530U4BI/530U4BH:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3BI/530U4BI/530U4BH dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. -- 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/1033410 Title: [Samsung NP530U3B-A02SE] samsung-laptop module kernel panic 3.2.0-27 Status in “linux” package in Ubuntu: Triaged Bug description: update to linux-image 3.2.0-27 results in system not booting on Samsung 5 Series laptop (NP530U3B-A02SE) there is a entry in changelog: * samsung-laptop: make the dmi check less strict - LP: #1012284 on kernel 3.2.0-26 modprobe samsung-laptop says no such device, but on 3.2.0-27 it tries to load it automatically and causes instant kernel panic and system hangs WORKAROUND: blacklisting samsung-laptop. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu11 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1
[Kernel-packages] [Bug 888838] AcpiTables.txt
apport information ** Attachment added: AcpiTables.txt https://bugs.launchpad.net/bugs/38/+attachment/3919235/+files/AcpiTables.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/38 Title: Saitek Pedals not recognized at boot, work after unplugging and plugging back in Status in “linux” package in Ubuntu: Incomplete Bug description: This report applies to Ubuntu 11.10. The bug exists under previous versions of linux. After a boot, Saitek pedals are not recognized. dmesg contains multiple attempts to read the device: usb 5-2: device descriptor read/64, error -32 etc. If you unplug and re-plug the device, it works immediately. It can be reproduced at will by unloading and reloading the usb or usbhid driver. The current workaround is to unplug the Saitek pedals and plug them back in. For some reason the sequence of events when connecting is different from what happens when the driver loads. In that case, the device is recognized without problem. After Plugging in the device, it was working fine. [ 6918.310857] I then reset the hid driver by removing and inserting the driver. [ 7183.832022] Then the pedals device was no longer recognized, only the Yoke device, which is completely separate. So what is different between what the driver does on load, and what the driver does when a device is plugged in? dmesg: [ 6918.310857] generic-usb 0003:06A3:0763.0005: input,hidraw3: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Rudder Pedals] on usb-:00:1a.2-2/input0 [ 7183.832022] usbcore: deregistering interface driver usbhid [ 7184.052097] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0/input/input22 [ 7184.053186] generic-usb 0003:050D:0119.0001: input,hidraw0: USB HID v1.00 Keyboard [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input0 [ 7184.066403] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.1/input/input23 [ 7184.066527] generic-usb 0003:050D:0119.0002: input,hidraw1: USB HID v1.00 Mouse [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input1 [ 7184.069467] input: Saitek Saitek Pro Flight Yoke as /devices/pci:00/:00:1a.7/usb1/1-5/1-5.4/1-5.4:1.0/input/input24 [ 7184.069602] generic-usb 0003:06A3:0BAC.0003: input,hidraw2: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Yoke] on usb-:00:1a.7-5.4/input0 [ 7199.069897] generic-usb: probe of 0003:06A3:0763.0004 failed with error -110 [ 7199.070267] usbcore: registered new interface driver usbhid [ 7199.070269] usbhid: USB HID core driver ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-generic 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pac1 2284 F pulseaudio /dev/snd/controlC0: pac1 2284 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf020 irq 45' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,1458a002,00100101' Controls : 34 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xef00 irq 17' Mixer name : 'Nvidia GPU 14 HDMI/DP' Components : 'HDA:10de0014,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Thu Nov 10 19:33:05 2011 HibernationDevice: RESUME=UUID=d90f94b7-890b-47d9-a648-acd3ecb92eb0 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-S3G ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=UUID=830cb168-a478-466e-b945-b20151ef6adc ro quiet splash irqpoll vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-generic N/A linux-backports-modules-3.0.0-12-generic N/A linux-firmware1.60 RfKill: SourcePackage: linux StagingDrivers: altera_stapl UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: P35-S3G 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:
[Kernel-packages] [Bug 888838] AplayDevices.txt
apport information ** Attachment added: AplayDevices.txt https://bugs.launchpad.net/bugs/38/+attachment/3919237/+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/38 Title: Saitek Pedals not recognized at boot, work after unplugging and plugging back in Status in “linux” package in Ubuntu: Incomplete Bug description: This report applies to Ubuntu 11.10. The bug exists under previous versions of linux. After a boot, Saitek pedals are not recognized. dmesg contains multiple attempts to read the device: usb 5-2: device descriptor read/64, error -32 etc. If you unplug and re-plug the device, it works immediately. It can be reproduced at will by unloading and reloading the usb or usbhid driver. The current workaround is to unplug the Saitek pedals and plug them back in. For some reason the sequence of events when connecting is different from what happens when the driver loads. In that case, the device is recognized without problem. After Plugging in the device, it was working fine. [ 6918.310857] I then reset the hid driver by removing and inserting the driver. [ 7183.832022] Then the pedals device was no longer recognized, only the Yoke device, which is completely separate. So what is different between what the driver does on load, and what the driver does when a device is plugged in? dmesg: [ 6918.310857] generic-usb 0003:06A3:0763.0005: input,hidraw3: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Rudder Pedals] on usb-:00:1a.2-2/input0 [ 7183.832022] usbcore: deregistering interface driver usbhid [ 7184.052097] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0/input/input22 [ 7184.053186] generic-usb 0003:050D:0119.0001: input,hidraw0: USB HID v1.00 Keyboard [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input0 [ 7184.066403] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.1/input/input23 [ 7184.066527] generic-usb 0003:050D:0119.0002: input,hidraw1: USB HID v1.00 Mouse [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input1 [ 7184.069467] input: Saitek Saitek Pro Flight Yoke as /devices/pci:00/:00:1a.7/usb1/1-5/1-5.4/1-5.4:1.0/input/input24 [ 7184.069602] generic-usb 0003:06A3:0BAC.0003: input,hidraw2: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Yoke] on usb-:00:1a.7-5.4/input0 [ 7199.069897] generic-usb: probe of 0003:06A3:0763.0004 failed with error -110 [ 7199.070267] usbcore: registered new interface driver usbhid [ 7199.070269] usbhid: USB HID core driver ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-generic 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pac1 2284 F pulseaudio /dev/snd/controlC0: pac1 2284 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf020 irq 45' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,1458a002,00100101' Controls : 34 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xef00 irq 17' Mixer name : 'Nvidia GPU 14 HDMI/DP' Components : 'HDA:10de0014,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Thu Nov 10 19:33:05 2011 HibernationDevice: RESUME=UUID=d90f94b7-890b-47d9-a648-acd3ecb92eb0 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-S3G ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=UUID=830cb168-a478-466e-b945-b20151ef6adc ro quiet splash irqpoll vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-generic N/A linux-backports-modules-3.0.0-12-generic N/A linux-firmware1.60 RfKill: SourcePackage: linux StagingDrivers: altera_stapl UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: P35-S3G 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:
[Kernel-packages] [Bug 1205104] Re: 12d1:1446 Huawei E173 only detected as mass storage
Hi
Today detect in my Dell Inspiron 14R the same problem, when run lsusb
Bus 002 Device 003: ID 8087:07da Intel Corp.
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0c45:648d Microdia
Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card
Reader Controller
Bus 001 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 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 12d1:1446 Huawei Technologies Co., Ltd. E1552/E1800/E173
(HSPA modem)
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
He detect correctly this modem but only i have the mass storage!!
thanks a lot
--
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/1205104
Title:
12d1:1446 Huawei E173 only detected as mass storage
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
My Huawei E173 UMTS-Stick is only detected as a mass storage device so I
can't connect to the internet with Ubuntu 13.10.
It works great with Ubuntu 13.04
lsusb:
Bus 002 Device 006: ID 12d1:1446 Huawei Technologies Co., Ltd.
E1552/E1800/E173 (HSPA modem)
I tried to add usbserial into the /etc/modules, but that didn't
help.
Also this USB device is already included in
/lib/udev/rules.d/40-usb_modeswitch.rules
# Huawei, newer modems
ATTRS{idVendor}==12d1, ATTRS{idProduct}==1446, RUN+=usb_modeswitch
'%b/%k'
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-generic 3.10.0.5.14
ProcVersionSignature: Ubuntu 3.10.0-5.14-generic 3.10.2
Uname: Linux 3.10.0-5-generic i686
ApportVersion: 2.11-0ubuntu1
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 3761 F pulseaudio
ubuntu 5721 F pulseaudio
CasperVersion: 1.335
Date: Thu Jul 25 20:46:32 2013
LiveMediaBuild: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130725)
MachineType: Dell Inc. XPS M1330
MarkForUpload: True
ProcFB: 0 nouveaufb
ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent
file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet
splash -- maybe-ubiquity
RelatedPackageVersions:
linux-restricted-modules-3.10.0-5-generic N/A
linux-backports-modules-3.10.0-5-generic N/A
linux-firmware1.112
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1205104/+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 888838] AlsaDevices.txt
apport information ** Attachment added: AlsaDevices.txt https://bugs.launchpad.net/bugs/38/+attachment/3919236/+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/38 Title: Saitek Pedals not recognized at boot, work after unplugging and plugging back in Status in “linux” package in Ubuntu: Incomplete Bug description: This report applies to Ubuntu 11.10. The bug exists under previous versions of linux. After a boot, Saitek pedals are not recognized. dmesg contains multiple attempts to read the device: usb 5-2: device descriptor read/64, error -32 etc. If you unplug and re-plug the device, it works immediately. It can be reproduced at will by unloading and reloading the usb or usbhid driver. The current workaround is to unplug the Saitek pedals and plug them back in. For some reason the sequence of events when connecting is different from what happens when the driver loads. In that case, the device is recognized without problem. After Plugging in the device, it was working fine. [ 6918.310857] I then reset the hid driver by removing and inserting the driver. [ 7183.832022] Then the pedals device was no longer recognized, only the Yoke device, which is completely separate. So what is different between what the driver does on load, and what the driver does when a device is plugged in? dmesg: [ 6918.310857] generic-usb 0003:06A3:0763.0005: input,hidraw3: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Rudder Pedals] on usb-:00:1a.2-2/input0 [ 7183.832022] usbcore: deregistering interface driver usbhid [ 7184.052097] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0/input/input22 [ 7184.053186] generic-usb 0003:050D:0119.0001: input,hidraw0: USB HID v1.00 Keyboard [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input0 [ 7184.066403] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.1/input/input23 [ 7184.066527] generic-usb 0003:050D:0119.0002: input,hidraw1: USB HID v1.00 Mouse [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input1 [ 7184.069467] input: Saitek Saitek Pro Flight Yoke as /devices/pci:00/:00:1a.7/usb1/1-5/1-5.4/1-5.4:1.0/input/input24 [ 7184.069602] generic-usb 0003:06A3:0BAC.0003: input,hidraw2: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Yoke] on usb-:00:1a.7-5.4/input0 [ 7199.069897] generic-usb: probe of 0003:06A3:0763.0004 failed with error -110 [ 7199.070267] usbcore: registered new interface driver usbhid [ 7199.070269] usbhid: USB HID core driver ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-generic 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pac1 2284 F pulseaudio /dev/snd/controlC0: pac1 2284 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf020 irq 45' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,1458a002,00100101' Controls : 34 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xef00 irq 17' Mixer name : 'Nvidia GPU 14 HDMI/DP' Components : 'HDA:10de0014,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Thu Nov 10 19:33:05 2011 HibernationDevice: RESUME=UUID=d90f94b7-890b-47d9-a648-acd3ecb92eb0 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-S3G ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=UUID=830cb168-a478-466e-b945-b20151ef6adc ro quiet splash irqpoll vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-generic N/A linux-backports-modules-3.0.0-12-generic N/A linux-firmware1.60 RfKill: SourcePackage: linux StagingDrivers: altera_stapl UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: P35-S3G 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:
[Kernel-packages] [Bug 888838] Re: Saitek Pedals not recognized at boot, work after unplugging and plugging back in
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: olivier2677 F pulseaudio /dev/snd/controlC0: olivier2677 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfeb0 irq 16' Mixer name : 'Realtek ALC887-VD' Components : 'HDA:10ec0887,10438445,00100302' Controls : 43 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'Generic'/'HD-Audio Generic at 0xfea4 irq 78' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 6 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] DistroRelease: Ubuntu 12.04 EcryptfsInUse: Yes IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. MarkForUpload: True NonfreeKernelModules: fglrx Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-57-generic root=/dev/mapper/vg0-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.2.0-57.87-generic 3.2.52 RelatedPackageVersions: linux-restricted-modules-3.2.0-57-generic N/A linux-backports-modules-3.2.0-57-generic N/A linux-firmware1.79.9 RfKill: StagingDrivers: zram Tags: precise running-unity staging Uname: Linux 3.2.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 debian-tor dialout dip lpadmin plugdev sambashare sudo dmi.bios.date: 07/17/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0601 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 LE R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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.:bvr0601:bd07/17/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. ** Tags added: apport-collected precise running-unity -- 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/38 Title: Saitek Pedals not recognized at boot, work after unplugging and plugging back in Status in “linux” package in Ubuntu: Incomplete Bug description: This report applies to Ubuntu 11.10. The bug exists under previous versions of linux. After a boot, Saitek pedals are not recognized. dmesg contains multiple attempts to read the device: usb 5-2: device descriptor read/64, error -32 etc. If you unplug and re-plug the device, it works immediately. It can be reproduced at will by unloading and reloading the usb or usbhid driver. The current workaround is to unplug the Saitek pedals and plug them back in. For some reason the sequence of events when connecting is different from what happens when the driver loads. In that case, the device is recognized without problem. After Plugging in the device, it was working fine. [ 6918.310857] I then reset the hid driver by removing and inserting the driver. [ 7183.832022] Then the pedals device was no longer recognized, only the Yoke device, which is completely separate. So what is different between what the driver does on load, and what the driver does when a device is plugged in? dmesg: [ 6918.310857] generic-usb 0003:06A3:0763.0005: input,hidraw3: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Rudder Pedals] on usb-:00:1a.2-2/input0 [ 7183.832022] usbcore: deregistering interface driver usbhid [ 7184.052097] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0/input/input22 [ 7184.053186] generic-usb 0003:050D:0119.0001: input,hidraw0: USB HID v1.00 Keyboard [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input0 [ 7184.066403] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.1/input/input23 [ 7184.066527] generic-usb 0003:050D:0119.0002: input,hidraw1: USB HID v1.00 Mouse [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input1 [ 7184.069467] input: Saitek Saitek Pro Flight Yoke as /devices/pci:00/:00:1a.7/usb1/1-5/1-5.4/1-5.4:1.0/input/input24 [ 7184.069602] generic-usb 0003:06A3:0BAC.0003: input,hidraw2: USB HID v1.11 Joystick [Saitek Saitek Pro Flight
[Kernel-packages] [Bug 888838] Card0.Codecs.codec.0.txt
apport information ** Attachment added: Card0.Codecs.codec.0.txt https://bugs.launchpad.net/bugs/38/+attachment/3919241/+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/38 Title: Saitek Pedals not recognized at boot, work after unplugging and plugging back in Status in “linux” package in Ubuntu: Incomplete Bug description: This report applies to Ubuntu 11.10. The bug exists under previous versions of linux. After a boot, Saitek pedals are not recognized. dmesg contains multiple attempts to read the device: usb 5-2: device descriptor read/64, error -32 etc. If you unplug and re-plug the device, it works immediately. It can be reproduced at will by unloading and reloading the usb or usbhid driver. The current workaround is to unplug the Saitek pedals and plug them back in. For some reason the sequence of events when connecting is different from what happens when the driver loads. In that case, the device is recognized without problem. After Plugging in the device, it was working fine. [ 6918.310857] I then reset the hid driver by removing and inserting the driver. [ 7183.832022] Then the pedals device was no longer recognized, only the Yoke device, which is completely separate. So what is different between what the driver does on load, and what the driver does when a device is plugged in? dmesg: [ 6918.310857] generic-usb 0003:06A3:0763.0005: input,hidraw3: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Rudder Pedals] on usb-:00:1a.2-2/input0 [ 7183.832022] usbcore: deregistering interface driver usbhid [ 7184.052097] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0/input/input22 [ 7184.053186] generic-usb 0003:050D:0119.0001: input,hidraw0: USB HID v1.00 Keyboard [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input0 [ 7184.066403] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.1/input/input23 [ 7184.066527] generic-usb 0003:050D:0119.0002: input,hidraw1: USB HID v1.00 Mouse [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input1 [ 7184.069467] input: Saitek Saitek Pro Flight Yoke as /devices/pci:00/:00:1a.7/usb1/1-5/1-5.4/1-5.4:1.0/input/input24 [ 7184.069602] generic-usb 0003:06A3:0BAC.0003: input,hidraw2: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Yoke] on usb-:00:1a.7-5.4/input0 [ 7199.069897] generic-usb: probe of 0003:06A3:0763.0004 failed with error -110 [ 7199.070267] usbcore: registered new interface driver usbhid [ 7199.070269] usbhid: USB HID core driver ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-generic 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pac1 2284 F pulseaudio /dev/snd/controlC0: pac1 2284 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf020 irq 45' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,1458a002,00100101' Controls : 34 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xef00 irq 17' Mixer name : 'Nvidia GPU 14 HDMI/DP' Components : 'HDA:10de0014,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Thu Nov 10 19:33:05 2011 HibernationDevice: RESUME=UUID=d90f94b7-890b-47d9-a648-acd3ecb92eb0 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-S3G ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=UUID=830cb168-a478-466e-b945-b20151ef6adc ro quiet splash irqpoll vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-generic N/A linux-backports-modules-3.0.0-12-generic N/A linux-firmware1.60 RfKill: SourcePackage: linux StagingDrivers: altera_stapl UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: P35-S3G 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:
[Kernel-packages] [Bug 888838] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/38/+attachment/3919247/+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/38 Title: Saitek Pedals not recognized at boot, work after unplugging and plugging back in Status in “linux” package in Ubuntu: Incomplete Bug description: This report applies to Ubuntu 11.10. The bug exists under previous versions of linux. After a boot, Saitek pedals are not recognized. dmesg contains multiple attempts to read the device: usb 5-2: device descriptor read/64, error -32 etc. If you unplug and re-plug the device, it works immediately. It can be reproduced at will by unloading and reloading the usb or usbhid driver. The current workaround is to unplug the Saitek pedals and plug them back in. For some reason the sequence of events when connecting is different from what happens when the driver loads. In that case, the device is recognized without problem. After Plugging in the device, it was working fine. [ 6918.310857] I then reset the hid driver by removing and inserting the driver. [ 7183.832022] Then the pedals device was no longer recognized, only the Yoke device, which is completely separate. So what is different between what the driver does on load, and what the driver does when a device is plugged in? dmesg: [ 6918.310857] generic-usb 0003:06A3:0763.0005: input,hidraw3: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Rudder Pedals] on usb-:00:1a.2-2/input0 [ 7183.832022] usbcore: deregistering interface driver usbhid [ 7184.052097] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0/input/input22 [ 7184.053186] generic-usb 0003:050D:0119.0001: input,hidraw0: USB HID v1.00 Keyboard [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input0 [ 7184.066403] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.1/input/input23 [ 7184.066527] generic-usb 0003:050D:0119.0002: input,hidraw1: USB HID v1.00 Mouse [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input1 [ 7184.069467] input: Saitek Saitek Pro Flight Yoke as /devices/pci:00/:00:1a.7/usb1/1-5/1-5.4/1-5.4:1.0/input/input24 [ 7184.069602] generic-usb 0003:06A3:0BAC.0003: input,hidraw2: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Yoke] on usb-:00:1a.7-5.4/input0 [ 7199.069897] generic-usb: probe of 0003:06A3:0763.0004 failed with error -110 [ 7199.070267] usbcore: registered new interface driver usbhid [ 7199.070269] usbhid: USB HID core driver ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-generic 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pac1 2284 F pulseaudio /dev/snd/controlC0: pac1 2284 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf020 irq 45' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,1458a002,00100101' Controls : 34 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xef00 irq 17' Mixer name : 'Nvidia GPU 14 HDMI/DP' Components : 'HDA:10de0014,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Thu Nov 10 19:33:05 2011 HibernationDevice: RESUME=UUID=d90f94b7-890b-47d9-a648-acd3ecb92eb0 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-S3G ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=UUID=830cb168-a478-466e-b945-b20151ef6adc ro quiet splash irqpoll vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-generic N/A linux-backports-modules-3.0.0-12-generic N/A linux-firmware1.60 RfKill: SourcePackage: linux StagingDrivers: altera_stapl UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: P35-S3G 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:
[Kernel-packages] [Bug 888838] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/38/+attachment/3919244/+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/38 Title: Saitek Pedals not recognized at boot, work after unplugging and plugging back in Status in “linux” package in Ubuntu: Incomplete Bug description: This report applies to Ubuntu 11.10. The bug exists under previous versions of linux. After a boot, Saitek pedals are not recognized. dmesg contains multiple attempts to read the device: usb 5-2: device descriptor read/64, error -32 etc. If you unplug and re-plug the device, it works immediately. It can be reproduced at will by unloading and reloading the usb or usbhid driver. The current workaround is to unplug the Saitek pedals and plug them back in. For some reason the sequence of events when connecting is different from what happens when the driver loads. In that case, the device is recognized without problem. After Plugging in the device, it was working fine. [ 6918.310857] I then reset the hid driver by removing and inserting the driver. [ 7183.832022] Then the pedals device was no longer recognized, only the Yoke device, which is completely separate. So what is different between what the driver does on load, and what the driver does when a device is plugged in? dmesg: [ 6918.310857] generic-usb 0003:06A3:0763.0005: input,hidraw3: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Rudder Pedals] on usb-:00:1a.2-2/input0 [ 7183.832022] usbcore: deregistering interface driver usbhid [ 7184.052097] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0/input/input22 [ 7184.053186] generic-usb 0003:050D:0119.0001: input,hidraw0: USB HID v1.00 Keyboard [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input0 [ 7184.066403] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.1/input/input23 [ 7184.066527] generic-usb 0003:050D:0119.0002: input,hidraw1: USB HID v1.00 Mouse [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input1 [ 7184.069467] input: Saitek Saitek Pro Flight Yoke as /devices/pci:00/:00:1a.7/usb1/1-5/1-5.4/1-5.4:1.0/input/input24 [ 7184.069602] generic-usb 0003:06A3:0BAC.0003: input,hidraw2: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Yoke] on usb-:00:1a.7-5.4/input0 [ 7199.069897] generic-usb: probe of 0003:06A3:0763.0004 failed with error -110 [ 7199.070267] usbcore: registered new interface driver usbhid [ 7199.070269] usbhid: USB HID core driver ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-generic 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pac1 2284 F pulseaudio /dev/snd/controlC0: pac1 2284 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf020 irq 45' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,1458a002,00100101' Controls : 34 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xef00 irq 17' Mixer name : 'Nvidia GPU 14 HDMI/DP' Components : 'HDA:10de0014,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Thu Nov 10 19:33:05 2011 HibernationDevice: RESUME=UUID=d90f94b7-890b-47d9-a648-acd3ecb92eb0 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-S3G ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=UUID=830cb168-a478-466e-b945-b20151ef6adc ro quiet splash irqpoll vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-generic N/A linux-backports-modules-3.0.0-12-generic N/A linux-firmware1.60 RfKill: SourcePackage: linux StagingDrivers: altera_stapl UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: P35-S3G 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:
[Kernel-packages] [Bug 888838] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/38/+attachment/3919239/+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/38 Title: Saitek Pedals not recognized at boot, work after unplugging and plugging back in Status in “linux” package in Ubuntu: Incomplete Bug description: This report applies to Ubuntu 11.10. The bug exists under previous versions of linux. After a boot, Saitek pedals are not recognized. dmesg contains multiple attempts to read the device: usb 5-2: device descriptor read/64, error -32 etc. If you unplug and re-plug the device, it works immediately. It can be reproduced at will by unloading and reloading the usb or usbhid driver. The current workaround is to unplug the Saitek pedals and plug them back in. For some reason the sequence of events when connecting is different from what happens when the driver loads. In that case, the device is recognized without problem. After Plugging in the device, it was working fine. [ 6918.310857] I then reset the hid driver by removing and inserting the driver. [ 7183.832022] Then the pedals device was no longer recognized, only the Yoke device, which is completely separate. So what is different between what the driver does on load, and what the driver does when a device is plugged in? dmesg: [ 6918.310857] generic-usb 0003:06A3:0763.0005: input,hidraw3: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Rudder Pedals] on usb-:00:1a.2-2/input0 [ 7183.832022] usbcore: deregistering interface driver usbhid [ 7184.052097] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0/input/input22 [ 7184.053186] generic-usb 0003:050D:0119.0001: input,hidraw0: USB HID v1.00 Keyboard [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input0 [ 7184.066403] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.1/input/input23 [ 7184.066527] generic-usb 0003:050D:0119.0002: input,hidraw1: USB HID v1.00 Mouse [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input1 [ 7184.069467] input: Saitek Saitek Pro Flight Yoke as /devices/pci:00/:00:1a.7/usb1/1-5/1-5.4/1-5.4:1.0/input/input24 [ 7184.069602] generic-usb 0003:06A3:0BAC.0003: input,hidraw2: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Yoke] on usb-:00:1a.7-5.4/input0 [ 7199.069897] generic-usb: probe of 0003:06A3:0763.0004 failed with error -110 [ 7199.070267] usbcore: registered new interface driver usbhid [ 7199.070269] usbhid: USB HID core driver ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-generic 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pac1 2284 F pulseaudio /dev/snd/controlC0: pac1 2284 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf020 irq 45' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,1458a002,00100101' Controls : 34 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xef00 irq 17' Mixer name : 'Nvidia GPU 14 HDMI/DP' Components : 'HDA:10de0014,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Thu Nov 10 19:33:05 2011 HibernationDevice: RESUME=UUID=d90f94b7-890b-47d9-a648-acd3ecb92eb0 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-S3G ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=UUID=830cb168-a478-466e-b945-b20151ef6adc ro quiet splash irqpoll vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-generic N/A linux-backports-modules-3.0.0-12-generic N/A linux-firmware1.60 RfKill: SourcePackage: linux StagingDrivers: altera_stapl UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: P35-S3G 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:
[Kernel-packages] [Bug 888838] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/38/+attachment/3919243/+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/38 Title: Saitek Pedals not recognized at boot, work after unplugging and plugging back in Status in “linux” package in Ubuntu: Incomplete Bug description: This report applies to Ubuntu 11.10. The bug exists under previous versions of linux. After a boot, Saitek pedals are not recognized. dmesg contains multiple attempts to read the device: usb 5-2: device descriptor read/64, error -32 etc. If you unplug and re-plug the device, it works immediately. It can be reproduced at will by unloading and reloading the usb or usbhid driver. The current workaround is to unplug the Saitek pedals and plug them back in. For some reason the sequence of events when connecting is different from what happens when the driver loads. In that case, the device is recognized without problem. After Plugging in the device, it was working fine. [ 6918.310857] I then reset the hid driver by removing and inserting the driver. [ 7183.832022] Then the pedals device was no longer recognized, only the Yoke device, which is completely separate. So what is different between what the driver does on load, and what the driver does when a device is plugged in? dmesg: [ 6918.310857] generic-usb 0003:06A3:0763.0005: input,hidraw3: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Rudder Pedals] on usb-:00:1a.2-2/input0 [ 7183.832022] usbcore: deregistering interface driver usbhid [ 7184.052097] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0/input/input22 [ 7184.053186] generic-usb 0003:050D:0119.0001: input,hidraw0: USB HID v1.00 Keyboard [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input0 [ 7184.066403] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.1/input/input23 [ 7184.066527] generic-usb 0003:050D:0119.0002: input,hidraw1: USB HID v1.00 Mouse [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input1 [ 7184.069467] input: Saitek Saitek Pro Flight Yoke as /devices/pci:00/:00:1a.7/usb1/1-5/1-5.4/1-5.4:1.0/input/input24 [ 7184.069602] generic-usb 0003:06A3:0BAC.0003: input,hidraw2: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Yoke] on usb-:00:1a.7-5.4/input0 [ 7199.069897] generic-usb: probe of 0003:06A3:0763.0004 failed with error -110 [ 7199.070267] usbcore: registered new interface driver usbhid [ 7199.070269] usbhid: USB HID core driver ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-generic 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pac1 2284 F pulseaudio /dev/snd/controlC0: pac1 2284 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf020 irq 45' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,1458a002,00100101' Controls : 34 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xef00 irq 17' Mixer name : 'Nvidia GPU 14 HDMI/DP' Components : 'HDA:10de0014,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Thu Nov 10 19:33:05 2011 HibernationDevice: RESUME=UUID=d90f94b7-890b-47d9-a648-acd3ecb92eb0 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-S3G ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=UUID=830cb168-a478-466e-b945-b20151ef6adc ro quiet splash irqpoll vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-generic N/A linux-backports-modules-3.0.0-12-generic N/A linux-firmware1.60 RfKill: SourcePackage: linux StagingDrivers: altera_stapl UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: P35-S3G 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:
[Kernel-packages] [Bug 888838] Card0.Amixer.values.txt
apport information ** Attachment added: Card0.Amixer.values.txt https://bugs.launchpad.net/bugs/38/+attachment/3919240/+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/38 Title: Saitek Pedals not recognized at boot, work after unplugging and plugging back in Status in “linux” package in Ubuntu: Incomplete Bug description: This report applies to Ubuntu 11.10. The bug exists under previous versions of linux. After a boot, Saitek pedals are not recognized. dmesg contains multiple attempts to read the device: usb 5-2: device descriptor read/64, error -32 etc. If you unplug and re-plug the device, it works immediately. It can be reproduced at will by unloading and reloading the usb or usbhid driver. The current workaround is to unplug the Saitek pedals and plug them back in. For some reason the sequence of events when connecting is different from what happens when the driver loads. In that case, the device is recognized without problem. After Plugging in the device, it was working fine. [ 6918.310857] I then reset the hid driver by removing and inserting the driver. [ 7183.832022] Then the pedals device was no longer recognized, only the Yoke device, which is completely separate. So what is different between what the driver does on load, and what the driver does when a device is plugged in? dmesg: [ 6918.310857] generic-usb 0003:06A3:0763.0005: input,hidraw3: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Rudder Pedals] on usb-:00:1a.2-2/input0 [ 7183.832022] usbcore: deregistering interface driver usbhid [ 7184.052097] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0/input/input22 [ 7184.053186] generic-usb 0003:050D:0119.0001: input,hidraw0: USB HID v1.00 Keyboard [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input0 [ 7184.066403] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.1/input/input23 [ 7184.066527] generic-usb 0003:050D:0119.0002: input,hidraw1: USB HID v1.00 Mouse [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input1 [ 7184.069467] input: Saitek Saitek Pro Flight Yoke as /devices/pci:00/:00:1a.7/usb1/1-5/1-5.4/1-5.4:1.0/input/input24 [ 7184.069602] generic-usb 0003:06A3:0BAC.0003: input,hidraw2: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Yoke] on usb-:00:1a.7-5.4/input0 [ 7199.069897] generic-usb: probe of 0003:06A3:0763.0004 failed with error -110 [ 7199.070267] usbcore: registered new interface driver usbhid [ 7199.070269] usbhid: USB HID core driver ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-generic 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pac1 2284 F pulseaudio /dev/snd/controlC0: pac1 2284 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf020 irq 45' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,1458a002,00100101' Controls : 34 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xef00 irq 17' Mixer name : 'Nvidia GPU 14 HDMI/DP' Components : 'HDA:10de0014,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Thu Nov 10 19:33:05 2011 HibernationDevice: RESUME=UUID=d90f94b7-890b-47d9-a648-acd3ecb92eb0 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-S3G ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=UUID=830cb168-a478-466e-b945-b20151ef6adc ro quiet splash irqpoll vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-generic N/A linux-backports-modules-3.0.0-12-generic N/A linux-firmware1.60 RfKill: SourcePackage: linux StagingDrivers: altera_stapl UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: P35-S3G 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:
[Kernel-packages] [Bug 888838] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/38/+attachment/3919250/+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/38 Title: Saitek Pedals not recognized at boot, work after unplugging and plugging back in Status in “linux” package in Ubuntu: Incomplete Bug description: This report applies to Ubuntu 11.10. The bug exists under previous versions of linux. After a boot, Saitek pedals are not recognized. dmesg contains multiple attempts to read the device: usb 5-2: device descriptor read/64, error -32 etc. If you unplug and re-plug the device, it works immediately. It can be reproduced at will by unloading and reloading the usb or usbhid driver. The current workaround is to unplug the Saitek pedals and plug them back in. For some reason the sequence of events when connecting is different from what happens when the driver loads. In that case, the device is recognized without problem. After Plugging in the device, it was working fine. [ 6918.310857] I then reset the hid driver by removing and inserting the driver. [ 7183.832022] Then the pedals device was no longer recognized, only the Yoke device, which is completely separate. So what is different between what the driver does on load, and what the driver does when a device is plugged in? dmesg: [ 6918.310857] generic-usb 0003:06A3:0763.0005: input,hidraw3: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Rudder Pedals] on usb-:00:1a.2-2/input0 [ 7183.832022] usbcore: deregistering interface driver usbhid [ 7184.052097] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0/input/input22 [ 7184.053186] generic-usb 0003:050D:0119.0001: input,hidraw0: USB HID v1.00 Keyboard [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input0 [ 7184.066403] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.1/input/input23 [ 7184.066527] generic-usb 0003:050D:0119.0002: input,hidraw1: USB HID v1.00 Mouse [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input1 [ 7184.069467] input: Saitek Saitek Pro Flight Yoke as /devices/pci:00/:00:1a.7/usb1/1-5/1-5.4/1-5.4:1.0/input/input24 [ 7184.069602] generic-usb 0003:06A3:0BAC.0003: input,hidraw2: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Yoke] on usb-:00:1a.7-5.4/input0 [ 7199.069897] generic-usb: probe of 0003:06A3:0763.0004 failed with error -110 [ 7199.070267] usbcore: registered new interface driver usbhid [ 7199.070269] usbhid: USB HID core driver ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-generic 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pac1 2284 F pulseaudio /dev/snd/controlC0: pac1 2284 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf020 irq 45' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,1458a002,00100101' Controls : 34 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xef00 irq 17' Mixer name : 'Nvidia GPU 14 HDMI/DP' Components : 'HDA:10de0014,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Thu Nov 10 19:33:05 2011 HibernationDevice: RESUME=UUID=d90f94b7-890b-47d9-a648-acd3ecb92eb0 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-S3G ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=UUID=830cb168-a478-466e-b945-b20151ef6adc ro quiet splash irqpoll vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-generic N/A linux-backports-modules-3.0.0-12-generic N/A linux-firmware1.60 RfKill: SourcePackage: linux StagingDrivers: altera_stapl UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: P35-S3G 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:
[Kernel-packages] [Bug 888838] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/38/+attachment/3919252/+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/38 Title: Saitek Pedals not recognized at boot, work after unplugging and plugging back in Status in “linux” package in Ubuntu: Incomplete Bug description: This report applies to Ubuntu 11.10. The bug exists under previous versions of linux. After a boot, Saitek pedals are not recognized. dmesg contains multiple attempts to read the device: usb 5-2: device descriptor read/64, error -32 etc. If you unplug and re-plug the device, it works immediately. It can be reproduced at will by unloading and reloading the usb or usbhid driver. The current workaround is to unplug the Saitek pedals and plug them back in. For some reason the sequence of events when connecting is different from what happens when the driver loads. In that case, the device is recognized without problem. After Plugging in the device, it was working fine. [ 6918.310857] I then reset the hid driver by removing and inserting the driver. [ 7183.832022] Then the pedals device was no longer recognized, only the Yoke device, which is completely separate. So what is different between what the driver does on load, and what the driver does when a device is plugged in? dmesg: [ 6918.310857] generic-usb 0003:06A3:0763.0005: input,hidraw3: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Rudder Pedals] on usb-:00:1a.2-2/input0 [ 7183.832022] usbcore: deregistering interface driver usbhid [ 7184.052097] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0/input/input22 [ 7184.053186] generic-usb 0003:050D:0119.0001: input,hidraw0: USB HID v1.00 Keyboard [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input0 [ 7184.066403] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.1/input/input23 [ 7184.066527] generic-usb 0003:050D:0119.0002: input,hidraw1: USB HID v1.00 Mouse [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input1 [ 7184.069467] input: Saitek Saitek Pro Flight Yoke as /devices/pci:00/:00:1a.7/usb1/1-5/1-5.4/1-5.4:1.0/input/input24 [ 7184.069602] generic-usb 0003:06A3:0BAC.0003: input,hidraw2: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Yoke] on usb-:00:1a.7-5.4/input0 [ 7199.069897] generic-usb: probe of 0003:06A3:0763.0004 failed with error -110 [ 7199.070267] usbcore: registered new interface driver usbhid [ 7199.070269] usbhid: USB HID core driver ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-generic 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pac1 2284 F pulseaudio /dev/snd/controlC0: pac1 2284 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf020 irq 45' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,1458a002,00100101' Controls : 34 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xef00 irq 17' Mixer name : 'Nvidia GPU 14 HDMI/DP' Components : 'HDA:10de0014,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Thu Nov 10 19:33:05 2011 HibernationDevice: RESUME=UUID=d90f94b7-890b-47d9-a648-acd3ecb92eb0 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-S3G ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=UUID=830cb168-a478-466e-b945-b20151ef6adc ro quiet splash irqpoll vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-generic N/A linux-backports-modules-3.0.0-12-generic N/A linux-firmware1.60 RfKill: SourcePackage: linux StagingDrivers: altera_stapl UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: P35-S3G 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:
[Kernel-packages] [Bug 888838] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/38/+attachment/3919251/+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/38 Title: Saitek Pedals not recognized at boot, work after unplugging and plugging back in Status in “linux” package in Ubuntu: Incomplete Bug description: This report applies to Ubuntu 11.10. The bug exists under previous versions of linux. After a boot, Saitek pedals are not recognized. dmesg contains multiple attempts to read the device: usb 5-2: device descriptor read/64, error -32 etc. If you unplug and re-plug the device, it works immediately. It can be reproduced at will by unloading and reloading the usb or usbhid driver. The current workaround is to unplug the Saitek pedals and plug them back in. For some reason the sequence of events when connecting is different from what happens when the driver loads. In that case, the device is recognized without problem. After Plugging in the device, it was working fine. [ 6918.310857] I then reset the hid driver by removing and inserting the driver. [ 7183.832022] Then the pedals device was no longer recognized, only the Yoke device, which is completely separate. So what is different between what the driver does on load, and what the driver does when a device is plugged in? dmesg: [ 6918.310857] generic-usb 0003:06A3:0763.0005: input,hidraw3: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Rudder Pedals] on usb-:00:1a.2-2/input0 [ 7183.832022] usbcore: deregistering interface driver usbhid [ 7184.052097] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0/input/input22 [ 7184.053186] generic-usb 0003:050D:0119.0001: input,hidraw0: USB HID v1.00 Keyboard [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input0 [ 7184.066403] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.1/input/input23 [ 7184.066527] generic-usb 0003:050D:0119.0002: input,hidraw1: USB HID v1.00 Mouse [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input1 [ 7184.069467] input: Saitek Saitek Pro Flight Yoke as /devices/pci:00/:00:1a.7/usb1/1-5/1-5.4/1-5.4:1.0/input/input24 [ 7184.069602] generic-usb 0003:06A3:0BAC.0003: input,hidraw2: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Yoke] on usb-:00:1a.7-5.4/input0 [ 7199.069897] generic-usb: probe of 0003:06A3:0763.0004 failed with error -110 [ 7199.070267] usbcore: registered new interface driver usbhid [ 7199.070269] usbhid: USB HID core driver ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-generic 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pac1 2284 F pulseaudio /dev/snd/controlC0: pac1 2284 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf020 irq 45' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,1458a002,00100101' Controls : 34 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xef00 irq 17' Mixer name : 'Nvidia GPU 14 HDMI/DP' Components : 'HDA:10de0014,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Thu Nov 10 19:33:05 2011 HibernationDevice: RESUME=UUID=d90f94b7-890b-47d9-a648-acd3ecb92eb0 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-S3G ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=UUID=830cb168-a478-466e-b945-b20151ef6adc ro quiet splash irqpoll vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-generic N/A linux-backports-modules-3.0.0-12-generic N/A linux-firmware1.60 RfKill: SourcePackage: linux StagingDrivers: altera_stapl UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: P35-S3G 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:
[Kernel-packages] [Bug 888838] PciMultimedia.txt
apport information ** Attachment added: PciMultimedia.txt https://bugs.launchpad.net/bugs/38/+attachment/3919246/+files/PciMultimedia.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/38 Title: Saitek Pedals not recognized at boot, work after unplugging and plugging back in Status in “linux” package in Ubuntu: Incomplete Bug description: This report applies to Ubuntu 11.10. The bug exists under previous versions of linux. After a boot, Saitek pedals are not recognized. dmesg contains multiple attempts to read the device: usb 5-2: device descriptor read/64, error -32 etc. If you unplug and re-plug the device, it works immediately. It can be reproduced at will by unloading and reloading the usb or usbhid driver. The current workaround is to unplug the Saitek pedals and plug them back in. For some reason the sequence of events when connecting is different from what happens when the driver loads. In that case, the device is recognized without problem. After Plugging in the device, it was working fine. [ 6918.310857] I then reset the hid driver by removing and inserting the driver. [ 7183.832022] Then the pedals device was no longer recognized, only the Yoke device, which is completely separate. So what is different between what the driver does on load, and what the driver does when a device is plugged in? dmesg: [ 6918.310857] generic-usb 0003:06A3:0763.0005: input,hidraw3: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Rudder Pedals] on usb-:00:1a.2-2/input0 [ 7183.832022] usbcore: deregistering interface driver usbhid [ 7184.052097] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0/input/input22 [ 7184.053186] generic-usb 0003:050D:0119.0001: input,hidraw0: USB HID v1.00 Keyboard [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input0 [ 7184.066403] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.1/input/input23 [ 7184.066527] generic-usb 0003:050D:0119.0002: input,hidraw1: USB HID v1.00 Mouse [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input1 [ 7184.069467] input: Saitek Saitek Pro Flight Yoke as /devices/pci:00/:00:1a.7/usb1/1-5/1-5.4/1-5.4:1.0/input/input24 [ 7184.069602] generic-usb 0003:06A3:0BAC.0003: input,hidraw2: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Yoke] on usb-:00:1a.7-5.4/input0 [ 7199.069897] generic-usb: probe of 0003:06A3:0763.0004 failed with error -110 [ 7199.070267] usbcore: registered new interface driver usbhid [ 7199.070269] usbhid: USB HID core driver ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-generic 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pac1 2284 F pulseaudio /dev/snd/controlC0: pac1 2284 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf020 irq 45' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,1458a002,00100101' Controls : 34 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xef00 irq 17' Mixer name : 'Nvidia GPU 14 HDMI/DP' Components : 'HDA:10de0014,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Thu Nov 10 19:33:05 2011 HibernationDevice: RESUME=UUID=d90f94b7-890b-47d9-a648-acd3ecb92eb0 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-S3G ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=UUID=830cb168-a478-466e-b945-b20151ef6adc ro quiet splash irqpoll vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-generic N/A linux-backports-modules-3.0.0-12-generic N/A linux-firmware1.60 RfKill: SourcePackage: linux StagingDrivers: altera_stapl UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: P35-S3G 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:
[Kernel-packages] [Bug 888838] Card1.Codecs.codec.0.txt
apport information ** Attachment added: Card1.Codecs.codec.0.txt https://bugs.launchpad.net/bugs/38/+attachment/3919242/+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/38 Title: Saitek Pedals not recognized at boot, work after unplugging and plugging back in Status in “linux” package in Ubuntu: Incomplete Bug description: This report applies to Ubuntu 11.10. The bug exists under previous versions of linux. After a boot, Saitek pedals are not recognized. dmesg contains multiple attempts to read the device: usb 5-2: device descriptor read/64, error -32 etc. If you unplug and re-plug the device, it works immediately. It can be reproduced at will by unloading and reloading the usb or usbhid driver. The current workaround is to unplug the Saitek pedals and plug them back in. For some reason the sequence of events when connecting is different from what happens when the driver loads. In that case, the device is recognized without problem. After Plugging in the device, it was working fine. [ 6918.310857] I then reset the hid driver by removing and inserting the driver. [ 7183.832022] Then the pedals device was no longer recognized, only the Yoke device, which is completely separate. So what is different between what the driver does on load, and what the driver does when a device is plugged in? dmesg: [ 6918.310857] generic-usb 0003:06A3:0763.0005: input,hidraw3: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Rudder Pedals] on usb-:00:1a.2-2/input0 [ 7183.832022] usbcore: deregistering interface driver usbhid [ 7184.052097] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0/input/input22 [ 7184.053186] generic-usb 0003:050D:0119.0001: input,hidraw0: USB HID v1.00 Keyboard [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input0 [ 7184.066403] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.1/input/input23 [ 7184.066527] generic-usb 0003:050D:0119.0002: input,hidraw1: USB HID v1.00 Mouse [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input1 [ 7184.069467] input: Saitek Saitek Pro Flight Yoke as /devices/pci:00/:00:1a.7/usb1/1-5/1-5.4/1-5.4:1.0/input/input24 [ 7184.069602] generic-usb 0003:06A3:0BAC.0003: input,hidraw2: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Yoke] on usb-:00:1a.7-5.4/input0 [ 7199.069897] generic-usb: probe of 0003:06A3:0763.0004 failed with error -110 [ 7199.070267] usbcore: registered new interface driver usbhid [ 7199.070269] usbhid: USB HID core driver ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-generic 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pac1 2284 F pulseaudio /dev/snd/controlC0: pac1 2284 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf020 irq 45' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,1458a002,00100101' Controls : 34 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xef00 irq 17' Mixer name : 'Nvidia GPU 14 HDMI/DP' Components : 'HDA:10de0014,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Thu Nov 10 19:33:05 2011 HibernationDevice: RESUME=UUID=d90f94b7-890b-47d9-a648-acd3ecb92eb0 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-S3G ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=UUID=830cb168-a478-466e-b945-b20151ef6adc ro quiet splash irqpoll vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-generic N/A linux-backports-modules-3.0.0-12-generic N/A linux-firmware1.60 RfKill: SourcePackage: linux StagingDrivers: altera_stapl UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: P35-S3G 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:
[Kernel-packages] [Bug 888838] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/38/+attachment/3919253/+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/38 Title: Saitek Pedals not recognized at boot, work after unplugging and plugging back in Status in “linux” package in Ubuntu: Incomplete Bug description: This report applies to Ubuntu 11.10. The bug exists under previous versions of linux. After a boot, Saitek pedals are not recognized. dmesg contains multiple attempts to read the device: usb 5-2: device descriptor read/64, error -32 etc. If you unplug and re-plug the device, it works immediately. It can be reproduced at will by unloading and reloading the usb or usbhid driver. The current workaround is to unplug the Saitek pedals and plug them back in. For some reason the sequence of events when connecting is different from what happens when the driver loads. In that case, the device is recognized without problem. After Plugging in the device, it was working fine. [ 6918.310857] I then reset the hid driver by removing and inserting the driver. [ 7183.832022] Then the pedals device was no longer recognized, only the Yoke device, which is completely separate. So what is different between what the driver does on load, and what the driver does when a device is plugged in? dmesg: [ 6918.310857] generic-usb 0003:06A3:0763.0005: input,hidraw3: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Rudder Pedals] on usb-:00:1a.2-2/input0 [ 7183.832022] usbcore: deregistering interface driver usbhid [ 7184.052097] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0/input/input22 [ 7184.053186] generic-usb 0003:050D:0119.0001: input,hidraw0: USB HID v1.00 Keyboard [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input0 [ 7184.066403] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.1/input/input23 [ 7184.066527] generic-usb 0003:050D:0119.0002: input,hidraw1: USB HID v1.00 Mouse [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input1 [ 7184.069467] input: Saitek Saitek Pro Flight Yoke as /devices/pci:00/:00:1a.7/usb1/1-5/1-5.4/1-5.4:1.0/input/input24 [ 7184.069602] generic-usb 0003:06A3:0BAC.0003: input,hidraw2: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Yoke] on usb-:00:1a.7-5.4/input0 [ 7199.069897] generic-usb: probe of 0003:06A3:0763.0004 failed with error -110 [ 7199.070267] usbcore: registered new interface driver usbhid [ 7199.070269] usbhid: USB HID core driver ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-generic 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pac1 2284 F pulseaudio /dev/snd/controlC0: pac1 2284 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf020 irq 45' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,1458a002,00100101' Controls : 34 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xef00 irq 17' Mixer name : 'Nvidia GPU 14 HDMI/DP' Components : 'HDA:10de0014,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Thu Nov 10 19:33:05 2011 HibernationDevice: RESUME=UUID=d90f94b7-890b-47d9-a648-acd3ecb92eb0 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-S3G ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=UUID=830cb168-a478-466e-b945-b20151ef6adc ro quiet splash irqpoll vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-generic N/A linux-backports-modules-3.0.0-12-generic N/A linux-firmware1.60 RfKill: SourcePackage: linux StagingDrivers: altera_stapl UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: P35-S3G 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:
[Kernel-packages] [Bug 888838] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/38/+attachment/3919248/+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/38 Title: Saitek Pedals not recognized at boot, work after unplugging and plugging back in Status in “linux” package in Ubuntu: Incomplete Bug description: This report applies to Ubuntu 11.10. The bug exists under previous versions of linux. After a boot, Saitek pedals are not recognized. dmesg contains multiple attempts to read the device: usb 5-2: device descriptor read/64, error -32 etc. If you unplug and re-plug the device, it works immediately. It can be reproduced at will by unloading and reloading the usb or usbhid driver. The current workaround is to unplug the Saitek pedals and plug them back in. For some reason the sequence of events when connecting is different from what happens when the driver loads. In that case, the device is recognized without problem. After Plugging in the device, it was working fine. [ 6918.310857] I then reset the hid driver by removing and inserting the driver. [ 7183.832022] Then the pedals device was no longer recognized, only the Yoke device, which is completely separate. So what is different between what the driver does on load, and what the driver does when a device is plugged in? dmesg: [ 6918.310857] generic-usb 0003:06A3:0763.0005: input,hidraw3: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Rudder Pedals] on usb-:00:1a.2-2/input0 [ 7183.832022] usbcore: deregistering interface driver usbhid [ 7184.052097] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0/input/input22 [ 7184.053186] generic-usb 0003:050D:0119.0001: input,hidraw0: USB HID v1.00 Keyboard [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input0 [ 7184.066403] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.1/input/input23 [ 7184.066527] generic-usb 0003:050D:0119.0002: input,hidraw1: USB HID v1.00 Mouse [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input1 [ 7184.069467] input: Saitek Saitek Pro Flight Yoke as /devices/pci:00/:00:1a.7/usb1/1-5/1-5.4/1-5.4:1.0/input/input24 [ 7184.069602] generic-usb 0003:06A3:0BAC.0003: input,hidraw2: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Yoke] on usb-:00:1a.7-5.4/input0 [ 7199.069897] generic-usb: probe of 0003:06A3:0763.0004 failed with error -110 [ 7199.070267] usbcore: registered new interface driver usbhid [ 7199.070269] usbhid: USB HID core driver ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-generic 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pac1 2284 F pulseaudio /dev/snd/controlC0: pac1 2284 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf020 irq 45' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,1458a002,00100101' Controls : 34 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xef00 irq 17' Mixer name : 'Nvidia GPU 14 HDMI/DP' Components : 'HDA:10de0014,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Thu Nov 10 19:33:05 2011 HibernationDevice: RESUME=UUID=d90f94b7-890b-47d9-a648-acd3ecb92eb0 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-S3G ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=UUID=830cb168-a478-466e-b945-b20151ef6adc ro quiet splash irqpoll vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-generic N/A linux-backports-modules-3.0.0-12-generic N/A linux-firmware1.60 RfKill: SourcePackage: linux StagingDrivers: altera_stapl UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: P35-S3G 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:
[Kernel-packages] [Bug 888838] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/38/+attachment/3919245/+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/38 Title: Saitek Pedals not recognized at boot, work after unplugging and plugging back in Status in “linux” package in Ubuntu: Incomplete Bug description: This report applies to Ubuntu 11.10. The bug exists under previous versions of linux. After a boot, Saitek pedals are not recognized. dmesg contains multiple attempts to read the device: usb 5-2: device descriptor read/64, error -32 etc. If you unplug and re-plug the device, it works immediately. It can be reproduced at will by unloading and reloading the usb or usbhid driver. The current workaround is to unplug the Saitek pedals and plug them back in. For some reason the sequence of events when connecting is different from what happens when the driver loads. In that case, the device is recognized without problem. After Plugging in the device, it was working fine. [ 6918.310857] I then reset the hid driver by removing and inserting the driver. [ 7183.832022] Then the pedals device was no longer recognized, only the Yoke device, which is completely separate. So what is different between what the driver does on load, and what the driver does when a device is plugged in? dmesg: [ 6918.310857] generic-usb 0003:06A3:0763.0005: input,hidraw3: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Rudder Pedals] on usb-:00:1a.2-2/input0 [ 7183.832022] usbcore: deregistering interface driver usbhid [ 7184.052097] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0/input/input22 [ 7184.053186] generic-usb 0003:050D:0119.0001: input,hidraw0: USB HID v1.00 Keyboard [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input0 [ 7184.066403] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.1/input/input23 [ 7184.066527] generic-usb 0003:050D:0119.0002: input,hidraw1: USB HID v1.00 Mouse [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input1 [ 7184.069467] input: Saitek Saitek Pro Flight Yoke as /devices/pci:00/:00:1a.7/usb1/1-5/1-5.4/1-5.4:1.0/input/input24 [ 7184.069602] generic-usb 0003:06A3:0BAC.0003: input,hidraw2: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Yoke] on usb-:00:1a.7-5.4/input0 [ 7199.069897] generic-usb: probe of 0003:06A3:0763.0004 failed with error -110 [ 7199.070267] usbcore: registered new interface driver usbhid [ 7199.070269] usbhid: USB HID core driver ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-generic 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pac1 2284 F pulseaudio /dev/snd/controlC0: pac1 2284 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf020 irq 45' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,1458a002,00100101' Controls : 34 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xef00 irq 17' Mixer name : 'Nvidia GPU 14 HDMI/DP' Components : 'HDA:10de0014,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Thu Nov 10 19:33:05 2011 HibernationDevice: RESUME=UUID=d90f94b7-890b-47d9-a648-acd3ecb92eb0 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-S3G ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=UUID=830cb168-a478-466e-b945-b20151ef6adc ro quiet splash irqpoll vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-generic N/A linux-backports-modules-3.0.0-12-generic N/A linux-firmware1.60 RfKill: SourcePackage: linux StagingDrivers: altera_stapl UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: P35-S3G 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:
[Kernel-packages] [Bug 888838] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/38/+attachment/3919249/+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/38 Title: Saitek Pedals not recognized at boot, work after unplugging and plugging back in Status in “linux” package in Ubuntu: Incomplete Bug description: This report applies to Ubuntu 11.10. The bug exists under previous versions of linux. After a boot, Saitek pedals are not recognized. dmesg contains multiple attempts to read the device: usb 5-2: device descriptor read/64, error -32 etc. If you unplug and re-plug the device, it works immediately. It can be reproduced at will by unloading and reloading the usb or usbhid driver. The current workaround is to unplug the Saitek pedals and plug them back in. For some reason the sequence of events when connecting is different from what happens when the driver loads. In that case, the device is recognized without problem. After Plugging in the device, it was working fine. [ 6918.310857] I then reset the hid driver by removing and inserting the driver. [ 7183.832022] Then the pedals device was no longer recognized, only the Yoke device, which is completely separate. So what is different between what the driver does on load, and what the driver does when a device is plugged in? dmesg: [ 6918.310857] generic-usb 0003:06A3:0763.0005: input,hidraw3: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Rudder Pedals] on usb-:00:1a.2-2/input0 [ 7183.832022] usbcore: deregistering interface driver usbhid [ 7184.052097] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0/input/input22 [ 7184.053186] generic-usb 0003:050D:0119.0001: input,hidraw0: USB HID v1.00 Keyboard [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input0 [ 7184.066403] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.1/input/input23 [ 7184.066527] generic-usb 0003:050D:0119.0002: input,hidraw1: USB HID v1.00 Mouse [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input1 [ 7184.069467] input: Saitek Saitek Pro Flight Yoke as /devices/pci:00/:00:1a.7/usb1/1-5/1-5.4/1-5.4:1.0/input/input24 [ 7184.069602] generic-usb 0003:06A3:0BAC.0003: input,hidraw2: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Yoke] on usb-:00:1a.7-5.4/input0 [ 7199.069897] generic-usb: probe of 0003:06A3:0763.0004 failed with error -110 [ 7199.070267] usbcore: registered new interface driver usbhid [ 7199.070269] usbhid: USB HID core driver ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-generic 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pac1 2284 F pulseaudio /dev/snd/controlC0: pac1 2284 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf020 irq 45' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,1458a002,00100101' Controls : 34 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xef00 irq 17' Mixer name : 'Nvidia GPU 14 HDMI/DP' Components : 'HDA:10de0014,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Thu Nov 10 19:33:05 2011 HibernationDevice: RESUME=UUID=d90f94b7-890b-47d9-a648-acd3ecb92eb0 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-S3G ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=UUID=830cb168-a478-466e-b945-b20151ef6adc ro quiet splash irqpoll vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-generic N/A linux-backports-modules-3.0.0-12-generic N/A linux-firmware1.60 RfKill: SourcePackage: linux StagingDrivers: altera_stapl UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: P35-S3G 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:
[Kernel-packages] [Bug 888838] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/38/+attachment/3919255/+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/38 Title: Saitek Pedals not recognized at boot, work after unplugging and plugging back in Status in “linux” package in Ubuntu: Incomplete Bug description: This report applies to Ubuntu 11.10. The bug exists under previous versions of linux. After a boot, Saitek pedals are not recognized. dmesg contains multiple attempts to read the device: usb 5-2: device descriptor read/64, error -32 etc. If you unplug and re-plug the device, it works immediately. It can be reproduced at will by unloading and reloading the usb or usbhid driver. The current workaround is to unplug the Saitek pedals and plug them back in. For some reason the sequence of events when connecting is different from what happens when the driver loads. In that case, the device is recognized without problem. After Plugging in the device, it was working fine. [ 6918.310857] I then reset the hid driver by removing and inserting the driver. [ 7183.832022] Then the pedals device was no longer recognized, only the Yoke device, which is completely separate. So what is different between what the driver does on load, and what the driver does when a device is plugged in? dmesg: [ 6918.310857] generic-usb 0003:06A3:0763.0005: input,hidraw3: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Rudder Pedals] on usb-:00:1a.2-2/input0 [ 7183.832022] usbcore: deregistering interface driver usbhid [ 7184.052097] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0/input/input22 [ 7184.053186] generic-usb 0003:050D:0119.0001: input,hidraw0: USB HID v1.00 Keyboard [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input0 [ 7184.066403] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.1/input/input23 [ 7184.066527] generic-usb 0003:050D:0119.0002: input,hidraw1: USB HID v1.00 Mouse [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input1 [ 7184.069467] input: Saitek Saitek Pro Flight Yoke as /devices/pci:00/:00:1a.7/usb1/1-5/1-5.4/1-5.4:1.0/input/input24 [ 7184.069602] generic-usb 0003:06A3:0BAC.0003: input,hidraw2: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Yoke] on usb-:00:1a.7-5.4/input0 [ 7199.069897] generic-usb: probe of 0003:06A3:0763.0004 failed with error -110 [ 7199.070267] usbcore: registered new interface driver usbhid [ 7199.070269] usbhid: USB HID core driver ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-generic 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pac1 2284 F pulseaudio /dev/snd/controlC0: pac1 2284 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf020 irq 45' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,1458a002,00100101' Controls : 34 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xef00 irq 17' Mixer name : 'Nvidia GPU 14 HDMI/DP' Components : 'HDA:10de0014,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Thu Nov 10 19:33:05 2011 HibernationDevice: RESUME=UUID=d90f94b7-890b-47d9-a648-acd3ecb92eb0 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-S3G ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=UUID=830cb168-a478-466e-b945-b20151ef6adc ro quiet splash irqpoll vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-generic N/A linux-backports-modules-3.0.0-12-generic N/A linux-firmware1.60 RfKill: SourcePackage: linux StagingDrivers: altera_stapl UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: P35-S3G 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:
[Kernel-packages] [Bug 888838] UserAsoundrc.txt
apport information ** Attachment added: UserAsoundrc.txt https://bugs.launchpad.net/bugs/38/+attachment/3919254/+files/UserAsoundrc.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/38 Title: Saitek Pedals not recognized at boot, work after unplugging and plugging back in Status in “linux” package in Ubuntu: Incomplete Bug description: This report applies to Ubuntu 11.10. The bug exists under previous versions of linux. After a boot, Saitek pedals are not recognized. dmesg contains multiple attempts to read the device: usb 5-2: device descriptor read/64, error -32 etc. If you unplug and re-plug the device, it works immediately. It can be reproduced at will by unloading and reloading the usb or usbhid driver. The current workaround is to unplug the Saitek pedals and plug them back in. For some reason the sequence of events when connecting is different from what happens when the driver loads. In that case, the device is recognized without problem. After Plugging in the device, it was working fine. [ 6918.310857] I then reset the hid driver by removing and inserting the driver. [ 7183.832022] Then the pedals device was no longer recognized, only the Yoke device, which is completely separate. So what is different between what the driver does on load, and what the driver does when a device is plugged in? dmesg: [ 6918.310857] generic-usb 0003:06A3:0763.0005: input,hidraw3: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Rudder Pedals] on usb-:00:1a.2-2/input0 [ 7183.832022] usbcore: deregistering interface driver usbhid [ 7184.052097] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0/input/input22 [ 7184.053186] generic-usb 0003:050D:0119.0001: input,hidraw0: USB HID v1.00 Keyboard [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input0 [ 7184.066403] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.1/input/input23 [ 7184.066527] generic-usb 0003:050D:0119.0002: input,hidraw1: USB HID v1.00 Mouse [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input1 [ 7184.069467] input: Saitek Saitek Pro Flight Yoke as /devices/pci:00/:00:1a.7/usb1/1-5/1-5.4/1-5.4:1.0/input/input24 [ 7184.069602] generic-usb 0003:06A3:0BAC.0003: input,hidraw2: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Yoke] on usb-:00:1a.7-5.4/input0 [ 7199.069897] generic-usb: probe of 0003:06A3:0763.0004 failed with error -110 [ 7199.070267] usbcore: registered new interface driver usbhid [ 7199.070269] usbhid: USB HID core driver ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-generic 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pac1 2284 F pulseaudio /dev/snd/controlC0: pac1 2284 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf020 irq 45' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,1458a002,00100101' Controls : 34 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xef00 irq 17' Mixer name : 'Nvidia GPU 14 HDMI/DP' Components : 'HDA:10de0014,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Thu Nov 10 19:33:05 2011 HibernationDevice: RESUME=UUID=d90f94b7-890b-47d9-a648-acd3ecb92eb0 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-S3G ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=UUID=830cb168-a478-466e-b945-b20151ef6adc ro quiet splash irqpoll vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-generic N/A linux-backports-modules-3.0.0-12-generic N/A linux-firmware1.60 RfKill: SourcePackage: linux StagingDrivers: altera_stapl UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: P35-S3G 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:
[Kernel-packages] [Bug 888838] ArecordDevices.txt
apport information ** Attachment added: ArecordDevices.txt https://bugs.launchpad.net/bugs/38/+attachment/3919238/+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/38 Title: Saitek Pedals not recognized at boot, work after unplugging and plugging back in Status in “linux” package in Ubuntu: Incomplete Bug description: This report applies to Ubuntu 11.10. The bug exists under previous versions of linux. After a boot, Saitek pedals are not recognized. dmesg contains multiple attempts to read the device: usb 5-2: device descriptor read/64, error -32 etc. If you unplug and re-plug the device, it works immediately. It can be reproduced at will by unloading and reloading the usb or usbhid driver. The current workaround is to unplug the Saitek pedals and plug them back in. For some reason the sequence of events when connecting is different from what happens when the driver loads. In that case, the device is recognized without problem. After Plugging in the device, it was working fine. [ 6918.310857] I then reset the hid driver by removing and inserting the driver. [ 7183.832022] Then the pedals device was no longer recognized, only the Yoke device, which is completely separate. So what is different between what the driver does on load, and what the driver does when a device is plugged in? dmesg: [ 6918.310857] generic-usb 0003:06A3:0763.0005: input,hidraw3: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Rudder Pedals] on usb-:00:1a.2-2/input0 [ 7183.832022] usbcore: deregistering interface driver usbhid [ 7184.052097] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0/input/input22 [ 7184.053186] generic-usb 0003:050D:0119.0001: input,hidraw0: USB HID v1.00 Keyboard [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input0 [ 7184.066403] input: Belkin Components USB-PS2 Adapter as /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.1/input/input23 [ 7184.066527] generic-usb 0003:050D:0119.0002: input,hidraw1: USB HID v1.00 Mouse [Belkin Components USB-PS2 Adapter ] on usb-:00:1a.1-2/input1 [ 7184.069467] input: Saitek Saitek Pro Flight Yoke as /devices/pci:00/:00:1a.7/usb1/1-5/1-5.4/1-5.4:1.0/input/input24 [ 7184.069602] generic-usb 0003:06A3:0BAC.0003: input,hidraw2: USB HID v1.11 Joystick [Saitek Saitek Pro Flight Yoke] on usb-:00:1a.7-5.4/input0 [ 7199.069897] generic-usb: probe of 0003:06A3:0763.0004 failed with error -110 [ 7199.070267] usbcore: registered new interface driver usbhid [ 7199.070269] usbhid: USB HID core driver ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-generic 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pac1 2284 F pulseaudio /dev/snd/controlC0: pac1 2284 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf020 irq 45' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,1458a002,00100101' Controls : 34 Simple ctrls : 18 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xef00 irq 17' Mixer name : 'Nvidia GPU 14 HDMI/DP' Components : 'HDA:10de0014,10de0101,00100100' Controls : 16 Simple ctrls : 4 Date: Thu Nov 10 19:33:05 2011 HibernationDevice: RESUME=UUID=d90f94b7-890b-47d9-a648-acd3ecb92eb0 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. P35-S3G ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=UUID=830cb168-a478-466e-b945-b20151ef6adc ro quiet splash irqpoll vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-generic N/A linux-backports-modules-3.0.0-12-generic N/A linux-firmware1.60 RfKill: SourcePackage: linux StagingDrivers: altera_stapl UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: P35-S3G 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:
Re: [Kernel-packages] [Bug 1252266] Re: Corrupted low memory after resume from suspend after updating to saucy
I built the first test kernel, up to the following commit: c7dad2343f494359f6e45f62ff97055749b99670 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1252266 Can you test that kernel and report back if it has the bug or not. I will build the next test kernel based on your test results. This one suspends, but corrupts memory. So I guess that would be 'good'. -- 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/1252266 Title: Corrupted low memory after resume from suspend after updating to saucy Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading to saucy and Linux 3.11 my Gigabyte 965P-DS3 board no longer properly resumes from suspend. The desktop still works fine after resume, but the ethernet interface won't come up again. dmesg after resume warns about corrupted low memory: [40560.864036] [ cut here ] [40560.864044] WARNING: CPU: 0 PID: 24687 at /build/buildd/linux-3.11.0/arch/x86/kernel/check.c:140 check_for_bios_corruption+0x10f/0x120() [40560.864046] Memory corruption detected in low memory [40560.864048] Modules linked in: pci_stub vboxpci(OF) vboxnetadp(OF) vboxnetflt(OF) vboxdrv(OF) cuse ipt_MASQUERADE(F) iptable_nat(F) nf_nat_ipv4(F) nf_nat(F) nf_conntrack_ipv4(F) nf_defrag_ipv4(F) xt_conntrack(F) nf_conntrack(F) ipt_REJECT(F) xt_CHECKSUM(F) iptable_mangle(F) xt_tcpudp(F) bridge(F) stp(F) llc(F) ip6table_filter(F) ip6_tables(F) iptable_filter(F) ip_tables(F) ebtable_nat(F) ebtables(F) x_tables(F) joydev(F) xpad ff_memless hid_generic usbhid hid rfcomm bnep bluetooth binfmt_misc(F) kvm_intel(F) kvm(F) gpio_ich ppdev(F) ir_lirc_codec lirc_dev ir_sanyo_decoder ir_mce_kbd_decoder ir_sony_decoder ir_jvc_decoder ir_rc6_decoder ir_rc5_decoder ir_nec_decoder e4000 rtl2832 usb_storage(F) snd_usb_audio snd_usbmidi_lib uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev dvb_usb_rtl28xxu rtl2830 dvb_usb_v2 dvb_core rc_core snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep(F) snd_pcm(F) snd_page_alloc(F) snd_seq_midi(F) snd_seq_midi_event(F) microcode(F) pcspkr serio_raw(F) snd_rawmidi(F) snd_seq(F) snd_seq_device(F) snd_timer(F) snd(F) lpc_ich soundcore(F) nvidia(POF) parport_pc(F) drm mac_hid it87 hwmon_vid coretemp lp(F) parport(F) pata_acpi sky2 pata_jmicron ahci(F) libahci(F) [40560.864148] CPU: 0 PID: 24687 Comm: kworker/0:1 Tainted: PF W O 3.11.0-13-generic #20-Ubuntu [40560.864151] Hardware name: Gigabyte Technology Co., Ltd. 965P-DS3/965P-DS3, BIOS F14d 12/18/2008 [40560.864155] Workqueue: events check_corruption [40560.864158] 0009 880064be9d30 816e54ba 880064be9d78 [40560.864162] 880064be9d68 81061dbd 8801 [40560.864166] 81ea73b0 0001 8800 880064be9dc8 [40560.864171] Call Trace: [40560.864178] [816e54ba] dump_stack+0x45/0x56 [40560.864183] [81061dbd] warn_slowpath_common+0x7d/0xa0 [40560.864187] [81061e2c] warn_slowpath_fmt+0x4c/0x50 [40560.864191] [8104e5bf] check_for_bios_corruption+0x10f/0x120 [40560.864195] [8104e5de] check_corruption+0xe/0x40 [40560.864200] [8107d05c] process_one_work+0x17c/0x430 [40560.864204] [8107dcac] worker_thread+0x11c/0x3c0 [40560.864208] [8107db90] ? manage_workers.isra.24+0x2a0/0x2a0 [40560.864212] [810847b0] kthread+0xc0/0xd0 [40560.864217] [810846f0] ? kthread_create_on_node+0x120/0x120 [40560.864221] [816f51ec] ret_from_fork+0x7c/0xb0 [40560.864225] [810846f0] ? kthread_create_on_node+0x120/0x120 [40560.864228] ---[ end trace a5d0e3f4744a1e9d ]--- This did not happen with raring/Linux 3.8 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: benpicco 3071 F pulseaudio /dev/snd/controlC0: benpicco 3071 F pulseaudio Date: Mon Nov 18 14:12:08 2013 HibernationDevice: RESUME=UUID=81e8d3af-3d5b-4a61-a550-702a919449c5 InstallationDate: Installed on 2012-02-27 (629 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) IwConfig: eth0 no wireless extensions. lono wireless extensions. virbr0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. 965P-DS3 MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=5b216424-8d68-4640-9d4c-494eb0e00e9d ro quiet splash
[Kernel-packages] [Bug 1245938] Re: Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10
** Attachment added: lspci-vv_3.5.0-44.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245938/+attachment/3919268/+files/lspci-vv_3.5.0-44.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/1245938 Title: Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10 Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Quantal: Confirmed Status in “linux” source package in Raring: Confirmed Status in “linux” source package in Saucy: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: We have a server (Dell R715) with two Intel x520 NIC's. If we run Ubuntu 12.04 on it, the NIC's works flawlessly (with stock kernel driver or with Intel compiled one), but if we upgrade release to 12.10, 13.04 or 13.10, the NIC's stop working: either stock or Intel drivers fails with error: [ 226.395766] Intel(R) 10 Gigabit PCI Express Network Driver - version 3.18.7 [ 226.395770] Copyright (c) 1999-2013 Intel Corporation. [ 226.395980] ixgbe: probe of :22:00.0 failed with error -5 [ 226.396092] ixgbe: probe of :22:00.1 failed with error -5 [ 226.396203] ixgbe: probe of :23:00.0 failed with error -5 [ 226.396311] ixgbe: probe of :23:00.1 failed with error -5 I contacted Intel developers and they responded: Hey Fernando, We (ixgbe) only returns EIO (error 5) for a couple of reasons. 1) When we fail to io map (ioremap) 2) If the eeprom checksum is incorrect. 3) If the MAC address from the checksum is invalid Reasons 2 and 3 are related to the NIC's eeprom so if they worked with another system they should still be fine now. If you really wanted to verify you could try out the NIC's on a known good system again to see if the eeprom somehow got corrupted. That pretty much leaves us with ioremap returning an error. I'm not at all sure why your Ubuntu release would not like the way we are calling ioremap, but it might give you a place to start looking in Ubuntu changes. Thanks, -Don If the server boot with kernel 3.2.0-55 (from grub menu) both NIC's works fine. Please let me know how can I help! Regards Fernando To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245938/+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 1252266] Re: Corrupted low memory after resume from suspend after updating to saucy
…or rather 'bad' as you are looking for the commit that fixed 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/1252266 Title: Corrupted low memory after resume from suspend after updating to saucy Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading to saucy and Linux 3.11 my Gigabyte 965P-DS3 board no longer properly resumes from suspend. The desktop still works fine after resume, but the ethernet interface won't come up again. dmesg after resume warns about corrupted low memory: [40560.864036] [ cut here ] [40560.864044] WARNING: CPU: 0 PID: 24687 at /build/buildd/linux-3.11.0/arch/x86/kernel/check.c:140 check_for_bios_corruption+0x10f/0x120() [40560.864046] Memory corruption detected in low memory [40560.864048] Modules linked in: pci_stub vboxpci(OF) vboxnetadp(OF) vboxnetflt(OF) vboxdrv(OF) cuse ipt_MASQUERADE(F) iptable_nat(F) nf_nat_ipv4(F) nf_nat(F) nf_conntrack_ipv4(F) nf_defrag_ipv4(F) xt_conntrack(F) nf_conntrack(F) ipt_REJECT(F) xt_CHECKSUM(F) iptable_mangle(F) xt_tcpudp(F) bridge(F) stp(F) llc(F) ip6table_filter(F) ip6_tables(F) iptable_filter(F) ip_tables(F) ebtable_nat(F) ebtables(F) x_tables(F) joydev(F) xpad ff_memless hid_generic usbhid hid rfcomm bnep bluetooth binfmt_misc(F) kvm_intel(F) kvm(F) gpio_ich ppdev(F) ir_lirc_codec lirc_dev ir_sanyo_decoder ir_mce_kbd_decoder ir_sony_decoder ir_jvc_decoder ir_rc6_decoder ir_rc5_decoder ir_nec_decoder e4000 rtl2832 usb_storage(F) snd_usb_audio snd_usbmidi_lib uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev dvb_usb_rtl28xxu rtl2830 dvb_usb_v2 dvb_core rc_core snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep(F) snd_pcm(F) snd_page_alloc(F) snd_seq_midi(F) snd_seq_midi_event(F) microcode(F) pcspkr serio_raw(F) snd_rawmidi(F) snd_seq(F) snd_seq_device(F) snd_timer(F) snd(F) lpc_ich soundcore(F) nvidia(POF) parport_pc(F) drm mac_hid it87 hwmon_vid coretemp lp(F) parport(F) pata_acpi sky2 pata_jmicron ahci(F) libahci(F) [40560.864148] CPU: 0 PID: 24687 Comm: kworker/0:1 Tainted: PF W O 3.11.0-13-generic #20-Ubuntu [40560.864151] Hardware name: Gigabyte Technology Co., Ltd. 965P-DS3/965P-DS3, BIOS F14d 12/18/2008 [40560.864155] Workqueue: events check_corruption [40560.864158] 0009 880064be9d30 816e54ba 880064be9d78 [40560.864162] 880064be9d68 81061dbd 8801 [40560.864166] 81ea73b0 0001 8800 880064be9dc8 [40560.864171] Call Trace: [40560.864178] [816e54ba] dump_stack+0x45/0x56 [40560.864183] [81061dbd] warn_slowpath_common+0x7d/0xa0 [40560.864187] [81061e2c] warn_slowpath_fmt+0x4c/0x50 [40560.864191] [8104e5bf] check_for_bios_corruption+0x10f/0x120 [40560.864195] [8104e5de] check_corruption+0xe/0x40 [40560.864200] [8107d05c] process_one_work+0x17c/0x430 [40560.864204] [8107dcac] worker_thread+0x11c/0x3c0 [40560.864208] [8107db90] ? manage_workers.isra.24+0x2a0/0x2a0 [40560.864212] [810847b0] kthread+0xc0/0xd0 [40560.864217] [810846f0] ? kthread_create_on_node+0x120/0x120 [40560.864221] [816f51ec] ret_from_fork+0x7c/0xb0 [40560.864225] [810846f0] ? kthread_create_on_node+0x120/0x120 [40560.864228] ---[ end trace a5d0e3f4744a1e9d ]--- This did not happen with raring/Linux 3.8 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: benpicco 3071 F pulseaudio /dev/snd/controlC0: benpicco 3071 F pulseaudio Date: Mon Nov 18 14:12:08 2013 HibernationDevice: RESUME=UUID=81e8d3af-3d5b-4a61-a550-702a919449c5 InstallationDate: Installed on 2012-02-27 (629 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) IwConfig: eth0 no wireless extensions. lono wireless extensions. virbr0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. 965P-DS3 MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=5b216424-8d68-4640-9d4c-494eb0e00e9d ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-11-16 (2 days ago) dmi.bios.date: 12/18/2008 dmi.bios.vendor: Award Software International, Inc.
[Kernel-packages] [Bug 1245938] Re: Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10
** Attachment added: dmesg_3.5.0-44.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245938/+attachment/3919269/+files/dmesg_3.5.0-44.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/1245938 Title: Intel x520 NIC's (ixgbe) stop working in 12.10, 13.04, 13.10 Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Quantal: Confirmed Status in “linux” source package in Raring: Confirmed Status in “linux” source package in Saucy: Confirmed Status in “linux” source package in Trusty: Confirmed Bug description: We have a server (Dell R715) with two Intel x520 NIC's. If we run Ubuntu 12.04 on it, the NIC's works flawlessly (with stock kernel driver or with Intel compiled one), but if we upgrade release to 12.10, 13.04 or 13.10, the NIC's stop working: either stock or Intel drivers fails with error: [ 226.395766] Intel(R) 10 Gigabit PCI Express Network Driver - version 3.18.7 [ 226.395770] Copyright (c) 1999-2013 Intel Corporation. [ 226.395980] ixgbe: probe of :22:00.0 failed with error -5 [ 226.396092] ixgbe: probe of :22:00.1 failed with error -5 [ 226.396203] ixgbe: probe of :23:00.0 failed with error -5 [ 226.396311] ixgbe: probe of :23:00.1 failed with error -5 I contacted Intel developers and they responded: Hey Fernando, We (ixgbe) only returns EIO (error 5) for a couple of reasons. 1) When we fail to io map (ioremap) 2) If the eeprom checksum is incorrect. 3) If the MAC address from the checksum is invalid Reasons 2 and 3 are related to the NIC's eeprom so if they worked with another system they should still be fine now. If you really wanted to verify you could try out the NIC's on a known good system again to see if the eeprom somehow got corrupted. That pretty much leaves us with ioremap returning an error. I'm not at all sure why your Ubuntu release would not like the way we are calling ioremap, but it might give you a place to start looking in Ubuntu changes. Thanks, -Don If the server boot with kernel 3.2.0-55 (from grub menu) both NIC's works fine. Please let me know how can I help! Regards Fernando To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245938/+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 1027368] Re: Samsung NP530U3B laptop does not suspend on lid close
Hi The laptop model is exactly the same a the one you quoted NP530U3B- A01UK. -- 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/1027368 Title: Samsung NP530U3B laptop does not suspend on lid close Status in The Linux Kernel: Incomplete Status in “linux” package in Ubuntu: Incomplete Bug description: I've installed Ubuntu 12.04 on my wife's laptop, (a Samsung NP530U3B), all goes well except when I close the lid it does not suspend. I've checked the settings and it is set to suspend on lid close, though does not. Things I've noticed are: 1 - Clicking suspend in the power menu works fine. 2 - When I cat /proc/acpi/button/lid/LID0/state it always returns open, even when closed, (I ran a script that looped the cat then closed the lid) 3 - Running the latest Ubuntu 12.10 alpha 2 does not work either. 4 - The latest mainstream kernel 'linux-image-3.5.0-999-generic_3.5.0-999.201207190406_i386' does not work either. 5 - One odd thing was that after installing the latest bios on the laptop using Windows 7, then restarting into Ubuntu worked once, then it never worked again. I tried booting in to Windows then rebooting back in to Ubuntu to see if that is what changed something but it did not work that time. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-26-generic-pae 3.2.0-26.41 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic-pae 3.2.19 Uname: Linux 3.2.0-26-generic-pae i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu11 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lou2512 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf070 irq 50' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:10ec0269,144dc0c7,00100202 HDA:80862805,80860101,0010' Controls : 24 Simple ctrls : 11 Date: Sat Jul 21 09:37:25 2012 HibernationDevice: RESUME=UUID=3c27803e-5c58-4d5f-b649-d7357db99120 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3BI/530U4BI/530U4BH ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-26-generic-pae root=UUID=36b0eced-301e-4fa8-a3e4-2c1466de4955 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-26-generic-pae N/A linux-backports-modules-3.2.0-26-generic-pae N/A linux-firmware1.79 SourcePackage: linux StagingDrivers: mei UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 08XK dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 530U3BI/530U4BI/530U4BH dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr08XK:bd07/11/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3BI/530U4BI/530U4BH:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn530U3BI/530U4BI/530U4BH:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3BI/530U4BI/530U4BH dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1027368/+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 1250661] Re: linux-ti-omap4: 3.5.0-236.52 -proposed tracker
** Tags added: qa-testing-passed ** Changed in: kernel-sru-workflow/regression-testing Status: In Progress = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1250661 Title: linux-ti-omap4: 3.5.0-236.52 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux-ti-omap4” source package in Quantal: New Bug description: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 12. November 2013 23:09 UTC kernel-stable-master-bug:1250577 kernel-stable-Certification-testing-end:Wednesday, 13. November 2013 11:03 UTC kernel-stable-Prepare-package-end:Wednesday, 13. November 2013 19:04 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 13. November 2013 19:04 UTC kernel-stable-Promote-to-proposed-end:Thursday, 14. November 2013 12:05 UTC kernel-stable-Security-signoff-start:Thursday, 14. November 2013 13:06 UTC kernel-stable-Verification-testing-start:Thursday, 14. November 2013 13:05 UTC kernel-stable-Regression-testing-start:Thursday, 14. November 2013 13:05 UTC kernel-stable-Security-signoff-end:Tuesday, 19. November 2013 01:03 UTC kernel-stable-phase:Testing kernel-stable-phase-changed:Monday, 25. November 2013 23:03 UTC kernel-stable-Verification-testing-end:Monday, 25. November 2013 23:03 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1250661/+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 1250661] Re: linux-ti-omap4: 3.5.0-236.52 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New = Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New = Confirmed ** Description changed: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 12. November 2013 23:09 UTC kernel-stable-master-bug:1250577 kernel-stable-Certification-testing-end:Wednesday, 13. November 2013 11:03 UTC kernel-stable-Prepare-package-end:Wednesday, 13. November 2013 19:04 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 13. November 2013 19:04 UTC kernel-stable-Promote-to-proposed-end:Thursday, 14. November 2013 12:05 UTC kernel-stable-Security-signoff-start:Thursday, 14. November 2013 13:06 UTC kernel-stable-Verification-testing-start:Thursday, 14. November 2013 13:05 UTC kernel-stable-Regression-testing-start:Thursday, 14. November 2013 13:05 UTC kernel-stable-Security-signoff-end:Tuesday, 19. November 2013 01:03 UTC - kernel-stable-phase:Testing - kernel-stable-phase-changed:Monday, 25. November 2013 23:03 UTC kernel-stable-Verification-testing-end:Monday, 25. November 2013 23:03 UTC + kernel-stable-phase:CopyToUpdates + kernel-stable-phase-changed:Thursday, 28. November 2013 19:04 UTC + kernel-stable-Promote-to-updates-start:Thursday, 28. November 2013 19:04 UTC + kernel-stable-Regression-testing-end:Thursday, 28. November 2013 19:04 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ti-omap4 in Ubuntu. https://bugs.launchpad.net/bugs/1250661 Title: linux-ti-omap4: 3.5.0-236.52 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in “linux-ti-omap4” package in Ubuntu: Invalid Status in “linux-ti-omap4” source package in Quantal: New Bug description: This bug is for tracking the version to be filled upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Tuesday, 12. November 2013 23:09 UTC kernel-stable-master-bug:1250577 kernel-stable-Certification-testing-end:Wednesday, 13. November 2013 11:03 UTC kernel-stable-Prepare-package-end:Wednesday, 13. November 2013 19:04 UTC kernel-stable-Promote-to-proposed-start:Wednesday, 13. November 2013 19:04 UTC kernel-stable-Promote-to-proposed-end:Thursday, 14. November 2013 12:05 UTC kernel-stable-Security-signoff-start:Thursday, 14. November 2013 13:06 UTC kernel-stable-Verification-testing-start:Thursday, 14. November 2013 13:05 UTC kernel-stable-Regression-testing-start:Thursday, 14. November 2013 13:05 UTC kernel-stable-Security-signoff-end:Tuesday, 19. November 2013 01:03 UTC kernel-stable-Verification-testing-end:Monday, 25. November 2013 23:03 UTC kernel-stable-phase:CopyToUpdates kernel-stable-phase-changed:Thursday, 28. November 2013 19:04 UTC kernel-stable-Promote-to-updates-start:Thursday, 28. November 2013 19:04 UTC kernel-stable-Regression-testing-end:Thursday, 28. November 2013 19:04 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1250661/+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 1256080] [NEW] CVE-2013-6378
*** This bug is a security vulnerability *** Public security bug reported: The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. Break-Fix: - a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 ** Affects: linux (Ubuntu) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Low Status: New ** Affects: linux (Ubuntu Lucid) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Low Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Low Status: New ** Affects: linux (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux (Ubuntu Raring) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Raring) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Raring) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Raring) Importance: Low
[Kernel-packages] [Bug 1256080] Re: CVE-2013-6378
CVE-2013-6378 ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** 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 Saucy) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) 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 Trusty) 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 Saucy) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu
[Kernel-packages] [Bug 1256083] [NEW] CVE-2013-6380
*** This bug is a security vulnerability *** Public security bug reported: The aac_send_raw_srb function in drivers/scsi/aacraid/commctrl.c in the Linux kernel through 3.12.1 does not properly validate a certain size value, which allows local users to cause a denial of service (invalid pointer dereference) or possibly have unspecified other impact via an FSACTL_SEND_RAW_SRB ioctl call that triggers a crafted SRB command. Break-Fix: - b4789b8e6be3151a955ade74872822f30e8cd914 ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: New ** Affects: linux (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Quantal) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Quantal) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Quantal) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Quantal) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Quantal) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Quantal) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Quantal) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Quantal) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Quantal) Importance: Medium Status: New ** Affects: linux (Ubuntu Raring) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Raring) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Raring) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Raring) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Raring) Importance: Undecided Status: New ** Affects:
[Kernel-packages] [Bug 1256083] Re: CVE-2013-6380
CVE-2013-6380 ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** 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 Saucy) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) 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 Trusty) 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 Saucy) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu
[Kernel-packages] [Bug 1256088] [NEW] CVE-2013-6381
*** This bug is a security vulnerability *** Public security bug reported: Buffer overflow in the qeth_snmp_command function in drivers/s390/net/qeth_core_main.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service or possibly have unspecified other impact via an SNMP ioctl call with a length value that is incompatible with the command-buffer size. Break-Fix: - 6fb392b1a63ae36c31f62bc3fc8630b49d602b62 ** Affects: linux (Ubuntu) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Low Status: New ** Affects: linux (Ubuntu Lucid) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Low Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Low Status: New ** Affects: linux (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux (Ubuntu Raring) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Raring) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Raring) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Raring) Importance: Low Status:
[Kernel-packages] [Bug 1256088] Re: CVE-2013-6381
CVE-2013-6381 ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** 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 Saucy) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) 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 Trusty) 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 Saucy) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu
[Kernel-packages] [Bug 1256091] [NEW] CVE-2013-6382
*** This bug is a security vulnerability *** Public security bug reported: Multiple buffer underflows in the XFS implementation in the Linux kernel through 3.12.1 allow local users to cause a denial of service (memory corruption) or possibly have unspecified other impact by leveraging the CAP_SYS_ADMIN capability for a (1) XFS_IOC_ATTRLIST_BY_HANDLE or (2) XFS_IOC_ATTRLIST_BY_HANDLE_32 ioctl call with a crafted length value, related to the xfs_attrlist_by_handle function in fs/xfs/xfs_ioctl.c and the xfs_compat_attrlist_by_handle function in fs/xfs/xfs_ioctl32.c. ** Affects: linux (Ubuntu) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Low Status: New ** Affects: linux (Ubuntu Lucid) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Low Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Low Status: New ** Affects: linux (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux (Ubuntu Raring) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Raring) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Raring)
[Kernel-packages] [Bug 1256091] Re: CVE-2013-6382
CVE-2013-6382 ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** 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 Saucy) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) 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 Trusty) 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 Saucy) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu
[Kernel-packages] [Bug 1256094] [NEW] CVE-2013-6383
*** This bug is a security vulnerability *** Public security bug reported: The aac_compat_ioctl function in drivers/scsi/aacraid/linit.c in the Linux kernel before 3.11.8 does not require the CAP_SYS_RAWIO capability, which allows local users to bypass intended access restrictions via a crafted ioctl call. Break-Fix: - f856567b930dfcdbc3323261bf77240ccdde01f5 ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Medium Status: New ** Affects: linux (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Medium Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Quantal) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Quantal) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Quantal) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Quantal) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Quantal) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Quantal) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Quantal) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Quantal) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Quantal) Importance: Medium Status: New ** Affects: linux (Ubuntu Raring) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Raring) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Raring) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Raring) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Raring) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Raring) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu
[Kernel-packages] [Bug 1256094] Re: CVE-2013-6383
CVE-2013-6383 ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** 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 Saucy) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) 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 Trusty) 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 Saucy) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu
[Kernel-packages] [Bug 1256095] [NEW] CVE-2013-6392
*** This bug is a security vulnerability *** Public security bug reported: information disclosure ** Affects: linux (Ubuntu) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu) Importance: Low Status: New ** Affects: linux (Ubuntu Lucid) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Lucid) Importance: Low Status: New ** Affects: linux-fsl-imx51 (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Lucid) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Lucid) Importance: Low Status: Invalid ** Affects: linux (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Low Status: New ** Affects: linux (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Quantal) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Quantal) Importance: Low Status: New ** Affects: linux (Ubuntu Raring) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Raring) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Raring) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Raring) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Raring) Importance:
[Kernel-packages] [Bug 1256095] Re: CVE-2013-6392
CVE-2013-6392 ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** 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 Saucy) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) 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 Trusty) 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 Saucy) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Lucid) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu Quantal) Status: New = Invalid ** Changed in: linux-lts-quantal (Ubuntu
[Kernel-packages] [Bug 1255322] Re: linux: 3.12.0-4.12 -proposed tracker
** Changed in: kernel-development-workflow/promote-to-release Status: New = Fix Released ** Changed in: kernel-development-workflow/package-testing Status: Confirmed = Fix Released ** Changed in: kernel-development-workflow Status: In Progress = Fix Released -- 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/1255322 Title: linux: 3.12.0-4.12 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow package-testing series: Fix Released Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Invalid Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Released Bug description: This bug is for tracking the 3.12.0-4.12 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-Prepare-package-start:Tuesday, 26. November 2013 21:46 UTC kernel-Package-testing-start:Thursday, 28. November 2013 00:00 UTC kernel-phase:Testing kernel-phase-changed:Thursday, 28. November 2013 00:00 UTC kernel-Prepare-package-end:Thursday, 28. November 2013 00:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1255322/+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 1254261] Re: xhci regression: usb 3.0 hdd disconnects immediately
As a last resort I upgraded the bios/uefi of the mainboard (B85M-G BIOS 0410 - B85M-G BIOS 0703) and now it works. Funny though, that 3.2 managed to circumvent whatever the bios messed up. Anyway, sorry for the noise. ** Changed in: linux (Ubuntu) Status: Triaged = 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/1254261 Title: xhci regression: usb 3.0 hdd disconnects immediately Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Invalid Bug description: On a fresh saucey installation (kernel 3.11), I can not use my external usb 3.0 hdd on usb 3.0 ports, it only works on usb 2 ports. kernel log shows, that it disconnects immediately after it is plugged in. Then it continues to connect and disconnect indefinitely (q.v. attached dmesg log): [ 2623.116141] usb 3-5: new SuperSpeed USB device number 2 using xhci_hcd [ 2623.132574] usb 3-5: New USB device found, idVendor=1058, idProduct=0740 [ 2623.132582] usb 3-5: New USB device strings: Mfr=1, Product=2, SerialNumber=5 [ 2623.132587] usb 3-5: Product: My Passport 0740 [ 2623.132591] usb 3-5: Manufacturer: Western Digital [ 2623.132595] usb 3-5: SerialNumber: 575847314139315836343531 [ 2623.133533] usb-storage 3-5:1.0: USB Mass Storage device detected [ 2623.133758] scsi7 : usb-storage 3-5:1.0 [ 2624.299678] usb 3-5: USB disconnect, device number 2 [ 2645.281554] scsi 7:0:0:0: Device offlined - not ready after error recovery [ 2645.281727] usb 3-5: Set SEL for device-initiated U1 failed. [ 2645.281730] usb 3-5: Set SEL for device-initiated U2 failed. [ 2645.521559] usb 3-5: new SuperSpeed USB device number 3 using xhci_hcd ... The same hw combination works with kernel 3.2 in precise, but not with 3.8 (see attachments below). I even tried 3.12 coming with trusty, but got the same log messages as with 3.11. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kiran 1633 F pulseaudio /dev/snd/controlC0: kiran 1633 F pulseaudio CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=5ea8b83e-6f6f-4e44-98f6-45ade2c2d6c3 InstallationDate: Installed on 2013-11-16 (7 days ago) InstallationMedia: Ubuntu-Server 13.10 Saucy Salamander - Release amd64 (20131016) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: ASUS All Series MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic.efi.signed root=UUID=4fee8160-326f-4688-a0d9-22e158e70f45 ro ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 RfKill: Error: [Errno 2] No such file or directory Tags: saucy Uname: Linux 3.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 06/28/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0410 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-G dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0410:bd06/28/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-G:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1254261/+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 1205104] Re: 12d1:1446 Huawei E173 only detected as mass storage
Alejandro Arcos, so your hardware may be tracked, could you please file a new
report via a terminal:
ubuntu-bug linux
--
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/1205104
Title:
12d1:1446 Huawei E173 only detected as mass storage
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
My Huawei E173 UMTS-Stick is only detected as a mass storage device so I
can't connect to the internet with Ubuntu 13.10.
It works great with Ubuntu 13.04
lsusb:
Bus 002 Device 006: ID 12d1:1446 Huawei Technologies Co., Ltd.
E1552/E1800/E173 (HSPA modem)
I tried to add usbserial into the /etc/modules, but that didn't
help.
Also this USB device is already included in
/lib/udev/rules.d/40-usb_modeswitch.rules
# Huawei, newer modems
ATTRS{idVendor}==12d1, ATTRS{idProduct}==1446, RUN+=usb_modeswitch
'%b/%k'
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-generic 3.10.0.5.14
ProcVersionSignature: Ubuntu 3.10.0-5.14-generic 3.10.2
Uname: Linux 3.10.0-5-generic i686
ApportVersion: 2.11-0ubuntu1
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 3761 F pulseaudio
ubuntu 5721 F pulseaudio
CasperVersion: 1.335
Date: Thu Jul 25 20:46:32 2013
LiveMediaBuild: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130725)
MachineType: Dell Inc. XPS M1330
MarkForUpload: True
ProcFB: 0 nouveaufb
ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent
file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet
splash -- maybe-ubiquity
RelatedPackageVersions:
linux-restricted-modules-3.10.0-5-generic N/A
linux-backports-modules-3.10.0-5-generic N/A
linux-firmware1.112
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1205104/+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 1165965] Re: 8086:0166 [MacBookAir5, 2] External display stopped working
Hans-Peter Schadler, in order to track your hardware, could you please file a new report via a terminal: ubuntu-bug linux ** Summary changed: - External display stopped working + 8086:0166 [MacBookAir5,2] External display stopped working -- 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/1165965 Title: 8086:0166 [MacBookAir5,2] External display stopped working Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading to 13.04 beta, my external monitor is no longer detected/driven. This works perfectly under 12.10, and is therefore a major regression impacting common use cases. When the Display Port/VGA adapter is plugged in dmesg reports 15 instances of: [drm:intel_dp_i2c_aux_ch] *ERROR* too many retries, giving up Hardware: MacBook Air 2012 Display configuration: Apple Display Port to VGA adaptor Ubuntu version: 13.04 beta. --- ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes InstallationDate: Installed on 2012-07-24 (258 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True Package: linux (not installed) Tags: raring Uname: Linux 3.9.0-030900rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to raring on 2013-04-07 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mwp3892 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes InstallationDate: Installed on 2012-07-24 (453 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: Apple Inc. MacBookAir5,2 MarkForUpload: True NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic root=UUID=6556813f-c877-4988-bde5-24ac4ec7 ro nointremap quiet splash i915.i915_enable_rc6=1 vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-21 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/22/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA51.88Z.00EF.B00.1205221442 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-2E6FAB96566FE58C dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir5,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-2E6FAB96566FE58C dmi.modalias: dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B00.1205221442:bd05/22/2012:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C: dmi.product.name: MacBookAir5,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1165965/+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 1165965] Re: 8086:0166 [MacBookAir5, 2] External display stopped working
Michael Paddon, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please just make a comment to this. ** 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/1165965 Title: 8086:0166 [MacBookAir5,2] External display stopped working Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading to 13.04 beta, my external monitor is no longer detected/driven. This works perfectly under 12.10, and is therefore a major regression impacting common use cases. When the Display Port/VGA adapter is plugged in dmesg reports 15 instances of: [drm:intel_dp_i2c_aux_ch] *ERROR* too many retries, giving up Hardware: MacBook Air 2012 Display configuration: Apple Display Port to VGA adaptor Ubuntu version: 13.04 beta. --- ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes InstallationDate: Installed on 2012-07-24 (258 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True Package: linux (not installed) Tags: raring Uname: Linux 3.9.0-030900rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to raring on 2013-04-07 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mwp3892 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes InstallationDate: Installed on 2012-07-24 (453 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: Apple Inc. MacBookAir5,2 MarkForUpload: True NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic root=UUID=6556813f-c877-4988-bde5-24ac4ec7 ro nointremap quiet splash i915.i915_enable_rc6=1 vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-21 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/22/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA51.88Z.00EF.B00.1205221442 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-2E6FAB96566FE58C dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir5,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-2E6FAB96566FE58C dmi.modalias: dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B00.1205221442:bd05/22/2012:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C: dmi.product.name: MacBookAir5,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1165965/+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 1027368] Re: [Samsung NP530U3B-A01UK] Laptop does not suspend on lid close
** Summary changed: - Samsung NP530U3B laptop does not suspend on lid close + [Samsung NP530U3B-A01UK] Laptop does not suspend on lid close -- 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/1027368 Title: [Samsung NP530U3B-A01UK] Laptop does not suspend on lid close Status in The Linux Kernel: Incomplete Status in “linux” package in Ubuntu: Incomplete Bug description: I've installed Ubuntu 12.04 on my wife's laptop, (a Samsung NP530U3B), all goes well except when I close the lid it does not suspend. I've checked the settings and it is set to suspend on lid close, though does not. Things I've noticed are: 1 - Clicking suspend in the power menu works fine. 2 - When I cat /proc/acpi/button/lid/LID0/state it always returns open, even when closed, (I ran a script that looped the cat then closed the lid) 3 - Running the latest Ubuntu 12.10 alpha 2 does not work either. 4 - The latest mainstream kernel 'linux-image-3.5.0-999-generic_3.5.0-999.201207190406_i386' does not work either. 5 - One odd thing was that after installing the latest bios on the laptop using Windows 7, then restarting into Ubuntu worked once, then it never worked again. I tried booting in to Windows then rebooting back in to Ubuntu to see if that is what changed something but it did not work that time. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-26-generic-pae 3.2.0-26.41 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic-pae 3.2.19 Uname: Linux 3.2.0-26-generic-pae i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu11 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lou2512 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf070 irq 50' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:10ec0269,144dc0c7,00100202 HDA:80862805,80860101,0010' Controls : 24 Simple ctrls : 11 Date: Sat Jul 21 09:37:25 2012 HibernationDevice: RESUME=UUID=3c27803e-5c58-4d5f-b649-d7357db99120 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3BI/530U4BI/530U4BH ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-26-generic-pae root=UUID=36b0eced-301e-4fa8-a3e4-2c1466de4955 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-26-generic-pae N/A linux-backports-modules-3.2.0-26-generic-pae N/A linux-firmware1.79 SourcePackage: linux StagingDrivers: mei UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 08XK dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 530U3BI/530U4BI/530U4BH dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr08XK:bd07/11/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3BI/530U4BI/530U4BH:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn530U3BI/530U4BI/530U4BH:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3BI/530U4BI/530U4BH dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1027368/+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 888838] Re: Saitek Pedals not recognized at boot, work after unplugging and plugging back in
Olivier Caro, please do not apport-collect to another person's report. 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 while booted into a Ubuntu repository kernel (not a mainline one) via: ubuntu-bug linux For more on this, please read the official Ubuntu documentation: Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports Ubuntu Community: 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. No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions or comments, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly. Thank you for your understanding. ** Tags removed: apport-collected precise running running-unity ** Attachment removed: WifiSyslog.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/38/+attachment/3919255/+files/WifiSyslog.txt ** Attachment removed: UserAsoundrc.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/38/+attachment/3919254/+files/UserAsoundrc.txt ** Attachment removed: UdevLog.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/38/+attachment/3919253/+files/UdevLog.txt ** Attachment removed: UdevDb.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/38/+attachment/3919252/+files/UdevDb.txt ** Attachment removed: PulseList.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/38/+attachment/3919251/+files/PulseList.txt ** Attachment removed: ProcModules.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/38/+attachment/3919250/+files/ProcModules.txt ** Attachment removed: ProcInterrupts.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/38/+attachment/3919249/+files/ProcInterrupts.txt ** Attachment removed: ProcEnviron.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/38/+attachment/3919248/+files/ProcEnviron.txt ** Attachment removed: ProcCpuinfo.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/38/+attachment/3919247/+files/ProcCpuinfo.txt ** Attachment removed: PciMultimedia.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/38/+attachment/3919246/+files/PciMultimedia.txt ** Attachment removed: Lsusb.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/38/+attachment/3919245/+files/Lsusb.txt ** Attachment removed: CurrentDmesg.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/38/+attachment/3919243/+files/CurrentDmesg.txt ** Attachment removed: Card1.Codecs.codec.0.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/38/+attachment/3919242/+files/Card1.Codecs.codec.0.txt ** Attachment removed: Lspci.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/38/+attachment/3919244/+files/Lspci.txt ** Attachment removed: Card0.Codecs.codec.0.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/38/+attachment/3919241/+files/Card0.Codecs.codec.0.txt ** Attachment removed: Card0.Amixer.values.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/38/+attachment/3919240/+files/Card0.Amixer.values.txt ** Attachment removed: BootDmesg.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/38/+attachment/3919239/+files/BootDmesg.txt ** Attachment removed: ArecordDevices.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/38/+attachment/3919238/+files/ArecordDevices.txt ** Attachment removed: AplayDevices.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/38/+attachment/3919237/+files/AplayDevices.txt ** Attachment removed: AlsaDevices.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/38/+attachment/3919236/+files/AlsaDevices.txt ** Attachment removed: AcpiTables.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/38/+attachment/3919235/+files/AcpiTables.txt ** Summary changed: - Saitek Pedals not recognized at boot, work after unplugging and plugging back in + [Gigabyte P35-S3G] Saitek Pedals not recognized at boot, work after unplugging and plugging back in -- 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/38 Title: [Gigabyte P35-S3G] Saitek Pedals not recognized at boot, work after unplugging and plugging back in Status in “linux” package in Ubuntu: Incomplete Bug description: This report applies
[Kernel-packages] [Bug 1027368] Re: [Samsung NP530U3B-A01UK] Laptop does not suspend on lid close
Pat Robinson, could you please execute the following at a terminal and post the results: sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date ** Tags removed: needs-full-computer-model -- 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/1027368 Title: [Samsung NP530U3B-A01UK] Laptop does not suspend on lid close Status in The Linux Kernel: Incomplete Status in “linux” package in Ubuntu: Incomplete Bug description: I've installed Ubuntu 12.04 on my wife's laptop, (a Samsung NP530U3B), all goes well except when I close the lid it does not suspend. I've checked the settings and it is set to suspend on lid close, though does not. Things I've noticed are: 1 - Clicking suspend in the power menu works fine. 2 - When I cat /proc/acpi/button/lid/LID0/state it always returns open, even when closed, (I ran a script that looped the cat then closed the lid) 3 - Running the latest Ubuntu 12.10 alpha 2 does not work either. 4 - The latest mainstream kernel 'linux-image-3.5.0-999-generic_3.5.0-999.201207190406_i386' does not work either. 5 - One odd thing was that after installing the latest bios on the laptop using Windows 7, then restarting into Ubuntu worked once, then it never worked again. I tried booting in to Windows then rebooting back in to Ubuntu to see if that is what changed something but it did not work that time. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-26-generic-pae 3.2.0-26.41 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic-pae 3.2.19 Uname: Linux 3.2.0-26-generic-pae i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu11 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lou2512 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf070 irq 50' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:10ec0269,144dc0c7,00100202 HDA:80862805,80860101,0010' Controls : 24 Simple ctrls : 11 Date: Sat Jul 21 09:37:25 2012 HibernationDevice: RESUME=UUID=3c27803e-5c58-4d5f-b649-d7357db99120 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3BI/530U4BI/530U4BH ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-26-generic-pae root=UUID=36b0eced-301e-4fa8-a3e4-2c1466de4955 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-26-generic-pae N/A linux-backports-modules-3.2.0-26-generic-pae N/A linux-firmware1.79 SourcePackage: linux StagingDrivers: mei UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 08XK dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 530U3BI/530U4BI/530U4BH dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr08XK:bd07/11/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3BI/530U4BI/530U4BH:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn530U3BI/530U4BI/530U4BH:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3BI/530U4BI/530U4BH dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1027368/+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 1213035] Re: e1000e module sometimes prevents suspend to ram
Just seen this on saucy with kernel 3.11.0-13-generic [32026.365726] PM: Entering mem sleep [32026.365783] Suspending console(s) (use no_console_suspend to debug) [32026.491757] sd 0:0:0:0: [sda] Synchronizing SCSI cache [32026.491946] sd 0:0:0:0: [sda] Stopping disk [32026.724207] mei_me :00:16.0: suspend [32027.346674] pci_pm_suspend(): e1000_suspend+0x0/0x20 [e1000e] returns -2 [32027.346678] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -2 [32027.346681] PM: Device :00:19.0 failed to suspend async: error -2 [32027.346722] PM: Some devices failed to suspend, or early wake event detected ** 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/1213035 Title: e1000e module sometimes prevents suspend to ram Status in “linux” package in Ubuntu: Confirmed Bug description: Sometimes, usually towards the end of the day, I find my e100e module does not allow the system to suspend. The following is seen in dmsg: [40697.709402] Freezing user space processes ... (elapsed 0.01 seconds) done. [40697.724258] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. [40697.740285] Suspending console(s) (use no_console_suspend to debug) [40697.872196] sd 0:0:0:0: [sda] Synchronizing SCSI cache [40698.041526] sd 0:0:0:0: [sda] Stopping disk [40698.714054] pci_pm_suspend(): e1000_suspend+0x0/0x20 [e1000e] returns -2 [40698.714058] dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -2 [40698.714061] PM: Device :00:19.0 failed to suspend async: error -2 [40698.714100] PM: Some devices failed to suspend rmmod e100e and I can suspend again. I do use the ethernet adapter, and it only has occurred after having been connected to ethernet. Seen on 13.04 amd64 with kernel 3.8.0-27-generic ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-27-generic 3.8.0-27.40 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anton 3094 F pulseaudio /dev/snd/controlC0: anton 3094 F pulseaudio Date: Thu Aug 15 17:22:00 2013 HibernationDevice: RESUME=UUID=471df139-754b-43b4-9979-4d334871c53e InstallationDate: Installed on 2013-07-05 (40 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: LENOVO 24491D1 MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nox2apic RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G5ET92WW (2.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 24491D1 dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ET92WW(2.52):bd02/27/2013:svnLENOVO:pn24491D1:pvrThinkPadW530:rvnLENOVO:rn24491D1:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 24491D1 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213035/+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 1255370] Re: MacBookPro11, 1 (Late 2013 Haswell) has no sound
I am not sure. My headphone works after installation and after resume. So there is no need to fix it. The internal mic seems to work fine, too. I do not have a mic to test external microphone. I don't know if the patch code posted on that page would work or not on my Macbook Pro 11,1. I actually don't know how to apply the patch. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1255370 Title: MacBookPro11,1 (Late 2013 Haswell) has no sound Status in “alsa-driver” package in Ubuntu: New Status in “linux” package in Ubuntu: Incomplete Bug description: I installed Ubuntu 13.10 on a new MacBook Pro (Late 2013, 13-inch Haswell retina). The speakers did not work after installation, and after I fixed it, it would not work after suspend. It turns out some of the flags were not set correctly. I can fix these problems but it would be nice to have them fixed at installation. The problem can be seen in the GPIO section in /proc/asound/card1/codec#0 (card0 is for HDMI). After boot, the GPIO flags for IO[0] were GPIO: io=6, o=2, i=0, unsolicited=1, wake=1 IO[0]: enable=1, dir=1, wake=0, sticky=0, data=0, unsol=0 If data were set to 1, sound would work! I fixed this by installing alsa-tools and adding to /etc/rc.local a line: hda-verb /dev/snd/hwC1D0 0x1 set_gpio_data 1 After resuming from suspend, the GPIO flags for IO[0] became GPIO: io=6, o=2, i=0, unsolicited=1, wake=1 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Here, three flags were set to 0. I fixed this by adding to /etc/pm/sleep.d/99_myfix a few lines: #!/bin/sh case $1 in resume|thaw) hda-verb /dev/snd/hwC1D0 0x1 set_gpio_mask 1 sleep 1 hda-verb /dev/snd/hwC1D0 0x1 set_gpio_direction 1 sleep 1 hda-verb /dev/snd/hwC1D0 0x1 set_gpio_data 1 ;; esac --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lic3 3717 F pulseaudio /dev/snd/controlC0: lic3 3717 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=a2156b27-f1e5-4408-9fb3-491e6f8229fb InstallationDate: Installed on 2013-11-06 (21 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Apple Inc. MacBookPro11,1 MarkForUpload: True NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic.efi.signed root=UUID=b62d2699-f735-46a1-8e31-23146f2497a3 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 Tags: saucy saucy Uname: Linux 3.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/22/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP111.88Z.0133.B00.1309220923 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvrMBP111.88Z.0133.B00.1309220923:bd09/22/2013:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.name: MacBookPro11,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1255370/+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 1255022] Re: Wireless networking unavailable/does not work
That said, using that kernel, I've had times when it's locked up -
acting like I have no network connection but not saying disconnected.
turning wifi off and on again (via network manager) brought it back
again. Couuld be coincidence, but never needed to do this before.
--
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/1255022
Title:
Wireless networking unavailable/does not work
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
After an upgrade to the linux-image-3.2.0-56-generic kernel on Ubuntu
12.04.3 LTS, my laptop had no wifi. No lights, nothing in network
manager to even acknowledge the existance of a wireless capability.
On rebooting into the previous kernel linux-image-3.2.0-55-generic it
works again (and thus I am able to report this!).
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-56-generic 3.2.0-56.86
ProcVersionSignature: Ubuntu 3.2.0-55.85-generic 3.2.51
Uname: Linux 3.2.0-55-generic x86_64
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rich 2542 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xc060 irq 48'
Mixer name : 'Intel CougarPoint HDMI'
Components : 'HDA:10ec0269,10250513,00100100
HDA:80862805,80860101,0010'
Controls : 27
Simple ctrls : 13
Date: Tue Nov 26 09:20:14 2013
HibernationDevice: RESUME=UUID=cdc83e00-ab58-4d15-8c00-1767e317ff39
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64
(20120425)
MachineType: Acer Aspire 5750
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-55-generic
root=UUID=72d863fd-0e78-4313-96b2-e194ebe1d127 ro
crashkernel=384M-2G:64M,2G-:128M quiet splash acpi_backlight=vendor vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-55-generic N/A
linux-backports-modules-3.2.0-55-generic N/A
linux-firmware1.79.7
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/09/2012
dmi.bios.vendor: Acer
dmi.bios.version: V1.21
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SJV70_HR
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.21
dmi.modalias:
dmi:bvnAcer:bvrV1.21:bd08/09/2012:svnAcer:pnAspire5750:pvrV1.21:rvnAcer:rnSJV70_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.21:
dmi.product.name: Aspire 5750
dmi.product.version: V1.21
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255022/+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 1256134] Re: Image appears cropped (underscan/overscan) on external HDTV display
** Attachment added: Xorg.0.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1256134/+attachment/3919428/+files/Xorg.0.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/1256134 Title: Image appears cropped (underscan/overscan) on external HDTV display Status in “linux” package in Ubuntu: New Bug description: I am visiting my parents who have a Samsung HDTV capable of 1920x1080i resolution (30/60Hz interlaced). When I plug in my Dell laptop (Inspiron N4010) with its integrated Intel graphics, I am unable to get the image to display correctly -- it appears cropped, with several percent of the top, bottom, left, and right missing -- I can't see the left-hand launch bar or the top menu bar on the screen. This HDTV displays correctly under Windows. I haven't been able to find any underscan/overscan setting for the display driver, either through xrandr or the Gnome display settings screen. This is something that should more or less just work. I have fought this problem periodically since I bought the laptop in 2010, but the situation has stayed about the same each time I have tried. This appears to be a fairly long-standing issue, and from my searching around, I suspect there may be a common root cause among Intel, nVidia, and ATI graphics devices. lsb_release -rd: Description: Ubuntu 13.04 Release: 13.04 /proc/version_signature: Ubuntu 3.8.0-33.48-generic 3.8.13.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1256134/+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 1256134] Re: Image appears cropped (underscan/overscan) on external HDTV display
** Attachment added: lspci-vnvn.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1256134/+attachment/3919427/+files/lspci-vnvn.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/1256134 Title: Image appears cropped (underscan/overscan) on external HDTV display Status in “linux” package in Ubuntu: New Bug description: I am visiting my parents who have a Samsung HDTV capable of 1920x1080i resolution (30/60Hz interlaced). When I plug in my Dell laptop (Inspiron N4010) with its integrated Intel graphics, I am unable to get the image to display correctly -- it appears cropped, with several percent of the top, bottom, left, and right missing -- I can't see the left-hand launch bar or the top menu bar on the screen. This HDTV displays correctly under Windows. I haven't been able to find any underscan/overscan setting for the display driver, either through xrandr or the Gnome display settings screen. This is something that should more or less just work. I have fought this problem periodically since I bought the laptop in 2010, but the situation has stayed about the same each time I have tried. This appears to be a fairly long-standing issue, and from my searching around, I suspect there may be a common root cause among Intel, nVidia, and ATI graphics devices. lsb_release -rd: Description: Ubuntu 13.04 Release: 13.04 /proc/version_signature: Ubuntu 3.8.0-33.48-generic 3.8.13.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1256134/+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 1256134] [NEW] Image appears cropped (underscan/overscan) on external HDTV display
Public bug reported: I am visiting my parents who have a Samsung HDTV capable of 1920x1080i resolution (30/60Hz interlaced). When I plug in my Dell laptop (Inspiron N4010) with its integrated Intel graphics, I am unable to get the image to display correctly -- it appears cropped, with several percent of the top, bottom, left, and right missing -- I can't see the left-hand launch bar or the top menu bar on the screen. This HDTV displays correctly under Windows. I haven't been able to find any underscan/overscan setting for the display driver, either through xrandr or the Gnome display settings screen. This is something that should more or less just work. I have fought this problem periodically since I bought the laptop in 2010, but the situation has stayed about the same each time I have tried. This appears to be a fairly long-standing issue, and from my searching around, I suspect there may be a common root cause among Intel, nVidia, and ATI graphics devices. lsb_release -rd: Description:Ubuntu 13.04 Release:13.04 /proc/version_signature: Ubuntu 3.8.0-33.48-generic 3.8.13.11 ** 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/1256134 Title: Image appears cropped (underscan/overscan) on external HDTV display Status in “linux” package in Ubuntu: New Bug description: I am visiting my parents who have a Samsung HDTV capable of 1920x1080i resolution (30/60Hz interlaced). When I plug in my Dell laptop (Inspiron N4010) with its integrated Intel graphics, I am unable to get the image to display correctly -- it appears cropped, with several percent of the top, bottom, left, and right missing -- I can't see the left-hand launch bar or the top menu bar on the screen. This HDTV displays correctly under Windows. I haven't been able to find any underscan/overscan setting for the display driver, either through xrandr or the Gnome display settings screen. This is something that should more or less just work. I have fought this problem periodically since I bought the laptop in 2010, but the situation has stayed about the same each time I have tried. This appears to be a fairly long-standing issue, and from my searching around, I suspect there may be a common root cause among Intel, nVidia, and ATI graphics devices. lsb_release -rd: Description: Ubuntu 13.04 Release: 13.04 /proc/version_signature: Ubuntu 3.8.0-33.48-generic 3.8.13.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1256134/+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 1256134] Re: Image appears cropped (underscan/overscan) on external HDTV display
** Attachment added: xrandr --verbose with Samsung HDTV connected (HDMI1) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1256134/+attachment/3919426/+files/xrandr--verbose.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/1256134 Title: Image appears cropped (underscan/overscan) on external HDTV display Status in “linux” package in Ubuntu: New Bug description: I am visiting my parents who have a Samsung HDTV capable of 1920x1080i resolution (30/60Hz interlaced). When I plug in my Dell laptop (Inspiron N4010) with its integrated Intel graphics, I am unable to get the image to display correctly -- it appears cropped, with several percent of the top, bottom, left, and right missing -- I can't see the left-hand launch bar or the top menu bar on the screen. This HDTV displays correctly under Windows. I haven't been able to find any underscan/overscan setting for the display driver, either through xrandr or the Gnome display settings screen. This is something that should more or less just work. I have fought this problem periodically since I bought the laptop in 2010, but the situation has stayed about the same each time I have tried. This appears to be a fairly long-standing issue, and from my searching around, I suspect there may be a common root cause among Intel, nVidia, and ATI graphics devices. lsb_release -rd: Description: Ubuntu 13.04 Release: 13.04 /proc/version_signature: Ubuntu 3.8.0-33.48-generic 3.8.13.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1256134/+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 1255370] Re: MacBookPro11, 1 (Late 2013 Haswell) has no sound
seem you are not using alsa-driver since dB range of headphone is different from speakers https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/log/?qt=grepq=cs4208 -- 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/1255370 Title: MacBookPro11,1 (Late 2013 Haswell) has no sound Status in “alsa-driver” package in Ubuntu: New Status in “linux” package in Ubuntu: Incomplete Bug description: I installed Ubuntu 13.10 on a new MacBook Pro (Late 2013, 13-inch Haswell retina). The speakers did not work after installation, and after I fixed it, it would not work after suspend. It turns out some of the flags were not set correctly. I can fix these problems but it would be nice to have them fixed at installation. The problem can be seen in the GPIO section in /proc/asound/card1/codec#0 (card0 is for HDMI). After boot, the GPIO flags for IO[0] were GPIO: io=6, o=2, i=0, unsolicited=1, wake=1 IO[0]: enable=1, dir=1, wake=0, sticky=0, data=0, unsol=0 If data were set to 1, sound would work! I fixed this by installing alsa-tools and adding to /etc/rc.local a line: hda-verb /dev/snd/hwC1D0 0x1 set_gpio_data 1 After resuming from suspend, the GPIO flags for IO[0] became GPIO: io=6, o=2, i=0, unsolicited=1, wake=1 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Here, three flags were set to 0. I fixed this by adding to /etc/pm/sleep.d/99_myfix a few lines: #!/bin/sh case $1 in resume|thaw) hda-verb /dev/snd/hwC1D0 0x1 set_gpio_mask 1 sleep 1 hda-verb /dev/snd/hwC1D0 0x1 set_gpio_direction 1 sleep 1 hda-verb /dev/snd/hwC1D0 0x1 set_gpio_data 1 ;; esac --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lic3 3717 F pulseaudio /dev/snd/controlC0: lic3 3717 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=a2156b27-f1e5-4408-9fb3-491e6f8229fb InstallationDate: Installed on 2013-11-06 (21 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Apple Inc. MacBookPro11,1 MarkForUpload: True NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic.efi.signed root=UUID=b62d2699-f735-46a1-8e31-23146f2497a3 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 Tags: saucy saucy Uname: Linux 3.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/22/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP111.88Z.0133.B00.1309220923 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvrMBP111.88Z.0133.B00.1309220923:bd09/22/2013:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.name: MacBookPro11,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1255370/+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 1213035] Re: e1000e module sometimes prevents suspend to ram
** Tags added: saucy -- 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/1213035 Title: e1000e module sometimes prevents suspend to ram Status in “linux” package in Ubuntu: Confirmed Bug description: Sometimes, usually towards the end of the day, I find my e100e module does not allow the system to suspend. The following is seen in dmsg: [40697.709402] Freezing user space processes ... (elapsed 0.01 seconds) done. [40697.724258] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. [40697.740285] Suspending console(s) (use no_console_suspend to debug) [40697.872196] sd 0:0:0:0: [sda] Synchronizing SCSI cache [40698.041526] sd 0:0:0:0: [sda] Stopping disk [40698.714054] pci_pm_suspend(): e1000_suspend+0x0/0x20 [e1000e] returns -2 [40698.714058] dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -2 [40698.714061] PM: Device :00:19.0 failed to suspend async: error -2 [40698.714100] PM: Some devices failed to suspend rmmod e100e and I can suspend again. I do use the ethernet adapter, and it only has occurred after having been connected to ethernet. Seen on 13.04 amd64 with kernel 3.8.0-27-generic ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-27-generic 3.8.0-27.40 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anton 3094 F pulseaudio /dev/snd/controlC0: anton 3094 F pulseaudio Date: Thu Aug 15 17:22:00 2013 HibernationDevice: RESUME=UUID=471df139-754b-43b4-9979-4d334871c53e InstallationDate: Installed on 2013-07-05 (40 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: LENOVO 24491D1 MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash nox2apic RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G5ET92WW (2.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 24491D1 dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ET92WW(2.52):bd02/27/2013:svnLENOVO:pn24491D1:pvrThinkPadW530:rvnLENOVO:rn24491D1:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 24491D1 dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213035/+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 1036063] Re: BUG: soft lockup - CPU#4 stuck for 22s! [rm:30630]
Micah Gersten, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If it remains an issue, could you please run the following command in the development release from a Terminal (Applications-Accessories-Terminal), as it will automatically gather and attach updated debug information to this report: apport-collect -p linux replace-with-bug-number Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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.13-rc1 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 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. ** Changed in: linux (Ubuntu) Status: Triaged = 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/1036063 Title: BUG: soft lockup - CPU#4 stuck for 22s! [rm:30630] Status in “linux” package in Ubuntu: Incomplete Bug description: There were similar messages for CPU #2. This was a few minutes after starting the -29.46 kernel ii linux-image-3.2.0-29-generic 3.2.0-29.46 Aug 13 01:59:51 voyager kernel: [ 1308.229091] BUG: soft lockup - CPU#4 stuck for 22s! [rm:30630] Aug 13 01:59:51 voyager kernel: [ 1308.229100] Modules linked in: overlayfs xt_multiport ip6table_filter ip6_tables ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter ip_tables x_tables bridge stp kvm_intel kvm bnep rfcomm bluetooth parport_pc ppdev binfmt_misc dm_crypt snd_hda_codec_hdmi snd_hda_code c_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq arc4 snd_timer uvcvideo videodev joydev snd_seq_device snd iwlwifi v4l2_compat_ioctl32 soundcore mac8021 1 cfg80211 mei(C) snd_page_alloc psmouse serio_raw mac_hid dm_multipath jmb38x_ms memstick sbs sbshc coretemp lp parport nbd dm_raid45 xor dm_mirror dm_region_hash dm_log usbhid hid nouveau ttm firewire_ohci drm_ kms_helper firewire_core jme crc_itu_t drm sdhci_pci sdhci i2c_algo_bit mxm_wmi wmi video Aug 13 01:59:51 voyager kernel: [ 1308.229247] CPU 4 Aug 13 01:59:51 voyager kernel: [ 1308.229250] Modules linked in: overlayfs xt_multiport ip6table_filter ip6_tables ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter ip_tables x_tables bridge stp kvm_intel kvm bnep rfcomm bluetooth parport_pc ppdev binfmt_misc dm_crypt snd_hda_codec_hdmi snd_hda_code c_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq arc4 snd_timer uvcvideo videodev joydev snd_seq_device snd iwlwifi v4l2_compat_ioctl32 soundcore mac8021 1 cfg80211 mei(C) snd_page_alloc psmouse serio_raw mac_hid dm_multipath jmb38x_ms memstick sbs sbshc coretemp lp parport nbd dm_raid45 xor dm_mirror dm_region_hash dm_log usbhid hid nouveau ttm firewire_ohci drm_ kms_helper firewire_core jme crc_itu_t drm sdhci_pci sdhci i2c_algo_bit mxm_wmi wmi video Aug 13 01:59:51 voyager kernel: [ 1308.229376] Aug 13 01:59:51 voyager kernel: [ 1308.229381] Pid: 30630, comm: rm Tainted: G D C 3.2.0-29-generic #46-Ubuntu System76, Inc. Gazelle Professional/Gazelle Professional Aug 13 01:59:51 voyager kernel: [ 1308.229394] RIP: 0010:[8103dc62] [8103dc62] __ticket_spin_lock+0x22/0x30 Aug 13 01:59:51 voyager kernel: [ 1308.229408] RSP: 0018:88073ff8bdd8 EFLAGS: 0297 Aug 13 01:59:51 voyager kernel: [ 1308.229413] RAX: 7b10 RBX: 8125e686 RCX: a9cc Aug 13 01:59:51 voyager kernel: [ 1308.229418] RDX: 7b11
[Kernel-packages] [Bug 1033410] Re: [Samsung NP530U3B-A02SE] samsung-laptop module kernel panic 3.2.0-27
Jarkko Torvinen, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If it remains an issue, could you please just make a comment to this. Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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.13-rc1 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 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. ** Changed in: linux (Ubuntu) Status: Triaged = Incomplete ** Changed in: linux (Ubuntu) Importance: High = Low -- 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/1033410 Title: [Samsung NP530U3B-A02SE] samsung-laptop module kernel panic 3.2.0-27 Status in “linux” package in Ubuntu: Incomplete Bug description: update to linux-image 3.2.0-27 results in system not booting on Samsung 5 Series laptop (NP530U3B-A02SE) there is a entry in changelog: * samsung-laptop: make the dmi check less strict - LP: #1012284 on kernel 3.2.0-26 modprobe samsung-laptop says no such device, but on 3.2.0-27 it tries to load it automatically and causes instant kernel panic and system hangs WORKAROUND: blacklisting samsung-laptop. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu11 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarkkot2067 F pulseaudio /dev/snd/pcmC0D0p: jarkkot2067 F...m pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf070 irq 50' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:10ec0269,144dc0c7,00100202 HDA:80862805,80860101,0010' Controls : 24 Simple ctrls : 11 DistroRelease: Ubuntu 12.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=5ce42c18-9f02-44fe-b82d-e1070195b1c5 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3BI/530U4BI/530U4BH Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-27-generic root=UUID=ecbc5b60-4608-4aec-b5c5-08c2c9f6aaa3 ro i915.semaphores=1 i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21 RelatedPackageVersions: linux-restricted-modules-3.2.0-27-generic N/A linux-backports-modules-3.2.0-27-generic N/A linux-firmware1.79 StagingDrivers: mei Tags: precise running-unity staging Uname: Linux 3.2.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 03/16/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 06XK dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 530U3BI/530U4BI/530U4BH dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr06XK:bd03/16/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3BI/530U4BI/530U4BH:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn530U3BI/530U4BI/530U4BH:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3BI/530U4BI/530U4BH dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1256134] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1256134 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 ** Tags added: 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/1256134 Title: Image appears cropped (underscan/overscan) on external HDTV display Status in “linux” package in Ubuntu: Incomplete Bug description: I am visiting my parents who have a Samsung HDTV capable of 1920x1080i resolution (30/60Hz interlaced). When I plug in my Dell laptop (Inspiron N4010) with its integrated Intel graphics, I am unable to get the image to display correctly -- it appears cropped, with several percent of the top, bottom, left, and right missing -- I can't see the left-hand launch bar or the top menu bar on the screen. This HDTV displays correctly under Windows. I haven't been able to find any underscan/overscan setting for the display driver, either through xrandr or the Gnome display settings screen. This is something that should more or less just work. I have fought this problem periodically since I bought the laptop in 2010, but the situation has stayed about the same each time I have tried. This appears to be a fairly long-standing issue, and from my searching around, I suspect there may be a common root cause among Intel, nVidia, and ATI graphics devices. lsb_release -rd: Description: Ubuntu 13.04 Release: 13.04 /proc/version_signature: Ubuntu 3.8.0-33.48-generic 3.8.13.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1256134/+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 1055475] Re: [Apple Inc. MacBookPro5, 4] suspend/resume failure [non-free: wl]
Mario Vukelic, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If it remains an issue, could you please just make a comment to this. Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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.13-rc1 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 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. ** Description changed: Note: When the problem occurred and the apport bug report was created, the non-free wl module was loaded (compiled from bcmwl-kernel-source) to enable the Broadcom wifi. However, the same problem happens after removing the wl module and rebooting. On this machine, suspend/resume has worked in released Ubuntu versions since its purchase mid-2009, when IIRC it received a development version install of Karmic (9.10). Hibernate/resume worked just as reliably. The latest fresh install was Oneiric (11.10), later upgraded to Precise (12.04) after release. The machine usually ran the proprietary NVidia graphics drivers, therefore I am unsure if suspend/hibernate/resume also worked with the nouveau drivers (however I seem to remember so). I now performed a reinstall with 12.04.1 (using the BIOS image, not the EFI image) and immediately upgraded to Quantal. (For some reason I could not make Quantal CDs boot). The machine is now using the nouveau drivers because currently the backlight adjustment does not work with NVidia drivers. - In Quantal with nouveau, resume from suspend never worked for me. When - going into suspended state all at first appears fine. However, the - machine does not resume properly. When trying to resume, the fan and - optical drive starts, however the screen remains black and I can't tell - if its responsive. I pressed the power button for 5 seconds and the - machine rebooted fine. After logging in, an apport prompt appeared, from - which I created this bug report. + In Quantal with nouveau, resume from suspend never worked for me. When going into suspended state all at first appears fine. However, the machine does not resume properly. When trying to resume, the fan and optical drive starts, however the screen remains black and I can't tell if its responsive. I pressed the power button for 5 seconds and the machine rebooted fine. After logging in, an apport prompt appeared, from which I created this bug report. + I don't know about hibernate since due to using an encrypted home directory it is not available anymore. - Resume works correctly with the proprietary nvidia-current drivers. - - I don't know about hibernate since due to using an encrypted home - directory it is not available anymore. + WORKAROUND: Resume works correctly with the proprietary nvidia-current + drivers. ProblemType: KernelOops DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-15-generic 3.5.0-15.22 ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.5.2-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mario 2337 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Sep 24 09:05:58 2012 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=58df2950-5d89-42a8-a44c-3bf5410313aa InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) InterpreterPath: /usr/bin/python3.2mu MachineType: Apple Inc. MacBookPro5,4 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0
[Kernel-packages] [Bug 1173681] Re: 168c:002b [asus_nb_wmi] [Asus U32U] AR9285 ath9k not working after updating to ubuntu 13.04 Raring (linux 3.8.0-19-generic)
I too await a fix for my Asus U32U Net Book Wireless. Thank you all, for all you do ! Your time and effort is greatly appreceiated :- ) LinuxPusher, Oz Development Team. -- 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/1173681 Title: 168c:002b [asus_nb_wmi] [Asus U32U] AR9285 ath9k not working after updating to ubuntu 13.04 Raring (linux 3.8.0-19-generic) Status in The Linux Kernel: New Status in “linux” package in Ubuntu: Incomplete Bug description: update: updated the BIOS to the latest version but the problem persists. Booting with the older kernel (latest linux kernel from 12.10) every thing works fine. After upgrading to Raring Ringtail Ubuntu 13.04, with the new kernel, hardware get blocked/disabled and wireless doesn't work: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes 1: asus-wlan: Wireless LAN Soft blocked: no Hard blocked: no WORKAROUND - is only applicable to Asus Notebooks/netbooks that use the asus_nb_wmi driver: Create and edit asus_nb_wmi.conf file with this command: sudo echo options asus_nb_wmi wapf=1 | sudo tee /etc/modprobe.d/asus_nb_wmi.conf For more detailed info of the workaround please see: http://ubuntuforums.org/showthread.php?t=2181558 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.29 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/controlC1: x 1822 F pulseaudio CurrentDmesg: [ 370.100280] r8169 :04:00.2 eth1: link up [ 370.100322] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 891.718748] systemd-hostnamed[2649]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname! [14119.241628] rtsx_pci :04:00.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update. Date: Sat Apr 27 17:31:51 2013 HibernationDevice: RESUME=UUID=e417e9f2-b63e-4b79-9be4-c21f55547205 InstallationDate: Installed on 2012-07-13 (287 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: ASUSTeK Computer Inc. U32U MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=3ad9d88b-a7a5-460f-ba15-a78dd7f2fc94 ro 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: Upgraded to raring on 2013-04-27 (0 days ago) dmi.bios.date: 12/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U32U.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U32U 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.:bvrU32U.204:bd12/16/2011:svnASUSTeKComputerInc.:pnU32U:pvr1.0:rvnASUSTeKComputerInc.:rnU32U:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: U32U dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1173681/+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 1173681] Re: 168c:002b [asus_nb_wmi] [Asus U32U] AR9285 ath9k not working after updating to ubuntu 13.04 Raring (linux 3.8.0-19-generic)
LInuxPusher, could you please file a report so your hardware may be tracked via a terminal: ubuntu-bug linux -- 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/1173681 Title: 168c:002b [asus_nb_wmi] [Asus U32U] AR9285 ath9k not working after updating to ubuntu 13.04 Raring (linux 3.8.0-19-generic) Status in The Linux Kernel: New Status in “linux” package in Ubuntu: Incomplete Bug description: update: updated the BIOS to the latest version but the problem persists. Booting with the older kernel (latest linux kernel from 12.10) every thing works fine. After upgrading to Raring Ringtail Ubuntu 13.04, with the new kernel, hardware get blocked/disabled and wireless doesn't work: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes 1: asus-wlan: Wireless LAN Soft blocked: no Hard blocked: no WORKAROUND - is only applicable to Asus Notebooks/netbooks that use the asus_nb_wmi driver: Create and edit asus_nb_wmi.conf file with this command: sudo echo options asus_nb_wmi wapf=1 | sudo tee /etc/modprobe.d/asus_nb_wmi.conf For more detailed info of the workaround please see: http://ubuntuforums.org/showthread.php?t=2181558 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-19-generic 3.8.0-19.29 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/controlC1: x 1822 F pulseaudio CurrentDmesg: [ 370.100280] r8169 :04:00.2 eth1: link up [ 370.100322] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 891.718748] systemd-hostnamed[2649]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname! [14119.241628] rtsx_pci :04:00.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update. Date: Sat Apr 27 17:31:51 2013 HibernationDevice: RESUME=UUID=e417e9f2-b63e-4b79-9be4-c21f55547205 InstallationDate: Installed on 2012-07-13 (287 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: ASUSTeK Computer Inc. U32U MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=3ad9d88b-a7a5-460f-ba15-a78dd7f2fc94 ro 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: Upgraded to raring on 2013-04-27 (0 days ago) dmi.bios.date: 12/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U32U.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U32U 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.:bvrU32U.204:bd12/16/2011:svnASUSTeKComputerInc.:pnU32U:pvr1.0:rvnASUSTeKComputerInc.:rnU32U:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: U32U dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1173681/+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 1064521] Re: Kernel I/O scheduling writes starving reads, local DoS
** Tags added: bios-outdated-2.6.1 needs-upstream-testing 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/1064521 Title: Kernel I/O scheduling writes starving reads, local DoS Status in “linux” package in Ubuntu: Triaged Status in “linux” source package in Precise: Triaged Status in “linux” source package in Quantal: Triaged Bug description: On the Precise default kernel, it is possible by executing zcat on a large file for an unprivileged user to disrupt I/O sufficiently that it causes serious disruption. Serious disruption means (e.g.) a single MySQL update hangs for over 120 seconds on the default scheduler (cfq), and between 1 and 11 seconds on the deadline scheduler. This is reproducible on 2 sets of hardware using: root@extility-qa-test:~# uname -a Linux extility-qa-test 3.2.0-29-generic #46-Ubuntu SMP Fri Jul 27 17:03:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux linux-image-3.2.0-29-generic 3.2.0-29.46 root@extility-qa-test:~# cat /proc/sys/vm/dirty_ratio 20 root@extility-qa-test:~# cat /proc/sys/vm/dirty_background_ratio 10 No such problems occur on Lucid OS running the Oneiric Backports kernel. root@management-dev2:~# uname -a Linux management-dev2 3.0.0-15-server #26~lucid1-Ubuntu SMP Wed Jan 25 15:55:45 UTC 2012 x86_64 GNU/Linux linux-image-3.0.0-15-server 3.0.0-15.26~lucid1 In order to replicate, download (e.g.) this gzipped Lucid image (note this is not the OS we are running, this is just an example of the a file that causes the problem): http://repo.flexiant.com/images/public/kvm/ubuntu10.04.img.gz and as un unprivileged user, on a default, untuned Precise install, do zcat ubuntu10.04.img.gz test Now in another window execute any trivial mysql update on any table. Note that this can take a hugely long time. show full processlist in mysql console will show the time taken executing the command. In kernel logs (with cfq) we see e.g.: Oct 8 14:57:02 extility-qa-test kernel: [ 3840.268048] INFO: task mysqld:1358 blocked for more than 120 seconds. Oct 8 14:57:02 extility-qa-test kernel: [ 3840.268144] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Oct 8 14:57:02 extility-qa-test kernel: [ 3840.268267] mysqld D 81806200 0 1358 1 0x Oct 8 14:57:02 extility-qa-test kernel: [ 3840.268272] 8801921fde48 0082 8801921fde00 00030001 Oct 8 14:57:02 extility-qa-test kernel: [ 3840.268278] 8801921fdfd8 8801921fdfd8 8801921fdfd8 00013780 Oct 8 14:57:02 extility-qa-test kernel: [ 3840.268283] 880195169700 880191f79700 8801921fde58 8801912b2800 Oct 8 14:57:02 extility-qa-test kernel: [ 3840.268288] Call Trace: Oct 8 14:57:02 extility-qa-test kernel: [ 3840.268298] [816579cf] schedule+0x3f/0x60 Oct 8 14:57:02 extility-qa-test kernel: [ 3840.268303] [812650d5] jbd2_log_wait_commit+0xb5/0x130 Oct 8 14:57:02 extility-qa-test kernel: [ 3840.268308] [8108aa50] ? add_wait_queue+0x60/0x60 Oct 8 14:57:02 extility-qa-test kernel: [ 3840.268313] [81211248] ext4_sync_file+0x208/0x2d0 Oct 8 14:57:02 extility-qa-test kernel: [ 3840.268317] [81177ba0] ? vfs_write+0x110/0x180 Oct 8 14:57:02 extility-qa-test kernel: [ 3840.268321] [811a63a6] do_fsync+0x56/0x80 Oct 8 14:57:02 extility-qa-test kernel: [ 3840.268325] [811a66d0] sys_fsync+0x10/0x20 Oct 8 14:57:02 extility-qa-test kernel: [ 3840.268329] [81661ec2] system_call_fastpath+0x16/0x1b Oct 8 14:59:02 extility-qa-test kernel: [ 3960.268176] INFO: task mysqld:1358 blocked for more than 120 seconds. Oct 8 14:59:02 extility-qa-test kernel: [ 3960.268282] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Oct 8 14:59:02 extility-qa-test kernel: [ 3960.268393] mysqld D 81806200 0 1358 1 0x Oct 8 14:59:02 extility-qa-test kernel: [ 3960.268399] 8801921fde48 0082 8801921fde00 00030001 Oct 8 14:59:02 extility-qa-test kernel: [ 3960.268405] 8801921fdfd8 8801921fdfd8 8801921fdfd8 00013780 Oct 8 14:59:02 extility-qa-test kernel: [ 3960.268410] 880195169700 880191f79700 8801921fde58 8801912b2800 Oct 8 14:59:02 extility-qa-test kernel: [ 3960.268415] Call Trace: Oct 8 14:59:02 extility-qa-test kernel: [ 3960.268426] [816579cf] schedule+0x3f/0x60 Oct 8 14:59:02 extility-qa-test kernel: [ 3960.268431] [812650d5] jbd2_log_wait_commit+0xb5/0x130 Oct 8 14:59:02 extility-qa-test kernel: [ 3960.268436] [8108aa50] ? add_wait_queue+0x60/0x60 Oct 8 14:59:02 extility-qa-test kernel: [
[Kernel-packages] [Bug 1066211] Re: 8086:0116 Screen backlight is off by default on HP Folio 13-1000 series
** Summary changed: - Screen backlight is off by default on HP Folio 13-1000 series + 8086:0116 Screen backlight is off by default on HP Folio 13-1000 series ** Tags added: needs-full-computer-model ** Summary changed: - 8086:0116 Screen backlight is off by default on HP Folio 13-1000 series + 8086:0116 [HP Folio 13-1050la] Screen backlight is off by default ** Tags removed: needs-full-computer-model ** Tags added: bios-outdated-f.0b -- 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/1066211 Title: 8086:0116 [HP Folio 13-1050la] Screen backlight is off by default Status in “linux” package in Ubuntu: Triaged Bug description: On an HP Folio 13, the monitor's backlight does not work by default. WORKAROUND: Add a kernel parameter through grub's config to make it work: acpi_backlight=vendor See http://labo.eliaz.fr/spip.php?article94 . ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gpothier 1892 F pulseaudio Date: Sat Oct 13 00:25:35 2012 HibernationDevice: RESUME=UUID=281e4254-f100-4193-8e7d-13c4d9785734 MachineType: Hewlett-Packard HP Folio 13 Notebook PCC ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=acdbf868-560a-4ec7-8772-45c16c166819 ro acpi_backlight=vendor quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 SourcePackage: linux StagingDrivers: rts_pstor UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 17F8 dmi.board.vendor: Hewlett-Packard dmi.board.version: 46.34 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.06:bd03/05/2012:svnHewlett-Packard:pnHPFolio13NotebookPCC:pvr068C10204A0320100:rvnHewlett-Packard:rn17F8:rvr46.34:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Folio 13 Notebook PCC dmi.product.version: 068C10204A0320100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066211/+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
