You are not logged in.
Hi
After updating to Kernel 4.8.x, I get error messages during shutdown and startup, mainly the following
1)
[ 1.167501] BERT: Can't request iomem region <00000000ca7ffd18-00000000ca7ffd2b>
2) This one doesn't show up in dmesg so I try to write down what's on the screen during shutdown:
ata2.00: revalidation failed (errno=-5)
ata2.00: ACPI cmd 00/00:00:00:00:00:b0 failed (Emask=0x4 Stat=0x00 Err=0x01)
(these are not the correct values but just that you have an idea of what is displayed)
Does anybody know what this is about? As I said, nothing to be found with dmesg | grep ata2...
Last edited by i716 (2017-01-02 05:03:40)
Offline
https://lkml.org/lkml/headers/2016/7/11/802
https://patchwork.kernel.org/patch/6353191/
BERT is likely falsely announced by your system?
Offline
@seth
Thanks. I have indeed updated the BIOS, almost at the same time when I updated to Kernel v. 4.8.x. Here are some information about my BIOS
# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: Dell Inc.
Version: A19
Release Date: 05/17/2016
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 12288 kB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Function key-initiated network boot is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 4.6
But this is just an error message which doesn't seem to really affect the boot process. The second error however causes severe delay during shutdown.
Offline
I get that BERT error on one of my systems too. It started appearing with the 4.8.X kernels. It seems safe to ignore, so I am.
Offline
The ata error can have many causes, first step is to "cat /proc/scsi/scsi" to determine which device is affected (scsi1 - iff the "not so exact number is actually ata2 ;-)
Could be eg. some usb key or a dvd - or actually your hard drive or whatnot.
In case it's the root device, "something" may attempt a late write (after the scsi subsystem is gone) - or the drive is damages (check smartmontools, but it's not the likely cause)
Offline
@ukhippo: Thanks for the information!
@seth: cat /proc/scsi/scsi correctly lists the two devices connected to the SATA bus:
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: WDC WD10EZEX-75Z Rev: 0A80
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: HL-DT-ST Model: DVD+-RW GTA0N Rev: A100
Type: CD-ROM ANSI SCSI revision: 05
A scsi1 file doesn't exist within the /proc/scsi folder. As for the smart test, the results are all fine!
And since these errors don't appear in any log, I did take a picture of the screen during shutdown and wrote part of what's showing up down:
[104299.975433] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[104299.975530] ata2.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 3 pio 16392 in
[104299.975530] opcode=0x4a 4a 01 00 00 10 00 00 00 08 00res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
[104299.975699] ata2.00: status: { DRDY }
[104305.295192] ata2.00: revalidation failed (errno=-5)
... ... ...
then almost the same for ata1.00 with two additional error messages:
ata1: COMRESET failed (errno=-16) (this one twice)
This error doesn't seem to affect the systems usability but it freezes the system for almost 2 minutes during shutdown.
Last edited by i716 (2016-11-03 04:29:34)
Offline
ata2 is your DvD drive, leaving ata1 aside for a moment: do you have a disc in there?
Offline
no disc in the drive
Offline
Though we lack context of the DRDY, this might be similar to/same as https://bbs.archlinux.org/viewtopic.php?id=218781
Do you have "lsmod | grep sp5100_tco"?
Offline
First of all sorry for the late reply but I have been quite busy recently.
I can definitely say, that these errors are not specific to my Arch installation, but they also appear when booting with the Arch installation CD/USB.
When using a different OS however, they don't show up (tested with a live USB of Ubuntu)
So it either must be related to Arch or the new Linux 4.8 kernel. Anyways, it is quite annoying, as the above errors delay shutdown by almost 3 minutes.
@seth: lsmod | grep sp5100_tco doesn't report anything back
UPDATE: I can confirm that all of the above mentioned errors are solely related to the 4.8 Kernel. I have booted with Arch-LTS and everything was fine.
As for me, I will keep on using LTS until the issue gets fixed upstream. If the others agree, I will mark this as solved.
Last edited by i716 (2016-11-21 05:24:39)
Offline
I can now officially mark this issue as solved:
Regarding the harmless BERT error: Add "bert_disable" to the Kernel and it'll be gone.
For the other rather time consuming error messages, you can either run a Kernel below 4.8 as mentioned in my previous post, OR you can perform a BIOS downgrade and use Kernel 4.8 and up. Your choice.
Last edited by i716 (2017-01-02 05:03:22)
Offline
UPDATE 2017/3/4: The issue might have been caused by Windows 10 which had quick boot feature activated. I have disabled it and updated the BIOS back to the latest version and the error message is still not displayed.
Offline