Date: Wed, 8 Mar 2006 13:28:08 GMT From: Anders Thulin <ath@algonet.se> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/94227: 'no dump device defined' on random occasions Message-ID: <200603081328.k28DS85T037686@www.freebsd.org> Resent-Message-ID: <200603081330.k28DU7rg028886@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 94227 >Category: kern >Synopsis: 'no dump device defined' on random occasions >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Mar 08 13:30:07 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Anders Thulin >Release: FreeBSD 6.0-RELEASE >Organization: none >Environment: FreeBSD 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 root@x64.samsco.home:/usr/obj/usr/src/sys/GENERIC i386 >Description: The hardware is a Fujitsu-Siemens Lifebook C-6565 laptop (PIII) on which I've run FreeBSD 5.4 for quite some time, as well as some earlier releases without problems. On first installation of 6.0, I got 'no dump device', followed by restart. This was a full installation, with reformatting of disks, as well as resetting boot manager to none. Second attempt worked. While I was reestablishing my old system, the same problem appeared again, while I was rm-rf-ing some old disk structures in one console, while working in another. This is the relevant parts from the /var/log/messages file -- I'm including all lines with the same timestamp. Mar 8 13:42:22 syslogd: kernel boot file is /boot/kernel/kernel Mar 8 13:42:22 kernel: subdisk0: detached Mar 8 13:42:22 kernel: ad0: detached Mar 8 13:42:22 kernel: unknown: TIMEOUT - READ_DMA retrying (1 retry left) LBA=19305279 Mar 8 13:42:22 kernel: unknown: timeout waiting to issue command Mar 8 13:42:22 kernel: unknown: error issueing READ_DMA command Mar 8 13:42:22 kernel: g_vfs_done():ad0s1f[WRITE(offset=98304, length=16384)]error = 6 Mar 8 13:42:22 kernel: g_vfs_done():ad0s1f[WRITE(offset=770048, length=16384)]error = 6 Mar 8 13:42:22 kernel: g_vfs_done():ad0s1f[WRITE(offset=786432, length=16384)]error = 6 .. etc, followed by some Mar 8 13:42:22 kernel: g_vfs_done():ad0s1f[READ(offset=6770188288, length=2048)]error = 5 Mar 8 13:42:22 kernel: g_vfs_done():ad0s1f[READ(offset=6770188288, length=2048)]error = 6 Mar 8 13:42:22 kernel: g_vfs_done():ad0s1f[READ(offset=6770190336, length=2048)]error = 6 .. etc Mar 8 13:42:22 kernel: panic: softdep_setup_freeblocks: inode busy Mar 8 13:42:22 kernel: Uptime: 20m30s Mar 8 13:42:22 kernel: Cannot dump. No dump device defined. Mar 8 13:42:22 kernel: Automatic reboot in 15 seconds - press a key on the console to abort Mar 8 13:42:22 kernel: --> Press a key on the console to reboot, Mar 8 13:42:22 kernel: --> or switch off the system now. Mar 8 13:42:22 kernel: Rebooting... Just in case ad0 should be of interest, Mar 8 13:20:49 kernel: ad0: 9590MB <TOSHIBA MK1016GAP U1.11 A> at ata0-master UDMA33 .. A related problem seems to have been reported earlier ... but in that case it seems to be traced to a Sil3112 controller. Nothing like that on the Lifebook. The C-6565 does not seem to be supported any more, so there are no BIOS updates to be found. >How-To-Repeat: I have not yet found a way to make the problem stand still. On the other hand it doesn't seem to repeat too often to make it unbearable ... so far. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200603081328.k28DS85T037686>