From: "J.J. Berkhout" <j.j.berkhout@staalenberk.nl>
To: linux-ide@vger.kernel.org
Subject: Re: Multiple errors with DVD drive
Date: Tue, 20 Sep 2022 12:05:57 +0200 [thread overview]
Message-ID: <0baf58ab-4e7e-e8bf-d1e8-0897542d1bc6@staalenberk.nl> (raw)
In-Reply-To: <a4326505-f52b-7a7b-d626-a77fb546642e@staalenberk.nl>
[-- Attachment #1.1: Type: text/plain, Size: 2666 bytes --]
On 05-08-2022 11:17, J.J. Berkhout wrote:
Hello,
This morning I updated my motherboard (ASRock model X570 Taichi) from
UEFI v. 3.60 to UEFI 4.80. Update went perfectly, but did not solve the
problem with my optical drive. I am at a loss how to proceed next.
Any suggestions?
With kind regards,
Jaap Berkhout
> Hello,
>
> This morning I tried the 5.19 kernel from
> https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
>
> The result regarding the problem with my optical drive still exists.
>
> With kind regards,
>
> Jaap Berkhout.
>
> On 27-05-2022 12:32, J.J. Berkhout wrote:
>> Hello,
>>
>> On 27-05-2022 01:36, Damien Le Moal wrote:
>>> On 2022/05/26 21:38, J.J. Berkhout wrote:
>> .
>> .
>>>> The problem is:
>>>> After going from Linux Mint 19.3 Cinnamon kernel 5.4.0-97 to Linux Mint
>>>> 20.3 Cinnamon kernel 5.4.0-107 I discovered that I could not (reliably)
>>>> access my optical drive anymore.
>>>> It produces errors like:
>>>> ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x40d0000 action 0xe frozen
>>>> ata1: SError: { PHYRdyChg CommWake 10B8B DevExch }
>>>> ata1.00: cmd a0/00:00:00:00:fc/00:00:00:00:00/a0 tag 0 pio 131072 in
>>>> Read(10) 28 00 00 00 05 61 00 00 40 00res
>>>> 50/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA bus error)
>>>> blk_update_request: I/O error, dev sr0, sector 5508 op 0x0:(READ) flags
>>>> 0x80700 phys_seg 19 prio class 0
>>>> ata1.00: failed to set xfermode (err_mask=0x1)
>>>>
>>>> The system was Linux Mint 20.3 Cinnamon with kernel 5.4.0-107-generic,
>>>> mobo ASRock model X570 Taichi.
>>>> After some tests I found out:
>>>> Kernel 5.4.0-99 works OK;
>>>> Kernel 5.4.0-100 has the problem;
>>>> Kernel 5.13.0-30 works OK;
>>>> Kernel 5.13.0-35 has the problem.
>>>
>>> It looks like your distro is backporting patches so the patch causing the
>>> problem could be found by bisecting. While 5.4 kernel is an LTS kernel, the
>>> latest release is 5.4.196... 5.4.0-100 is the distro version number which does
>>> not tell me what set of patches it got on top of 5.4.0. These are not
>>> stable/vanilla kernels.
>>>
>>> To get help from this list, you will need to try with a vanilla kernel, ideally
>>> from git. You could try the latest mainline 5.18 first to see if the problem is
>>> there or not.
>>
>> OK, I installed kernel 5.18.0 with 'mainline' (Ubuntu Mainline Kernel
>> Installer).
>> Kernel installed was 5.18.0-051800.202205222030.
>> Same problem existed.
>> I reverted to the ubuntu 5.13.0-30 kernel.
>> A copy of the dmesg output is attached.
>>
>> With kind regards,
>>
>> Jaap Berkhout.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-09-20 11:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 12:38 Multiple errors with DVD drive J.J. Berkhout
2022-05-26 23:36 ` Damien Le Moal
2022-05-27 8:50 ` J.J. Berkhout
2022-05-27 10:32 ` J.J. Berkhout
2022-08-05 9:17 ` J.J. Berkhout
2022-09-20 10:05 ` J.J. Berkhout [this message]
2022-09-20 13:06 ` Niklas Cassel
[not found] ` <9756ac37-6790-7b83-5840-abe04f8ab838@staalenberk.nl>
2022-09-20 21:08 ` Niklas Cassel
2022-09-21 10:28 ` J.J. Berkhout
2022-09-21 11:58 ` Niklas Cassel
2022-09-21 12:38 ` J.J. Berkhout
2022-09-21 14:54 ` J.J. Berkhout
2022-09-21 18:32 ` Niklas Cassel
2022-09-26 12:59 ` J.J. Berkhout
2022-09-26 14:39 ` Niklas Cassel
2022-09-26 14:50 ` J.J. Berkhout
2022-09-22 22:08 ` Damien Le Moal
2022-09-23 12:07 ` J.J. Berkhout
2022-09-25 22:57 ` Damien Le Moal
2022-09-20 13:35 ` Niklas Cassel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0baf58ab-4e7e-e8bf-d1e8-0897542d1bc6@staalenberk.nl \
--to=j.j.berkhout@staalenberk.nl \
--cc=linux-ide@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox