Date: Fri, 13 Feb 2004 12:12:07 +0100 From: Johan Pettersson <manlix@demonized.net> To: "Putinas Piliponis" <putinas.piliponis@icnspot.net> Cc: freebsd-current@freebsd.org Subject: Re: Bad interrupt routing causes my SATA controller to fail. Message-ID: <20040213121207.25bc7944.manlix@demonized.net> In-Reply-To: <000601c3f1cf$3f9cc9b0$ee64a8c0@pilkishome2> References: <20040211025317.13af3d36.manlix@demonized.net> <20040212021355.GA9984@xor.obsecurity.org> <20040212190942.47c09b06.manlix@demonized.net> <200402121443.31105.jhb@FreeBSD.org> <20040212230646.23be797d.manlix@demonized.net> <008701c3f1b6$b2ca9a70$1e64a8c0@spotripoli.local> <20040212232447.6a1fbbd4.manlix@demonized.net> <009501c3f1b7$7026b540$1e64a8c0@spotripoli.local> <20040213013043.573a47a0.manlix@demonized.net> <000601c3f1cf$3f9cc9b0$ee64a8c0@pilkishome2>
next in thread | previous in thread | raw e-mail | index | archive | help
Tons of spurious interrupts. :] > then try to boot in verbose mode.. and you will see what things are far from > ok :) > > ----- Original Message ----- > From: "Johan Pettersson" <manlix@demonized.net> > To: "Putinas" <pilkis@gmx.net> > Cc: <freebsd-current@freebsd.org> > Sent: Friday, February 13, 2004 2:30 AM > Subject: Re: Bad interrupt routing causes my SATA controller to fail. > > > > It seems to work just as it should do with 5.2.1-RC2. No problems except > that it still hangs after printing uptime when rebooting, as I said in some > previous mail to freebsd-current. > > > > > would be nice.. I would like to know, if only me suffers from this ... > > > with new kernel from releng , my server lockups in couple of hours with > > > error WRITE_DMA retries 2 left LBA xxx... > > > > > > ----- Original Message ----- > > > From: "Johan Pettersson" <manlix@demonized.net> > > > To: "Putinas" <pilkis@gmx.net> > > > Cc: <freebsd-current@freebsd.org> > > > Sent: Friday, February 13, 2004 12:24 AM > > > Subject: Re: Bad interrupt routing causes my SATA controller to fail. > > > > > > > > > >I should cvsup to latest RELENG_5_2 and try this out. > > > > > > > >> current is current ... it's no problem to fix it later... but what > about > > > >> release 5.2.1-rc2 ? which suffers from same problem ? > > > >> > > > > _______________________________________________ > > > > freebsd-current@freebsd.org mailing list > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > > > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" > > > > > > > > > > > > > > _______________________________________________ > > > freebsd-current@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" > > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040213121207.25bc7944.manlix>