Opened 8 months ago
Last modified 7 weeks ago
#18885 new bug
panic: bounce buffer already in use! — at Version 2
| Reported by: | davidkaroly | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | Drivers/Network | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description (last modified by )
Got this panic while building llvm18. It seems to happen after heavy usage of the file system, with lots of small files.
Steps to reproduce looks something like this:
- build llvm18 with haikuporter
- delete the work directory:
rm -rf work-18.1.2 - start the build again.
- we get a panic
Screenshot: tbd, unfortunately I didn't create one. It will take some time to trigger this again.
I saw this on recent hrevs e.g. hrev57667 in Hyper-V. Seems to happen both on 32-bit and 64-bit.
Change History (2)
comment:1 by , 8 months ago
| Component: | System/Kernel → Drivers/Network |
|---|---|
| Priority: | high → normal |
comment:2 by , 8 months ago
| Description: | modified (diff) |
|---|
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.
Seems odd this would happen on heavy filesystem usage, because the message comes from the DMA code in the FreeBSD network compatibility layer.