[SOLVED] ACPI error

[thenemesis584]

Hello everyone,

I have problem with my Proxmox and need to reboot machine, sometimes I need to hard reset. Computer works for 2 or 3 days and then the same problem occurs.

Here is part of log

ACPI Error: [_SB_.PCI0.RP05.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload2-191)
[ 0.048483] No Local Variables are initialized for Method [PXSX]
[ 0.048484] No Arguments are initialized for method [PXSX]
[ 0.048485] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170831/psobject-252)
[ 0.048489] ACPI Error: Method parse/execution failed \_SB.PCI0.RP04.PXSX, AE_NOT_FOUND (20170831/psparse-550)
[ 0.049662] ACPI Error: [_SB_.PCI0.RP09.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload2-191)
[ 0.049668] No Local Variables are initialized for Method [PXSX]
[ 0.049668] No Arguments are initialized for method [PXSX]
[ 0.049669] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170831/psobject-252)
[ 0.049672] ACPI Error: Method parse/execution failed \_SB.PCI0.RP08.PXSX, AE_NOT_FOUND (20170831/psparse-550)
[ 0.050656] ACPI Error: [_SB_.PCI0.RP13.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload2-191)
[ 0.050661] No Local Variables are initialized for Method [PXSX]
[ 0.050662] No Arguments are initialized for method [PXSX]
[ 0.050663] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170831/psobject-252)
[ 0.050666] ACPI Error: Method parse/execution failed \_SB.PCI0.RP12.PXSX, AE_NOT_FOUND (20170831/psparse-550)
[ 0.057410] ACPI Error: [\_SB_.PCI0.RP05.PXSX.WIST] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
[ 0.057410] No Local Variables are initialized for Method [CNDP]
[ 0.057410] No Arguments are initialized for method [CNDP]
[ 0.057410] ACPI Error: Method parse/execution failed \CNDP, AE_NOT_FOUND (20170831/psparse-550)
[ 0.057410] ACPI Error: Method parse/execution failed \, AE_NOT_FOUND (20170831/psparse-550)

there were an error for I/O
I've run test with smartctl -t long -a /dev/sda and no errors
Also I've upgraded kernel to the latest version.

I'm using ordinary computer:

Intel core I5-8400
ASUS Prime B360-Plus
4x8GB DDR4 Kingston 2666Mhz
SSD Kingston A400 480GB
Proxmox 5.3-8

I have more computers like this one and never had similar problem.

Also, there are 12 VMs that are running CentOS 6.
Could this be motherboard fault? This machine is assembled in March this year, so basically it's new

Can someone help with this? Sorry for my poor english

 

[Chris]

Hi,
is your BIOS up to date? Please flash the latest firmware if not and see if this resolves some issues https://www.asus.com/us/Motherboards/PRIME-B360-PLUS/HelpDesk_BIOS/

 

[thenemesis584]

Thanks for response. I thought about update BIOS but not sure will it help.
I will try with BIOS update.

I have also found this logs

[98846.565550] sd 3:0:0:0: [sda] tag#22 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98846.565552] sd 3:0:0:0: [sda] tag#22 CDB: Read(10) 28 00 35 14 6f d8 00 00 08 00
[98846.565553] print_req_error: I/O error, dev sda, sector 890531800
[98846.565803] device-mapper: thin: process_cell: dm_thin_find_block() failed: e rror = -5
[98848.617729] sd 3:0:0:0: [sda] tag#23 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98848.617732] sd 3:0:0:0: [sda] tag#23 CDB: Read(10) 28 00 35 14 6e 88 00 00 08 00
[98848.617733] print_req_error: I/O error, dev sda, sector 890531464
[98848.618017] device-mapper: thin: process_cell: dm_thin_find_block() failed: e rror = -5
[98848.618493] sd 3:0:0:0: [sda] tag#24 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98848.618494] sd 3:0:0:0: [sda] tag#24 CDB: Read(10) 28 00 35 14 6e 88 00 00 08 00
[98848.618495] print_req_error: I/O error, dev sda, sector 890531464
[98848.618784] device-mapper: thin: process_cell: dm_thin_find_block() failed: e rror = -5
[98848.688347] sd 3:0:0:0: [sda] tag#25 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98848.688350] sd 3:0:0:0: [sda] tag#25 CDB: Read(10) 28 00 35 14 6e 88 00 00 08 00
[98848.688351] print_req_error: I/O error, dev sda, sector 890531464
[98848.688668] device-mapper: thin: process_cell: dm_thin_find_block() failed: e rror = -5
[98848.689149] sd 3:0:0:0: [sda] tag#26 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98848.689151] sd 3:0:0:0: [sda] tag#26 CDB: Read(10) 28 00 35 14 6e 88 00 00 08 00
[98848.689152] print_req_error: I/O error, dev sda, sector 890531464
[98848.689481] device-mapper: thin: process_cell: dm_thin_find_block() failed: e rror = -5
[98848.748574] sd 3:0:0:0: [sda] tag#27 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98848.748576] sd 3:0:0:0: [sda] tag#27 CDB: Read(10) 28 00 35 14 6e 88 00 00 08 00
[98848.748577] print_req_error: I/O error, dev sda, sector 890531464
[98848.748959] device-mapper: thin: process_cell: dm_thin_find_block() failed: e rror = -5
[98848.750243] sd 3:0:0:0: [sda] tag#28 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98848.750245] sd 3:0:0:0: [sda] tag#28 CDB: Read(10) 28 00 35 13 b8 68 00 00 08 00
[98848.750246] print_req_error: I/O error, dev sda, sector 890484840
[98848.750637] device-mapper: thin: process_cell: dm_thin_find_block() failed: e

 

