[Kernel-packages] [Bug 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
@vicamo At this time the kernel is available in proposed.
I can confirm that the kernel 5.8.0-44, in proposed, solves the problem
in Groovy.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1894778
Title:
Cannot probe sata disk on sata controller behind VMD: ata1.00: failed
to IDENTIFY (I/O error, err_mask=0x4)
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Won't Fix
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
[SRU Justification]
[Impact]
When booting with a certain platforms with boot disk attached to SATA
bus behind Intel VMD controller, disk probing may fail with following
error messages left in dmesg:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Fix]
Upstream commit f6b7bb847ca8 ("PCI: vmd: Offset Client VMD MSI-X
vectors") currently in vanilla kernel tree for v5.11.
[Test Case]
Check dmesg/lsblk for disk probe.
For pci MSI address, check lspci output:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0 Data:
When it fails, the address is fee0. And with a patched kernel:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000 Data:
[Where problems could occur]
An unpatched kernel will not be able to probe SATA controllers moved
behind VMD when VMD/RAID mode is enabled in BIOS, leaving disks
attached on it completely unusable. With this change, kernel would
then be able to probe them but may also suffer from issues that only
occur under such configuration. However, the worst case is to move away
sata disks from VMD bus as they are currently without this fix, so the
risk here should be justified.
== Previous SRU ==
[SRU Justification]
[Impact]
When booting with a certain platforms with boot disk attached to SATA
bus behind Intel VMD controller, disk probing may fail with following
error messages left in dmesg:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Fix]
Proposed kernel patch https://patchwork.kernel.org/patch/11758345/
[Test Case]
Check dmesg/lsblk for disk probe.
For pci MSI address, check lspci output:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0 Data:
When it fails, the address is fee0. And with a patched kernel:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000 Data:
[Regression Potential]
Low. For previous NVMe based platforms, this patch brings no effective
change for NVMe devices because they will still stay in fast-interrupt
list.
== Original Bug Description ==
When booting with root filesystem on sata disks under Intel VMD mode,
following errors printed in dmesg and no disk is found, nor booting
into it:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 16.659284] ata1.00: qc timeout (cmd 0xec)
[ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps
[ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 48.147294] ata1.00: qc timeout (cmd 0xec)
[ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
$ lspci
...
1:e0:17.0 SATA controller: Intel Corporation Device a0d3 (rev 20)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1894778/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
@vicamo Thanks for your explanation. I can test 5.8.0-44 as soon as it
is in proposed.
regards
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1894778
Title:
Cannot probe sata disk on sata controller behind VMD: ata1.00: failed
to IDENTIFY (I/O error, err_mask=0x4)
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Won't Fix
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
[SRU Justification]
[Impact]
When booting with a certain platforms with boot disk attached to SATA
bus behind Intel VMD controller, disk probing may fail with following
error messages left in dmesg:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Fix]
Upstream commit f6b7bb847ca8 ("PCI: vmd: Offset Client VMD MSI-X
vectors") currently in vanilla kernel tree for v5.11.
[Test Case]
Check dmesg/lsblk for disk probe.
For pci MSI address, check lspci output:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0 Data:
When it fails, the address is fee0. And with a patched kernel:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000 Data:
[Where problems could occur]
An unpatched kernel will not be able to probe SATA controllers moved
behind VMD when VMD/RAID mode is enabled in BIOS, leaving disks
attached on it completely unusable. With this change, kernel would
then be able to probe them but may also suffer from issues that only
occur under such configuration. However, the worst case is to move away
sata disks from VMD bus as they are currently without this fix, so the
risk here should be justified.
== Previous SRU ==
[SRU Justification]
[Impact]
When booting with a certain platforms with boot disk attached to SATA
bus behind Intel VMD controller, disk probing may fail with following
error messages left in dmesg:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Fix]
Proposed kernel patch https://patchwork.kernel.org/patch/11758345/
[Test Case]
Check dmesg/lsblk for disk probe.
For pci MSI address, check lspci output:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0 Data:
When it fails, the address is fee0. And with a patched kernel:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000 Data:
[Regression Potential]
Low. For previous NVMe based platforms, this patch brings no effective
change for NVMe devices because they will still stay in fast-interrupt
list.
== Original Bug Description ==
When booting with root filesystem on sata disks under Intel VMD mode,
following errors printed in dmesg and no disk is found, nor booting
into it:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 16.659284] ata1.00: qc timeout (cmd 0xec)
[ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps
[ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 48.147294] ata1.00: qc timeout (cmd 0xec)
[ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
$ lspci
...
1:e0:17.0 SATA controller: Intel Corporation Device a0d3 (rev 20)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1894778/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
I must report that this bug has returned to Groovy with linux-
image-5.8.0-43-generic
It was tested in groovy since proposed with linux-image-5.8.0-42-generic
and verified as indicated here, within 5 days of publication.
What happened?
Does anyone know?
I myself marked it as Fix Released in groovy
And now?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1894778
Title:
Cannot probe sata disk on sata controller behind VMD: ata1.00: failed
to IDENTIFY (I/O error, err_mask=0x4)
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Won't Fix
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
[SRU Justification]
[Impact]
When booting with a certain platforms with boot disk attached to SATA
bus behind Intel VMD controller, disk probing may fail with following
error messages left in dmesg:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Fix]
Upstream commit f6b7bb847ca8 ("PCI: vmd: Offset Client VMD MSI-X
vectors") currently in vanilla kernel tree for v5.11.
[Test Case]
Check dmesg/lsblk for disk probe.
For pci MSI address, check lspci output:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0 Data:
When it fails, the address is fee0. And with a patched kernel:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000 Data:
[Where problems could occur]
An unpatched kernel will not be able to probe SATA controllers moved
behind VMD when VMD/RAID mode is enabled in BIOS, leaving disks
attached on it completely unusable. With this change, kernel would
then be able to probe them but may also suffer from issues that only
occur under such configuration. However, the worst case is to move away
sata disks from VMD bus as they are currently without this fix, so the
risk here should be justified.
== Previous SRU ==
[SRU Justification]
[Impact]
When booting with a certain platforms with boot disk attached to SATA
bus behind Intel VMD controller, disk probing may fail with following
error messages left in dmesg:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Fix]
Proposed kernel patch https://patchwork.kernel.org/patch/11758345/
[Test Case]
Check dmesg/lsblk for disk probe.
For pci MSI address, check lspci output:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0 Data:
When it fails, the address is fee0. And with a patched kernel:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000 Data:
[Regression Potential]
Low. For previous NVMe based platforms, this patch brings no effective
change for NVMe devices because they will still stay in fast-interrupt
list.
== Original Bug Description ==
When booting with root filesystem on sata disks under Intel VMD mode,
following errors printed in dmesg and no disk is found, nor booting
into it:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 16.659284] ata1.00: qc timeout (cmd 0xec)
[ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps
[ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 48.147294] ata1.00: qc timeout (cmd 0xec)
[ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
$ lspci
...
1:e0:17.0 SATA controller: Intel Corporation Device a0d3 (rev 20)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1894778/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Aksahat:
Could something go wrong while doing this?
No, it couldn't be worse than what you already have. The OEM kernel is
tested and resolves this particular bug and others.
How long before patched kernel is released for ubuntu-20.04?
That question is for the Ubuntu development team. I dare to calculate
that between two and four weeks. Maybe less, but no more than that.
How can I be sure of my error is this same error and will be relsolved
by patch?
If you use sudo apt install linux-oem-20.04 you reboot and in grub you
select the OEM kernel and it fixes the error, that's it.
If you don't want to do that, check the detail of the error in this
thread and compare it with yours.
The command output you share says nothing more than the kernel version
you have.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1894778
Title:
Cannot probe sata disk on sata controller behind VMD: ata1.00: failed
to IDENTIFY (I/O error, err_mask=0x4)
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Won't Fix
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
[SRU Justification]
[Impact]
When booting with a certain platforms with boot disk attached to SATA
bus behind Intel VMD controller, disk probing may fail with following
error messages left in dmesg:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Fix]
Upstream commit f6b7bb847ca8 ("PCI: vmd: Offset Client VMD MSI-X
vectors") currently in vanilla kernel tree for v5.11.
[Test Case]
Check dmesg/lsblk for disk probe.
For pci MSI address, check lspci output:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0 Data:
When it fails, the address is fee0. And with a patched kernel:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000 Data:
[Where problems could occur]
An unpatched kernel will not be able to probe SATA controllers moved
behind VMD when VMD/RAID mode is enabled in BIOS, leaving disks
attached on it completely unusable. With this change, kernel would
then be able to probe them but may also suffer from issues that only
occur under such configuration. However, the worst case is to move away
sata disks from VMD bus as they are currently without this fix, so the
risk here should be justified.
== Previous SRU ==
[SRU Justification]
[Impact]
When booting with a certain platforms with boot disk attached to SATA
bus behind Intel VMD controller, disk probing may fail with following
error messages left in dmesg:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Fix]
Proposed kernel patch https://patchwork.kernel.org/patch/11758345/
[Test Case]
Check dmesg/lsblk for disk probe.
For pci MSI address, check lspci output:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0 Data:
When it fails, the address is fee0. And with a patched kernel:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000 Data:
[Regression Potential]
Low. For previous NVMe based platforms, this patch brings no effective
change for NVMe devices because they will still stay in fast-interrupt
list.
== Original Bug Description ==
When booting with root filesystem on sata disks under Intel VMD mode,
following errors printed in dmesg and no disk is found, nor booting
into it:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 16.659284] ata1.00: qc timeout (cmd 0xec)
[ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps
[ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 48.147294] ata1.00: qc timeout (cmd 0xec)
[ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
$ lspci
...
1:e0:17.0 SATA controller: Intel Corporation
[Kernel-packages] [Bug 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Aksahat: The kernel 5.8.0-42 is not yet in proposed, on Ubuntu 20.04.
For now only on Ubuntu 20.10.
The alternative, until it is included in Ubuntu 20.04.2 is this:
sudo apt install linux-oem-20.04
This way, the OEM 5.6 kernel is installed, which is fix.
Then you have to uninstall the hwe kernel:
sudo apt remove --purge --install-recommends linux-generic-hwe-20.04
To list installed kernels:
sudo dpkg --list | grep linux-image
and:
sudo dpkg --list | grep linux-headers
Clear all 5.8 kernels with:
sudo apt-get --purge remove linux-xxx
That or wait for it to be fixed in ubuntu 20.04 with kernel 5.8
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1894778
Title:
Cannot probe sata disk on sata controller behind VMD: ata1.00: failed
to IDENTIFY (I/O error, err_mask=0x4)
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Won't Fix
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
[SRU Justification]
[Impact]
When booting with a certain platforms with boot disk attached to SATA
bus behind Intel VMD controller, disk probing may fail with following
error messages left in dmesg:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Fix]
Upstream commit f6b7bb847ca8 ("PCI: vmd: Offset Client VMD MSI-X
vectors") currently in vanilla kernel tree for v5.11.
[Test Case]
Check dmesg/lsblk for disk probe.
For pci MSI address, check lspci output:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0 Data:
When it fails, the address is fee0. And with a patched kernel:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000 Data:
[Where problems could occur]
An unpatched kernel will not be able to probe SATA controllers moved
behind VMD when VMD/RAID mode is enabled in BIOS, leaving disks
attached on it completely unusable. With this change, kernel would
then be able to probe them but may also suffer from issues that only
occur under such configuration. However, the worst case is to move away
sata disks from VMD bus as they are currently without this fix, so the
risk here should be justified.
== Previous SRU ==
[SRU Justification]
[Impact]
When booting with a certain platforms with boot disk attached to SATA
bus behind Intel VMD controller, disk probing may fail with following
error messages left in dmesg:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Fix]
Proposed kernel patch https://patchwork.kernel.org/patch/11758345/
[Test Case]
Check dmesg/lsblk for disk probe.
For pci MSI address, check lspci output:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0 Data:
When it fails, the address is fee0. And with a patched kernel:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000 Data:
[Regression Potential]
Low. For previous NVMe based platforms, this patch brings no effective
change for NVMe devices because they will still stay in fast-interrupt
list.
== Original Bug Description ==
When booting with root filesystem on sata disks under Intel VMD mode,
following errors printed in dmesg and no disk is found, nor booting
into it:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 16.659284] ata1.00: qc timeout (cmd 0xec)
[ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps
[ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 48.147294] ata1.00: qc timeout (cmd 0xec)
[ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
$ lspci
...
1:e0:17.0 SATA controller: Intel Corporation Device a0d3 (rev 20)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1894778/+subscriptions
--
Mailing list:
[Kernel-packages] [Bug 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Aksahat: Here are the instructions to activate proposed:
https://wiki.ubuntu.com/Testing/EnableProposed Either way, the new
kernel should be on regular Ubuntu 20.10 updates, and also 20.04 with
HWE kernel, in the next few days or weeks. I still hope that it reaches
the launch of Ubuntu 20.04.2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1894778
Title:
Cannot probe sata disk on sata controller behind VMD: ata1.00: failed
to IDENTIFY (I/O error, err_mask=0x4)
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Won't Fix
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
[SRU Justification]
[Impact]
When booting with a certain platforms with boot disk attached to SATA
bus behind Intel VMD controller, disk probing may fail with following
error messages left in dmesg:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Fix]
Upstream commit f6b7bb847ca8 ("PCI: vmd: Offset Client VMD MSI-X
vectors") currently in vanilla kernel tree for v5.11.
[Test Case]
Check dmesg/lsblk for disk probe.
For pci MSI address, check lspci output:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0 Data:
When it fails, the address is fee0. And with a patched kernel:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000 Data:
[Where problems could occur]
An unpatched kernel will not be able to probe SATA controllers moved
behind VMD when VMD/RAID mode is enabled in BIOS, leaving disks
attached on it completely unusable. With this change, kernel would
then be able to probe them but may also suffer from issues that only
occur under such configuration. However, the worst case is to move away
sata disks from VMD bus as they are currently without this fix, so the
risk here should be justified.
== Previous SRU ==
[SRU Justification]
[Impact]
When booting with a certain platforms with boot disk attached to SATA
bus behind Intel VMD controller, disk probing may fail with following
error messages left in dmesg:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Fix]
Proposed kernel patch https://patchwork.kernel.org/patch/11758345/
[Test Case]
Check dmesg/lsblk for disk probe.
For pci MSI address, check lspci output:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0 Data:
When it fails, the address is fee0. And with a patched kernel:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000 Data:
[Regression Potential]
Low. For previous NVMe based platforms, this patch brings no effective
change for NVMe devices because they will still stay in fast-interrupt
list.
== Original Bug Description ==
When booting with root filesystem on sata disks under Intel VMD mode,
following errors printed in dmesg and no disk is found, nor booting
into it:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 16.659284] ata1.00: qc timeout (cmd 0xec)
[ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps
[ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 48.147294] ata1.00: qc timeout (cmd 0xec)
[ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
$ lspci
...
1:e0:17.0 SATA controller: Intel Corporation Device a0d3 (rev 20)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1894778/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1894778
Title:
Cannot probe sata disk on sata controller behind VMD: ata1.00: failed
to IDENTIFY (I/O error, err_mask=0x4)
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Won't Fix
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
[SRU Justification]
[Impact]
When booting with a certain platforms with boot disk attached to SATA
bus behind Intel VMD controller, disk probing may fail with following
error messages left in dmesg:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Fix]
Upstream commit f6b7bb847ca8 ("PCI: vmd: Offset Client VMD MSI-X
vectors") currently in vanilla kernel tree for v5.11.
[Test Case]
Check dmesg/lsblk for disk probe.
For pci MSI address, check lspci output:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0 Data:
When it fails, the address is fee0. And with a patched kernel:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000 Data:
[Where problems could occur]
An unpatched kernel will not be able to probe SATA controllers moved
behind VMD when VMD/RAID mode is enabled in BIOS, leaving disks
attached on it completely unusable. With this change, kernel would
then be able to probe them but may also suffer from issues that only
occur under such configuration. However, the worst case is to move away
sata disks from VMD bus as they are currently without this fix, so the
risk here should be justified.
== Previous SRU ==
[SRU Justification]
[Impact]
When booting with a certain platforms with boot disk attached to SATA
bus behind Intel VMD controller, disk probing may fail with following
error messages left in dmesg:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Fix]
Proposed kernel patch https://patchwork.kernel.org/patch/11758345/
[Test Case]
Check dmesg/lsblk for disk probe.
For pci MSI address, check lspci output:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0 Data:
When it fails, the address is fee0. And with a patched kernel:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000 Data:
[Regression Potential]
Low. For previous NVMe based platforms, this patch brings no effective
change for NVMe devices because they will still stay in fast-interrupt
list.
== Original Bug Description ==
When booting with root filesystem on sata disks under Intel VMD mode,
following errors printed in dmesg and no disk is found, nor booting
into it:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 16.659284] ata1.00: qc timeout (cmd 0xec)
[ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps
[ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 48.147294] ata1.00: qc timeout (cmd 0xec)
[ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
$ lspci
...
1:e0:17.0 SATA controller: Intel Corporation Device a0d3 (rev 20)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1894778/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
I have tested it on my ASUS Laptop X513EQ with the kernel 5.8.0-42 and
now it detects the SATA hard drive without problem.
** Changed in: linux (Ubuntu Groovy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1894778
Title:
Cannot probe sata disk on sata controller behind VMD: ata1.00: failed
to IDENTIFY (I/O error, err_mask=0x4)
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Won't Fix
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
[SRU Justification]
[Impact]
When booting with a certain platforms with boot disk attached to SATA
bus behind Intel VMD controller, disk probing may fail with following
error messages left in dmesg:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Fix]
Upstream commit f6b7bb847ca8 ("PCI: vmd: Offset Client VMD MSI-X
vectors") currently in vanilla kernel tree for v5.11.
[Test Case]
Check dmesg/lsblk for disk probe.
For pci MSI address, check lspci output:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0 Data:
When it fails, the address is fee0. And with a patched kernel:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000 Data:
[Where problems could occur]
An unpatched kernel will not be able to probe SATA controllers moved
behind VMD when VMD/RAID mode is enabled in BIOS, leaving disks
attached on it completely unusable. With this change, kernel would
then be able to probe them but may also suffer from issues that only
occur under such configuration. However, the worst case is to move away
sata disks from VMD bus as they are currently without this fix, so the
risk here should be justified.
== Previous SRU ==
[SRU Justification]
[Impact]
When booting with a certain platforms with boot disk attached to SATA
bus behind Intel VMD controller, disk probing may fail with following
error messages left in dmesg:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[Fix]
Proposed kernel patch https://patchwork.kernel.org/patch/11758345/
[Test Case]
Check dmesg/lsblk for disk probe.
For pci MSI address, check lspci output:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0 Data:
When it fails, the address is fee0. And with a patched kernel:
$ lspci -vvnn
Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000 Data:
[Regression Potential]
Low. For previous NVMe based platforms, this patch brings no effective
change for NVMe devices because they will still stay in fast-interrupt
list.
== Original Bug Description ==
When booting with root filesystem on sata disks under Intel VMD mode,
following errors printed in dmesg and no disk is found, nor booting
into it:
[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 16.659284] ata1.00: qc timeout (cmd 0xec)
[ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps
[ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 48.147294] ata1.00: qc timeout (cmd 0xec)
[ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
$ lspci
...
1:e0:17.0 SATA controller: Intel Corporation Device a0d3 (rev 20)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1894778/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359803] Re: External mic not being used in combo port
This is the ultimate solution to suggest ubuntu include in future versions. It works for the specific model of the bug Asus 1015E, I've tried and I guess for other models of notebooks and laptops. No need of foreign configurations, only edit this file: Edit: /etc/modprobe.d/alsa-base.conf add options snd_hda_intel model=laptop-dmic ** Changed in: linux (Ubuntu) Assignee: (unassigned) = fabianbur (fabianbur) ** Changed in: linux (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359803 Title: External mic not being used in combo port Status in linux package in Ubuntu: In Progress Bug description: I'm using Ubuntu 14.04 on my Asus 1015E that only has a combo audio port which accepts smartphone type headsets (3.5mm TRRS headphones with mic on the same wire). Ubuntu does not deactivate the built-in mic when I connect my headset. It doesn't even use the headset mic and instead keeps picking up audio signal from the integrated microphone (that's on my laptop bezel). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: power-inside 4651 F pulseaudio Date: Thu Aug 21 20:24:20 2014 HibernationDevice: RESUME=UUID=d0a4bd33-50b7-419e-80da-efc7ad5b1247 InstallationDate: Installed on 2013-11-08 (286 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: ASUSTeK COMPUTER INC. 1015E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=0323822b-7902-4f91-bf79-2a91c47d7df5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-18 (124 days ago) dmi.bios.date: 03/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1015E.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 1015E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1015E.303:bd03/15/2013:svnASUSTeKCOMPUTERINC.:pn1015E:pvr1.0:rvnASUSTeKCOMPUTERINC.:rn1015E:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: 1015E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359803/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359803] Re: External mic not being used in combo port
It's the same with the same machine ** Changed in: linux (Ubuntu) Status: Incomplete = Opinion ** Changed in: linux (Ubuntu) Assignee: (unassigned) = fabianbur (fabianbur) ** Changed in: linux (Ubuntu) Status: Opinion = 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/1359803 Title: External mic not being used in combo port Status in “linux” package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 14.04 on my Asus 1015E that only has a combo audio port which accepts smartphone type headsets (3.5mm TRRS headphones with mic on the same wire). Ubuntu does not deactivate the built-in mic when I connect my headset. It doesn't even use the headset mic and instead keeps picking up audio signal from the integrated microphone (that's on my laptop bezel). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: power-inside 4651 F pulseaudio Date: Thu Aug 21 20:24:20 2014 HibernationDevice: RESUME=UUID=d0a4bd33-50b7-419e-80da-efc7ad5b1247 InstallationDate: Installed on 2013-11-08 (286 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: ASUSTeK COMPUTER INC. 1015E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=0323822b-7902-4f91-bf79-2a91c47d7df5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-18 (124 days ago) dmi.bios.date: 03/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1015E.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 1015E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1015E.303:bd03/15/2013:svnASUSTeKCOMPUTERINC.:pn1015E:pvr1.0:rvnASUSTeKCOMPUTERINC.:rn1015E:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: 1015E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359803/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1359803] Re: External mic not being used in combo port
** Changed in: linux (Ubuntu) Assignee: fabianbur (fabianbur) = (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1359803 Title: External mic not being used in combo port Status in “linux” package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 14.04 on my Asus 1015E that only has a combo audio port which accepts smartphone type headsets (3.5mm TRRS headphones with mic on the same wire). Ubuntu does not deactivate the built-in mic when I connect my headset. It doesn't even use the headset mic and instead keeps picking up audio signal from the integrated microphone (that's on my laptop bezel). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: power-inside 4651 F pulseaudio Date: Thu Aug 21 20:24:20 2014 HibernationDevice: RESUME=UUID=d0a4bd33-50b7-419e-80da-efc7ad5b1247 InstallationDate: Installed on 2013-11-08 (286 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: ASUSTeK COMPUTER INC. 1015E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=0323822b-7902-4f91-bf79-2a91c47d7df5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-18 (124 days ago) dmi.bios.date: 03/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1015E.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 1015E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1015E.303:bd03/15/2013:svnASUSTeKCOMPUTERINC.:pn1015E:pvr1.0:rvnASUSTeKCOMPUTERINC.:rn1015E:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: 1015E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359803/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
