> A Fairly Big Server just died 3 times with "wait_on_bh" showing on the
> console. The call trace looked like:
>
> synchronize_bh
> tcp_v4_unhash
> tcp_close_state
> tcp_close
> inet_release
> sock_release
> sock_close
> __fput
>
> (symbols translated by hand from System.map)
>
> It was running 2.2.1 at the time. Yesterday the same machine running 2.0.36
> decided to kill its ethernet driver (eepro100) with the message "too much
> work in interrupt".
>
> Today it froze once during boot (2.2.1) right after "Probing for PCI
> devices".
this looks like the socket locking bug fixed in 2.2.2.
-- mingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/