Changes between Initial Version and Version 2 of Ticket #18885


Ignore:
Timestamp:
Apr 9, 2024, 3:59:07 PM (8 months ago)
Author:
davidkaroly
Comment:

ehh sorry I stand corrected, it happened in Hyper-V, not VMware.

Anyway, probably I also deleted the download folder so the panic could have happened during re-downloading the source tarball.

idk does this make more sense like this? e.g. the file system using some kind of buffers and therefore at a later point the network stack runs out of resources?

I saw this happening a few times, every time after heavy file system usage. If I reboot the VM and then re-run the build (possibly including a wget download) I don't get any panic.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #18885

    • Property Component System/KernelDrivers/Network
    • Property Priority highnormal
  • Ticket #18885 – Description

    initial v2  
    99Screenshot: tbd, unfortunately I didn't create one. It will take some time to trigger this again.
    1010
    11 I saw this on recent hrevs e.g. hrev57667 in VMware Player.
     11I saw this on recent hrevs e.g. hrev57667 in Hyper-V.
    1212Seems to happen both on 32-bit and 64-bit.