DFly-stable as of April 1st crashed, but no crash dump was possible due to ips driver being unable to do crash dumps

YONETANI Tomokazu qhwt+dfly at les.ath.cx
Sat Apr 2 19:06:46 PST 2005

On Sun, Apr 03, 2005 at 04:28:52AM +0200, Tomaž Borštnar wrote:
> YONETANI Tomokazu wrote:
> >>boot() called on cpu#0
> >>
> >>syncing disks...
> >
> >
> >This is strange; looking at the code responsible for the sync on
> >panic, it should not print the message "syncing disks" when
> >sync_on_panic is set to zero(i.e. (bootopt & RB_NOSYNC) != 0).
> nope, I added this later - after 2nd crash.

Ah, I see.

> >As for dump feature on ips driver, sorry I haven't had enough time
> >to port it. I asked Scott Long many months ago for his work-in-progress
> >dump patch(which has already been committed on FreeBSD 5.x+), and he gave
> So it is part of 5.3+ now? Because older FreeBSDs have the same problem 
> - stuck in syncing disks.

Actually, the feature is in HEAD and RELENG_5, but not in any -RELEASEes
yet.  But I don't think not having dump support caused `stuck in syncing
disks' problem; when there's no dump support, it just does nothing and it
immediately shows a prompt `Automatic reboot in %d seconds -'.

> >it to me, but I couldn't finish porting it then. I'm still trying to find
> >time to work on it though.
> btw: how is your controller configured as far as read and write caching 
> are concerned?

I probably can't answer this question until tomorrow(I don't have console
access to the server right now), but IIRC it hasn't been changed from the

More information about the Bugs mailing list