Date: Wed, 21 Mar 2001 17:50:39 -0600 From: rand@meridian-enviro.com To: Mike Smith <msmith@FreeBSD.ORG> Cc: freebsd-stable@FreeBSD.ORG, Mike Tancsa <mike@sentex.net>, bryanh@meridian-enviro.com Subject: Re: 3ware problems Message-ID: <87u24m7kc0.wl@delta.meridian-enviro.com> In-Reply-To: <200103210258.f2L2wGO00829@mass.dis.org> References: <87g0gb55ef.wl@localhost.meridian-enviro.com> <200103210258.f2L2wGO00829@mass.dis.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Mike> If you can add another function like twe_printstate that invokes Mike> twe_print_request on each of the requests on the busy queue and Mike> let me know what they look like, that might give me some clues. OK, I haven't written the twe_printstate function yet, but I think I have the request. I got the filesystem wedged first, and then browsing the datastructures with DDB, I think I've found the busy queue. Here's the request: db> call twe_print_request(0xc1529800) twe0: CMD: request_id 89 opcode <READ> size 7 unit 0 host_id 0 twe0: status 0 flags 0x0 count 16 sgl_offset 3 twe0: lba 264703 twe0: 0: 0xce4f000/4096 twe0: 1: 0x2ab0000/4096 twe0: tr_command 0xc1529800/0x1749d800 tr_data 0xcb928000/0xce4f000,8192 twe0: tr_status 2 tr_flags 0x1 tr_complete 0xc011f170 tr_private 0 I'm rebuilding the kernel now with the function twe_printstate, after I figured it out with the debugger. (This reminds me of a saying that has to do with horses and carriages, hmm.) Oh, btw, it took over 3 million rows to get it stuck this time. Gotta love a test cycle of 6 hours or so. Sigh. I also paniced the kernel from DDB, so I have a core file too. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87u24m7kc0.wl>