In message <[EMAIL PROTECTED]>, Mark Santcroos writes:
>596: DEV_STRATEGY(bp);
>
>I don't understand what you want me to examine there as the arguments are
>not usefull anymore (or are they?).
Well that line in my copy was not code, so I just wanted to see what
your sources said.
>> >#15 0xc01
On Tue, Feb 11, 2003 at 12:21:19PM +0100, [EMAIL PROTECTED] wrote:
> >#14 0xc01edc00 in spec_xstrategy (vp=0xc23046c0, bp=0xc7502da8) at
>../../../fs/specfs/spec_vnops.c:596
>
> This doesn't correspond to my sourcefile, but you should examine this one.
Sorry, I should have do the backtrace on th
In message <[EMAIL PROTECTED]>, Mark Santcroos writes:
>While doing heavy IO (updating my p4 repo) on my laptop I got the following
>panic. (I was running in X so both backtrace and dmesg are from the core
>dump after reboot)
>
>I'm wondering whether the ENOMEM's reported by GEOM point out that GE
While doing heavy IO (updating my p4 repo) on my laptop I got the following
panic. (I was running in X so both backtrace and dmesg are from the core
dump after reboot)
I'm wondering whether the ENOMEM's reported by GEOM point out that GEOM
has a problem or just tell us that the machine was out of
