On Sun, Mar 22, 2020 at 12:46:22PM +0100, Jarom?r Dole?ek wrote:
> Hello,
>
> can you please compile your kernel with ATADEBUG option, then for
> running system with new kernel set wdcdebug_wd_mask variable to '2'
> via ddb before the daily run, and then collect the output after it
> hangs again?
Hello,
can you please compile your kernel with ATADEBUG option, then for
running system with new kernel set wdcdebug_wd_mask variable to '2'
via ddb before the daily run, and then collect the output after it
hangs again? Beware it's going to be a lot of messages.
I'm particularly interested if
On Thu, Mar 12, 2020 at 12:53:47PM +1100, Paul Ripke wrote:
> Just wondering what other people are doing to avoid ide timeouts when
> running qemu? My disk image is on spinning rust, and when the /etc/daily
> jobs run on the host, the qemu emulated netbsd kernel tends to see
> timeouts and
Just wondering what other people are doing to avoid ide timeouts when
running qemu? My disk image is on spinning rust, and when the /etc/daily
jobs run on the host, the qemu emulated netbsd kernel tends to see
timeouts and ultimately hang. Eg:
piixide0:0:0: lost interrupt
[ 20336.2698191]
