Hello!
I'm using proxmox for over 1 decade on my HP Microserver Gen8. This machine have a known problem with the iommu that it's broken. 3 or 4 years ago i found that the pve kernel have a patch to enable
and it's working fine since.
Following all the vulnerabilities that have come out this days i update my server and i saw that a new 7.0.2 kernel was installed. With this kernel my machine have constant 100% wait-io and it's inoperable.
Have the patches on kernel 7.0 been removed?
HI,
you could pin the old kernel and report a bug (if before it was a native kernel without modifications).
Is the mentioned patch was from here?
Could you clarify what kernel was installed before?
Is it was custom kernel or just custom options in a standard one?
Could you share a system report, dmesg and journal output or at least specific errors?
Could you provide more details about hardware?
Last edited:
Same issue here. I got a repeated DMA error on /dev/sde (the disk on the CD-ROM slot) and switch back to the 6.17 fixed this issue.
Hardware is the Gen8 Microserver, which is a very old model of small home server, and a intel SSD on the CD rom slot as ata3.00
Jun 18 00:01:44 esxi kernel: I/O error, dev sde, sector 2099200 op 0x0
READ) flags 0x0 phys_seg 32 prio class 2
Jun 18 00:01:44 esxi kernel: ata3: EH complete
Jun 18 00:01:44 esxi kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jun 18 00:01:44 esxi kernel: ata3.00: failed command: READ DMA
Jun 18 00:01:44 esxi kernel: ata3.00: cmd c8/00:00:00:00:00/00:00:00:00:00/e0 tag 0 dma 131072 in
res 50/00:00:30:01:80/00:00:00:00:00/a0 Emask 0x40 (internal error)
Jun 18 00:01:44 esxi kernel: ata3.00: status: { DRDY }
Jun 18 00:01:44 esxi kernel: ata3.00: configured for UDMA/133
Jun 18 00:01:44 esxi kernel: ata3: EH complete
Jun 18 00:01:44 esxi kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jun 18 00:01:44 esxi kernel: ata3.00: failed command: READ DMA
Jun 18 00:01:44 esxi kernel: ata3.00: cmd c8/00:00:00:00:00/00:00:00:00:00/e0 tag 0 dma 131072 in
res 50/00:00:30:01:80/00:00:00:00:00/a0 Emask 0x40 (internal error)
Jun 18 00:01:44 esxi kernel: ata3.00: status: { DRDY }
Jun 18 00:01:44 esxi kernel: ata3.00: configured for UDMA/133
Jun 18 00:01:44 esxi kernel: ata3: EH complete
Jun 18 00:01:44 esxi kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jun 18 00:01:44 esxi kernel: ata3.00: failed command: READ DMA
Jun 18 00:01:44 esxi kernel: ata3.00: cmd c8/00:00:00:00:00/00:00:00:00:00/e0 tag 0 dma 131072 in
res 50/00:00:30:01:80/00:00:00:00:00/a0 Emask 0x40 (internal error)
Jun 18 00:01:44 esxi kernel: ata3.00: status: { DRDY }
Jun 18 00:01:44 esxi kernel: ata3.00: configured for UDMA/133
Jun 18 00:01:44 esxi kernel: ata3: EH complete
Jun 18 00:01:44 esxi kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jun 18 00:01:44 esxi kernel: ata3.00: failed command: READ DMA
Jun 18 00:01:44 esxi kernel: ata3.00: cmd c8/00:00:00:00:00/00:00:00:00:00/e0 tag 0 dma 131072 in
res 50/00:00:30:01:80/00:00:00:00:00/a0 Emask 0x40 (internal error)
The error log is very long, and I have no idea which parts help.
I'm testing to add it into grub attribute, no idea whether it helps.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
