Date: Mon, 5 Aug 1996 11:01:25 -0700 (PDT) From: "Keith Beattie[SFSU Student]" <beattie@george.lbl.gov> To: questions@freebsd.org Subject: wd0 and sio0 messages Message-ID: <199608051801.LAA16413@george.lbl.gov>
next in thread | raw e-mail | index | archive | help
Anybody know what these might mean? --- from /var/log/messages --- Aug 4 16:10:27 viv /kernel: wd0: interrupt timeout: Aug 4 16:10:32 viv /kernel: wd0: status 50<seekdone> error 0 Aug 4 16:10:32 viv /kernel: wd0: interrupt timeout: Aug 4 16:10:32 viv /kernel: wd0: status 50<seekdone> error 1<no_dam> Aug 4 18:09:26 viv /kernel: sio0: 71 more tty-level buffer overflows (total 71) Aug 4 18:09:27 viv /kernel: sio0: 16 more tty-level buffer overflows (total 87) --- from /var/log/messages --- (the sio0 messages continue on...) Here's what those devices look like when booting: --- from dmesg --- sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16450 [...] wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): <Maxtor 7120 AT>, multi-block-16 wd0: 124MB (254592 sectors), 936 cyls, 16 heads, 17 S/T, 512 B/S --- from dmesg --- My mouse is on sio0, (com1) and wd0 has /, /var and swap on it. The wd0 messages have been poping up every once in a while since I built a kernel. Yesterday, when I quit netscape 3.0b6, my whole X session, (mouse too) froze. Fortunately my SLIP connection was still up so I could get somebody to reboot it gracefully. I'm going to build (yet another) kernel without the "flags 0x80ff" for wd0 and wd1, which adds the mulit-sector transfers and 32-bit access. Hopefully that will fix the wd0 errors but are sio0 errors the fault of netscape? Thanks again, Keith -- // Keith Beattie Lawrence Berkeley Laboratory (LBL) \\ // SFSU Grad Student Imaging and Distributed Computing Group (ITG) \\ // KSBeattie@lbl.gov http://www-itg.lbl.gov/~beattie \\ // 1 Cyclotron Rd. MS: 50B-2239 Berkeley, CA 94720 (510) 486-6692 \\
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199608051801.LAA16413>