Re: port-hpcarm/60283

["requiem. via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR port-hpcarm/60283; it has been noted by GNATS.

From: "requiem." <rqm%0xde501a7a.net@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: port-hpcarm-maintainer%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
Subject: Re: port-hpcarm/60283
Date: Tue, 9 Jun 2026 15:17:54 +0100

 sorry I meant h3600 and h3630
 
 9 Jun 2026 13:00:09 requiem. via gnats <gnats-admin%NetBSD.org@localhost>:
 
 > The following reply was made to PR port-hpcarm/60283; it has been noted b=
 y GNATS.
 >=20
 > From: "requiem." <rqm%0xde501a7a.net@localhost>
 > To: gnats-bugs%netbsd.org@localhost
 > Cc:
 > Subject: Re: port-hpcarm/60283
 > Date: Tue, 9 Jun 2026 12:55:01 +0100
 >=20
 > Hello uwe,
 >=20
 > Tried booting the NetBSD8.gz kernel; and I am getting stuck with the
 > same issue on boot:
 >=20
 > wdc0:0:0: lost interrupt
 > =C2=A0=C2=A0=C2=A0 type: ata tc_bcount: 512 tc_skip: 0
 > wd0d: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying
 > wdc0:0:0: lost interrupt
 > =C2=A0=C2=A0=C2=A0 type: ata tc_bcount: 512 tc_skip: 0
 > wd0d: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying
 > wdc0:0:0: lost interrupt
 > =C2=A0=C2=A0=C2=A0 type: ata tc_bcount: 512 tc_skip: 0
 > wd0d: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying
 > wdc0:0:0: lost interrupt
 > =C2=A0=C2=A0=C2=A0 type: ata tc_bcount: 512 tc_skip: 0
 > wd0d: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying
 > wdc0:0:0: recal error (5)
 > wd0d: error reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0)
 > wd0: (address mark not found, aborted command)
 > wdc0:0:0: lost interrupt
 > =C2=A0=C2=A0=C2=A0 type: ata tc_bcount: 512 tc_skip: 0
 > wd0d: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying
 > wdc0:0:0: recal error (60)
 > wd0d: error reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying
 > wd0: (media changed, uncorrectable data error)
 > wdc0:0:0: recal drive fault
 > wd0d: device fault reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying
 >=20
 >=20
 > The CF Card works fine in the machine otherwise; it's an old 1G
 > Industrial grade CF card (used to hold a Windows XP Embedded
 > installation).
 >=20
 > However I just discovered not long ago that what I purchased listed as
 > a "8600" is in fact a *8630*. Might this be the cause; is the
 > underlying hardware just different enough to cause these problems?
 >=20
 > On Mon, 25 May 2026 08:20:02 +0000 (UTC)
 > "Valery Ushakov via gnats" <gnats-admin%NetBSD.org@localhost> wrote:
 >=20
 >> The following reply was made to PR port-hpcarm/60283; it has been
 >> noted by GNATS.
 >>
 >> From: Valery Ushakov <uwe%stderr.spb.ru@localhost>
 >> To: gnats-bugs%netbsd.org@localhost
 >> Cc:
 >> Subject: Re: port-hpcarm/60283
 >> Date: Mon, 25 May 2026 11:17:22 +0300
 >>
 >>=C2=A0 On Sun, May 24, 2026 at 21:41:06 +0100, requiem. wrote:
 >>=C2=A0 [...]
 >>=C2=A0 > [=C2=A0=C2=A0 1.0542408] wd0 at atabus0 drive 0
 >>=C2=A0 > [=C2=A0=C2=A0 1.1042437] syscall 295 is busy
 >>=C2=A0 > wdc0:0:0: lost interrupt
 >>=C2=A0 > [=C2=A0=C2=A0 4.0642161]=C2=A0=C2=A0=C2=A0 type: ata tc_bcount: =
 512 tc_skip: 0
 >>=C2=A0 > [=C2=A0=C2=A0 4.1010932] wd0: <SMART CF>
 >>=C2=A0 > [=C2=A0=C2=A0 4.1177233] wd0: drive supports 1-sector PIO transf=
 ers, LBA
 >>=C2=A0 > addressing [=C2=A0=C2=A0 4.1479389] wd0: 971 MB, 1974 cyl, 16 he=
 ad, 63 sec,
 >>=C2=A0 > 512 bytes/sect x 1989792 sectors=C2=A0
 >>=C2=A0
 >>=C2=A0 This:
 >>=C2=A0
 >>=C2=A0=C2=A0=C2=A0 wdc0:0:0: lost interrupt
 >>=C2=A0=C2=A0=C2=A0 type: ata tc_bcount: 512 tc_skip: 0
 >>=C2=A0
 >>=C2=A0 probably indicates that something is not right when netbsd tries t=
 o
 >>=C2=A0 talk to the card.
 >>=C2=A0
 >>=C2=A0 I'm not familiar with this hardware or wdc(4) internals.=C2=A0 One=
  thing
 >>=C2=A0 that you can try _easily_ is using older NetBSD releases.=C2=A0 Yo=
 u don't
 >>=C2=A0 have to bother with the installation, just drop an old kernel to t=
 he
 >>=C2=A0 CF card under a different name and try to boot it.=C2=A0 Some wd/w=
 dc
 >>=C2=A0 changes might have broken the driver for hpcarm b/c it, obviously,
 >>=C2=A0 doesn't get a lot of testing there...
 >>=C2=A0
 >>=C2=A0 The next thing to try (if none of the old kernels work) would be
 >> using an older, simpler CF card.=C2=A0 I don't know _anything_ about the
 >>=C2=A0 hardware, but HPC is _old_ and who knows what corners they cut.
 >>=C2=A0 E.g. you can't use large cards (a 8GB CF card doesn't work in my
 >>=C2=A0 Jornada 690) b/c some address lines are not there or something.=C2=
 =A0 I
 >> did run into cards that just didn't work in my hpcsh, though it's been
 >>=C2=A0 decades ago and I don't remember any details.
 >>=C2=A0
 >>=C2=A0
 >>=C2=A0 -uwe
 >>=C2=A0
 >=20