virtualbox.org

End user forums for VirtualBox
https://forums.virtualbox.org/

AHCI#0: Port 0 reset

https://forums.virtualbox.org/viewtopic.php?t=96051

Page 1 of 1

AHCI#0: Port 0 reset

Posted: 17. Dec 2019, 19:29
by Konstigt
Hello

I have a Win 10 guest which is not working OK. I found that every time it locks up, I get this in the log: 
17:19:45.493616 00:00:02.602955 AHCI#0: Port 0 reset
17:19:45.493658 00:00:02.602998 VD#0: Cancelling all active requests
After a while it's OK again. Doesn't reboot or anything like that but it is completely inaccessible.

I'm not sure where to start to troubleshoot this further?

Full VBox.log: [ModEdit; Link to log-in service removed]

Re: AHCI#0: Port 0 reset

Posted: 18. Dec 2019, 14:45
by Konstigt
I also get this, don't know if it's related: 
11:56:41.368792 17:15:35.173258 VMMDev: Guest Log: VBOXNP: DLL unloaded.
11:56:41.370468 17:15:35.174919 VMMDev: Guest Log: VBOXNP: DLL loaded.
A new VBox.log below. The VM has been running between 18:41 yesterday until now, 13:45.

[ModEdit; Link to log-in service removed]

Re: AHCI#0: Port 0 reset

Posted: 18. Dec 2019, 14:49
by scottgus1
While I'm not entirely certain how we could troubleshoot this, I am certain that you need to zip and post your logs here using the forum's Upload Attachment tab. Most forum gurus won't go to 3rd-party sites for logs or screenshots.

Re: AHCI#0: Port 0 reset

Posted: 18. Dec 2019, 15:17
by socratis
I actually removed the links from https://paste.ubuntu.com/
I will not let such links stand, that actually want me to log-in to Ubuntu before I can download the raw text... :roll:
I do have an account, but this isn't about what *I* have, it's about what the rest of the users might not have...

Re: AHCI#0: Port 0 reset

Posted: 19. Dec 2019, 16:36
by Konstigt
Wow, that sucks. I'm not using that service again.

Here as an attachment instead:
VBox.log.1.gz
(37.07 KiB) Downloaded 12 times
It seems I only get this port reset one time, always about 11 minutes after the boot of the VM actually. So it isn't really a big problem.

The second thing, I'm not sure if that's an issue or not? This happens every now and then (maybe 4-5 times per 24hrs) 
11:49:46.243138 02:07:12.281463 VMMDev: Guest Log: VBOXNP: DLL unloaded.
11:49:46.269952 02:07:12.308318 VMMDev: Guest Log: VBOXNP: DLL loaded.
What I experience as a real problem though is that my network (via bridged adapter) totally drops the connection. If I do a ping from the Win 10 Guest to the Host on the bridged interface + a ping towards localhost, ping to the host fails regularly but the ping to localhost never stops working. So from this I gather that the VM doesn't stop.. it's just the networking. And this does not happen the same time as the DLL unloaded/loaded messages. I don't see anything in the log when this happens.

Code: Select all

<snip>

Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64
Reply from 10.0.0.254: bytes=32 time<1ms TTL=64

Ping statistics for 10.0.0.254:
    Packets: Sent = 976, Received = 921, Lost = 55 (5% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 2ms, Average = 0ms
Control-C
^C

Code: Select all

<snip>

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
    Packets: Sent = 653, Received = 653, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
Control-C
^C
All times are UTC+02:00
Page 1 of 1

Powered by phpBB® Forum Software © phpBB Limited