Date: Tue, 6 Mar 2001 13:25:12 -0500 (EST) From: Andrew Gallatin <gallatin@cs.duke.edu> To: naddy@mips.inka.de (Christian Weisgerber) Cc: freebsd-alpha@FreeBSD.ORG, phk@FreeBSD.ORG Subject: Dump segv w/devfs (was Re: My list of -CURRENT problems) Message-ID: <15013.11144.757425.205222@grasshopper.cs.duke.edu> In-Reply-To: <98328r$f38$1@kemoauc.mips.inka.de> References: <9806fj$1si$1@kemoauc.mips.inka.de> <Pine.LNX.4.21.0103050923450.16541-100000@zeppo.feral.com> <15011.59405.333814.964428@grasshopper.cs.duke.edu> <98328r$f38$1@kemoauc.mips.inka.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Christian Weisgerber writes: > Andrew Gallatin <gallatin@cs.duke.edu> wrote: > > > Perhaps it is scsi-controller specific? What type of scsi controller > > is in this machine? > > sym(4), although I can't imagine this making a difference. <...> OK, it seems to be related to devfs. Dumping with /dev/null as a file crashes. Dumping to a normal file elsewhere works. Dumping through a redirect to /dev/null (tcsh) seems to work as well. /dev/null as a "file" works just fine w/o devfs. Eg: dump 0af - / > /dev/null - works dump 0af /usr/tmp/foo / - works dump 0af /dev/null / - SEGV w/devfs, works with normal /dev Anybody have some ideas? Does this happen only on alphas? ( I don't have a -current PC). FWIW, cat'ting the resulting /usr/tmp/foo to /dev/null works just dandy.. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15013.11144.757425.205222>