Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 26 Sep 2006 13:01:59 +0900
From:      YONETANI Tomokazu <qhwt+fbsd@les.ath.cx>
To:        freebsd-current@freebsd.org
Subject:   Re: LSI 1030 mpt doesn't work if I build a new kernel
Message-ID:  <20060926040159.GE1080@les.ath.cx>
In-Reply-To: <7579f7fb0609251606t2913858boaa2e6d71914d0fa6@mail.gmail.com>
References:  <1157154024.835.6.camel@atomizer.opensourcebeef.net> <20060924071601.GA1080@les.ath.cx> <20060924205903.GY1045@tigerfish2.my.domain> <20060925111048.GD1080@les.ath.cx> <7579f7fb0609251606t2913858boaa2e6d71914d0fa6@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Sep 25, 2006 at 04:06:11PM -0700, Matthew Jacob wrote:
> Um- I'm still trying to find a real error here. The bootverbose simply
> lists selection failures for devices that don't exist. Other than
> that, I cannot see what you are claiming is an error.

No, they don't contain error message, they're just there to hopefully give
you hints about our hardware (and I couldn't find a way to include the real
error message in the dmesg output without hitting the panic at that time :).
The real visible problems are:

- random I/O errors during disk activity; buildworld almost immediately
  terminates because of the error.  sometimes it leads to a panic in
  softupdates code.

- error messages to the console:
  (da0:mpt0:0:0:0): CAM Status 0x34
  (da0:mpt0:0:0:0): Retrying Command
  (da0:mpt0:0:0:0): CAM Status 0x34
  (da0:mpt0:0:0:0): Retrying Command
  (da0:mpt0:0:0:0): error 5
  (da0:mpt0:0:0:0): Retries Exhausted
  (da0:mpt0:0:0:0): error 5
  (da0:mpt0:0:0:0): Retries Exhausted
  (da0:mpt0:0:0:0): error 5

If I raise dev.mpt.0.debug from 4(the default) to a higher value than 5,
the above errors stop popping up,  although it spams the message buffer.
Changing it to 5 doesn't seem to change the amount of the message the
driver spews.

Regards.

> On 9/25/06, YONETANI Tomokazu <qhwt+fbsd@les.ath.cx> wrote:
> >On Sun, Sep 24, 2006 at 03:59:03PM -0500, Bruce Burden wrote:
> >> On Sun, Sep 24, 2006 at 04:16:01PM +0900, YONETANI Tomokazu wrote:
> >> >
> >> > Recently I tried installing FreeBSD 5.4-RELEASE on an IBM X335 in my
> >> > office and tried to upgrade to 6.2-PRERELEASE, and found that although
> >> > it doesn't hang or panic during boot, running I/O intensive 
> >applications
> >> > (including buildworld) ends up in an I/O error, and eventually 
> >panicked and
> >> > rebooted.
> >> >
> >>       This would be best on -STABLE, which the 6x thread is. Anyway,
> >
> >But I found that the snapshot from September 5 still has the similar
> >issue, so I'd imagine that the driver in -CURRENT still has the problem,
> >though I'm speaking without knowing how much changes have been made since
> >the last MFC.  I need to set up a machine which can build current -CURRENT
> >to be sure.
> >
> >>    I have:
> >[snip]
> >> FreeBSD tigerfish2.my.domain 6.1-STABLE FreeBSD 6.1-STABLE #6: Sun Aug 
> >27 11:03:43 CDT 2006
> >
> >Thanks for the suggestion, I put mine at
> >  http://les.ath.cx/FreeBSD/mpt/
> >
> >>    and have not had any problems with the mpt device. The controller is
> >>    built into the Tyan S2895/Thunder K8WE board.
> >>
> >>       I am not using the Seagate drive - it will be used to hold the
> >>    AMD64 installation when I get around to doing that, while the IBM
> >>    drive will continue to hold the i386 install if I need to switch
> >>    back. The RAID holds user data, and is not an issue when performing
> >>    kernel builds.
> >>
> >>       Have you tried to install the 6.1 release from CD/DVD?
> >
> >Not yet, but I doubt it'll make it through to the end because of the
> >I/O error issue.
> >
> >Cheers.
> >_______________________________________________
> >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?20060926040159.GE1080>