A clarification: I did not think that the networking issue was
caused by the oops; I thought that the networking issue might
have been one of the things that triggered the oops. It might
be completely unrelated, though.
After sending in the report I discovered that during a session
of updating p
Package: linux-image-2.6.18-3-xen-686
Version: 2.6.18-8
Severity: normal
I have a directory on a remote machine mounted to my machine via
sshfs. Earlier today there was a networking issue, which I
suspect is related to the bug. For over an hour my machine was
unable to see the remote machine.
2 matches
Mail list logo