From owner-freebsd-bugs Mon Sep 8 10:36:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA14684 for bugs-outgoing; Mon, 8 Sep 1997 10:36:15 -0700 (PDT) Received: from innocence.interface-business.de (innocence.interface-business.de [193.101.57.202]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA14667 for ; Mon, 8 Sep 1997 10:36:10 -0700 (PDT) Received: from ida.interface-business.de (ida.interface-business.de [193.101.57.203]) by innocence.interface-business.de (8.6.11/8.6.9) with SMTP id TAA15016 for ; Mon, 8 Sep 1997 19:36:03 +0200 Received: (from j@localhost) by ida.interface-business.de (8.8.7/8.7.3) id TAA00497; Mon, 8 Sep 1997 19:36:01 +0200 (MET DST) Message-ID: <19970908193559.WU22983@ida.interface-business.de> Date: Mon, 8 Sep 1997 19:35:59 +0200 From: j@ida.interface-business.de (J Wunsch) To: freebsd-bugs@freebsd.org Subject: My 2.2-stable panic reproduced X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-31809-14 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Organization: interface business GmbH, Dresden Reply-To: joerg_wunsch@interface-business.de (Joerg Wunsch) Sender: owner-freebsd-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well, it hit again. And it's not only an ahc(4) issue, as it seems. I was rm -rf'ing a large directory hierarchy on an additional disk, and thought about speeding it up by doing mount -u -o async /dev/sd3e /mnt1/usr while the rm was running. This yielded on the console: ============================================================================ WARNING: R/W mount of /dev/sd3e denied. Filesystem is not clean - run fsck. worm0(ahc1:0:0): Deferred Error: UNIT ATTENTION asc: 29,0 worm0(ahc1:0:0): Power on, reset, or bus device reset occurred panic: vref used where vget required syncing disks... 50 50 42 32 21 9 done dumping to dev 401, offset 241664 dump 32 ============================================================================ ...and there it was sitting, waiting for me to hit reset. No coredumps on 2.2-stable, see my PR. I forgot to boot the DDB kernel at the last reboot, but i think the panic message stands for itself. It's probably a little bogus that a R/W upgrade mount was denied, but well, i could have lived with this. I have no idea why worm0 (which is on the same bus as sd3) caught a UNIT ATTN, nor why this was noticed just at that point (/dev/worm0 had been mounted all the time). Maybe someone was accessing the CD-ROM just in this moment over the network, but i doubt this. (The Plasmon has a strong tendency for deferred errors, for whatever reason.) It would be great if we could fix the `vref' panic at least, before 2.2.5 will ship. -- J"org Wunsch Unix support engineer joerg_wunsch@interface-business.de http://www.interface-business.de/~j