In message [EMAIL PROTECTED], Kris Kennaway writes:
I just got the following on axp1:
panic: malloc(M_WAITOK) returned NULL
db_print_backtrace() at db_print_backtrace+0x18
panic() at panic+0x104
malloc() at malloc+0x1a8
initiate_write_inodeblock_ufs1() at initiate_write_inodeblock_ufs1+0xc4
On Sat, 2003/01/18 at 09:00:39 +0100, [EMAIL PROTECTED] wrote:
In message [EMAIL PROTECTED], Kris Kennaway writes:
I just got the following on axp1:
panic: malloc(M_WAITOK) returned NULL
db_print_backtrace() at db_print_backtrace+0x18
panic() at panic+0x104
malloc() at malloc+0x1a8
On Sat, 2003/01/18 at 13:22:45 +0100, Thomas Moestl wrote:
None of the two could have caused this panic. I would guess that it
was caused by the alpha uma_small_alloc() implementation trying less
hard to allocate a page than kmem_alloc() (i.e. it does not sleep at
all). This problem does also
On Fri, Jan 17, 2003 at 08:53:16PM -0800, Kris Kennaway wrote:
I just got the following on axp1:
I forgot to add that the machine was under heavy load at the time it
panicked (14 simultaneous package builds), so this could well have
been due to a low memory condition.
Kris
I just got the following on axp1:
panic: malloc(M_WAITOK) returned NULL
db_print_backtrace() at db_print_backtrace+0x18
panic() at panic+0x104
malloc() at malloc+0x1a8
initiate_write_inodeblock_ufs1() at initiate_write_inodeblock_ufs1+0xc4
softdep_disk_io_initiation
