Matt Dillon <[EMAIL PROTECTED]> writes:
>     (2) the I/O for the buffer synchronization is initiated but interrupts
>     are winding up being disabled by the halt code due to holding Giant
>     and not sleeping (more likely).  That all I can think of.  We've hit
>     the interrupt disablement problem before in -current, it's probably
>     something simliar.

Sounds likely. On my laptop, the "giving up on n buffers" message is
usually accompanied by an ata0 timeout.

DES
-- 
Dag-Erling Smorgrav - [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to