On Thu, Apr 09, 2020 at 12:24:17PM +0200, Otto Moerbeek wrote:
> On Wed, Apr 08, 2020 at 07:03:29PM +0200, Sigi Rudzio wrote:
>
> > Am Mi., 8. Apr. 2020 um 08:37 Uhr schrieb Otto Moerbeek <o...@drijf.net>:
> > >
> > > On Wed, Apr 08, 2020 at 01:11:29AM +0200, Sigi Rudzio wrote:
> > >
> > > > Hello misc@,
> > > >
> > > > while testing the FFS2 patches by otto@ I noticed that I was unable
> > > > to install -current on my silver Blade 2500.
> > > >
> > > > tar fails while unpacking the sets, although the files are ok, if I
> > > > rename
> > > > base67.tgz to base66.tgz to fool the 6.6 installer I can install
> > > > 6.7-beta,
> > > > although it fails/panics with a lot of "Illegal instruction" errors on
> > > > the
> > > > first boot.
> > > >
> > > > otto@ already told me that this might be fallout from the recent clang
> > > > changes.
> > >
> > > Well, I sais it *could be*, but you did not show my the actual errors
> > > in that email. The errorsbelow indicate a harware issue, i.e. bad
> > > disk.
> > >
> > > -Otto
> >
> > Sorry, I should have been clearer.
> >
> > I tried another disk from my working V240 and got the same errors.
> >
> > Installing on an IDE hard disk works and the system is working fine,
> > even writing large files to the SCSI disk is fine, but I can make it panic
> > with tar.
> > So I guess this is some kind of SCSI bus hardware issue that 6.6 doesn't
> > trigger and some change between 6.6 and 6.7-beta does trigger it.
> >
> > Sorry for the noise and thanks for the help!
>
> Hmm, you might be onto something. I have seen similar issues on a
> Blade 150 but blamed it on hardware. Sadly I do not thave easy access
> to the machine atm.
In the meantime krw@ committed (with your help) a fix for a DMA issue
on mpi(4) that seems to make my Blade150 much more reliable. Thanks to
both of you!
-Otto
