[Kernel-packages] [Bug 2034607] Re: Bus error after reading or writing a specific number of unique locations from/to a shared memory pool.
Please see the post I just made here:
https://stackoverflow.com/questions/77090823/linux-kernel-overcommit-
support-isnt-working-properly-cannot-access-all-memory
If this is a bug, it's in the linux-kernel, not just Ubuntu as RHEL and
Fedora have the same behavior.
Feel free to close this.
Thamks,
Gene
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2034607
Title:
Bus error after reading or writing a specific number of unique
locations from/to a shared memory pool.
Status in linux package in Ubuntu:
Confirmed
Bug description:
A Bus error always occurs after reading or writing a specific number
of unique locations from/to a shared memory pool which is created
using shm_open() and mmap(). It does not matter if the pool memory
locations are accessed starting at the base of the pool, incrementing
up through the addresses, or starting at the top of the pool,
decrementing down through the addresses. The count of unique locations
accessed before the Bus error occurs is the same repeatable value. The
count value is close to but not exactly 1/2 of the total system
memory.
The count is of unique locations accessed. If an address range less
than the failure count is accessed repeatedly, the Bus error does not
occur.
The unique addresses do not have to be accessed sequentially to cause
the Bus error. While this aspect has not been tested exhaustively, if
a range of addresses are jumped over, the Bus error still occurs. Note
that the failure count is slightly different than if the addresses are
accessed sequentially.
This error is consistently repeatable on the following 3 systems:
Ubuntu 22.04.3 LTS
gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
Machine: Amazon EC2
CPU: AMD EPYC 7571
Memory: 124.68 GiB
Distro: Linux Mint 20 base: Ubuntu 20.04
gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04)
Machine: Dell System XPS L502X
CPU: Intel Core i7-2620M
Total Memory: 8,219,435,008 bytes
Distro: Linux Mint 21 base: Ubuntu 22.04
gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
Machine: Dell Inspiron 5558
CPU: Intel Core i3-5005U
Total Memory: 8,229,298,176 bytes
C++ Test program that demonstrates the issue.
-
// September 2023 - Gene Weber
// This test program generates a Bus error core dump after reading or writing
a specific number
// of unique locations from/to a shared memory pool. It does not matter if
the pool memory locations
// are accessed starting at the base of the pool, incrementing up through the
addresses, or starting
// at the top of the pool, decrementing down through the addresses. The count
of unique locations
// accessed before the Bus error occurs is the same repeatable value. The
count value is close to
// but not exactly 1/2 of the total system memory.
//
// The count is of unique locations accessed. If an address range less than
the failure count is
// accessed repeatedly, the Bus error does not occur.
//
// The unique addresses do not have to be accessed sequentially to cause the
Bus error. While this
// has not been tested exhaustively, if a range of addresses are jumped over,
the Bus error still
// occurs. Note that the failure count is slightly different than if the
addresses are accessed
// sequentially.
//
// This test program has command line options to allow testing these
different scenarios.
// Compiling with either has the same results:
// g++ -std=c++11 test.cpp -W -Wall -Wextra -pedantic -pthread -o test -lrt
// g++ -std=c++20 -O3 test.cpp -W -Wall -Wextra -pedantic -pthread -o test
-lrt
#include
#include
#include
#include
#include
#include
#include
int main(int argc, char** argv) {
int page_size = 4096;
if (argc != 5) {
std::cerr << "\nUsage: ./test
\n\n";
std::cerr << "= total from \"free
-b\".\n";
std::cerr << "= u to index addresses up from bottom of
pool, d for down from top.\n";
std::cerr << "= r to read indexed address, w for
write.\n";
std::cerr << "= j for jump index by 5% of total, r for
limit index range to 1/2 of total, x linear indexing.\n\n";
exit(EXIT_FAILURE);
}
uint_fast64_t total_system_ram = strtoull(argv[1], NULL, 10);
// Set pool_size to a whole number of pages that is ~60% of system memory.
uint_fast64_t pool_size = total_system_ram * 0.6;
pool_size = pool_size - (pool_size % page_size);
std::cout << "pool size = " << pool_size << "\n";
// Create a mask to print status at intervals of ~1/20 of the pool size.
uint_fast64_t print_interval = pow(2,ceil(log
[Kernel-packages] [Bug 2034607] Re: Bus error after reading or writing a specific number of unique locations from/to a shared memory pool.
Even though this was tried with two different gcc versions, I just
installed clang version 17.0.0 and compiled the test program. The Bus
Error issue is the same with the clang compiled program.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2034607
Title:
Bus error after reading or writing a specific number of unique
locations from/to a shared memory pool.
Status in linux package in Ubuntu:
Confirmed
Bug description:
A Bus error always occurs after reading or writing a specific number
of unique locations from/to a shared memory pool which is created
using shm_open() and mmap(). It does not matter if the pool memory
locations are accessed starting at the base of the pool, incrementing
up through the addresses, or starting at the top of the pool,
decrementing down through the addresses. The count of unique locations
accessed before the Bus error occurs is the same repeatable value. The
count value is close to but not exactly 1/2 of the total system
memory.
The count is of unique locations accessed. If an address range less
than the failure count is accessed repeatedly, the Bus error does not
occur.
The unique addresses do not have to be accessed sequentially to cause
the Bus error. While this aspect has not been tested exhaustively, if
a range of addresses are jumped over, the Bus error still occurs. Note
that the failure count is slightly different than if the addresses are
accessed sequentially.
This error is consistently repeatable on the following 3 systems:
Ubuntu 22.04.3 LTS
gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
Machine: Amazon EC2
CPU: AMD EPYC 7571
Memory: 124.68 GiB
Distro: Linux Mint 20 base: Ubuntu 20.04
gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04)
Machine: Dell System XPS L502X
CPU: Intel Core i7-2620M
Total Memory: 8,219,435,008 bytes
Distro: Linux Mint 21 base: Ubuntu 22.04
gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
Machine: Dell Inspiron 5558
CPU: Intel Core i3-5005U
Total Memory: 8,229,298,176 bytes
C++ Test program that demonstrates the issue.
-
// September 2023 - Gene Weber
// This test program generates a Bus error core dump after reading or writing
a specific number
// of unique locations from/to a shared memory pool. It does not matter if
the pool memory locations
// are accessed starting at the base of the pool, incrementing up through the
addresses, or starting
// at the top of the pool, decrementing down through the addresses. The count
of unique locations
// accessed before the Bus error occurs is the same repeatable value. The
count value is close to
// but not exactly 1/2 of the total system memory.
//
// The count is of unique locations accessed. If an address range less than
the failure count is
// accessed repeatedly, the Bus error does not occur.
//
// The unique addresses do not have to be accessed sequentially to cause the
Bus error. While this
// has not been tested exhaustively, if a range of addresses are jumped over,
the Bus error still
// occurs. Note that the failure count is slightly different than if the
addresses are accessed
// sequentially.
//
// This test program has command line options to allow testing these
different scenarios.
// Compiling with either has the same results:
// g++ -std=c++11 test.cpp -W -Wall -Wextra -pedantic -pthread -o test -lrt
// g++ -std=c++20 -O3 test.cpp -W -Wall -Wextra -pedantic -pthread -o test
-lrt
#include
#include
#include
#include
#include
#include
#include
int main(int argc, char** argv) {
int page_size = 4096;
if (argc != 5) {
std::cerr << "\nUsage: ./test
\n\n";
std::cerr << "= total from \"free
-b\".\n";
std::cerr << "= u to index addresses up from bottom of
pool, d for down from top.\n";
std::cerr << "= r to read indexed address, w for
write.\n";
std::cerr << "= j for jump index by 5% of total, r for
limit index range to 1/2 of total, x linear indexing.\n\n";
exit(EXIT_FAILURE);
}
uint_fast64_t total_system_ram = strtoull(argv[1], NULL, 10);
// Set pool_size to a whole number of pages that is ~60% of system memory.
uint_fast64_t pool_size = total_system_ram * 0.6;
pool_size = pool_size - (pool_size % page_size);
std::cout << "pool size = " << pool_size << "\n";
// Create a mask to print status at intervals of ~1/20 of the pool size.
uint_fast64_t print_interval = pow(2,ceil(log2(pool_size/20))) - 1;
// Create a value to start printing all addresses after a few pages less
[Kernel-packages] [Bug 2034607] Re: Bus error after reading or writing a specific number of unique locations from/to a shared memory pool.
I am unable to run the apport-collect command.
** 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/2034607
Title:
Bus error after reading or writing a specific number of unique
locations from/to a shared memory pool.
Status in linux package in Ubuntu:
Confirmed
Bug description:
A Bus error always occurs after reading or writing a specific number
of unique locations from/to a shared memory pool which is created
using shm_open() and mmap(). It does not matter if the pool memory
locations are accessed starting at the base of the pool, incrementing
up through the addresses, or starting at the top of the pool,
decrementing down through the addresses. The count of unique locations
accessed before the Bus error occurs is the same repeatable value. The
count value is close to but not exactly 1/2 of the total system
memory.
The count is of unique locations accessed. If an address range less
than the failure count is accessed repeatedly, the Bus error does not
occur.
The unique addresses do not have to be accessed sequentially to cause
the Bus error. While this aspect has not been tested exhaustively, if
a range of addresses are jumped over, the Bus error still occurs. Note
that the failure count is slightly different than if the addresses are
accessed sequentially.
This error is consistently repeatable on the following 3 systems:
Ubuntu 22.04.3 LTS
gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
Machine: Amazon EC2
CPU: AMD EPYC 7571
Memory: 124.68 GiB
Distro: Linux Mint 20 base: Ubuntu 20.04
gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04)
Machine: Dell System XPS L502X
CPU: Intel Core i7-2620M
Total Memory: 8,219,435,008 bytes
Distro: Linux Mint 21 base: Ubuntu 22.04
gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
Machine: Dell Inspiron 5558
CPU: Intel Core i3-5005U
Total Memory: 8,229,298,176 bytes
C++ Test program that demonstrates the issue.
-
// September 2023 - Gene Weber
// This test program generates a Bus error core dump after reading or writing
a specific number
// of unique locations from/to a shared memory pool. It does not matter if
the pool memory locations
// are accessed starting at the base of the pool, incrementing up through the
addresses, or starting
// at the top of the pool, decrementing down through the addresses. The count
of unique locations
// accessed before the Bus error occurs is the same repeatable value. The
count value is close to
// but not exactly 1/2 of the total system memory.
//
// The count is of unique locations accessed. If an address range less than
the failure count is
// accessed repeatedly, the Bus error does not occur.
//
// The unique addresses do not have to be accessed sequentially to cause the
Bus error. While this
// has not been tested exhaustively, if a range of addresses are jumped over,
the Bus error still
// occurs. Note that the failure count is slightly different than if the
addresses are accessed
// sequentially.
//
// This test program has command line options to allow testing these
different scenarios.
// Compiling with either has the same results:
// g++ -std=c++11 test.cpp -W -Wall -Wextra -pedantic -pthread -o test -lrt
// g++ -std=c++20 -O3 test.cpp -W -Wall -Wextra -pedantic -pthread -o test
-lrt
#include
#include
#include
#include
#include
#include
#include
int main(int argc, char** argv) {
int page_size = 4096;
if (argc != 5) {
std::cerr << "\nUsage: ./test
\n\n";
std::cerr << "= total from \"free
-b\".\n";
std::cerr << "= u to index addresses up from bottom of
pool, d for down from top.\n";
std::cerr << "= r to read indexed address, w for
write.\n";
std::cerr << "= j for jump index by 5% of total, r for
limit index range to 1/2 of total, x linear indexing.\n\n";
exit(EXIT_FAILURE);
}
uint_fast64_t total_system_ram = strtoull(argv[1], NULL, 10);
// Set pool_size to a whole number of pages that is ~60% of system memory.
uint_fast64_t pool_size = total_system_ram * 0.6;
pool_size = pool_size - (pool_size % page_size);
std::cout << "pool size = " << pool_size << "\n";
// Create a mask to print status at intervals of ~1/20 of the pool size.
uint_fast64_t print_interval = pow(2,ceil(log2(pool_size/20))) - 1;
// Create a value to start printing all addresses after a few pages less
than
// 1/2 of the pool size has been accessed.
uint_fast64_t almost_
[Kernel-packages] [Bug 2034607] [NEW] Bus error after reading or writing a specific number of unique locations from/to a shared memory pool.
Public bug reported:
A Bus error always occurs after reading or writing a specific number of
unique locations from/to a shared memory pool which is created using
shm_open() and mmap(). It does not matter if the pool memory locations
are accessed starting at the base of the pool, incrementing up through
the addresses, or starting at the top of the pool, decrementing down
through the addresses. The count of unique locations accessed before the
Bus error occurs is the same repeatable value. The count value is close
to but not exactly 1/2 of the total system memory.
The count is of unique locations accessed. If an address range less than
the failure count is accessed repeatedly, the Bus error does not occur.
The unique addresses do not have to be accessed sequentially to cause
the Bus error. While this aspect has not been tested exhaustively, if a
range of addresses are jumped over, the Bus error still occurs. Note
that the failure count is slightly different than if the addresses are
accessed sequentially.
This error is consistently repeatable on the following 3 systems:
Ubuntu 22.04.3 LTS
gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
Machine: Amazon EC2
CPU: AMD EPYC 7571
Memory: 124.68 GiB
Distro: Linux Mint 20 base: Ubuntu 20.04
gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04)
Machine: Dell System XPS L502X
CPU: Intel Core i7-2620M
Total Memory: 8,219,435,008 bytes
Distro: Linux Mint 21 base: Ubuntu 22.04
gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
Machine: Dell Inspiron 5558
CPU: Intel Core i3-5005U
Total Memory: 8,229,298,176 bytes
C++ Test program that demonstrates the issue.
-
// September 2023 - Gene Weber
// This test program generates a Bus error core dump after reading or writing a
specific number
// of unique locations from/to a shared memory pool. It does not matter if the
pool memory locations
// are accessed starting at the base of the pool, incrementing up through the
addresses, or starting
// at the top of the pool, decrementing down through the addresses. The count
of unique locations
// accessed before the Bus error occurs is the same repeatable value. The count
value is close to
// but not exactly 1/2 of the total system memory.
//
// The count is of unique locations accessed. If an address range less than the
failure count is
// accessed repeatedly, the Bus error does not occur.
//
// The unique addresses do not have to be accessed sequentially to cause the
Bus error. While this
// has not been tested exhaustively, if a range of addresses are jumped over,
the Bus error still
// occurs. Note that the failure count is slightly different than if the
addresses are accessed
// sequentially.
//
// This test program has command line options to allow testing these different
scenarios.
// Compiling with either has the same results:
// g++ -std=c++11 test.cpp -W -Wall -Wextra -pedantic -pthread -o test -lrt
// g++ -std=c++20 -O3 test.cpp -W -Wall -Wextra -pedantic -pthread -o test -lrt
#include
#include
#include
#include
#include
#include
#include
int main(int argc, char** argv) {
int page_size = 4096;
if (argc != 5) {
std::cerr << "\nUsage: ./test
\n\n";
std::cerr << "= total from \"free
-b\".\n";
std::cerr << "= u to index addresses up from bottom of
pool, d for down from top.\n";
std::cerr << "= r to read indexed address, w for write.\n";
std::cerr << "= j for jump index by 5% of total, r for
limit index range to 1/2 of total, x linear indexing.\n\n";
exit(EXIT_FAILURE);
}
uint_fast64_t total_system_ram = strtoull(argv[1], NULL, 10);
// Set pool_size to a whole number of pages that is ~60% of system memory.
uint_fast64_t pool_size = total_system_ram * 0.6;
pool_size = pool_size - (pool_size % page_size);
std::cout << "pool size = " << pool_size << "\n";
// Create a mask to print status at intervals of ~1/20 of the pool size.
uint_fast64_t print_interval = pow(2,ceil(log2(pool_size/20))) - 1;
// Create a value to start printing all addresses after a few pages less
than
// 1/2 of the pool size has been accessed.
uint_fast64_t almost_half = (total_system_ram/2) - (3 * page_size);
// Create a "jump address index" value to use if the jump option is
selected.
uint_fast64_t jmp_indx = total_system_ram * 0.05;
if (*argv[4] == 'j') {
std::cout << "jump address index by " << jmp_indx << "\n";
}
// Create an "address index range" value to use if range limit option is
selected.
uint_fast64_t indx_range = pool_size / 2;
if (*argv[4] == 'r') {
std::cout << "address index range will be limited to " <<
[Kernel-packages] [Bug 1971930] [NEW] Shutdown does not work, reboot takes to long
Public bug reported: The system does not shut down completely. The display goes black, but the power LED stays on (ThinkPad E460). Trying to boot the system in that state is not successful. Only way out is a hard reset. Interestingly, rebooting works (very slowly). Normal boot takes to long. BIOS is the latest available. Thanks for your service. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruben 1751 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 6 09:01:39 2022 InstallationDate: Installed on 2018-06-09 (1426 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint Reader Bus 001 Device 003: ID 04f2:b541 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20ET0049GE ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=336bc2cb-0ac4-4e48-9e8f-ee4038aa340f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-03 (2 days ago) dmi.bios.date: 01/26/2022 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R00ET68W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ET0049GE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrR00ET68W(1.43):bd01/26/2022:br1.43:efr1.43:svnLENOVO:pn20ET0049GE:pvrThinkPadE460:rvnLENOVO:rn20ET0049GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20ET_BU_Think_FM_ThinkPadE460: dmi.product.family: ThinkPad E460 dmi.product.name: 20ET0049GE dmi.product.sku: LENOVO_MT_20ET_BU_Think_FM_ThinkPad E460 dmi.product.version: ThinkPad E460 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971930 Title: Shutdown does not work, reboot takes to long Status in linux package in Ubuntu: New Bug description: The system does not shut down completely. The display goes black, but the power LED stays on (ThinkPad E460). Trying to boot the system in that state is not successful. Only way out is a hard reset. Interestingly, rebooting works (very slowly). Normal boot takes to long. BIOS is the latest available. Thanks for your service. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruben 1751 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 6 09:01:39 2022 InstallationDate: Installed on 2018-06-09 (1426 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint Reader Bus 001 Device 003: ID 04f2:b541 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20ET0049GE ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=336bc2cb-0ac4-4e48-9e8f-ee4038aa340f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-03 (2 days ago) dmi.bios.date: 01/26/2022 dmi
[Kernel-packages] [Bug 1971551] [NEW] Hibernate wake up does not work
Public bug reported: Closing the notebook results in the system going to sleep/hibernate. Since upgrading to 22.04, the system is unable to wake up. No buttons pressed register, even the power button does not work as a wake-up call. Only way out seems to be a hard reset. I am not alone with this problem, as it seems: https://unix.stackexchange.com/questions/698342/thinkpad-p50-ubuntu-22-04-cannot-wake-up-at-all-why Thank you for your service. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruben 1724 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed May 4 11:21:14 2022 InstallationDate: Installed on 2018-06-09 (1424 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint Reader Bus 001 Device 003: ID 04f2:b541 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20ET0049GE ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=336bc2cb-0ac4-4e48-9e8f-ee4038aa340f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-03 (1 days ago) dmi.bios.date: 12/18/2017 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: R00ET58W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ET0049GE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrR00ET58W(1.33):bd12/18/2017:br1.33:efr1.33:svnLENOVO:pn20ET0049GE:pvrThinkPadE460:rvnLENOVO:rn20ET0049GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20ET_BU_Think_FM_ThinkPadE460: dmi.product.family: ThinkPad E460 dmi.product.name: 20ET0049GE dmi.product.sku: LENOVO_MT_20ET_BU_Think_FM_ThinkPad E460 dmi.product.version: ThinkPad E460 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971551 Title: Hibernate wake up does not work Status in linux package in Ubuntu: New Bug description: Closing the notebook results in the system going to sleep/hibernate. Since upgrading to 22.04, the system is unable to wake up. No buttons pressed register, even the power button does not work as a wake-up call. Only way out seems to be a hard reset. I am not alone with this problem, as it seems: https://unix.stackexchange.com/questions/698342/thinkpad-p50-ubuntu-22-04-cannot-wake-up-at-all-why Thank you for your service. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruben 1724 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed May 4 11:21:14 2022 InstallationDate: Installed on 2018-06-09 (1424 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint Reader Bus 001 Device 003: ID 04f2:b541 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20ET0049GE ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=336bc2cb-0ac4-4e48-9e8f-ee4038aa340f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux
[Kernel-packages] [Bug 1959193] [NEW] symlink loop in libnvpair1linux
Public bug reported: I got this e-mail that debsums found a symlink loop and am filing a bug as instructed: /etc/cron.daily/debsums: debsums: Error: symlink loop detected in path 'usr/share/doc/libnvpair1linux/COPYRIGHT'. Please file a bug again libnvpair1linux. Additional info: ~$ apt-cache policy libnvpair1linux libnvpair1linux: Installed: 0.7.5-1ubuntu16.12 Candidate: 0.7.5-1ubuntu16.12 Version table: *** 0.7.5-1ubuntu16.12 500 500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.7.5-1ubuntu15 500 500 http://dk.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ~$ lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1959193 Title: symlink loop in libnvpair1linux Status in zfs-linux package in Ubuntu: New Bug description: I got this e-mail that debsums found a symlink loop and am filing a bug as instructed: /etc/cron.daily/debsums: debsums: Error: symlink loop detected in path 'usr/share/doc/libnvpair1linux/COPYRIGHT'. Please file a bug again libnvpair1linux. Additional info: ~$ apt-cache policy libnvpair1linux libnvpair1linux: Installed: 0.7.5-1ubuntu16.12 Candidate: 0.7.5-1ubuntu16.12 Version table: *** 0.7.5-1ubuntu16.12 500 500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.7.5-1ubuntu15 500 500 http://dk.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ~$ lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1959193/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858844] Re: [Dell XPS 15 9575] Screen brightness stopped working with linux-image-5.4.0-9-generic
Same here on a XPS 13 7390, 5.4.0-14-generic also. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858844 Title: [Dell XPS 15 9575] Screen brightness stopped working with linux- image-5.4.0-9-generic Status in linux package in Ubuntu: Confirmed Bug description: I upgraded to Focal Fossa 3 days ago and nothing broke. At the time, it was still using linux 5.3 (linux-image-5.3.0-24-generic). Today, it updated to linux 5.4 (linux-image-5.4.0-9-generic) and after rebooting, the screen brightness does not work anymore - neither from keyboard keys nor from the slider in the gnome-shell panel. It works again when rebooting into the previous linux- image-5.3.0-24-generic kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mario 1892 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 8 20:23:31 2020 InstallationDate: Installed on 2018-09-13 (481 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=26ff4c95-5f68-4121-b7d0-989fa705fcc8 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-04 (3 days ago) dmi.bios.date: 07/07/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858844/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
I didn’t need to remove GDM3, but installing LightDM (and switching to it) fixed it for me. Well, I should say it was a workaround, anyway... > On Oct 24, 2018, at 11:56 PM, ccdisle wrote: > > Uncommenting "WaylandEnable=false " worked. > > Removing gdm3 did not work, I just got redirected to a tty3 login shell. > > Thanks again > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1752053 > > Title: > nvidia-390 fails to boot graphical display > > Status in mesa package in Ubuntu: > Fix Released > Status in nvidia-graphics-drivers-390 package in Ubuntu: > Fix Released > Status in xserver-xorg-video-nouveau package in Ubuntu: > Invalid > > Bug description: > I'm using Bionic with the new 4.15 kernel. I've been using the > nvidia-384 driver with no problem for a while. Today I issued "sudo > apt-get upgrade" and I was prompted to upgrade the nvidia driver to > the nvidia-390. After installing the driver and rebooting, I was only > able to boot in to the tty terminal. The graphical display failed to > boot. I have had similar problems with nvidia driver version 390 with > Arch Linux and with Open Suse Tumbleweed. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1508510] Re: Something in the Kernel crashes when I try to mount via NFS
Why is it incomplete again? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1508510 Title: Something in the Kernel crashes when I try to mount via NFS Status in linux package in Ubuntu: Confirmed Bug description: I have a vagrant virtual machine that mounts a directory on my computer via NFS, this does not work and the reason seems to be this. My System is using SMP, reverting to the kernel before solves the problem. Broken: Linux paul-ThinkPad-T430s 3.13.0-66-generic Working: Broken: Linux paul-ThinkPad-T430s 3.13.0-65-generic BUG: unable to handle kernel NULL pointer dereference at 0008 [ 84.360198] IP: [] skb_copy_and_csum_datagram_iovec+0x2d/0x110 [ 84.360224] PGD 0 [ 84.360232] Oops: [#1] SMP [ 84.360246] Modules linked in: ctr ccm pci_stub vboxpci(OX) vboxnetadp(OX) vboxnetflt(OX) vboxdrv(OX) vmw_vsock_vmci_transport vsock vmw_vmci rfcomm bnep arc4 iwldvm mac80211 hid_generic usbhid hid snd_hda_codec_hdmi snd_hda_codec_realtek iwlwifi cfg80211 binfmt_misc nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache nls_iso8859_1 uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev cdc_mbim cdc_ncm usbnet mii cdc_wdm cdc_acm btusb bluetooth intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd joydev serio_raw snd_hda_intel snd_hda_codec snd_hwdep thinkpad_acpi nvram snd_pcm snd_seq_midi lpc_ich snd_seq_midi_event snd_rawmidi shpchp snd_page_alloc mei_me mei i915 snd_seq drm_kms_helper drm i2c_algo_bit parport_pc wmi snd_seq_device snd_timer ppdev snd soundcore lp mac_hid parport video mmc_block psmouse e1000e ahci sdhci_pci libahc i ptp sdhci pps_core [ 84.360613] CPU: 2 PID: 1507 Comm: nfsd Tainted: G OX 3.13.0-66-generic #108-Ubuntu [ 84.360643] Hardware name: LENOVO 2355CTO/2355CTO, BIOS G7ET95WW (2.55 ) 07/10/2013 [ 84.360673] task: 880036929800 ti: 880036b7a000 task.ti: 880036b7a000 [ 84.360696] RIP: 0010:[] [] skb_copy_and_csum_datagram_iovec+0x2d/0x110 [ 84.360728] RSP: 0018:880036b7bbc0 EFLAGS: 00010216 [ 84.360743] RAX: RBX: 880035910700 RCX: [ 84.360762] RDX: RSI: 0030 RDI: 88038e23ab00 [ 84.360781] RBP: 880036b7bbf8 R08: R09: 62e59d1a [ 84.360800] R10: R11: 0004 R12: 0008 [ 84.360819] R13: 88038e23ab00 R14: 0028 R15: 88038e23ab00 [ 84.360838] FS: () GS:88043e28() knlGS: [ 84.360859] CS: 0010 DS: ES: CR0: 80050033 [ 84.360874] CR2: 0008 CR3: 000425ea CR4: 001427e0 [ 84.360893] Stack: [ 84.360900] 81616f66 81616fb0 880035910700 880036b7bdf8 [ 84.360924] 0028 88038e23ab00 880036b7bc60 [ 84.360948] 8168b2ec 880426f8c028 880035910770 0002 [ 84.360972] Call Trace: [ 84.360984] [] ? skb_checksum+0x26/0x30 [ 84.361005] [] ? skb_push+0x40/0x40 [ 84.361025] [] udp_recvmsg+0x1dc/0x380 [ 84.361046] [] inet_recvmsg+0x6c/0x80 [ 84.361065] [] sock_recvmsg+0x9a/0xd0 [ 84.361087] [] ? del_timer_sync+0x4a/0x60 [ 84.361106] [] ? schedule_timeout+0x17d/0x2d0 [ 84.361126] [] kernel_recvmsg+0x3a/0x50 [ 84.361164] [] svc_udp_recvfrom+0x89/0x440 [sunrpc] [ 84.361185] [] ? _raw_spin_unlock_bh+0x1b/0x40 [ 84.361211] [] ? svc_get_next_xprt+0xd8/0x310 [sunrpc] [ 84.361237] [] svc_recv+0x4a0/0x5c0 [sunrpc] [ 84.361255] [] ? recalc_sigpending+0x1b/0x50 [ 84.361276] [] nfsd+0xad/0x130 [nfsd] [ 84.361295] [] ? nfsd_destroy+0x80/0x80 [nfsd] [ 84.361313] [] kthread+0xd2/0xf0 [ 84.361328] [] ? kthread_create_on_node+0x1c0/0x1c0 [ 84.361346] [] ret_from_fork+0x58/0x90 [ 84.361362] [] ? kthread_create_on_node+0x1c0/0x1c0 [ 84.361383] Code: 44 00 00 55 31 c0 48 89 e5 41 57 41 56 41 55 49 89 fd 41 54 41 89 f4 53 48 83 ec 10 8b 77 68 41 89 f6 45 29 e6 0f 84 89 00 00 00 <48> 8b 42 08 48 89 d3 48 85 c0 75 14 0f 1f 80 00 00 00 00 48 83 [ 84.361514] RIP [] skb_copy_and_csum_datagram_iovec+0x2d/0x110 [ 84.361546] RSP [ 84.361557] CR2: 0008 [ 84.366322] ---[ end trace f8aceef52c8aecd1 ]--- ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-66-generic 3.13.0-66.108 ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27 Uname: Linux 3.13.0-66-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0:
[Kernel-packages] [Bug 1508510] Re: Something in the Kernel crashes when I try to mount via NFS
** 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/1508510 Title: Something in the Kernel crashes when I try to mount via NFS Status in linux package in Ubuntu: Confirmed Bug description: I have a vagrant virtual machine that mounts a directory on my computer via NFS, this does not work and the reason seems to be this. My System is using SMP, reverting to the kernel before solves the problem. Broken: Linux paul-ThinkPad-T430s 3.13.0-66-generic Working: Broken: Linux paul-ThinkPad-T430s 3.13.0-65-generic BUG: unable to handle kernel NULL pointer dereference at 0008 [ 84.360198] IP: [] skb_copy_and_csum_datagram_iovec+0x2d/0x110 [ 84.360224] PGD 0 [ 84.360232] Oops: [#1] SMP [ 84.360246] Modules linked in: ctr ccm pci_stub vboxpci(OX) vboxnetadp(OX) vboxnetflt(OX) vboxdrv(OX) vmw_vsock_vmci_transport vsock vmw_vmci rfcomm bnep arc4 iwldvm mac80211 hid_generic usbhid hid snd_hda_codec_hdmi snd_hda_codec_realtek iwlwifi cfg80211 binfmt_misc nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache nls_iso8859_1 uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev cdc_mbim cdc_ncm usbnet mii cdc_wdm cdc_acm btusb bluetooth intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd joydev serio_raw snd_hda_intel snd_hda_codec snd_hwdep thinkpad_acpi nvram snd_pcm snd_seq_midi lpc_ich snd_seq_midi_event snd_rawmidi shpchp snd_page_alloc mei_me mei i915 snd_seq drm_kms_helper drm i2c_algo_bit parport_pc wmi snd_seq_device snd_timer ppdev snd soundcore lp mac_hid parport video mmc_block psmouse e1000e ahci sdhci_pci libahc i ptp sdhci pps_core [ 84.360613] CPU: 2 PID: 1507 Comm: nfsd Tainted: G OX 3.13.0-66-generic #108-Ubuntu [ 84.360643] Hardware name: LENOVO 2355CTO/2355CTO, BIOS G7ET95WW (2.55 ) 07/10/2013 [ 84.360673] task: 880036929800 ti: 880036b7a000 task.ti: 880036b7a000 [ 84.360696] RIP: 0010:[] [] skb_copy_and_csum_datagram_iovec+0x2d/0x110 [ 84.360728] RSP: 0018:880036b7bbc0 EFLAGS: 00010216 [ 84.360743] RAX: RBX: 880035910700 RCX: [ 84.360762] RDX: RSI: 0030 RDI: 88038e23ab00 [ 84.360781] RBP: 880036b7bbf8 R08: R09: 62e59d1a [ 84.360800] R10: R11: 0004 R12: 0008 [ 84.360819] R13: 88038e23ab00 R14: 0028 R15: 88038e23ab00 [ 84.360838] FS: () GS:88043e28() knlGS: [ 84.360859] CS: 0010 DS: ES: CR0: 80050033 [ 84.360874] CR2: 0008 CR3: 000425ea CR4: 001427e0 [ 84.360893] Stack: [ 84.360900] 81616f66 81616fb0 880035910700 880036b7bdf8 [ 84.360924] 0028 88038e23ab00 880036b7bc60 [ 84.360948] 8168b2ec 880426f8c028 880035910770 0002 [ 84.360972] Call Trace: [ 84.360984] [] ? skb_checksum+0x26/0x30 [ 84.361005] [] ? skb_push+0x40/0x40 [ 84.361025] [] udp_recvmsg+0x1dc/0x380 [ 84.361046] [] inet_recvmsg+0x6c/0x80 [ 84.361065] [] sock_recvmsg+0x9a/0xd0 [ 84.361087] [] ? del_timer_sync+0x4a/0x60 [ 84.361106] [] ? schedule_timeout+0x17d/0x2d0 [ 84.361126] [] kernel_recvmsg+0x3a/0x50 [ 84.361164] [] svc_udp_recvfrom+0x89/0x440 [sunrpc] [ 84.361185] [] ? _raw_spin_unlock_bh+0x1b/0x40 [ 84.361211] [] ? svc_get_next_xprt+0xd8/0x310 [sunrpc] [ 84.361237] [] svc_recv+0x4a0/0x5c0 [sunrpc] [ 84.361255] [] ? recalc_sigpending+0x1b/0x50 [ 84.361276] [] nfsd+0xad/0x130 [nfsd] [ 84.361295] [] ? nfsd_destroy+0x80/0x80 [nfsd] [ 84.361313] [] kthread+0xd2/0xf0 [ 84.361328] [] ? kthread_create_on_node+0x1c0/0x1c0 [ 84.361346] [] ret_from_fork+0x58/0x90 [ 84.361362] [] ? kthread_create_on_node+0x1c0/0x1c0 [ 84.361383] Code: 44 00 00 55 31 c0 48 89 e5 41 57 41 56 41 55 49 89 fd 41 54 41 89 f4 53 48 83 ec 10 8b 77 68 41 89 f6 45 29 e6 0f 84 89 00 00 00 <48> 8b 42 08 48 89 d3 48 85 c0 75 14 0f 1f 80 00 00 00 00 48 83 [ 84.361514] RIP [] skb_copy_and_csum_datagram_iovec+0x2d/0x110 [ 84.361546] RSP [ 84.361557] CR2: 0008 [ 84.366322] ---[ end trace f8aceef52c8aecd1 ]--- ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-66-generic 3.13.0-66.108 ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27 Uname: Linux 3.13.0-66-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.16 Architecture: amd64 AudioDevicesInUse: USERP
[Kernel-packages] [Bug 1508510] Re: Something in the Kernel crashes when I try to mount via NFS
Nope ... did not work uname -a Linux paul-ThinkPad-T430s 3.13.11-031311ckt27-generic #201509251131 SMP Fri Sep 25 15:34:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux [ 133.141688] BUG: unable to handle kernel NULL pointer dereference at 0008 [ 133.141734] IP: [] skb_copy_and_csum_datagram_iovec+0x2d/0x110 [ 133.141773] PGD 0 [ 133.141785] Oops: [#1] SMP [ 133.141804] Modules linked in: ctr ccm pci_stub vboxpci(OF) vboxnetadp(OF) vboxnetflt(OF) vboxdrv(OF) vmw_vsock_vmci_transport vsock vmw_vmci rfcomm bnep snd_hda_codec_hdmi snd_hda_codec_realtek binfmt_misc nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache nls_iso8859_1 arc4 iwldvm mac80211 hid_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul usbhid ghash_clmulni_intel aesni_intel hid cdc_mbim cdc_ncm btusb snd_hda_intel aes_x86_64 usbnet snd_hda_codec bluetooth lrw mii gf128mul uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev snd_hwdep glue_helper cdc_acm iwlwifi cdc_wdm ablk_helper thinkpad_acpi cryptd snd_pcm snd_page_alloc nvram cfg80211 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq joydev i915 serio_raw shpchp snd_seq_device mei_me wmi snd_timer mei drm_kms_helper drm snd lpc_ich soundcore parport_pc ppdev i2c_algo_bit mac_hid video lp parport mmc_block psmouse ahci e1000e sdhci_pci libahci sdhci ptp pps_core [ 133.142227] CPU: 3 PID: 1503 Comm: nfsd Tainted: GF O 3.13.11-031311ckt27-generic #201509251131 [ 133.142251] Hardware name: LENOVO 2355CTO/2355CTO, BIOS G7ET95WW (2.55 ) 07/10/2013 [ 133.142271] task: 8803f588c800 ti: 8803f4c4a000 task.ti: 8803f4c4a000 [ 133.142291] RIP: 0010:[] [] skb_copy_and_csum_datagram_iovec+0x2d/0x110 [ 133.142318] RSP: 0018:8803f4c4bbc0 EFLAGS: 00010216 [ 133.142332] RAX: RBX: 880425cf0380 RCX: [ 133.142350] RDX: RSI: 0030 RDI: 8803756e7100 [ 133.142369] RBP: 8803f4c4bbf8 R08: R09: 5fe5a01a [ 133.142388] R10: R11: 0005 R12: 0008 [ 133.142406] R13: 8803756e7100 R14: 0028 R15: 8803756e7100 [ 133.142425] FS: () GS:88043e2c() knlGS: [ 133.142445] CS: 0010 DS: ES: CR0: 80050033 [ 133.142460] CR2: 0008 CR3: 02c0e000 CR4: 001427e0 [ 133.142479] Stack: [ 133.142486] 81608836 81608880 880425cf0380 8803f4c4bdf8 [ 133.142509] 0028 8803756e7100 8803f4c4bc60 [ 133.142532] 8167c6dc 880426ff8028 880425cf03f0 0002 [ 133.142555] Call Trace: [ 133.142564] [] ? skb_checksum+0x26/0x30 [ 133.142580] [] ? skb_push+0x40/0x40 [ 133.142596] [] udp_recvmsg+0x1dc/0x380 [ 133.142612] [] inet_recvmsg+0x6c/0x80 [ 133.142628] [] sock_recvmsg+0x9a/0xd0 [ 133.142644] [] ? del_timer_sync+0x4a/0x60 [ 133.142661] [] ? schedule_timeout+0x17d/0x2d0 [ 133.142678] [] ? sched_clock_cpu+0xb5/0x100 [ 133.142695] [] kernel_recvmsg+0x3a/0x50 [ 133.142719] [] svc_udp_recvfrom+0x89/0x440 [sunrpc] [ 133.142738] [] ? _raw_spin_unlock_bh+0x1b/0x40 [ 133.142761] [] ? svc_get_next_xprt+0xd8/0x300 [sunrpc] [ 133.142785] [] svc_recv+0x4a0/0x5c0 [sunrpc] [ 133.142802] [] ? recalc_sigpending+0x1b/0x50 [ 133.142822] [] nfsd+0xad/0x130 [nfsd] [ 133.142839] [] ? nfsd_destroy+0x80/0x80 [nfsd] [ 133.142857] [] kthread+0xc9/0xe0 [ 133.142871] [] ? kthread_create_on_node+0x180/0x180 [ 133.142889] [] ret_from_fork+0x58/0x90 [ 133.142904] [] ? kthread_create_on_node+0x180/0x180 [ 133.142921] Code: 44 00 00 55 31 c0 48 89 e5 41 57 41 56 41 55 49 89 fd 41 54 41 89 f4 53 48 83 ec 10 8b 77 68 41 89 f6 45 29 e6 0f 84 89 00 00 00 <48> 8b 42 08 48 89 d3 48 85 c0 75 14 0f 1f 80 00 00 00 00 48 83 [ 133.143042] RIP [] skb_copy_and_csum_datagram_iovec+0x2d/0x110 [ 133.143063] RSP [ 133.143073] CR2: 0008 [ 133.147406] ---[ end trace 247e1a3a36cb883b ]--- ** 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/1508510 Title: Something in the Kernel crashes when I try to mount via NFS Status in linux package in Ubuntu: Incomplete Bug description: I have a vagrant virtual machine that mounts a directory on my computer via NFS, this does not work and the reason seems to be this. My System is using SMP, reverting to the kernel before solves the problem. Broken: Linux paul-ThinkPad-T430s 3.13.0-66-generic Working: Broken: Linux paul-ThinkPad-T430s 3.13.0-65-generic BUG: unable to handle kernel NULL pointer dereference at 0008 [ 84.360198] IP: [] skb_copy_and_csum_datagram_iovec+0x2d/0x110 [ 84.360224] PGD 0 [ 84.360232] Oops
[Kernel-packages] [Bug 1508510] Re: Something in the Kernel crashes when I try to mount via NFS
Will try. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1508510 Title: Something in the Kernel crashes when I try to mount via NFS Status in linux package in Ubuntu: Incomplete Bug description: I have a vagrant virtual machine that mounts a directory on my computer via NFS, this does not work and the reason seems to be this. My System is using SMP, reverting to the kernel before solves the problem. Broken: Linux paul-ThinkPad-T430s 3.13.0-66-generic Working: Broken: Linux paul-ThinkPad-T430s 3.13.0-65-generic BUG: unable to handle kernel NULL pointer dereference at 0008 [ 84.360198] IP: [] skb_copy_and_csum_datagram_iovec+0x2d/0x110 [ 84.360224] PGD 0 [ 84.360232] Oops: [#1] SMP [ 84.360246] Modules linked in: ctr ccm pci_stub vboxpci(OX) vboxnetadp(OX) vboxnetflt(OX) vboxdrv(OX) vmw_vsock_vmci_transport vsock vmw_vmci rfcomm bnep arc4 iwldvm mac80211 hid_generic usbhid hid snd_hda_codec_hdmi snd_hda_codec_realtek iwlwifi cfg80211 binfmt_misc nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache nls_iso8859_1 uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev cdc_mbim cdc_ncm usbnet mii cdc_wdm cdc_acm btusb bluetooth intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd joydev serio_raw snd_hda_intel snd_hda_codec snd_hwdep thinkpad_acpi nvram snd_pcm snd_seq_midi lpc_ich snd_seq_midi_event snd_rawmidi shpchp snd_page_alloc mei_me mei i915 snd_seq drm_kms_helper drm i2c_algo_bit parport_pc wmi snd_seq_device snd_timer ppdev snd soundcore lp mac_hid parport video mmc_block psmouse e1000e ahci sdhci_pci libahc i ptp sdhci pps_core [ 84.360613] CPU: 2 PID: 1507 Comm: nfsd Tainted: G OX 3.13.0-66-generic #108-Ubuntu [ 84.360643] Hardware name: LENOVO 2355CTO/2355CTO, BIOS G7ET95WW (2.55 ) 07/10/2013 [ 84.360673] task: 880036929800 ti: 880036b7a000 task.ti: 880036b7a000 [ 84.360696] RIP: 0010:[] [] skb_copy_and_csum_datagram_iovec+0x2d/0x110 [ 84.360728] RSP: 0018:880036b7bbc0 EFLAGS: 00010216 [ 84.360743] RAX: RBX: 880035910700 RCX: [ 84.360762] RDX: RSI: 0030 RDI: 88038e23ab00 [ 84.360781] RBP: 880036b7bbf8 R08: R09: 62e59d1a [ 84.360800] R10: R11: 0004 R12: 0008 [ 84.360819] R13: 88038e23ab00 R14: 0028 R15: 88038e23ab00 [ 84.360838] FS: () GS:88043e28() knlGS: [ 84.360859] CS: 0010 DS: ES: CR0: 80050033 [ 84.360874] CR2: 0008 CR3: 000425ea CR4: 001427e0 [ 84.360893] Stack: [ 84.360900] 81616f66 81616fb0 880035910700 880036b7bdf8 [ 84.360924] 0028 88038e23ab00 880036b7bc60 [ 84.360948] 8168b2ec 880426f8c028 880035910770 0002 [ 84.360972] Call Trace: [ 84.360984] [] ? skb_checksum+0x26/0x30 [ 84.361005] [] ? skb_push+0x40/0x40 [ 84.361025] [] udp_recvmsg+0x1dc/0x380 [ 84.361046] [] inet_recvmsg+0x6c/0x80 [ 84.361065] [] sock_recvmsg+0x9a/0xd0 [ 84.361087] [] ? del_timer_sync+0x4a/0x60 [ 84.361106] [] ? schedule_timeout+0x17d/0x2d0 [ 84.361126] [] kernel_recvmsg+0x3a/0x50 [ 84.361164] [] svc_udp_recvfrom+0x89/0x440 [sunrpc] [ 84.361185] [] ? _raw_spin_unlock_bh+0x1b/0x40 [ 84.361211] [] ? svc_get_next_xprt+0xd8/0x310 [sunrpc] [ 84.361237] [] svc_recv+0x4a0/0x5c0 [sunrpc] [ 84.361255] [] ? recalc_sigpending+0x1b/0x50 [ 84.361276] [] nfsd+0xad/0x130 [nfsd] [ 84.361295] [] ? nfsd_destroy+0x80/0x80 [nfsd] [ 84.361313] [] kthread+0xd2/0xf0 [ 84.361328] [] ? kthread_create_on_node+0x1c0/0x1c0 [ 84.361346] [] ret_from_fork+0x58/0x90 [ 84.361362] [] ? kthread_create_on_node+0x1c0/0x1c0 [ 84.361383] Code: 44 00 00 55 31 c0 48 89 e5 41 57 41 56 41 55 49 89 fd 41 54 41 89 f4 53 48 83 ec 10 8b 77 68 41 89 f6 45 29 e6 0f 84 89 00 00 00 <48> 8b 42 08 48 89 d3 48 85 c0 75 14 0f 1f 80 00 00 00 00 48 83 [ 84.361514] RIP [] skb_copy_and_csum_datagram_iovec+0x2d/0x110 [ 84.361546] RSP [ 84.361557] CR2: 0008 [ 84.366322] ---[ end trace f8aceef52c8aecd1 ]--- ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-66-generic 3.13.0-66.108 ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27 Uname: Linux 3.13.0-66-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paul 2717
[Kernel-packages] [Bug 1508510] [NEW] Something in the Kernel crashes when I try to mount via NFS
Public bug reported: I have a vagrant virtual machine that mounts a directory on my computer via NFS, this does not work and the reason seems to be this. My System is using SMP, reverting to the kernel before solves the problem. Broken: Linux paul-ThinkPad-T430s 3.13.0-66-generic Working: Broken: Linux paul-ThinkPad-T430s 3.13.0-65-generic BUG: unable to handle kernel NULL pointer dereference at 0008 [ 84.360198] IP: [] skb_copy_and_csum_datagram_iovec+0x2d/0x110 [ 84.360224] PGD 0 [ 84.360232] Oops: [#1] SMP [ 84.360246] Modules linked in: ctr ccm pci_stub vboxpci(OX) vboxnetadp(OX) vboxnetflt(OX) vboxdrv(OX) vmw_vsock_vmci_transport vsock vmw_vmci rfcomm bnep arc4 iwldvm mac80211 hid_generic usbhid hid snd_hda_codec_hdmi snd_hda_codec_realtek iwlwifi cfg80211 binfmt_misc nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache nls_iso8859_1 uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev cdc_mbim cdc_ncm usbnet mii cdc_wdm cdc_acm btusb bluetooth intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd joydev serio_raw snd_hda_intel snd_hda_codec snd_hwdep thinkpad_acpi nvram snd_pcm snd_seq_midi lpc_ich snd_seq_midi_event snd_rawmidi shpchp snd_page_alloc mei_me mei i915 snd_seq drm_kms_helper drm i2c_algo_bit parport_pc wmi snd_seq_device snd_timer ppdev snd soundcore lp mac_hid parport video mmc_block psmouse e1000e ahci sdhci_pci libahci ptp sdhci pps_core [ 84.360613] CPU: 2 PID: 1507 Comm: nfsd Tainted: G OX 3.13.0-66-generic #108-Ubuntu [ 84.360643] Hardware name: LENOVO 2355CTO/2355CTO, BIOS G7ET95WW (2.55 ) 07/10/2013 [ 84.360673] task: 880036929800 ti: 880036b7a000 task.ti: 880036b7a000 [ 84.360696] RIP: 0010:[] [] skb_copy_and_csum_datagram_iovec+0x2d/0x110 [ 84.360728] RSP: 0018:880036b7bbc0 EFLAGS: 00010216 [ 84.360743] RAX: RBX: 880035910700 RCX: [ 84.360762] RDX: RSI: 0030 RDI: 88038e23ab00 [ 84.360781] RBP: 880036b7bbf8 R08: R09: 62e59d1a [ 84.360800] R10: R11: 0004 R12: 0008 [ 84.360819] R13: 88038e23ab00 R14: 0028 R15: 88038e23ab00 [ 84.360838] FS: () GS:88043e28() knlGS: [ 84.360859] CS: 0010 DS: ES: CR0: 80050033 [ 84.360874] CR2: 0008 CR3: 000425ea CR4: 001427e0 [ 84.360893] Stack: [ 84.360900] 81616f66 81616fb0 880035910700 880036b7bdf8 [ 84.360924] 0028 88038e23ab00 880036b7bc60 [ 84.360948] 8168b2ec 880426f8c028 880035910770 0002 [ 84.360972] Call Trace: [ 84.360984] [] ? skb_checksum+0x26/0x30 [ 84.361005] [] ? skb_push+0x40/0x40 [ 84.361025] [] udp_recvmsg+0x1dc/0x380 [ 84.361046] [] inet_recvmsg+0x6c/0x80 [ 84.361065] [] sock_recvmsg+0x9a/0xd0 [ 84.361087] [] ? del_timer_sync+0x4a/0x60 [ 84.361106] [] ? schedule_timeout+0x17d/0x2d0 [ 84.361126] [] kernel_recvmsg+0x3a/0x50 [ 84.361164] [] svc_udp_recvfrom+0x89/0x440 [sunrpc] [ 84.361185] [] ? _raw_spin_unlock_bh+0x1b/0x40 [ 84.361211] [] ? svc_get_next_xprt+0xd8/0x310 [sunrpc] [ 84.361237] [] svc_recv+0x4a0/0x5c0 [sunrpc] [ 84.361255] [] ? recalc_sigpending+0x1b/0x50 [ 84.361276] [] nfsd+0xad/0x130 [nfsd] [ 84.361295] [] ? nfsd_destroy+0x80/0x80 [nfsd] [ 84.361313] [] kthread+0xd2/0xf0 [ 84.361328] [] ? kthread_create_on_node+0x1c0/0x1c0 [ 84.361346] [] ret_from_fork+0x58/0x90 [ 84.361362] [] ? kthread_create_on_node+0x1c0/0x1c0 [ 84.361383] Code: 44 00 00 55 31 c0 48 89 e5 41 57 41 56 41 55 49 89 fd 41 54 41 89 f4 53 48 83 ec 10 8b 77 68 41 89 f6 45 29 e6 0f 84 89 00 00 00 <48> 8b 42 08 48 89 d3 48 85 c0 75 14 0f 1f 80 00 00 00 00 48 83 [ 84.361514] RIP [] skb_copy_and_csum_datagram_iovec+0x2d/0x110 [ 84.361546] RSP [ 84.361557] CR2: 0008 [ 84.366322] ---[ end trace f8aceef52c8aecd1 ]--- ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-66-generic 3.13.0-66.108 ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27 Uname: Linux 3.13.0-66-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paul 2717 F pulseaudio CurrentDesktop: GNOME Date: Wed Oct 21 17:05:35 2015 HibernationDevice: RESUME=UUID=d00bf67f-487f-437c-9069-db3ff456958f InstallationDate: Installed on 2013-10-05 (745 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: LENOVO 2355CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-66-generic.efi.signed root=UUID=67ae3efa-eae6-4b17-
[Kernel-packages] [Bug 1485057] Re: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown
Installing Xubuntu 15.04 to boot in UEFI non-secure mode has some challenges of it's own. But once I got the system working, it doesn't freeze anymore. If you want to use legacy BIOS mode, you'll have to compile a kernel. However, it is not necessary to apply the patch above. Just disable the USB EHCI driver. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485057 Title: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown Status in linux package in Ubuntu: Triaged Bug description: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) Incidentally, the shutdown sequence also freezes with the kernels that exhibit the problem; but I cannot be sure that the cause is the same. I decided to first chase the USB freeze, because it was easier to gather information about that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rweber 1525 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 14 18:38:36 2015 HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a InstallationDate: Installed on 2015-06-28 (46 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire ES1-111M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-111M dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485057] Re: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown
The cause of the freeze seems to be a BIOS problem, as Alan suggested on the linux-usb mailing list. When booting in UEFI mode (from a Xubuntu 15.04 installation medium), three of the devices listed by lspci are missing, compared to legacy BIOS mode. One of those is the device that caused the freezes. Looks like some of the hardware is unused, and Acer just hides it from the OS. But only in UEFI mode. I'll try a re-installation of Xubuntu in UEFI mode. ** Attachment added: "output of lspci when booting in UEFI mode (insecure)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+attachment/4474853/+files/lspci-uefi.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/1485057 Title: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown Status in linux package in Ubuntu: Triaged Bug description: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) Incidentally, the shutdown sequence also freezes with the kernels that exhibit the problem; but I cannot be sure that the cause is the same. I decided to first chase the USB freeze, because it was easier to gather information about that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rweber 1525 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 14 18:38:36 2015 HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a InstallationDate: Installed on 2015-06-28 (46 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire ES1-111M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-111M dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485057] Re: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown
** Attachment added: "output of lspci when booting in legacy BIOS mode" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+attachment/4474852/+files/lspci-legacy.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/1485057 Title: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown Status in linux package in Ubuntu: Triaged Bug description: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) Incidentally, the shutdown sequence also freezes with the kernels that exhibit the problem; but I cannot be sure that the cause is the same. I decided to first chase the USB freeze, because it was easier to gather information about that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rweber 1525 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 14 18:38:36 2015 HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a InstallationDate: Installed on 2015-06-28 (46 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire ES1-111M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-111M dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485057] Re: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown
contents of /sys/kernel/debug/usb/ehci/:00:1d.0/registers before unbinding: bus pci, device :00:1d.0 EHCI Host Controller EHCI 1.00, rh state running ownership 0001 SMI sts/enable 0xc008 structural params 0x0028 capability params 0x00036881 status 6008 Periodic Recl FLR command 0010011 (park)=0 ithresh=1 Periodic period=1024 RUN intrenable 37 IAA FATAL PCD ERR INT uframe 2cb2 port:1 status 001005 0 ACK POWER sig=se0 PE CONNECT port:2 status 001000 0 ACK POWER sig=se0 port:3 status 001000 0 ACK POWER sig=se0 port:4 status 001000 0 ACK POWER sig=se0 port:5 status 001000 0 ACK POWER sig=se0 port:6 status 001000 0 ACK POWER sig=se0 port:7 status 001000 0 ACK POWER sig=se0 port:8 status 001000 0 ACK POWER sig=se0 irq normal 17 err 0 iaa 8 (lost 0) complete 17 unlink 0 There are no /sys/.../power/ files, because CONFIG_PM is disabled. This kernel does not freeze, so the debug output on unbinding is contained in the attached dmesg log. ** Attachment added: "dmesg from a corresponding 4.2 kernel, CONFIG_PM disabled" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+attachment/4469704/+files/dmesg-g-after-unbind.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/1485057 Title: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown Status in linux package in Ubuntu: Triaged Bug description: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) Incidentally, the shutdown sequence also freezes with the kernels that exhibit the problem; but I cannot be sure that the cause is the same. I decided to first chase the USB freeze, because it was easier to gather information about that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rweber 1525 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 14 18:38:36 2015 HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a InstallationDate: Installed on 2015-06-28 (46 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire ES1-111M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-111M dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://lau
[Kernel-packages] [Bug 1485057] Re: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown
contents of /sys/kernel/debug/usb/ehci/:00:1d.0/registers before unbinding the bus which triggers the freeze: bus pci, device :00:1d.0 EHCI Host Controller EHCI 1.00, rh state suspended ownership 0101 linux SMI sts/enable 0xe000 structural params 0x0028 capability params 0x00036881 status 1000 Halt command 001 (park)=0 ithresh=1 period=1024 HALT intrenable 37 IAA FATAL PCD ERR INT uframe 0bbf port:1 status 601085 0 ACK POWER sig=se0 SUSPEND PE CONNECT port:2 status 501000 0 ACK POWER sig=se0 port:3 status 501000 0 ACK POWER sig=se0 port:4 status 501000 0 ACK POWER sig=se0 port:5 status 501000 0 ACK POWER sig=se0 port:6 status 501000 0 ACK POWER sig=se0 port:7 status 501000 0 ACK POWER sig=se0 port:8 status 501000 0 ACK POWER sig=se0 irq normal 18 err 0 iaa 8 (lost 0) complete 18 unlink 1 /sys/bus/pci/devices/:00:1d.0/power/control: on /sys/bus/pci/devices/:00:1d.0/power/runtime_status: active transcript of on-screen output when unbinding the EHCI USB bus: ehci-pci :00:1d.0: remove, state 4 ehci-pci :00:1d.0: roothub graceful disconnect usb usb3: USB disconnect, device number 1 usb 3-1: USB disconnect, device number 2 usb 3-1: ep 81: release intr @ 8+64 (1.0+256) [1/0 us] mask 0001 usb_remove_hcd: calling stop ehci_silence_controller: entry ehci_halt: entry ehci_halt: about to readl prematurely ehci_halt: premature readl returned 1 ehci_halt: after first ehci_writel ehci_halt: before ehci_readl ** Attachment added: "dmesg from a 4.2 kernel with extra debug output, CONFIG_PM enabled" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+attachment/4469703/+files/dmesg-f.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/1485057 Title: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown Status in linux package in Ubuntu: Triaged Bug description: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) Incidentally, the shutdown sequence also freezes with the kernels that exhibit the problem; but I cannot be sure that the cause is the same. I decided to first chase the USB freeze, because it was easier to gather information about that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rweber 1525 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 14 18:38:36 2015 HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a InstallationDate: Installed on 2015-06-28 (46 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire ES1-111M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvn
[Kernel-packages] [Bug 1485057] Re: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown
I removed the bios-outdated tag. The guy who wrote about his BIOS update in comment #9 has a completely different problem and commented off- topic. ** Tags removed: bios-outdated-1.13 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485057 Title: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown Status in linux package in Ubuntu: Triaged Bug description: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) Incidentally, the shutdown sequence also freezes with the kernels that exhibit the problem; but I cannot be sure that the cause is the same. I decided to first chase the USB freeze, because it was easier to gather information about that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rweber 1525 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 14 18:38:36 2015 HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a InstallationDate: Installed on 2015-06-28 (46 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire ES1-111M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-111M dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485057] Re: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown
Current state of things: I've tracked down the code line where the freeze happens. It's in function ehci_halt within file ehci-hcd.c. The function is executed on shutdown as well as when the usb devices on the bus are about to be probed again. The latter is triggered by "lsusb -v" as root. Apparently, the hardware misbehaves by not responding to a "readl" call. As a workaround, it is possible to compile kernel 4.2 with a patch that disables the unused EHCI USB bus. However, this is *not* a generic solution! The same chip may be built into other computers, and the EHCI bus may be used there. ** Patch added: "Patch to blacklist the problematic EHCI bus. This is a workaround, NOT a solution!" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+attachment/4462350/+files/blacklist-evil-ehci-device.diff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485057 Title: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown Status in linux package in Ubuntu: Triaged Bug description: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) Incidentally, the shutdown sequence also freezes with the kernels that exhibit the problem; but I cannot be sure that the cause is the same. I decided to first chase the USB freeze, because it was easier to gather information about that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rweber 1525 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 14 18:38:36 2015 HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a InstallationDate: Installed on 2015-06-28 (46 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire ES1-111M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-111M dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485057] Re: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown
For the records, here's a screenshot (photo) of the system after a freeze. Series of actions to get there: 1. enable kernel debug output 2. detach external mouse, to verify that messages appear 3. hit enter to get a new prompt line 4. trigger the freeze with "lsusb -v" lsusb prints the name of the device it's going to work with. Then nothing anymore. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485057 Title: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown Status in linux package in Ubuntu: Triaged Bug description: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) Incidentally, the shutdown sequence also freezes with the kernels that exhibit the problem; but I cannot be sure that the cause is the same. I decided to first chase the USB freeze, because it was easier to gather information about that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rweber 1525 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 14 18:38:36 2015 HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a InstallationDate: Installed on 2015-06-28 (46 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire ES1-111M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-111M dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485057] Re: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown
** Attachment added: "photo of the virtual terminal after the freeze" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+attachment/4458832/+files/screenshot-freeze.JPG -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485057 Title: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown Status in linux package in Ubuntu: Triaged Bug description: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) Incidentally, the shutdown sequence also freezes with the kernels that exhibit the problem; but I cannot be sure that the cause is the same. I decided to first chase the USB freeze, because it was easier to gather information about that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rweber 1525 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 14 18:38:36 2015 HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a InstallationDate: Installed on 2015-06-28 (46 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire ES1-111M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-111M dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485057] Re: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown
Sorry, the link in comment #14 is nonsense, a paste error. The new way to trigger a freeze is: echo :00:1d.0 >/sys/bus/pci/drivers/ehci-pci/unbind -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485057 Title: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown Status in linux package in Ubuntu: Triaged Bug description: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) Incidentally, the shutdown sequence also freezes with the kernels that exhibit the problem; but I cannot be sure that the cause is the same. I decided to first chase the USB freeze, because it was easier to gather information about that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rweber 1525 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 14 18:38:36 2015 HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a InstallationDate: Installed on 2015-06-28 (46 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire ES1-111M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-111M dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485057] Re: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown
Sorry, the link in comment #14 is nonsense, a paste error. The new way to trigger a freeze is: echo :00:1d.0 >/sys/bus/pci/drivers/ehci-pci/unbind -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485057 Title: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown Status in linux package in Ubuntu: Triaged Bug description: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) Incidentally, the shutdown sequence also freezes with the kernels that exhibit the problem; but I cannot be sure that the cause is the same. I decided to first chase the USB freeze, because it was easier to gather information about that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rweber 1525 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 14 18:38:36 2015 HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a InstallationDate: Installed on 2015-06-28 (46 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire ES1-111M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-111M dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485057] Re: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown
As suggested by Alan Stone on the linux-usb mailing list, I've verified that the "USB cable is bad" messages are caused by the order in which the USB devices are initialized. I've also found a new way of triggering the freeze on a bad kernel: https://bugs.freedesktop.org/show_bug.cgi?id=76935#c1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485057 Title: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown Status in linux package in Ubuntu: Triaged Bug description: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) Incidentally, the shutdown sequence also freezes with the kernels that exhibit the problem; but I cannot be sure that the cause is the same. I decided to first chase the USB freeze, because it was easier to gather information about that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rweber 1525 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 14 18:38:36 2015 HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a InstallationDate: Installed on 2015-06-28 (46 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire ES1-111M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-111M dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485057] Re: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown
The previous log for the "bad" kernel was incomplete, due to kernel buffer overflows caused by systemd output. I've switched that off as explained here: https://bugs.freedesktop.org/show_bug.cgi?id=76935#c1 ** Bug watch added: freedesktop.org Bugzilla #76935 https://bugs.freedesktop.org/show_bug.cgi?id=76935 ** Attachment added: "boot messages of a "bad" kernel with additional entry/exit for USB hub init" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+attachment/4458181/+files/dmesg.nosystemd.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/1485057 Title: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown Status in linux package in Ubuntu: Triaged Bug description: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) Incidentally, the shutdown sequence also freezes with the kernels that exhibit the problem; but I cannot be sure that the cause is the same. I decided to first chase the USB freeze, because it was easier to gather information about that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rweber 1525 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 14 18:38:36 2015 HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a InstallationDate: Installed on 2015-06-28 (46 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire ES1-111M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-111M dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485057] Re: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown
Valentine, your problem is almost certainly not related to the one I reported here. You should seek advice in forums or on mailing lists for your computer and/or distribution. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485057 Title: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown Status in linux package in Ubuntu: Triaged Bug description: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) Incidentally, the shutdown sequence also freezes with the kernels that exhibit the problem; but I cannot be sure that the cause is the same. I decided to first chase the USB freeze, because it was easier to gather information about that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rweber 1525 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 14 18:38:36 2015 HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a InstallationDate: Installed on 2015-06-28 (46 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire ES1-111M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-111M dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485057] Re: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown
As suggested on the linux.usb mailing list, I've added some additional debug print statements to the first bad kernel. They are not triggered by "lsusb -v" though. I'm attaching kernel debug output from the boot sequence of two kernels: - the bad one, with additional print statements - the last good one, without additional print statements The difference in the startup behavior is remarkable. ** Attachment added: "first bad kernel, extra output "entry" and "exit"" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+attachment/4456918/+files/dmesg.bad.full.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/1485057 Title: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown Status in linux package in Ubuntu: Triaged Bug description: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) Incidentally, the shutdown sequence also freezes with the kernels that exhibit the problem; but I cannot be sure that the cause is the same. I decided to first chase the USB freeze, because it was easier to gather information about that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rweber 1525 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 14 18:38:36 2015 HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a InstallationDate: Installed on 2015-06-28 (46 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire ES1-111M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-111M dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485057] Re: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown
** Attachment added: "last good kernel" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+attachment/4456919/+files/dmesg.good.full.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/1485057 Title: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown Status in linux package in Ubuntu: Triaged Bug description: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) Incidentally, the shutdown sequence also freezes with the kernels that exhibit the problem; but I cannot be sure that the cause is the same. I decided to first chase the USB freeze, because it was easier to gather information about that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rweber 1525 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 14 18:38:36 2015 HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a InstallationDate: Installed on 2015-06-28 (46 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire ES1-111M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-111M dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485057] Re: "lsusb -v" as root freezes the kernel on Acer ES1-111
I've verified that the freeze on shutdown is caused by the same commit. Contrary to my initial report here, the freeze on shutdown happens late in the sequence, not early. I'm used to much longer shutdown times from my desktop :-) ** Summary changed: - "lsusb -v" as root freezes the kernel on Acer ES1-111 + "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown ** Description changed: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) - Incidentally, the shutdown sequence also freezes early on with the - kernels that exhibit the problem; but I cannot be sure that the cause is - the same. I decided to first chase the USB freeze, because it was easier - to gather information about that. + Incidentally, the shutdown sequence also freezes with the kernels that + exhibit the problem; but I cannot be sure that the cause is the same. I + decided to first chase the USB freeze, because it was easier to gather + information about that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rweber 1525 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 14 18:38:36 2015 HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a InstallationDate: Installed on 2015-06-28 (46 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire ES1-111M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-111M dmi.product.version: V1.08 dmi.sys.vendor: Acer -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485057 Title: "lsusb -v" as root freezes the kernel on Acer ES1-111; also freeze on shutdown Status in linux package in Ubuntu: Triaged Bug description: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to wo
[Kernel-packages] [Bug 1485057] Re: "lsusb -v" as root freezes the kernel on Acer ES1-111
As requested on the linux-usb mailing list, I've bisected the problem in the mainline git repository. 638139eb95d2d241781330a321e88c8dafe46078 is the first bad commit commit 638139eb95d2d241781330a321e88c8dafe46078 Author: Petr Mladek Date: Fri Sep 19 17:32:24 2014 +0200 usb: hub: allow to process more usb hub events in parallel It seems that only choose_devnum() was not ready to process more hub events at the same time. All should be fine if we take bus->usb_address0_mutex there. It will make sure that more devnums will not be chosen for the given bus and the related devices at the same time. Signed-off-by: Petr Mladek Acked-by: Alan Stern Signed-off-by: Greg Kroah-Hartman :04 04 6c3b464b8db2bec572cf7904c0aac317b41c1eec da3ee40957d0637f17895ae05aad4a6646377b2a M drivers -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485057 Title: "lsusb -v" as root freezes the kernel on Acer ES1-111 Status in linux package in Ubuntu: Triaged Bug description: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) Incidentally, the shutdown sequence also freezes early on with the kernels that exhibit the problem; but I cannot be sure that the cause is the same. I decided to first chase the USB freeze, because it was easier to gather information about that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rweber 1525 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 14 18:38:36 2015 HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a InstallationDate: Installed on 2015-06-28 (46 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire ES1-111M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-111M dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485057] Re: "lsusb -v" as root freezes the kernel on Acer ES1-111
** Attachment added: "output of "git bisect log"" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+attachment/4451330/+files/bisect.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/1485057 Title: "lsusb -v" as root freezes the kernel on Acer ES1-111 Status in linux package in Ubuntu: Triaged Bug description: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) Incidentally, the shutdown sequence also freezes early on with the kernels that exhibit the problem; but I cannot be sure that the cause is the same. I decided to first chase the USB freeze, because it was easier to gather information about that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rweber 1525 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 14 18:38:36 2015 HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a InstallationDate: Installed on 2015-06-28 (46 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire ES1-111M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-111M dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485057] Re: "lsusb -v" as root freezes the kernel on Acer ES1-111
Thanks for your advice! I've posted a bug report upstream: http://permalink.gmane.org/gmane.linux.usb.general/129790 I also checked out some older kernels. The problem is present since 3.18, while 3.17.x was OK. Or rather, had other, less dramatic problems on the machine. ** Tags added: kernel-bug-reported-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/1485057 Title: "lsusb -v" as root freezes the kernel on Acer ES1-111 Status in linux package in Ubuntu: Triaged Bug description: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) Incidentally, the shutdown sequence also freezes early on with the kernels that exhibit the problem; but I cannot be sure that the cause is the same. I decided to first chase the USB freeze, because it was easier to gather information about that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rweber 1525 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 14 18:38:36 2015 HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a InstallationDate: Installed on 2015-06-28 (46 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire ES1-111M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-111M dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485057] Re: "lsusb -v" as root freezes the kernel on Acer ES1-111
** Attachment added: "output of lsusb -t" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+attachment/865/+files/lsusb-t.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/1485057 Title: "lsusb -v" as root freezes the kernel on Acer ES1-111 Status in linux package in Ubuntu: New Bug description: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) Incidentally, the shutdown sequence also freezes early on with the kernels that exhibit the problem; but I cannot be sure that the cause is the same. I decided to first chase the USB freeze, because it was easier to gather information about that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rweber 1525 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 14 18:38:36 2015 HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a InstallationDate: Installed on 2015-06-28 (46 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire ES1-111M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-111M dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1485057] [NEW] "lsusb -v" as root freezes the kernel on Acer ES1-111
Public bug reported: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) Incidentally, the shutdown sequence also freezes early on with the kernels that exhibit the problem; but I cannot be sure that the cause is the same. I decided to first chase the USB freeze, because it was easier to gather information about that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rweber 1525 F pulseaudio CurrentDesktop: XFCE Date: Fri Aug 14 18:38:36 2015 HibernationDevice: RESUME=UUID=8a45266d-0232-428e-bb25-113d23caaf8a InstallationDate: Installed on 2015-06-28 (46 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire ES1-111M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=b8872e03-7295-4cbd-ac86-06b9be2f112f ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.3 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-05 (39 days ago) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireES1-111M:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-111M dmi.product.version: V1.08 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1485057 Title: "lsusb -v" as root freezes the kernel on Acer ES1-111 Status in linux package in Ubuntu: New Bug description: reproducible: always Steps to reproduce: - open a terminal - sudo bash - lsusb -v In a virtual terminal, the command prints the name of the first device it finds, then the system freezes completely. In a terminal of the desktop, I don't even get the name of the device, the system freezes immediately. Either way, I have to power off the machine. There is no kernel oops. Nothing is written to the log. The magic sysreq key yields no response, although I have verified that it works before triggering the freeze. I've narrowed down the problem by calling "lsusb -v -s ". The system freezes on both devices of bus 3 (003:001 and 003:002). For all other devices, it prints the expected output and continues to work. When calling lsusb as a regular user, I get "Couldn't open device, some information will be missing", then the regular output, and the system keeps running. Therefore I assume that the problem is somewhere in the kernel, when the devices are accessed. This is a regression. It used to work in 14.10, and fails to work since 15.04. It also used to work in 14.04.2, and fails in 14.04.3. It fails with mainline builds 4.2.0-rc6-unstable, 4.2.0-rc2-unstable, 4.1.0-rc2-vivid. (yeah, I've been trying for a while :-) Incidentally, the shutdown sequence also freezes early on with the kernels that exhibit the problem; but I cannot be sure that the cause is the same. I decided to
[Kernel-packages] [Bug 1440724] Re: linux-image 3.19.0.12.11 will not boot - Intel mobile 965 chipset
Joseph, your kernel in comment #52 does work on my 2 affected laptops -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1440724 Title: linux-image 3.19.0.12.11 will not boot - Intel mobile 965 chipset Status in linux package in Ubuntu: Confirmed Status in linux source package in Vivid: Confirmed Bug description: the recent Vivid linux meta package upgrade of 3.19.0.12.11 caused my Dell Latitude D630 to stop booting. The boot continues to "starting version 219" and then freezes. Eliminating the "splash" option by editing GRUB allows the computer to boot until the login screen. After login, the computer again locks up, displaying a blue background and a immobile mouse pointer in the center of the screen. The same behavior occurs when booting from the daily DVD image which contains 3.19.0.12. I have reverted to 3.19.0.11.10 which is how I am reporting this bug. I'm not sure the usual commands for reporting bugs would be helpful while running the previous kernel. I am unable to run these commands with 3.19.0.12 as I cannot get to a point of interacting with the system. I have attached the syslog from attempting to boot 3.19.0.12. --- ApportVersion: 2.17-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: tom1459 F...m pulseaudio /dev/snd/pcmC0D0p: tom1459 F...m pulseaudio /dev/snd/controlC0: tom1459 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=4588a704-477d-4b44-b827-bd13e745d90f InstallationDate: Installed on 2012-08-01 (977 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120801) MachineType: Dell Inc. Latitude D630 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-11-lowlatency root=UUID=91eb6d24-9c1b-47d8-ac9f-75db6a566e5c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-11.11-lowlatency 3.19.3 RelatedPackageVersions: linux-restricted-modules-3.19.0-11-lowlatency N/A linux-backports-modules-3.19.0-11-lowlatency N/A linux-firmware1.143 Tags: vivid Uname: Linux 3.19.0-11-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev pulse sambashare sudo users _MarkForUpload: True dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.17-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: tom1459 F...m pulseaudio /dev/snd/pcmC0D0p: tom1459 F...m pulseaudio /dev/snd/controlC0: tom1459 F pulseaudio /dev/snd/seq:timidity718 F timidity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=4588a704-477d-4b44-b827-bd13e745d90f InstallationDate: Installed on 2012-08-01 (977 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120801) MachineType: Dell Inc. Latitude D630 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-11-lowlatency root=UUID=91eb6d24-9c1b-47d8-ac9f-75db6a566e5c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-11.11-lowlatency 3.19.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.19.0-11-lowlatency N/A linux-backports-modules-3.19.0-11-lowlatency N/A linux-firmware1.143 Tags: vivid Uname: Linux 3.19.0-11-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug
[Kernel-packages] [Bug 1440724] Re: linux-image 3.19.0.12.11 will not boot - Intel mobile 965 chipset
Same here, on two laptops, one the same Dell D630 as the OP, as well as a basically identical D830. However, editing the boot parameters from the grub menu does not allow me to get to a login screen, and I am unable to even get to a vt to run any sort of commands. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1440724 Title: linux-image 3.19.0.12.11 will not boot - Intel mobile 965 chipset Status in linux package in Ubuntu: Incomplete Bug description: the recent Vivid linux meta package upgrade of 3.19.0.12.11 caused my Dell Latitude D630 to stop booting. The boot continues to "starting version 219" and then freezes. Eliminating the "splash" option by editing GRUB allows the computer to boot until the login screen. After login, the computer again locks up, displaying a blue background and a immobile mouse pointer in the center of the screen. The same behavior occurs when booting from the daily DVD image which contains 3.19.0.12. I have reverted to 3.19.0.11.10 which is how I am reporting this bug. I'm not sure the usual commands for reporting bugs would be helpful while running the previous kernel. I am unable to run these commands with 3.19.0.12 as I cannot get to a point of interacting with the system. I have attached the syslog from attempting to boot 3.19.0.12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440724/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1140716] Re: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge
same here on Acer TravelMate B113 on 3.8.0-29-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge Status in The Linux Kernel: Invalid Status in “linux” package in Ubuntu: Invalid Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux” source package in Precise: Fix Released Status in “linux-lts-quantal” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux” source package in Raring: Confirmed Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux” package in Debian: New Status in “linux” package in Fedora: Unknown Bug description: I'm getting errors about GPU hangs every minute or so (usually only when using FF and scrolling a webpage or something). I also get an annoying ubuntu dialog saying there is a "system error". This didn't happen with 3.5.0-24-generic. Here is the dmesg: [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.658405] [ cut here ] [26285.658472] WARNING: at /build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 gen6_enable_rps+0x706/0x710 [i915]() [26285.658474] Hardware name: SATELLITE Z830 [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc lp parport e1000e ahci libahci [last unloaded: sdhci] [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic #40-Ubuntu [26285.658539] Call Trace: [26285.658549] [] warn_slowpath_common+0x7f/0xc0 [26285.658553] [] warn_slowpath_null+0x1a/0x20 [26285.658569] [] gen6_enable_rps+0x706/0x710 [i915] [26285.658584] [] intel_modeset_init_hw+0x66/0xa0 [i915] [26285.658595] [] i915_reset+0x1a4/0x6e0 [i915] [26285.658601] [] ? __switch_to+0x12b/0x420 [26285.658612] [] i915_error_work_func+0xc3/0x110 [i915] [26285.658618] [] process_one_work+0x12a/0x420 [26285.658629] [] ? gen6_pm_rps_work+0xe0/0xe0 [i915] [26285.658632] [] worker_thread+0x12e/0x2f0 [26285.658636] [] ? manage_workers.isra.26+0x200/0x200 [26285.658640] [] kthread+0x93/0xa0 [26285.658644] [] kernel_thread_helper+0x4/0x10 [26285.658649] [] ? kthread_freezable_should_stop+0x70/0x70 [26285.658652] [] ? gs_change+0x13/0x13 [26285.658654] ---[ end trace 59c6162fdfcbffee ]--- [26756.021167] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26756.021426] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26766.014093] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26766.014397] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26932.376233] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26932.376544] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26932.384285] [ cut here ] [26932.384354] WARNING: at /build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 gen6_enable_rps+0x706/0x710 [i915]() [26932.384356] Hardware name: SATELLITE Z830 [26932.384358] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_6
