Subject: Re: kern/29291
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: Jens Kessmeier <j.kessmeier@teles.de>
List: netbsd-bugs
Date: 02/14/2005 15:57:01
The following reply was made to PR kern/29291; it has been noted by GNATS.

From: Jens Kessmeier <j.kessmeier@teles.de>
To: "'gnats-bugs@gnats.netbsd.org'" <gnats-bugs@netbsd.org>
Cc: 
Subject: Re: kern/29291
Date: Mon, 14 Feb 2005 16:57:50 +0100

 Pretty new information about ddb(4), reboot, DDB_ONPANIC, panic(9). Nice to
 know it.
 
 You say: In my experience, after a failed "sync" attempt, the scsi driver is
 usually too horked for the dump to take.
 
 Right, that is our problem. If you repeat my test stuff, or something else
 with a panic, you will see 80 times no dump and
 1 time a dump. Your solution is fine in development. For a crashed server
 machine far from home, in a dark room, on weekend, at night with your
 girlfriend,  you will drive or what ever to the console? Please, please say
 that is not what you want.
 
 Let us talk about another solution. Why failed the "sync" or why is the scsi
 driver too horked?