| View previous topic :: View next topic |
| Author |
Message |
andyr7
n00b
Joined: 27 Nov 2017
Posts: 23
Location: ::1
|
 Posted: Sun Nov 07, 2021 11:25 am Post subject: ATA kernel upgrade error (5.14.15 -> 5.15) |
 |
|
Hi guys!
Just a quick question,
After kernel upgrade from 5.14.15 -> 5.15 I got the following messages from kernel before the OpenRC starts:
| Code: |
andreas@gentoo ~ $ dmesg | grep -i fail
[ 1.302355] ata2.00: Read log page 0x08 failed, Emask 0x1
[ 1.303024] ata2.00: Read log page 0x08 failed, Emask 0x1
[ 3.849056] r8169 0000:04:00.0: Direct firmware load for rtl_nic/rtl8168h-2.fw failed with error -2
andreas@gentoo ~ $
|
Note that in grub I load the kernel with parameters "ro quiet"
Do you have any idea what is this - how can I correct it?
Thank you in advance for your support,
Andreas |
|
| Back to top |
|
 |
Marlo
Veteran
Joined: 26 Jul 2003
Posts: 1591
|
| Posted: Sun Nov 07, 2021 8:16 pm Post subject: |
|
|
If ata2 is an NTFS drive, then the error message is new and related to the new ntfs3 kernel driver.
I think this is harmless but may be wrong of course.
I don't have a Realtek but try making the r8169 driver as a module. So that the firmware has enough time to be loaded.
_________________
------------------------------------------------------------------
http://radio.garden/ |
|
| Back to top |
|
|
CaptainBlood
Advocate
Joined: 24 Jan 2010
Posts: 3998
|
| Posted: Sun Nov 07, 2021 8:37 pm Post subject: |
|
|
In both 5.15.0 & 5.15.1 | Code: | amd64 ~ # dmesg | grep -i fail
[ 0.730264] ata3.00: Read log page 0x08 failed, Emask 0x1
[ 0.738101] ata3.00: Read log page 0x08 failed, Emask 0x1 |
where drive is Sata II & kernel NTFS is activated.
No idea what's happening there.
Thks 4 ur attention, interest & support.
_________________
USE="-* ..." in /etc/portage/make.conf here, i.e. a countermeasure to portage implicit braces, belt & diaper paradigm
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. " |
|
| Back to top |
|
|
CaptainBlood
Advocate
Joined: 24 Jan 2010
Posts: 3998
|
| Posted: Mon Nov 08, 2021 7:34 am Post subject: |
|
|
Cancelling new kerneldidn't help there.
Likely to be a warning only here.
Message removal is prefered here...
Failed trying to remove ata3 msg using | Code: | | Device Drivers/CONFIG_ATA/CONFIG_ATA_FORCE=y providing libata.force= |
kernel command line param, which I'm new at, so no surprise if I've missed up param value definition, should message cancellation be achievable that way  .
Sata II disk on Sata III capable mb controller.
Thks 4 ur attention, interest & support.
_________________
USE="-* ..." in /etc/portage/make.conf here, i.e. a countermeasure to portage implicit braces, belt & diaper paradigm
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. " |
|
| Back to top |
|
|
andyr7
n00b
Joined: 27 Nov 2017
Posts: 23
Location: ::1
|
| Posted: Mon Nov 08, 2021 6:37 pm Post subject: |
|
|
| CaptainBlood wrote: | Cancelling new kerneldidn't help there.
Likely to be a warning only here.
Message removal is prefered here...
Failed trying to remove ata3 msg using | Code: | | Device Drivers/CONFIG_ATA/CONFIG_ATA_FORCE=y providing libata.force= |
kernel command line param, which I'm new at, so no surprise if I've missed up param value definition, should message cancellation be achievable that way .
Sata II disk on Sata III capable mb controller.
Thks 4 ur attention, interest & support. |
Indeed canceling CONFIG_NTFS3_FS didn't help..
At least, I can hide this annoying error by using loglevel=0 on grub params. |
|
| Back to top |
|
|
|
Kernel & Hardware
