[Kernel-packages] [Bug 1259846] [NEW] "Lost connection" errors due to failure of handling EINTR correctly
Public bug reported: Hello guys! We have got this bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715065 in ubuntu "precise" Our strace: pid 20763] write(7, "0\3\0\0\3SELECT mc.cid\n FROM ... mc\n ... LIMIT 120 OFFSET 0", 820 [pid 20763] <... write resumed> ) = 820 [pid 20763] read(7, [pid 20763] <... read resumed> 0x9b87ba0, 16384) = -1 EINTR (Interrupted system call) [pid 20763] --- SIGCHLD (Child exited) @ 0 (0) --- [pid 20763] rt_sigreturn(0 [pid 20763] <... rt_sigreturn resumed> ) = -1 EINTR (Interrupted system call) [pid 20763] shutdown(7, 2 /* send and receive */ [pid 20763] <... shutdown resumed> )= 0 [pid 20763] close(7 [pid 20763] <... close resumed> ) = 0 [pid 20763] write(2, "DBD::mysql::st execute failed: Lost connection to MySQL server during query at /usr/share/perl5/Yandex/DBTools.pm line 814.\n", 124DBD::mysql::st execute failed: Lost ackage: libmysqlclient18 Source: percona-server-5.5 Version: 1:5.5.34-rel32.0-591.precise Architecture: amd64 Maintainer: Percona Server Development Team Installed-Size: 3103 Replaces: libpercona-server-client18 Homepage: http://www.percona.com/software/percona-server/ Priority: extra Section: libs Filename: pool/main/p/percona-server-5.5/libmysqlclient18_5.5.34-rel32.0-591.precise_amd64.deb Size: 840708 SHA256: fbff998bf2d9c13a58e019600954765a037ca8f9da80847fd6cee68bba462579 SHA1: cc71b36386c0e1a5b532647fb9dc1314dd376036 MD5sum: 3cc1f960a217d6ac6f7f184c81a38272 Description: Percona Server database client library Percona Server is a fast, stable and true multi-user, multi-threaded SQL database server. SQL (Structured Query Language) is the most popular database query language in the world. The main goals of Percona Server are speed, robustness and ease of use. . This package includes the client library. # cat /proc/version Linux version 2.6.32-042stab076.5 (root@rh6-build-x64) (gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Mon Mar 18 20:41:34 MSK 2013 #lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 12.04.1 LTS Release:12.04 Codename: precise ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: mysql precise 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/1259846 Title: "Lost connection" errors due to failure of handling EINTR correctly Status in “linux” package in Ubuntu: Incomplete Bug description: Hello guys! We have got this bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715065 in ubuntu "precise" Our strace: pid 20763] write(7, "0\3\0\0\3SELECT mc.cid\n FROM ... mc\n ... LIMIT 120 OFFSET 0", 820 [pid 20763] <... write resumed> ) = 820 [pid 20763] read(7, [pid 20763] <... read resumed> 0x9b87ba0, 16384) = -1 EINTR (Interrupted system call) [pid 20763] --- SIGCHLD (Child exited) @ 0 (0) --- [pid 20763] rt_sigreturn(0 [pid 20763] <... rt_sigreturn resumed> ) = -1 EINTR (Interrupted system call) [pid 20763] shutdown(7, 2 /* send and receive */ [pid 20763] <... shutdown resumed> )= 0 [pid 20763] close(7 [pid 20763] <... close resumed> ) = 0 [pid 20763] write(2, "DBD::mysql::st execute failed: Lost connection to MySQL server during query at /usr/share/perl5/Yandex/DBTools.pm line 814.\n", 124DBD::mysql::st execute failed: Lost ackage: libmysqlclient18 Source: percona-server-5.5 Version: 1:5.5.34-rel32.0-591.precise Architecture: amd64 Maintainer: Percona Server Development Team Installed-Size: 3103 Replaces: libpercona-server-client18 Homepage: http://www.percona.com/software/percona-server/ Priority: extra Section: libs Filename: pool/main/p/percona-server-5.5/libmysqlclient18_5.5.34-rel32.0-591.precise_amd64.deb Size: 840708 SHA256: fbff998bf2d9c13a58e019600954765a037ca8f9da80847fd6cee68bba462579 SHA1: cc71b36386c0e1a5b532647fb9dc1314dd376036 MD5sum: 3cc1f960a217d6ac6f7f184c81a38272 Description: Percona Server database client library Percona Server is a fast, stable and true multi-user, multi-threaded SQL database server. SQL (Structured Query Language) is the most popular database query language in the world. The main goals of Percona Server are speed, robustness and ease of use. . This package includes the client library. # cat /proc/version Linux version 2.6.32-042stab076.5 (root@rh6-build-x64) (gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Mon Mar 18 20:41:34 MSK 2013 #lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 12.04.1 LTS Release:12.04 Codename: precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259846/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 1259846] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1259846 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: precise -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1259846 Title: "Lost connection" errors due to failure of handling EINTR correctly Status in “linux” package in Ubuntu: Incomplete Bug description: Hello guys! We have got this bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715065 in ubuntu "precise" Our strace: pid 20763] write(7, "0\3\0\0\3SELECT mc.cid\n FROM ... mc\n ... LIMIT 120 OFFSET 0", 820 [pid 20763] <... write resumed> ) = 820 [pid 20763] read(7, [pid 20763] <... read resumed> 0x9b87ba0, 16384) = -1 EINTR (Interrupted system call) [pid 20763] --- SIGCHLD (Child exited) @ 0 (0) --- [pid 20763] rt_sigreturn(0 [pid 20763] <... rt_sigreturn resumed> ) = -1 EINTR (Interrupted system call) [pid 20763] shutdown(7, 2 /* send and receive */ [pid 20763] <... shutdown resumed> )= 0 [pid 20763] close(7 [pid 20763] <... close resumed> ) = 0 [pid 20763] write(2, "DBD::mysql::st execute failed: Lost connection to MySQL server during query at /usr/share/perl5/Yandex/DBTools.pm line 814.\n", 124DBD::mysql::st execute failed: Lost ackage: libmysqlclient18 Source: percona-server-5.5 Version: 1:5.5.34-rel32.0-591.precise Architecture: amd64 Maintainer: Percona Server Development Team Installed-Size: 3103 Replaces: libpercona-server-client18 Homepage: http://www.percona.com/software/percona-server/ Priority: extra Section: libs Filename: pool/main/p/percona-server-5.5/libmysqlclient18_5.5.34-rel32.0-591.precise_amd64.deb Size: 840708 SHA256: fbff998bf2d9c13a58e019600954765a037ca8f9da80847fd6cee68bba462579 SHA1: cc71b36386c0e1a5b532647fb9dc1314dd376036 MD5sum: 3cc1f960a217d6ac6f7f184c81a38272 Description: Percona Server database client library Percona Server is a fast, stable and true multi-user, multi-threaded SQL database server. SQL (Structured Query Language) is the most popular database query language in the world. The main goals of Percona Server are speed, robustness and ease of use. . This package includes the client library. # cat /proc/version Linux version 2.6.32-042stab076.5 (root@rh6-build-x64) (gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Mon Mar 18 20:41:34 MSK 2013 #lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 12.04.1 LTS Release:12.04 Codename: precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259846/+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 1259846] Re: "Lost connection" errors due to failure of handling EINTR correctly
What is that "apport-collect" ? I cant find it in repository. I work on remote server over ssh. # apport-collect bash: apport-collect: command not found # apt-cache search apport-collect # -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1259846 Title: "Lost connection" errors due to failure of handling EINTR correctly Status in “linux” package in Ubuntu: Confirmed Bug description: Hello guys! We have got this bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715065 in ubuntu "precise" Our strace: pid 20763] write(7, "0\3\0\0\3SELECT mc.cid\n FROM ... mc\n ... LIMIT 120 OFFSET 0", 820 [pid 20763] <... write resumed> ) = 820 [pid 20763] read(7, [pid 20763] <... read resumed> 0x9b87ba0, 16384) = -1 EINTR (Interrupted system call) [pid 20763] --- SIGCHLD (Child exited) @ 0 (0) --- [pid 20763] rt_sigreturn(0 [pid 20763] <... rt_sigreturn resumed> ) = -1 EINTR (Interrupted system call) [pid 20763] shutdown(7, 2 /* send and receive */ [pid 20763] <... shutdown resumed> )= 0 [pid 20763] close(7 [pid 20763] <... close resumed> ) = 0 [pid 20763] write(2, "DBD::mysql::st execute failed: Lost connection to MySQL server during query at /usr/share/perl5/Yandex/DBTools.pm line 814.\n", 124DBD::mysql::st execute failed: Lost ackage: libmysqlclient18 Source: percona-server-5.5 Version: 1:5.5.34-rel32.0-591.precise Architecture: amd64 Maintainer: Percona Server Development Team Installed-Size: 3103 Replaces: libpercona-server-client18 Homepage: http://www.percona.com/software/percona-server/ Priority: extra Section: libs Filename: pool/main/p/percona-server-5.5/libmysqlclient18_5.5.34-rel32.0-591.precise_amd64.deb Size: 840708 SHA256: fbff998bf2d9c13a58e019600954765a037ca8f9da80847fd6cee68bba462579 SHA1: cc71b36386c0e1a5b532647fb9dc1314dd376036 MD5sum: 3cc1f960a217d6ac6f7f184c81a38272 Description: Percona Server database client library Percona Server is a fast, stable and true multi-user, multi-threaded SQL database server. SQL (Structured Query Language) is the most popular database query language in the world. The main goals of Percona Server are speed, robustness and ease of use. . This package includes the client library. # cat /proc/version Linux version 2.6.32-042stab076.5 (root@rh6-build-x64) (gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Mon Mar 18 20:41:34 MSK 2013 #lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 12.04.1 LTS Release:12.04 Codename: precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259846/+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 1259846] Re: "Lost connection" errors due to failure of handling EINTR correctly
Ok, I found this app.. ** 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/1259846 Title: "Lost connection" errors due to failure of handling EINTR correctly Status in “linux” package in Ubuntu: Confirmed Bug description: Hello guys! We have got this bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715065 in ubuntu "precise" Our strace: pid 20763] write(7, "0\3\0\0\3SELECT mc.cid\n FROM ... mc\n ... LIMIT 120 OFFSET 0", 820 [pid 20763] <... write resumed> ) = 820 [pid 20763] read(7, [pid 20763] <... read resumed> 0x9b87ba0, 16384) = -1 EINTR (Interrupted system call) [pid 20763] --- SIGCHLD (Child exited) @ 0 (0) --- [pid 20763] rt_sigreturn(0 [pid 20763] <... rt_sigreturn resumed> ) = -1 EINTR (Interrupted system call) [pid 20763] shutdown(7, 2 /* send and receive */ [pid 20763] <... shutdown resumed> )= 0 [pid 20763] close(7 [pid 20763] <... close resumed> ) = 0 [pid 20763] write(2, "DBD::mysql::st execute failed: Lost connection to MySQL server during query at /usr/share/perl5/Yandex/DBTools.pm line 814.\n", 124DBD::mysql::st execute failed: Lost ackage: libmysqlclient18 Source: percona-server-5.5 Version: 1:5.5.34-rel32.0-591.precise Architecture: amd64 Maintainer: Percona Server Development Team Installed-Size: 3103 Replaces: libpercona-server-client18 Homepage: http://www.percona.com/software/percona-server/ Priority: extra Section: libs Filename: pool/main/p/percona-server-5.5/libmysqlclient18_5.5.34-rel32.0-591.precise_amd64.deb Size: 840708 SHA256: fbff998bf2d9c13a58e019600954765a037ca8f9da80847fd6cee68bba462579 SHA1: cc71b36386c0e1a5b532647fb9dc1314dd376036 MD5sum: 3cc1f960a217d6ac6f7f184c81a38272 Description: Percona Server database client library Percona Server is a fast, stable and true multi-user, multi-threaded SQL database server. SQL (Structured Query Language) is the most popular database query language in the world. The main goals of Percona Server are speed, robustness and ease of use. . This package includes the client library. # cat /proc/version Linux version 2.6.32-042stab076.5 (root@rh6-build-x64) (gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Mon Mar 18 20:41:34 MSK 2013 #lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 12.04.1 LTS Release:12.04 Codename: precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259846/+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 1259850] [NEW] KDE powermanagement crashes kernel
Public bug reported: I have a Dell Latitude D6510 running (K)ubuntu 13.10 with the current kernel (3.11.0-14). In KDE when I pull the power cord, the system instantly freezes - completely, leaving no helpful traces of the cause in syslog or pm-powersave.log. It does not happen w/o a running KDE session or when I switch to Unity or XFCE. Hence, I suspect KDE triggering the bug. Googling for "power unplug crash linux kernel" yields a bunch of somewhat similiar issues, but those all seem slightly diffrent from what I see. In fact, I have had the/an "unplug crash issue" before like a year or so ago. Somehow it vanished, and now it is back again, so this could be a kernel regression. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-bug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1259850 Title: KDE powermanagement crashes kernel Status in “linux” package in Ubuntu: New Bug description: I have a Dell Latitude D6510 running (K)ubuntu 13.10 with the current kernel (3.11.0-14). In KDE when I pull the power cord, the system instantly freezes - completely, leaving no helpful traces of the cause in syslog or pm-powersave.log. It does not happen w/o a running KDE session or when I switch to Unity or XFCE. Hence, I suspect KDE triggering the bug. Googling for "power unplug crash linux kernel" yields a bunch of somewhat similiar issues, but those all seem slightly diffrent from what I see. In fact, I have had the/an "unplug crash issue" before like a year or so ago. Somehow it vanished, and now it is back again, so this could be a kernel regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259850/+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 1259850] Re: KDE powermanagement crashes kernel
** Package changed: linux-meta (Ubuntu) => linux (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/1259850 Title: KDE powermanagement crashes kernel Status in “linux” package in Ubuntu: New Bug description: I have a Dell Latitude D6510 running (K)ubuntu 13.10 with the current kernel (3.11.0-14). In KDE when I pull the power cord, the system instantly freezes - completely, leaving no helpful traces of the cause in syslog or pm-powersave.log. It does not happen w/o a running KDE session or when I switch to Unity or XFCE. Hence, I suspect KDE triggering the bug. Googling for "power unplug crash linux kernel" yields a bunch of somewhat similiar issues, but those all seem slightly diffrent from what I see. In fact, I have had the/an "unplug crash issue" before like a year or so ago. Somehow it vanished, and now it is back again, so this could be a kernel regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259850/+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 1259861] [NEW] 5-10 second delay in kernel boot
Public bug reported: In Trusty I see a big delay while the kernel boots that I did not see back in Precise. Some people have been experiencing this in Saucy too, so I don't know exactly when it started happening. Excerpt from dmesg: [3.740100] Switched to clocksource tsc [ 14.208118] PM: Hibernation image not present or could not be loaded. [ 14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000) The exact messages above don't matter, they are different on different boots or on different machines. It even happens with e.g. $ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso My current kernel is Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 i686 i686 GNU/Linux ...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run `dmesg` yourself and check if there's a big delay there. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1259861 Title: 5-10 second delay in kernel boot Status in “linux” package in Ubuntu: Incomplete Bug description: In Trusty I see a big delay while the kernel boots that I did not see back in Precise. Some people have been experiencing this in Saucy too, so I don't know exactly when it started happening. Excerpt from dmesg: [3.740100] Switched to clocksource tsc [ 14.208118] PM: Hibernation image not present or could not be loaded. [ 14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000) The exact messages above don't matter, they are different on different boots or on different machines. It even happens with e.g. $ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso My current kernel is Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 i686 i686 GNU/Linux ...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run `dmesg` yourself and check if there's a big delay there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259861/+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 1259850] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1259850 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/1259850 Title: KDE powermanagement crashes kernel Status in “linux” package in Ubuntu: Incomplete Bug description: I have a Dell Latitude D6510 running (K)ubuntu 13.10 with the current kernel (3.11.0-14). In KDE when I pull the power cord, the system instantly freezes - completely, leaving no helpful traces of the cause in syslog or pm-powersave.log. It does not happen w/o a running KDE session or when I switch to Unity or XFCE. Hence, I suspect KDE triggering the bug. Googling for "power unplug crash linux kernel" yields a bunch of somewhat similiar issues, but those all seem slightly diffrent from what I see. In fact, I have had the/an "unplug crash issue" before like a year or so ago. Somehow it vanished, and now it is back again, so this could be a kernel regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259850/+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 1259861] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1259861 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1259861 Title: 5-10 second delay in kernel boot Status in “linux” package in Ubuntu: Incomplete Bug description: In Trusty I see a big delay while the kernel boots that I did not see back in Precise. Some people have been experiencing this in Saucy too, so I don't know exactly when it started happening. Excerpt from dmesg: [3.740100] Switched to clocksource tsc [ 14.208118] PM: Hibernation image not present or could not be loaded. [ 14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000) The exact messages above don't matter, they are different on different boots or on different machines. It even happens with e.g. $ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso My current kernel is Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 i686 i686 GNU/Linux ...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run `dmesg` yourself and check if there's a big delay there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259861/+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 1259829] Re: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name
apport information ** Tags added: apport-collected staging ** Description changed: fs goes into read-only mode while build lo $ dmesg ... [ 2045.473249] virbr0: port 1(vnet0) entered forwarding state [ 2045.473283] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready [10660.961381] perf samples too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 5 [11822.935891] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 [11822.935896] Aborting journal on device dm-1-8. [11822.935998] EXT4-fs (dm-1): Remounting filesystem read-only [11822.960425] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629605: block 214443466: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2707156714, rec_len=19312, name_len=162 [11850.985003] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629557: block 214443458: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=512948573, rec_len=8858, name_len=176 [11850.985276] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629465: block 214443455: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=160939375, rec_len=26085, name_len=126 [11850.985499] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629325: block 214443451: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2322664969, rec_len=33791, name_len=132 [11850.985927] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629467: block 214443456: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=954332768, rec_len=21653, name_len=30 [11850.986409] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629074: block 214443433: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2061605548, rec_len=4984, name_len=3 [11850.986831] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53628835: block 214443432: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=3523041938, rec_len=53167, name_len=41 [11850.987001] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629098: block 214443436: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4225920287, rec_len=35138, name_len=75 [11850.987466] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629275: block 214443449: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=923253145, rec_len=44001, name_len=144 [11850.988115] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629270: block 214443448: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1892288796, rec_len=55247, name_len=58 [11851.042303] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629300: block 214443450: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=1809316884, rec_len=4208, name_len=195 [11851.042938] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629401: block 214443453: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4223616103, rec_len=36326, name_len=130 [11851.045745] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629406: block 214443454: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=415237227, rec_len=24702, name_len=59 [11851.125849] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629101: block 214443437: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=23292377, rec_len=28820, name_len=135 [11851.126086] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629543: block 214443457: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2624043515, rec_len=58633, name_len=250 [11851.126292] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629244: block 214443446: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=194839831, rec_len=15430, name_len=123 [11851.126529] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629345: block 214443452: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=3316601052, rec_len=49124, name_len=10 [11851.126751] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629080: block 214443434: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2978861680, rec_len=55340, name_len=75 [11851.127326] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629254: block 214443447: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2927900409, rec_len=17708, name_len=67 [1
[Kernel-packages] [Bug 1259829] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1259829/+attachment/3927436/+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/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 Status in “linux” package in Ubuntu: Incomplete Bug description: fs goes into read-only mode while build lo $ dmesg ... [ 2045.473249] virbr0: port 1(vnet0) entered forwarding state [ 2045.473283] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready [10660.961381] perf samples too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 5 [11822.935891] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 [11822.935896] Aborting journal on device dm-1-8. [11822.935998] EXT4-fs (dm-1): Remounting filesystem read-only [11822.960425] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629605: block 214443466: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2707156714, rec_len=19312, name_len=162 [11850.985003] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629557: block 214443458: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=512948573, rec_len=8858, name_len=176 [11850.985276] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629465: block 214443455: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=160939375, rec_len=26085, name_len=126 [11850.985499] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629325: block 214443451: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2322664969, rec_len=33791, name_len=132 [11850.985927] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629467: block 214443456: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=954332768, rec_len=21653, name_len=30 [11850.986409] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629074: block 214443433: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2061605548, rec_len=4984, name_len=3 [11850.986831] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53628835: block 214443432: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=3523041938, rec_len=53167, name_len=41 [11850.987001] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629098: block 214443436: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4225920287, rec_len=35138, name_len=75 [11850.987466] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629275: block 214443449: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=923253145, rec_len=44001, name_len=144 [11850.988115] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629270: block 214443448: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1892288796, rec_len=55247, name_len=58 [11851.042303] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629300: block 214443450: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=1809316884, rec_len=4208, name_len=195 [11851.042938] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629401: block 214443453: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4223616103, rec_len=36326, name_len=130 [11851.045745] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629406: block 214443454: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=415237227, rec_len=24702, name_len=59 [11851.125849] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629101: block 214443437: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=23292377, rec_len=28820, name_len=135 [11851.126086] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629543: block 214443457: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2624043515, rec_len=58633, name_len=250 [11851.126292] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629244: block 214443446: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=194839831, rec_len=15430, name_len=123 [11851.126529] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629345: block 214443452: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=3316601052, rec_len=49124, name_
[Kernel-packages] [Bug 1259829] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1259829/+attachment/3927438/+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/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 Status in “linux” package in Ubuntu: Incomplete Bug description: fs goes into read-only mode while build lo $ dmesg ... [ 2045.473249] virbr0: port 1(vnet0) entered forwarding state [ 2045.473283] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready [10660.961381] perf samples too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 5 [11822.935891] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 [11822.935896] Aborting journal on device dm-1-8. [11822.935998] EXT4-fs (dm-1): Remounting filesystem read-only [11822.960425] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629605: block 214443466: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2707156714, rec_len=19312, name_len=162 [11850.985003] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629557: block 214443458: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=512948573, rec_len=8858, name_len=176 [11850.985276] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629465: block 214443455: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=160939375, rec_len=26085, name_len=126 [11850.985499] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629325: block 214443451: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2322664969, rec_len=33791, name_len=132 [11850.985927] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629467: block 214443456: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=954332768, rec_len=21653, name_len=30 [11850.986409] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629074: block 214443433: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2061605548, rec_len=4984, name_len=3 [11850.986831] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53628835: block 214443432: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=3523041938, rec_len=53167, name_len=41 [11850.987001] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629098: block 214443436: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4225920287, rec_len=35138, name_len=75 [11850.987466] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629275: block 214443449: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=923253145, rec_len=44001, name_len=144 [11850.988115] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629270: block 214443448: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1892288796, rec_len=55247, name_len=58 [11851.042303] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629300: block 214443450: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=1809316884, rec_len=4208, name_len=195 [11851.042938] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629401: block 214443453: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4223616103, rec_len=36326, name_len=130 [11851.045745] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629406: block 214443454: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=415237227, rec_len=24702, name_len=59 [11851.125849] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629101: block 214443437: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=23292377, rec_len=28820, name_len=135 [11851.126086] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629543: block 214443457: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2624043515, rec_len=58633, name_len=250 [11851.126292] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629244: block 214443446: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=194839831, rec_len=15430, name_len=123 [11851.126529] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629345: block 214443452: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=3316601052, rec_len=49124, name_le
[Kernel-packages] [Bug 1259829] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1259829/+attachment/3927437/+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/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 Status in “linux” package in Ubuntu: Incomplete Bug description: fs goes into read-only mode while build lo $ dmesg ... [ 2045.473249] virbr0: port 1(vnet0) entered forwarding state [ 2045.473283] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready [10660.961381] perf samples too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 5 [11822.935891] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 [11822.935896] Aborting journal on device dm-1-8. [11822.935998] EXT4-fs (dm-1): Remounting filesystem read-only [11822.960425] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629605: block 214443466: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2707156714, rec_len=19312, name_len=162 [11850.985003] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629557: block 214443458: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=512948573, rec_len=8858, name_len=176 [11850.985276] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629465: block 214443455: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=160939375, rec_len=26085, name_len=126 [11850.985499] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629325: block 214443451: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2322664969, rec_len=33791, name_len=132 [11850.985927] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629467: block 214443456: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=954332768, rec_len=21653, name_len=30 [11850.986409] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629074: block 214443433: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2061605548, rec_len=4984, name_len=3 [11850.986831] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53628835: block 214443432: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=3523041938, rec_len=53167, name_len=41 [11850.987001] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629098: block 214443436: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4225920287, rec_len=35138, name_len=75 [11850.987466] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629275: block 214443449: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=923253145, rec_len=44001, name_len=144 [11850.988115] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629270: block 214443448: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1892288796, rec_len=55247, name_len=58 [11851.042303] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629300: block 214443450: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=1809316884, rec_len=4208, name_len=195 [11851.042938] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629401: block 214443453: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4223616103, rec_len=36326, name_len=130 [11851.045745] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629406: block 214443454: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=415237227, rec_len=24702, name_len=59 [11851.125849] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629101: block 214443437: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=23292377, rec_len=28820, name_len=135 [11851.126086] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629543: block 214443457: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2624043515, rec_len=58633, name_len=250 [11851.126292] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629244: block 214443446: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=194839831, rec_len=15430, name_len=123 [11851.126529] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629345: block 214443452: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=3316601052, rec_len=49124,
[Kernel-packages] [Bug 1259829] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1259829/+attachment/3927442/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 Status in “linux” package in Ubuntu: Incomplete Bug description: fs goes into read-only mode while build lo $ dmesg ... [ 2045.473249] virbr0: port 1(vnet0) entered forwarding state [ 2045.473283] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready [10660.961381] perf samples too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 5 [11822.935891] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 [11822.935896] Aborting journal on device dm-1-8. [11822.935998] EXT4-fs (dm-1): Remounting filesystem read-only [11822.960425] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629605: block 214443466: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2707156714, rec_len=19312, name_len=162 [11850.985003] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629557: block 214443458: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=512948573, rec_len=8858, name_len=176 [11850.985276] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629465: block 214443455: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=160939375, rec_len=26085, name_len=126 [11850.985499] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629325: block 214443451: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2322664969, rec_len=33791, name_len=132 [11850.985927] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629467: block 214443456: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=954332768, rec_len=21653, name_len=30 [11850.986409] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629074: block 214443433: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2061605548, rec_len=4984, name_len=3 [11850.986831] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53628835: block 214443432: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=3523041938, rec_len=53167, name_len=41 [11850.987001] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629098: block 214443436: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4225920287, rec_len=35138, name_len=75 [11850.987466] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629275: block 214443449: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=923253145, rec_len=44001, name_len=144 [11850.988115] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629270: block 214443448: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1892288796, rec_len=55247, name_len=58 [11851.042303] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629300: block 214443450: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=1809316884, rec_len=4208, name_len=195 [11851.042938] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629401: block 214443453: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4223616103, rec_len=36326, name_len=130 [11851.045745] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629406: block 214443454: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=415237227, rec_len=24702, name_len=59 [11851.125849] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629101: block 214443437: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=23292377, rec_len=28820, name_len=135 [11851.126086] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629543: block 214443457: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2624043515, rec_len=58633, name_len=250 [11851.126292] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629244: block 214443446: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=194839831, rec_len=15430, name_len=123 [11851.126529] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629345: block 214443452: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=3316601052, rec_len=49124, n
[Kernel-packages] [Bug 1259829] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1259829/+attachment/3927443/+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/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 Status in “linux” package in Ubuntu: Incomplete Bug description: fs goes into read-only mode while build lo $ dmesg ... [ 2045.473249] virbr0: port 1(vnet0) entered forwarding state [ 2045.473283] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready [10660.961381] perf samples too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 5 [11822.935891] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 [11822.935896] Aborting journal on device dm-1-8. [11822.935998] EXT4-fs (dm-1): Remounting filesystem read-only [11822.960425] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629605: block 214443466: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2707156714, rec_len=19312, name_len=162 [11850.985003] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629557: block 214443458: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=512948573, rec_len=8858, name_len=176 [11850.985276] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629465: block 214443455: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=160939375, rec_len=26085, name_len=126 [11850.985499] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629325: block 214443451: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2322664969, rec_len=33791, name_len=132 [11850.985927] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629467: block 214443456: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=954332768, rec_len=21653, name_len=30 [11850.986409] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629074: block 214443433: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2061605548, rec_len=4984, name_len=3 [11850.986831] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53628835: block 214443432: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=3523041938, rec_len=53167, name_len=41 [11850.987001] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629098: block 214443436: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4225920287, rec_len=35138, name_len=75 [11850.987466] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629275: block 214443449: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=923253145, rec_len=44001, name_len=144 [11850.988115] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629270: block 214443448: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1892288796, rec_len=55247, name_len=58 [11851.042303] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629300: block 214443450: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=1809316884, rec_len=4208, name_len=195 [11851.042938] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629401: block 214443453: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4223616103, rec_len=36326, name_len=130 [11851.045745] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629406: block 214443454: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=415237227, rec_len=24702, name_len=59 [11851.125849] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629101: block 214443437: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=23292377, rec_len=28820, name_len=135 [11851.126086] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629543: block 214443457: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2624043515, rec_len=58633, name_len=250 [11851.126292] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629244: block 214443446: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=194839831, rec_len=15430, name_len=123 [11851.126529] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629345: block 214443452: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=3316601052, rec_len=49
[Kernel-packages] [Bug 1259829] Re: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name
disabling "discard" option fixed this for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 Status in “linux” package in Ubuntu: Incomplete Bug description: fs goes into read-only mode while build lo $ dmesg ... [ 2045.473249] virbr0: port 1(vnet0) entered forwarding state [ 2045.473283] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready [10660.961381] perf samples too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 5 [11822.935891] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 [11822.935896] Aborting journal on device dm-1-8. [11822.935998] EXT4-fs (dm-1): Remounting filesystem read-only [11822.960425] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629605: block 214443466: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2707156714, rec_len=19312, name_len=162 [11850.985003] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629557: block 214443458: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=512948573, rec_len=8858, name_len=176 [11850.985276] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629465: block 214443455: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=160939375, rec_len=26085, name_len=126 [11850.985499] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629325: block 214443451: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2322664969, rec_len=33791, name_len=132 [11850.985927] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629467: block 214443456: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=954332768, rec_len=21653, name_len=30 [11850.986409] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629074: block 214443433: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2061605548, rec_len=4984, name_len=3 [11850.986831] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53628835: block 214443432: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=3523041938, rec_len=53167, name_len=41 [11850.987001] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629098: block 214443436: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4225920287, rec_len=35138, name_len=75 [11850.987466] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629275: block 214443449: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=923253145, rec_len=44001, name_len=144 [11850.988115] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629270: block 214443448: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1892288796, rec_len=55247, name_len=58 [11851.042303] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629300: block 214443450: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=1809316884, rec_len=4208, name_len=195 [11851.042938] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629401: block 214443453: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4223616103, rec_len=36326, name_len=130 [11851.045745] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629406: block 214443454: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=415237227, rec_len=24702, name_len=59 [11851.125849] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629101: block 214443437: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=23292377, rec_len=28820, name_len=135 [11851.126086] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629543: block 214443457: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2624043515, rec_len=58633, name_len=250 [11851.126292] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629244: block 214443446: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=194839831, rec_len=15430, name_len=123 [11851.126529] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629345: block 214443452: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=3316601052, rec_len=49124, name_len=10 [11851.126751] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #5362908
[Kernel-packages] [Bug 1259829] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1259829/+attachment/3927444/+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/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 Status in “linux” package in Ubuntu: Incomplete Bug description: fs goes into read-only mode while build lo $ dmesg ... [ 2045.473249] virbr0: port 1(vnet0) entered forwarding state [ 2045.473283] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready [10660.961381] perf samples too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 5 [11822.935891] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 [11822.935896] Aborting journal on device dm-1-8. [11822.935998] EXT4-fs (dm-1): Remounting filesystem read-only [11822.960425] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629605: block 214443466: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2707156714, rec_len=19312, name_len=162 [11850.985003] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629557: block 214443458: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=512948573, rec_len=8858, name_len=176 [11850.985276] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629465: block 214443455: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=160939375, rec_len=26085, name_len=126 [11850.985499] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629325: block 214443451: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2322664969, rec_len=33791, name_len=132 [11850.985927] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629467: block 214443456: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=954332768, rec_len=21653, name_len=30 [11850.986409] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629074: block 214443433: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2061605548, rec_len=4984, name_len=3 [11850.986831] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53628835: block 214443432: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=3523041938, rec_len=53167, name_len=41 [11850.987001] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629098: block 214443436: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4225920287, rec_len=35138, name_len=75 [11850.987466] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629275: block 214443449: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=923253145, rec_len=44001, name_len=144 [11850.988115] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629270: block 214443448: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1892288796, rec_len=55247, name_len=58 [11851.042303] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629300: block 214443450: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=1809316884, rec_len=4208, name_len=195 [11851.042938] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629401: block 214443453: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4223616103, rec_len=36326, name_len=130 [11851.045745] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629406: block 214443454: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=415237227, rec_len=24702, name_len=59 [11851.125849] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629101: block 214443437: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=23292377, rec_len=28820, name_len=135 [11851.126086] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629543: block 214443457: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2624043515, rec_len=58633, name_len=250 [11851.126292] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629244: block 214443446: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=194839831, rec_len=15430, name_len=123 [11851.126529] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629345: block 214443452: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=3316601052, rec_len=49124, n
[Kernel-packages] [Bug 1259829] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1259829/+attachment/3927441/+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/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 Status in “linux” package in Ubuntu: Incomplete Bug description: fs goes into read-only mode while build lo $ dmesg ... [ 2045.473249] virbr0: port 1(vnet0) entered forwarding state [ 2045.473283] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready [10660.961381] perf samples too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 5 [11822.935891] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 [11822.935896] Aborting journal on device dm-1-8. [11822.935998] EXT4-fs (dm-1): Remounting filesystem read-only [11822.960425] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629605: block 214443466: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2707156714, rec_len=19312, name_len=162 [11850.985003] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629557: block 214443458: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=512948573, rec_len=8858, name_len=176 [11850.985276] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629465: block 214443455: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=160939375, rec_len=26085, name_len=126 [11850.985499] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629325: block 214443451: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2322664969, rec_len=33791, name_len=132 [11850.985927] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629467: block 214443456: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=954332768, rec_len=21653, name_len=30 [11850.986409] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629074: block 214443433: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2061605548, rec_len=4984, name_len=3 [11850.986831] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53628835: block 214443432: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=3523041938, rec_len=53167, name_len=41 [11850.987001] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629098: block 214443436: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4225920287, rec_len=35138, name_len=75 [11850.987466] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629275: block 214443449: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=923253145, rec_len=44001, name_len=144 [11850.988115] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629270: block 214443448: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1892288796, rec_len=55247, name_len=58 [11851.042303] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629300: block 214443450: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=1809316884, rec_len=4208, name_len=195 [11851.042938] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629401: block 214443453: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4223616103, rec_len=36326, name_len=130 [11851.045745] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629406: block 214443454: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=415237227, rec_len=24702, name_len=59 [11851.125849] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629101: block 214443437: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=23292377, rec_len=28820, name_len=135 [11851.126086] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629543: block 214443457: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2624043515, rec_len=58633, name_len=250 [11851.126292] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629244: block 214443446: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=194839831, rec_len=15430, name_len=123 [11851.126529] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629345: block 214443452: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=3316601052, rec_len=49124, n
[Kernel-packages] [Bug 1259829] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1259829/+attachment/3927446/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 Status in “linux” package in Ubuntu: Incomplete Bug description: fs goes into read-only mode while build lo $ dmesg ... [ 2045.473249] virbr0: port 1(vnet0) entered forwarding state [ 2045.473283] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready [10660.961381] perf samples too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 5 [11822.935891] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 [11822.935896] Aborting journal on device dm-1-8. [11822.935998] EXT4-fs (dm-1): Remounting filesystem read-only [11822.960425] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629605: block 214443466: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2707156714, rec_len=19312, name_len=162 [11850.985003] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629557: block 214443458: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=512948573, rec_len=8858, name_len=176 [11850.985276] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629465: block 214443455: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=160939375, rec_len=26085, name_len=126 [11850.985499] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629325: block 214443451: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2322664969, rec_len=33791, name_len=132 [11850.985927] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629467: block 214443456: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=954332768, rec_len=21653, name_len=30 [11850.986409] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629074: block 214443433: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2061605548, rec_len=4984, name_len=3 [11850.986831] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53628835: block 214443432: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=3523041938, rec_len=53167, name_len=41 [11850.987001] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629098: block 214443436: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4225920287, rec_len=35138, name_len=75 [11850.987466] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629275: block 214443449: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=923253145, rec_len=44001, name_len=144 [11850.988115] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629270: block 214443448: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1892288796, rec_len=55247, name_len=58 [11851.042303] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629300: block 214443450: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=1809316884, rec_len=4208, name_len=195 [11851.042938] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629401: block 214443453: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4223616103, rec_len=36326, name_len=130 [11851.045745] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629406: block 214443454: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=415237227, rec_len=24702, name_len=59 [11851.125849] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629101: block 214443437: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=23292377, rec_len=28820, name_len=135 [11851.126086] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629543: block 214443457: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2624043515, rec_len=58633, name_len=250 [11851.126292] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629244: block 214443446: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=194839831, rec_len=15430, name_len=123 [11851.126529] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629345: block 214443452: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=3316601052, rec_len=49124, name_len=10
[Kernel-packages] [Bug 1259829] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1259829/+attachment/3927445/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 Status in “linux” package in Ubuntu: Incomplete Bug description: fs goes into read-only mode while build lo $ dmesg ... [ 2045.473249] virbr0: port 1(vnet0) entered forwarding state [ 2045.473283] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready [10660.961381] perf samples too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 5 [11822.935891] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 [11822.935896] Aborting journal on device dm-1-8. [11822.935998] EXT4-fs (dm-1): Remounting filesystem read-only [11822.960425] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629605: block 214443466: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2707156714, rec_len=19312, name_len=162 [11850.985003] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629557: block 214443458: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=512948573, rec_len=8858, name_len=176 [11850.985276] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629465: block 214443455: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=160939375, rec_len=26085, name_len=126 [11850.985499] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629325: block 214443451: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2322664969, rec_len=33791, name_len=132 [11850.985927] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629467: block 214443456: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=954332768, rec_len=21653, name_len=30 [11850.986409] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629074: block 214443433: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2061605548, rec_len=4984, name_len=3 [11850.986831] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53628835: block 214443432: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=3523041938, rec_len=53167, name_len=41 [11850.987001] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629098: block 214443436: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4225920287, rec_len=35138, name_len=75 [11850.987466] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629275: block 214443449: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=923253145, rec_len=44001, name_len=144 [11850.988115] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629270: block 214443448: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1892288796, rec_len=55247, name_len=58 [11851.042303] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629300: block 214443450: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=1809316884, rec_len=4208, name_len=195 [11851.042938] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629401: block 214443453: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4223616103, rec_len=36326, name_len=130 [11851.045745] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629406: block 214443454: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=415237227, rec_len=24702, name_len=59 [11851.125849] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629101: block 214443437: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=23292377, rec_len=28820, name_len=135 [11851.126086] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629543: block 214443457: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2624043515, rec_len=58633, name_len=250 [11851.126292] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629244: block 214443446: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=194839831, rec_len=15430, name_len=123 [11851.126529] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629345: block 214443452: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=3316601052, rec_len=49124, name_
[Kernel-packages] [Bug 1259829] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1259829/+attachment/3927440/+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/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 Status in “linux” package in Ubuntu: Incomplete Bug description: fs goes into read-only mode while build lo $ dmesg ... [ 2045.473249] virbr0: port 1(vnet0) entered forwarding state [ 2045.473283] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready [10660.961381] perf samples too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 5 [11822.935891] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 [11822.935896] Aborting journal on device dm-1-8. [11822.935998] EXT4-fs (dm-1): Remounting filesystem read-only [11822.960425] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629605: block 214443466: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2707156714, rec_len=19312, name_len=162 [11850.985003] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629557: block 214443458: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=512948573, rec_len=8858, name_len=176 [11850.985276] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629465: block 214443455: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=160939375, rec_len=26085, name_len=126 [11850.985499] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629325: block 214443451: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2322664969, rec_len=33791, name_len=132 [11850.985927] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629467: block 214443456: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=954332768, rec_len=21653, name_len=30 [11850.986409] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629074: block 214443433: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2061605548, rec_len=4984, name_len=3 [11850.986831] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53628835: block 214443432: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=3523041938, rec_len=53167, name_len=41 [11850.987001] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629098: block 214443436: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4225920287, rec_len=35138, name_len=75 [11850.987466] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629275: block 214443449: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=923253145, rec_len=44001, name_len=144 [11850.988115] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629270: block 214443448: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1892288796, rec_len=55247, name_len=58 [11851.042303] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629300: block 214443450: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=1809316884, rec_len=4208, name_len=195 [11851.042938] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629401: block 214443453: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4223616103, rec_len=36326, name_len=130 [11851.045745] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629406: block 214443454: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=415237227, rec_len=24702, name_len=59 [11851.125849] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629101: block 214443437: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=23292377, rec_len=28820, name_len=135 [11851.126086] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629543: block 214443457: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2624043515, rec_len=58633, name_len=250 [11851.126292] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629244: block 214443446: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=194839831, rec_len=15430, name_len=123 [11851.126529] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629345: block 214443452: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=3316601052, rec_len=49124, name_len=10
[Kernel-packages] [Bug 1259829] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1259829/+attachment/3927448/+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/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 Status in “linux” package in Ubuntu: Incomplete Bug description: fs goes into read-only mode while build lo $ dmesg ... [ 2045.473249] virbr0: port 1(vnet0) entered forwarding state [ 2045.473283] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready [10660.961381] perf samples too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 5 [11822.935891] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 [11822.935896] Aborting journal on device dm-1-8. [11822.935998] EXT4-fs (dm-1): Remounting filesystem read-only [11822.960425] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629605: block 214443466: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2707156714, rec_len=19312, name_len=162 [11850.985003] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629557: block 214443458: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=512948573, rec_len=8858, name_len=176 [11850.985276] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629465: block 214443455: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=160939375, rec_len=26085, name_len=126 [11850.985499] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629325: block 214443451: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2322664969, rec_len=33791, name_len=132 [11850.985927] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629467: block 214443456: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=954332768, rec_len=21653, name_len=30 [11850.986409] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629074: block 214443433: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2061605548, rec_len=4984, name_len=3 [11850.986831] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53628835: block 214443432: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=3523041938, rec_len=53167, name_len=41 [11850.987001] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629098: block 214443436: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4225920287, rec_len=35138, name_len=75 [11850.987466] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629275: block 214443449: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=923253145, rec_len=44001, name_len=144 [11850.988115] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629270: block 214443448: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1892288796, rec_len=55247, name_len=58 [11851.042303] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629300: block 214443450: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=1809316884, rec_len=4208, name_len=195 [11851.042938] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629401: block 214443453: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4223616103, rec_len=36326, name_len=130 [11851.045745] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629406: block 214443454: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=415237227, rec_len=24702, name_len=59 [11851.125849] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629101: block 214443437: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=23292377, rec_len=28820, name_len=135 [11851.126086] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629543: block 214443457: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2624043515, rec_len=58633, name_len=250 [11851.126292] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629244: block 214443446: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=194839831, rec_len=15430, name_len=123 [11851.126529] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629345: block 214443452: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=3316601052, rec_len=49124, name_len=
[Kernel-packages] [Bug 1259829] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1259829/+attachment/3927447/+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/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 Status in “linux” package in Ubuntu: Incomplete Bug description: fs goes into read-only mode while build lo $ dmesg ... [ 2045.473249] virbr0: port 1(vnet0) entered forwarding state [ 2045.473283] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready [10660.961381] perf samples too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 5 [11822.935891] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 [11822.935896] Aborting journal on device dm-1-8. [11822.935998] EXT4-fs (dm-1): Remounting filesystem read-only [11822.960425] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629605: block 214443466: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2707156714, rec_len=19312, name_len=162 [11850.985003] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629557: block 214443458: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=512948573, rec_len=8858, name_len=176 [11850.985276] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629465: block 214443455: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=160939375, rec_len=26085, name_len=126 [11850.985499] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629325: block 214443451: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2322664969, rec_len=33791, name_len=132 [11850.985927] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629467: block 214443456: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=954332768, rec_len=21653, name_len=30 [11850.986409] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629074: block 214443433: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2061605548, rec_len=4984, name_len=3 [11850.986831] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53628835: block 214443432: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=3523041938, rec_len=53167, name_len=41 [11850.987001] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629098: block 214443436: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4225920287, rec_len=35138, name_len=75 [11850.987466] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629275: block 214443449: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=923253145, rec_len=44001, name_len=144 [11850.988115] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629270: block 214443448: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1892288796, rec_len=55247, name_len=58 [11851.042303] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629300: block 214443450: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=1809316884, rec_len=4208, name_len=195 [11851.042938] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629401: block 214443453: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4223616103, rec_len=36326, name_len=130 [11851.045745] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629406: block 214443454: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=415237227, rec_len=24702, name_len=59 [11851.125849] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629101: block 214443437: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=23292377, rec_len=28820, name_len=135 [11851.126086] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629543: block 214443457: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2624043515, rec_len=58633, name_len=250 [11851.126292] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629244: block 214443446: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=194839831, rec_len=15430, name_len=123 [11851.126529] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629345: block 214443452: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=3316601052, rec_len=49124, name_len=10
[Kernel-packages] [Bug 1259829] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1259829/+attachment/3927439/+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/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 Status in “linux” package in Ubuntu: Incomplete Bug description: fs goes into read-only mode while build lo $ dmesg ... [ 2045.473249] virbr0: port 1(vnet0) entered forwarding state [ 2045.473283] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready [10660.961381] perf samples too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 5 [11822.935891] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 [11822.935896] Aborting journal on device dm-1-8. [11822.935998] EXT4-fs (dm-1): Remounting filesystem read-only [11822.960425] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629605: block 214443466: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2707156714, rec_len=19312, name_len=162 [11850.985003] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629557: block 214443458: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=512948573, rec_len=8858, name_len=176 [11850.985276] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629465: block 214443455: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=160939375, rec_len=26085, name_len=126 [11850.985499] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629325: block 214443451: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2322664969, rec_len=33791, name_len=132 [11850.985927] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629467: block 214443456: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=954332768, rec_len=21653, name_len=30 [11850.986409] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629074: block 214443433: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2061605548, rec_len=4984, name_len=3 [11850.986831] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53628835: block 214443432: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=3523041938, rec_len=53167, name_len=41 [11850.987001] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629098: block 214443436: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4225920287, rec_len=35138, name_len=75 [11850.987466] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629275: block 214443449: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=923253145, rec_len=44001, name_len=144 [11850.988115] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629270: block 214443448: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1892288796, rec_len=55247, name_len=58 [11851.042303] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629300: block 214443450: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=1809316884, rec_len=4208, name_len=195 [11851.042938] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629401: block 214443453: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4223616103, rec_len=36326, name_len=130 [11851.045745] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629406: block 214443454: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=415237227, rec_len=24702, name_len=59 [11851.125849] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629101: block 214443437: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=23292377, rec_len=28820, name_len=135 [11851.126086] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629543: block 214443457: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2624043515, rec_len=58633, name_len=250 [11851.126292] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629244: block 214443446: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=194839831, rec_len=15430, name_len=123 [11851.126529] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629345: block 214443452: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=3316601052, rec_len=49124, name_len=10
[Kernel-packages] [Bug 1237296] Re: ath9k QCA9565/AR9565/QCWB335 Bluetooth not working
rc3 and it still hasn't landed, I'm a bit depressed. Could you propably build a rc3 test kernel with patch applied, so I could test if something has changed? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1237296 Title: ath9k QCA9565/AR9565/QCWB335 Bluetooth not working 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: Hello, I got myself a brand new Acer Aspire E1-572-54204G50Mnkk, because of the shine new Haswell hardware I choose to install Ubuntu 13.10 Beta 2. This laptop uses a Atheros AR9565 802.11 b/g/n 1 × 1 WiFi + Bluetooth 4.0 combination adapter, Wireless is working fine. But Bluetooth doesn't, it seems to be successfully deteced but I can't see any other Bluetooth devices and they can't see me too. Yours sincerly Joshua --- ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-10-12 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) MarkForUpload: True Package: linux (not installed) ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: saucy Uname: Linux 3.12.0-031200rc4-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshua 1348 F pulseaudio /dev/snd/controlC0: joshua 1348 F pulseaudio DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-10-12 (8 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) MachineType: Acer Aspire E1-572 MarkForUpload: True Package: linux (not installed) ProcEnviron: LANGUAGE=de_DE 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.efi.signed root=UUID=287c8de2-616f-42ec-998d-1ac09ffb2d8a ro quiet splash vt.handoff=7 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 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/21/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HW dmi.board.vendor: Acer dmi.board.version: V2.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.04:bd05/21/2013:svnAcer:pnAspireE1-572:pvrV2.04:rvnAcer:rnEA50_HW:rvrV2.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.name: Aspire E1-572 dmi.product.version: V2.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237296/+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 1259850] Re: KDE powermanagement crashes kernel
apport information ** Tags added: apport-collected saucy ** Description changed: I have a Dell Latitude D6510 running (K)ubuntu 13.10 with the current kernel (3.11.0-14). In KDE when I pull the power cord, the system instantly freezes - completely, leaving no helpful traces of the cause in syslog or pm-powersave.log. It does not happen w/o a running KDE session or when I switch to Unity or XFCE. Hence, I suspect KDE triggering the bug. - Googling for "power unplug crash linux kernel" yields a bunch of - somewhat similiar issues, but those all seem slightly diffrent from what - I see. In fact, I have had the/an "unplug crash issue" before like a - year or so ago. Somehow it vanished, and now it is back again, so this - could be a kernel regression. + Googling for "power unplug crash linux kernel" yields a bunch of somewhat similiar issues, but those all seem slightly diffrent from what I see. In fact, I have had the/an "unplug crash issue" before like a year or so ago. Somehow it vanished, and now it is back again, so this could be a kernel regression. + --- + ApportVersion: 2.12.5-0ubuntu2.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: deas 6090 F pulseaudio + DistroRelease: Ubuntu 13.10 + EcryptfsInUse: Yes + HibernationDevice: RESUME=UUID=901a5939-36e9-4493-9f9d-68a6fea3613e + InstallationDate: Installed on 2011-03-07 (1009 days ago) + InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101008) + MachineType: Dell Inc. Latitude E6510 + MarkForUpload: True + Package: linux 3.11.0.14.15 + PackageArchitecture: amd64 + PccardctlIdent: + Socket 0: +no product info available + PccardctlStatus: + Socket 0: +no card + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 + RelatedPackageVersions: + linux-restricted-modules-3.11.0-14-generic N/A + linux-backports-modules-3.11.0-14-generic N/A + linux-firmware 1.116 + Tags: saucy + Uname: Linux 3.11.0-14-generic x86_64 + UpgradeStatus: Upgraded to saucy on 2013-10-17 (54 days ago) + UserGroups: adm admin cdrom dialout libvirtd lp lpadmin plugdev sambashare vboxusers + dmi.bios.date: 05/09/2012 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A12 + dmi.board.name: 02K3Y4 + dmi.board.vendor: Dell Inc. + dmi.board.version: A02 + dmi.chassis.type: 9 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/09/2012:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn02K3Y4:rvrA02:cvnDellInc.:ct9:cvr: + dmi.product.name: Latitude E6510 + dmi.product.version: 0001 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1259850/+attachment/3927465/+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/1259850 Title: KDE powermanagement crashes kernel Status in “linux” package in Ubuntu: Confirmed Bug description: I have a Dell Latitude D6510 running (K)ubuntu 13.10 with the current kernel (3.11.0-14). In KDE when I pull the power cord, the system instantly freezes - completely, leaving no helpful traces of the cause in syslog or pm-powersave.log. It does not happen w/o a running KDE session or when I switch to Unity or XFCE. Hence, I suspect KDE triggering the bug. Googling for "power unplug crash linux kernel" yields a bunch of somewhat similiar issues, but those all seem slightly diffrent from what I see. In fact, I have had the/an "unplug crash issue" before like a year or so ago. Somehow it vanished, and now it is back again, so this could be a kernel regression. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: deas 6090 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=901a5939-36e9-4493-9f9d-68a6fea3613e InstallationDate: Installed on 2011-03-07 (1009 days ago) InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101008) MachineType: Dell Inc. Latitude E6510 MarkForUpload: True Package: linux 3.11.0.14.15 PackageArchitecture: amd64 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded
[Kernel-packages] [Bug 1259850] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1259850/+attachment/3927471/+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/1259850 Title: KDE powermanagement crashes kernel Status in “linux” package in Ubuntu: Confirmed Bug description: I have a Dell Latitude D6510 running (K)ubuntu 13.10 with the current kernel (3.11.0-14). In KDE when I pull the power cord, the system instantly freezes - completely, leaving no helpful traces of the cause in syslog or pm-powersave.log. It does not happen w/o a running KDE session or when I switch to Unity or XFCE. Hence, I suspect KDE triggering the bug. Googling for "power unplug crash linux kernel" yields a bunch of somewhat similiar issues, but those all seem slightly diffrent from what I see. In fact, I have had the/an "unplug crash issue" before like a year or so ago. Somehow it vanished, and now it is back again, so this could be a kernel regression. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: deas 6090 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=901a5939-36e9-4493-9f9d-68a6fea3613e InstallationDate: Installed on 2011-03-07 (1009 days ago) InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101008) MachineType: Dell Inc. Latitude E6510 MarkForUpload: True Package: linux 3.11.0.14.15 PackageArchitecture: amd64 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (54 days ago) UserGroups: adm admin cdrom dialout libvirtd lp lpadmin plugdev sambashare vboxusers dmi.bios.date: 05/09/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 02K3Y4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/09/2012:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn02K3Y4:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259850/+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 1259850] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1259850/+attachment/3927469/+files/Dependencies.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/1259850 Title: KDE powermanagement crashes kernel Status in “linux” package in Ubuntu: Confirmed Bug description: I have a Dell Latitude D6510 running (K)ubuntu 13.10 with the current kernel (3.11.0-14). In KDE when I pull the power cord, the system instantly freezes - completely, leaving no helpful traces of the cause in syslog or pm-powersave.log. It does not happen w/o a running KDE session or when I switch to Unity or XFCE. Hence, I suspect KDE triggering the bug. Googling for "power unplug crash linux kernel" yields a bunch of somewhat similiar issues, but those all seem slightly diffrent from what I see. In fact, I have had the/an "unplug crash issue" before like a year or so ago. Somehow it vanished, and now it is back again, so this could be a kernel regression. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: deas 6090 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=901a5939-36e9-4493-9f9d-68a6fea3613e InstallationDate: Installed on 2011-03-07 (1009 days ago) InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101008) MachineType: Dell Inc. Latitude E6510 MarkForUpload: True Package: linux 3.11.0.14.15 PackageArchitecture: amd64 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (54 days ago) UserGroups: adm admin cdrom dialout libvirtd lp lpadmin plugdev sambashare vboxusers dmi.bios.date: 05/09/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 02K3Y4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/09/2012:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn02K3Y4:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259850/+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 1259850] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1259850/+attachment/3927468/+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/1259850 Title: KDE powermanagement crashes kernel Status in “linux” package in Ubuntu: Confirmed Bug description: I have a Dell Latitude D6510 running (K)ubuntu 13.10 with the current kernel (3.11.0-14). In KDE when I pull the power cord, the system instantly freezes - completely, leaving no helpful traces of the cause in syslog or pm-powersave.log. It does not happen w/o a running KDE session or when I switch to Unity or XFCE. Hence, I suspect KDE triggering the bug. Googling for "power unplug crash linux kernel" yields a bunch of somewhat similiar issues, but those all seem slightly diffrent from what I see. In fact, I have had the/an "unplug crash issue" before like a year or so ago. Somehow it vanished, and now it is back again, so this could be a kernel regression. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: deas 6090 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=901a5939-36e9-4493-9f9d-68a6fea3613e InstallationDate: Installed on 2011-03-07 (1009 days ago) InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101008) MachineType: Dell Inc. Latitude E6510 MarkForUpload: True Package: linux 3.11.0.14.15 PackageArchitecture: amd64 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (54 days ago) UserGroups: adm admin cdrom dialout libvirtd lp lpadmin plugdev sambashare vboxusers dmi.bios.date: 05/09/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 02K3Y4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/09/2012:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn02K3Y4:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259850/+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 1259850] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1259850/+attachment/3927466/+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/1259850 Title: KDE powermanagement crashes kernel Status in “linux” package in Ubuntu: Confirmed Bug description: I have a Dell Latitude D6510 running (K)ubuntu 13.10 with the current kernel (3.11.0-14). In KDE when I pull the power cord, the system instantly freezes - completely, leaving no helpful traces of the cause in syslog or pm-powersave.log. It does not happen w/o a running KDE session or when I switch to Unity or XFCE. Hence, I suspect KDE triggering the bug. Googling for "power unplug crash linux kernel" yields a bunch of somewhat similiar issues, but those all seem slightly diffrent from what I see. In fact, I have had the/an "unplug crash issue" before like a year or so ago. Somehow it vanished, and now it is back again, so this could be a kernel regression. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: deas 6090 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=901a5939-36e9-4493-9f9d-68a6fea3613e InstallationDate: Installed on 2011-03-07 (1009 days ago) InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101008) MachineType: Dell Inc. Latitude E6510 MarkForUpload: True Package: linux 3.11.0.14.15 PackageArchitecture: amd64 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (54 days ago) UserGroups: adm admin cdrom dialout libvirtd lp lpadmin plugdev sambashare vboxusers dmi.bios.date: 05/09/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 02K3Y4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/09/2012:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn02K3Y4:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259850/+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 1259850] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1259850/+attachment/3927470/+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/1259850 Title: KDE powermanagement crashes kernel Status in “linux” package in Ubuntu: Confirmed Bug description: I have a Dell Latitude D6510 running (K)ubuntu 13.10 with the current kernel (3.11.0-14). In KDE when I pull the power cord, the system instantly freezes - completely, leaving no helpful traces of the cause in syslog or pm-powersave.log. It does not happen w/o a running KDE session or when I switch to Unity or XFCE. Hence, I suspect KDE triggering the bug. Googling for "power unplug crash linux kernel" yields a bunch of somewhat similiar issues, but those all seem slightly diffrent from what I see. In fact, I have had the/an "unplug crash issue" before like a year or so ago. Somehow it vanished, and now it is back again, so this could be a kernel regression. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: deas 6090 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=901a5939-36e9-4493-9f9d-68a6fea3613e InstallationDate: Installed on 2011-03-07 (1009 days ago) InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101008) MachineType: Dell Inc. Latitude E6510 MarkForUpload: True Package: linux 3.11.0.14.15 PackageArchitecture: amd64 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (54 days ago) UserGroups: adm admin cdrom dialout libvirtd lp lpadmin plugdev sambashare vboxusers dmi.bios.date: 05/09/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 02K3Y4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/09/2012:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn02K3Y4:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259850/+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 1259850] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1259850/+attachment/3927467/+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/1259850 Title: KDE powermanagement crashes kernel Status in “linux” package in Ubuntu: Confirmed Bug description: I have a Dell Latitude D6510 running (K)ubuntu 13.10 with the current kernel (3.11.0-14). In KDE when I pull the power cord, the system instantly freezes - completely, leaving no helpful traces of the cause in syslog or pm-powersave.log. It does not happen w/o a running KDE session or when I switch to Unity or XFCE. Hence, I suspect KDE triggering the bug. Googling for "power unplug crash linux kernel" yields a bunch of somewhat similiar issues, but those all seem slightly diffrent from what I see. In fact, I have had the/an "unplug crash issue" before like a year or so ago. Somehow it vanished, and now it is back again, so this could be a kernel regression. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: deas 6090 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=901a5939-36e9-4493-9f9d-68a6fea3613e InstallationDate: Installed on 2011-03-07 (1009 days ago) InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101008) MachineType: Dell Inc. Latitude E6510 MarkForUpload: True Package: linux 3.11.0.14.15 PackageArchitecture: amd64 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (54 days ago) UserGroups: adm admin cdrom dialout libvirtd lp lpadmin plugdev sambashare vboxusers dmi.bios.date: 05/09/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 02K3Y4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/09/2012:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn02K3Y4:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259850/+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 1259850] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1259850/+attachment/3927477/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1259850 Title: KDE powermanagement crashes kernel Status in “linux” package in Ubuntu: Confirmed Bug description: I have a Dell Latitude D6510 running (K)ubuntu 13.10 with the current kernel (3.11.0-14). In KDE when I pull the power cord, the system instantly freezes - completely, leaving no helpful traces of the cause in syslog or pm-powersave.log. It does not happen w/o a running KDE session or when I switch to Unity or XFCE. Hence, I suspect KDE triggering the bug. Googling for "power unplug crash linux kernel" yields a bunch of somewhat similiar issues, but those all seem slightly diffrent from what I see. In fact, I have had the/an "unplug crash issue" before like a year or so ago. Somehow it vanished, and now it is back again, so this could be a kernel regression. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: deas 6090 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=901a5939-36e9-4493-9f9d-68a6fea3613e InstallationDate: Installed on 2011-03-07 (1009 days ago) InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101008) MachineType: Dell Inc. Latitude E6510 MarkForUpload: True Package: linux 3.11.0.14.15 PackageArchitecture: amd64 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (54 days ago) UserGroups: adm admin cdrom dialout libvirtd lp lpadmin plugdev sambashare vboxusers dmi.bios.date: 05/09/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 02K3Y4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/09/2012:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn02K3Y4:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259850/+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 1259850] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1259850/+attachment/3927476/+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/1259850 Title: KDE powermanagement crashes kernel Status in “linux” package in Ubuntu: Confirmed Bug description: I have a Dell Latitude D6510 running (K)ubuntu 13.10 with the current kernel (3.11.0-14). In KDE when I pull the power cord, the system instantly freezes - completely, leaving no helpful traces of the cause in syslog or pm-powersave.log. It does not happen w/o a running KDE session or when I switch to Unity or XFCE. Hence, I suspect KDE triggering the bug. Googling for "power unplug crash linux kernel" yields a bunch of somewhat similiar issues, but those all seem slightly diffrent from what I see. In fact, I have had the/an "unplug crash issue" before like a year or so ago. Somehow it vanished, and now it is back again, so this could be a kernel regression. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: deas 6090 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=901a5939-36e9-4493-9f9d-68a6fea3613e InstallationDate: Installed on 2011-03-07 (1009 days ago) InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101008) MachineType: Dell Inc. Latitude E6510 MarkForUpload: True Package: linux 3.11.0.14.15 PackageArchitecture: amd64 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (54 days ago) UserGroups: adm admin cdrom dialout libvirtd lp lpadmin plugdev sambashare vboxusers dmi.bios.date: 05/09/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 02K3Y4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/09/2012:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn02K3Y4:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259850/+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 1259850] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1259850/+attachment/3927473/+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/1259850 Title: KDE powermanagement crashes kernel Status in “linux” package in Ubuntu: Confirmed Bug description: I have a Dell Latitude D6510 running (K)ubuntu 13.10 with the current kernel (3.11.0-14). In KDE when I pull the power cord, the system instantly freezes - completely, leaving no helpful traces of the cause in syslog or pm-powersave.log. It does not happen w/o a running KDE session or when I switch to Unity or XFCE. Hence, I suspect KDE triggering the bug. Googling for "power unplug crash linux kernel" yields a bunch of somewhat similiar issues, but those all seem slightly diffrent from what I see. In fact, I have had the/an "unplug crash issue" before like a year or so ago. Somehow it vanished, and now it is back again, so this could be a kernel regression. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: deas 6090 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=901a5939-36e9-4493-9f9d-68a6fea3613e InstallationDate: Installed on 2011-03-07 (1009 days ago) InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101008) MachineType: Dell Inc. Latitude E6510 MarkForUpload: True Package: linux 3.11.0.14.15 PackageArchitecture: amd64 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (54 days ago) UserGroups: adm admin cdrom dialout libvirtd lp lpadmin plugdev sambashare vboxusers dmi.bios.date: 05/09/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 02K3Y4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/09/2012:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn02K3Y4:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259850/+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 1259850] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1259850/+attachment/3927480/+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/1259850 Title: KDE powermanagement crashes kernel Status in “linux” package in Ubuntu: Confirmed Bug description: I have a Dell Latitude D6510 running (K)ubuntu 13.10 with the current kernel (3.11.0-14). In KDE when I pull the power cord, the system instantly freezes - completely, leaving no helpful traces of the cause in syslog or pm-powersave.log. It does not happen w/o a running KDE session or when I switch to Unity or XFCE. Hence, I suspect KDE triggering the bug. Googling for "power unplug crash linux kernel" yields a bunch of somewhat similiar issues, but those all seem slightly diffrent from what I see. In fact, I have had the/an "unplug crash issue" before like a year or so ago. Somehow it vanished, and now it is back again, so this could be a kernel regression. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: deas 6090 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=901a5939-36e9-4493-9f9d-68a6fea3613e InstallationDate: Installed on 2011-03-07 (1009 days ago) InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101008) MachineType: Dell Inc. Latitude E6510 MarkForUpload: True Package: linux 3.11.0.14.15 PackageArchitecture: amd64 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (54 days ago) UserGroups: adm admin cdrom dialout libvirtd lp lpadmin plugdev sambashare vboxusers dmi.bios.date: 05/09/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 02K3Y4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/09/2012:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn02K3Y4:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259850/+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 1259850] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1259850/+attachment/3927474/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1259850 Title: KDE powermanagement crashes kernel Status in “linux” package in Ubuntu: Confirmed Bug description: I have a Dell Latitude D6510 running (K)ubuntu 13.10 with the current kernel (3.11.0-14). In KDE when I pull the power cord, the system instantly freezes - completely, leaving no helpful traces of the cause in syslog or pm-powersave.log. It does not happen w/o a running KDE session or when I switch to Unity or XFCE. Hence, I suspect KDE triggering the bug. Googling for "power unplug crash linux kernel" yields a bunch of somewhat similiar issues, but those all seem slightly diffrent from what I see. In fact, I have had the/an "unplug crash issue" before like a year or so ago. Somehow it vanished, and now it is back again, so this could be a kernel regression. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: deas 6090 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=901a5939-36e9-4493-9f9d-68a6fea3613e InstallationDate: Installed on 2011-03-07 (1009 days ago) InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101008) MachineType: Dell Inc. Latitude E6510 MarkForUpload: True Package: linux 3.11.0.14.15 PackageArchitecture: amd64 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (54 days ago) UserGroups: adm admin cdrom dialout libvirtd lp lpadmin plugdev sambashare vboxusers dmi.bios.date: 05/09/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 02K3Y4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/09/2012:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn02K3Y4:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259850/+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 1259850] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1259850/+attachment/3927481/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1259850 Title: KDE powermanagement crashes kernel Status in “linux” package in Ubuntu: Confirmed Bug description: I have a Dell Latitude D6510 running (K)ubuntu 13.10 with the current kernel (3.11.0-14). In KDE when I pull the power cord, the system instantly freezes - completely, leaving no helpful traces of the cause in syslog or pm-powersave.log. It does not happen w/o a running KDE session or when I switch to Unity or XFCE. Hence, I suspect KDE triggering the bug. Googling for "power unplug crash linux kernel" yields a bunch of somewhat similiar issues, but those all seem slightly diffrent from what I see. In fact, I have had the/an "unplug crash issue" before like a year or so ago. Somehow it vanished, and now it is back again, so this could be a kernel regression. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: deas 6090 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=901a5939-36e9-4493-9f9d-68a6fea3613e InstallationDate: Installed on 2011-03-07 (1009 days ago) InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101008) MachineType: Dell Inc. Latitude E6510 MarkForUpload: True Package: linux 3.11.0.14.15 PackageArchitecture: amd64 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (54 days ago) UserGroups: adm admin cdrom dialout libvirtd lp lpadmin plugdev sambashare vboxusers dmi.bios.date: 05/09/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 02K3Y4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/09/2012:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn02K3Y4:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259850/+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 1259850] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1259850/+attachment/3927479/+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/1259850 Title: KDE powermanagement crashes kernel Status in “linux” package in Ubuntu: Confirmed Bug description: I have a Dell Latitude D6510 running (K)ubuntu 13.10 with the current kernel (3.11.0-14). In KDE when I pull the power cord, the system instantly freezes - completely, leaving no helpful traces of the cause in syslog or pm-powersave.log. It does not happen w/o a running KDE session or when I switch to Unity or XFCE. Hence, I suspect KDE triggering the bug. Googling for "power unplug crash linux kernel" yields a bunch of somewhat similiar issues, but those all seem slightly diffrent from what I see. In fact, I have had the/an "unplug crash issue" before like a year or so ago. Somehow it vanished, and now it is back again, so this could be a kernel regression. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: deas 6090 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=901a5939-36e9-4493-9f9d-68a6fea3613e InstallationDate: Installed on 2011-03-07 (1009 days ago) InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101008) MachineType: Dell Inc. Latitude E6510 MarkForUpload: True Package: linux 3.11.0.14.15 PackageArchitecture: amd64 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (54 days ago) UserGroups: adm admin cdrom dialout libvirtd lp lpadmin plugdev sambashare vboxusers dmi.bios.date: 05/09/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 02K3Y4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/09/2012:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn02K3Y4:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259850/+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 1259850] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1259850/+attachment/3927472/+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/1259850 Title: KDE powermanagement crashes kernel Status in “linux” package in Ubuntu: Confirmed Bug description: I have a Dell Latitude D6510 running (K)ubuntu 13.10 with the current kernel (3.11.0-14). In KDE when I pull the power cord, the system instantly freezes - completely, leaving no helpful traces of the cause in syslog or pm-powersave.log. It does not happen w/o a running KDE session or when I switch to Unity or XFCE. Hence, I suspect KDE triggering the bug. Googling for "power unplug crash linux kernel" yields a bunch of somewhat similiar issues, but those all seem slightly diffrent from what I see. In fact, I have had the/an "unplug crash issue" before like a year or so ago. Somehow it vanished, and now it is back again, so this could be a kernel regression. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: deas 6090 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=901a5939-36e9-4493-9f9d-68a6fea3613e InstallationDate: Installed on 2011-03-07 (1009 days ago) InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101008) MachineType: Dell Inc. Latitude E6510 MarkForUpload: True Package: linux 3.11.0.14.15 PackageArchitecture: amd64 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (54 days ago) UserGroups: adm admin cdrom dialout libvirtd lp lpadmin plugdev sambashare vboxusers dmi.bios.date: 05/09/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 02K3Y4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/09/2012:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn02K3Y4:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259850/+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 1259850] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1259850/+attachment/3927478/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1259850 Title: KDE powermanagement crashes kernel Status in “linux” package in Ubuntu: Confirmed Bug description: I have a Dell Latitude D6510 running (K)ubuntu 13.10 with the current kernel (3.11.0-14). In KDE when I pull the power cord, the system instantly freezes - completely, leaving no helpful traces of the cause in syslog or pm-powersave.log. It does not happen w/o a running KDE session or when I switch to Unity or XFCE. Hence, I suspect KDE triggering the bug. Googling for "power unplug crash linux kernel" yields a bunch of somewhat similiar issues, but those all seem slightly diffrent from what I see. In fact, I have had the/an "unplug crash issue" before like a year or so ago. Somehow it vanished, and now it is back again, so this could be a kernel regression. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: deas 6090 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=901a5939-36e9-4493-9f9d-68a6fea3613e InstallationDate: Installed on 2011-03-07 (1009 days ago) InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101008) MachineType: Dell Inc. Latitude E6510 MarkForUpload: True Package: linux 3.11.0.14.15 PackageArchitecture: amd64 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (54 days ago) UserGroups: adm admin cdrom dialout libvirtd lp lpadmin plugdev sambashare vboxusers dmi.bios.date: 05/09/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 02K3Y4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/09/2012:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn02K3Y4:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259850/+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 1259850] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1259850/+attachment/3927475/+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/1259850 Title: KDE powermanagement crashes kernel Status in “linux” package in Ubuntu: Confirmed Bug description: I have a Dell Latitude D6510 running (K)ubuntu 13.10 with the current kernel (3.11.0-14). In KDE when I pull the power cord, the system instantly freezes - completely, leaving no helpful traces of the cause in syslog or pm-powersave.log. It does not happen w/o a running KDE session or when I switch to Unity or XFCE. Hence, I suspect KDE triggering the bug. Googling for "power unplug crash linux kernel" yields a bunch of somewhat similiar issues, but those all seem slightly diffrent from what I see. In fact, I have had the/an "unplug crash issue" before like a year or so ago. Somehow it vanished, and now it is back again, so this could be a kernel regression. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: deas 6090 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=901a5939-36e9-4493-9f9d-68a6fea3613e InstallationDate: Installed on 2011-03-07 (1009 days ago) InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101008) MachineType: Dell Inc. Latitude E6510 MarkForUpload: True Package: linux 3.11.0.14.15 PackageArchitecture: amd64 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (54 days ago) UserGroups: adm admin cdrom dialout libvirtd lp lpadmin plugdev sambashare vboxusers dmi.bios.date: 05/09/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 02K3Y4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/09/2012:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn02K3Y4:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259850/+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 917668] Re: system freeze ("hard LOCKUP"), warn_slowpath_common+0x7f in sock_aio_read
The freezes still occure from time to time on my computer, although my kernel
is of 3.5 series.
The reports in kern.log are similar to the one in my post #33 above, though
they often are
truncated at some early position after the words "Modules linked in...".
The system hangs without any response and need to be rebooted.
My system is KUbuntu 12.10 with all current updates.
MB Asus M5A990FX Pro R2.0, CPU AMD FX 8150, GPU GeForce 210
I've stress-tested the system with prime95 several times, and it looked stable.
Besides, it is not important whether the CPU is on load or idle: the freezes
may occur in any case.
So I believe it is not a hardware failure/instability.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/917668
Title:
system freeze ("hard LOCKUP"), warn_slowpath_common+0x7f in
sock_aio_read
Status in “linux” package in Ubuntu:
Fix Released
Bug description:
I've had sporadic freezes on this system before since upgrading to
Precise, but I haven't had the resources to try and ssh in prior to
this, so I can't tell if this has occurred before. Now that I have an
additional laptop I can hopefully catch this again if it occurs.
I screwed up with the logs first, but then managed to salvage dmesg
with a Trace from terminal buffer. I'll attach it separately below.
I wasn't active on the desktop when the freeze happened (had my hands
on the laptop). At least Chromium, Transmission and Google Music were
running at the time.
(I'm not familiar with Traces so I'll just pick something from the
first line as title. Feel free to change it if needed.)
[19199.961223] [ cut here ]
[19199.961223] WARNING: at /build/buildd/linux-3.2.0/kernel/watchdog.c:241
watchdog_overflow_callback+0x9a/0xc0()
[19199.961223] Hardware name: System Product Name
[19199.961223] Watchdog detected hard LOCKUP on cpu 0
[19199.961223] Modules linked in: nls_iso8859_1 nls_cp437 vfat fat sit
tunnel4 bnep rfcomm binfmt_misc dm_crypt snd_hda_codec_hdmi
snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm
snd_seq_midi usbhid snd_rawmidi snd_seq_midi_event btusb bluetooth hid snd_seq
snd_timer snd_seq_device snd sp5100_tco soundcore snd_page_alloc i2c_piix4
edac_core shpchp dm_multipath ppdev asus_atk0110 edac_mce_amd k10temp mac_hid
parport_pc lp parport usb_storage uas dm_raid45 xor dm_mirror dm_region_hash
dm_log radeon ttm drm_kms_helper drm r8169 wmi i2c_algo_bit pata_atiixp
[19199.961223] Pid: 1387, comm: Xorg Not tainted 3.2.0-9-generic #16-Ubuntu
[19199.961223] Call Trace:
[19199.961223][] warn_slowpath_common+0x7f/0xc0
[19199.961223] [] warn_slowpath_fmt+0x46/0x50
[19199.961223] [] ? sched_clock+0x9/0x10
[19199.961223] [] watchdog_overflow_callback+0x9a/0xc0
[19199.961223] [] __perf_event_overflow+0x96/0x1e0
[19199.961223] [] ? perf_event_update_userpage+0x11/0xc0
[19199.961223] [] perf_event_overflow+0x14/0x20
[19199.961223] [] x86_pmu_handle_irq+0xd7/0x120
[19199.961223] [] perf_event_nmi_handler+0x21/0x30
[19199.961223] [] default_do_nmi+0x69/0x220
[19199.961223] [] do_nmi+0x80/0x90
[19199.961223] [] nmi+0x20/0x30
[19199.961223] [] ? __ticket_spin_lock+0x25/0x30
[19199.961223] <> [] default_spin_lock_flags+0x9/0x10
[19199.961223] [] _raw_spin_lock_irqsave+0x2e/0x40
[19199.961223] [] remove_wait_queue+0x20/0x70
[19199.961223] [] poll_freewait+0x98/0xe0
[19199.961223] [] do_select+0x557/0x600
[19199.961223] [] ? try_to_wake_up+0x18e/0x200
[19199.961223] [] ? poll_freewait+0xe0/0xe0
[19199.961223] [] ? __pollwait+0xf0/0xf0
[19199.961223] [] ? __pollwait+0xf0/0xf0
[19199.961223] [] ? __pollwait+0xf0/0xf0
[19199.961223] [] ? __pollwait+0xf0/0xf0
[19199.961223] [] ? __pollwait+0xf0/0xf0
[19199.961223] [] ? __pollwait+0xf0/0xf0
[19199.961223] [] ? __pollwait+0xf0/0xf0
[19199.961223] [] ? __pollwait+0xf0/0xf0
[19199.961223] [] ? __pollwait+0xf0/0xf0
[19199.961223] [] core_sys_select+0x1ec/0x370
[19199.961223] [] ? sock_aio_read+0x2d/0x40
[19199.961223] [] ? do_sync_read+0xd2/0x110
[19199.961223] [] ? timerqueue_del+0x34/0x90
[19199.961223] [] ? __remove_hrtimer+0x60/0xc0
[19199.961223] [] ? hrtimer_try_to_cancel+0x50/0xc0
[19199.961223] [] ? read_tsc+0x9/0x20
[19199.961223] [] ? ktime_get_ts+0xad/0xe0
[19199.961223] [] sys_select+0xc0/0x100
[19199.961223] [] system_call_fastpath+0x16/0x1b
[19199.961223] ---[ end trace 104ea42b28f227b7 ]---
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xserver-xorg-video-radeon 1:6.14.99~git20110811.g93fc084-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-9.16-generic 3.2.1
Uname: Linux 3.2.0-9-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 1.90-0ubuntu2
Architecture: amd64
CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
CheckboxSystem: edda5d4f616
[Kernel-packages] [Bug 1124040] Re: 8086:1502 [Lenovo ThinkPad W520] e1000e reconnecting in 12.04
I tested today with Ubuntu 12.04 with all updates with onboard ethernet on two different Intel mainboard DH61BE. The problem is still there! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1124040 Title: 8086:1502 [Lenovo ThinkPad W520] e1000e reconnecting in 12.04 Status in “linux” package in Ubuntu: Incomplete Bug description: The Intel e1000e kernel NIC driver is constantly reconnecting to my network causing flowstops and errors. I do not know in which exact kernel the problem started since I do not use this laptop wired regularly. Firstly I suspected faulty networking equipment, but the problem persisted on other hardware. WORKAROUND: Fetch driver directly from Intel: http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=15817&ProdId=3003&lang=eng Error: Feb 13 12:04:52 stevieray kernel: [ 1451.580536] e1000e: eth0 NIC Link is Down Feb 13 12:04:53 stevieray kernel: [ 1453.229010] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx Feb 13 12:04:53 stevieray kernel: [ 1453.229024] e1000e :00:19.0: eth0: 10/100 speed: disabling TSO Feb 13 12:04:53 stevieray NetworkManager[1088]: (eth0): carrier now ON (device state 100) Feb 13 12:05:01 stevieray CRON[3406]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Feb 13 12:05:14 stevieray NetworkManager[1088]: (eth0): carrier now OFF (device state 100, deferring action for 4 seconds) Feb 13 12:05:14 stevieray kernel: [ 1473.312198] e1000e: eth0 NIC Link is Down Feb 13 12:05:15 stevieray kernel: [ 1474.944394] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx Feb 13 12:05:15 stevieray kernel: [ 1474.944409] e1000e :00:19.0: eth0: 10/100 speed: disabling TSO Feb 13 12:05:15 stevieray NetworkManager[1088]: (eth0): carrier now ON (device state 100) Feb 13 12:05:27 stevieray NetworkManager[1088]: (eth0): carrier now OFF (device state 100, deferring action for 4 seconds) Feb 13 12:05:27 stevieray kernel: [ 1486.340811] e1000e: eth0 NIC Link is Down Feb 13 12:05:28 stevieray kernel: [ 1488.008923] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx Feb 13 12:05:28 stevieray kernel: [ 1488.008938] e1000e :00:19.0: eth0: 10/100 speed: disabling TSO Feb 13 12:05:28 stevieray NetworkManager[1088]: (eth0): carrier now ON (device state 100) With the Intel Driver: [ 2214.353191] e1000e :00:19.0: PCI INT A disabled [ 2824.335482] e1000e: Intel(R) PRO/1000 Network Driver - 2.2.14-NAPI [ 2824.335491] e1000e: Copyright(c) 1999 - 2012 Intel Corporation. [ 2824.335548] e1000e :00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20 [ 2824.335570] e1000e :00:19.0: setting latency timer to 64 [ 2824.335753] e1000e :00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 2824.347221] e1000e :00:19.0: irq 50 for MSI/MSI-X [ 2824.578329] e1000e :00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) f0:de:f1:67:84:e9 [ 2824.578340] e1000e :00:19.0: eth0: Intel(R) PRO/1000 Network Connection [ 2824.578405] e1000e :00:19.0: eth0: MAC: 11, PHY: 11, PBA No: 1000FF-0FF [ 2824.737160] e1000e :00:19.0: irq 50 for MSI/MSI-X [ 2824.840802] e1000e :00:19.0: irq 50 for MSI/MSI-X [ 2824.843896] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 2824.845415] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 2867.226514] e1000e: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx [ 2867.226529] e1000e :00:19.0: eth0: 10/100 speed: disabling TSO [ 2867.229384] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nikolaj2516 F pulseaudio /dev/snd/controlC0: nikolaj2516 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xd832 irq 53' Mixer name : 'Conexant CX20590' Components : 'HDA:14f1506e,17aa21cf,0010 HDA:14f12c06,17aa2122,0010' Controls : 20 Simple ctrls : 10 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xd600 irq 17' Mixer name : 'Nvidia GPU 11 HDMI/DP' Components : 'HDA:10de0011,10de0101,00100100' Controls : 24 Simple ctrls : 4 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown' Mixer name : 'ThinkPad EC (unknown)' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0
[Kernel-packages] [Bug 1259861] Re: 5-10 second delay in kernel boot
...ignoring the bot and changing the state back to New, as the exact kernel version doesn't matter... ** 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/1259861 Title: 5-10 second delay in kernel boot Status in “linux” package in Ubuntu: New Bug description: In Trusty I see a big delay while the kernel boots that I did not see back in Precise. Some people have been experiencing this in Saucy too, so I don't know exactly when it started happening. Excerpt from dmesg: [3.740100] Switched to clocksource tsc [ 14.208118] PM: Hibernation image not present or could not be loaded. [ 14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000) The exact messages above don't matter, they are different on different boots or on different machines. It even happens with e.g. $ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso My current kernel is Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 i686 i686 GNU/Linux ...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run `dmesg` yourself and check if there's a big delay there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259861/+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 1250909] Re: Trusty linux kernel 3.12.0-2 doesn't boot on Macbook Pro 8, 2
The kernel from your link does not bring up the display. The last message I think I saw was : fb: conflicting fb hw usage radeondrmfb vs EFI VGA - removing generic driver ** Tags added: kernel-bug-exists-upstream ** 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/1250909 Title: Trusty linux kernel 3.12.0-2 doesn't boot on Macbook Pro 8,2 Status in “linux” package in Ubuntu: Confirmed Bug description: After upgrading from Saucy to Trusty, the 3.12.0-2 kernel doesn't fully boot on my machine. I have to use the older 3.11 kernel to boot. The 3.12.0 kernel tries to boot but then seems to fail at some stage. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-2-generic 3.12.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadeslayer 2482 F pulseaudio /dev/snd/controlC0: shadeslayer 2482 F pulseaudio Date: Wed Nov 13 16:56:49 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0d23fd6f-b835-411a-af8b-c1d7a07cbf91 InstallationDate: Installed on 2013-10-31 (12 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Apple Inc. MacBookPro8,2 MarkForUpload: True ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: \boot\vmlinuz-3.11.0-12-generic ro root=UUID=ff872e15-889d-4f71-b33f-176cf27e2f12 initrd=boot\initrd.img-3.11.0-12-generic RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.117 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2013-10-31 (12 days ago) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250909/+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 1259861] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1259861 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/1259861 Title: 5-10 second delay in kernel boot Status in “linux” package in Ubuntu: Incomplete Bug description: In Trusty I see a big delay while the kernel boots that I did not see back in Precise. Some people have been experiencing this in Saucy too, so I don't know exactly when it started happening. Excerpt from dmesg: [3.740100] Switched to clocksource tsc [ 14.208118] PM: Hibernation image not present or could not be loaded. [ 14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000) The exact messages above don't matter, they are different on different boots or on different machines. It even happens with e.g. $ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso My current kernel is Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 i686 i686 GNU/Linux ...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run `dmesg` yourself and check if there's a big delay there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259861/+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 1197482] Re: 8086:0a26 [MacBook Air 6, 2] After suspend/resume, screen is dark for brighness levels below 13 with i915 driver
Cyro, so your hardware may be tracked, could you please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via: ubuntu-bug linux For more on this, please read the official Ubuntu documentation: Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette When opening up the new report, please feel free to subscribe me to it. Thank you for your understanding. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1197482 Title: 8086:0a26 [MacBook Air 6,2] After suspend/resume, screen is dark for brighness levels below 13 with i915 driver Status in “linux” package in Ubuntu: Incomplete Bug description: After installing Raring on my 2013 MacBook Air 6,2, I find that sometimes when resuming from suspend, the screen is dark. I have tracked this down to the i915 driver, where the screen brightness can be adjusted between levels 0-15. This works correctly after boot, with 0 being dark and 15 the brightest. Sometimes after suspend/resume, the screen is equally dark between levels 0-12, and seems to be equally bright for levels 13-15 (brightest). I say sometimes, because it's not every time. It _might_ be after the second or third suspend/resume, but I'm not yet sure how to repeat it. When this happens, I have to kill lightum, the backlight/keyboard monitoring daemon, and manually set the brightness using the sys filesystem: echo '15' | sudo tee /sys/devices/pci\:00/\:00\:02.0/backlight/acpi_video0/brightness ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-25-generic 3.8.0-25.37 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: linus 1939 F pulseaudio CRDA: country SE: (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: Wed Jul 3 19:23:53 2013 HibernationDevice: RESUME=/dev/mapper/cryptswap1 #RESUME=UUID=7625120b-1951-4a58-8da6-1c47db358631 MachineType: Apple Inc. MacBookAir6,2 MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=UUID=2f08800d-d161-46e7-87b6-0f88e86890af ro i915.i915_enable_rc6=3 libata.force=1:noncq resume=/dev/sda4 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-25-generic N/A linux-backports-modules-3.8.0-25-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/24/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA61.88Z.0099.B00.1305241529 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-7DF21CB3ED6977E5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-7DF21CB3ED6977E5 dmi.modalias: dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B00.1305241529:bd05/24/2013:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5: dmi.product.name: MacBookAir6,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ApportVersion: 2.12.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2716 F pulseaudio ubuntu 5277 F pulseaudio /dev/snd/controlC0: ubuntu 2716 F pulseaudio ubuntu 5277 F pulseaudio CasperVersion: 1.336ubuntu1 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64+mac (20131203) MachineType: Apple Inc. MacBookAir6,2 MarkForUpload: True NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2 RelatedPackageVersions: linux-restricted-modules-3.12.0-5-generic N/A linux-backports-modules-3.12.0-5-generic N/A linux-firmware1.117 Tags: trusty Uname: Linux 3.12.0-5-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo Wif
[Kernel-packages] [Bug 1259861] Re: 5-10 second delay in kernel boot
Changing to confirmed to satisfy the bot. :) ** 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/1259861 Title: 5-10 second delay in kernel boot Status in “linux” package in Ubuntu: Confirmed Bug description: In Trusty I see a big delay while the kernel boots that I did not see back in Precise. Some people have been experiencing this in Saucy too, so I don't know exactly when it started happening. Excerpt from dmesg: [3.740100] Switched to clocksource tsc [ 14.208118] PM: Hibernation image not present or could not be loaded. [ 14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000) The exact messages above don't matter, they are different on different boots or on different machines. It even happens with e.g. $ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso My current kernel is Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 i686 i686 GNU/Linux ...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run `dmesg` yourself and check if there's a big delay there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259861/+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 1098697] Re: [HP ENVY Sleekbook 6-1006sa] High Battery discharge rate when Laptop is off.
Dave H, would you need a backport to a release prior to Saucy, or may this be closed as Status Invalid? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1098697 Title: [HP ENVY Sleekbook 6-1006sa] High Battery discharge rate when Laptop is off. Status in “linux” package in Ubuntu: Incomplete Bug description: I have a HP ENVY 6 1006sa Sleekbook running Ubuntu 12.10. Fully charged, unplugged Mains adaptor powered down. 48hrs later re-powered charge now only 65% ! The Laptop battery is discharging when the Laptop is powered off: http://www.divnut.com/HP_ENVY6_1006sa/HP_ENVY_6_48hr_discharge_2012-12-08.png The gradient looks OK, so nothing wrong with the battery. Left a further 48 hrs and the Sleekbook would not start on battery alone. http://www.divnut.com/Ubuntu/HP_ENVY_6_96hr_discharge_2012-12-10.png While my Sleekbook is in warranty I'm dual booting Win 7 and Ubuntu 12.10 (Unity desktop). I've done a Win 7 and Ubuntu 12.10 battery drain 'when off' comparison: Win7: 4% per 24hrs / Ubuntu 12.10: ~17% per 24hrs. (The measurement includes power on and boot to OS to make the measurement) Did a longer Win 7 test for improved accuracy: 10% depletion in 7.5 days or 1.3% in 24hrs. Updated the Sleekbook BIOS from F.04 to the latest F.12 – No Change. Did a Win7 HP Battery diagnostics check: OK http://www.divnut.com/HP_ENVY6_1006sa/Battery_check_281212_15pm26.png WORKAROUND: sudo ethtool -s eth0 wol d ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-21-generic 3.5.0-21.32 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 NonfreeKernelModules: fglrx wl ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dave 2120 F pulseaudio /dev/snd/controlC0: dave 2120 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Fri Jan 11 19:25:02 2013 HibernationDevice: RESUME=UUID=10a7229b-c7dc-4be5-b73a-47f8cc688067 InstallationDate: Installed on 2012-11-02 (69 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Hewlett-Packard HP ENVY 6 Notebook PC MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-21-generic root=UUID=7f85374d-bd7c-4780-90aa-b2538b5a0b75 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.5.0-21-generic N/A linux-backports-modules-3.5.0-21-generic N/A linux-firmware1.95 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: Jan 11 17:58:57 dave-HP-ENVY-6-Notebook-PC wpa_supplicant[1190]: eth1: WPA: Group rekeying completed with 00:1f:33:26:3d:7f [GTK=TKIP] Jan 11 18:11:49 dave-HP-ENVY-6-Notebook-PC kernel: [ 7547.438831] EXT4-fs (sda10): recovery complete Jan 11 18:11:49 dave-HP-ENVY-6-Notebook-PC kernel: [ 7547.469516] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null) Jan 11 18:11:52 dave-HP-ENVY-6-Notebook-PC kernel: [ 7551.321057] EXT4-fs (sda11): mounted filesystem with ordered data mode. Opts: (null) Jan 11 18:58:56 dave-HP-ENVY-6-Notebook-PC wpa_supplicant[1190]: eth1: WPA: Group rekeying completed with 00:1f:33:26:3d:7f [GTK=TKIP] dmi.bios.date: 09/03/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.12 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 18DE dmi.board.vendor: Hewlett-Packard dmi.board.version: 77.44 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.12:bd09/03/2012:svnHewlett-Packard:pnHPENVY6NotebookPC:pvr07951020560320100:rvnHewlett-Packard:rn18DE:rvr77.44:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY 6 Notebook PC dmi.product.version: 07951020560320100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1098697/+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 1230359] Re: [Lenovo ThinkPad S431 20AX] boots up after shutdown, twice
CaptSaltyJack, for regression testing purposes, could you please test for this in Precise via http://releases.ubuntu.com/precise/ ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1230359 Title: [Lenovo ThinkPad S431 20AX] boots up after shutdown, twice Status in “linux” package in Ubuntu: Incomplete Bug description: Running Ubuntu 13.04 on a ThinkPad S431. When shutting down Ubuntu, the machine turns off normally, but then turns back on again by itself. I have to hit the power button to turn it off, but then it turns on once more. Hitting the power button a second time finally turns the machine off. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-30-generic 3.8.0-30.44 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: samh 1801 F pulseaudio Date: Wed Sep 25 10:23:24 2013 HibernationDevice: RESUME=UUID=ce2190d2-c875-4c5d-b2e8-1b1473c7c4db InstallationDate: Installed on 2013-09-15 (9 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: LENOVO 20AXCTO1WW MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-30-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash "acpi_osi=!Windows 2012" acpi=force RelatedPackageVersions: linux-restricted-modules-3.8.0-30-generic N/A linux-backports-modules-3.8.0-30-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2013 dmi.bios.vendor: LENOVO dmi.bios.version: HFET30WW (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Win8 STD DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrHFET30WW(1.07):bd07/10/2013:svnLENOVO:pn20AXCTO1WW:pvrThinkPadS3-S431:rvnLENOVO:rn20AXCTO1WW:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AXCTO1WW dmi.product.version: ThinkPad S3-S431 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1230359/+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 1230359] Re: [Lenovo ThinkPad S431 20AX] boots up after shutdown, twice
ramgorur, so your hardware may be tracked, could you please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via: ubuntu-bug linux For more on this, please read the official Ubuntu documentation: Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette When opening up the new report, please feel free to subscribe me to it. Thank you for your understanding. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1230359 Title: [Lenovo ThinkPad S431 20AX] boots up after shutdown, twice Status in “linux” package in Ubuntu: Incomplete Bug description: Running Ubuntu 13.04 on a ThinkPad S431. When shutting down Ubuntu, the machine turns off normally, but then turns back on again by itself. I have to hit the power button to turn it off, but then it turns on once more. Hitting the power button a second time finally turns the machine off. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-30-generic 3.8.0-30.44 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: samh 1801 F pulseaudio Date: Wed Sep 25 10:23:24 2013 HibernationDevice: RESUME=UUID=ce2190d2-c875-4c5d-b2e8-1b1473c7c4db InstallationDate: Installed on 2013-09-15 (9 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: LENOVO 20AXCTO1WW MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-30-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash "acpi_osi=!Windows 2012" acpi=force RelatedPackageVersions: linux-restricted-modules-3.8.0-30-generic N/A linux-backports-modules-3.8.0-30-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2013 dmi.bios.vendor: LENOVO dmi.bios.version: HFET30WW (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Win8 STD DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrHFET30WW(1.07):bd07/10/2013:svnLENOVO:pn20AXCTO1WW:pvrThinkPadS3-S431:rvnLENOVO:rn20AXCTO1WW:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AXCTO1WW dmi.product.version: ThinkPad S3-S431 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1230359/+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 1244768] Re: Bluetooth stopped working after upgrade to ubuntu 13.10
Vladimir lg, assuming no change in the issue, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. For example: kernel-fixed-upstream-v3.13-rc3 This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag: needs-upstream-testing If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER As well, please remove the tag: needs-upstream-testing Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Tags removed: bios-outdated-2.59 ** Tags added: latest-bios-2.59 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1244768 Title: Bluetooth stopped working after upgrade to ubuntu 13.10 Status in “linux” package in Ubuntu: Incomplete Bug description: cat /proc/version_signature Ubuntu 3.11.0-13.20-generic 3.11.6 dmesg | grep -i bluetooth [2.214484] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked [2.241367] Bluetooth: Core ver 2.16 [2.241383] Bluetooth: HCI device and connection manager initialized [2.241390] Bluetooth: HCI socket layer initialized [2.241392] Bluetooth: L2CAP socket layer initialized [2.241397] Bluetooth: SCO socket layer initialized [2.325165] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [2.325166] Bluetooth: BNEP filters: protocol multicast [2.325172] Bluetooth: BNEP socket layer initialized [2.336771] Bluetooth: RFCOMM TTY layer initialized [2.336779] Bluetooth: RFCOMM socket layer initialized [2.336780] Bluetooth: RFCOMM ver 1.11 [2.423106] Bluetooth: can't load firmware, may not work correctly [ 1106.750498] Bluetooth: can't load firmware, may not work correctly [ 1110.079697] Bluetooth: can't load firmware, may not work correctly [ .360045] Bluetooth: can't load firmware, may not work correctly [ 1113.664919] Bluetooth: can't load firmware, may not work correctly [ 1118.786717] Bluetooth: can't load firmware, may not work correctly [ 1120.835455] Bluetooth: can't load firmware, may not work correctly [ 1129.029982] Bluetooth: can't load firmware, may not work correctly [ 1131.589729] Bluetooth: can't load firmware, may not work correctly [ 1140.553215] Bluetooth: can't load firmware, may not work correctly [ 1142.344158] Bluetooth: can't load firmware, may not work correctly [ 1146.954210] Bluetooth: can't load firmware, may not work correctly [ 1150.026402] Bluetooth: can't load firmware, may not work correctly [ 1151.563511] Bluetooth: can't load firmware, may not work correctly [ 1152.586974] Bluetooth: can't load firmware, may not work correctly [ 1153.612224] Bluetooth: can't load firmware, may not work correctly [ 1155.148246] Bluetooth: can't load firmware, may not work correctly [ 9109.086486] Bluetooth: can't load firmware, may not work correctly [ 9110.366899] Bluetooth: can't load firmware, may not work correctly [ 9111.647188] Bluetooth: can't load firmware, may not work correctly - Trying to switch on bluetooth in System settings/Bluetooth sudo tail -f /var/log/syslog Oct 25 12:23:29 th-t430 bluetoothd[526]: Endpoint registered: sender=:1.64 path=/MediaEndpoint/HFPAG Oct 25 12:23:29 th-t430 bluetoothd[526]: Endpoint registered: sender=:1.64 path=/MediaEndpoint/HFPHS Oct 25 12:23:29 th-t430 bluetoothd[526]: Endpoint registered: sender=:1.64 path=/MediaEndpoint/A2DPSource Oct 25 12:23:29 th-t430 bluetoothd[526]: Endpoint registered: sender=:1.64 path=/MediaEndpoint/A2DPSink Oct 25 12:23:29 th-t430 bluetoothd[526]: Unregister path: /org/bluez/526/hci0 Oct 25 12:23:29 th-t430 bluetoothd[526]: Endpoint unregistered: sender=:1.64 path=/MediaEndpoint/A2DPSink Oct 25 12:23:29 th-t430 bluetoothd[526]: Endpoint unregistered: sender=:1.64 path=/MediaEndpoint/A2DPSource Oct 25 12:23:29 th-t430 bluetoothd[526]: Endpoint unregistered: sender=:1.64 path=/MediaEndpoint/HFPAG Oct 25 12:23:29 th-t430 bluetoothd[526]: Endpoint unregistered: sender=:1.64 path=/MediaEndpoint/HFPHS Oct 25 12:23:29 th-t430 kernel: [ 9111.860295] usb 1-1.4: USB disconnect, device number 26 Oct 25 12:30
[Kernel-packages] [Bug 1205694] Re: 8086:0166 [Taichi 21] external screen is not working properly
SOIMiMozO, so your hardware may be tracked, could you please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via: ubuntu-bug linux For more on this, please read the official Ubuntu documentation: Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette When opening up the new report, please feel free to subscribe me to it. Thank you for your understanding. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1205694 Title: 8086:0166 [Taichi 21] external screen is not working properly Status in “linux” package in Ubuntu: Incomplete Bug description: First of all, I'd like to say that both screen are recognized by xrandr: The internal as eDP1 and the external as DP1. The external screen works under some circumstances, but without backlight. If the computer is off, and I turn on with the lid closed, the external screen "works" If the computer is turned on, on linux, and I restart, the external screen keeps "working". If the computer is off and I turn on with the lid opened or the computer is on windows, using the external screen, and I restart to linux, I can't use the external screen: The image keeps "off". Although, the screen is recognized by xrandr, but no setting turns the screen on (not even xrandr --output DP1 --auto) In the situations that the external screen works, the backlight has no effect on it: When I adjust the backlight (either by the hotkeys, or by echo 50 > /sys/class/backlight/acpi_video0/brightness, or echo 3000 > /sys/class/backlight/intel_backlight/brightness), it just adjusts the internal screen When I use the hotkey to turn off the screen, it just turn off the internal screen Also, if I use xrandr to turn off the external screen, or suspend the computer, the external screen is turned off. When I try again to turn on, or resume it doesn't work. I tried to boot with acpi_backlight=vendor, and again just the internal screen worked properly. The hotkey to change the backlight didn't work, but echo 3000 > /sys/class/backlight/intel_backlight/brightness worked I tried to boot with video.use_bios_initial_backlight=0 and the backlight worked just for the internal screen again I tried to boot with acpi_osi="!Windows 2012", the same thing By running dmesg | grep 'ACPI: Video', I get: [4.981826] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) And lspci | grep VGA shows: 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) I don't know if I should get 2 results in them, since I have two screens, but in DSDT, I just see one device with methods _DOS, _DOD, so I guess it is right. There is an if in the BCL, checking if it is Windows 8, but I believe acpi_osi="!Windows 2012", should "fix" it if that was the problem I believe that solving the backlight problem when I'm able to turn on the screen might solve the screen not turning on with the lid open. I tried to use the current Mainline kernel (3.11.0-999, or something like that), but after the boot the external screen was off and the internal was on, not showing anything but a black screen. I followed the Kernel/Debugging/Backlight page and I'll submit all the files that it generated. Thank you for your help! ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-26-generic 3.8.0-26.38 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joao 2437 F pulseaudio Date: Sat Jul 27 12:44:02 2013 HibernationDevice: RESUME=UUID=8c6201ab-045c-4bb7-b20d-c4650cca8821 InstallationDate: Installed on 2013-07-23 (4 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. TAICHI21 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-26-generic root=UUID=1b4e19b1-47cc-4068-a6d6-b73868b3c9d8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-26-generic N/A linux-backports-modules-3.8.0-26-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2013 dmi.bios
[Kernel-packages] [Bug 1233794] Re: [LENOVO ThinkPad X220] suspend/resume failure
Mark Stosberg, so your hardware may be tracked, could you please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via: ubuntu-bug linux For more on this, please read the official Ubuntu documentation: Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette When opening up the new report, please feel free to subscribe me to it. Thank you for your understanding. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1233794 Title: [LENOVO ThinkPad X220] suspend/resume failure Status in “linux” package in Ubuntu: Incomplete Bug description: It seem to me that this is a strange problem. After suspend, there is no resume. The strange thing is that after installing a new kernelpackage it work as it should for 2 or 3 times, the it start failing again. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-9-generic 3.11.0-9.16 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-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: rolfc 2312 F pulseaudio /dev/snd/seq:timidity 1375 F timidity Date: Tue Oct 1 20:24:13 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=26a91e75-e73a-4504-831f-5088ed794e48 InstallationDate: Installed on 2012-05-22 (497 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) InterpreterPath: /usr/bin/python3.3 MachineType: LENOVO 42914CG 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-9-generic root=UUID=0e70b3de-2758-4c05-aee2-4955f07e0e7c 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-9-generic N/A linux-backports-modules-3.11.0-9-generic N/A linux-firmware1.115 SourcePackage: linux Title: [LENOVO 42914CG] suspend/resume failure UpgradeStatus: Upgraded to saucy on 2013-09-09 (21 days ago) UserGroups: dmi.bios.date: 02/14/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET58WW (1.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 42914CG 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:bvr8DET58WW(1.28):bd02/14/2012:svnLENOVO:pn42914CG:pvrThinkPadX220:rvnLENOVO:rn42914CG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42914CG dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1233794/+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 1257227] Re: be2net: SRIOV functionality broken with latest firmware
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Released ** Changed in: linux (Ubuntu Saucy) Status: New => Fix Committed ** Changed in: linux (Ubuntu Saucy) Assignee: (unassigned) => Jesse Sung (wenchien) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1257227 Title: be2net: SRIOV functionality broken with latest firmware Status in The Emulex project: In Progress Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Fix Committed Status in “linux” source package in Trusty: Fix Released Bug description: SRIOV functionality is broken in Saucy inbox driver with latest firmware (10.0.727.x). VF's are failed to initialize. This issue is due to incompatibility between driver and Firmware. The following net-next commits needs to be pulled in to resolve this issue. Patch 1: 5a712c13d3641a3bed243753f115434a7125e440 Subject: [PATCH] be2net: fix MAC address modification for VF Patch 2: 04a060280a083860e4d4723b878d69af1ba53ec9 Subject: [PATCH 1/5] be2net: allow VFs to program MAC and VLAN filters Patch 3: b5bb9776b143dcf7931c6e00330bf8d518376760 Subject: [PATCH 2/5] be2net: fix pmac_id for BE3 VFs Patch 4: 95046b927a54f461766f83a212c6a93bc5fd2e67 Subject: [PATCH 3/5] be2net: refactor MAC-addr setup code Patch 3: 3175d8c2d05f4c87ba616d4c11037a4ad3f77378 Subject: [PATCH 4/5] be2net: use SET/GET_MAC_LIST for SH-R Patch 6: 2d17f4031475f2e836dd06d5b03593ee59f12fbd Subject: [PATCH 5/5] be2net: delete primary MAC address while unloading Could you please pull them to Saucy. Thanks, Suresh. To manage notifications about this bug go to: https://bugs.launchpad.net/emulex/+bug/1257227/+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 1189896] Re: [FUJITSU FMVS54KR] always boot with minimum backlight brightness
This issue is no longer reproducible with latest trusty kernel. Linux lifebook 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:39:27 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1189896 Title: [FUJITSU FMVS54KR] always boot with minimum backlight brightness Status in “linux” package in Ubuntu: Invalid Bug description: It always boot with minimum backlight brightness. just after the boot: /sys/class/backlight/acpi_video0/actual_brightness:0 /sys/class/backlight/acpi_video0/brightness:0 /sys/class/backlight/acpi_video0/max_brightness:100 /sys/class/backlight/intel_backlight/actual_brightness:41 /sys/class/backlight/intel_backlight/brightness:3487 /sys/class/backlight/intel_backlight/max_brightness:3487 I can change brightness after boot with hotkeys. ProblemType: BugDistroRelease: Ubuntu 13.10 Package: linux-image-3.9.0-4-generic 3.9.0-4.9 ProcVersionSignature: Ubuntu 3.9.0-4.9-generic 3.9.4 Uname: Linux 3.9.0-4-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nobuto 2339 F pulseaudio Date: Tue Jun 11 21:55:10 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=e1bbd58c-ba6f-4896-95d9-3bdb60dde26d InstallationDate: Installed on 2013-04-21 (50 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130420) MachineType: FUJITSU FMVS54KR MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-4-generic.efi.signed root=UUID=f0ca756b-8b3f-4cb2-908f-5d8e2273c93e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.9.0-4-generic N/A linux-backports-modules-3.9.0-4-generic N/A linux-firmware 1.109SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-06-08 (2 days ago) dmi.bios.date: 01/07/2013 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.06 dmi.board.name: FJNB24F dmi.board.vendor: FUJITSU dmi.board.version: D2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.06:bd01/07/2013:svnFUJITSU:pnFMVS54KR:pvr:rvnFUJITSU:rnFJNB24F:rvrD2:cvnFUJITSU:ct10:cvr: dmi.product.name: FMVS54KR dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1189896/+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 1259829] Re: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name
** 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/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 Status in “linux” package in Ubuntu: New Bug description: fs goes into read-only mode while build lo $ dmesg ... [ 2045.473249] virbr0: port 1(vnet0) entered forwarding state [ 2045.473283] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready [10660.961381] perf samples too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 5 [11822.935891] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 [11822.935896] Aborting journal on device dm-1-8. [11822.935998] EXT4-fs (dm-1): Remounting filesystem read-only [11822.960425] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629605: block 214443466: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2707156714, rec_len=19312, name_len=162 [11850.985003] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629557: block 214443458: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=512948573, rec_len=8858, name_len=176 [11850.985276] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629465: block 214443455: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=160939375, rec_len=26085, name_len=126 [11850.985499] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629325: block 214443451: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2322664969, rec_len=33791, name_len=132 [11850.985927] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629467: block 214443456: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=954332768, rec_len=21653, name_len=30 [11850.986409] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629074: block 214443433: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2061605548, rec_len=4984, name_len=3 [11850.986831] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53628835: block 214443432: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=3523041938, rec_len=53167, name_len=41 [11850.987001] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629098: block 214443436: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4225920287, rec_len=35138, name_len=75 [11850.987466] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629275: block 214443449: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=923253145, rec_len=44001, name_len=144 [11850.988115] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629270: block 214443448: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1892288796, rec_len=55247, name_len=58 [11851.042303] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629300: block 214443450: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=1809316884, rec_len=4208, name_len=195 [11851.042938] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629401: block 214443453: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4223616103, rec_len=36326, name_len=130 [11851.045745] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629406: block 214443454: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=415237227, rec_len=24702, name_len=59 [11851.125849] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629101: block 214443437: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=23292377, rec_len=28820, name_len=135 [11851.126086] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629543: block 214443457: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2624043515, rec_len=58633, name_len=250 [11851.126292] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629244: block 214443446: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=194839831, rec_len=15430, name_len=123 [11851.126529] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629345: block 214443452: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=3316601052, rec_len=49124, name_len=10 [11851.126751] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode
[Kernel-packages] [Bug 1259829] 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/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 Status in “linux” package in Ubuntu: Confirmed Bug description: fs goes into read-only mode while build lo $ dmesg ... [ 2045.473249] virbr0: port 1(vnet0) entered forwarding state [ 2045.473283] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready [10660.961381] perf samples too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 5 [11822.935891] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 [11822.935896] Aborting journal on device dm-1-8. [11822.935998] EXT4-fs (dm-1): Remounting filesystem read-only [11822.960425] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629605: block 214443466: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2707156714, rec_len=19312, name_len=162 [11850.985003] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629557: block 214443458: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=512948573, rec_len=8858, name_len=176 [11850.985276] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629465: block 214443455: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=160939375, rec_len=26085, name_len=126 [11850.985499] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629325: block 214443451: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2322664969, rec_len=33791, name_len=132 [11850.985927] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629467: block 214443456: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=954332768, rec_len=21653, name_len=30 [11850.986409] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629074: block 214443433: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2061605548, rec_len=4984, name_len=3 [11850.986831] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53628835: block 214443432: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=3523041938, rec_len=53167, name_len=41 [11850.987001] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629098: block 214443436: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4225920287, rec_len=35138, name_len=75 [11850.987466] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629275: block 214443449: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=923253145, rec_len=44001, name_len=144 [11850.988115] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629270: block 214443448: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1892288796, rec_len=55247, name_len=58 [11851.042303] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629300: block 214443450: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=1809316884, rec_len=4208, name_len=195 [11851.042938] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629401: block 214443453: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4223616103, rec_len=36326, name_len=130 [11851.045745] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629406: block 214443454: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=415237227, rec_len=24702, name_len=59 [11851.125849] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629101: block 214443437: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=23292377, rec_len=28820, name_len=135 [11851.126086] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629543: block 214443457: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2624043515, rec_len=58633, name_len=250 [11851.126292] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629244: block 214443446: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=194839831, rec_len=15430, name_len=123 [11851.126529] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629345: block 214443452: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=3316601052, rec_len=49124, name_len=10 [11851.126751] EXT4-fs error (device dm-
[Kernel-packages] [Bug 1118447] Re: Race condition with network and NFS mounts causes boottime hang
The workaround of mounting the NFS shares through rc.local doesn't work for me, sometimes it mounts them and sometimes not. Could it get executed at the end of systemd scripts but not at the end of upstart jobs? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1118447 Title: Race condition with network and NFS mounts causes boottime hang Status in “linux” package in Ubuntu: Confirmed Status in “nfs-utils” package in Ubuntu: Incomplete Bug description: I seem to experience a race condition during boot of my ubuntu 12.04 server: In approx. one of seven boots, the server hangs during bootup. This is what I see on the screen: After the line * Starting configure network device there is a short delay of about 1 second, then messages continue. I see * Starting Mount network filesystems [ OK ] * Starting set sysctls from /etc/sysctl.conf [ OK ] * Starting configure network device [ OK ] * Stopping Mount network filesystems [ OK ] * Stopping set sysctls from /etc/sysctl.conf [ OK ] * Starting Block the mounting event for NFS filesytems until statd is running [ OK ] * Stopping Block the mounting event for NFS filesytems until statd is running [ OK ] * Starting Block the mounting event for NFS filesytems until statd is running [ OK ] * Stopping Block the mounting event for NFS filesytems until statd is running [ OK ] The last messages repeats several times, and then the boot process hangs. In 6/7 of cases, I wait for a minute, and after that bootup continues. But in approx 1/7 cases, the system hangs at this point forever. The machine does not respond to CTRL-ALT-DEL, I have to reboot it using SysRq-Keys. WORKAROUND: Setting the NFS entries in fstab to "noauto" completely removes the problem: There is no timeout during boot, and no lockup any more. The machine boote smoothly with the NFS-shares unmounted. After the machine is up, we can manually mount the NFS-shares without a problem. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-37-generic 3.2.0-37.58 ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35 Uname: Linux 3.2.0-37-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: aplay: device_list:252: keine Soundkarten gefunden ... ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 ArecordDevices: arecord: device_list:252: keine Soundkarten gefunden ... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [ 85.200104] lxcbr0: no IPv6 routers present Date: Thu Feb 7 15:50:40 2013 HibernationDevice: RESUME=UUID=6c172536-57cc-4deb-867a-0718d572f23e IwConfig: lono wireless extensions. eth0 no wireless extensions. lxcbr0no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. MarkForUpload: True ProcEnviron: LANGUAGE=de:en TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-37-generic root=/dev/mapper/lvmvg-root ro debug splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Es läuft kein PulseAudio-Dienst oder nicht als Sessiondienst. RelatedPackageVersions: linux-restricted-modules-3.2.0-37-generic N/A linux-backports-modules-3.2.0-37-generic N/A linux-firmware1.79.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to precise on 2012-04-28 (285 days ago) dmi.bios.date: 07/04/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0302:bd07/04/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97EVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1118447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages
[Kernel-packages] [Bug 1222838] Re: X fails to start with nvidia-prime on Acer Aspire V5-573G/V3-772G
As there has been nothing going on here lately: You guys still need someone doing the testing? I also own one of these Aspire V5's 573g and am facing these kinds of problems. As I'm pretty new to Ubuntu and it's Community I'm still learning my ways. Thanks for a brief update. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1222838 Title: X fails to start with nvidia-prime on Acer Aspire V5-573G/V3-772G Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Incomplete Bug description: I get offered low-graphics mode but that doesn't start a session either. Let me know if you need info beyond what comes in these logs. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nvidia-prime 0.4 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Mon Sep 9 16:52:00 2013 MarkForUpload: True PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1222838/+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 1258686] Re: [Dell Latitude D420] Faulty laptop battery or AC throws system cache for a loop
** Attachment added: "firmware test suite results - baseline" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258686/+attachment/3927631/+files/results.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/1258686 Title: [Dell Latitude D420] Faulty laptop battery or AC throws system cache for a loop Status in “linux” package in Ubuntu: Confirmed Bug description: After a random period of time after a fresh boot, the system cache gets corrupted. This is shown by hdparm -T. Before system cache corruption: Timing cached reads: 1804 MB in 2.00 seconds = 902.88 MB/sec After system cache corruption: Timing cached reads: 258 MB in 2.00 seconds = 129.10 MB/sec Either the system battery or the AC adaptor is not functioning correctly, the Dell bios at times indicates that the AC adaptor is not a valid Dell product, though it is. In any case, the battery does not charge, but remains at 0%. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asp1931 F pulseaudio Date: Fri Dec 6 18:45:58 2013 HibernationDevice: RESUME=UUID=08003f81-dc4b-4697-adb9-c4f28291be17 InstallationDate: Installed on 2013-12-06 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) MachineType: Dell Inc. Latitude D420 MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=ecd26c7d-0cb5-446e-a2ca-e4fefc0c0fd0 ro quiet splash processor.ignore_ppc=1 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: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0TJ984 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd02/02/2008:svnDellInc.:pnLatitudeD420:pvr:rvnDellInc.:rn0TJ984:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D420 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258686/+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 344631] Re: mount.ntfs-fuse not properly umounting devices?
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-ntfs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ntfs in Ubuntu. https://bugs.launchpad.net/bugs/344631 Title: mount.ntfs-fuse not properly umounting devices? Status in “linux-ntfs” package in Ubuntu: Confirmed Bug description: Trying to change a label to an ntfs partition whit ntfslabel command, I receive this message luca@luca-desktop:~$ sudo umount /dev/sdb1 luca@luca-desktop:~$ sudo ntfsfix /dev/sdb1 Mounting volume... OK Processing of $MFT and $MFTMirr completed successfully. NTFS volume version is 3.1. NTFS partition /dev/sdb1 was processed successfully. luca@luca-desktop:~$ sudo ntfslabel -v /dev/sdb1 mila Volume is scheduled for check. Please boot into Windows TWICE, or use the 'force' option. NOTE: If you had not scheduled check and last time accessed this volume using ntfsmount and shutdown system properly, then init scripts in your distribution are broken. Please report to your distribution developers (NOT to us!) that init scripts kill ntfsmount or mount.ntfs-fuse during shutdown instead of proper umount. luca@luca-desktop:~$ - Because I didn' t schedule any check, and my windows box shutdown corretly the last two times, I'm reporting this to you. I' m running Ubuntu 8.10 AMD64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-ntfs/+bug/344631/+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 1259259] Re: linux: 3.11.0-15.23 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Brendan Donegan (brendan-donegan) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1259259 Title: linux: 3.11.0-15.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Saucy: New Bug description: This bug is for tracking the 3.11.0-15.23 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 09. December 2013 17:42 UTC kernel-stable-Prepare-package-end:Tuesday, 10. December 2013 01:11 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 10. December 2013 01:11 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 10. December 2013 04:04 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Tuesday, 10. December 2013 16:04 UTC kernel-stable-Verification-testing-start:Tuesday, 10. December 2013 16:04 UTC kernel-stable-Certification-testing-start:Tuesday, 10. December 2013 16:04 UTC kernel-stable-Security-signoff-start:Tuesday, 10. December 2013 16:04 UTC kernel-stable-Regression-testing-start:Tuesday, 10. December 2013 16:04 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1259259/+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 1259259] Re: linux: 3.11.0-15.23 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed and results are available here: http://people.canonical.com/~hwcert/sru-testing/saucy/3.11.0-15.23 /saucy-proposed.html ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released ** Tags added: certification-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1259259 Title: linux: 3.11.0-15.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Saucy: New Bug description: This bug is for tracking the 3.11.0-15.23 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 09. December 2013 17:42 UTC kernel-stable-Prepare-package-end:Tuesday, 10. December 2013 01:11 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 10. December 2013 01:11 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 10. December 2013 04:04 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Tuesday, 10. December 2013 16:04 UTC kernel-stable-Verification-testing-start:Tuesday, 10. December 2013 16:04 UTC kernel-stable-Certification-testing-start:Tuesday, 10. December 2013 16:04 UTC kernel-stable-Security-signoff-start:Tuesday, 10. December 2013 16:04 UTC kernel-stable-Regression-testing-start:Tuesday, 10. December 2013 16:04 UTC kernel-stable-Certification-testing-end:Wednesday, 11. December 2013 16:04 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1259259/+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 1259259] Re: linux: 3.11.0-15.23 -proposed tracker
** Description changed: This bug is for tracking the 3.11.0-15.23 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 09. December 2013 17:42 UTC kernel-stable-Prepare-package-end:Tuesday, 10. December 2013 01:11 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 10. December 2013 01:11 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 10. December 2013 04:04 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Tuesday, 10. December 2013 16:04 UTC kernel-stable-Verification-testing-start:Tuesday, 10. December 2013 16:04 UTC kernel-stable-Certification-testing-start:Tuesday, 10. December 2013 16:04 UTC kernel-stable-Security-signoff-start:Tuesday, 10. December 2013 16:04 UTC kernel-stable-Regression-testing-start:Tuesday, 10. December 2013 16:04 UTC + kernel-stable-Certification-testing-end:Wednesday, 11. December 2013 16:04 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1259259 Title: linux: 3.11.0-15.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in “linux” package in Ubuntu: Invalid Status in “linux” source package in Saucy: New Bug description: This bug is for tracking the 3.11.0-15.23 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 09. December 2013 17:42 UTC kernel-stable-Prepare-package-end:Tuesday, 10. December 2013 01:11 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 10. December 2013 01:11 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 10. December 2013 04:04 UTC kernel-stable-phase:Verification & Testing kernel-stable-phase-changed:Tuesday, 10. December 2013 16:04 UTC kernel-stable-Verification-testing-start:Tuesday, 10. December 2013 16:04 UTC kernel-stable-Certification-testing-start:Tuesday, 10. December 2013 16:04 UTC kernel-stable-Security-signoff-start:Tuesday, 10. December 2013 16:04 UTC kernel-stable-Regression-testing-start:Tuesday, 10. December 2013 16:04 UTC kernel-stable-Certification-testing-end:Wednesday, 11. December 2013 16:04 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1259259/+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 1259829] Re: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name
Did this issue occur in a previous version of Ubuntu, or is this a new issue? 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.13-rc3-trusty/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 Status in “linux” package in Ubuntu: Incomplete Bug description: fs goes into read-only mode while build lo $ dmesg ... [ 2045.473249] virbr0: port 1(vnet0) entered forwarding state [ 2045.473283] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready [10660.961381] perf samples too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 5 [11822.935891] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 [11822.935896] Aborting journal on device dm-1-8. [11822.935998] EXT4-fs (dm-1): Remounting filesystem read-only [11822.960425] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629605: block 214443466: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2707156714, rec_len=19312, name_len=162 [11850.985003] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629557: block 214443458: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=512948573, rec_len=8858, name_len=176 [11850.985276] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629465: block 214443455: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=160939375, rec_len=26085, name_len=126 [11850.985499] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629325: block 214443451: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2322664969, rec_len=33791, name_len=132 [11850.985927] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629467: block 214443456: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=954332768, rec_len=21653, name_len=30 [11850.986409] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629074: block 214443433: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2061605548, rec_len=4984, name_len=3 [11850.986831] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53628835: block 214443432: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=3523041938, rec_len=53167, name_len=41 [11850.987001] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629098: block 214443436: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4225920287, rec_len=35138, name_len=75 [11850.987466] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629275: block 214443449: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=923253145, rec_len=44001, name_len=144 [11850.988115] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629270: block 214443448: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1892288796, rec_len=55247, name_len=58 [11851.042303] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629300: block 214443450: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=1809316884, rec_len=4208, name_len=195 [11851.042938] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629401: block 214443453: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4223616103, rec_len=36326, name_len=130 [11851.045745] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629406: block 214443454: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=415237227, rec_len=24702, name_len=59 [11851.125849] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629101: block 214443437: comm rm: bad entry in directory: directory ent
[Kernel-packages] [Bug 1258675] Re: hardware switch of wireless not working for Centrino Advanced-N 6235
I have now tested the latest mainline kernel, namely I used the image linux- image-3.13.0-031300rc3-generic_3.13.0-031300rc3.201312061335_amd64.deb E.g. I can see vmlinuz -> boot/vmlinuz-3.13.0-031300rc3-generic in the / directory. The system behaves in the same way as with the ordinary kernel: I can not turn the wireless radio on/off using the hardware switch. The software control works. ** 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/1258675 Title: hardware switch of wireless not working for Centrino Advanced-N 6235 Status in “linux” package in Ubuntu: Incomplete Bug description: I have ubuntu 13.10 64-bit running on a HP ZBook 15. The notebook uses an Intel Corporation Centrino Advanced-N 6235 (rev 24) wireless adapter. The wireless networking principally works. The issue is that it is not possible to enable or disable it using the hardware button. The only way is the software control (clicking on "Enable Wi-Fi"). BTW, when I click on "Enable Wi-Fi", it indicates the changes status of the wifi radio by changing the colour of the light on the hardware button. (This is the correct and expected behaviour. What is wrong is that I can not change the status by pressing the hardware button.) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-firmware 1.116 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Dec 6 23:04:18 2013 Dependencies: InstallationDate: Installed on 2013-12-04 (2 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258675/+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 1245150] Re: 0a12:0001 Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesn't work after upgrading to Saucy
I have not yet given up hope.. I am trying to do the bisection, but everytime I get into the situation of not being able to boot the kernel. For someone who hasn't done anything like this before; building the kernels and bisecting it to get hold of the bad commit is a pretty daunting task indeed. Any it takes upwards to 2.5hours to build the kernel on my system. So, I am still doing the bisection as and when possible and would report things in due course. However, is it possible to provide more parameters to `git bisect start` in order to cut down the number of bisections required in this case; as mentioned over here: https://www.kernel.org/pub/software/scm/git/docs/git- bisect.html#_cutting_down_bisection_by_giving_more_parameters_to_bisect_start -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1245150 Title: 0a12:0001 Bluetooth Dongle (Cambridge Silicon Radio, Ltd) doesn't work after upgrading to Saucy Status in “linux” package in Ubuntu: Incomplete Bug description: After upgrading to Saucy, the bluetooth-indicator was no longer present in the taskbar. If I go to System Settings >> Bluetooth; it shows as "Bluetooth is disabled" and toggling the On|Off Switch doesn't enable it: http://i.stack.imgur.com/vwfEo.png I have installed the Blueman Device Manager to solve this issue and its bluetooth indicator is shown on the taskbar, but it doesn't function. However, toggling the On|Off switch in System Settings >> Bluetooth, grays out the icon of Blueman indicator in the taskbar. To debug the issue, I am following the instructions mentioned at https://wiki.ubuntu.com/Kernel/KernelBisection. I have downloaded and installed the kernals from https://launchpad.net/ubuntu/saucy/+source/linux: - 3.9.0-7.15 works for me - 3.10.0-0.6 doesn't work For further commit bisecting, I have downloaded the git repository of `ubuntu-saucy` by running: git clone git://kernel.ubuntu.com/ubuntu /ubuntu-saucy.git To see how many commits are there in between, I run the following command: git log --oneline Ubuntu-3.9.0-7.15..Ubuntu-3.10.0-0.6 | wc 14802 117434 922801 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aditya 1767 F pulseaudio /dev/snd/pcmC0D0c: aditya 1767 F...m pulseaudio /dev/snd/pcmC0D0p: aditya 1767 F...m pulseaudio CurrentDmesg: [ 23.616595] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 23.617367] alx :02:00.0 eth0: NIC Up: 100 Mbps Full [ 23.617591] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Sun Oct 27 15:17:38 2013 HibernationDevice: RESUME=UUID=98bed5fe-b467-4bb4-9173-177ee22f8c76 InstallationDate: Installed on 2013-07-06 (112 days ago) InstallationMedia: This IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-S2PT MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=1274a22c-31b4-4c65-8a0f-8eede0288fea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-18 (8 days ago) dmi.bios.date: 11/05/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FC dmi.board.name: GA-78LMT-S2PT dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFC:bd11/05/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2PT:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2PT:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-S2PT dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245150/+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 1259861] Re: 5-10 second delay in kernel boot
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.13-rc3-trusty/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1259861 Title: 5-10 second delay in kernel boot Status in “linux” package in Ubuntu: Incomplete Bug description: In Trusty I see a big delay while the kernel boots that I did not see back in Precise. Some people have been experiencing this in Saucy too, so I don't know exactly when it started happening. Excerpt from dmesg: [3.740100] Switched to clocksource tsc [ 14.208118] PM: Hibernation image not present or could not be loaded. [ 14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000) The exact messages above don't matter, they are different on different boots or on different machines. It even happens with e.g. $ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso My current kernel is Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 i686 i686 GNU/Linux ...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run `dmesg` yourself and check if there's a big delay there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259861/+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 1259846] Re: "Lost connection" errors due to failure of handling EINTR correctly
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.13-rc3-trusty/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Bug watch added: Debian Bug tracker #715065 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715065 ** Also affects: linux via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715065 Importance: Unknown Status: Unknown ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1259846 Title: "Lost connection" errors due to failure of handling EINTR correctly Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Incomplete Bug description: Hello guys! We have got this bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715065 in ubuntu "precise" Our strace: pid 20763] write(7, "0\3\0\0\3SELECT mc.cid\n FROM ... mc\n ... LIMIT 120 OFFSET 0", 820 [pid 20763] <... write resumed> ) = 820 [pid 20763] read(7, [pid 20763] <... read resumed> 0x9b87ba0, 16384) = -1 EINTR (Interrupted system call) [pid 20763] --- SIGCHLD (Child exited) @ 0 (0) --- [pid 20763] rt_sigreturn(0 [pid 20763] <... rt_sigreturn resumed> ) = -1 EINTR (Interrupted system call) [pid 20763] shutdown(7, 2 /* send and receive */ [pid 20763] <... shutdown resumed> )= 0 [pid 20763] close(7 [pid 20763] <... close resumed> ) = 0 [pid 20763] write(2, "DBD::mysql::st execute failed: Lost connection to MySQL server during query at /usr/share/perl5/Yandex/DBTools.pm line 814.\n", 124DBD::mysql::st execute failed: Lost ackage: libmysqlclient18 Source: percona-server-5.5 Version: 1:5.5.34-rel32.0-591.precise Architecture: amd64 Maintainer: Percona Server Development Team Installed-Size: 3103 Replaces: libpercona-server-client18 Homepage: http://www.percona.com/software/percona-server/ Priority: extra Section: libs Filename: pool/main/p/percona-server-5.5/libmysqlclient18_5.5.34-rel32.0-591.precise_amd64.deb Size: 840708 SHA256: fbff998bf2d9c13a58e019600954765a037ca8f9da80847fd6cee68bba462579 SHA1: cc71b36386c0e1a5b532647fb9dc1314dd376036 MD5sum: 3cc1f960a217d6ac6f7f184c81a38272 Description: Percona Server database client library Percona Server is a fast, stable and true multi-user, multi-threaded SQL database server. SQL (Structured Query Language) is the most popular database query language in the world. The main goals of Percona Server are speed, robustness and ease of use. . This package includes the client library. # cat /proc/version Linux version 2.6.32-042stab076.5 (root@rh6-build-x64) (gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Mon Mar 18 20:41:34 MSK 2013 #lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 12.04.1 LTS Release:12.04 Codename: precise To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1259846/+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 1259850] Re: KDE powermanagement crashes kernel
** Package changed: linux (Ubuntu) => meta-kde (Ubuntu) ** Changed in: meta-kde (Ubuntu) Status: Confirmed => 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/1259850 Title: KDE powermanagement crashes kernel Status in “meta-kde” package in Ubuntu: New Bug description: I have a Dell Latitude D6510 running (K)ubuntu 13.10 with the current kernel (3.11.0-14). In KDE when I pull the power cord, the system instantly freezes - completely, leaving no helpful traces of the cause in syslog or pm-powersave.log. It does not happen w/o a running KDE session or when I switch to Unity or XFCE. Hence, I suspect KDE triggering the bug. Googling for "power unplug crash linux kernel" yields a bunch of somewhat similiar issues, but those all seem slightly diffrent from what I see. In fact, I have had the/an "unplug crash issue" before like a year or so ago. Somehow it vanished, and now it is back again, so this could be a kernel regression. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: deas 6090 F pulseaudio DistroRelease: Ubuntu 13.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=901a5939-36e9-4493-9f9d-68a6fea3613e InstallationDate: Installed on 2011-03-07 (1009 days ago) InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101008) MachineType: Dell Inc. Latitude E6510 MarkForUpload: True Package: linux 3.11.0.14.15 PackageArchitecture: amd64 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (54 days ago) UserGroups: adm admin cdrom dialout libvirtd lp lpadmin plugdev sambashare vboxusers dmi.bios.date: 05/09/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 02K3Y4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/09/2012:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn02K3Y4:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-kde/+bug/1259850/+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 1259727] Re: Crashes under load
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.13-rc3-trusty/ ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1259727 Title: Crashes under load Status in “linux” package in Ubuntu: Incomplete Bug description: The Wandboard Quad crashes under load. This can be triggered by running "apt-get upgrade" or a scripts that converts a git repository to bzr, for example. It does not crash every time, but often enough to reproduce the crash. Attached the output of dmesg after the crash. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.12.0-7-generic 3.12.0-7.15 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic armv7l AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 1 1970 seq crw-rw 1 root audio 116, 33 Jan 1 1970 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.12.0-7-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.12.7-0ubuntu2 Architecture: armhf ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' 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: 'iw' CurrentDmesg: Date: Tue Dec 10 23:38:45 2013 HibernationDevice: RESUME=UUID=174445a8-0f41-440c-a1c4-9d6e6657b834 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcFB: ProcKernelCmdLine: ro quiet splash root=UUID=5b2e9784-4869-4303-a512-a7f29dde7cf1 RelatedPackageVersions: linux-restricted-modules-3.12.0-7-generic N/A linux-backports-modules-3.12.0-7-generic N/A linux-firmware1.117 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' 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/1259727/+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 1259736] Re: System Crashed
Did this issue occur in a previous version of Ubuntu, or is this a new issue? 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.13-rc3-trusty/ ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1259736 Title: System Crashed Status in “linux” package in Ubuntu: Incomplete Bug description: I suspect this is a bug in Ext4 and it's handling of sparse files, specifically recent(ish) additions that allow hole punching with "fallocate". I have an application that makes much use of "fallocate" and whereas it generally works just fine, it seems that under stress the kernel has problems. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.11.0-13-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Tue Dec 10 23:17:10 2013 HibernationDevice: RESUME=/dev/mapper/data2-swap InstallationDate: Installed on 2013-11-08 (32 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) MachineType: System manufacturer System Product Name MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-13-generic root=/dev/mapper/hostname-root ro RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/05/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3029 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO 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.:bvr3029:bd07/05/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO: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/1259736/+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 1237296] Re: ath9k QCA9565/AR9565/QCWB335 Bluetooth not working
You mentioned that you got the patch from the author on the ath9k-devel mailinglist. Can you ping the patch author and see if you submitted the patch upstream or if there is a reason why he did not? Once the patch lands upstream, we can cherry-pick it into the Ubuntu 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/1237296 Title: ath9k QCA9565/AR9565/QCWB335 Bluetooth not working 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: Hello, I got myself a brand new Acer Aspire E1-572-54204G50Mnkk, because of the shine new Haswell hardware I choose to install Ubuntu 13.10 Beta 2. This laptop uses a Atheros AR9565 802.11 b/g/n 1 × 1 WiFi + Bluetooth 4.0 combination adapter, Wireless is working fine. But Bluetooth doesn't, it seems to be successfully deteced but I can't see any other Bluetooth devices and they can't see me too. Yours sincerly Joshua --- ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-10-12 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) MarkForUpload: True Package: linux (not installed) ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: saucy Uname: Linux 3.12.0-031200rc4-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: --- ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshua 1348 F pulseaudio /dev/snd/controlC0: joshua 1348 F pulseaudio DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-10-12 (8 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) MachineType: Acer Aspire E1-572 MarkForUpload: True Package: linux (not installed) ProcEnviron: LANGUAGE=de_DE 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.efi.signed root=UUID=287c8de2-616f-42ec-998d-1ac09ffb2d8a ro quiet splash vt.handoff=7 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 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/21/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HW dmi.board.vendor: Acer dmi.board.version: V2.04 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.04:bd05/21/2013:svnAcer:pnAspireE1-572:pvrV2.04:rvnAcer:rnEA50_HW:rvrV2.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.name: Aspire E1-572 dmi.product.version: V2.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237296/+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 1259570] Re: kexec should get a disabling sysctl
Patch v2: https://lkml.org/lkml/2013/12/9/790 ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Medium Assignee: Tyler Hicks (tyhicks) Status: Confirmed ** Also affects: linux (Ubuntu Raring) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Saucy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Precise) Status: New => Confirmed ** Changed in: linux (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Precise) Assignee: (unassigned) => Tyler Hicks (tyhicks) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1259570 Title: kexec should get a disabling sysctl Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Precise: Confirmed Status in “linux” source package in Quantal: New Status in “linux” source package in Raring: New Status in “linux” source package in Saucy: New Status in “linux” source package in Trusty: Confirmed Bug description: To enable kexec makes sense for a generic distro kernel. But if your users have root in their virtual machines, and you want to make it hard for them to run code in ring 0, you commonly disable further module loading and you also want to disable kexec[1]. Kees Cook wrote up a patch[2] that we'd like to see applied to the Ubuntu kernel to avoid recompilation of the distro kernel. I'm marking this as a security issue on the ground that it's quite surprising that setting kernel.modules_disabled=1 as a hardening feature can be subverted by using kexec. [1] http://mjg59.dreamwidth.org/28746.html [2] https://lkml.org/lkml/2013/12/9/765 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259570/+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 1201528] Re: [INTEL DP55WG, Realtek ALC889] - Audio Playback Unavailable
I started a kernel bisect between 3.8.13.1 and 3.8.13.2 . The kernel bisect will require testing of about 7-10 test kernels. I built the first test kernel, up to the following commit: 90856193fc94eec039ab17bbde2906d6fc6919c6 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1201528 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/1201528 Title: [INTEL DP55WG,Realtek ALC889] - Audio Playback Unavailable Status in “alsa-driver” package in Ubuntu: New Status in “linux” package in Ubuntu: Incomplete Status in “alsa-driver” source package in Raring: New Status in “linux” source package in Raring: Incomplete Status in “alsa-driver” source package in Saucy: New Status in “linux” source package in Saucy: Incomplete Bug description: This is a fresh upgrade to raring. During the weekend, I updated from precise to quantal, and from there to raring. I did not use sound while the system was in quantal, so no idea if the bug was present there as well. The symptom is: * after some period of sound usage, playback stops working What I mean with sound usage is: I tried having a meeting with: mumble, skype, and google hangout, and in all three cases, audio input/outout will work just fine for ~5 minutes, and the playback just dies (people tell me they keep listening to me, so mic works fine). The only way to solve this is by rebooting. After one of the reboots, I was able to play a 20 minute video with mplayer with no further issue. Then opened skype and after ~3-5 minute talk, audio playback died again. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nessita2627 F pulseaudio Date: Mon Jul 15 14:40:20 2013 InstallationDate: Installed on 2011-12-20 (572 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (2029.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_AlsaPlaybackTestStderr: W r i t e e r r o r : - 5 , I n p u t / o u t p u t e r r o r x r u n _ r e c o v e r y f a i l e d : - 5 , I n p u t / o u t p u t e r r o r T r a n s f e r f a i l e d : O p e r a t i o n n o t p e r m i t t e d Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Headphone Out, Front Symptom_Type: None of the above Title: [, Realtek ALC889, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to raring on 2013-07-13 (2 days ago) dmi.bios.date: 08/05/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: KGIBX10J.86A.3206.2009.0805.1855 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WG dmi.board.vendor: Intel Corporation dmi.board.version: AAE57269-404 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrKGIBX10J.86A.3206.2009.0805.1855:bd08/05/2009:svn:pn:pvr:rvnIntelCorporation:rnDP55WG:rvrAAE57269-404:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1201528/+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 1258303] Re: PPC: Live CD doesn't produce live session
*** This bug is a duplicate of bug 1257372 *** https://bugs.launchpad.net/bugs/1257372 This bug is still present in today's PPC Live CD. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ppc in Ubuntu. https://bugs.launchpad.net/bugs/1258303 Title: PPC: Live CD doesn't produce live session Status in “linux-ppc” package in Ubuntu: New Bug description: The PPC Live iso for 20131205 stalls at the plymouth splash screen. I was able to get to a console and ran ubuntu-bug linux to get this report. I had to use another computer to actually file the bug report. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.11.0-3-powerpc-smp 3.11.0-3.5 ProcVersionSignature: Ubuntu 3.11.0-3.5-powerpc-smp 3.11.3 Uname: Linux 3.11.0-3-powerpc-smp ppc ApportVersion: 2.12.7-0ubuntu1 Architecture: powerpc CasperVersion: 1.336ubuntu1 Date: Thu Dec 5 20:52:17 2013 LiveMediaBuild: Lubuntu 14.04 "Trusty Tahr" - Alpha powerpc (20131205) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-ppc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1258303/+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 995456] Re: Duplicate ACPI video bus devices for the same VGA controller
I ran FWTS on my system and it gave the following:
ADVICE: The ACPI video driver has found a duplicate ACPI video bus device for
the same VGA controller. If the current driver does not work, one can try to
work around this using the video.allow_duplicates=1 kernel parameter.
Note: Dell D420, Ubuntu 14.04, kernel: 3.11.0-14
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/995456
Title:
Duplicate ACPI video bus devices for the same VGA controller
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
The same bug in:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/938631
I have Ubuntu 11.10 with all the last update.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-19-generic 3.0.0-19.33
ProcVersionSignature: Ubuntu 3.0.0-19.33-generic 3.0.27
Uname: Linux 3.0.0-19-generic x86_64
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 1.23-0ubuntu4
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/controlC0: daniele1941 F pulseaudio
CRDA: Error: [Errno 2] File o directory non esistente
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf6fdc000 irq 47'
Mixer name : 'IDT 92HD71B7X'
Components : 'HDA:111d76b2,1028024f,00100302'
Controls : 15
Simple ctrls : 10
Date: Sun May 6 14:28:38 2012
HibernationDevice: RESUME=UUID=c757a0dc-e6d0-474f-a874-73d8eabbafdc
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: Dell Inc. Latitude E6500
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-19-generic
root=UUID=5a3064d5-8e85-4983-9541-82de5f238f2b ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.0.0-19-generic N/A
linux-backports-modules-3.0.0-19-generic N/A
linux-firmware1.60
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/06/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A27
dmi.board.asset.tag: 4Q9XX3J
dmi.board.vendor: Dell Inc.
dmi.chassis.asset.tag: 4Q9XX3J
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA27:bd12/06/2011:svnDellInc.:pnLatitudeE6500:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E6500
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/995456/+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 1244438] Re: EOL notification system required for HWE kernels in LTSs
Canonical's OEM preinstall team would like to have a way to control the timing of the update. One way to do this is to provide a way to opt-out of the default upgrade notification, such as by dropping a file on disk via a software update delivered only to those OEM preinstall machines (we have a way to do this already). The second part of the request is a way to opt in/trigger the notification to the end user. The reason is that Canonical in conjunction with OEMs will do upgrade tests on preloaded hardware to ensure that end users with this hardware have a smooth upgrade path to the next LTS kernel. We'd like to delay the upgrade notifications until those upgrades are tested. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1244438 Title: EOL notification system required for HWE kernels in LTSs Status in Release Notes for Ubuntu: New Status in “landscape” package in Ubuntu: New Status in “linux” package in Ubuntu: Triaged Status in “unattended-upgrades” package in Ubuntu: New Status in “update-manager” package in Ubuntu: New Status in “update-motd” package in Ubuntu: New Bug description: We need to have some mechanism to allow us to record that you have an EOL kernel installed which will no longer recieve updates. For example for the kernel when a kernel is going EOL the last upload should include an appropriate file: /var/lib/update-notifier/kernel-eol We need to coordinate this with the notifier itself to ensure it is displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1244438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1124040] Re: 8086:1502 [Lenovo ThinkPad W520] e1000e reconnecting in 12.04
Sergey Spiridonov, so your hardware may be tracked, could you please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via: ubuntu-bug linux For more on this, please read the official Ubuntu documentation: Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette When opening up the new report, please feel free to subscribe me to it. Thank you for your understanding. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1124040 Title: 8086:1502 [Lenovo ThinkPad W520] e1000e reconnecting in 12.04 Status in “linux” package in Ubuntu: Incomplete Bug description: The Intel e1000e kernel NIC driver is constantly reconnecting to my network causing flowstops and errors. I do not know in which exact kernel the problem started since I do not use this laptop wired regularly. Firstly I suspected faulty networking equipment, but the problem persisted on other hardware. WORKAROUND: Fetch driver directly from Intel: http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=15817&ProdId=3003&lang=eng Error: Feb 13 12:04:52 stevieray kernel: [ 1451.580536] e1000e: eth0 NIC Link is Down Feb 13 12:04:53 stevieray kernel: [ 1453.229010] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx Feb 13 12:04:53 stevieray kernel: [ 1453.229024] e1000e :00:19.0: eth0: 10/100 speed: disabling TSO Feb 13 12:04:53 stevieray NetworkManager[1088]: (eth0): carrier now ON (device state 100) Feb 13 12:05:01 stevieray CRON[3406]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Feb 13 12:05:14 stevieray NetworkManager[1088]: (eth0): carrier now OFF (device state 100, deferring action for 4 seconds) Feb 13 12:05:14 stevieray kernel: [ 1473.312198] e1000e: eth0 NIC Link is Down Feb 13 12:05:15 stevieray kernel: [ 1474.944394] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx Feb 13 12:05:15 stevieray kernel: [ 1474.944409] e1000e :00:19.0: eth0: 10/100 speed: disabling TSO Feb 13 12:05:15 stevieray NetworkManager[1088]: (eth0): carrier now ON (device state 100) Feb 13 12:05:27 stevieray NetworkManager[1088]: (eth0): carrier now OFF (device state 100, deferring action for 4 seconds) Feb 13 12:05:27 stevieray kernel: [ 1486.340811] e1000e: eth0 NIC Link is Down Feb 13 12:05:28 stevieray kernel: [ 1488.008923] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx Feb 13 12:05:28 stevieray kernel: [ 1488.008938] e1000e :00:19.0: eth0: 10/100 speed: disabling TSO Feb 13 12:05:28 stevieray NetworkManager[1088]: (eth0): carrier now ON (device state 100) With the Intel Driver: [ 2214.353191] e1000e :00:19.0: PCI INT A disabled [ 2824.335482] e1000e: Intel(R) PRO/1000 Network Driver - 2.2.14-NAPI [ 2824.335491] e1000e: Copyright(c) 1999 - 2012 Intel Corporation. [ 2824.335548] e1000e :00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20 [ 2824.335570] e1000e :00:19.0: setting latency timer to 64 [ 2824.335753] e1000e :00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 2824.347221] e1000e :00:19.0: irq 50 for MSI/MSI-X [ 2824.578329] e1000e :00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) f0:de:f1:67:84:e9 [ 2824.578340] e1000e :00:19.0: eth0: Intel(R) PRO/1000 Network Connection [ 2824.578405] e1000e :00:19.0: eth0: MAC: 11, PHY: 11, PBA No: 1000FF-0FF [ 2824.737160] e1000e :00:19.0: irq 50 for MSI/MSI-X [ 2824.840802] e1000e :00:19.0: irq 50 for MSI/MSI-X [ 2824.843896] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 2824.845415] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 2867.226514] e1000e: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx [ 2867.226529] e1000e :00:19.0: eth0: 10/100 speed: disabling TSO [ 2867.229384] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nikolaj2516 F pulseaudio /dev/snd/controlC0: nikolaj2516 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xd832 irq 53' Mixer name : 'Conexant CX20590' Components : 'HDA:14f1506e,17aa21cf,0010 HDA:14f12c
[Kernel-packages] [Bug 1222838] Re: X fails to start with nvidia-prime on Acer Aspire V5-573G/V3-772G
Florian Mang, so your hardware may be tracked, could you please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via: ubuntu-bug linux For more on this, please read the official Ubuntu documentation: Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette When opening up the new report, please feel free to subscribe me to it. Thank you for your understanding. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1222838 Title: X fails to start with nvidia-prime on Acer Aspire V5-573G/V3-772G Status in The Linux Kernel: Unknown Status in “linux” package in Ubuntu: Incomplete Bug description: I get offered low-graphics mode but that doesn't start a session either. Let me know if you need info beyond what comes in these logs. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nvidia-prime 0.4 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Mon Sep 9 16:52:00 2013 MarkForUpload: True PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1222838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1107150] Re: B75 Chipset I/O Problems
The bisect identified the following commit: commit 252c3d84ed398b090ac2dace46fc6faa6cfaea99 Author: RongQing.Li Date: Thu Jan 12 22:33:46 2012 + ipv6: release idev when ip6_neigh_lookup failed in icmp6_dst_alloc I'm not sure if this is the real root cause. However, I built a mainline test kernel with this commit reverted. Can you give this kernel a test to see if it still exhibits the bug: The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1107150 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1107150 Title: B75 Chipset I/O Problems Status in “linux” package in Ubuntu: Confirmed Bug description: I built a new system and installed Ubuntu 12.10. The system has the following specifications: Samsung 840 Pro 128 GB Gigabyte P75-D3 Intel i7 3770 32 GB Ram Western Digital 1 TB Black (mounted as /home) Western Digital 3 TB Green (mounted as /media/data_drive) The initial Ubuntu 12.10 install took almost 6 hours as transfer rates were very slow. After reboot everything appeared very fast. However when I did an "apt-get update" the download took 20 seconds and the processing of lists took 19 minutes. I had 12.10 installed on another computer which was working great (older Althon system) so I installed the drive and tested the new machine. It suffered the same performance problems. I installed Windows 7 and performed speeds tests, it reported great results. I installed 12.04 onto the 1 TB drive and it did not suffer the same performance problems. Everything ran great. I then upgraded 12.10 to 13.04 (January 27, 2013) and it too suffered from the performance issue. It appears that a change between 12.04 to 12.10 impacts AHCI based systems specifically running the Intel B75 chipset. I am not certain but I think that either the motherboard is misrepresenting something (that 12.04 ignores but it impacts 12.10) or the kernel is not detecting the system correctly. I created a couple of pastebins with data collected: 12.10 Install: http://pastebin.ubuntu.com/1561660/ 12.04 Live Disk (was checked against installed version and data is mostly the same): http://paste.ubuntu.com/1565140/ I have a thread on the ubuntu forums that may provide additional details: http://ubuntuforums.org/showthread.php?t=2104709 I also started an e-mail thread to the ubuntu-users mailing list: http://ubuntu.5.n6.nabble.com/Seeking-Help-td5010422.html I have done a lot of troubleshooting and I feel that the problem must either be the kernel or the bios misrepresenting information. In either case I am stuck without any idea of where to go next with the debuging and diagnoses path. If any additional information needs to be collected, please let me know and I will work to assist. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bakers 1729 F pulseaudio /dev/snd/controlC0: bakers 1729 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf711 irq 45' Mixer name : 'Realtek ALC887-VD' Components : 'HDA:10ec0887,1458a002,00100302' Controls : 39 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583553,00100100' Controls : 18 Simple ctrls : 3 DistroRelease: Ubuntu 12.04 IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-36-generic-pae root=UUID=4f30252c-fa56-4d53-be78-117cddab55f4 ro quiet splash ProcVersionSignature: Ubuntu 3.2.0-36.57-generic-pae 3.2.35 RelatedPackageVersions: linux-restricted-modules-3.2.0-36-generic-pae N/A linux-backports-modules-3.2.0-36-generic-pae N/A linux-firmware1.79.1 RfKill: StagingDrivers: mei Tags: precise running-unity staging Uname: Linux 3.2.0-36-generic-pae i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/21/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P75-D3 dmi.board.vendor: Gigabyte Technology Co., Ltd.
[Kernel-packages] [Bug 1256988] Re: netns: crash during namespace destroy
** Description changed: [Impact] * When restoring an iptable in a network namespace, if the network namespace is deleted the kernel crashes. [Test Case] $ sudo -s # ip netns add foobar # ip netns exec foobar iptables -A OUTPUT -m recent --rcheck --rsource # ip netns del foobar [Regression Potential] * The following patches fix the issue: 665e205c1 32263dd1b - http://patchwork.ozlabs.org/patch/294312/ + http://www.spinics.net/lists/netfilter-devel/msg29196.html Two are upstream patches, while the last one hasn't been accepted upstream yet. ** Description changed: [Impact] * When restoring an iptable in a network namespace, if the network namespace is deleted the kernel crashes. [Test Case] $ sudo -s # ip netns add foobar # ip netns exec foobar iptables -A OUTPUT -m recent --rcheck --rsource # ip netns del foobar [Regression Potential] * The following patches fix the issue: 665e205c1 32263dd1b - http://www.spinics.net/lists/netfilter-devel/msg29196.html + https://git.kernel.org/cgit/linux/kernel/git/pablo/nf.git/commit/?id=b4ef4ce09308955d1aa54a289c0162607b3aa16c Two are upstream patches, while the last one hasn't been accepted upstream yet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1256988 Title: netns: crash during namespace destroy Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Precise: In Progress Status in “linux” source package in Quantal: In Progress Status in “linux” source package in Raring: Fix Released Bug description: [Impact] * When restoring an iptable in a network namespace, if the network namespace is deleted the kernel crashes. [Test Case] $ sudo -s # ip netns add foobar # ip netns exec foobar iptables -A OUTPUT -m recent --rcheck --rsource # ip netns del foobar [Regression Potential] * The following patches fix the issue: 665e205c1 32263dd1b https://git.kernel.org/cgit/linux/kernel/git/pablo/nf.git/commit/?id=b4ef4ce09308955d1aa54a289c0162607b3aa16c Two are upstream patches, while the last one hasn't been accepted upstream yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1256988/+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 1258686] Re: [Dell Latitude D420] Faulty laptop battery or AC throws system cache for a loop
Looking though the FWTS results, I see that the most recent microcode is not being loaded. Attempting to fix that runs me into https://bugs.launchpad.net/initramfs-tools/+bug/1194370 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1258686 Title: [Dell Latitude D420] Faulty laptop battery or AC throws system cache for a loop Status in “linux” package in Ubuntu: Confirmed Bug description: After a random period of time after a fresh boot, the system cache gets corrupted. This is shown by hdparm -T. Before system cache corruption: Timing cached reads: 1804 MB in 2.00 seconds = 902.88 MB/sec After system cache corruption: Timing cached reads: 258 MB in 2.00 seconds = 129.10 MB/sec Either the system battery or the AC adaptor is not functioning correctly, the Dell bios at times indicates that the AC adaptor is not a valid Dell product, though it is. In any case, the battery does not charge, but remains at 0%. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asp1931 F pulseaudio Date: Fri Dec 6 18:45:58 2013 HibernationDevice: RESUME=UUID=08003f81-dc4b-4697-adb9-c4f28291be17 InstallationDate: Installed on 2013-12-06 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) MachineType: Dell Inc. Latitude D420 MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=ecd26c7d-0cb5-446e-a2ca-e4fefc0c0fd0 ro quiet splash processor.ignore_ppc=1 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: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0TJ984 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd02/02/2008:svnDellInc.:pnLatitudeD420:pvr:rvnDellInc.:rn0TJ984:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D420 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258686/+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 1253825] Re: PPC: Live CD boots to login window instead of live desktop; asks for password to continue.
This bug effects me, lubuntu i386, 20131211. Live CD boots to a login box on the background wallpaper instead of the live desktop. Either crashes to tty when you click in it / press enter or (what's the user/password) ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-ppc in Ubuntu. https://bugs.launchpad.net/bugs/1253825 Title: PPC: Live CD boots to login window instead of live desktop; asks for password to continue. Status in “linux-ppc” package in Ubuntu: Fix Released Bug description: Live CD boots to a login box on the background wallpaper instead of the live desktop. It wants a password to be entered to continue. I was able to get to a console to file this bug. I used ubuntu-bug linux, copied down the provided URL and then filed the bug using another computer. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.11.0-3-powerpc-smp 3.11.0-3.5 ProcVersionSignature: Ubuntu 3.11.0-3.5-powerpc-smp 3.11.3 Uname: Linux 3.11.0-3-powerpc-smp ppc ApportVersion: 2.12.7-0ubuntu1 Architecture: powerpc CasperVersion: 1.336ubuntu1 Date: Thu Nov 21 22:43:51 2013 LiveMediaBuild: Lubuntu 14.04 "Trusty Tahr" - Alpha powerpc (20131120) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-ppc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-ppc/+bug/1253825/+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 1258058] Re: Brightness control no effect on screen
Q: 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]. A: I tested with 3.12 kernel and it still didnt work A: now I'm trying to test with leatest kernel from your comment footnote [0] but last version is not v3.13-rc2 but v3.13-rc3 before restart I received these error messages: ... Error! Bad return status for module build on kernel: 3.13.0-031300rc3-generic (x86_64) Consult /var/lib/dkms/nvidia-319-updates/319.60/build/make.log for more information. ERROR (dkms apport): binary package for nvidia: 331.20 not found Error! Bad return status for module build on kernel: 3.13.0-031300rc3-generic (x86_64) Consult /var/lib/dkms/nvidia/331.20/build/make.log for more information. ... Error! Bad return status for module build on kernel: 3.13.0-031300rc3-generic (x86_64) Consult /var/lib/dkms/nvidia-319-updates/319.60/build/make.log for more information. ERROR (dkms apport): binary package for nvidia: 331.20 not found Error! Bad return status for module build on kernel: 3.13.0-031300rc3-generic (x86_64) Consult /var/lib/dkms/nvidia/331.20/build/make.log for more information. ... make.log is attached. I'll continue if I manage to boot the system after this exercise :) ** Attachment added: "/var/lib/dkms/nvidia/331.20/build/make.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258058/+attachment/3927704/+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/1258058 Title: Brightness control no effect on screen Status in “linux” package in Ubuntu: Incomplete Bug description: Brightness control no effect on screen, I managed to get control over brightness by using xbacklight. My issue (laptop and everything else) is exactly the same as this one http://ubuntuforums.org/showthread.php?t=2167180 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: radenkovich 2284 F pulseaudio /dev/snd/controlC0: radenkovich 2284 F pulseaudio Date: Thu Dec 5 09:45:30 2013 HibernationDevice: RESUME=UUID=ea9a6ac1-13ea-4060-9ef9-60a3309bd921 InstallationDate: Installed on 2013-11-11 (23 days ago) InstallationMedia: This MachineType: LENOVO 20217 MarkForUpload: True ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=aec56d0c-f753-4e40-948a-34e69d7dfca6 ro "acpi_osi=!Windows 2012" RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN41WW(V2.07) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 3194STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN41WW(V2.07):bd08/22/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr3194STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258058/+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 1259634] Re: Atheros AR8161 Gigabit Ethernet very slow with 3.11.0-14-generic
Hi Joseph, I have installed version 3.11.0-15 of the packages linux-headers, linux- image and linux-image-extra and tested the connection speed with the same poor result. Alexander -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1259634 Title: Atheros AR8161 Gigabit Ethernet very slow with 3.11.0-14-generic Status in “linux” package in Ubuntu: Confirmed Bug description: When I boot my machine with the 3.11.0-14 kernel configuration my Atheros ethernet card (AR8161) is very slow. I talk about less than 1/3 of the speed when I boot de machine with the 3.11.0-13 kernel configuration. Both are the default kernels form kubuntu. Ubuntu 3.11.0-13.20-generic 3.11.6 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-extra-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ae 6943 F pulseaudio Date: Tue Dec 10 18:31:51 2013 HibernationDevice: RESUME=UUID=a8289c13-425d-464f-b8cb-7ab63ffa3ea9 InstallationDate: Installed on 2013-08-02 (130 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=/dev/mapper/hostname-root ro persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-17 (54 days ago) dmi.bios.date: 10/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F16 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF16:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259634/+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 1259861] Re: 5-10 second delay in kernel boot
I just tested with linux- image-3.13.0-031300rc3-generic_3.13.0-031300rc3.201312061335_i386.deb, it doesn't happen there. I don't think I should put the 'kernel-fixed-upstream' tag as the problem might be in some Ubuntu-specific kernel patch or configuration option that's been around for a couple of years. Do you want me to test with the vanilla 3.12 too? The delay probably won't exist there either... ** 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/1259861 Title: 5-10 second delay in kernel boot Status in “linux” package in Ubuntu: Confirmed Bug description: In Trusty I see a big delay while the kernel boots that I did not see back in Precise. Some people have been experiencing this in Saucy too, so I don't know exactly when it started happening. Excerpt from dmesg: [3.740100] Switched to clocksource tsc [ 14.208118] PM: Hibernation image not present or could not be loaded. [ 14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000) The exact messages above don't matter, they are different on different boots or on different machines. It even happens with e.g. $ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso My current kernel is Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 i686 i686 GNU/Linux ...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run `dmesg` yourself and check if there's a big delay there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259861/+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 1258960] Re: No sound after suspending Ubuntu 13.04 and no mouse after restarting from Ubuntu to Windows 8
The first problem was fixed with the kernel 3.13., but the second problem is not fixed. Where I add the tag, it's the first time I report a bug so I don't know how to do that. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1258960 Title: No sound after suspending Ubuntu 13.04 and no mouse after restarting from Ubuntu to Windows 8 Status in “linux” package in Ubuntu: Incomplete Bug description: When I suspend Ubuntu, in resume I don't have sound. The solution that work for me is to force shut down (by pressing the power on button for 5 seconds). Restarting or shutting down the computer normally doesn't help. I've got similar problem when I restart from Linux to Windows, I don't have mouse. The solution to get back the mouse is also to force shut down. I thought that problem is Windows 8 but now I'm sure that is Ubuntu. I don't care about the second problem as now I don't use Windows 8. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-34-generic 3.8.0-34.49 ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: meradi 1949 F pulseaudio /dev/snd/pcmC0D0p: meradi 1949 F...m pulseaudio Date: Sun Dec 8 20:13:12 2013 HibernationDevice: RESUME=UUID=e71568e2-e875-4053-b3b7-2046540e78bf InstallationDate: Installed on 2013-11-03 (35 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Hewlett-Packard HP Compaq 6830s MarkForUpload: True ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-generic root=UUID=61e20a6d-19a5-4042-b9b8-b2dba6593f97 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-34-generic N/A linux-backports-modules-3.8.0-34-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZD Ver. F.0C dmi.board.name: 30E9 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 95.1C dmi.chassis.asset.tag: CNU91609Y2 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZDVer.F.0C:bd03/12/2009:svnHewlett-Packard:pnHPCompaq6830s:pvrF.0C:rvnHewlett-Packard:rn30E9:rvrKBCVersion95.1C:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 6830s dmi.product.version: F.0C dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258960/+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 1258058] Re: Brightness control no effect on screen
i was not able to install nvidia drivers using this kernel 3.13.0-031300rc3 therefore with this kernel i was not able to test ** Tags added: kernel-bug-exists-upstream kernel-unable-to-test-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/1258058 Title: Brightness control no effect on screen Status in “linux” package in Ubuntu: Confirmed Bug description: Brightness control no effect on screen, I managed to get control over brightness by using xbacklight. My issue (laptop and everything else) is exactly the same as this one http://ubuntuforums.org/showthread.php?t=2167180 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: radenkovich 2284 F pulseaudio /dev/snd/controlC0: radenkovich 2284 F pulseaudio Date: Thu Dec 5 09:45:30 2013 HibernationDevice: RESUME=UUID=ea9a6ac1-13ea-4060-9ef9-60a3309bd921 InstallationDate: Installed on 2013-11-11 (23 days ago) InstallationMedia: This MachineType: LENOVO 20217 MarkForUpload: True ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=aec56d0c-f753-4e40-948a-34e69d7dfca6 ro "acpi_osi=!Windows 2012" RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN41WW(V2.07) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 3194STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN41WW(V2.07):bd08/22/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr3194STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258058/+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 1258058] Re: Brightness control no effect on screen
Marking Confirmed: linux-kernel-3.12.0-031200_3.12.0-031200.201311031935 kernel-bug-exists-upstream kernel 3.13.0-031300rc3 kernel-unable-to-test-upstream ** 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/1258058 Title: Brightness control no effect on screen Status in “linux” package in Ubuntu: Confirmed Bug description: Brightness control no effect on screen, I managed to get control over brightness by using xbacklight. My issue (laptop and everything else) is exactly the same as this one http://ubuntuforums.org/showthread.php?t=2167180 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: radenkovich 2284 F pulseaudio /dev/snd/controlC0: radenkovich 2284 F pulseaudio Date: Thu Dec 5 09:45:30 2013 HibernationDevice: RESUME=UUID=ea9a6ac1-13ea-4060-9ef9-60a3309bd921 InstallationDate: Installed on 2013-11-11 (23 days ago) InstallationMedia: This MachineType: LENOVO 20217 MarkForUpload: True ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=aec56d0c-f753-4e40-948a-34e69d7dfca6 ro "acpi_osi=!Windows 2012" RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN41WW(V2.07) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 3194STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN41WW(V2.07):bd08/22/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr3194STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258058/+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 785394] Re: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient
Yeah looks like the minimum amount of ram required to complete the
writing of a dump in the case of a generic-image and default initrd is
roughly 109-110M with the 3.8 kernel (I just tested it).
My $.02 on this matter is that the default values should work for
default installs. Right now that is not the case even if they have
enough ram to complete a dump.
My guess is that 64M works for virtual images just fine, but it's not
enough for generic images. So perhaps we should make this value
dependent on virtual or generic being in the kernel name.
So how about something like the below patch. I haven't fully vetted it,
but want to see what people think.
--- 10_linux.orig 2013-12-11 14:33:00.384344265 -0600
+++ 10_linux2013-12-11 15:13:42.485036921 -0600
@@ -73,7 +73,7 @@ done
# add crashkernel option if we have the required tools
if [ -x "/usr/bin/makedumpfile" ] && [ -x "/sbin/kexec" ]; then
-GRUB_CMDLINE_EXTRA="$GRUB_CMDLINE_EXTRA crashkernel=384M-2G:92M,2G-:128M"
+CRASH="on"
fi
linux_entry ()
@@ -120,6 +120,14 @@ EOF
echo'$message'
EOF
fi
+ if [ "x${CRASH}" = "xon" ]; then
+if [ "x${basename%%generic}" != "x${basename}" ]; then
+ args="$args crashkernel=384M-2G:110M,2G-:128M"
+elif [ "${basename%%virtual}" != ${basename} ]; then
+args="$args crashkernel=384M-2G:64M,2G-:128M"
+fi
+ fi
+
if test -d /sys/firmware/efi && test -e "${linux}.efi.signed"; then
cat << EOF
linux ${rel_dirname}/${basename}.efi.signed
root=${linux_root_device_thisversion} ro ${args}
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/785394
Title:
Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux
is insufficient
Status in “grub2” package in Ubuntu:
Confirmed
Status in “kexec-tools” package in Ubuntu:
In Progress
Bug description:
Binary package hint: grub-pc
This concerns grub-pc 1.99~rc1-13ubuntu3 in Ubuntu Natty.
The /etc/grub.d/10_linux file contains this snippet:
# add crashkernel option if we have the required tools
if [ -x "/usr/bin/makedumpfile" ] && [ -x "/sbin/kexec" ]; then
GRUB_CMDLINE_EXTRA="$GRUB_CMDLINE_EXTRA
crashkernel=384M-2G:64M,2G-:128M"
fi
I am on a system with 2GB of RAM (reported as 2038MB), and according
to the kernel startup messages, 64MB is reserved for the crash kernel.
Unfortunately, this does not appear to be enough memory for the
regular Ubuntu kernel to boot. I am attaching a kernel log obtained
via serial cable; it shows the initial boot, a crash in the kernel's
video-driver-related code, the subsequent crashkernel boot, and then
an apparent "out of memory" kernel panic. (A side effect of the
"double crash" is that the system is left unresponsive, requiring a
manual reset instead of rebooting itself automatically.)
If I double the memory numbers in the crashkernel=... argument, so
that the reservation is 128MB, the system correctly goes on to attempt
a vmcore dump and reboot.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/785394/+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 1161863] Re: no sound macbook air 2.1
Finally resolved in kernel 3.13, look here: https://bugzilla.kernel.org/show_bug.cgi?id=65681 ** Bug watch added: Linux Kernel Bug Tracker #65681 http://bugzilla.kernel.org/show_bug.cgi?id=65681 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1161863 Title: no sound macbook air 2.1 Status in “linux” package in Ubuntu: Expired Bug description: Hello, I have no sound on my macbook air 2.1, thanks for your help. # lspci 00:08.0 Audio device: NVIDIA Corporation MCP79 High Definition Audio (rev b1) # lshw -C sound *-multimedia NON-RÉCLAMÉ description: Audio device produit: MCP79 High Definition Audio fabriquant: NVIDIA Corporation identifiant matériel: 8 information bus: pci@:00:08.0 version: b1 bits: 32 bits horloge: 66MHz fonctionnalités: pm cap_list configuration: latency=0 maxlatency=5 mingnt=2 ressources: mémoire:9338-93383fff # dmesg [ 1786.009932] hda_intel: Disabling MSI [ 1786.009970] snd_hda_intel :00:08.0: setting latency timer to 64 [ 1786.042057] hda-intel :00:08.0: no codecs found! ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-15-generic 3.8.0-15.25 ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4 Uname: Linux 3.8.0-15-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Mar 29 13:55:27 2013 HibernationDevice: RESUME=UUID=726edf9a-821f-46eb-80e7-9ee1dd2d6f5e InstallationDate: Installed on 2013-02-26 (31 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130214) MachineType: Apple Inc. MacBookAir2,1 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-15-generic root=UUID=883b18c5-21fd-44b1-af9d-49fb2fdd33d4 ro acpi=off noapic nouveau.modeset=0 rdblacklist=nouveau RelatedPackageVersions: linux-restricted-modules-3.8.0-15-generic N/A linux-backports-modules-3.8.0-15-generic N/A linux-firmware1.104 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA21.88Z.0075.B03.0811141325 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F42D88C8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F42D88C8 dmi.modalias: dmi:bvnAppleInc.:bvrMBA21.88Z.0075.B03.0811141325:bd11/14/08:svnAppleInc.:pnMacBookAir2,1:pvr1.0:rvnAppleInc.:rnMac-F42D88C8:rvr:cvnAppleInc.:ct10:cvrMac-F42D88C8: dmi.product.name: MacBookAir2,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/1161863/+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 1207812] Re: [Sony VGN-SR29XN_S] Iphone with iOS 7 does not work on Ubuntu
I think the trust prompt issue may have been fixed with a newer release of iOS 7. I no longer see it on 7.0.4 either. However I still can't access my iPhone 5S, I get the following error box instead: " Unable to mount (iPhone name) Unhandled Lockdown error (-3) " -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1207812 Title: [Sony VGN-SR29XN_S] Iphone with iOS 7 does not work on Ubuntu Status in “linux” package in Ubuntu: Incomplete Bug description: When plugging in an iPhone with iOS 7 - Currently BETA 4 I receive the following message on Ubuntu 13.04 : The Device "Nick's iPhone" is locked. Enter the passcode on the device and click "Try again". The iPhone reporting "Trust the currently connected computer?" Trust/Don't Trust. This then happens in a continous loop when clicking Trust. --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nrawlins 2068 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=f089ceb3-a892-4f99-92d3-a61c99bb2feb InstallationDate: Installed on 2013-08-15 (3 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Sony Corporation VGN-SR29XN_S MarkForUpload: True Package: linux 3.8.0.27.45 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=7656e9f3-5437-4e10-a467-62d52144f471 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1130Y1 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1130Y1:bd08/28/2009:svnSonyCorporation:pnVGN-SR29XN_S:pvrC6017UKK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-SR29XN_S dmi.product.version: C6017UKK dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1207812/+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 1207812] Re: [Sony VGN-SR29XN_S] Iphone with iOS 7 does not work on Ubuntu
Looking at LP #1215098 and the libimobiledevice website it appears there is likely some bugs still in 1.1.5 that are affecting some systems. Some users on that bug thread can use iPhone 5S just fine but it doesn't work on mine. The libimobiledevice page seems to indicate the old 1.1.5 release should work for the 5S but there have been a lot of fixes since that old release that haven't been rolled out yet as a 1.1.6 release. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1207812 Title: [Sony VGN-SR29XN_S] Iphone with iOS 7 does not work on Ubuntu Status in “linux” package in Ubuntu: Incomplete Bug description: When plugging in an iPhone with iOS 7 - Currently BETA 4 I receive the following message on Ubuntu 13.04 : The Device "Nick's iPhone" is locked. Enter the passcode on the device and click "Try again". The iPhone reporting "Trust the currently connected computer?" Trust/Don't Trust. This then happens in a continous loop when clicking Trust. --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nrawlins 2068 F pulseaudio DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=f089ceb3-a892-4f99-92d3-a61c99bb2feb InstallationDate: Installed on 2013-08-15 (3 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Sony Corporation VGN-SR29XN_S MarkForUpload: True Package: linux 3.8.0.27.45 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=7656e9f3-5437-4e10-a467-62d52144f471 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 RelatedPackageVersions: linux-restricted-modules-3.8.0-27-generic N/A linux-backports-modules-3.8.0-27-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1130Y1 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1130Y1:bd08/28/2009:svnSonyCorporation:pnVGN-SR29XN_S:pvrC6017UKK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-SR29XN_S dmi.product.version: C6017UKK dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1207812/+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 1070958] Re: Touchpad not working but USB mouse working
Michael Henson, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report: apport-collect -p linux Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. For example: kernel-fixed-upstream-v3.13-rc3 This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag: needs-upstream-testing If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER As well, please remove the tag: needs-upstream-testing Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Changed in: linux (Ubuntu) Status: 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/1070958 Title: Touchpad not working but USB mouse working Status in “linux” package in Ubuntu: Incomplete Bug description: I have just installed Ubuntu 12.10 64-bit on my laptop (Novatech nFinity N1403 [NNB-979] ultrabook with 8gb RAM) but the cursor will not move and is just stuck in the middle of the screen. This was the same during the installation but I just used the keyboard and hoped that after installation the cursor would move but to no avail. An external USB mouse does work. WORKAROUND: Kernel parameter: i8042.noloop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1070958/+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 1244643] Re: [Novatech N1402 NNB-978] Touchpad does not work at all
Geoff Kelsall, thank you for checking in with Novatech. Could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. For example: kernel-fixed-upstream-v3.13-rc3 This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag: needs-upstream-testing If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER As well, please remove the tag: needs-upstream-testing Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Changed in: linux (Ubuntu) Importance: Medium => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1244643 Title: [Novatech N1402 NNB-978] Touchpad does not work at all Status in “linux” package in Ubuntu: Incomplete Bug description: WORKAROUND: Kernel parameter: i8042.noloop When producing this bug report I got: ubuntu@ubuntu:~$ ubuntu-bug linux ubuntu@ubuntu:~$ (process:4162): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2918 F pulseaudio CasperVersion: 1.336ubuntu1 Date: Fri Oct 25 12:32:01 2013 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20131021.1) MachineType: To be filled by O.E.M. To be filled by O.E.M. MarkForUpload: True ProcFB: 0 inteldrmfb 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-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: ChiefRiver dmi.board.vendor: INTEL Corporation 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.:bvr4.6.5:bd06/11/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnChiefRiver: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/1244643/+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 1244176] Re: Server 13.10 Install Fails with USB Keyboard (Appears to Hang)
** Branch linked: lp:ubuntu/precise-proposed/linux-lts-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/1244176 Title: Server 13.10 Install Fails with USB Keyboard (Appears to Hang) Status in “initramfs-tools” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Fix Released Status in “initramfs-tools” source package in Saucy: Invalid Status in “linux” source package in Saucy: In Progress Status in “initramfs-tools” source package in Trusty: Invalid Status in “linux” source package in Trusty: Fix Released Bug description: A fresh install of Server 13.10 on old hardware fails when a USB keyboard is present. The installation succeeds when a PS/2 keyboard is installed. The installation appears to hang at the third screen, which is "Select Language". The screen does not respond to keyboard or mouse events. The issue was experienced independently on HP/Compag dc5850 with Athlon X2 2.3 GHz dual core, 4GB RAM; and DELL Optiplex 755. See "Server 13.10 Install Hangs", http://askubuntu.com/questions/364945/server-13-10-install- hangs/364949. The issue was not present on Server 12.04.3 LTS or 13.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1244176/+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 1260112] [NEW] CPU stuck on minimum frequency after resume from suspend and unplugged
Public bug reported: This happens on a Dell Latitude E6540 (4th gen core i7 CPU). Steps to reproduce: 1) normally boot the computer and make sure everything works as expected (i use the ondemand governor) 2) suspend 3) make the computer is unplugged and resume Expected behavior: cpu should work normally Actual behavior: cpu always stays at minimum frequency (in my case 800 MHz) If i resume from suspend while plugged to the AC charger, everything works as expected. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1260112 Title: CPU stuck on minimum frequency after resume from suspend and unplugged Status in “linux” package in Ubuntu: New Bug description: This happens on a Dell Latitude E6540 (4th gen core i7 CPU). Steps to reproduce: 1) normally boot the computer and make sure everything works as expected (i use the ondemand governor) 2) suspend 3) make the computer is unplugged and resume Expected behavior: cpu should work normally Actual behavior: cpu always stays at minimum frequency (in my case 800 MHz) If i resume from suspend while plugged to the AC charger, everything works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1260112/+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