[LnxBil]

Thanks for response. I thought about update BIOS but not sure will it help.
I will try with BIOS update.

I have also found this logs

[98846.565550] sd 3:0:0:0: [sda] tag#22 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98846.565552] sd 3:0:0:0: [sda] tag#22 CDB: Read(10) 28 00 35 14 6f d8 00 00 08 00
[98846.565553] print_req_error: I/O error, dev sda, sector 890531800
[98846.565803] device-mapper: thin: process_cell: dm_thin_find_block() failed: e rror = -5
[98848.617729] sd 3:0:0:0: [sda] tag#23 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98848.617732] sd 3:0:0:0: [sda] tag#23 CDB: Read(10) 28 00 35 14 6e 88 00 00 08 00
[98848.617733] print_req_error: I/O error, dev sda, sector 890531464
[98848.618017] device-mapper: thin: process_cell: dm_thin_find_block() failed: e rror = -5
[98848.618493] sd 3:0:0:0: [sda] tag#24 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98848.618494] sd 3:0:0:0: [sda] tag#24 CDB: Read(10) 28 00 35 14 6e 88 00 00 08 00
[98848.618495] print_req_error: I/O error, dev sda, sector 890531464
[98848.618784] device-mapper: thin: process_cell: dm_thin_find_block() failed: e rror = -5
[98848.688347] sd 3:0:0:0: [sda] tag#25 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98848.688350] sd 3:0:0:0: [sda] tag#25 CDB: Read(10) 28 00 35 14 6e 88 00 00 08 00
[98848.688351] print_req_error: I/O error, dev sda, sector 890531464
[98848.688668] device-mapper: thin: process_cell: dm_thin_find_block() failed: e rror = -5
[98848.689149] sd 3:0:0:0: [sda] tag#26 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98848.689151] sd 3:0:0:0: [sda] tag#26 CDB: Read(10) 28 00 35 14 6e 88 00 00 08 00
[98848.689152] print_req_error: I/O error, dev sda, sector 890531464
[98848.689481] device-mapper: thin: process_cell: dm_thin_find_block() failed: e rror = -5
[98848.748574] sd 3:0:0:0: [sda] tag#27 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98848.748576] sd 3:0:0:0: [sda] tag#27 CDB: Read(10) 28 00 35 14 6e 88 00 00 08 00
[98848.748577] print_req_error: I/O error, dev sda, sector 890531464
[98848.748959] device-mapper: thin: process_cell: dm_thin_find_block() failed: e rror = -5
[98848.750243] sd 3:0:0:0: [sda] tag#28 FAILED Result: hostbyte=DID_BAD_TARGET d riverbyte=DRIVER_OK
[98848.750245] sd 3:0:0:0: [sda] tag#28 CDB: Read(10) 28 00 35 13 b8 68 00 00 08 00
[98848.750246] print_req_error: I/O error, dev sda, sector 890484840
[98848.750637] device-mapper: thin: process_cell: dm_thin_find_block() failed: e

That looks like a faulty disk.

 

[thenemesis584]

Yes, it does look, but still not sure if that's the problem. Machine is working for about 3 days and then this happens.

I'm still new to linux so it's a bit difficult for me to explain in more details.

When machine "freezes" this log for I/O occurs, I can't type anything because it is writing constantly, so the only way to stop it is to hard reset machine.

I will try with BIOS update but I don't think it will help. I think that the problem is ssd or in motherboard itself, and only way to find out is to replace ssd and see what will happen.

Or maybe is problem in power supply, maybe power supply is week and in one moment can't deliver enough of power.

This problem is very complicated, never saw anything like it.

 

[thenemesis584]

Hello again.

So, 10 days ago I updated bios to the newest version and from then I didn't encountered any problem.
For now this is working.

Still, I don't know what truly caused the problem with ACPI since the motherboard is new and working since march.

So, if any of you encounter the same problem just update bios to the newest version, it should solve the porblem.

Thanks everyone for help.

 

[Chris]

Glad you are up and running without issues now. Please mark the thread as solved for others to ease the search.

 

[thenemesis584]

Hey guys, I have new info about this problem.

So, it wasn't the problem in BIOS, it was in the SSD.
I found out that the writing speed of ssd is not as the vendor says (480GB to 500MB/s Read and 450MB/s Write)

I've tested it with crystal disk info and the writing speed was about 250MB/s writing. I did a little research on the internet and found out that vendor says that this is some bug in there firmware. In order to upgrade it, need to install their software which is written only for windows and also it will destroy your data.

So, I did that, but didn't test it again, no time for that.

Just wanna to say, if someone having this issues like me, don't use Kingstons cheap ssd's if you have a lot of writing on the drive, use Samsung Evo 860 or other (I'm using Evo 860 on 7 different machines, 24h writing a lot of data, never had the problem with any of it).