On 08/01/17 11:57, Arno Wagner wrote:
> Maybe your disk is dying or your CPU is inadequately cooled?
> Or there is something else putting high load on your machine?
It really doesn't seem that one of these is the case, I performed these
steps without any other open programs: After completely wiping the hard
disk with the other method, I retried opening it with a random key in
cryptsetup
cryptsetup open --type plain -d /dev/urandom /dev/sdX sdX_wipe
and then overwriting it again
pv /dev/zero > /dev/mapper/sdX_wipe
and after a couple of seconds, the computer locked up again. Does
someone know how to debug this?
These dmesg entries look suspicious:
Aug 01 22:05:27 kernel: ata_piix 0000:00:1f.2: swiotlb buffer is full
(sz: 61440 bytes)
Aug 01 22:05:27 kernel: ata_piix 0000:00:1f.2: DMA: Out of SW-IOMMU
space for 61440 bytes
Aug 01 22:05:27 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0
action 0x0
Aug 01 22:05:27 kernel: ata1.00: failed command: READ DMA EXT
Aug 01 22:05:27 kernel: ata1.00: cmd 25/00:00:50:f5:53/00:01:bd:00:00/e0
tag 0 dma 131072 in
res 50/00:00:4f:c1:3b/00:00:b8:00:00/e0
Emask 0x40 (internal error)
Aug 01 22:05:27 kernel: ata1.00: status: { DRDY }
Aug 01 22:05:27 kernel: ata1.00: configured for UDMA/133
Aug 01 22:05:27 kernel: ata1: EH complete
Aug 01 22:05:27 kernel: ata_piix 0000:00:1f.2: swiotlb buffer is full
(sz: 61440 bytes)
Aug 01 22:05:27 kernel: ata_piix 0000:00:1f.2: DMA: Out of SW-IOMMU
space for 61440 bytes
Aug 01 22:05:27 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0
action 0x0
Aug 01 22:05:27 kernel: ata1.00: failed command: READ DMA EXT
Aug 01 22:05:27 kernel: ata1.00: cmd 25/00:00:50:f5:53/00:01:bd:00:00/e0
tag 0 dma 131072 in
res 50/00:00:af:88:e0/00:00:e8:00:00/e0
Emask 0x40 (internal error)
Aug 01 22:05:27 kernel: ata1.00: status: { DRDY }
[... a lot of repetitions of this]
Thanks
_______________________________________________
dm-crypt mailing list
dm-crypt@xxxxxxxx
http://www.saout.de/mailman/listinfo/dm-crypt
