Date: Sun, 2 Sep 2001 10:24:52 +0930 From: Greg Lehey <grog@FreeBSD.org> To: Mike Harding <mvh@ix.netcom.com> Cc: stable@freebsd.org Subject: Tagged queueing causes silo overflows? (was: ah! the dread 'silo overflow' returns!) Message-ID: <20010902102452.D59668@wantadilla.lemis.com> In-Reply-To: <20010901232101.33FF513120@netcom1.netcom.com>; from mvh@ix.netcom.com on Sat, Sep 01, 2001 at 04:21:01PM -0700 References: <20010901232101.33FF513120@netcom1.netcom.com> <20010901234031.50B1313120@netcom1.netcom.com> <20010901232101.33FF513120@netcom1.netcom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday, 1 September 2001 at 16:21:01 -0700, Mike Harding wrote: > > I have been getting 'silo overflow' messages for a week or two, on > recent buildworld (for, example, today). I am using a 56K modem, 1.3 > GHz Athlon, IDE, etc. Is this a known issue??? I remember this from > the bad old days, but I haven't seen it in a while. On Saturday, 1 September 2001 at 16:40:31 -0700, Mike Harding wrote: > > (I think) never mind - I think that this is related to tagged queuing, > which got (re)enabled in the source. I saw this earlier when I hacked > the kernel source to support tagged queuing with my newish IBM drive - > the newer kernels recognize this drive. I had bad silo overflow > issues when I had previously enabled the tagged queuing. Hmm. I'd be inclined to consider this a bug. Looks as if the tagged queueing might cause interrupts to be locked out for too long. Greg -- See complete headers for address and phone numbers 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?20010902102452.D59668>