Date: Thu, 18 Oct 2012 08:46:12 -0400 From: John Baldwin <jhb@freebsd.org> To: "Harald Schmalzbauer (mobil)" <h.schmalzbauer@omnilan.de> Cc: freebsd-stable@freebsd.org Subject: Re: mpt irq timeout problem after reboot - only if non-verbose booting !?! Message-ID: <201210180846.12630.jhb@freebsd.org> In-Reply-To: <7671651912.1034975692@omnilan.de> References: <507D27DC.5030104@omnilan.de> <201210171319.32815.jhb@freebsd.org> <7671651912.1034975692@omnilan.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, October 17, 2012 3:14:52 pm Harald Schmalzbauer (mobil) wrote: > -----Urspr=C3=BCngliche Nachricht----- > > Von: John Baldwin <jhb@freebsd.org> > > An: freebsd-stable@freebsd.org > > Cc: h.schmalzbauer@omnilan.de > > Gesendet: 17.10.'12, 20:46 > >=20 > > On Tuesday, October 16, 2012 5:24:44 am Harald Schmalzbauer wrote: > >> Hello, > >>=20 > >> I have 9.1-RC2 running in an ESXi 5.1 guest. > >> I use 'lsisas' as virtual SCSI-Controller and mpt attaches and finds 1= 068E. > >>=20 > >> Everything is working fine until the first 'shutdown -r now': > >> The second boot pauses for ~2 minutes after probing disks and continues > >> with this error: > >> mpt0: Timedout requests already complete. Interrupts may not be functi= oning. > >=20 > > To be clear, you only see this at the end of reboot, and the hardware i= s fine > > once the machine is back up? > . >=20 > Thanks for your attention! > The timeout occurs after the first 'shutdown -r' while device probing dur= ing > second boot process. Perhaps this is amd64 specific. Today I had a new i= 386 > setup which doesn't exhibit this timeout. But it's on different hardware = and > hv-host was 5.0 inestead 5.1. So not really representative... Hmmm, ok. In that case my patch is not relevant. It would only fix that message occuring during the shutdown. =2D-=20 John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201210180846.12630.jhb>