On Fri, May 25, 2001 at 03:20:20PM +1000, Keith Owens wrote:
>
> >> On a side note, does anyone know if the kernel does checking if the
> >> stack overflowed at any time?
> >
> >You normally get a silent hang or worse a stack fault exception
> >(which linux/x86 without kdb cannot recover from) w
Hi,
I received the following oops when using the loop driver on kernel
2.4.2-pre2 patched with Jens Axboe's loop4 patch. I believe it occurs
because in loop.c, lo->lo_tsk is only assigned to by the loop thread when
it starts up but it is possible for block requests to be sent to the
loop drive
[1.]
Hang when unmounting filesystem on loop device
[2.]
Intermittently (once so far) umount hangs when umounting
a filesystem mounted on a loop device. Other processes run until they
access the filesystem when they hang too.
[3.]
loop
[4.]
Linux version 2.4.2-pre1
([EMAIL PROTECTED]
On Fri, Jan 26, 2001 at 08:19:58AM -0800, H. Peter Anvin wrote:
>
> A better idea might be to find out what port, if any, Windows uses. If
> Windows does it, it is usually safe.
>
Windows NT 4 Service Pack 6 doesn't use any delay however
READ/WRITE_PORT_* are implemented as indirect function c
4 matches
Mail list logo