From: HiPhish <HiPhish@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: linux-firmware-network-20230804_1: [unpack] failed to unpack files from archive
Date: Thu, 14 Sep 2023 15:33:55 +0200 [thread overview]
Message-ID: <20230914133355.cybAKJ7If9lixrlql6UjK050w25V3Uly-IVsJIr6kak@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46054@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1692 bytes --]
New comment by HiPhish on void-packages repository
https://github.com/void-linux/void-packages/issues/46054#issuecomment-1719462892
Comment:
Using `dmesg` gives me the following output which keeps repeating:
```
[11372.657063] ata2.00: configured for UDMA/133
[11372.657146] sd 1:0:0:0: [sda] tag#19 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
[11372.657150] sd 1:0:0:0: [sda] tag#19 Sense Key : 0x3 [current]
[11372.657152] sd 1:0:0:0: [sda] tag#19 ASC=0x11 ASCQ=0x4
[11372.657154] sd 1:0:0:0: [sda] tag#19 CDB: opcode=0x28 28 00 0e 45 8c c0 00 00 08 00
[11372.657156] I/O error, dev sda, sector 239439044 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[11372.657166] ata2: EH complete
[11372.725125] ata2.00: exception Emask 0x0 SAct 0x400000 SErr 0x0 action 0x0
[11372.725132] ata2.00: irq_stat 0x40000008
[11372.725135] ata2.00: failed command: READ FPDMA QUEUED
[11372.725137] ata2.00: cmd 60/08:b0:c0:8c:45/00:00:0e:00:00/40 tag 22 ncq dma 4096 in
res 41/40:00:c4:8c:45/00:00:0e:00:00/00 Emask 0x409 (media error) <F>
[11372.725145] ata2.00: status: { DRDY ERR }
[11372.725147] ata2.00: error: { UNC }
[11372.732179] ata2.00: configured for UDMA/133
[11372.732251] sd 1:0:0:0: [sda] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
[11372.732254] sd 1:0:0:0: [sda] tag#22 Sense Key : 0x3 [current]
[11372.732256] sd 1:0:0:0: [sda] tag#22 ASC=0x11 ASCQ=0x4
[11372.732259] sd 1:0:0:0: [sda] tag#22 CDB: opcode=0x28 28 00 0e 45 8c c0 00 00 08 00
[11372.732260] I/O error, dev sda, sector 239439044 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[11372.732270] ata2: EH complete
```
next prev parent reply other threads:[~2023-09-14 13:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 7:41 [ISSUE] " HiPhish
2023-09-14 7:51 ` classabbyamp
2023-09-14 7:54 ` HiPhish
2023-09-14 7:56 ` classabbyamp
2023-09-14 7:56 ` classabbyamp
2023-09-14 12:47 ` HiPhish
2023-09-14 13:00 ` Duncaen
2023-09-14 13:03 ` HiPhish
2023-09-14 13:06 ` Duncaen
2023-09-14 13:07 ` Anachron
2023-09-14 13:14 ` HiPhish
2023-09-14 13:17 ` Duncaen
2023-09-14 13:19 ` Duncaen
2023-09-14 13:31 ` HiPhish
2023-09-14 13:33 ` HiPhish [this message]
2023-09-14 13:47 ` Duncaen
2023-09-15 11:51 ` HiPhish
2023-09-15 16:54 ` Anachron
2023-09-15 19:19 ` HiPhish
2023-09-16 15:44 ` Anachron
2023-09-16 15:45 ` Anachron
2023-09-16 15:46 ` Anachron
2023-09-20 17:05 ` [ISSUE] [CLOSED] " HiPhish
2023-09-20 17:05 ` HiPhish
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=20230914133355.cybAKJ7If9lixrlql6UjK050w25V3Uly-IVsJIr6kak@z \
--to=hiphish@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).