Re: [Kernel-packages] [Bug 1247647] Re: Kernel oops during btrfs access
Strange, i get the same problem with both kernels. Nov 5 08:12:31 ubuntunas kernel: [ 18.506379] [ cut here ] Nov 5 08:12:31 ubuntunas kernel: [ 18.507390] Kernel BUG at a014f0d2 [verbose debug info unavailable] Nov 5 08:12:31 ubuntunas kernel: [ 18.508754] invalid opcode: [#1] SMP Nov 5 08:12:31 ubuntunas kernel: [ 18.509711] Modules linked in: dm_crypt kvm_intel kvm microcode psmouse serio_raw virtio_balloon i2c_piix4 mac_hid lp parport btrfs xor zlib_deflate raid6_pq libcrc32c cirrus syscopyarea sysfillrect sysimgblt ttm drm_kms_helper drm floppy Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] CPU: 0 PID: 611 Comm: btrfs-balance Not tainted 3.11.0-031100-generic #201309021735 Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2007 Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] task: 8800360d1770 ti: 8800b5a68000 task.ti: 8800b5a68000 Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] RIP: 0010:[] [] build_backref_tree+0x282/0x1250 [btrfs] Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] RSP: 0018:8800b5a69ab8 EFLAGS: 00010246 Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] RAX: RBX: 8800b7bf8240 RCX: 8800b4c4f590 Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] RDX: 8800b5a69b58 RSI: 8800b4c4f580 RDI: 88004d7a8280 Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] RBP: 8800b5a69bb8 R08: 88004d7a8b80 R09: 88004d7a8b80 Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] R10: 0001 R11: R12: 8800b4c4f590 Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] R13: 88004d7a8580 R14: R15: 8800b3dfe800 Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] FS: () GS:8800bb20() knlGS: Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] CS: 0010 DS: ES: CR0: 8005003b Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] CR2: 7fef3c9972f0 CR3: b4d93000 CR4: 06f0 Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] Stack: Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] 88004d7a8b80 8800b4c4f060 8800b3dfe920 Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] 88003607a000 88004d7a8380 88004d7a83c0 8800b7bf8240 Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] 88004d7a8380 8800b7bf8120 8800b3dfe924 8800b3dfe820 Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] Call Trace: Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] [] relocate_tree_blocks+0x13b/0x1e0 [btrfs] Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] [] relocate_block_group+0x193/0x570 [btrfs] Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] [] btrfs_relocate_block_group+0x1b7/0x2f0 [btrfs] Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] [] btrfs_relocate_chunk.isra.62+0x56/0x3e0 [btrfs] Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] [] ? block_group_cache_tree_search+0xb0/0xf0 [btrfs] Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] [] ? release_extent_buffer+0x39/0x60 [btrfs] Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] [] ? _raw_spin_lock+0xe/0x20 Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] [] ? free_extent_buffer.part.40+0x32/0x90 [btrfs] Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] [] __btrfs_balance+0x312/0x3f0 [btrfs] Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] [] btrfs_balance+0x33a/0x5d0 [btrfs] Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] [] balance_kthread+0x84/0x90 [btrfs] Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] [] ? btrfs_balance+0x5d0/0x5d0 [btrfs] Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] [] kthread+0xc0/0xd0 Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] [] ? flush_kthread_worker+0xb0/0xb0 Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] [] ret_from_fork+0x7c/0xb0 Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] [] ? flush_kthread_worker+0xb0/0xb0 Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] Code: 0f 85 9b 0f 00 00 49 8d 44 24 40 48 89 85 30 ff ff ff 49 8b 44 24 40 48 39 85 30 ff ff ff 74 20 49 3b 44 24 48 0f 84 6a 09 00 00 <0f> 0b 48 8b 9d 38 ff ff ff 49 c7 c4 f4 ff ff ff e9 ec fd ff ff Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] RIP [] build_backref_tree+0x282/0x1250 [btrfs] Nov 5 08:12:31 ubuntunas kernel: [ 18.510211] RSP Nov 5 08:12:31 ubuntunas kernel: [ 18.567218] ---[ end trace 51fc6470fa94310c ]--- Nov 5 08:13:41 ubuntunas kernel: [ 13.895581] [ cut here ] Nov 5 08:13:41 ubuntunas kernel: [ 13.896407] Kernel BUG at a0150512 [verbose debug info unavailable] Nov 5 08:13:41 ubuntunas kernel: [ 13.897821] invalid opcode: [#1] SMP Nov 5 08:13:41 ubuntunas kernel: [ 13.898717] Modules linked in: dm_crypt kvm_intel kvm microcode psmouse serio_raw virtio_balloon i2c_piix4 mac_hid lp parport btrfs xor zlib_deflate raid6_pq libcrc3
[Kernel-packages] [Bug 1243825] Re: wont resume when awakened from suspend
Mary, do you have an AMD/ATI video card? I removed the proprietary fglrx driver and so far it seems to work again. Even my problems with the external monitor are gone. -- 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/1243825 Title: wont resume when awakened from suspend Status in “linux” package in Ubuntu: Incomplete Bug description: I'm on an HP mini running 13.10 32 bit. After I got the update for this 13.10 from 13.04 my computer stopped waking up from suspension. Everything was perfect before the update. If you need more info, just let me know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1243825/+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 585765] Re: [HP ProBook 6440b] Ubuntu 10.04 random freezes
I am currently running 13.04 and the same problem is still present. It's
been with me since 12.04
But now I have discovered a pattern to these freezes: My power cord is
always unplugged when Ubuntu freezes.
I have a usage pattern that might have an impact: Whenever the screen
saver is starting (the desktop is fading out), I push shift or move my
mouse to avoid having to write the password. I know, it's odd behavior
since I could just prolong the timeout.
Clearly this has to do with power management, 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/585765
Title:
[HP ProBook 6440b] Ubuntu 10.04 random freezes
Status in The Linux Kernel:
New
Status in “linux” package in Ubuntu:
Incomplete
Status in “xorg-server” package in Ubuntu:
Invalid
Bug description:
Hello,
on my new laptop, a HP ProBook 6440b (with Core i5 and a plain Intel
Chipset, 4GB RAM) I get randomly freezes of the whole system. I can't
reproduce that, what means I don't know a aplication or usage of the
system making it freeze. sometimes I have uptimes of a day, without
freeze and sometimes it freezes right after booting the system.
I found out, that sometimes the MagicSysRQ (R-E-I-S-U-B) works and let
me shut down the system, sometimes not. I don't know what makes that
difference. In the system log I can't find any unusual entries. But I
foun that the system log is still runing, so shuting down the wifi
with the notebooks hardware switch for example is logged. Also the
Wifi network connection to my router is not interrupted.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-generic 2.6.32-22.33
Regression: No
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: florian1689 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xd490 irq 17'
Mixer name : 'Intel G45 DEVIBX'
Components : 'HDA:111d7603,103c1722,00100202
HDA:11c11040,103c3066,00100200 HDA:80862804,80860101,0010'
Controls : 23
Simple ctrls : 14
Date: Wed May 26 11:03:07 2010
EcryptfsInUse: Yes
Frequency: Once a day.
HibernationDevice: RESUME=UUID=24088f3d-7be1-4efd-a05a-d1fac42086df
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MachineType: Hewlett-Packard HP ProBook 6440b
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic
root=UUID=ac1bccdd-e231-45c3-bfde-991ae9549f0f ro quiet splash
ProcEnviron:
LANG=de_DE.utf8
SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
SourcePackage: linux
dmi.bios.date: 01/27/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68CDD Ver. F.04
dmi.board.name: 1722
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 29.2B
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnHewlett-Packard:bvr68CDDVer.F.04:bd01/27/2010:svnHewlett-Packard:pnHPProBook6440b:pvr:rvnHewlett-Packard:rn1722:rvrKBCVersion29.2B:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 6440b
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/585765/+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 1235081] Re: [ASUSTeK COMPUTER INC. X202E] suspend/resume failure
This did not occur previously. It seems to have stopped occurring since Saucy was released. You can probably close this bug in the meantime. -- 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/1235081 Title: [ASUSTeK COMPUTER INC. X202E] suspend/resume failure Status in “linux” package in Ubuntu: Incomplete Bug description: Closed the lid and opened it again. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-11-generic 3.11.0-11.17 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kfarnung 2075 F pulseaudio Date: Thu Oct 3 22:24:02 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=b91fa4b0-91ee-4f6e-b315-ac2a94c0dab8 InstallationDate: Installed on 2013-10-03 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterpreterPath: /usr/bin/python3.3 MachineType: ASUSTeK COMPUTER INC. X202E MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.11.0-11-generic N/A linux-backports-modules-3.11.0-11-generic N/A linux-firmware 1.116 SourcePackage: linux Title: [ASUSTeK COMPUTER INC. X202E] suspend/resume failure UpgradeStatus: Upgraded to saucy on 2013-10-03 (0 days ago) UserGroups: dmi.bios.date: 06/20/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X202E.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X202E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX202E.210:bd06/20/2013:svnASUSTeKCOMPUTERINC.:pnX202E:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX202E:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X202E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235081/+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 1248034] [NEW] The "Restart" button in system menu does not make sense
Public bug reported: On Saucy, there is a stand-alone "Restart" button in the system menu. But when you click it, it brings up the same menu that "Shut down" will brings. Furthermore, it will be focusing on "Shut down" instead of Restart Maybe these two option in the system should be combined together. Or at lease the "Restart" option should be highlighted when the menu was called by the Restart option. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 [modified: boot/vmlinuz-3.11.0-12-generic] 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 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1407 F pulseaudio CurrentDmesg: Date: Tue Nov 5 00:36:56 2013 HibernationDevice: RESUME=UUID=0986bf55-0186-4118-93df-522940ac63d0 InstallationDate: Installed on 2013-11-05 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Vostro 3560 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=51a4484a-5bd4-4d0e-acb5-6a826989ba8d ro rootdelay=60 quiet splash initcall_debug 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 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: X44 dmi.board.name: 05GV6H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X44 dmi.modalias: dmi:bvnDellInc.:bvrX44:bd08/03/2012:svnDellInc.:pnVostro3560:pvrX44:rvnDellInc.:rn05GV6H:rvrA00:cvnDellInc.:ct8:cvrX44: dmi.product.name: Vostro 3560 dmi.product.version: X44 dmi.sys.vendor: Dell Inc. ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy staging ** Package changed: linux (Ubuntu) => unity (Ubuntu) -- 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/1248034 Title: The "Restart" button in system menu does not make sense Status in “unity” package in Ubuntu: New Bug description: On Saucy, there is a stand-alone "Restart" button in the system menu. But when you click it, it brings up the same menu that "Shut down" will brings. Furthermore, it will be focusing on "Shut down" instead of Restart Maybe these two option in the system should be combined together. Or at lease the "Restart" option should be highlighted when the menu was called by the Restart option. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 [modified: boot/vmlinuz-3.11.0-12-generic] 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 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1407 F pulseaudio CurrentDmesg: Date: Tue Nov 5 00:36:56 2013 HibernationDevice: RESUME=UUID=0986bf55-0186-4118-93df-522940ac63d0 InstallationDate: Installed on 2013-11-05 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Vostro 3560 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=51a4484a-5bd4-4d0e-acb5-6a826989ba8d ro rootdelay=60 quiet splash initcall_debug 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 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: X44 dmi.board.name: 05GV6H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X44 dmi.modalias: dmi:bvnDellInc.:bvrX44:bd08/03/2012:svnDellInc.:pnVostro3560:pvrX44:rvnDellInc.:rn05GV6H:rvrA00:cvnDellInc.:ct8:cvrX44: dmi.product.name: Vostro 3560 dmi.product.version: X44 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/
[Kernel-packages] [Bug 997883] Re: Intel WiFi Link 5300 doesn't work with kernel 3.2.0.24
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
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/997883
Title:
Intel WiFi Link 5300 doesn't work with kernel 3.2.0.24
Status in “linux” package in Ubuntu:
Expired
Bug description:
A couple of days ago, I upgraded to not only Ubuntu 12.04 LTS, but also from
kernel 3.0.0.17 to 3.2.0.24. This worked correctly at my friends house just
fine. However, I flew home and now my computer cannot ping or connect to the
internet at all. (Both of these were wireless networks). I switched to my
windows partition of my computer, and it connected to the internet no issues.
So the problem was isolated to ubuntu.
My computer is a Dell Studio XPS which is about 3 years old now. The
WiFi adapter is an Intel WiFi Link 5300. This will play into the game
later.
After a couple of hours searching around and talking to people, a few
things were unearthed. First, that a dhcp lease was obtained from the
router. Other than that, the computer could not communicate with
anything on the network (no ping even). All of the /etc/hosts,
/etc/hostname, and /etc/network/interfaces stuff was in order. There
was nothing abnormal in any of the logs that were checked.
With the help of some googling, someone pointed out that it sounded
remarkably like what was happening in this thread. DHCP lease acquired, no
transmission after that.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/420678
This was for the Intel Wifi Link 5300. That is my adapter. It must be
conflicting between the G and N standards from the Linksys WRT310N router here
at home, and it must not have had that conflict at the previous house I was at.
I booted into a previous version of the kernel (3.0.0.17) and there was no
issue (that's actually how I'm typing this right now). I performed a "sudo
apt-get --reinstall install linux-image-3.2.0-24-generic" to make sure the
kernel was correct, and the error repeated after a restart. Once again, I
booted into the previous version of the kernel, and it worked correctly.
If there is any differing conclusion about what happened, feel free to
let me know!
Just to verify the version claim, my "lsb_release -rd" output is:
Description: Ubuntu 12.04 LTS
Release: 12.04
Here is the "lspci -vvxxx" result for the network adapter:
04:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300
Subsystem: Intel Corporation Device 1121
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-
Kernel driver in use: iwlagn
Kernel modules: iwlagn
00: 86 80 35 42 06 01 10 00 00 00 80 02 10 00 00 00
10: 04 00 00 f8 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 86 80 21 11
30: 00 00 00 00 c8 00 00 00 00 00 00 00 0a 01 00 00
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: adam 1833 F pulseaudio
/dev/snd/controlC0: adam 1833 F pulseaudio
/dev/snd/pcmC0D0p: adam 1833 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfc40 irq 47'
Mixer name : 'IDT 92HD73C1X5'
Components : 'HDA:111d7675,10280272,00100103'
Controls : 16
Simple ctrls : 10
Card1.Amixer.info:
Card hw:1 'HDMI'/'HDA ATI HDMI at 0xcfeec000 irq 48'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100100'
Controls : 4
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
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
MachineType: Dell Inc. Studio XPS 1640
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-17-generic
root=UUID=F4FE6024FE5FDE04 loop=/ubuntu/disks/root.disk ro quiet splash
vt.handoff=7
ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22
RelatedPackageVersions:
linux-restricted-modules-3.0.0-17-generic N/A
linux-backports-modules-3.0.0-17-generic N/A
linux-firmware1.79
[Kernel-packages] [Bug 1201671] Re: [HP Pavilion dv6-4008tx Entertainment Notebook PC] Wireless key light constantly flashing when connected
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1201671 Title: [HP Pavilion dv6-4008tx Entertainment Notebook PC] Wireless key light constantly flashing when connected Status in “linux” package in Ubuntu: Expired Bug description: Hi, The wireless light at FN+F12 is alternating between white and orange all the time when connected to a wireless network. When disconnected but wireless is enabled it stays white and when wireless is disabled it turns orange. This behaviour doesn't seem correct. Suggested behaviour: When wireless is enabled (i.e. connected/disconnected but enabled) it should stay white. When wireless is disabled it should stay orange. Cheers, ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.10.0-2-generic 3.10.0-2.11 ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: z 2187 F pulseaudio /dev/snd/controlC0: z 2187 F pulseaudio /dev/snd/pcmC0D0p: z 2187 F...m pulseaudio Date: Tue Jul 16 13:32:21 2013 HibernationDevice: RESUME=UUID=da95f1e0-c928-4bd6-98d8-e76486710b08 InstallationDate: Installed on 2013-07-13 (2 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC MarkForUpload: True ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.10.0-2-generic root=/dev/mapper/ubuntu--vg-root ro video.use_bios_initial_backlight=0 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.10.0-2-generic N/A linux-backports-modules-3.10.0-2-generic N/A linux-firmware1.112 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-07-16 (0 days ago) dmi.bios.date: 07/26/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.0F dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1594 dmi.board.vendor: Hewlett-Packard dmi.board.version: 91.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.0F:bd07/26/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058420242B2620100:rvnHewlett-Packard:rn1594:rvr91.36:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 058420242B2620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1201671/+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 1221060] Re: [TOSHIBA Portege R830-17C] suspend/resume failure [non-free: zfs zunicode zavl zcommon znvpair]
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1221060 Title: [TOSHIBA Portege R830-17C] suspend/resume failure [non-free: zfs zunicode zavl zcommon znvpair] Status in “linux” package in Ubuntu: Expired Bug description: After resume I was unable to login, including text consoles. After type of username no password prompt was shown. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-2-generic 3.11.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jkohoute 2690 F pulseaudio /dev/snd/controlC1: jkohoute 2690 F pulseaudio Date: Thu Sep 5 09:42:18 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=8c2bc05b-0680-45f6-b42c-e5c038285ace InstallationDate: Installed on 2013-06-21 (75 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130618) InterpreterPath: /usr/bin/python3.3 MachineType: TOSHIBA Portege R830 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic root=UUID=9b88150f-1752-4a7e-b5ab-7204261e69c3 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.11.0-2-generic N/A linux-backports-modules-3.11.0-2-generic N/A linux-firmware1.113 SourcePackage: linux Title: [TOSHIBA Portege R830] suspend/resume failure [non-free: zfs zunicode zavl zcommon znvpair] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/08/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 4.10 dmi.board.asset.tag: 00 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion4.10:bd01/08/2013:svnTOSHIBA:pnPortegeR830:pvrPT321E-08502W0V:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: Portege R830 dmi.product.version: PT321E-08502W0V dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1221060/+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 1221251] Re: [LENOVO 3626WNQ] suspend/resume failure
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1221251 Title: [LENOVO 3626WNQ] suspend/resume failure Status in “linux” package in Ubuntu: Expired Bug description: closed while in docking station. Pressed the eject button to remove usb devices, etc. Removed. Tried turning it on. nothing happened. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-4-generic 3.11.0-4.9 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: surak 1685 F pulseaudio Date: Thu Sep 5 14:51:38 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=9c143982-caef-43f4-bf00-fcb14a9089fb InstallationDate: Installed on 2013-07-04 (62 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130703) InterpreterPath: /usr/bin/python3.3 MachineType: LENOVO 3626WNQ MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic root=UUID=1f266836-f1f1-4f6e-a4fa-45361a64cd0a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.11.0-4-generic N/A linux-backports-modules-3.11.0-4-generic N/A linux-firmware1.113 SourcePackage: linux Title: [LENOVO 3626WNQ] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 6QET68WW (1.38 ) dmi.board.name: 3626WNQ 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:bvr6QET68WW(1.38):bd12/01/2011:svnLENOVO:pn3626WNQ:pvrThinkPadX201:rvnLENOVO:rn3626WNQ:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3626WNQ dmi.product.version: ThinkPad X201 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1221251/+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 1219320] Re: Ubuntu 13.10 crash
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1219320 Title: Ubuntu 13.10 crash Status in “linux” package in Ubuntu: Expired Bug description: While I was watching a Youtube video the system crashed. The screen fall back to text mode and the last second of the sound of the video was playing repeatedly. I'm on a 64bit system. --- ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: norbs 2189 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=5850760a-629d-48f4-9f5f-fff2e0b35c01 InstallationDate: Installed on 2013-08-30 (5 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130829) MachineType: Acer AO725 MarkForUpload: True Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic root=UUID=edf495c4-4cb9-41fc-ad5c-c02c3c15aa22 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 RelatedPackageVersions: linux-restricted-modules-3.11.0-4-generic N/A linux-backports-modules-3.11.0-4-generic N/A linux-firmware1.113 Tags: saucy Uname: Linux 3.11.0-4-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 04/18/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: ZA10_BZ dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd04/18/2013:svnAcer:pnAO725:pvrV1.07:rvnAcer:rnZA10_BZ:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: AO725 dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1219320/+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 1219621] Re: [Apple Inc. MacBook4, 1] suspend/resume failure [non-free: wl]
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1219621 Title: [Apple Inc. MacBook4,1] suspend/resume failure [non-free: wl] Status in “linux” package in Ubuntu: Expired Bug description: Black screen, uses up battery instead of suspend. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-4-generic 3.11.0-4.9 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luke 2970 F pulseaudio /dev/snd/pcmC0D0p: luke 2970 F...m pulseaudio CurrentDmesg: [ 55.167462] sky2 :03:00.0 eth0: enabling interface [ 55.167776] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 55.169284] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 61.840036] init: plymouth-stop pre-start process (1752) terminated with status 1 Date: Sun Sep 1 20:09:09 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2012-03-07 (544 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) InterpreterPath: /usr/bin/python3.3 MachineType: Apple Inc. MacBook4,1 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic root=UUID=d7cc0fdf-615d-40c5-9ed5-f42b9add ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.11.0-4-generic N/A linux-backports-modules-3.11.0-4-generic N/A linux-firmware1.113 SourcePackage: linux StagingDrivers: zram Title: [Apple Inc. MacBook4,1] suspend/resume failure [non-free: wl] UpgradeStatus: Upgraded to saucy on 2013-08-27 (6 days ago) UserGroups: dmi.bios.date: 02/09/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB41.88Z.00C1.B00.0802091535 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F22788A9 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22788A9 dmi.modalias: dmi:bvnAppleInc.:bvrMB41.88Z.00C1.B00.0802091535:bd02/09/08:svnAppleInc.:pnMacBook4,1:pvr1.0:rvnAppleInc.:rnMac-F22788A9:rvrPVT:cvnAppleInc.:ct2:cvrMac-F22788A9: dmi.product.name: MacBook4,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/linux/+bug/1219621/+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 1221067] Re: Fn+F2 (switch wireless) doesn't work on Asus 1015e
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1221067 Title: Fn+F2 (switch wireless) doesn't work on Asus 1015e Status in “linux” package in Ubuntu: Expired Bug description: Using: * Asus 1015e (French, Windows 8 pre-installed) * SecureBoot disabled from UEFI * Ubuntu Saucy nightly image (from Aug 27th) on USB stick * Starting Live (didn't install Ubuntu) When I hit Fn+F2 (which shows a switch wireless icon), nothing happens. I expected it to turn off wifi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1221067/+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 1219954] Re: Slow startup of lightDM in Ubuntu 13.04
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1219954 Title: Slow startup of lightDM in Ubuntu 13.04 Status in “linux” package in Ubuntu: Expired Bug description: When starting up the PC, the tty1 login prompt is shown for ca. one minute, before the Unity login screen is shown. First is was once every x startups, now it is almost always. This problem is introduced on an upgrade of Ubuntu to 13.04 from 12.10. Suggested workarounds tried, but failed: - choosing different driver for grafical card; - adding sleep 2 before start lightDM ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ronald 2031 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Sep 2 20:49:03 2013 HibernationDevice: RESUME=UUID=2a70a086-21af-4490-aa96-d78caf67d7dd InstallationDate: Installed on 2012-05-18 (472 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. EP41-UD3L MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=c7741f68-6fd3-4478-9dd7-b797ecad1955 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.8.0-29-generic N/A linux-backports-modules-3.8.0-29-generic N/A linux-firmware1.106 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to raring on 2013-05-05 (120 days ago) dmi.bios.date: 04/03/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: EP41-UD3L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd04/03/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP41-UD3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP41-UD3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: EP41-UD3L dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1219954/+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 1213887] Re: Bridge does not work i ubuntu 12.04 - kernel 3.5.0-37
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1213887 Title: Bridge does not work i ubuntu 12.04 - kernel 3.5.0-37 Status in “linux” package in Ubuntu: Expired Bug description: We are using ganeti on a HP ProLiant DL380p Gen8. We are running kvm as virtualization. Then enable a new ganeti instance, the kernel will make a new network interface (TAPx). After a minut or two, the instance starts to drop packages. Ping is sufficent. We have tried on different network cards on the server, and all fails. Changing to different kernels has not solved the problems. Currently we have 6 ProLiant DL380p Gen7 running on the same configuration with no problems at all. Regards Søren Laursen ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-37-generic 3.5.0-37.58~precise1 ProcVersionSignature: Ubuntu 3.5.0-37.58~precise1-generic 3.5.7.16 Uname: Linux 3.5.0-37-generic x86_64 AlsaDevices: total 0 crw-rw---T 1 root audio 116, 1 Aug 16 11:08 seq crw-rw---T 1 root audio 116, 33 Aug 16 11:08 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory Date: Mon Aug 19 13:05:33 2013 HibernationDevice: RESUME=UUID=eb9606b5-5c67-4221-82c4-13d0f88abba9 InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MachineType: HP ProLiant DL380p Gen8 MarkForUpload: True PciMultimedia: ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-37-generic root=UUID=3a6a448e-8900-4eb5-b203-f5ddd1fbe28d ro RelatedPackageVersions: linux-restricted-modules-3.5.0-37-generic N/A linux-backports-modules-3.5.0-37-generic N/A linux-firmware1.79.6 RfKill: Error: [Errno 2] No such file or directory SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2012 dmi.bios.vendor: HP dmi.bios.version: P70 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP70:bd12/14/2012:svnHP:pnProLiantDL380pGen8:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380p Gen8 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213887/+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 1221052] Re: linux-headers-3.2.0-41
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1221052 Title: linux-headers-3.2.0-41 Status in “linux” package in Ubuntu: Expired Bug description: E:O pacote linux-headers-3.2.0-41 precisa ser reinstalado, mas não foi possível encontrar um arquivo para o mesmo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1221052/+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 1218970] Re: [ASUSTeK COMPUTER INC. UX51VZH] suspend/resume failure
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1218970 Title: [ASUSTeK COMPUTER INC. UX51VZH] suspend/resume failure Status in “linux” package in Ubuntu: Expired Bug description: My Zenbook does not like to suspend/sleep. I tried to Maybe this helps; /var/log/pm-suspend.log says: /etc/pm/sleep.d/10_unattended-upgrades-hibernate suspend suspend: success. Running hook /usr/lib/pm-utils/sleep.d/60_wpa_supplicant suspend suspend: Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory and /usr/lib/pm-utils/sleep.d/95led suspend suspend: not applicable. Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: Kernel modesetting video driver detected, not using quirks. --- ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-4-generic 3.11.0-4.9 [modified: boot/vmlinuz-3.11.0-4-generic] ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anskaal2093 F pulseaudio /dev/snd/controlC0: anskaal2093 F pulseaudio Date: Fri Aug 30 00:43:37 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=6137de52-88e4-4135-b3fd-3911575839e6 InstallationDate: Installed on 2013-08-29 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130829) InterpreterPath: /usr/bin/python3.3 MachineType: ASUSTeK COMPUTER INC. UX51VZH MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic.efi.signed root=/dev/mapper/isw_bccdhjieij_Volume0p2 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.11.0-4-generic N/A linux-backports-modules-3.11.0-4-generic N/A linux-firmware1.113 SourcePackage: linux Title: [ASUSTeK COMPUTER INC. UX51VZH] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/06/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX51VZH.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX51VZH dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX51VZH.206:bd03/06/2013:svnASUSTeKCOMPUTERINC.:pnUX51VZH:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX51VZH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX51VZH dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1218970/+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 1205843] Re: e1000e ethernet not working on raring 13.04 (nor in precise 12.04)
Hello Jorge, did you try to reinstall the e1000e driver on a new kernel you installed? (The latest driver version is 2.5.4) According to https://answers.launchpad.net/ubuntu-certification/+question/238609 You might need to rebuild the driver once you upgrade the 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/1205843 Title: e1000e ethernet not working on raring 13.04 (nor in precise 12.04) Status in “linux” package in Ubuntu: Confirmed Bug description: After an upgrade in precise, the ethernet connection started failing. My desktop is a Dell Inspiron 530s with e1000e 82562V-2 Ethernet interface. The problem is that it seems to connect and receive the dhcp but the ethernet fails all the time. Syslog: Jul 28 13:33:16 oro-1 kernel: [ 2031.340121] e1000e: eth0 NIC Link is Down Jul 28 13:33:17 oro-1 NetworkManager[869]: (eth0): carrier now ON (device state 100) Jul 28 13:33:17 oro-1 kernel: [ 2032.996765] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx Jul 28 13:33:17 oro-1 kernel: [ 2032.996772] e1000e :00:19.0 eth0: 10/100 speed: disabling TSO Jul 28 13:33:18 oro-1 kernel: [ 2033.968121] e1000e: eth0 NIC Link is Down Jul 28 13:33:18 oro-1 NetworkManager[869]: (eth0): carrier now OFF (device state 100, deferring action for 4 seconds) Jul 28 13:33:20 oro-1 NetworkManager[869]: (eth0): carrier now ON (device state 100) Jul 28 13:33:20 oro-1 kernel: [ 2035.820755] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx Jul 28 13:33:20 oro-1 kernel: [ 2035.820763] e1000e :00:19.0 eth0: 10/100 speed: disabling TSO Jul 28 13:33:22 oro-1 NetworkManager[869]: (eth0): carrier now OFF (device state 100, deferring action for 4 seconds) Jul 28 13:33:22 oro-1 kernel: [ 2037.592124] e1000e: eth0 NIC Link is Down Jul 28 13:33:24 oro-1 NetworkManager[869]: (eth0): carrier now ON (device state 100) Jul 28 13:33:24 oro-1 kernel: [ 2039.288783] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx Jul 28 13:33:24 oro-1 kernel: [ 2039.288790] e1000e :00:19.0 eth0: 10/100 speed: disabling TSO Jul 28 13:33:25 oro-1 NetworkManager[869]: (eth0): carrier now OFF (device state 100, deferring action for 4 seconds) Jul 28 13:33:25 oro-1 kernel: [ 2040.504122] e1000e: eth0 NIC Link is Down Jul 28 13:33:27 oro-1 NetworkManager[869]: (eth0): carrier now ON (device state 100) Jul 28 13:33:27 oro-1 kernel: [ 2042.196762] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx Jul 28 13:33:27 oro-1 kernel: [ 2042.196770] e1000e :00:19.0 eth0: 10/100 speed: disabling TSO Jul 28 13:33:27 oro-1 kernel: [ 2042.704125] e1000e: eth0 NIC Link is Down Jul 28 13:33:28 oro-1 NetworkManager[869]: (eth0): carrier now OFF (device state 100, deferring action for 4 seconds) Jul 28 13:33:29 oro-1 NetworkManager[869]: (eth0): carrier now ON (device state 100) Jul 28 13:33:29 oro-1 kernel: [ 2044.344766] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx Jul 28 13:33:29 oro-1 kernel: [ 2044.344774] e1000e :00:19.0 eth0: 10/100 speed: disabling TSO dmesg: [ 2013.376189] e1000e: eth0 NIC Link is Down [ 2014.968757] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx [ 2014.968765] e1000e :00:19.0 eth0: 10/100 speed: disabling TSO [ 2018.504123] e1000e: eth0 NIC Link is Down [ 2020.124759] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx [ 2020.124767] e1000e :00:19.0 eth0: 10/100 speed: disabling TSO [ 2022.188128] e1000e: eth0 NIC Link is Down [ 2023.796761] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx [ 2023.796769] e1000e :00:19.0 eth0: 10/100 speed: disabling TSO [ 2023.840120] e1000e: eth0 NIC Link is Down [ 2025.468762] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx [ 2025.468770] e1000e :00:19.0 eth0: 10/100 speed: disabling TSO [ 2026.860120] e1000e: eth0 NIC Link is Down [ 2028.512768] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx [ 2028.512775] e1000e :00:19.0 eth0: 10/100 speed: disabling TSO [ 2031.340121] e1000e: eth0 NIC Link is Down [ 2032.996765] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx [ 2032.996772] e1000e :00:19.0 eth0: 10/100 speed: disabling TSO [ 2033.968121] e1000e: eth0 NIC Link is Down lshw *-network description: Ethernet interface product: 82562V-2 10/100 Network Connection vendor: Intel Corporation physical id: 19 bus info: pci@:00:19.0 logical name: eth0 version: 02 serial: 00:1d:09:81:db:c4 capacity: 100Mbit/s width: 32 bits clock: 33MHz capabilities: pm msi bus_master cap_list ethernet physical
[Kernel-packages] [Bug 1239572] Re: TCP Tail Loss Probe problem in Ubuntu 13.10 kernel
This patch has already been merged into the 3.12 upstream. From: Joseph Salisbury To: chenttu...@yahoo.com Sent: Wednesday, October 16, 2013 12:41 AM Subject: [Bug 1239572] Re: TCP Tail Loss Probe problem in Ubuntu 13.10 kernel The patch: "tcp: fix incorrect ca_state in tail loss probe" has not made it into Linus's tree as of yet. When it does, we can perform a cherry- pick into Saucy. If it is cc'd to stable, it will automatically be included in Saucy through the normal stable release update process. Are you able to reproduce this bug easily? If so, was it introduced in the v3.10 kernel and not exist in earlier kernels? If that is the case, we might be able to revert the commit that introduced this, until the fix lands upstream. ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Tags added: bot-stop-nagging ** Tags added: kernel-da-key -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1239572 Title: TCP Tail Loss Probe problem in Ubuntu 13.10 kernel Status in “linux” package in Ubuntu: Triaged Bug description: Bug of type net/tcp in linux kernel >3.10 Please Refer to http://article.gmane.org/gmane.linux.network/286793/match= AND https://bugzilla.redhat.com/show_bug.cgi?id=989251 We are planing to widely deploy Ubuntu 13.10 in our frontend server for advanced TCP enhancement in the latest linux kernel and Tail Loss Probe is considered as one of the most important features, so do please fix this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1239572/+subscriptions ** Bug watch added: Red Hat Bugzilla #989251 https://bugzilla.redhat.com/show_bug.cgi?id=989251 -- 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/1239572 Title: TCP Tail Loss Probe problem in Ubuntu 13.10 kernel Status in “linux” package in Ubuntu: Triaged Bug description: Bug of type net/tcp in linux kernel >3.10 Please Refer to http://article.gmane.org/gmane.linux.network/286793/match= AND https://bugzilla.redhat.com/show_bug.cgi?id=989251 We are planing to widely deploy Ubuntu 13.10 in our frontend server for advanced TCP enhancement in the latest linux kernel and Tail Loss Probe is considered as one of the most important features, so do please fix this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1239572/+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 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically
Henning, the fix is already in Saucy. You may have a different problem. -- 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/1094744 Title: MS Sculpt Touch Mouse needs to be re-paired periodically Status in GNOME Bluetooth: Fix Released Status in “bluez” package in Ubuntu: Confirmed Status in “gnome-bluetooth” package in Ubuntu: Fix Released Status in “bluez” source package in Precise: Confirmed Status in “gnome-bluetooth” source package in Precise: Fix Committed Status in “bluez” source package in Quantal: Confirmed Status in “gnome-bluetooth” source package in Quantal: Fix Committed Status in “bluez” source package in Raring: Confirmed Status in “gnome-bluetooth” source package in Raring: Fix Committed Status in “bluez” package in Fedora: Unknown Bug description: [Impact] The patch makes Microsoft Wedge/Sculpt Touch mice stay connected. [Test Case] Get a Microsoft Wedge/Sculpt Touch mouse, pair it, restart session, watch it automatically re-pair. [Regression Potential] Little. The patched piece of XML is only relevant to hardware having the same ID. When you don't use the mouse for a long enough time, the mouse disconnects and won't reconnect. I have to go into bluetooth settings, remove it, and re-pair it. 1) ~ % lsb_release -rd Description: Ubuntu 12.04.1 LTS Release: 12.04 2) ~ % apt-cache policy bluez bluez: Installed: 4.98-2ubuntu7 Candidate: 4.98-2ubuntu7 Version table: *** 4.98-2ubuntu7 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status 3) I expected the mouse to reconnect automatically, or at least after I try to reconnect manually through the bluetooth settings. 4) I have to re-pair the mouse in order to use it again. Turning the mouse off and on doesn't work either. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+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 1248004] 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/1248004 Title: Webcam LED is always on Status in “linux” package in Ubuntu: Confirmed Bug description: When starting the computer and login, the Webcam LED is turned on and stays on forever. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-42-generic 3.5.0-42.65 ProcVersionSignature: Ubuntu 3.5.0-42.65-generic 3.5.7.21 Uname: Linux 3.5.0-42-generic i686 ApportVersion: 2.6.1-0ubuntu13 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: flo2286 F xfce4-volumed flo2307 F pulseaudio Date: Tue Nov 5 02:10:23 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=7de79b1e-4bd3-4b1c-8033-89e1eae5b4f7 InstallationDate: Installed on 2013-01-07 (301 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1) MachineType: Dell Inc. XPS M1530 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-42-generic root=UUID=c0807425-3882-42a4-8ce1-8a6fc5a75c69 ro noquiet nosplash mmccore.removable=0 mmc_core.removable=0 usbcore.autosuspend=0 RelatedPackageVersions: linux-restricted-modules-3.5.0-42-generic N/A linux-backports-modules-3.5.0-42-generic N/A linux-firmware1.95.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0D501F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn0D501F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248004/+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 1237541] Re: Artigo A1100 Fails to Boot/Install with 13.10 Beta 2
penalvch, Done. dirk-kraft, Both the LiveUSB and the Server install failed at the same place with the network disconnected. -- 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/1237541 Title: Artigo A1100 Fails to Boot/Install with 13.10 Beta 2 Status in “linux” package in Ubuntu: Incomplete Bug description: I have an Artigo A1100 mini-computer, which ran Ubuntu 13.04 fine. Spec Sheet here: http://www.viaembedded.com/en/products/DatasheetPreview/1351/11620/VIA_ARTiGO_A1100_datasheet_v110126.pdf.html I attempted a clean install of 13.10 Beta 2 via a live USB, and found the Live CD, Desktop Install, and Server install to all fail to load properly. The Live CD / Desktop install failed to boot, and froze at the point shown in the attachment. The cursor continued to blink, but made no progress beyond that. The Server Install becomes unresponsive at the language selection screen - the first dialog of the text installer. This appears to be a regression, as 13.04 and 12.04 both install and run fine on this hardware. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu2881 F lxpanel CRDA: Error: [Errno 2] No such file or directory CasperVersion: 1.330 CurrentDmesg: [ 55.323671] Velocity is AUTO mode [ 55.495503] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 55.512512] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 57.109225] eth0: Link auto-negotiation speed 100M bps full duplex [ 57.109702] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready DistroRelease: Ubuntu 13.04 IwConfig: eth0 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 RfKill: Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/04/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. 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.:bvr080015:bd03/04/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237541/+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 1248004] [NEW] Webcam LED is always on
Public bug reported: When starting the computer and login, the Webcam LED is turned on and stays on forever. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-42-generic 3.5.0-42.65 ProcVersionSignature: Ubuntu 3.5.0-42.65-generic 3.5.7.21 Uname: Linux 3.5.0-42-generic i686 ApportVersion: 2.6.1-0ubuntu13 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: flo2286 F xfce4-volumed flo2307 F pulseaudio Date: Tue Nov 5 02:10:23 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=7de79b1e-4bd3-4b1c-8033-89e1eae5b4f7 InstallationDate: Installed on 2013-01-07 (301 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1) MachineType: Dell Inc. XPS M1530 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-42-generic root=UUID=c0807425-3882-42a4-8ce1-8a6fc5a75c69 ro noquiet nosplash mmccore.removable=0 mmc_core.removable=0 usbcore.autosuspend=0 RelatedPackageVersions: linux-restricted-modules-3.5.0-42-generic N/A linux-backports-modules-3.5.0-42-generic N/A linux-firmware1.95.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0D501F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn0D501F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1530 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal -- 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/1248004 Title: Webcam LED is always on Status in “linux” package in Ubuntu: New Bug description: When starting the computer and login, the Webcam LED is turned on and stays on forever. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-42-generic 3.5.0-42.65 ProcVersionSignature: Ubuntu 3.5.0-42.65-generic 3.5.7.21 Uname: Linux 3.5.0-42-generic i686 ApportVersion: 2.6.1-0ubuntu13 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: flo2286 F xfce4-volumed flo2307 F pulseaudio Date: Tue Nov 5 02:10:23 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=7de79b1e-4bd3-4b1c-8033-89e1eae5b4f7 InstallationDate: Installed on 2013-01-07 (301 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1) MachineType: Dell Inc. XPS M1530 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-42-generic root=UUID=c0807425-3882-42a4-8ce1-8a6fc5a75c69 ro noquiet nosplash mmccore.removable=0 mmc_core.removable=0 usbcore.autosuspend=0 RelatedPackageVersions: linux-restricted-modules-3.5.0-42-generic N/A linux-backports-modules-3.5.0-42-generic N/A linux-firmware1.95.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0D501F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn0D501F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248004/+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 1210393] Re: MAAS ipmi fails on OCPv3 Roadrunner
BMC is detected on the network, just cannot establish connection via link: ipmiping 10.193.37.122 ipmiping 10.193.37.122 (10.193.37.122) response received from 10.193.37.122: rq_seq=32 response received from 10.193.37.122: rq_seq=33 response received from 10.193.37.122: rq_seq=34 response received from 10.193.37.122: rq_seq=35 response received from 10.193.37.122: rq_seq=36 -- 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/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: Incomplete Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+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 1210393] Re: MAAS ipmi fails on OCPv3 Roadrunner
Troubleshooting steps: modprobe ipmi_msghandler modprobe ipmi_devintf modprobe ipmi_si Will enable the bmc device parameters to be changed locally and eliminate the write back errors, something I feel the Saucy ephemeral images are not doing. Secondly, trying to enable link authentication fails to set: ipmitool lan set 1 auth ADMIN MD5,PASSWORD Channel link access still states: User ID : 4 User Name : admin Fixed Name : No Access Available : call-in / callback Link Authentication : disabled IPMI Messaging : enabled Also, setting link access for channel 1 fails: sudo ipmitool lan set 1 access on Set Channel Access for channel 1 failed: Unknown (0x83) -- 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/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: Incomplete Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+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 1247906] Re: Repeatable oops qxl_enc_commit
Answer to 1st question 1st; I've got this on both a saucy and a trusty guest, so not new in Trusty, but Raring doesn't seem to exhibit it Linux saucy 3.12.0-031200-generic #201311031935 SMP Mon Nov 4 00:36:54 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux still oopsing - slightly different backtrace and it took three vt changes to trigger it: [ 66.200441] Kernel BUG at a01114e0 [verbose debug info unavailable] [ 66.200445] invalid opcode: [#1] SMP [ 66.200457] Modules linked in: bnep rfcomm bluetooth qxl ttm drm_kms_helper ppdev drm psmouse i2c_piix4 serio_raw virtio_balloon virtio_console lp microcode mac_hid parport_pc parport floppy [ 66.200462] CPU: 0 PID: 1033 Comm: Xorg Not tainted 3.12.0-031200-generic #201311031935 [ 66.200464] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 [ 66.200465] task: 880078c02f60 ti: 880078cd2000 task.ti: 880078cd2000 [ 66.200475] RIP: 0010:[] [] qxl_send_monitors_config+0x150/0x160 [qxl] [ 66.200477] RSP: 0018:880078cd3698 EFLAGS: 00010246 [ 66.200478] RAX: c93d8000 RBX: 88007a5c RCX: a011aeb8 [ 66.200480] RDX: a011a640 RSI: a011b769 RDI: 88007a5c [ 66.200481] RBP: 880078cd36b8 R08: R09: [ 66.200483] R10: 0001 R11: R12: c93d2004 [ 66.200484] R13: 88007986fd68 R14: 88007c39e000 R15: 8800795af700 [ 66.200487] FS: 7fb411855980() GS:88007fc0() knlGS: [ 66.200489] CS: 0010 DS: ES: CR0: 80050033 [ 66.200490] CR2: 7fa4549980e0 CR3: 7957a000 CR4: 06f0 [ 66.200502] Stack: [ 66.200506] 880079863000 88007c39e420 88007a5c [ 66.200509] 880078cd3718 a01117f0 0300 0400 [ 66.200512] 88000300 8801 88007a5c [ 66.200513] Call Trace: [ 66.200521] [] qxl_write_monitors_config_for_encoder+0x130/0x210 [qxl] [ 66.200527] [] qxl_enc_commit+0x1b/0x40 [qxl] [ 66.200534] [] drm_crtc_helper_set_mode+0x431/0x5c0 [drm_kms_helper] [ 66.200542] [] drm_crtc_helper_set_config+0x8fa/0xb70 [drm_kms_helper] [ 66.200561] [] drm_mode_set_config_internal+0x5c/0xe0 [drm] [ 66.200567] [] drm_fb_helper_set_par+0x66/0xe0 [drm_kms_helper] [ 66.200572] [] fb_set_var+0x283/0x3a0 [ 66.200578] [] ? check_preempt_wakeup+0x165/0x260 [ 66.200581] [] ? update_curr+0x141/0x200 [ 66.200585] [] ? __switch_to_xtra+0x14e/0x180 [ 66.200589] [] fbcon_blank+0x1e4/0x2d0 [ 66.200594] [] do_unblank_screen.part.17+0xa0/0x180 [ 66.200597] [] do_unblank_screen+0x48/0x80 [ 66.200601] [] complete_change_console+0x65/0xf0 [ 66.200605] [] vt_ioctl+0x112c/0x11d0 [ 66.200608] [] ? __wake_up+0x53/0x70 [ 66.200613] [] tty_ioctl+0x298/0x8f0 [ 66.200618] [] ? mntput_no_expire+0x49/0x160 [ 66.200621] [] ? mntput+0x24/0x40 [ 66.200626] [] ? __fput+0x189/0x240 [ 66.200630] [] do_vfs_ioctl+0x7a/0x2e0 [ 66.200634] [] ? fput+0xe/0x10 [ 66.200638] [] ? task_work_run+0xac/0xe0 [ 66.200641] [] SyS_ioctl+0x91/0xb0 [ 66.200647] [] ? do_notify_resume+0xc7/0xd0 [ 66.200651] [] system_call_fastpath+0x1a/0x1f [ 66.200680] Code: 4e 08 eb d7 0f 1f 80 00 00 00 00 48 c7 c2 d0 a3 11 a0 48 c7 c6 6e b8 11 a0 31 c0 e8 ab 42 00 00 48 83 c4 18 5b 5d c3 31 d2 eb b0 <0f> 0b 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 [ 66.200687] RIP [] qxl_send_monitors_config+0x150/0x160 [qxl] [ 66.200688] RSP [ 66.200691] ---[ end trace ff52923c1ba99f25 ]--- ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1247906 Title: Repeatable oops qxl_enc_commit Status in “linux” package in Ubuntu: Confirmed Bug description: I've got an Ubuntu Trusty guest running under a Fedora 20-pre-beta, the guest oops reliably. To repeat: Setup KVM with the guest configured with QXL graphics, Install openssh-server in the guest Boot it and then send a ctrl-alt-f1 Problem 1 : Corrupt graphics instead of console Now ssh into the guest Send a ctrl-alt-f2 Problem 2 : dmesg on the guest to see backtrace. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-1-generic 3.12.0-1.3 ProcVersionSignature: Ubuntu 3.12.0-1.3-generic 3.12.0-rc7 Uname: Linux 3.12.0-1-generic x86_64 ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Nov 4 17:08:38 2013 HibernationDevice: RES
[Kernel-packages] [Bug 1223851] Re: High CPU load after resuming on Samsung NP550P5C in BIOS mode
Just to make sure I went back to 3.11.0 and I couldn't reproduce the issue. I think installing the Intel MEI drivers on Windows (this is a dual boot box) did something. Weird. -- 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/1223851 Title: High CPU load after resuming on Samsung NP550P5C in BIOS mode Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Triaged Bug description: Description of problem: After I resume the system and plug something in one of the machine's USB3 ports (it doesn't happen if I plug the same device on a USB2 port), the CPU load raises to 50%, with one particular process with the highest load: 4 root 20 0 000 R 50.1 0.0 1:43.63 kworker/0:0 The problem seems to be caused by too many ACPI interrupts: root@ubuntu:~# grep -r . /sys/firmware/acpi/interrupts/ /sys/firmware/acpi/interrupts/sci:12554973 /sys/firmware/acpi/interrupts/error: 0 /sys/firmware/acpi/interrupts/gpe00: 0 invalid /sys/firmware/acpi/interrupts/gpe01: 0 invalid /sys/firmware/acpi/interrupts/gpe02: 0 enabled /sys/firmware/acpi/interrupts/gpe03: 0 disabled /sys/firmware/acpi/interrupts/gpe04: 0 disabled /sys/firmware/acpi/interrupts/gpe05: 0 disabled /sys/firmware/acpi/interrupts/gpe06: 0 enabled /sys/firmware/acpi/interrupts/gpe07: 0 invalid /sys/firmware/acpi/interrupts/gpe08: 0 invalid /sys/firmware/acpi/interrupts/gpe09: 0 disabled /sys/firmware/acpi/interrupts/gpe10: 0 invalid /sys/firmware/acpi/interrupts/gpe11: 0 invalid /sys/firmware/acpi/interrupts/gpe12: 0 invalid /sys/firmware/acpi/interrupts/gpe13: 0 invalid /sys/firmware/acpi/interrupts/gpe14: 0 invalid /sys/firmware/acpi/interrupts/gpe15: 0 invalid /sys/firmware/acpi/interrupts/gpe16: 0 invalid /sys/firmware/acpi/interrupts/gpe0A: 0 invalid /sys/firmware/acpi/interrupts/gpe17:1504 enabled /sys/firmware/acpi/interrupts/gpe0B: 0 disabled /sys/firmware/acpi/interrupts/gpe18: 0 invalid /sys/firmware/acpi/interrupts/gpe0C: 0 disabled /sys/firmware/acpi/interrupts/gpe19: 0 invalid /sys/firmware/acpi/interrupts/gpe0D:12553562 enabled /sys/firmware/acpi/interrupts/gpe0E: 0 disabled /sys/firmware/acpi/interrupts/gpe20: 0 disabled /sys/firmware/acpi/interrupts/gpe0F: 0 invalid /sys/firmware/acpi/interrupts/gpe21: 0 invalid /sys/firmware/acpi/interrupts/gpe22: 0 invalid /sys/firmware/acpi/interrupts/gpe23: 0 invalid /sys/firmware/acpi/interrupts/gpe24: 0 invalid /sys/firmware/acpi/interrupts/gpe25: 0 disabled /sys/firmware/acpi/interrupts/gpe26: 0 invalid /sys/firmware/acpi/interrupts/gpe1A: 0 invalid /sys/firmware/acpi/interrupts/gpe27: 0 invalid /sys/firmware/acpi/interrupts/gpe1B: 0 invalid /sys/firmware/acpi/interrupts/gpe28: 0 invalid /sys/firmware/acpi/interrupts/gpe1C: 0 invalid /sys/firmware/acpi/interrupts/gpe29: 0 invalid /sys/firmware/acpi/interrupts/gpe1D: 0 invalid /sys/firmware/acpi/interrupts/gpe1E: 0 enabled /sys/firmware/acpi/interrupts/gpe30: 0 invalid /sys/firmware/acpi/interrupts/gpe1F: 0 enabled /sys/firmware/acpi/interrupts/gpe31: 0 invalid /sys/firmware/acpi/interrupts/gpe32: 0 invalid /sys/firmware/acpi/interrupts/gpe33: 0 invalid /sys/firmware/acpi/interrupts/gpe34: 0 invalid /sys/firmware/acpi/interrupts/gpe35: 0 invalid /sys/firmware/acpi/interrupts/gpe36: 0 invalid /sys/firmware/acpi/interrupts/gpe2A: 0 invalid /sys/firmware/acpi/interrupts/gpe37: 0 invalid /sys/firmware/acpi/interrupts/gpe2B: 0 invalid /sys/firmware/acpi/interrupts/gpe38: 0 invalid /sys/firmware/acpi/interrupts/gpe2C: 0 invalid /sys/firmware/acpi/interrupts/gpe39: 0 invalid /sys/firmware/acpi/interrupts/gpe2D: 0 invalid /sys/firmware/acpi/interrupts/gpe2E: 0 invalid /sys/firmware/acpi/interrupts/gpe2F: 0 invalid /sys/firmware/acpi/interrupts/gpe3A: 0 invalid /sys/firmware/acpi/interrupts/gpe3B: 0 invalid /sys/firmware/acpi/interrupts/gpe3C: 0 invalid /sys/firmware/acpi/interrupts/gpe3D: 0 invalid /sys/firmware/acpi/interrupts/gpe3E: 0 invalid /sys/firmware/acpi/interrupts/gpe3F: 0 invalid /sys/firmware/acpi/interrupts/sci_not: 0 /sys/firmware/acpi/interrupts/ff_pmtimer: 0 invalid /sys/firmware/acpi/interrupts/ff_rt_clk: 0 disabled /sys/firmware/acpi/interrupts/gpe_all:12556159 /sys/firmware/acpi/interrupts/ff_gbl_lock: 0 disab
[Kernel-packages] [Bug 1246664] Re: "Buffer I/O error on device zram0, logical block 515067"
Ok, after more than one hour and a half, with lots of heavy programs started at same time no issue, no freeze on the P4. On the T60 with the 3.2.0-55 generic and zram-config in use the session was exiting really fast and sending the user back to the login screen. With the 3.2.0-56 generic no such issue happened, and no I/O buffer error in either of the two machines. Thanks a lot to the people who fixed it! I'll be looking forward to get it from the repositories. (I don't have systems installed for other architectures to test on). Regards, Mélodie -- 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/1246664 Title: "Buffer I/O error on device zram0, logical block 515067" Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Precise: Fix Committed Status in “linux” source package in Saucy: Fix Released Bug description: SRU Justification: Commit 12a7ad3 "zram: avoid access beyond the zram device" introduced a regression where valid_io_request() checks if request end coincides with disksize (end equals bound). It fails if we attempt to read beyond the bound. Impact: Several errors will be logged if, for example, zram-config is installed: [ 14.666280] zram: module is from the staging directory, the quality is unknown, you have been warned. [ 14.667040] zram: Creating 1 devices ... [ 14.830355] Buffer I/O error on device zram0, logical block 62411 [ 14.830375] Buffer I/O error on device zram0, logical block 62411 [ 14.830598] Buffer I/O error on device zram0, logical block 62411 [ 14.830621] Buffer I/O error on device zram0, logical block 62411 [ 14.878597] Adding 249644k swap on /dev/zram0. Priority:5 extents:1 across:249644k SS Fix: Commit 75c7caf5a052ffd8db3312fa7864ee2d142890c4 "zram: allow request end to coincide with disksize" fixes the issue by correcting the test in valid_io_request() function. Testcase: I was able to reproduce the issue by simply installing zram-config in a precise box. = This is a duplicate of #1217189, but for some reason neither @oibaf nor me can reopen it. It is in "fix released" state, but the problem is at most partially solved. It seems that the bug no longer causes lockups (described in another bug: #1215513), but is still present (as I get error messages on boot screen and after $ dmesg | grep zram). If someone has enough privileges to reopen 1217189 for "linux (ubuntu)" (I don't know about raring, but no one complains, so it is probably ok), and remove this bug (maybe merging this message to the comments in 1217189), I would be really grateful. Ubuntu 12.04.3 LTS Kernel Linux 3.2.0-56-generic-pae (the problem was first observed in 53 and since 54 there are no lockups). --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: damian 2771 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf830 irq 47' Mixer name : 'Realtek ALC268' Components : 'HDA:10ec0268,10280275,0013' Controls : 16 Simple ctrls : 9 DistroRelease: Ubuntu 12.04 MachineType: Dell Inc. Vostro1710 MarkForUpload: True NonfreeKernelModules: nvidia wl Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-56-generic-pae root=UUID=bfe81069-1c35-4ccc-a23a-33528ac81877 ro selinux=1 security=selinux quiet splash ProcVersionSignature: Ubuntu 3.2.0-56.86-generic-pae 3.2.51 RelatedPackageVersions: linux-restricted-modules-3.2.0-56-generic-pae N/A linux-backports-modules-3.2.0-56-generic-pae N/A linux-firmware1.79.7 StagingDrivers: zram Tags: precise running-unity staging Uname: Linux 3.2.0-56-generic-pae i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo dmi.bios.date: 09/09/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0X805C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnDellInc.:bvrA09:bd09/09/2008:svnDellInc.:pnVostro1710:pvrNull:rvnDellInc.:rn0X805C:rvr:cvnDellInc.:ct8:cvrN/A: dmi.product.name: Vostro1710 dmi.prod
[Kernel-packages] [Bug 1036456] Re: [Fujitsu LIFEBOOK AH530] BUG: soft lockup - CPU#0 stuck for 22s!
The latest development release (13.10) is now installed.
Thus far, after 35 suspend/resumes (25 using the drop down menu and 10 using
lid closure), suspend/resume is working just fine. That's not a thorough test
yet, after my experience with 12.04.
However, internet connectivity (wireless and ethernet) is not working at all.
It works with other computers in the household and with 12.04. Therefore, it
must be a problem with the development release.
Immediately after attempting wireless connectivity, I was told there was a
system problem and was finally presented with the following dialog:
Problem in wpasupplicant
The problem cannot be reported:
You have some obsolete package versions installed.
Please upgrade the following package and check if the problem still occurs:
apt-utils, dbus, debianutils, dpkg, gcc-4.8 base, ifupdown, initramfs-
tools, initramfs-tools-bin, libapt-inst1.5, libapt-pkg4.12, libc6,
libdbus-1-3, libgcc1, libpam-systemd, libpci3, libstdc++6, libsystemd-
login0, libudev1, libxctables10, lsb-base, mountall, multiarch-support,
pciutils, systemd-services, tar, tsdata, udev, upstart
I cannot cannot send automatically gathered debug information, if
necessary, or download these packages without an internet connection.
The most I can do is count the suspend/resumes and the failures.
Additionally, please tell me, in a clear manner, if there is anything
else that can be done to troubleshoot the suspend/resume problem. The
instructions, to this point, have been rather unclear. In the above
message, for example, I cannot determine whether you would like the
upstream kernel for 13.10 or 12.04 tested. This is also an issue with
some of the instructions at your web site.
--
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/1036456
Title:
[Fujitsu LIFEBOOK AH530] BUG: soft lockup - CPU#0 stuck for 22s!
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
60% of the time computer will not resume from suspend when lid is opened.
Display begins with ACPI errors and Device PNP0C0D:00 errors and
then a cycle of text after the "BUG: soft lockup - CPU#0 stuck for 22s!"
error.
Additionally,
yelp process consumed 100% of each of the 4 processors in sequence for a long
time after this event last occured.
Terminal will not take administrator's password at all - the cursur won't
move. Therefore, "sudo lspci -vnvn > lspci-vnvn.log" could not be done at all.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-29-generic-pae 3.2.0-29.46
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic-pae 3.2.24
Uname: Linux 3.2.0-29-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu12
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: lfeq 1628 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf070 irq 44'
Mixer name : 'Intel IbexPeak HDMI'
Components : 'HDA:10ec0269,10cf0200,0014
HDA:80862804,80860101,0010'
Controls : 23
Simple ctrls : 10
Date: Mon Aug 13 20:28:09 2012
HibernationDevice: RESUME=UUID=306aab40-d7f0-4c2f-95bb-bab8bcb6da07
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386
(20120423)
MachineType: FUJITSU LIFEBOOK AH530
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-29-generic-pae
root=UUID=5e649b17-1a99-456b-bd08-ef7aec3da8c1 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-29-generic-pae N/A
linux-backports-modules-3.2.0-29-generic-pae N/A
linux-firmware1.79
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/19/2010
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.16
dmi.board.name: FJNBB06
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias:
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.16:bd08/19/2010:svnFUJITSU:pnLIFEBOOKAH530:pvr:rvnFUJITSU:rnFJNBB06:rvr:cvnFUJITSU:ct10:cvr:
dmi.product.name: LIFEBOOK AH530
dmi.sys.vendor: FUJITSU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1036456/+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 1247819] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1247819 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1247819 Title: Kernel Panic-Not Syncing Status in “linux” package in Ubuntu: Incomplete Bug description: I have downloaded Ubantu 13.04 and I am trying to boot it in my Asus E Notebook with a bootable pendrive.When I change the boot priority to the removable disk,An error message shows up saying Kernel Panic-Not Syncing.What should I do? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1247819/+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 1247710] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1247710 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1247710 Title: CIFS kernel sockets do not belong to any UID Status in “linux” package in Ubuntu: Incomplete Bug description: I have a Kubuntu which uses a customized UFW to do egress filtering. The default policy of the OUTPUT chain is REJECT, which means that NO process is allowed to send packets until I have explicitly allowed it. To allow output packets on a per-user base, I use the "-m owner --uid-owner username" match of iptables. Unfortunately, CIFS mounting kept failing even though I've allowed root to send packets. So I experimented with the UIDs to find out which UID the kernel uses for CIFS. As "--uid-owner" supports user ranges, I was able to determine that the packets do not belong to ANY valid UID: The following rule makes CIFS mounts succeed: -A ufw-before-output -m owner --socket-exists ! --uid-owner 0-4294967294 -o eth0 --dest 192.168.1.1 -p tcp --dport 445 -j ACCEPT The inversion of the UID-owner match in the same rule makes them NOT succeed: -A ufw-before-output -m owner --socket-exists ! --uid-owner 0-4294967294 -o eth0 --dest 192.168.1.1 -p tcp --dport 445 -j ACCEPT Incrementing the maximal UID of the range by 1 to 4294967295 makes iptables complain that the UID is out of range. So the range of ALL UIDs available in the Linux kernel is indeed 0-4294967294, and CIFS mounts only work if we assume the packets to be OUT of that range. So the packets are missing an UID. Distro = Kubuntu 12.10 amd64 Kernel package = linux-image-3.5.0-42-generic Kernel package version = 3.5.0-42.65 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1247710/+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 1247667] Re: alx module problem (wakeonlan)
Thanks. I just downloaded kernel 3.12, from http://kernel.ubuntu.com /~kernel-ppa/mainline/v3.12-saucy/, and rebooted my machine with this new kernel. Verified that I am running the new kernel. However, I still do not see that the wol capability of my card is recognized by ethtool. So, I will go ahead and do what you tell me to do below, regarding the tag and the status. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1247667 Title: alx module problem (wakeonlan) Status in “linux” package in Ubuntu: Confirmed Bug description: I am using 13.10 (saucy) on my new laptop---a Lenovo laptop (Y510P). It appears that the alx module that loads the network card (08:00.0 Ethernet controller: Qualcomm Atheros QCA8171 Gigabit Ethernet (rev 10)) might have some problem. The wakonlan functionality is important for me. However, when I do ethtool eth0 I do not get any encouraging information on wakeonlan. There just isn't any information printed out regarding wakeonlan. However, when booted to the Windows 7 partition, it is shown that this network card does support wakeonlan, and wakeonlan does work when I put the computer to sleep and then send the magic packet to it. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gweon 2649 F pulseaudio gweon 2907 F panel-5-mixer /dev/snd/controlC0: gweon 2649 F pulseaudio gweon 2907 F panel-5-mixer DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fbec5182-7824-41fa-97f4-6af1f60bc15a InstallationDate: Installed on 2011-04-30 (918 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) MachineType: LENOVO 20217 MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=bb8e49fb-46b6-4a7d-bfd4-8a12679411d7 ro quiet splash video.use_bios_initial_backlight=0 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 i686 UpgradeStatus: Upgraded to saucy on 2013-10-31 (3 days ago) UserGroups: adm admin cdrom dialout griffin lpadmin plugdev sambashare vboxusers www-data dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN35WW(V1.10) dmi.board.asset.tag: YB00831328 dmi.board.name: 20217 dmi.board.vendor: LENOVO dmi.board.version: 3193STD dmi.chassis.asset.tag: YB00831328 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN35WW(V1.10):bd07/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rn20217:rvr3193STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gweon 2649 F pulseaudio gweon 2907 F panel-5-mixer /dev/snd/controlC0: gweon 2649 F pulseaudio gweon 2907 F panel-5-mixer DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fbec5182-7824-41fa-97f4-6af1f60bc15a InstallationDate: Installed on 2011-04-30 (918 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) MachineType: LENOVO 20217 MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=bb8e49fb-46b6-4a7d-bfd4-8a12679411d7 ro quiet splash video.use_bios_initial_backlight=0 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied 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-31 (3 days ago) UserGroups: dmi.bio
[Kernel-packages] [Bug 1247819] Re: Kernel Panic-Not Syncing
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/1247819 Title: Kernel Panic-Not Syncing Status in “linux” package in Ubuntu: New Bug description: I have downloaded Ubantu 13.04 and I am trying to boot it in my Asus E Notebook with a bootable pendrive.When I change the boot priority to the removable disk,An error message shows up saying Kernel Panic-Not Syncing.What should I do? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1247819/+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 1247710] Re: CIFS kernel sockets do not belong to any UID
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/1247710 Title: CIFS kernel sockets do not belong to any UID Status in “linux” package in Ubuntu: New Bug description: I have a Kubuntu which uses a customized UFW to do egress filtering. The default policy of the OUTPUT chain is REJECT, which means that NO process is allowed to send packets until I have explicitly allowed it. To allow output packets on a per-user base, I use the "-m owner --uid-owner username" match of iptables. Unfortunately, CIFS mounting kept failing even though I've allowed root to send packets. So I experimented with the UIDs to find out which UID the kernel uses for CIFS. As "--uid-owner" supports user ranges, I was able to determine that the packets do not belong to ANY valid UID: The following rule makes CIFS mounts succeed: -A ufw-before-output -m owner --socket-exists ! --uid-owner 0-4294967294 -o eth0 --dest 192.168.1.1 -p tcp --dport 445 -j ACCEPT The inversion of the UID-owner match in the same rule makes them NOT succeed: -A ufw-before-output -m owner --socket-exists ! --uid-owner 0-4294967294 -o eth0 --dest 192.168.1.1 -p tcp --dport 445 -j ACCEPT Incrementing the maximal UID of the range by 1 to 4294967295 makes iptables complain that the UID is out of range. So the range of ALL UIDs available in the Linux kernel is indeed 0-4294967294, and CIFS mounts only work if we assume the packets to be OUT of that range. So the packets are missing an UID. Distro = Kubuntu 12.10 amd64 Kernel package = linux-image-3.5.0-42-generic Kernel package version = 3.5.0-42.65 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1247710/+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 1210393] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1210393 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: Incomplete Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+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 1243904] Re: Internal keyboard doesn't work in 13.10
Added the tag "kernel-fixed-upstream" and changed to "confirmed". Do I have to repeat the command "order apport-collect xxx"? or everything is correct? Thanks in advance and please bear whith me. I repeat I am a basic user in 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/1243904 Title: Internal keyboard doesn't work in 13.10 Status in “linux” package in Ubuntu: Confirmed Bug description: Hello. I updated from 13.04 to 13.10 but the keyboard did not work. I tried doing a fresh install but the keyboard did not work with the live cd. In 13.04 all works correctly My laptop is a lg p1 express dual Thank you very much --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jac2262 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=3b3ffa91-078a-4731-b078-8ba3ebafc542 InstallationDate: Installed on 2013-04-28 (190 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: LG Electronics P1-J273B MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=fd418822-b188-423d-a734-75f80a75f92c ro quiet splash 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 StagingDrivers: et131x Tags: saucy staging Uname: Linux 3.11.0-12-generic i686 UpgradeStatus: Upgraded to saucy on 2013-10-20 (15 days ago) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo dmi.bios.date: 04/20/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: RKYWSF10 dmi.board.name: ROCKY dmi.board.vendor: LG Electronics dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF10:bd04/20/2006:svnLGElectronics:pnP1-J273B:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A: dmi.product.name: P1-J273B dmi.product.version: Not Applicable dmi.sys.vendor: LG Electronics --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-04-28 (190 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MarkForUpload: True Package: linux (not installed) Tags: saucy Uname: Linux 3.12.0-031200-generic i686 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to saucy on 2013-10-20 (15 days ago) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1243904/+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 1210393] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1210393/+attachment/3900224/+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/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: New Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+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 1210393] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1210393/+attachment/3900225/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: New Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+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 1210393] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1210393/+attachment/3900221/+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/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: New Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+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 1210393] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1210393/+attachment/3900223/+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/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: New Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+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 1210393] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1210393/+attachment/3900222/+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/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: New Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+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 1210393] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1210393/+attachment/3900214/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: New Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+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 1210393] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1210393/+attachment/3900216/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: New Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+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 1210393] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1210393/+attachment/3900220/+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/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: New Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+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 1210393] Re: MAAS ipmi fails on OCPv3 Roadrunner
ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2918 F pulseaudio CasperVersion: 1.336 DistroRelease: Ubuntu 13.10 IwConfig: eth0 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130916) MachineType: empty empty MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-7-generic N/A linux-backports-modules-3.11.0-7-generic N/A linux-firmware1.114 RfKill: Tags: saucy Uname: Linux 3.11.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: S8237 dmi.board.vendor: TYAN dmi.board.version: empty dmi.chassis.asset.tag: empty dmi.chassis.type: 28 dmi.chassis.vendor: empty dmi.chassis.version: empty dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd03/04/2013:svnempty:pnempty:pvrempty:rvnTYAN:rnS8237:rvrempty:cvnempty:ct28:cvrempty: dmi.product.name: empty dmi.product.version: empty dmi.sys.vendor: empty ** Tags added: apport-collected 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/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: New Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+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 1210393] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1210393/+attachment/3900215/+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/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: New Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+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 1210393] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1210393/+attachment/3900218/+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/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: New Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+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 1210393] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1210393/+attachment/3900217/+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/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: New Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+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 1210393] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1210393/+attachment/3900219/+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/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: New Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+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 1243904] Re: Internal keyboard doesn't work in 13.10
ok. I'm sorry. I have a mistake. Now, using the lastest upstream kernel. I'm going to repeat the -order apport-collect 1243904- Buff. It's so hard for me. I can't repeat the "apport-collect xxx". there is a warning like this: It appears you are currently running a mainline kernel. It would be better to report this bug upstream at http://bugzilla.kernel.org/ so that the upstream kernel developers are aware of the issue. If you'd still like to file a bug against the Ubuntu kernel, please boot with an official Ubuntu kernel and re-file. But, the internal keyboard still does not work. ** Description changed: Hello. I updated from 13.04 to 13.10 but the keyboard did not work. I tried doing a fresh install but the keyboard did not work with the live cd. In 13.04 all works correctly My laptop is a lg p1 express dual Thank you very much --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jac2262 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=3b3ffa91-078a-4731-b078-8ba3ebafc542 InstallationDate: Installed on 2013-04-28 (190 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: LG Electronics P1-J273B MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=fd418822-b188-423d-a734-75f80a75f92c ro quiet splash 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 StagingDrivers: et131x Tags: saucy staging Uname: Linux 3.11.0-12-generic i686 UpgradeStatus: Upgraded to saucy on 2013-10-20 (15 days ago) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo dmi.bios.date: 04/20/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: RKYWSF10 dmi.board.name: ROCKY dmi.board.vendor: LG Electronics dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF10:bd04/20/2006:svnLGElectronics:pnP1-J273B:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A: dmi.product.name: P1-J273B dmi.product.version: Not Applicable dmi.sys.vendor: LG Electronics + --- + ApportVersion: 2.12.5-0ubuntu2.1 + Architecture: i386 + DistroRelease: Ubuntu 13.10 + InstallationDate: Installed on 2013-04-28 (190 days ago) + InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) + MarkForUpload: True + Package: linux (not installed) + Tags: saucy + Uname: Linux 3.12.0-031200-generic i686 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: Upgraded to saucy on 2013-10-20 (15 days ago) + UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo -- 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/1243904 Title: Internal keyboard doesn't work in 13.10 Status in “linux” package in Ubuntu: Confirmed Bug description: Hello. I updated from 13.04 to 13.10 but the keyboard did not work. I tried doing a fresh install but the keyboard did not work with the live cd. In 13.04 all works correctly My laptop is a lg p1 express dual Thank you very much --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jac2262 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=3b3ffa91-078a-4731-b078-8ba3ebafc542 InstallationDate: Installed on 2013-04-28 (190 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: LG Electronics P1-J273B MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=fd418822-b188-423d-a734-75f80a75f92c ro quiet splash 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 StagingDrivers: et131x Tags: saucy staging Uname: Linux 3.11.0-12-generic i686 UpgradeStatus: Upgraded to saucy on 2013-10-20 (15 days ago) UserGroups: adm cdrom dip lpadmin nopasswdlogin pl
[Kernel-packages] [Bug 1243904] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1243904/+attachment/3900207/+files/ProcEnviron.txt ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1243904 Title: Internal keyboard doesn't work in 13.10 Status in “linux” package in Ubuntu: Confirmed Bug description: Hello. I updated from 13.04 to 13.10 but the keyboard did not work. I tried doing a fresh install but the keyboard did not work with the live cd. In 13.04 all works correctly My laptop is a lg p1 express dual Thank you very much --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jac2262 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=3b3ffa91-078a-4731-b078-8ba3ebafc542 InstallationDate: Installed on 2013-04-28 (190 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: LG Electronics P1-J273B MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=fd418822-b188-423d-a734-75f80a75f92c ro quiet splash 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 StagingDrivers: et131x Tags: saucy staging Uname: Linux 3.11.0-12-generic i686 UpgradeStatus: Upgraded to saucy on 2013-10-20 (15 days ago) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo dmi.bios.date: 04/20/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: RKYWSF10 dmi.board.name: ROCKY dmi.board.vendor: LG Electronics dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF10:bd04/20/2006:svnLGElectronics:pnP1-J273B:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A: dmi.product.name: P1-J273B dmi.product.version: Not Applicable dmi.sys.vendor: LG Electronics --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-04-28 (190 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MarkForUpload: True Package: linux (not installed) Tags: saucy Uname: Linux 3.12.0-031200-generic i686 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to saucy on 2013-10-20 (15 days ago) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1243904/+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 1210393] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1210393 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: Incomplete Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+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 1210393] Re: MAAS ipmi fails on OCPv3 Roadrunner
** Also affects: linux Importance: Undecided Status: New ** Project changed: linux => ubuntu ** Package changed: ubuntu => linux (Ubuntu) ** No longer affects: freeipmi (Ubuntu) -- 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/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: Incomplete Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+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 1223851] Re: High CPU load after resuming on Samsung NP550P5C in BIOS mode
3.11.7 works fine too -- 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/1223851 Title: High CPU load after resuming on Samsung NP550P5C in BIOS mode Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Triaged Bug description: Description of problem: After I resume the system and plug something in one of the machine's USB3 ports (it doesn't happen if I plug the same device on a USB2 port), the CPU load raises to 50%, with one particular process with the highest load: 4 root 20 0 000 R 50.1 0.0 1:43.63 kworker/0:0 The problem seems to be caused by too many ACPI interrupts: root@ubuntu:~# grep -r . /sys/firmware/acpi/interrupts/ /sys/firmware/acpi/interrupts/sci:12554973 /sys/firmware/acpi/interrupts/error: 0 /sys/firmware/acpi/interrupts/gpe00: 0 invalid /sys/firmware/acpi/interrupts/gpe01: 0 invalid /sys/firmware/acpi/interrupts/gpe02: 0 enabled /sys/firmware/acpi/interrupts/gpe03: 0 disabled /sys/firmware/acpi/interrupts/gpe04: 0 disabled /sys/firmware/acpi/interrupts/gpe05: 0 disabled /sys/firmware/acpi/interrupts/gpe06: 0 enabled /sys/firmware/acpi/interrupts/gpe07: 0 invalid /sys/firmware/acpi/interrupts/gpe08: 0 invalid /sys/firmware/acpi/interrupts/gpe09: 0 disabled /sys/firmware/acpi/interrupts/gpe10: 0 invalid /sys/firmware/acpi/interrupts/gpe11: 0 invalid /sys/firmware/acpi/interrupts/gpe12: 0 invalid /sys/firmware/acpi/interrupts/gpe13: 0 invalid /sys/firmware/acpi/interrupts/gpe14: 0 invalid /sys/firmware/acpi/interrupts/gpe15: 0 invalid /sys/firmware/acpi/interrupts/gpe16: 0 invalid /sys/firmware/acpi/interrupts/gpe0A: 0 invalid /sys/firmware/acpi/interrupts/gpe17:1504 enabled /sys/firmware/acpi/interrupts/gpe0B: 0 disabled /sys/firmware/acpi/interrupts/gpe18: 0 invalid /sys/firmware/acpi/interrupts/gpe0C: 0 disabled /sys/firmware/acpi/interrupts/gpe19: 0 invalid /sys/firmware/acpi/interrupts/gpe0D:12553562 enabled /sys/firmware/acpi/interrupts/gpe0E: 0 disabled /sys/firmware/acpi/interrupts/gpe20: 0 disabled /sys/firmware/acpi/interrupts/gpe0F: 0 invalid /sys/firmware/acpi/interrupts/gpe21: 0 invalid /sys/firmware/acpi/interrupts/gpe22: 0 invalid /sys/firmware/acpi/interrupts/gpe23: 0 invalid /sys/firmware/acpi/interrupts/gpe24: 0 invalid /sys/firmware/acpi/interrupts/gpe25: 0 disabled /sys/firmware/acpi/interrupts/gpe26: 0 invalid /sys/firmware/acpi/interrupts/gpe1A: 0 invalid /sys/firmware/acpi/interrupts/gpe27: 0 invalid /sys/firmware/acpi/interrupts/gpe1B: 0 invalid /sys/firmware/acpi/interrupts/gpe28: 0 invalid /sys/firmware/acpi/interrupts/gpe1C: 0 invalid /sys/firmware/acpi/interrupts/gpe29: 0 invalid /sys/firmware/acpi/interrupts/gpe1D: 0 invalid /sys/firmware/acpi/interrupts/gpe1E: 0 enabled /sys/firmware/acpi/interrupts/gpe30: 0 invalid /sys/firmware/acpi/interrupts/gpe1F: 0 enabled /sys/firmware/acpi/interrupts/gpe31: 0 invalid /sys/firmware/acpi/interrupts/gpe32: 0 invalid /sys/firmware/acpi/interrupts/gpe33: 0 invalid /sys/firmware/acpi/interrupts/gpe34: 0 invalid /sys/firmware/acpi/interrupts/gpe35: 0 invalid /sys/firmware/acpi/interrupts/gpe36: 0 invalid /sys/firmware/acpi/interrupts/gpe2A: 0 invalid /sys/firmware/acpi/interrupts/gpe37: 0 invalid /sys/firmware/acpi/interrupts/gpe2B: 0 invalid /sys/firmware/acpi/interrupts/gpe38: 0 invalid /sys/firmware/acpi/interrupts/gpe2C: 0 invalid /sys/firmware/acpi/interrupts/gpe39: 0 invalid /sys/firmware/acpi/interrupts/gpe2D: 0 invalid /sys/firmware/acpi/interrupts/gpe2E: 0 invalid /sys/firmware/acpi/interrupts/gpe2F: 0 invalid /sys/firmware/acpi/interrupts/gpe3A: 0 invalid /sys/firmware/acpi/interrupts/gpe3B: 0 invalid /sys/firmware/acpi/interrupts/gpe3C: 0 invalid /sys/firmware/acpi/interrupts/gpe3D: 0 invalid /sys/firmware/acpi/interrupts/gpe3E: 0 invalid /sys/firmware/acpi/interrupts/gpe3F: 0 invalid /sys/firmware/acpi/interrupts/sci_not: 0 /sys/firmware/acpi/interrupts/ff_pmtimer: 0 invalid /sys/firmware/acpi/interrupts/ff_rt_clk: 0 disabled /sys/firmware/acpi/interrupts/gpe_all:12556159 /sys/firmware/acpi/interrupts/ff_gbl_lock: 0 disabled /sys/firmware/acpi/interrupts/ff_pwr_btn: 0 enabled /sys/firmware/acpi/interrupts/ff_slp_btn: 0 invalid I can mitigate the prob
[Kernel-packages] [Bug 1237336] Re: linux-image-3.11.0-12-generic doesn't boot
The last test kernel has the bug. -- 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= 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 1240882] Re: [drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1
I confirm this. Since Kubuntu 12.10 at least. Then 13.04 and now 13.10. Every time I want to use the nouveau driver but I end up trashing it just because of that. The dev team did an awesome job in the past year, the driver works on everything I use, is SMOOTH and FAST, flawless to me. But because it cannot support resuming fro suspend to RAM, I trash it and install the drivers from nvidia, which sometimes cause issues elsewhere. Nothing's perfect but the nouveau driver in Kubuntu 13.10 is at perfection to me if it wasn't for that. This is a mandatory requirement for me, if it can't suspend and resume in an acceptable way, then it's a total no use for me. I have an nvidia GeFroce 8400GS, does the same thing with my other GeForce 8600GT. I wish we can fix this! -- 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/1240882 Title: [drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1 Status in “linux” package in Ubuntu: Confirmed Bug description: Error log Oct 17 19:38:00 nanak-P570WM kernel: [ 20.031700] [drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1 Oct 17 19:38:00 nanak-P570WM kernel: [ 20.034197] [drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1 Oct 17 19:38:00 nanak-P570WM kernel: [ 20.036692] [drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1 Oct 17 19:38:00 nanak-P570WM kernel: [ 20.039192] [drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1 Oct 17 19:38:00 nanak-P570WM kernel: [ 20.199700] [drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1 Oct 17 19:38:01 nanak-P570WM kernel: [ 20.202196] [drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1 Oct 17 19:38:01 nanak-P570WM kernel: [ 20.204688] [drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1 Oct 17 19:38:01 nanak-P570WM kernel: [ 20.207185] [drm:drm_edid_block_valid] *ERROR* EDID has major version 0, instead of 1 Oct 17 19:38:01 nanak-P570WM kernel: [ 20.262737] nouveau E[ PBUS][:01:00.0] MMIO write of 0x FAULT at 0x418880 [ IBUS ] Oct 17 19:38:01 nanak-P570WM kernel: [ 20.262846] nouveau E[ PIBUS][:01:00.0] GPC0: 0x419eb4 0xbadf1000 (0x3800820c) Oct 17 19:38:01 nanak-P570WM kernel: [ 20.262872] nouveau E[ PIBUS][:01:00.0] GPC1: 0x419eb4 0xbadf1000 (0x3800820c) Oct 17 19:38:01 nanak-P570WM kernel: [ 20.262905] nouveau E[ PIBUS][:01:00.0] GPC2: 0x419eb4 0xbadf1000 (0x3800820c) Oct 17 19:38:01 nanak-P570WM kernel: [ 20.262912] nouveau E[ PIBUS][:01:00.0] GPC3: 0x419eb4 0xbadf1000 (0x3800820c) Oct 17 19:38:01 nanak-P570WM kernel: [ 20.262927] nouveau E[ PBUS][:01:00.0] MMIO write of 0xc000 FAULT at 0x518824 [ IBUS ] --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-09-05 (42 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130904) MarkForUpload: True Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: saucy Uname: Linux 3.12.0-999-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1240882/+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 1210393] [NEW] MAAS ipmi fails on OCPv3 Roadrunner
You have been subscribed to a public bug: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. ** Affects: maas Importance: High Status: Triaged ** Affects: opencompute Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: freeipmi (Ubuntu) Importance: Undecided Status: New -- MAAS ipmi fails on OCPv3 Roadrunner https://bugs.launchpad.net/bugs/1210393 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1246664] Re: "Buffer I/O error on device zram0, logical block 515067"
Hi, Why installing zram-config in the Ubuntu Builder Synaptic module there has been this message: E: zram-config: subprocess installed post-installation script returned error exit status 1 In the current system itself all is working fine so far (more than one hour running). No zram Buffer I/O error to be reported by dmesg either: $ dmesg | grep zram [ 25.841182] zram: module is from the staging directory, the quality is unknown, you have been warned. [ 25.841620] zram: Creating 2 devices ... [ 26.494074] Adding 772040k swap on /dev/zram0. Priority:5 extents:1 across:772040k SS [ 26.500818] Adding 772040k swap on /dev/zram1. Priority:5 extents:1 across:772040k SS $ -- 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/1246664 Title: "Buffer I/O error on device zram0, logical block 515067" Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Precise: Fix Committed Status in “linux” source package in Saucy: Fix Released Bug description: SRU Justification: Commit 12a7ad3 "zram: avoid access beyond the zram device" introduced a regression where valid_io_request() checks if request end coincides with disksize (end equals bound). It fails if we attempt to read beyond the bound. Impact: Several errors will be logged if, for example, zram-config is installed: [ 14.666280] zram: module is from the staging directory, the quality is unknown, you have been warned. [ 14.667040] zram: Creating 1 devices ... [ 14.830355] Buffer I/O error on device zram0, logical block 62411 [ 14.830375] Buffer I/O error on device zram0, logical block 62411 [ 14.830598] Buffer I/O error on device zram0, logical block 62411 [ 14.830621] Buffer I/O error on device zram0, logical block 62411 [ 14.878597] Adding 249644k swap on /dev/zram0. Priority:5 extents:1 across:249644k SS Fix: Commit 75c7caf5a052ffd8db3312fa7864ee2d142890c4 "zram: allow request end to coincide with disksize" fixes the issue by correcting the test in valid_io_request() function. Testcase: I was able to reproduce the issue by simply installing zram-config in a precise box. = This is a duplicate of #1217189, but for some reason neither @oibaf nor me can reopen it. It is in "fix released" state, but the problem is at most partially solved. It seems that the bug no longer causes lockups (described in another bug: #1215513), but is still present (as I get error messages on boot screen and after $ dmesg | grep zram). If someone has enough privileges to reopen 1217189 for "linux (ubuntu)" (I don't know about raring, but no one complains, so it is probably ok), and remove this bug (maybe merging this message to the comments in 1217189), I would be really grateful. Ubuntu 12.04.3 LTS Kernel Linux 3.2.0-56-generic-pae (the problem was first observed in 53 and since 54 there are no lockups). --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: damian 2771 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf830 irq 47' Mixer name : 'Realtek ALC268' Components : 'HDA:10ec0268,10280275,0013' Controls : 16 Simple ctrls : 9 DistroRelease: Ubuntu 12.04 MachineType: Dell Inc. Vostro1710 MarkForUpload: True NonfreeKernelModules: nvidia wl Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-56-generic-pae root=UUID=bfe81069-1c35-4ccc-a23a-33528ac81877 ro selinux=1 security=selinux quiet splash ProcVersionSignature: Ubuntu 3.2.0-56.86-generic-pae 3.2.51 RelatedPackageVersions: linux-restricted-modules-3.2.0-56-generic-pae N/A linux-backports-modules-3.2.0-56-generic-pae N/A linux-firmware1.79.7 StagingDrivers: zram Tags: precise running-unity staging Uname: Linux 3.2.0-56-generic-pae i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo dmi.bios.date: 09/09/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0X805C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnDellInc.
[Kernel-packages] [Bug 1247967] Re: nvidia optimus chipset disabled when running on battery, even in discrete mode
The nvidia kernel module source fails to build against the 3.12 mainline kernel (see attached build failure). Unable to complete the requested testing due to this. ** Tags added: kernel-unable-to-test-upstream ** Attachment added: "nvidia module build failure" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1247967/+attachment/3900206/+files/make.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/1247967 Title: nvidia optimus chipset disabled when running on battery, even in discrete mode Status in “linux” package in Ubuntu: Incomplete Bug description: It appears that under 3.11.0-13, the Nvidia Optimus GPU is disabled when running on battery even if the chipset is set to discrete mode in the BIOS. When running without AC power under the 3.11 kernel, lspci -v gives the following: http://paste.ubuntu.com/6360607/ With AC power under 3.11, the same command gives: http://paste.ubuntu.com/6360613/ If the system is booted into the 3.11 kernel with AC power connected, it can be removed and the GPU continues to function normally. I have not tested suspend and resume under the 3.11 kernel (with or without AC power). This same configuration worked properly under Raring (13.04). Booting with the 3.8 kernel and the same nvidia module version used in the above 3.11 kernel tests results in the previously experienced (correct, working) behavior. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D8p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC29', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Nov 4 12:31:48 2013 HibernationDevice: RESUME=UUID=1fbfa69c-fb52-4aee-ad35-9c523aa14974 InstallationDate: Installed on 2009-12-21 (1414 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MachineType: LENOVO 2436CTO MarkForUpload: True ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-32-generic root=/dev/mapper/ssd-root ro vga=792 splash nox2apic crashkernel=384M-2G:64M,2G-:128M quiet splash RelatedPackageVersions: linux-restricted-modules-3.8.0-32-generic N/A linux-backports-modules-3.8.0-32-generic N/A linux-firmware1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-11-04 (0 days ago) dmi.bios.date: 08/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G5ET94WW (2.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ET94WW(2.54):bd08/12/2013:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2436CTO 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/1247967/+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 1247967] Re: nvidia optimus chipset disabled when running on battery, even in discrete mode
If someone can point me to steps for bisecting the changes between the 3.8 and 3.11 kernels, I'd be happy to do the leg work. -- 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/1247967 Title: nvidia optimus chipset disabled when running on battery, even in discrete mode Status in “linux” package in Ubuntu: Incomplete Bug description: It appears that under 3.11.0-13, the Nvidia Optimus GPU is disabled when running on battery even if the chipset is set to discrete mode in the BIOS. When running without AC power under the 3.11 kernel, lspci -v gives the following: http://paste.ubuntu.com/6360607/ With AC power under 3.11, the same command gives: http://paste.ubuntu.com/6360613/ If the system is booted into the 3.11 kernel with AC power connected, it can be removed and the GPU continues to function normally. I have not tested suspend and resume under the 3.11 kernel (with or without AC power). This same configuration worked properly under Raring (13.04). Booting with the 3.8 kernel and the same nvidia module version used in the above 3.11 kernel tests results in the previously experienced (correct, working) behavior. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D8p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC29', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Nov 4 12:31:48 2013 HibernationDevice: RESUME=UUID=1fbfa69c-fb52-4aee-ad35-9c523aa14974 InstallationDate: Installed on 2009-12-21 (1414 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MachineType: LENOVO 2436CTO MarkForUpload: True ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-32-generic root=/dev/mapper/ssd-root ro vga=792 splash nox2apic crashkernel=384M-2G:64M,2G-:128M quiet splash RelatedPackageVersions: linux-restricted-modules-3.8.0-32-generic N/A linux-backports-modules-3.8.0-32-generic N/A linux-firmware1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-11-04 (0 days ago) dmi.bios.date: 08/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G5ET94WW (2.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ET94WW(2.54):bd08/12/2013:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2436CTO 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/1247967/+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 1243904] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1243904/+attachment/3900174/+files/ProcEnviron.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1243904 Title: Internal keyboard doesn't work in 13.10 Status in “linux” package in Ubuntu: Confirmed Bug description: Hello. I updated from 13.04 to 13.10 but the keyboard did not work. I tried doing a fresh install but the keyboard did not work with the live cd. In 13.04 all works correctly My laptop is a lg p1 express dual Thank you very much --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jac2262 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=3b3ffa91-078a-4731-b078-8ba3ebafc542 InstallationDate: Installed on 2013-04-28 (190 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: LG Electronics P1-J273B MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=fd418822-b188-423d-a734-75f80a75f92c ro quiet splash 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 StagingDrivers: et131x Tags: saucy staging Uname: Linux 3.11.0-12-generic i686 UpgradeStatus: Upgraded to saucy on 2013-10-20 (15 days ago) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo dmi.bios.date: 04/20/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: RKYWSF10 dmi.board.name: ROCKY dmi.board.vendor: LG Electronics dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF10:bd04/20/2006:svnLGElectronics:pnP1-J273B:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A: dmi.product.name: P1-J273B dmi.product.version: Not Applicable dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1243904/+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 1243904] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1243904/+attachment/3900167/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1243904 Title: Internal keyboard doesn't work in 13.10 Status in “linux” package in Ubuntu: Confirmed Bug description: Hello. I updated from 13.04 to 13.10 but the keyboard did not work. I tried doing a fresh install but the keyboard did not work with the live cd. In 13.04 all works correctly My laptop is a lg p1 express dual Thank you very much --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jac2262 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=3b3ffa91-078a-4731-b078-8ba3ebafc542 InstallationDate: Installed on 2013-04-28 (190 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: LG Electronics P1-J273B MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=fd418822-b188-423d-a734-75f80a75f92c ro quiet splash 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 StagingDrivers: et131x Tags: saucy staging Uname: Linux 3.11.0-12-generic i686 UpgradeStatus: Upgraded to saucy on 2013-10-20 (15 days ago) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo dmi.bios.date: 04/20/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: RKYWSF10 dmi.board.name: ROCKY dmi.board.vendor: LG Electronics dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF10:bd04/20/2006:svnLGElectronics:pnP1-J273B:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A: dmi.product.name: P1-J273B dmi.product.version: Not Applicable dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1243904/+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 1243904] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1243904/+attachment/3900169/+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/1243904 Title: Internal keyboard doesn't work in 13.10 Status in “linux” package in Ubuntu: Confirmed Bug description: Hello. I updated from 13.04 to 13.10 but the keyboard did not work. I tried doing a fresh install but the keyboard did not work with the live cd. In 13.04 all works correctly My laptop is a lg p1 express dual Thank you very much --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jac2262 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=3b3ffa91-078a-4731-b078-8ba3ebafc542 InstallationDate: Installed on 2013-04-28 (190 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: LG Electronics P1-J273B MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=fd418822-b188-423d-a734-75f80a75f92c ro quiet splash 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 StagingDrivers: et131x Tags: saucy staging Uname: Linux 3.11.0-12-generic i686 UpgradeStatus: Upgraded to saucy on 2013-10-20 (15 days ago) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo dmi.bios.date: 04/20/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: RKYWSF10 dmi.board.name: ROCKY dmi.board.vendor: LG Electronics dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF10:bd04/20/2006:svnLGElectronics:pnP1-J273B:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A: dmi.product.name: P1-J273B dmi.product.version: Not Applicable dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1243904/+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 1243904] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1243904/+attachment/3900171/+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/1243904 Title: Internal keyboard doesn't work in 13.10 Status in “linux” package in Ubuntu: Confirmed Bug description: Hello. I updated from 13.04 to 13.10 but the keyboard did not work. I tried doing a fresh install but the keyboard did not work with the live cd. In 13.04 all works correctly My laptop is a lg p1 express dual Thank you very much --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jac2262 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=3b3ffa91-078a-4731-b078-8ba3ebafc542 InstallationDate: Installed on 2013-04-28 (190 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: LG Electronics P1-J273B MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=fd418822-b188-423d-a734-75f80a75f92c ro quiet splash 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 StagingDrivers: et131x Tags: saucy staging Uname: Linux 3.11.0-12-generic i686 UpgradeStatus: Upgraded to saucy on 2013-10-20 (15 days ago) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo dmi.bios.date: 04/20/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: RKYWSF10 dmi.board.name: ROCKY dmi.board.vendor: LG Electronics dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF10:bd04/20/2006:svnLGElectronics:pnP1-J273B:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A: dmi.product.name: P1-J273B dmi.product.version: Not Applicable dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1243904/+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 1243904] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1243904/+attachment/3900173/+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/1243904 Title: Internal keyboard doesn't work in 13.10 Status in “linux” package in Ubuntu: Confirmed Bug description: Hello. I updated from 13.04 to 13.10 but the keyboard did not work. I tried doing a fresh install but the keyboard did not work with the live cd. In 13.04 all works correctly My laptop is a lg p1 express dual Thank you very much --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jac2262 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=3b3ffa91-078a-4731-b078-8ba3ebafc542 InstallationDate: Installed on 2013-04-28 (190 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: LG Electronics P1-J273B MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=fd418822-b188-423d-a734-75f80a75f92c ro quiet splash 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 StagingDrivers: et131x Tags: saucy staging Uname: Linux 3.11.0-12-generic i686 UpgradeStatus: Upgraded to saucy on 2013-10-20 (15 days ago) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo dmi.bios.date: 04/20/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: RKYWSF10 dmi.board.name: ROCKY dmi.board.vendor: LG Electronics dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF10:bd04/20/2006:svnLGElectronics:pnP1-J273B:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A: dmi.product.name: P1-J273B dmi.product.version: Not Applicable dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1243904/+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 1243904] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1243904/+attachment/3900170/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1243904 Title: Internal keyboard doesn't work in 13.10 Status in “linux” package in Ubuntu: Confirmed Bug description: Hello. I updated from 13.04 to 13.10 but the keyboard did not work. I tried doing a fresh install but the keyboard did not work with the live cd. In 13.04 all works correctly My laptop is a lg p1 express dual Thank you very much --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jac2262 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=3b3ffa91-078a-4731-b078-8ba3ebafc542 InstallationDate: Installed on 2013-04-28 (190 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: LG Electronics P1-J273B MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=fd418822-b188-423d-a734-75f80a75f92c ro quiet splash 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 StagingDrivers: et131x Tags: saucy staging Uname: Linux 3.11.0-12-generic i686 UpgradeStatus: Upgraded to saucy on 2013-10-20 (15 days ago) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo dmi.bios.date: 04/20/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: RKYWSF10 dmi.board.name: ROCKY dmi.board.vendor: LG Electronics dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF10:bd04/20/2006:svnLGElectronics:pnP1-J273B:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A: dmi.product.name: P1-J273B dmi.product.version: Not Applicable dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1243904/+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 1243904] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1243904/+attachment/3900172/+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/1243904 Title: Internal keyboard doesn't work in 13.10 Status in “linux” package in Ubuntu: Confirmed Bug description: Hello. I updated from 13.04 to 13.10 but the keyboard did not work. I tried doing a fresh install but the keyboard did not work with the live cd. In 13.04 all works correctly My laptop is a lg p1 express dual Thank you very much --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jac2262 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=3b3ffa91-078a-4731-b078-8ba3ebafc542 InstallationDate: Installed on 2013-04-28 (190 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: LG Electronics P1-J273B MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=fd418822-b188-423d-a734-75f80a75f92c ro quiet splash 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 StagingDrivers: et131x Tags: saucy staging Uname: Linux 3.11.0-12-generic i686 UpgradeStatus: Upgraded to saucy on 2013-10-20 (15 days ago) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo dmi.bios.date: 04/20/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: RKYWSF10 dmi.board.name: ROCKY dmi.board.vendor: LG Electronics dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF10:bd04/20/2006:svnLGElectronics:pnP1-J273B:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A: dmi.product.name: P1-J273B dmi.product.version: Not Applicable dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1243904/+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 1243904] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1243904/+attachment/3900166/+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/1243904 Title: Internal keyboard doesn't work in 13.10 Status in “linux” package in Ubuntu: Confirmed Bug description: Hello. I updated from 13.04 to 13.10 but the keyboard did not work. I tried doing a fresh install but the keyboard did not work with the live cd. In 13.04 all works correctly My laptop is a lg p1 express dual Thank you very much --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jac2262 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=3b3ffa91-078a-4731-b078-8ba3ebafc542 InstallationDate: Installed on 2013-04-28 (190 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: LG Electronics P1-J273B MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=fd418822-b188-423d-a734-75f80a75f92c ro quiet splash 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 StagingDrivers: et131x Tags: saucy staging Uname: Linux 3.11.0-12-generic i686 UpgradeStatus: Upgraded to saucy on 2013-10-20 (15 days ago) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo dmi.bios.date: 04/20/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: RKYWSF10 dmi.board.name: ROCKY dmi.board.vendor: LG Electronics dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF10:bd04/20/2006:svnLGElectronics:pnP1-J273B:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A: dmi.product.name: P1-J273B dmi.product.version: Not Applicable dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1243904/+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 1243904] Re: Internal keyboard doesn't work in 13.10
apport information ** Tags added: apport-collected staging ** Description changed: Hello. I updated from 13.04 to 13.10 but the keyboard did not work. I tried doing a fresh install but the keyboard did not work with the live cd. In 13.04 all works correctly My laptop is a lg p1 express dual Thank you very much + --- + ApportVersion: 2.12.5-0ubuntu2.1 + Architecture: i386 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: jac2262 F pulseaudio + DistroRelease: Ubuntu 13.10 + HibernationDevice: RESUME=UUID=3b3ffa91-078a-4731-b078-8ba3ebafc542 + InstallationDate: Installed on 2013-04-28 (190 days ago) + InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) + MachineType: LG Electronics P1-J273B + MarkForUpload: True + Package: linux (not installed) + PccardctlIdent: + Socket 0: +no product info available + PccardctlStatus: + Socket 0: +no card + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=fd418822-b188-423d-a734-75f80a75f92c ro quiet splash 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 + StagingDrivers: et131x + Tags: saucy staging + Uname: Linux 3.11.0-12-generic i686 + UpgradeStatus: Upgraded to saucy on 2013-10-20 (15 days ago) + UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo + dmi.bios.date: 04/20/2006 + dmi.bios.vendor: Phoenix Technologies LTD + dmi.bios.version: RKYWSF10 + dmi.board.name: ROCKY + dmi.board.vendor: LG Electronics + dmi.board.version: Not Applicable + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: LG Electronics + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF10:bd04/20/2006:svnLGElectronics:pnP1-J273B:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A: + dmi.product.name: P1-J273B + dmi.product.version: Not Applicable + dmi.sys.vendor: LG Electronics ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1243904/+attachment/3900165/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1243904 Title: Internal keyboard doesn't work in 13.10 Status in “linux” package in Ubuntu: Confirmed Bug description: Hello. I updated from 13.04 to 13.10 but the keyboard did not work. I tried doing a fresh install but the keyboard did not work with the live cd. In 13.04 all works correctly My laptop is a lg p1 express dual Thank you very much --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jac2262 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=3b3ffa91-078a-4731-b078-8ba3ebafc542 InstallationDate: Installed on 2013-04-28 (190 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: LG Electronics P1-J273B MarkForUpload: True Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=fd418822-b188-423d-a734-75f80a75f92c ro quiet splash 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 StagingDrivers: et131x Tags: saucy staging Uname: Linux 3.11.0-12-generic i686 UpgradeStatus: Upgraded to saucy on 2013-10-20 (15 days ago) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo dmi.bios.date: 04/20/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: RKYWSF10 dmi.board.name: ROCKY dmi.board.vendor: LG Electronics dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF10:bd04/20/2006:svnLGElectronics:pnP1-J273B:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A: dmi.product.name: P1-J273B dmi.product.version: Not Applicable dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1243904/+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/List
[Kernel-packages] [Bug 1237541] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1237541/+attachment/3900145/+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/1237541 Title: Artigo A1100 Fails to Boot/Install with 13.10 Beta 2 Status in “linux” package in Ubuntu: Incomplete Bug description: I have an Artigo A1100 mini-computer, which ran Ubuntu 13.04 fine. Spec Sheet here: http://www.viaembedded.com/en/products/DatasheetPreview/1351/11620/VIA_ARTiGO_A1100_datasheet_v110126.pdf.html I attempted a clean install of 13.10 Beta 2 via a live USB, and found the Live CD, Desktop Install, and Server install to all fail to load properly. The Live CD / Desktop install failed to boot, and froze at the point shown in the attachment. The cursor continued to blink, but made no progress beyond that. The Server Install becomes unresponsive at the language selection screen - the first dialog of the text installer. This appears to be a regression, as 13.04 and 12.04 both install and run fine on this hardware. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu2881 F lxpanel CRDA: Error: [Errno 2] No such file or directory CasperVersion: 1.330 CurrentDmesg: [ 55.323671] Velocity is AUTO mode [ 55.495503] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 55.512512] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 57.109225] eth0: Link auto-negotiation speed 100M bps full duplex [ 57.109702] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready DistroRelease: Ubuntu 13.04 IwConfig: eth0 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 RfKill: Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/04/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. 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.:bvr080015:bd03/04/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237541/+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 1237541] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1237541/+attachment/3900147/+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/1237541 Title: Artigo A1100 Fails to Boot/Install with 13.10 Beta 2 Status in “linux” package in Ubuntu: Incomplete Bug description: I have an Artigo A1100 mini-computer, which ran Ubuntu 13.04 fine. Spec Sheet here: http://www.viaembedded.com/en/products/DatasheetPreview/1351/11620/VIA_ARTiGO_A1100_datasheet_v110126.pdf.html I attempted a clean install of 13.10 Beta 2 via a live USB, and found the Live CD, Desktop Install, and Server install to all fail to load properly. The Live CD / Desktop install failed to boot, and froze at the point shown in the attachment. The cursor continued to blink, but made no progress beyond that. The Server Install becomes unresponsive at the language selection screen - the first dialog of the text installer. This appears to be a regression, as 13.04 and 12.04 both install and run fine on this hardware. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu2881 F lxpanel CRDA: Error: [Errno 2] No such file or directory CasperVersion: 1.330 CurrentDmesg: [ 55.323671] Velocity is AUTO mode [ 55.495503] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 55.512512] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 57.109225] eth0: Link auto-negotiation speed 100M bps full duplex [ 57.109702] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready DistroRelease: Ubuntu 13.04 IwConfig: eth0 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 RfKill: Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/04/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. 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.:bvr080015:bd03/04/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237541/+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 1237541] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1237541/+attachment/3900149/+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/1237541 Title: Artigo A1100 Fails to Boot/Install with 13.10 Beta 2 Status in “linux” package in Ubuntu: Incomplete Bug description: I have an Artigo A1100 mini-computer, which ran Ubuntu 13.04 fine. Spec Sheet here: http://www.viaembedded.com/en/products/DatasheetPreview/1351/11620/VIA_ARTiGO_A1100_datasheet_v110126.pdf.html I attempted a clean install of 13.10 Beta 2 via a live USB, and found the Live CD, Desktop Install, and Server install to all fail to load properly. The Live CD / Desktop install failed to boot, and froze at the point shown in the attachment. The cursor continued to blink, but made no progress beyond that. The Server Install becomes unresponsive at the language selection screen - the first dialog of the text installer. This appears to be a regression, as 13.04 and 12.04 both install and run fine on this hardware. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu2881 F lxpanel CRDA: Error: [Errno 2] No such file or directory CasperVersion: 1.330 CurrentDmesg: [ 55.323671] Velocity is AUTO mode [ 55.495503] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 55.512512] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 57.109225] eth0: Link auto-negotiation speed 100M bps full duplex [ 57.109702] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready DistroRelease: Ubuntu 13.04 IwConfig: eth0 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 RfKill: Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/04/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. 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.:bvr080015:bd03/04/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237541/+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 1237541] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1237541/+attachment/3900148/+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/1237541 Title: Artigo A1100 Fails to Boot/Install with 13.10 Beta 2 Status in “linux” package in Ubuntu: Incomplete Bug description: I have an Artigo A1100 mini-computer, which ran Ubuntu 13.04 fine. Spec Sheet here: http://www.viaembedded.com/en/products/DatasheetPreview/1351/11620/VIA_ARTiGO_A1100_datasheet_v110126.pdf.html I attempted a clean install of 13.10 Beta 2 via a live USB, and found the Live CD, Desktop Install, and Server install to all fail to load properly. The Live CD / Desktop install failed to boot, and froze at the point shown in the attachment. The cursor continued to blink, but made no progress beyond that. The Server Install becomes unresponsive at the language selection screen - the first dialog of the text installer. This appears to be a regression, as 13.04 and 12.04 both install and run fine on this hardware. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu2881 F lxpanel CRDA: Error: [Errno 2] No such file or directory CasperVersion: 1.330 CurrentDmesg: [ 55.323671] Velocity is AUTO mode [ 55.495503] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 55.512512] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 57.109225] eth0: Link auto-negotiation speed 100M bps full duplex [ 57.109702] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready DistroRelease: Ubuntu 13.04 IwConfig: eth0 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 RfKill: Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/04/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. 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.:bvr080015:bd03/04/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237541/+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 1237541] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1237541/+attachment/3900150/+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/1237541 Title: Artigo A1100 Fails to Boot/Install with 13.10 Beta 2 Status in “linux” package in Ubuntu: Incomplete Bug description: I have an Artigo A1100 mini-computer, which ran Ubuntu 13.04 fine. Spec Sheet here: http://www.viaembedded.com/en/products/DatasheetPreview/1351/11620/VIA_ARTiGO_A1100_datasheet_v110126.pdf.html I attempted a clean install of 13.10 Beta 2 via a live USB, and found the Live CD, Desktop Install, and Server install to all fail to load properly. The Live CD / Desktop install failed to boot, and froze at the point shown in the attachment. The cursor continued to blink, but made no progress beyond that. The Server Install becomes unresponsive at the language selection screen - the first dialog of the text installer. This appears to be a regression, as 13.04 and 12.04 both install and run fine on this hardware. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu2881 F lxpanel CRDA: Error: [Errno 2] No such file or directory CasperVersion: 1.330 CurrentDmesg: [ 55.323671] Velocity is AUTO mode [ 55.495503] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 55.512512] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 57.109225] eth0: Link auto-negotiation speed 100M bps full duplex [ 57.109702] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready DistroRelease: Ubuntu 13.04 IwConfig: eth0 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 RfKill: Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/04/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. 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.:bvr080015:bd03/04/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237541/+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 1237541] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1237541/+attachment/3900146/+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/1237541 Title: Artigo A1100 Fails to Boot/Install with 13.10 Beta 2 Status in “linux” package in Ubuntu: Incomplete Bug description: I have an Artigo A1100 mini-computer, which ran Ubuntu 13.04 fine. Spec Sheet here: http://www.viaembedded.com/en/products/DatasheetPreview/1351/11620/VIA_ARTiGO_A1100_datasheet_v110126.pdf.html I attempted a clean install of 13.10 Beta 2 via a live USB, and found the Live CD, Desktop Install, and Server install to all fail to load properly. The Live CD / Desktop install failed to boot, and froze at the point shown in the attachment. The cursor continued to blink, but made no progress beyond that. The Server Install becomes unresponsive at the language selection screen - the first dialog of the text installer. This appears to be a regression, as 13.04 and 12.04 both install and run fine on this hardware. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu2881 F lxpanel CRDA: Error: [Errno 2] No such file or directory CasperVersion: 1.330 CurrentDmesg: [ 55.323671] Velocity is AUTO mode [ 55.495503] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 55.512512] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 57.109225] eth0: Link auto-negotiation speed 100M bps full duplex [ 57.109702] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready DistroRelease: Ubuntu 13.04 IwConfig: eth0 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 RfKill: Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/04/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. 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.:bvr080015:bd03/04/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237541/+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 1237541] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1237541/+attachment/3900141/+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/1237541 Title: Artigo A1100 Fails to Boot/Install with 13.10 Beta 2 Status in “linux” package in Ubuntu: Incomplete Bug description: I have an Artigo A1100 mini-computer, which ran Ubuntu 13.04 fine. Spec Sheet here: http://www.viaembedded.com/en/products/DatasheetPreview/1351/11620/VIA_ARTiGO_A1100_datasheet_v110126.pdf.html I attempted a clean install of 13.10 Beta 2 via a live USB, and found the Live CD, Desktop Install, and Server install to all fail to load properly. The Live CD / Desktop install failed to boot, and froze at the point shown in the attachment. The cursor continued to blink, but made no progress beyond that. The Server Install becomes unresponsive at the language selection screen - the first dialog of the text installer. This appears to be a regression, as 13.04 and 12.04 both install and run fine on this hardware. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu2881 F lxpanel CRDA: Error: [Errno 2] No such file or directory CasperVersion: 1.330 CurrentDmesg: [ 55.323671] Velocity is AUTO mode [ 55.495503] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 55.512512] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 57.109225] eth0: Link auto-negotiation speed 100M bps full duplex [ 57.109702] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready DistroRelease: Ubuntu 13.04 IwConfig: eth0 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 RfKill: Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/04/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. 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.:bvr080015:bd03/04/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237541/+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 1237541] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1237541/+attachment/3900143/+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/1237541 Title: Artigo A1100 Fails to Boot/Install with 13.10 Beta 2 Status in “linux” package in Ubuntu: Incomplete Bug description: I have an Artigo A1100 mini-computer, which ran Ubuntu 13.04 fine. Spec Sheet here: http://www.viaembedded.com/en/products/DatasheetPreview/1351/11620/VIA_ARTiGO_A1100_datasheet_v110126.pdf.html I attempted a clean install of 13.10 Beta 2 via a live USB, and found the Live CD, Desktop Install, and Server install to all fail to load properly. The Live CD / Desktop install failed to boot, and froze at the point shown in the attachment. The cursor continued to blink, but made no progress beyond that. The Server Install becomes unresponsive at the language selection screen - the first dialog of the text installer. This appears to be a regression, as 13.04 and 12.04 both install and run fine on this hardware. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu2881 F lxpanel CRDA: Error: [Errno 2] No such file or directory CasperVersion: 1.330 CurrentDmesg: [ 55.323671] Velocity is AUTO mode [ 55.495503] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 55.512512] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 57.109225] eth0: Link auto-negotiation speed 100M bps full duplex [ 57.109702] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready DistroRelease: Ubuntu 13.04 IwConfig: eth0 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 RfKill: Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/04/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. 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.:bvr080015:bd03/04/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237541/+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 1237541] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1237541/+attachment/3900144/+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/1237541 Title: Artigo A1100 Fails to Boot/Install with 13.10 Beta 2 Status in “linux” package in Ubuntu: Incomplete Bug description: I have an Artigo A1100 mini-computer, which ran Ubuntu 13.04 fine. Spec Sheet here: http://www.viaembedded.com/en/products/DatasheetPreview/1351/11620/VIA_ARTiGO_A1100_datasheet_v110126.pdf.html I attempted a clean install of 13.10 Beta 2 via a live USB, and found the Live CD, Desktop Install, and Server install to all fail to load properly. The Live CD / Desktop install failed to boot, and froze at the point shown in the attachment. The cursor continued to blink, but made no progress beyond that. The Server Install becomes unresponsive at the language selection screen - the first dialog of the text installer. This appears to be a regression, as 13.04 and 12.04 both install and run fine on this hardware. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu2881 F lxpanel CRDA: Error: [Errno 2] No such file or directory CasperVersion: 1.330 CurrentDmesg: [ 55.323671] Velocity is AUTO mode [ 55.495503] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 55.512512] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 57.109225] eth0: Link auto-negotiation speed 100M bps full duplex [ 57.109702] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready DistroRelease: Ubuntu 13.04 IwConfig: eth0 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 RfKill: Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/04/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. 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.:bvr080015:bd03/04/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237541/+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 1237541] Re: Artigo A1100 Fails to Boot/Install with 13.10 Beta 2
apport information ** Tags added: apport-collected raring ** Description changed: I have an Artigo A1100 mini-computer, which ran Ubuntu 13.04 fine. Spec Sheet here: http://www.viaembedded.com/en/products/DatasheetPreview/1351/11620/VIA_ARTiGO_A1100_datasheet_v110126.pdf.html I attempted a clean install of 13.10 Beta 2 via a live USB, and found the Live CD, Desktop Install, and Server install to all fail to load properly. The Live CD / Desktop install failed to boot, and froze at the point shown in the attachment. The cursor continued to blink, but made no progress beyond that. The Server Install becomes unresponsive at the language selection screen - the first dialog of the text installer. - This appears to be a regression, as 13.04 and 12.04 both install and run - fine on this hardware. + This appears to be a regression, as 13.04 and 12.04 both install and run fine on this hardware. + --- + ApportVersion: 2.9.2-0ubuntu8 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: lubuntu2881 F lxpanel + CRDA: Error: [Errno 2] No such file or directory + CasperVersion: 1.330 + CurrentDmesg: + [ 55.323671] Velocity is AUTO mode + [ 55.495503] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready + [ 55.512512] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready + [ 57.109225] eth0: Link auto-negotiation speed 100M bps full duplex + [ 57.109702] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready + DistroRelease: Ubuntu 13.04 + IwConfig: + eth0 no wireless extensions. + + lono wireless extensions. + LiveMediaBuild: Lubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) + MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. + MarkForUpload: True + Package: linux (not installed) + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz + ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 + RelatedPackageVersions: + linux-restricted-modules-3.8.0-19-generic N/A + linux-backports-modules-3.8.0-19-generic N/A + linux-firmware1.106 + RfKill: + + Tags: raring + Uname: Linux 3.8.0-19-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + dmi.bios.date: 03/04/2010 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 080015 + dmi.board.asset.tag: To Be Filled By O.E.M. + dmi.board.name: To be filled by O.E.M. + dmi.board.vendor: To be filled by O.E.M. + dmi.board.version: To be filled by O.E.M. + 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.:bvr080015:bd03/04/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.: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. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1237541/+attachment/3900140/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1237541 Title: Artigo A1100 Fails to Boot/Install with 13.10 Beta 2 Status in “linux” package in Ubuntu: Incomplete Bug description: I have an Artigo A1100 mini-computer, which ran Ubuntu 13.04 fine. Spec Sheet here: http://www.viaembedded.com/en/products/DatasheetPreview/1351/11620/VIA_ARTiGO_A1100_datasheet_v110126.pdf.html I attempted a clean install of 13.10 Beta 2 via a live USB, and found the Live CD, Desktop Install, and Server install to all fail to load properly. The Live CD / Desktop install failed to boot, and froze at the point shown in the attachment. The cursor continued to blink, but made no progress beyond that. The Server Install becomes unresponsive at the language selection screen - the first dialog of the text installer. This appears to be a regression, as 13.04 and 12.04 both install and run fine on this hardware. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu2881 F lxpanel CRDA: Error: [Errno 2] No such file or directory CasperVersion: 1.330 CurrentDmesg: [ 55.323671] Velocity is AUTO mode [ 55.495503] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 55.512512] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 57.109225] eth0: Link auto-negotiation speed 100M bps full duplex [ 57.109702] IPv6: ADDRCONF(NETDEV_CHANGE): et
[Kernel-packages] [Bug 1237541] HookError_cloud_archive.txt
apport information ** Attachment added: "HookError_cloud_archive.txt" https://bugs.launchpad.net/bugs/1237541/+attachment/3900142/+files/HookError_cloud_archive.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1237541 Title: Artigo A1100 Fails to Boot/Install with 13.10 Beta 2 Status in “linux” package in Ubuntu: Incomplete Bug description: I have an Artigo A1100 mini-computer, which ran Ubuntu 13.04 fine. Spec Sheet here: http://www.viaembedded.com/en/products/DatasheetPreview/1351/11620/VIA_ARTiGO_A1100_datasheet_v110126.pdf.html I attempted a clean install of 13.10 Beta 2 via a live USB, and found the Live CD, Desktop Install, and Server install to all fail to load properly. The Live CD / Desktop install failed to boot, and froze at the point shown in the attachment. The cursor continued to blink, but made no progress beyond that. The Server Install becomes unresponsive at the language selection screen - the first dialog of the text installer. This appears to be a regression, as 13.04 and 12.04 both install and run fine on this hardware. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu2881 F lxpanel CRDA: Error: [Errno 2] No such file or directory CasperVersion: 1.330 CurrentDmesg: [ 55.323671] Velocity is AUTO mode [ 55.495503] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 55.512512] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 57.109225] eth0: Link auto-negotiation speed 100M bps full duplex [ 57.109702] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready DistroRelease: Ubuntu 13.04 IwConfig: eth0 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 RfKill: Tags: raring Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/04/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. 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.:bvr080015:bd03/04/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237541/+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 1246664] Re: "Buffer I/O error on device zram0, logical block 515067"
To damian-sawiicki: Do you see a zram-config.conf file under /etc/init ? Another stupid question: did you precisely invoke "dpkg --purge zram- config" ? (When I realized I still had zram-config at work after uninstalling it, I didn't think about "dpkg --purge" and just removed whatever "zram" files I found in the system, especially /dev/zram0 and /dev/zram1 as the machine has two cores, and eventually zram-config.conf if it was still there, but I am not even sure it was still there). To Luis Henriques: I installed the generic i386 kernel and headers in a P4, and it has also been installed to a T60 where it was running with many programs at same time and zram-config installed and at work. All this lasted about 45 minutes and the session didn't fail, although some swapping was occurring. No buffer I/O occurred. Now I am being testing in the P4, zram-config reinstalled, your kernel i386 generic installed, since about 15 minutes. Are running: Libreoffice writer, Firefox, Software Center, PPA Software Center… $ uname -a Linux peluche 3.2.0-56-generic #86~lp1246664 SMP Mon Nov 4 11:21:05 UTC 2013 i686 i686 i386 GNU/Linux $ $ cat /proc/swaps FilenameTypeSizeUsedPriority /dev/zram0 partition 772040 0 5 /dev/zram1 partition 772040 0 5 /dev/sdb5 partition 3174396 0 -1 $ Before meeting with the buffer I/O error I used to change the default values for the size of the swap devices (lower the size to 1/4) and setup the swappiness to 0, but for the test I do leave the default values unchanged. I will come back later to add information according to the results I will get. Now I will start an additional heavy load by starting Ubuntu Builder and build a custom ISO with your newer kernel and reinstall zram-config to it. (At least to test the behavior while 'heavy duty' is being done). -- 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/1246664 Title: "Buffer I/O error on device zram0, logical block 515067" Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Precise: Fix Committed Status in “linux” source package in Saucy: Fix Released Bug description: SRU Justification: Commit 12a7ad3 "zram: avoid access beyond the zram device" introduced a regression where valid_io_request() checks if request end coincides with disksize (end equals bound). It fails if we attempt to read beyond the bound. Impact: Several errors will be logged if, for example, zram-config is installed: [ 14.666280] zram: module is from the staging directory, the quality is unknown, you have been warned. [ 14.667040] zram: Creating 1 devices ... [ 14.830355] Buffer I/O error on device zram0, logical block 62411 [ 14.830375] Buffer I/O error on device zram0, logical block 62411 [ 14.830598] Buffer I/O error on device zram0, logical block 62411 [ 14.830621] Buffer I/O error on device zram0, logical block 62411 [ 14.878597] Adding 249644k swap on /dev/zram0. Priority:5 extents:1 across:249644k SS Fix: Commit 75c7caf5a052ffd8db3312fa7864ee2d142890c4 "zram: allow request end to coincide with disksize" fixes the issue by correcting the test in valid_io_request() function. Testcase: I was able to reproduce the issue by simply installing zram-config in a precise box. = This is a duplicate of #1217189, but for some reason neither @oibaf nor me can reopen it. It is in "fix released" state, but the problem is at most partially solved. It seems that the bug no longer causes lockups (described in another bug: #1215513), but is still present (as I get error messages on boot screen and after $ dmesg | grep zram). If someone has enough privileges to reopen 1217189 for "linux (ubuntu)" (I don't know about raring, but no one complains, so it is probably ok), and remove this bug (maybe merging this message to the comments in 1217189), I would be really grateful. Ubuntu 12.04.3 LTS Kernel Linux 3.2.0-56-generic-pae (the problem was first observed in 53 and since 54 there are no lockups). --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: damian 2771 F
[Kernel-packages] [Bug 1175759] Re: Atheros AR9161 Ethernet Gigabit adapter works till suspend
Thanks, I will try your suggestion next week, when I have time. -- 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/1175759 Title: Atheros AR9161 Ethernet Gigabit adapter works till suspend Status in “linux” package in Ubuntu: Incomplete Bug description: My Ethernet adapter in my N56-VZ only works till the computer suspends, after that it's not recognized anymore. It just disapeared from ifconfig and I can't use it anymore. There is no eth0 anymore. I am now on Ubuntu 13.04 linux version 3.8.0-19-generic #29-Ubuntu SMP. I tried the 3.9.0-030900 mainline kernel, but this doesn't fix the problem. it seems it doesn't recognizes the ethernet network adapter at all. 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/controlC0: steven 2235 F pulseaudio Date: Thu May 2 21:37:32 2013 HibernationDevice: RESUME=UUID=099313ad-92b7-4954-8935-dc24a403d638 InstallationDate: Installed on 2013-02-15 (76 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: ASUSTeK COMPUTER INC. N56VZ MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=7a8daf7f-3ff2-4e73-be9c-f0803bb86bd2 ro acpi=force 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-25 (7 days ago) dmi.bios.date: 12/06/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VZ.216 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VZ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.216:bd12/06/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N56VZ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1175759/+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 1131091] Re: LAN cannot be connected after wakeup
hi Christopher, I'm no longer at that version of kernel or distribution. I'm using Trusty and don't experience the issue for the last moths. Thanks, tamas -- 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/1131091 Title: LAN cannot be connected after wakeup Status in “linux” package in Ubuntu: Incomplete Bug description: My HP Elitebook 2540p laptop worked fine but in the recent times sometimes my laptop cannot connect via ethernet after suspend & wakeup. LED lights are on, there is link. At the same time wifi works. After reboot it works. I setup network manually from shell by ifconfig and from Networkmanager as well, but didn't help. I removed and inserted e1000e and didn't help. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-generic 3.8.0.6.20 ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tompos 2379 F pulseaudio CRDA: country HU: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS Date: Thu Feb 21 09:28:46 2013 InstallationDate: Installed on 2013-02-17 (3 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130216) MachineType: Hewlett-Packard HP EliteBook 2540p MarkForUpload: True PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.8.0-6-generic root=UUID=bc11614b-497d-499f-a046-7e8fdb99c4d2 ro rootflags=subvol=@ 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.8.0-6-generic N/A linux-backports-modules-3.8.0-6-generic N/A linux-firmware 1.103 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CSU Ver. F.08 dmi.board.name: 7008 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 38.32 dmi.chassis.asset.tag: CZC0295P29 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CSUVer.F.08:bd11/24/2010:svnHewlett-Packard:pnHPEliteBook2540p:pvr:rvnHewlett-Packard:rn7008:rvrKBCVersion38.32:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 2540p dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1131091/+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 1195483] Re: Installation, Live and Check disc do not start on Asus ZenBook Prime UX31A
I built a trusty test kernel with the following commits from upstream: c6cd2ee2d59111a07cd9199564c9bdcb2d11e5cf 7195a50b5c7e00cc3312934fd022c3006b533d12 4f56d12ebb28fceac4c6e60c8993fbfc122e1399 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1195483/ Can you test this kernel and confirm if it fixes this bug or not? -- 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/1195483 Title: Installation, Live and Check disc do not start on Asus ZenBook Prime UX31A Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Saucy: In Progress Status in “linux” source package in Trusty: In Progress Bug description: When I try to install Ubuntu 13.04 on a new Asus ZenBook Prime UX31A from june 2013, grub will come up bit every option such as Installation, Live and Check disc result in a blank screen. This is possibly due to preinstalled Windows 8 and UEFI. I did not approve/accept the Windows 8 installation and that should not matter. I want to install only Ubuntu and *no* dual boot with the preinstalled Windows 8. I want to erase the entire disc in firsts steps of installation procedure. Screenshot illustrating the problem are: http://i.imgur.com/94zPRh5.jpg (ASUS splash screen) http://i.imgur.com/CKJZf6s.jpg (language selection for Windows 8) http://i.imgur.com/2OIGnra.jpg (accept license, which I did not and rebooted with F1/F2) http://i.imgur.com/0l3ZIme.jpg (general BIOS info, I upgrade to latest BIOS) http://i.imgur.com/RtjRraF.jpg (used settings to boot from USB) http://i.imgur.com/Vgb3Xju.jpg (grub which goes to black screen and systems is locked in that state) For more information, see: device information https://help.ubuntu.com/community/AsusZenbookPrime similar problem http://ubuntuforums.org/showthread.php?t=2149954 UEFI and preinstalled Windwos 8 http://askubuntu.com/questions/221835/installing-ubuntu-on-a-pre-installed-uefi-supported-windows-8-system More about EUFI https://help.ubuntu.com/community/UEFI More on installing without WUBI http://www.omgubuntu.co.uk/2013/04/wubi-advice Debugging attempts from https://wiki.archlinux.org/index.php/Boot_Debugging failed. Perhaps I did something wrong. What are ways to write debug to the screen in my case? And, more importantly, how do I get it working because have the right to install whatever I want? Is the only way to get it installed to accept the Windows 8 license and install Ubuntu from Windows (and in effect making it dual boot which I don't want). Ubuntu should fix this as it is the flagship of a major laptop manufacturer (ASUS) for which Ubuntu is no longer installable. --- ApportVersion: 2.9.2-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sander 2424 F pulseaudio DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=24994e67-9b18-4cad-b387-788beff8b388 InstallationDate: Installed on 2013-07-06 (80 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. UX31A MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-30-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 RelatedPackageVersions: linux-restricted-modules-3.8.0-30-generic N/A linux-backports-modules-3.8.0-30-generic N/A linux-firmware1.106 StagingDrivers: rts5139 Tags: raring staging raring staging raring staging Uname: Linux 3.8.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo dmi.bios.date: 01/31/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX31A.218 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX31A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX31A.218:bd01/31/2013:svnASUSTeKCOMPUTERINC.:pnUX31A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX31A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX31A 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/1195483/+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 1247967] Re: nvidia optimus chipset disabled when running on battery, even in discrete mode
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.12 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-saucy/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: kernel-da-key needs-bisect -- 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/1247967 Title: nvidia optimus chipset disabled when running on battery, even in discrete mode Status in “linux” package in Ubuntu: Incomplete Bug description: It appears that under 3.11.0-13, the Nvidia Optimus GPU is disabled when running on battery even if the chipset is set to discrete mode in the BIOS. When running without AC power under the 3.11 kernel, lspci -v gives the following: http://paste.ubuntu.com/6360607/ With AC power under 3.11, the same command gives: http://paste.ubuntu.com/6360613/ If the system is booted into the 3.11 kernel with AC power connected, it can be removed and the GPU continues to function normally. I have not tested suspend and resume under the 3.11 kernel (with or without AC power). This same configuration worked properly under Raring (13.04). Booting with the 3.8 kernel and the same nvidia module version used in the above 3.11 kernel tests results in the previously experienced (correct, working) behavior. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D8p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC29', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Nov 4 12:31:48 2013 HibernationDevice: RESUME=UUID=1fbfa69c-fb52-4aee-ad35-9c523aa14974 InstallationDate: Installed on 2009-12-21 (1414 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MachineType: LENOVO 2436CTO MarkForUpload: True ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-32-generic root=/dev/mapper/ssd-root ro vga=792 splash nox2apic crashkernel=384M-2G:64M,2G-:128M quiet splash RelatedPackageVersions: linux-restricted-modules-3.8.0-32-generic N/A linux-backports-modules-3.8.0-32-generic N/A linux-firmware1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-11-04 (0 days ago) dmi.bios.date: 08/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G5ET94WW (2.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 2436CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ET94WW(2.54):bd08/12/2013:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2436CTO 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/1247967/+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 1246664] Re: "Buffer I/O error on device zram0, logical block 515067"
@meets I talked about it in the previous thread (#1217189) and was told by @danmbox to run dpkg --purge (but anyway I think that zram-config wasn't installed before - however I'm not 100% sure), but it didn't help... -- 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/1246664 Title: "Buffer I/O error on device zram0, logical block 515067" Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Precise: Fix Committed Status in “linux” source package in Saucy: Fix Released Bug description: SRU Justification: Commit 12a7ad3 "zram: avoid access beyond the zram device" introduced a regression where valid_io_request() checks if request end coincides with disksize (end equals bound). It fails if we attempt to read beyond the bound. Impact: Several errors will be logged if, for example, zram-config is installed: [ 14.666280] zram: module is from the staging directory, the quality is unknown, you have been warned. [ 14.667040] zram: Creating 1 devices ... [ 14.830355] Buffer I/O error on device zram0, logical block 62411 [ 14.830375] Buffer I/O error on device zram0, logical block 62411 [ 14.830598] Buffer I/O error on device zram0, logical block 62411 [ 14.830621] Buffer I/O error on device zram0, logical block 62411 [ 14.878597] Adding 249644k swap on /dev/zram0. Priority:5 extents:1 across:249644k SS Fix: Commit 75c7caf5a052ffd8db3312fa7864ee2d142890c4 "zram: allow request end to coincide with disksize" fixes the issue by correcting the test in valid_io_request() function. Testcase: I was able to reproduce the issue by simply installing zram-config in a precise box. = This is a duplicate of #1217189, but for some reason neither @oibaf nor me can reopen it. It is in "fix released" state, but the problem is at most partially solved. It seems that the bug no longer causes lockups (described in another bug: #1215513), but is still present (as I get error messages on boot screen and after $ dmesg | grep zram). If someone has enough privileges to reopen 1217189 for "linux (ubuntu)" (I don't know about raring, but no one complains, so it is probably ok), and remove this bug (maybe merging this message to the comments in 1217189), I would be really grateful. Ubuntu 12.04.3 LTS Kernel Linux 3.2.0-56-generic-pae (the problem was first observed in 53 and since 54 there are no lockups). --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: damian 2771 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf830 irq 47' Mixer name : 'Realtek ALC268' Components : 'HDA:10ec0268,10280275,0013' Controls : 16 Simple ctrls : 9 DistroRelease: Ubuntu 12.04 MachineType: Dell Inc. Vostro1710 MarkForUpload: True NonfreeKernelModules: nvidia wl Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-56-generic-pae root=UUID=bfe81069-1c35-4ccc-a23a-33528ac81877 ro selinux=1 security=selinux quiet splash ProcVersionSignature: Ubuntu 3.2.0-56.86-generic-pae 3.2.51 RelatedPackageVersions: linux-restricted-modules-3.2.0-56-generic-pae N/A linux-backports-modules-3.2.0-56-generic-pae N/A linux-firmware1.79.7 StagingDrivers: zram Tags: precise running-unity staging Uname: Linux 3.2.0-56-generic-pae i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo dmi.bios.date: 09/09/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0X805C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnDellInc.:bvrA09:bd09/09/2008:svnDellInc.:pnVostro1710:pvrNull:rvnDellInc.:rn0X805C:rvr:cvnDellInc.:ct8:cvrN/A: dmi.product.name: Vostro1710 dmi.product.version: Null dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1246664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help
[Kernel-packages] [Bug 1247784] Re: please enable CONFIG_RT2800USB_RT3573 in kernel 3.12
** Tags removed: 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/1247784 Title: please enable CONFIG_RT2800USB_RT3573 in kernel 3.12 Status in “linux” package in Ubuntu: Triaged Bug description: As said into the title, in the new 3.12 this option is disabled in ubuntu quoting the .config file # CONFIG_RT2800USB_RT3573 is not set I have a device using this module, and I did recompile the kernel (enabling it) successfully. Please consider enabling it. Thanks --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-10-18 (16 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True Package: linux (not installed) Tags: saucy Uname: Linux 3.12.0 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1247784/+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 1247654] Re: PC freezes after resuming from suspension
I tested the latest upstream kernel 3.12.0-031200 but nothing has changed. ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1247654 Title: PC freezes after resuming from suspension Status in “linux” package in Ubuntu: Confirmed Bug description: I select "Suspend" from the ghear icon on the top left hand side of the indicators bar, wait from a fiew secons (20-30) to half an hour, press the power button again. My PC does not resume correclty from suspension, it looks like it is resuming, hard disk starts working and it sounds it is resuming but everything on the video freezes, I get just a black screen, have to reboot manually by pressing the power button. I am currently running Trust Tahr with all updates. This is my hardware: http://phillw.net/hardware/kuDwMTTb. I have updated my BIOS firmware and followed the instructions here: https://wiki.ubuntu.com/DebuggingKernelSuspend. I am attaching dmesg file and /proc/acpi/wakeup file. --- ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: letozaf2771 F pulseaudio /dev/snd/controlC1: letozaf2771 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=aa591f66-2a28-435e-8570-155157c9a301 InstallationDate: Installed on 2012-03-02 (610 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) IwConfig: eth0 no wireless extensions. lono wireless extensions. virbr0no wireless extensions. MachineType: System manufacturer System Product Name MarkForUpload: True Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-1-generic root=UUID=85f8c649-a0b7-4899-8b56-cf85fbe7f8e5 ro crashkernel=384M-2G:64M,2G-:128M quiet splash ProcVersionSignature: Ubuntu 3.12.0-1.3-generic 3.12.0-rc7 RelatedPackageVersions: linux-restricted-modules-3.12.0-1-generic N/A linux-backports-modules-3.12.0-1-generic N/A linux-firmware1.117 RfKill: Tags: trusty Uname: Linux 3.12.0-1-generic x86_64 UpgradeStatus: Upgraded to trusty on 2013-10-25 (8 days ago) UserGroups: adm admin autopilot cdrom dip libvirtd lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 03/27/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0808 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.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.:bvr0808:bd03/27/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N:rvrRev1.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/1247654/+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
I built the next test kernel, up to the following commit: be547436c22c3b7d934d9afd841cfd7a6807f7ab The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1237336 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. Thanks in advance -- 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= 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 1216422] Re: [Acer Aspire One 725] Touchpad not working
Dear Christopher, The upstream post was sent to the platform-driver-x86 list: http://article.gmane.org/gmane.linux.drivers.platform.x86.devel/4772/ The maintainer of the regression commit answered he will look into the issue a few weeks ago. Since then, I have not read anything. Perhaps I did something wrong? Please advice. I tested the two most recent mainline kernels: 3.12.0-031200rc7-generic and 3.12.0-031200-generic. Both with negative results, the touchpad issue remains. How should we proceed now? Please advice. Thanks in advance, Launchy -- 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/1216422 Title: [Acer Aspire One 725] Touchpad not working Status in “linux” package in Ubuntu: Incomplete Bug description: Touchpad will not work out of the box on this netbook. This is a regression from Oneiric to Precise+. a)WORKAROUND: Pushing Fn+F7 before login or b)WORKAROUND: Pushing Alt+Fn+F7 or Ctr+Fn+F7 after login makes the touchpad working. After reboot, I have to repeat a) or b) to get touchpad working again. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-3-generic 3.11.0-3.7 ProcVersionSignature: Ubuntu 3.11.0-3.7-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2749 F pulseaudio ubuntu 4053 F pulseaudio /dev/snd/controlC0: ubuntu 2749 F pulseaudio ubuntu 4053 F pulseaudio CasperVersion: 1.336 Date: Sat Aug 24 21:01:43 2013 LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130822) MachineType: Acer AO725 MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/username.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi RelatedPackageVersions: linux-restricted-modules-3.11.0-3-generic N/A linux-backports-modules-3.11.0-3-generic N/A linux-firmware1.113 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: ZA10_BZ dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd04/18/2013:svnAcer:pnAO725:pvrV1.07:rvnAcer:rnZA10_BZ:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: AO725 dmi.product.version: V1.07 dmi.sys.vendor: Acer --- ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2773 F pulseaudio /dev/snd/controlC0: ubuntu 2773 F pulseaudio CasperVersion: 1.336 DistroRelease: Ubuntu 13.10 LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130827) MachineType: Acer AO725 MarkForUpload: True Package: linux (not installed) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/hostname.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-4-generic N/A linux-backports-modules-3.11.0-4-generic N/A linux-firmware1.113 Tags: saucy Uname: Linux 3.11.0-4-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/18/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: ZA10_BZ dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd04/18/2013:svnAcer:pnAO725:pvrV1.07:rvnAcer:rnZA10_BZ:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: AO725 dmi.product.version: V1.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1216422/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel
[Kernel-packages] [Bug 1247647] Re: Kernel oops during btrfs access
To start a bisect, we first need to identify the last good kernel version and first bad kernel version. Can you test the following two kernels: v3.10 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-saucy/ v3.11 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-saucy/ They can be installed by installing the linux-image .deb package and rebooting. ** Tags added: performing-bisect -- 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/1247647 Title: Kernel oops during btrfs access Status in “linux” package in Ubuntu: Confirmed Bug description: cat /proc/version_signature Ubuntu 3.11.0-12.19-generic 3.11.3 root@ubuntunas:~# sudo lspci -vnvn 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=0dbf4328-2e66-42b3-88dd-b96a5c25b11d ro console=tty0 console=ttyS0,115200n8 crashkernel=384M-2G:64M,2G-:128M quiet 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 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-08-25 (70 days ago) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1247647/+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 1246664] Re: "Buffer I/O error on device zram0, logical block 515067"
> Is it normal, that I didn't have the package installed, but the error still occurred and zram0 was visible after 'swapon -s'? Hi, If you had it installed before then removed it happens, and is also filed in a bug report: zram-config runs even after uninstalled, needs purge - https://bugs.launchpad.net/ubuntu/+source/zram-config/+bug/1036339 If you didn't have zram-config installed before, or another script meant to load and configure it's behavior… the zram module should not be loaded, nor the zram devices created. -- 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/1246664 Title: "Buffer I/O error on device zram0, logical block 515067" Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Precise: Fix Committed Status in “linux” source package in Saucy: Fix Released Bug description: SRU Justification: Commit 12a7ad3 "zram: avoid access beyond the zram device" introduced a regression where valid_io_request() checks if request end coincides with disksize (end equals bound). It fails if we attempt to read beyond the bound. Impact: Several errors will be logged if, for example, zram-config is installed: [ 14.666280] zram: module is from the staging directory, the quality is unknown, you have been warned. [ 14.667040] zram: Creating 1 devices ... [ 14.830355] Buffer I/O error on device zram0, logical block 62411 [ 14.830375] Buffer I/O error on device zram0, logical block 62411 [ 14.830598] Buffer I/O error on device zram0, logical block 62411 [ 14.830621] Buffer I/O error on device zram0, logical block 62411 [ 14.878597] Adding 249644k swap on /dev/zram0. Priority:5 extents:1 across:249644k SS Fix: Commit 75c7caf5a052ffd8db3312fa7864ee2d142890c4 "zram: allow request end to coincide with disksize" fixes the issue by correcting the test in valid_io_request() function. Testcase: I was able to reproduce the issue by simply installing zram-config in a precise box. = This is a duplicate of #1217189, but for some reason neither @oibaf nor me can reopen it. It is in "fix released" state, but the problem is at most partially solved. It seems that the bug no longer causes lockups (described in another bug: #1215513), but is still present (as I get error messages on boot screen and after $ dmesg | grep zram). If someone has enough privileges to reopen 1217189 for "linux (ubuntu)" (I don't know about raring, but no one complains, so it is probably ok), and remove this bug (maybe merging this message to the comments in 1217189), I would be really grateful. Ubuntu 12.04.3 LTS Kernel Linux 3.2.0-56-generic-pae (the problem was first observed in 53 and since 54 there are no lockups). --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: damian 2771 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf830 irq 47' Mixer name : 'Realtek ALC268' Components : 'HDA:10ec0268,10280275,0013' Controls : 16 Simple ctrls : 9 DistroRelease: Ubuntu 12.04 MachineType: Dell Inc. Vostro1710 MarkForUpload: True NonfreeKernelModules: nvidia wl Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-56-generic-pae root=UUID=bfe81069-1c35-4ccc-a23a-33528ac81877 ro selinux=1 security=selinux quiet splash ProcVersionSignature: Ubuntu 3.2.0-56.86-generic-pae 3.2.51 RelatedPackageVersions: linux-restricted-modules-3.2.0-56-generic-pae N/A linux-backports-modules-3.2.0-56-generic-pae N/A linux-firmware1.79.7 StagingDrivers: zram Tags: precise running-unity staging Uname: Linux 3.2.0-56-generic-pae i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo dmi.bios.date: 09/09/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0X805C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnDellInc.:bvrA09:bd09/09/2008:svnDellInc.:pnVostro1710:pvrNull:rvnDellInc.:rn0X805C:rvr:cvnDellInc.:ct8:cvrN/A: dmi.product.name: Vostro1710 dmi.product.version: Null dmi.sys.ve
[Kernel-packages] [Bug 1094800] Re: [Toshiba Protege Z930-12T PT235E-02Q04KEP] fails to resume after second suspend on kernel >=3.4
** Changed in: linux (Ubuntu Quantal) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu Raring) Status: Confirmed => Incomplete ** Tags added: kernel-da-key -- 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/1094800 Title: [Toshiba Protege Z930-12T PT235E-02Q04KEP] fails to resume after second suspend on kernel >=3.4 Status in “linux” package in Ubuntu: Incomplete Status in “linux” source package in Quantal: Incomplete Status in “linux” source package in Raring: Incomplete Status in “linux” package in Arch Linux: New Bug description: After resuming from first supend, brightness keys don't work, power key doesn't show logout menu, and if I try to suspend a second time I'm unable to recover from suspension (blank screen) Seems similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1088721 This is definetly seems a regression. I did a manual bisect on kernels from http://kernel.ubuntu.com/~kernel-ppa/mainline and everytihng works ok up until kernel 3.3.8. Starting from 3.4 and up until 3.8-rc, I can see this bug. I also have a toshiba portege z830 and this doesn't happen, so it's specific to Toshiba Portege z930(-12T) --- ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 DistroRelease: Ubuntu 12.10 InstallationDate: Installed on 2011-12-18 (378 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MarkForUpload: True Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: quantal Uname: Linux 3.4.0-030400-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to quantal on 2012-12-23 (7 days ago) UserGroups: --- ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedro 4284 F xfce4-volumed pedro 4425 F xfce4-mixer-plu pedro 6001 F pulseaudio CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 12.10 HibernationDevice: RESUME=UUID=7ed7eab4-062c-41fe-87ed-15e8c5d1f9c8 InstallationDate: Installed on 2011-12-18 (378 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: TOSHIBA PORTEGE Z930 MarkForUpload: True Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-21-generic root=UUID=f56c9ffc-46c0-46ce-a425-1f45c00fc6d2 ro quiet splash acpi_backlight=vendor i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 resume=UUID=7ed7eab4-062c-41fe-87ed-15e8c5d1f9c8 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/pedro not ours. No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.5.0-21-generic N/A linux-backports-modules-3.5.0-21-generic N/A linux-firmware1.95 Tags: quantal Uname: Linux 3.5.0-21-generic x86_64 UpgradeStatus: Upgraded to quantal on 2012-12-23 (7 days ago) UserGroups: dmi.bios.date: 10/01/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 6.40 dmi.board.asset.tag: 00 dmi.board.name: PORTEGE Z930 dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion6.40:bd10/01/2012:svnTOSHIBA:pnPORTEGEZ930:pvrPT235E-02Q04KEP:rvnTOSHIBA:rnPORTEGEZ930:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE Z930 dmi.product.version: PT235E-02Q04KEP dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1094800/+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 1152736] Re: system swapping itself to death in raring for no good reason
** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu Raring) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu Saucy) 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/1152736 Title: system swapping itself to death in raring for no good reason Status in “linux” package in Ubuntu: Incomplete Status in “linux” source package in Raring: Incomplete Status in “linux” source package in Saucy: Incomplete Bug description: My laptop has 4GB of RAM and ~6GB of swap configured. After my most recent kernel upgrade in raring, I am noticing the system has started swapping itself to death; the desktop becomes completely unresponsive, and in some cases it becomes unresponsive even over SSH. Looking remotely with SSH, I find that kswapd0 is using up nearly one full core. I have no idea *why* - I have vm.swappiness set to 30, and 'free' shows that over 1GB of RAM is still being used for buffers, so there really shouldn't be any memory pressure. Despite the fact that there's only ~400MB of swap used, which should certainly fit back into system memory, 'swapoff -a' fails with a 'Could not allocate memory' error. If I set vm.swappiness to 0, the swap usage decreases, but *very* slowly: after over a half hour, there's still over 400MB of swap used. And I don't have any idea what kswapd is doing at this point, but it's still very busy; and even after setting vm.swappiness=0, the system has managed a second time to get itself into an unresponsive state, with swap looking like the culprit. dmesg shows nothing (which I will try to demonstrate by attaching logs from the machine in question, once it's responsive enough to let me run apport-collect). --- ApportVersion: 2.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vorlon29618 F pulseaudio /dev/snd/controlC0: vorlon29618 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=f6ab3c43-61b4-4af7-bf03-fa3b147a1de0 InstallationDate: Installed on 2010-09-24 (896 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) MachineType: LENOVO 3249CTO MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-10-generic root=/dev/mapper/hostname-root ro quiet splash --verbose vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-10.19-generic 3.8.2 RelatedPackageVersions: linux-restricted-modules-3.8.0-10-generic N/A linux-backports-modules-3.8.0-10-generic N/A linux-firmware1.103 Tags: quantal Uname: Linux 3.8.0-10-generic x86_64 UpgradeStatus: Upgraded to quantal on 2013-01-25 (42 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev sambashare src sudo WifiSyslog: dmi.bios.date: 08/23/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6QET52WW (1.22 ) dmi.board.name: 3249CTO 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:bvr6QET52WW(1.22):bd08/23/2010:svnLENOVO:pn3249CTO:pvrThinkPadX201:rvnLENOVO:rn3249CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3249CTO dmi.product.version: ThinkPad X201 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1152736/+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 1191603] Re: raring-updates: regression: 3.8.0-24.35 causes sporadic failure of USB audio devices
** Tags added: kernel-da-key -- 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/1191603 Title: raring-updates: regression: 3.8.0-24.35 causes sporadic failure of USB audio devices Status in “linux” package in Ubuntu: Incomplete Bug description: The 3.8.0-24.35 kernel update in raring introduced sporadic failure of USB audio devices. The symptoms are that the device suddenly stops working and you get the following dmesg output: [ 7532.838274] cannot submit urb (err = -18) [ 7532.838283] cannot submit urb (err = -18) [ 7532.838291] cannot submit urb (err = -18) [ 7532.842224] delay: estimated 288, actual 96 [ 7532.922160] delay: estimated 432, actual 96 This bug has been introduced by the following commits (UHCI: implement new semantics for URB_ISO_ASAP, OHCI: implement new semantics for URB_ISO_ASAP): https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c44b225077bb1fb25ed5cd5c4f226897b91bedd4 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=6a41b4d3fe8cd4cc95181516fc6fba7b1747a27c A fix has been released (USB: fix latency in uhci-hcd and ohci-hcd): https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=e1944017839d7dfbf7329fac4bdec8b4050edf5e The fix hasn't been backported to 3.8 yet, but as this bug was introduced to raring by pulling upstream kernel changes, it would be nice to backport the fix to raring as soon as possible. For further reference: http://markmail.org/message/gt554vejrjkutsfw#query:+page:1+mid:gt554vejrjkutsfw+state:results https://bbs.archlinux.org/viewtopic.php?id=163891 http://comments.gmane.org/gmane.linux.usb.general/85343 http://lists.opensuse.org/opensuse-bugs/2013-05/msg01617.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1191603/+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 1159219] Re: Ubuntu Raring , IOMMU, fails to boot
The 3.12 final kernel is now out. Can you give this kernel a try to see if the bug still exists in mainline: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-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/1159219 Title: Ubuntu Raring , IOMMU, fails to boot Status in “linux” package in Ubuntu: Incomplete Status in “linux” source package in Raring: Incomplete Status in “linux” source package in Saucy: Incomplete Bug description: My system, Ubuntu 13.04, at boot, it drops to busybox if i have AMD IOMMU enabled in BIOS. If i have the option enabled then the system only boots with a kernel version <= 3.6. I have tried all the kernels from Ubuntu Kernel Mainline, 3.8.4 included. The error that it throws during boot, it is: AMD-VI: Event logged.. INVALID DEVICE REQUEST Thank you. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-13-generic 3.8.0-13.23 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mdalacu2411 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Sat Mar 23 21:39:49 2013 InstallationDate: Installed on 2010-10-18 (886 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-13-generic root=UUID=d17fe8b8-a39b-48b6-991a-ea7e7c7a230d ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.8.0-13-generic N/A linux-backports-modules-3.8.0-13-generic N/A linux-firmware1.104 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to raring on 2013-03-13 (9 days ago) dmi.bios.date: 01/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: 890FX Deluxe4 dmi.board.vendor: ASRock 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.:bvrP1.70:bd01/09/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn890FXDeluxe4:rvr: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1159219/+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 1208532] Re: put_page failures with 3.8.0-27.40
** Changed in: linux (Ubuntu) Status: In Progress => 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/1208532 Title: put_page failures with 3.8.0-27.40 Status in “linux” package in Ubuntu: Incomplete Bug description: Since update to 3.8.0-27.40 kernel I have been seeing these errors on an almost daily basis. I run two Windows Server 2012 instances under KVM. One or both of the Windows instances will disconnect from the network when this error happens and will not reconnect until I reboot Windows. Linux seems to recover silently on its own. Running on an HP Z600 Workstation with ECC RAM (memory issue is very unlikely). Scanned the boot/swap HDD for errors with Seagate SeaTools, no issues found. 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.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: greg 3352 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Aug 5 09:44:31 2013 HibernationDevice: RESUME=UUID=94c635e6-8245-4fe1-8c93-432c8d10dbd1 InstallationDate: Installed on 2012-02-14 (538 days ago) InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 (20111011) MachineType: Hewlett-Packard HP Z600 Workstation MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-27-generic root=/dev/mapper/mizuno-root ro RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to raring on 2013-04-25 (101 days ago) dmi.bios.date: 11/02/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G4 v03.54 dmi.board.asset.tag: 2UA00605JK dmi.board.name: 0AE8h dmi.board.vendor: Hewlett-Packard dmi.board.version: C dmi.chassis.asset.tag: 2UA00605JK dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G4v03.54:bd11/02/2011:svnHewlett-Packard:pnHPZ600Workstation:pvr:rvnHewlett-Packard:rn0AE8h:rvrC:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Z600 Workstation dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208532/+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 1219368] Re: 14e4:4320 Airport Extreme (Broadcom BCM4306) not working on iMac G5
** Changed in: linux (Ubuntu) Status: In Progress => 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/1219368 Title: 14e4:4320 Airport Extreme (Broadcom BCM4306) not working on iMac G5 Status in “linux” package in Ubuntu: Incomplete Bug description: wlan0 worked approximately 3 months ago, when I last booted this system, but upon updating and rebooting, my wireless NIC stopped working. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-52-powerpc64-smp 3.2.0-52.78 ProcVersionSignature: Ubuntu 3.2.0-52.78-powerpc64-smp 3.2.48 Uname: Linux 3.2.0-52-powerpc64-smp ppc64 AcpiTables: AlsaDevices: total 0 crw-rw---T+ 1 root audio 116, 1 Aug 31 22:51 seq crw-rw---T+ 1 root audio 116, 33 Aug 31 22:51 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: aplay: device_list:252: no soundcards found... ApportVersion: 2.0.1-0ubuntu17.4 Architecture: powerpc ArecordDevices: arecord: device_list:252: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 146.992985] [drm] nouveau :f0:10.0: Pixel clock comparison table not found Date: Sat Aug 31 22:54:17 2013 HibernationDevice: RESUME=UUID=b408cf63-ff5f-4a59-936e-86a765d55f66 InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release powerpc (20120423.1) MarkForUpload: True PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: root=UUID=d0b20cde-d75e-45ce-8b9c-c958416c59bd ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.2.0-52-powerpc64-smp N/A linux-backports-modules-3.2.0-52-powerpc64-smp N/A linux-firmware 1.79.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1219368/+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 1235110] Re: boot parameter "cgroup_disable=memory"
The 3.12 final kernel is now available. Can you test this kernel to see if the bug still exists in mainline: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-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/1235110 Title: boot parameter "cgroup_disable=memory" Status in “linux” package in Ubuntu: Confirmed Bug description: Glancing at dmesg, i'm testing that boot parameter, but got surprised about the result: [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.11.0-11-generic root=UUID=9e61e83e-bca9-43cf-aa90-5a68892213fa ro crashkernel=384M-2G:64M,2G-:128M cgroup_disable=memory [0.00] Disabling memory control group subsystem so it seems working; but later i'm seeing: [0.008534] Initializing cgroup subsys memory [0.008590] Initializing cgroup subsys devices [0.008636] Initializing cgroup subsys freezer [0.008682] Initializing cgroup subsys blkio [0.008728] Initializing cgroup subsys perf_event [0.008776] Initializing cgroup subsys hugetlb thats making me confused; i was beleiving that all these processes been replaced by zram process inside the recent kernels. Am i wrong ? ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-11-generic 3.11.0-11.17 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem3186 F pulseaudio Date: Fri Oct 4 09:14:52 2013 HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16 IwConfig: lono wireless extensions. eth0 no wireless extensions. eth1 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-11-generic root=UUID=9e61e83e-bca9-43cf-aa90-5a68892213fa ro crashkernel=384M-2G:64M,2G-:128M cgroup_disable=memory RelatedPackageVersions: linux-restricted-modules-3.11.0-11-generic N/A linux-backports-modules-3.11.0-11-generic N/A linux-firmware 1.116 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: Oct 4 07:33:37 oem-desktop kernel: [ 1030.311038] perf samples too long (2513 > 2500), lowering kernel.perf_event_max_sample_rate to 5 Oct 4 07:37:32 oem-desktop kernel: [ 1265.386172] midori[20822]: segfault at 4 ip b4b7d649 sp bfe32fb0 error 4 in libjavascriptcoregtk-3.0.so.0.13.16[b4a2c000+4e8000] Oct 4 07:39:24 oem-desktop kernel: [ 1377.706293] midori[20917]: segfault at 4 ip b4b82649 sp bff64650 error 4 in libjavascriptcoregtk-3.0.so.0.13.16[b4a31000+4e8000] dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.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.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1247647] Re: Kernel oops during btrfs access
I will try. Didn't do kernel tweaks for a long time. Mit freundlichen Grüßen Gregor Suhr On Mon, Nov 4, 2013 at 9:20 PM, Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > We can perform a kernel bisect to try and identify the commit that > introduced this regression. Would you be able to install some test > kernels on this machine? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1247647 > > Title: > Kernel oops during btrfs access > > Status in “linux” package in Ubuntu: > Confirmed > > Bug description: > cat /proc/version_signature > Ubuntu 3.11.0-12.19-generic 3.11.3 > > > root@ubuntunas:~# sudo lspci -vnvn > 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC > [Natoma] [8086:1237] (rev 02) > Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100] > Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR- FastB2B- DisINTx- > Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- > SERR- > 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA > [Natoma/Triton II] [8086:7000] > Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100] > Physical Slot: 1 > Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR- FastB2B- DisINTx- > Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- > SERR- > 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE > [Natoma/Triton II] [8086:7010] (prog-if 80 [Master]) > Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100] > Physical Slot: 1 > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR- FastB2B- DisINTx- > Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > SERR- Latency: 0 > Region 0: [virtual] Memory at 01f0 (32-bit, non-prefetchable) > [size=8] > Region 1: [virtual] Memory at 03f0 (type 3, non-prefetchable) > [size=1] > Region 2: [virtual] Memory at 0170 (32-bit, non-prefetchable) > [size=8] > Region 3: [virtual] Memory at 0370 (type 3, non-prefetchable) > [size=1] > Region 4: I/O ports at c160 [size=16] > Kernel driver in use: ata_piix > > 00:01.2 USB controller [0c03]: Intel Corporation 82371SB PIIX3 USB > [Natoma/Triton II] [8086:7020] (rev 01) (prog-if 00 [UHCI]) > Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100] > Physical Slot: 1 > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR- FastB2B- DisINTx- > Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- > SERR- Latency: 0 > Interrupt: pin D routed to IRQ 11 > Region 4: I/O ports at c100 [size=32] > Kernel driver in use: uhci_hcd > > 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI > [8086:7113] (rev 03) > Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100] > Physical Slot: 1 > Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR- FastB2B- DisINTx- > Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > SERR- Interrupt: pin A routed to IRQ 9 > Kernel driver in use: piix4_smbus > > 00:02.0 VGA compatible controller [0300]: Cirrus Logic GD 5446 > [1013:00b8] (prog-if 00 [VGA controller]) > Subsystem: Red Hat, Inc Device [1af4:1100] > Physical Slot: 2 > Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR- FastB2B- DisINTx- > Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- > SERR- Region 0: Memory at fc00 (32-bit, prefetchable) [size=32M] > Region 1: Memory at febf (32-bit, non-prefetchable) [size=4K] > Expansion ROM at febd [disabled] [size=64K] > Kernel driver in use: cirrus > > 00:03.0 Ethernet controller [0200]: Red Hat, Inc Virtio network device > [1af4:1000] > Subsystem: Red Hat, Inc Device [1af4:0001] > Physical Slot: 3 > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR- FastB2B- DisINTx+ > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- > SERR- Latency: 0 > Interrupt: pin A routed to IRQ 10 > Region 0: I/O ports at c120 [size=32] > Region 1: Memory at febf1000 (32-bit, non-prefetchable) [size=4K] > Expansion ROM at febe [disabled] [size=64K] > Capabilities: [40] MSI-X: Enable+ Count=3 Masked- > Vector table: BAR=1 offset= > PBA: BAR=1 offset=0800 > Kernel driver in use: virtio-pci > > 00:04.0 SCSI storage controller [0100]: Red Hat, Inc Virtio block device > [1af4:1001] > Subsystem: Red Hat, Inc Device [1af4:0002] >
[Kernel-packages] [Bug 1242938] Re: 13.10: Kernel panic - not syncing (on system start)
Tested this version and it did not have the bug. -- 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/1242938 Title: 13.10: Kernel panic - not syncing (on system start) Status in “linux” package in Ubuntu: Confirmed Bug description: If i start ubuntu 13.10 i always get the error (see attached picture). This happens if i start via live-usb stick and after normal update from 13.04 to 13.10 within ubuntu. The same usb-live stick works on another computer without any errors. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubuntu-release-upgrader-core 1:0.205 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic i686 ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 CrashDB: ubuntu Date: Tue Oct 22 00:31:43 2013 InstallationDate: Installed on 2013-08-05 (77 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release i386 (20130424) MarkForUpload: True PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to saucy on 2013-10-20 (0 days ago) VarLogDistupgradeTermlog: --- ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fabian 1845 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=411d36d6-4f07-4f5b-a060-18096ace08de InstallationDate: Installed on 2013-08-05 (79 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: Medion P8610 MarkForUpload: True Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-31-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: saucy Uname: Linux 3.8.0-31-generic i686 UpgradeStatus: Upgraded to saucy on 2013-10-20 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 11/28/2008 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: M1.04 dmi.board.name: P8610 dmi.board.vendor: Medion dmi.board.version: REFERENCE dmi.chassis.type: 10 dmi.chassis.vendor: Medion dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrM1.04:bd11/28/2008:svnMedion:pnP8610:pvrREFERENCE:rvnMedion:rnP8610:rvrREFERENCE:cvnMedion:ct10:cvr: dmi.product.name: P8610 dmi.product.version: REFERENCE dmi.sys.vendor: Medion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242938/+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
