NetBSD Problem Report #56987
From mlh@goathill.org Tue Aug 30 00:11:10 2022
Return-Path: <mlh@goathill.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
by mollari.NetBSD.org (Postfix) with ESMTPS id 6D9CB1A921F
for <gnats-bugs@gnats.NetBSD.org>; Tue, 30 Aug 2022 00:11:10 +0000 (UTC)
Message-Id: <20220829225409.AC82C12C46@chopper.goathill.org>
Date: Mon, 29 Aug 2022 18:54:09 -0400 (EDT)
From: mlh@goathill.org
Reply-To: mlh@goathill.org
To: gnats-bugs@NetBSD.org
Subject: problems with mounting usb memory devices on -current
X-Send-Pr-Version: 3.95
>Number: 56987
>Category: port-amd64
>Synopsis: Certain usb devices can no longer be mounted on -current
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: port-amd64-maintainer
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Aug 30 00:15:00 +0000 2022
>Closed-Date:
>Last-Modified: Thu Oct 05 15:45:01 +0000 2023
>Originator: MLH
>Release: NetBSD 9.99.99 Fri Jan 14 23:21:22 EST 2022
>Organization:
>Environment:
System: NetBSD 9.99.93 NetBSD 9.99.93 #0: Fri Jan 14 23:21:22 EST 2022 amd64
Architecture: amd64
Machine: amd64
>Description:
Since some time shortly after NetBSD 9.99.93, certain usb memory
devices no longer can be mounted - with "Device not configured"
error. It no longer works with devices that have correctly worked
for a number of years. Works fine with others.
NetBSD 9.99.99 - doesn't work :
attach:
Aug 29 13:26:37 tiamat /netbsd: [ 127.6388237] umass0 at uhub4 port 2 configuration 1 interface 0
Aug 29 13:26:37 tiamat /netbsd: [ 127.6388237] umass0: Lezyne (0x2b29) GPS Device (0x0055), rev 2.00/1.00, addr 5
Aug 29 13:26:37 tiamat /netbsd: [ 127.6388237] umass0: using SCSI over Bulk-Only
Aug 29 13:26:37 tiamat /netbsd: [ 127.6388237] scsibus0 at umass0: 2 targets, 1 lun per target
Aug 29 13:26:37 tiamat /netbsd: [ 127.6388237] uhidev3 at uhub4 port 2 configuration 1 interface 1
Aug 29 13:26:37 tiamat /netbsd: [ 127.6388237] uhidev3: Lezyne (0x2b29) GPS Device (0x0055), rev 2.00/1.00, addr 5, iclass 3/0
Aug 29 13:26:37 tiamat /netbsd: [ 127.6388237] uhid4 at uhidev3: input=64, output=64, feature=0
Missing the two lines as such:
Aug 29 13:45:52 tiamat /netbsd: [ 95.6407866] sd0 at scsibus0 target 0 lun 0: <FSL SEMI, FSL MASS STORAGE, 0001> disk removable
Aug 29 13:45:52 tiamat /netbsd: [ 95.6507884] sd0: fabricating a geometry
detach:
Aug 29 13:26:37 tiamat /netbsd: [ 128.3388163] umass0: BBB bulk-out clear stall failed, STALLED
Aug 29 13:26:37 tiamat /netbsd: [ 128.3388163] umass0: BBB reset failed, STALLED
Aug 29 13:26:37 tiamat /netbsd: [ 128.3388163] umass0: BBB bulk-in clear stall failed, IOERROR
Aug 29 13:26:37 tiamat /netbsd: [ 128.3388163] umass0: BBB bulk-out clear stall failed, IOERROR
Aug 29 13:26:37 tiamat /netbsd: [ 128.3388163] umass0: BBB reset failed, IOERROR
Aug 29 13:26:37 tiamat /netbsd: [ 128.3388163] umass0: BBB bulk-in clear stall failed, IOERROR
Aug 29 13:26:37 tiamat /netbsd: [ 128.3388163] umass0: BBB bulk-out clear stall failed, IOERROR
Aug 29 13:26:37 tiamat /netbsd: [ 128.3488165] umass0: BBB reset failed, IOERROR
Aug 29 13:26:37 tiamat /netbsd: [ 128.3488165] umass0: BBB bulk-in clear stall failed, IOERROR
Aug 29 13:26:37 tiamat /netbsd: [ 128.3488165] umass0: BBB bulk-out clear stall failed, IOERROR
Aug 29 13:26:37 tiamat /netbsd: [ 128.3488165] umass0: BBB reset failed, IOERROR
Aug 29 13:26:37 tiamat /netbsd: [ 128.3488165] umass0: BBB bulk-in clear stall failed, IOERROR
Aug 29 13:26:37 tiamat /netbsd: [ 128.3488165] umass0: BBB bulk-out clear stall failed, IOERROR
Aug 29 13:26:37 tiamat /netbsd: [ 128.3488165] umass0: BBB reset failed, IOERROR
Aug 29 13:26:37 tiamat /netbsd: [ 128.3488165] umass0: BBB bulk-in clear stall failed, IOERROR
Aug 29 13:26:37 tiamat /netbsd: [ 128.3488165] umass0: BBB bulk-out clear stall failed, IOERROR
Aug 29 13:26:37 tiamat /netbsd: [ 128.4288153] scsibus0: detached
Aug 29 13:26:37 tiamat /netbsd: [ 128.4288153] umass0: detached
Aug 29 13:26:37 tiamat /netbsd: [ 128.4288153] umass0: at uhub4 port 2 (addr 5) disconnected
Aug 29 13:26:37 tiamat /netbsd: [ 128.4288153] uhid4: detached
Aug 29 13:26:37 tiamat /netbsd: [ 128.4288153] uhidev3: detached
Aug 29 13:26:37 tiamat /netbsd: [ 128.4288153] uhidev3: at uhub4 port 2 (addr 5) disconnected
The bulk-in/out stall errors aren't always reported (or occur?).
NetBSD 9.99.93 - works correctly :
attach:
Aug 29 13:45:52 tiamat /netbsd: [ 95.6407866] umass0 at uhub4 port 2 configuration 1 interface 0
Aug 29 13:45:52 tiamat /netbsd: [ 95.6407866] umass0: Lezyne (0x2b29) GPS Device (0x0055), rev 2.00/1.00, addr 5
Aug 29 13:45:52 tiamat /netbsd: [ 95.6407866] umass0: using SCSI over Bulk-Only
Aug 29 13:45:52 tiamat /netbsd: [ 95.6407866] scsibus0 at umass0: 2 targets, 1 lun per target
Aug 29 13:45:52 tiamat /netbsd: [ 95.6407866] uhidev3 at uhub4 port 2 configuration 1 interface 1
Aug 29 13:45:52 tiamat /netbsd: [ 95.6407866] uhidev3: Lezyne (0x2b29) GPS Device (0x0055), rev 2.00/1.00, addr 5, iclass 3/0
Aug 29 13:45:52 tiamat /netbsd: [ 95.6407866] uhid4 at uhidev3: input=64, output=64, feature=0
Aug 29 13:45:52 tiamat /netbsd: [ 95.6407866] sd0 at scsibus0 target 0 lun 0: <FSL SEMI, FSL MASS STORAGE, 0001> disk removable
Aug 29 13:45:52 tiamat /netbsd: [ 95.6507884] sd0: fabricating a geometry
detach:
Aug 29 13:46:11 tiamat /netbsd: [ 114.3505992] sd0: detached
Aug 29 13:46:11 tiamat /netbsd: [ 114.3505992] scsibus0: detached
Aug 29 13:46:11 tiamat /netbsd: [ 114.3505992] umass0: detached
Aug 29 13:46:11 tiamat /netbsd: [ 114.3505992] umass0: at uhub4 port 2 (addr 5) disconnected
Aug 29 13:46:11 tiamat /netbsd: [ 114.3505992] uhid4: detached
Aug 29 13:46:11 tiamat /netbsd: [ 114.3505992] uhidev3: detached
Aug 29 13:46:11 tiamat /netbsd: [ 114.3505992] uhidev3: at uhub4 port 2 (addr 5) disconnected
>How-To-Repeat:
Plug in a usb memory device. The following commands work with NetBSD
9.99.93 but not later versions with some usb devices. (I have used
amd to mount them for many years)
$ mount -t msdos /dev/sd0e /mnt
mount_msdos: /dev/sd0e on /mnt: Device not configured
$ disklabel sd0
disklabel: /dev/rsd0: Device not configured
Plug in a usb memory card into another usb port while the first is
still plugged in and the second device can be mounted as sd0x:
$ disklabel sd0
# /dev/rsd0:
type: SCSI
disk: Flash Reader
label: fictitious
flags: removable
bytes/sector: 512
sectors/track: 32
tracks/cylinder: 64
sectors/cylinder: 2048
cylinders: 122112
total sectors: 250085376
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # microseconds
track-to-track seek: 0 # microseconds
drivedata: 0
5 partitions:
# size offset fstype [fsize bsize cpg/sgs]
d: 250085376 0 unused 0 0 # (Cyl. 0 - 122111)
e: 250052608 32768 MSDOS # (Cyl. 16 - 122111)
>Fix:
?
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback
State-Changed-By: skrll@NetBSD.org
State-Changed-When: Tue, 30 Aug 2022 05:28:09 +0000
State-Changed-Why:
Please bisect it further.
From: mlh@goathill.org (MLH)
To: gnats-bugs@netbsd.org
Cc: port-amd64-maintainer@netbsd.org, netbsd-bugs@netbsd.org,
gnats-admin@netbsd.org, skrll@NetBSD.org, mlh@goathill.org
Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on
-current)
Date: Tue, 30 Aug 2022 12:45:24 -0400 (EDT)
skrll@NetBSD.org wrote:
> Synopsis: Certain usb devices can no longer be mounted on -current
>
> State-Changed-From-To: open->feedback
> State-Changed-By: skrll@NetBSD.org
> State-Changed-When: Tue, 30 Aug 2022 05:28:09 +0000
> State-Changed-Why:
> Please bisect it further.
?
Why does it no longer configure to use sd0 as it used to :
Aug 29 13:45:52 tiamat /netbsd: [ 95.6407866] sd0 at scsibus0 target 0 lun 0: <FSL SEMI, FSL MASS STORAGE, 0001> disk removable
Aug 29 13:45:52 tiamat /netbsd: [ 95.6507884] sd0: fabricating a geometry
$ disklabel sd0
disklabel: /dev/rsd0: Device not configured
I have no idea at this point.
From: Robert Elz <kre@munnari.OZ.AU>
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on -current)
Date: Wed, 31 Aug 2022 18:19:55 +0700
Date: Tue, 30 Aug 2022 16:50:02 +0000 (UTC)
From: mlh@goathill.org (MLH)
Message-ID: <20220830165002.2D1E41A923A@mollari.NetBSD.org>
| skrll@NetBSD.org wrote:
| > Please bisect it further.
|
| ?
What Nick (skrll@) asked you to do, is to try running kernels from
the period between when you know it worked, and when you are seeing
the problem, and find out exactly when things changed.
Since you are seeing an issue, and most of us are not, you might be
the only person who can do that.
It worked in mid January, fails in late August, so try something from
early May. If that works, then try something from late June or
early July, and if that works, from early August, ... keep getting
to a narrower and narrower time range until you are comparing systems
from sources just an hour or so apart, where the earlier one works,
and the later one fails.
Obviously (I hope) if early May failed, you instead pick a time between
Mid Jan and early May - so probably about the end of the first week in
March (you don't have to be highly accurate in picking the mid point
of the time interval - but the closer you are the less iterations you're
likely to need to make, unless you get lucky, and that rarely seems to
happen).
So each time a mid point test succeeds (sd0 works) you pick half way
between that time, and the current end (a known failed system). Each
time it fails, you pick the mid point between the current beginning
(a known working version) and the current one (now known to fail).
You now have a new (begin, end) time pair (where one of those will be
the mid point of the last test, and the other is unchanged from that
one), you pick somewhere approximately at the middle of that range,
and try again. This is bisection. (A similar technique is sometimes
used in mathematics to solve problems that are difficult other ways.)
| Why does it no longer configure to use sd0 as it used to :
This we don't know - but I'm running 9.99.99 and my sd devices all
work just fine. So it is probable that only you can work this out.
Once you find just when (as close as you can get) the breaking change
happened, let us know, and someone might be able to tell what the problem
might be, just from looking at what changed about that time.
kre
From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: port-amd64/56987: Certain usb devices can no longer be mounted
on -current
Date: Sun, 15 Jan 2023 21:39:50 +0000
The submitter wrote to the main gnats log inbox with the following,
about an unspecified PR but probably this one:
(To reply to a PR, send to gnats-bugs@ using the PR number in the
Subject: line in the form seen above. If in doubt, crosscheck after a
few hours that the message arrived by looking at the PR webpage. If
you run into problems, ask on irc or contact me directly. Note that
the automated nag mails include directions for replying, but just
replying to them doesn't do anything useful. Mail sent to gnats@ or
gnats-admin@ goes into a sewer that receives Cc:'s of all gnats
transactions, and stuff sent there can languish for months if it
doesn't get missed entirely.)
------
From: MLH <mlh@goathill.org>
To: NetBSD Problem Report DB Administrator <gnats@netbsd.org>
Subject: Re: Reminder of 1 NetBSD Problem Report awaiting feedback
Date: Sun, 20 Nov 2022 13:07:23 -0500 (EST)
NetBSD Problem Report DB Administrator wrote:
> This is an infrequent reminder that there is 1 Problem Report
> (PR) of yours in the NetBSD GNATS database in "feedback" state.
I could not build a version closer than the early May I had first
seen the problem with so could not provide any further information.
I will try newer releases as they become buildable for me, hoping
someone else discovers the issue. There were a number of other
issues with the August 9.99.99 release so I will just stay with
the Jan 9.99.93 release for now, as it works properly with everything
I use.
From: mlh@goathill.org (MLH)
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: port-amd64/56987: problems with mounting usb memory devices on -current
Date: Tue, 28 Mar 2023 09:20:27 -0400 (EDT)
gnats-admin@netbsd.org wrote:
> Thank you very much for your problem report.
> It has the internal identification `port-amd64/56987'.
> The individual assigned to look at your
> report is: port-amd64-maintainer.
>
> >Category: port-amd64
> >Responsible: port-amd64-maintainer
> >Synopsis: Certain usb devices can no longer be mounted on -current
> >Arrival-Date: Tue Aug 30 00:15:00 +0000 2022
Note that at the current time I cannot build the kernels required to provide
more information.
From: mlh@goathill.org (MLH)
To: MLH <mlh@goathill.org>
Cc: gnats-bugs@netbsd.org, port-amd64-maintainer@netbsd.org,
netbsd-bugs@netbsd.org, gnats-admin@netbsd.org, skrll@NetBSD.org
Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on
-current)
Date: Sat, 6 May 2023 19:22:51 -0400 (EDT)
MLH wrote:
> skrll@NetBSD.org wrote:
> > Synopsis: Certain usb devices can no longer be mounted on -current
> >
> > State-Changed-From-To: open->feedback
> > State-Changed-By: skrll@NetBSD.org
> > State-Changed-When: Tue, 30 Aug 2022 05:28:09 +0000
> > State-Changed-Why:
>
> > Please bisect it further.
Using NetBSD 10.99.4 (USBDEBUG) #0: Sat May 6 18:32:06 EDT 2023
And one of the usb devices that used to work but no longer has since Jan 2022 without using 9.99.93 :
When attached:
May 6 19:07:51 tiamat /netbsd: [ 21.8112624] uhub4: at uhub1 port 7 (addr 3) disconnected
May 6 19:07:51 tiamat /netbsd: [ 21.8112624] uhub4: at uhub1 port : vendor 214b (0x214b) USB2.0 HUB (0x7000), class 9/0, rev 2.00/1.00, addr 5
May 6 19:07:51 tiamat /netbsd: [ 67.5011090] uhub4: single transaction translator
May 6 19:07:51 tiamat /netbsd: [ 67.5211090] uhub4: 4 ports with 4 removable, self powered
May 6 19:07:52 tiamat /netbsd: [ 68.4011060] umass0 at uhub4 port 2 configuration 1 interface 0
May 6 19:07:52 tiamat /netbsd: [ 68.4011060] umass0: Lezyne (0x2b29) GPS Device (0x0055), rev 2.00/1.00, addr 6
May 6 19:07:52 tiamat /netbsd: [ 68.4011060] umass0: using SCSI over Bulk-Only
May 6 19:07:52 tiamat /netbsd: [ 68.4111060] scsibus0 at umass0: 2 targets, 1 lun per target
May 6 19:07:52 tiamat /netbsd: [ 68.4111060] uhidev3 at uhub4 port 2 configuration 1 interface 1
May 6 19:07:52 tiamat /netbsd: [ 68.4111060] uhidev3: Lezyne (0x2b29) GPS Device (0x0055), rev 2.00/1.00, addr 6, iclass 3/0
May 6 19:07:52 tiamat /netbsd: [ 68.4111060] uhid4 at uhidev3: input=64, output=64, feature=0
May 6 19:07:52 tiamat /netbsd: [ 68.8211046] uhub5 at uhub4 port 3: vendor 214b (0x214b) USB2.0 HUB (0x7000), class 9/0, rev 2.00/1.00, addr 7
May 6 19:07:52 tiamat /netbsd: [ 68.8211046] uhub5 at uhub transaction translator
May 6 19:07:52 tiamat /netbsd: [ 68.8211046] uhub5: 4 ports with 4 removable, self powered
$ disklabel sd0
disklabel: /dev/rsd0: Device not configured
So can't be mounted
And what should be something like this below is missing:
sd0 at scsibus0 target 0 lun 0: <FSL SEMI, FSL MASS STORAGE, 0001> disk removable
sd0: fabricating a geometry
When detached:
May 6 19:09:31 tiamat /netbsd: [ 166.9107756] scsibus0: detached
May 6 19:09:31 tiamat /netbsd: [ 166.9107756] umass0: detached
May 6 19:09:31 tiamat /netbsd: [ 166.9107756] umass0: at uhub4 port 2 (addr 6) disconnected
May 6 19:09:31 tiamat /netbsd: [ 166.9107756] uhid4: detached
May 6 19:09:31 tiamat /netbsd: [ 166.9107756] uhidev3: detached
May 6 19:09:31 tiamat /netbsd: [ 166.9107756] uhidev3: at uhub4 port 2 (addr 6) disconnected
So what is missing?
From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: port-amd64/56987: Certain usb devices can no longer be mounted
on -current
Date: Fri, 12 May 2023 20:00:16 +0000
The submitter wrote to the gnats administrator address (which is not a
useful place to write to and messages there often don't get seen --
please comment on PRs by writing to gnats-bugs@) with the following:
------
From: MLH <mlh@goathill.org>
To: NetBSD Problem Report DB Administrator <gnats@netbsd.org>
CC: mlh@goathill.org
Subject: Re: Reminder of 1 NetBSD Problem Report awaiting feedback
Date: Thu, 4 May 2023 16:17:14 -0400 (EDT)
Using new hardware I built -current NetBSD 10.99.4 Thu May 4
16:04:21 EDT 2023, and the original problem still persists. NetBSD
9.3 was the last version that could mount several of my usb devices.
From: MLH <mlh@goathill.org>
To: NetBSD Problem Report DB Administrator <gnats@netbsd.org>
Subject: Re: Reminder of 1 NetBSD Problem Report awaiting feedback
Date: Fri, 5 May 2023 20:17:47 -0400 (EDT)
> Using new hardware I built -current NetBSD 10.99.4 Thu May 4
> 16:04:21 EDT 2023, and the original problem still persists. NetBSD
> 9.3 was the last version that could mount several of my usb devices.
Sorry but I meant 9.99.3 Jan 14 2022
State-Changed-From-To: feedback->open
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Sun, 14 May 2023 00:41:13 +0000
State-Changed-Why:
Submitter cannot test
From: mlh@goathill.org (MLH)
To: gnats-bugs@netbsd.org
Cc: port-amd64-maintainer@netbsd.org, netbsd-bugs@netbsd.org,
gnats-admin@netbsd.org, dholland@NetBSD.org, mlh@goathill.org
Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on
-current)
Date: Fri, 19 May 2023 15:29:37 -0400 (EDT)
dholland@NetBSD.org wrote:
> Synopsis: Certain usb devices can no longer be mounted on -current
>
> State-Changed-From-To: feedback->open
> State-Changed-By: dholland@NetBSD.org
> State-Changed-When: Sun, 14 May 2023 00:41:13 +0000
> State-Changed-Why:
> Submitter cannot test
NetBSD 10.99.4 (HDMIAUDIO) #1: Thu May 18 17:09:01 EDT 2023 still
does not work with these usb devices
insert :
May 19 15:20:00 tiamat /netbsd: [ 71.8609145] umass0 at uhub4 port 2 configuration 1 interface 0
May 19 15:20:00 tiamat /netbsd: [ 71.8609145] umass0 aLezyne (0x2b29) GPS Device (0x0055), rev 2.00/1.00, addr 3
May 19 15:20:00 tiamat /netbsd: [ 71.8609145] umass0: using SCSI over Bulk-Only
May 19 15:20:00 tiamat /netbsd: [ 71.8709146] scsibus0 at umass0: 2 targets, 1 lun per target
May 19 15:20:00 tiamat /netbsd: [ 71.8709146] uhidev3 at uhub4 port 2 configuration 1 interface 1
May 19 15:20:00 tiamat /netbsd: [ 71.8709146] uhidev3: Lezyne (0x2b29) GPS Device (0x0055), rev 2.00/1.00, addr 3, iclass 3/0
May 19 15:20:00 tiamat /netbsd: [ 71.8709146] uhid4 at uhidev3: input=64, output=64, feature=0
mount attempt:
/u/m0/: Device not configured.
From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted
on -current)
Date: Sat, 20 May 2023 13:53:19 +0200
You have not shown enough of the dmesg and what mount command you tried,
so it is hard to guess what happened.
Martin
From: mlh@goathill.org (MLH)
To: gnats-bugs@netbsd.org
Cc: port-amd64-maintainer@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org, mlh@goathill.org
Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on
-current)
Date: Sat, 20 May 2023 12:06:27 -0400 (EDT)
Martin Husemann wrote:
> The following reply was made to PR port-amd64/56987; it has been noted by GNATS.
>
> From: Martin Husemann <martin@duskware.de>
> To: gnats-bugs@netbsd.org
> Cc:
> Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted
> on -current)
> Date: Sat, 20 May 2023 13:53:19 +0200
>
> You have not shown enough of the dmesg and what mount command you tried,
> so it is hard to guess what happened.
(dmesg shown below)
As I mentioned earlier, these five usb devices have worked properly
with NetBSD for a number of years (about 15 years for the oldest
one which just recently finally died and the newest is five years
old) and now on three totally different motherboards. Only after
NetBSD 9.99.93, as mentioned before, do they no longer mount. I
only have two of them currently at hand to work with though. Two
died last year and one is loaned out. The two I have still work
fine with NetBSD 9.99.93 so I have to boot that to work with them.
I also shoulod note that I very recently (this month) upgraded my
box from about an 8-10 yr old Gigabyte Intel motherboard to a new
ASUS AMD motherboard and the behavior is the same regardless of
the motherboard usb support.
insert #1 using NetBSD 10.99.4 Thu May 18 17:09:01 EDT 2023 :
May 20 11:32:23 tiamat /netbsd: [ 72813.4894663] umass0 at uhub4 port 2 configuration 1 interface 0
May 20 11:32:23 tiamat /netbsd: [ 72813.4894663] umass0: Lezyne (0x2b29) GPS Device (0x0055), rev 2.00/1.00, addr 4
May 20 11:32:23 tiamat /netbsd: [ 72813.4894663] umass0: using SCSI over Bulk-Only
May 20 11:32:23 tiamat /netbsd: [ 72813.4994665] scsibus0 at umass0: 2 targets, 1 lun per target
May 20 11:32:23 tiamat /netbsd: [ 72813.4994665] uhidev3 at uhub4 port 2 configuration 1 interface 1
May 20 11:32:23 tiamat /netbsd: [ 72813.4994665] uhidev3: Lezyne (0x2b29) GPS Device (0x0055), rev 2.00/1.00, addr 4, iclass 3/0
May 20 11:32:23 tiamat /netbsd: [ 72813.4994665] uhid4 at uhidev3: input=64, output=64, feature=0
this used to be followed by something like (from 9.99.93) :
Aug 29 13:45:52 tiamat /netbsd: [ 95.6407866] sd0 at scsibus0 target 0 lun 0: <FSL SEMI, FSL MASS STORAGE, 0001> disk remova
Aug 29 13:45:52 tiamat /netbsd: [ 95.6507884] sd0: fabricating a geometry
This unit used to mount as /dev/sd0a :
$ disklabel sd0
disklabel: /dev/rsd0: Device not configured
I don't have a copy of the disklabel using 9.99.93 for this device but can get it if needed
----
#2 is a different usb device by the same manufacturer
insert #2 using NetBSD 10.99.4 Thu May 18 17:09:01 EDT 2023 :
May 20 11:39:07 tiamat /netbsd: [ 73218.2328773] umass0 at uhub4 port 2 configuration 1 interface 0
May 20 11:39:07 tiamat /netbsd: [ 73218.2328773] umass0: Lezyne (0x2b29) GPS Device (0x0055), rev 2.00/1.00, addr 5
May 20 11:39:07 tiamat /netbsd: [ 73218.2328773] umass0: using SCSI over Bulk-Only
May 20 11:39:07 tiamat /netbsd: [ 73218.2428774] scsibus0 at umass0: 2 targets, 1 lun per target
May 20 11:39:07 tiamat /netbsd: [ 73218.2428774] uhidev3 at uhub4 port 2 configuration 1 interface 1
May 20 11:39:07 tiamat /netbsd: [ 73218.2428774] uhidev3: Lezyne (0x2b29) GPS Device (0x0055), rev 2.00/1.00, addr 5, iclass 3/0
May 20 11:39:07 tiamat /netbsd: [ 73218.2428774] uhid4 at uhidev3: input=64, output=64, feature=0
this used to be followed by (from 9.99.93) :
Aug 29 13:45:52 tiamat /netbsd: [ 95.6407866] sd0 at scsibus0 target 0 lun 0: <FSL SEMI, FSL MASS STORAGE, 0001> disk removable
Aug 29 13:45:52 tiamat /netbsd: [ 95.6507884] sd0: fabricating a geometry
Note that up to the sd0 lines, the umass, scsibus and uhid* lines
are identical before and after the changes were made that stopped
allowing them to be mounted.
This unit used to mount as /dev/sd0e :
$ disklabel sd0
# /dev/rsd0:
type: SCSI
disk: Flash Reader
label: fictitious
flags: removable
bytes/sector: 512
sectors/track: 32
tracks/cylinder: 64
sectors/cylinder: 2048
cylinders: 122112
total sectors: 250085376
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # microseconds
track-to-track seek: 0 # microseconds
drivedata: 0
5 partitions:
# size offset fstype [fsize bsize cpg/sgs]
d: 250085376 0 unused 0 0 # (Cyl. 0 - 122111)
e: 250052608 32768 MSDOS # (Cyl. 16 - 122111)
disklabel: boot block size 0
disklabel: super block size 0
However, using NetBSD 10.99.4 :
$ disklabel sd0
disklabel: /dev/rsd0: Device not configured
I normally use AMD(8) to automount these devices but can manually
mount them as msdos filesystems. AMD entries are:
m0 type:=pcfs;opts:=rw,noatime;dev:=/dev/sd0e
m1 type:=pcfs;opts:=rw,noatime;dev:=/dev/sd1e
m2 type:=pcfs;opts:=rw,noatime;dev:=/dev/sd2e
and
g0 type:=pcfs;opts:=rw,noatime;dev:=/dev/sd0a
g1 type:=pcfs;opts:=rw,noatime;dev:=/dev/sd1a
g2 type:=pcfs;opts:=rw,noatime;dev:=/dev/sd2a
-----
dmesg:
[ 1.000000] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003,
[ 1.000000] 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013,
[ 1.000000] 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023
[ 1.000000] The NetBSD Foundation, Inc. All rights reserved.
[ 1.000000] Copyright (c) 1982, 1986, 1989, 1991, 1993
[ 1.000000] The Regents of the University of California. All rights reserved.
[ 1.000000] NetBSD 10.99.4 (HDMIAUDIO) #1: Thu May 18 17:09:01 EDT 2023
[ 1.000000] -----------:/opt/obj/amd64/usr/src/sys/arch/amd64/compile/HDMIAUDIO
[ 1.000000] total memory = 32678 MB
[ 1.000000] avail memory = 31591 MB
[ 1.000000] timecounter: Timecounters tick every 10.000 msec
[ 1.000000] Kernelized RAIDframe activated
[ 1.000000] RTC BIOS diagnostic error 0xf<fixed_disk,invalid_time>
[ 1.000000] timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100
[ 1.000004] efi: systbl at pa cbb59018
[ 1.000004] mainbus0 (root)
[ 1.000004] ACPI: RSDP 0x00000000CA6CE014 000024 (v02 ALASKA)
[ 1.000004] ACPI: XSDT 0x00000000CA6CD728 0000E4 (v01 ALASKA A M I 01072009 AMI 01000013)
[ 1.000004] ACPI: FACP 0x00000000CA6BE000 000114 (v06 ALASKA A M I 01072009 AMI 00010013)
[ 1.000004] ACPI: DSDT 0x00000000CA6B2000 00B8C9 (v02 ALASKA A M I 01072009 INTL 20120913)
[ 1.000004] ACPI: FACS 0x00000000CAE59000 000040
[ 1.000004] ACPI: SSDT 0x00000000CA6C4000 008CE9 (v02 AMD AmdTable 00000002 MSFT 04000000)
[ 1.000004] ACPI: SSDT 0x00000000CA6C0000 003B8E (v02 AMD AMD AOD 00000001 INTL 20120913)
[ 1.000004] ACPI: SSDT 0x00000000CA6BF000 0001AD (v02 ALASKA CPUSSDT 01072009 AMI 01072009)
[ 1.000004] ACPI: FIDT 0x00000000CA6B1000 00009C (v01 ALASKA A M I 01072009 AMI 00010013)
[ 1.000004] ACPI: FPDT 0x00000000CA5B7000 000044 (v01 ALASKA A M I 01072009 AMI 01000013)
[ 1.000004] ACPI: MCFG 0x00000000CA6AF000 00003C (v01 ALASKA A M I 01072009 MSFT 00010013)
[ 1.000004] ACPI: HPET 0x00000000CA6AE000 000038 (v01 ALASKA A M I 01072009 AMI 00000005)
[ 1.000004] ACPI: IVRS 0x00000000CA6AC000 0000D0 (v02 AMD AmdTable 00000001 AMD 00000001)
[ 1.000004] ACPI: BGRT 0x00000000CA6AB000 000038 (v01 ALASKA A M I 01072009 AMI 00010013)
[ 1.000004] ACPI: WPBT 0x00000000CA5CC000 00003C (v01 ALASKA A M I 00000001 ASUS 00000001)
[ 1.000004] ACPI: TPM2 0x00000000CA5CB000 00004C (v04 ALASKA A M I 00000001 AMI 00000000)
[ 1.000004] ACPI: PCCT 0x00000000CA5CA000 00006E (v02 AMD AmdTable 00000001 AMD 00000001)
[ 1.000004] ACPI: SSDT 0x00000000CA5C6000 0030FB (v02 AMD AmdTable 00000001 AMD 00000001)
[ 1.000004] ACPI: CRAT 0x00000000CA5C5000 000B90 (v01 AMD AmdTable 00000001 AMD 00000001)
[ 1.000004] ACPI: CDIT 0x00000000CA5C4000 000029 (v01 AMD AmdTable 00000001 AMD 00000001)
[ 1.000004] ACPI: SSDT 0x00000000CA5C3000 000259 (v02 AMD ArticDGP 00000001 INTL 20120913)
[ 1.000004] ACPI: SSDT 0x00000000CA5C1000 0010C1 (v02 AMD ArticTPX 00000001 INTL 20120913)
[ 1.000004] ACPI: SSDT 0x00000000CA5C0000 00052C (v02 AMD ArticNOI 00000001 INTL 20120913)
[ 1.000004] ACPI: SSDT 0x00000000CA5BC000 003E6E (v02 AMD ArticN 00000001 INTL 20120913)
[ 1.000004] ACPI: WSMT 0x00000000CA5BB000 000028 (v01 ALASKA A M I 01072009 AMI 00010013)
[ 1.000004] ACPI: APIC 0x00000000CA5BA000 00015E (v04 ALASKA A M I 01072009 AMI 00010013)
[ 1.000004] ACPI: SSDT 0x00000000CA5B9000 00007D (v02 AMD ArticDIS 00000001 INTL 20120913)
[ 1.000004] ACPI: SSDT 0x00000000CA5B8000 0000BF (v01 AMD AmdTable 00001000 INTL 20120913)
[ 1.000004] ACPI: 11 ACPI AML tables successfully acquired and loaded
[ 1.000004] ioapic0 at mainbus0 apid 13: pa 0xfec00000, version 0x21, 24 pins
[ 1.000004] ioapic1 at mainbus0 apid 14: pa 0xfec01000, version 0x21, 32 pins
[ 1.000004] cpu0 at mainbus0 apid 0
[ 1.000004] cpu0: Use mfence to serialize rdtsc
[ 1.000004] cpu0: AMD Ryzen 5 5600X 6-Core Processor , id 0xa20f12
[ 1.000004] cpu0: node 0, package 0, core 0, smt 0
[ 1.000004] cpu0: SVM disabled by the BIOS
[ 1.000004] cpu1 at mainbus0 apid 2
[ 1.000004] cpu1: AMD Ryzen 5 5600X 6-Core Processor , id 0xa20f12
[ 1.000004] cpu1: node 0, package 0, core 1, smt 0
[ 1.000004] cpu2 at mainbus0 apid 4
[ 1.000004] cpu2: AMD Ryzen 5 5600X 6-Core Processor , id 0xa20f12
[ 1.000004] cpu2: node 0, package 0, core 2, smt 0
[ 1.000004] cpu3 at mainbus0 apid 6
[ 1.000004] cpu3: AMD Ryzen 5 5600X 6-Core Processor , id 0xa20f12
[ 1.000004] cpu3: node 0, package 0, core 3, smt 0
[ 1.000004] cpu4 at mainbus0 apid 8
[ 1.000004] cpu4: AMD Ryzen 5 5600X 6-Core Processor , id 0xa20f12
[ 1.000004] cpu4: node 0, package 0, core 4, smt 0
[ 1.000004] cpu5 at mainbus0 apid 10
[ 1.000004] cpu5: AMD Ryzen 5 5600X 6-Core Processor , id 0xa20f12
[ 1.000004] cpu5: node 0, package 0, core 5, smt 0
[ 1.000004] cpu6 at mainbus0 apid 1
[ 1.000004] cpu6: AMD Ryzen 5 5600X 6-Core Processor , id 0xa20f12
[ 1.000004] cpu6: node 0, package 0, core 0, smt 1
[ 1.000004] cpu7 at mainbus0 apid 3
[ 1.000004] cpu7: AMD Ryzen 5 5600X 6-Core Processor , id 0xa20f12
[ 1.000004] cpu7: node 0, package 0, core 1, smt 1
[ 1.000004] cpu8 at mainbus0 apid 5
[ 1.000004] cpu8: AMD Ryzen 5 5600X 6-Core Processor , id 0xa20f12
[ 1.000004] cpu8: node 0, package 0, core 2, smt 1
[ 1.000004] cpu9 at mainbus0 apid 7
[ 1.000004] cpu9: AMD Ryzen 5 5600X 6-Core Processor , id 0xa20f12
[ 1.000004] cpu9: node 0, package 0, core 3, smt 1
[ 1.000004] cpu10 at mainbus0 apid 9
[ 1.000004] cpu10: AMD Ryzen 5 5600X 6-Core Processor , id 0xa20f12
[ 1.000004] cpu10: node 0, package 0, core 4, smt 1
[ 1.000004] cpu11 at mainbus0 apid 11
[ 1.000004] cpu11: AMD Ryzen 5 5600X 6-Core Processor , id 0xa20f12
[ 1.000004] cpu11: node 0, package 0, core 5, smt 1
[ 1.000004] acpi0 at mainbus0: Intel ACPICA 20221020
[ 1.000004] acpi0: X/RSDT: OemId <ALASKA, A M I ,01072009>, AslId <AMI ,01000013>
[ 1.000004] acpi0: autoconfiguration error: invalid PCI address for D003
[ 1.000004] acpi0: MCFG: segment 0, bus 0-127, address 0x00000000f0000000
[ 1.000004] acpi0: SCI interrupting at int 9
[ 1.000004] acpi0: fixed power button present
[ 1.000004] timecounter: Timecounter "ACPI-Safe" frequency 3579545 Hz quality 900
[ 1.043448] hpet0 at acpi0: high precision event timer (mem 0xfed00000-0xfed00400)
[ 1.043448] timecounter: Timecounter "hpet0" frequency 14318180 Hz quality 2000
[ 1.045433] AMDN (PNP0C01) at acpi0 not configured
[ 1.045433] attimer1 at acpi0 (TMR, PNP0100): io 0x40-0x43 irq 0
[ 1.045433] pcppi1 at acpi0 (SPKR, PNP0800): io 0x61
[ 1.045433] spkr0 at pcppi1: PC Speaker
[ 1.045433] wsbell at spkr0 not configured
[ 1.045433] midi0 at pcppi1: PC speaker
[ 1.045433] sysbeep0 at pcppi1
[ 1.045433] com0 at acpi0 (UAR1, PNP0501-0): io 0x3f8-0x3ff irq 4
[ 1.045433] com0: ns16550a, 16-byte FIFO
[ 1.045433] acpibut0 at acpi0 (PWRB, PNP0C0C-170): ACPI Power Button
[ 1.045433] GPIO (AMDI0030) at acpi0 not configured
[ 1.045433] TPM (MSFT0101) at acpi0 not configured
[ 1.045433] PTIO (AMDIF030) at acpi0 not configured
[ 1.045433] acpiwmi0 at acpi0 (AWW0, PNP0C14-AWW): ACPI WMI Interface
[ 1.045433] acpiwmibus at acpiwmi0 not configured
[ 1.045433] acpiwmi1 at acpi0 (AMW0, PNP0C14-ASUSWMI): ACPI WMI Interface
[ 1.045433] wmieeepc0 at acpiwmi1: Asus Eee PC WMI mappings
[ 1.045433] acpiwmi2 at acpi0 (ABAW, PNP0C14-AsusBACKUPWMI): ACPI WMI Interface
[ 1.045433] acpiwmibus at acpiwmi2 not configured
[ 1.045433] acpiwmi3 at acpi0 (ACCE, PNP0C14-ASUSCONTROLCENTER): ACPI WMI Interface
[ 1.045433] acpiwmibus at acpiwmi3 not configured
[ 1.045433] acpiwmi4 at acpi0 (AOD, PNP0C14-AOD): ACPI WMI Interface
[ 1.045433] acpiwmibus at acpiwmi4 not configured
[ 1.045433] attimer1: attached to pcppi1
[ 1.045433] pci0 at mainbus0 bus 0: configuration mode 1
[ 1.045433] pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
[ 1.045433] amdsmn0 at pci0 dev 0 function 0: AMD System Management Network
[ 1.045433] amdzentemp0 at amdsmn0: AMD CPU Temperature Sensors (Family19h)
[ 1.045433] AMD Family17h/7xh IOMMU (IOMMU system) at pci0 dev 0 function 2 not configured
[ 1.045433] pchb0 at pci0 dev 1 function 0: AMD 17h/7xh Host Bridge (rev. 0x00)
[ 1.045433] ppb0 at pci0 dev 1 function 1: AMD 17h/7xh PCIe (rev. 0x00)
[ 1.045433] ppb0: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x4 @ 16.0GT/s
[ 1.045433] pci1 at ppb0 bus 1
[ 1.045433] pci1: i/o space, memory space enabled, rd/line, wr/inv ok
[ 1.045433] nvme0 at pci1 dev 0 function 0: Samsung Electronics (3rd vendor ID) PM9A1 M.2 NVMe SSD (rev. 0x00)
[ 1.045433] nvme0: NVMe 1.3
[ 1.045433] nvme0: for admin queue interrupting at msix0 vec 0
[ 1.045433] nvme0: Samsung SSD 980 PRO with Heatsink 2TB, firmware 5B2QGXA7, serial S6WRNS0W229578J
[ 1.045433] nvme0: for io queue 1 interrupting at msix0 vec 1 affinity to cpu0
[ 1.045433] nvme0: for io queue 2 interrupting at msix0 vec 2 affinity to cpu1
[ 1.045433] nvme0: for io queue 3 interrupting at msix0 vec 3 affinity to cpu2
[ 1.045433] nvme0: for io queue 4 interrupting at msix0 vec 4 affinity to cpu3
[ 1.045433] nvme0: for io queue 5 interrupting at msix0 vec 5 affinity to cpu4
[ 1.045433] nvme0: for io queue 6 interrupting at msix0 vec 6 affinity to cpu5
[ 1.045433] nvme0: for io queue 7 interrupting at msix0 vec 7 affinity to cpu6
[ 1.045433] nvme0: for io queue 8 interrupting at msix0 vec 8 affinity to cpu7
[ 1.045433] nvme0: for io queue 9 interrupting at msix0 vec 9 affinity to cpu8
[ 1.045433] nvme0: for io queue 10 interrupting at msix0 vec 10 affinity to cpu9
[ 1.045433] nvme0: for io queue 11 interrupting at msix0 vec 11 affinity to cpu10
[ 1.045433] nvme0: for io queue 12 interrupting at msix0 vec 12 affinity to cpu11
[ 1.045433] ld0 at nvme0 nsid 1
[ 1.045433] ld0: 1863 GB, 243201 cyl, 255 head, 63 sec, 512 bytes/sect x 3907029168 sectors
[ 1.045433] ppb1 at pci0 dev 1 function 2: AMD 17h/7xh PCIe (rev. 0x00)
[ 1.045433] ppb1: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x8 @ 16.0GT/s
[ 1.045433] ppb1: link is x4 @ 8.0GT/s
[ 1.045433] pci2 at ppb1 bus 2
[ 1.045433] pci2: i/o space, memory space enabled, rd/line, wr/inv ok
[ 1.045433] xhci0 at pci2 dev 0 function 0: AMD 500 Series xHCI (rev. 0x00)
[ 1.045433] xhci0: 64-bit DMA
[ 1.045433] xhci0: interrupting at msix1 vec 0
[ 1.045433] xhci0: xHCI version 1.10
[ 1.045433] usb0 at xhci0: USB revision 3.1
[ 1.045433] usb1 at xhci0: USB revision 2.0
[ 1.045433] ahcisata0 at pci2 dev 0 function 1: AMD 500 Series AHCI (rev. 0x00)
[ 1.045433] ahcisata0: 64-bit DMA
[ 1.045433] ahcisata0: AHCI revision 1.31, 6 ports, 32 slots, CAP 0xef36ff25<SXS,PSC,SSC,PMD,SPM,SAM,ISS=0x3=Gen3,SCLO,SAL,SALP,SSS,SSNTF,SNCQ,S64A>
[ 1.045433] ahcisata0: interrupting at msi2 vec 0
[ 1.045433] atabus0 at ahcisata0 channel 0
[ 1.045433] atabus1 at ahcisata0 channel 1
[ 1.045433] atabus2 at ahcisata0 channel 2
[ 1.045433] atabus3 at ahcisata0 channel 3
[ 1.045433] atabus4 at ahcisata0 channel 4
[ 1.045433] atabus5 at ahcisata0 channel 5
[ 1.045433] ppb2 at pci2 dev 0 function 2: AMD 500 Series PCIe (rev. 0x00)
[ 1.045433] ppb2: PCI Express capability version 2 <Upstream Port of PCI-E Switch>
[ 1.045433] pci3 at ppb2 bus 3
[ 1.045433] pci3: i/o space, memory space enabled, rd/line, wr/inv ok
[ 1.045433] ppb3 at pci3 dev 0 function 0: AMD 500 Series PCIe (rev. 0x00)
[ 1.045433] ppb3: PCI Express capability version 2 <Downstream Port of PCI-E Switch> x1 @ 8.0GT/s
[ 1.045433] pci4 at ppb3 bus 4
[ 1.045433] pci4: i/o space, memory space enabled, rd/line, wr/inv ok
[ 1.045433] ppb4 at pci3 dev 1 function 0: AMD 500 Series PCIe (rev. 0x00)
[ 1.045433] ppb4: PCI Express capability version 2 <Downstream Port of PCI-E Switch> x1 @ 8.0GT/s
[ 1.045433] pci5 at ppb4 bus 5
[ 1.045433] pci5: i/o space, memory space enabled, rd/line, wr/inv ok
[ 1.045433] ppb5 at pci3 dev 2 function 0: AMD 500 Series PCIe (rev. 0x00)
[ 1.045433] ppb5: PCI Express capability version 2 <Downstream Port of PCI-E Switch> x1 @ 8.0GT/s
[ 1.045433] pci6 at ppb5 bus 6
[ 1.045433] pci6: i/o space, memory space enabled, rd/line, wr/inv ok
[ 1.045433] ppb6 at pci3 dev 3 function 0: AMD 500 Series PCIe (rev. 0x00)
[ 1.045433] ppb6: PCI Express capability version 2 <Downstream Port of PCI-E Switch> x1 @ 8.0GT/s
[ 1.045433] ppb6: link is x1 @ 2.5GT/s
[ 1.045433] pci7 at ppb6 bus 7
[ 1.045433] pci7: i/o space, memory space enabled, rd/line, wr/inv ok
[ 1.045433] jmide0 at pci7 dev 0 function 0: JMicron Technology JMB363 SATA/PATA Controller (rev. 0x10)
[ 1.045433] jmide0: 1 PATA port, 2 SATA ports
[ 1.045433] jmide0: interrupting at ioapic1 pin 7
[ 1.045433] ahcisata1 at jmide0
[ 1.045433] ahcisata1: AHCI revision 1.10, 2 ports, 32 slots, CAP 0xc722ff01<PSC,SSC,PMD,SPM,ISS=0x2=Gen2,SCLO,SAL,SALP,SNCQ,S64A>
[ 1.045433] atabus6 at ahcisata1 channel 0
[ 1.045433] atabus7 at ahcisata1 channel 1
[ 1.045433] jmide0: PCI IDE interface used
[ 1.045433] jmide0: bus-master DMA support present
[ 1.045433] jmide0: primary channel wired to native-PCI mode
[ 1.045433] jmide0: primary channel is unused
[ 1.045433] jmide0: secondary channel wired to native-PCI mode
[ 1.045433] jmide0: secondary channel is PATA
[ 1.045433] atabus8 at jmide0 channel 1
[ 1.045433] ppb7 at pci3 dev 4 function 0: AMD 500 Series PCIe (rev. 0x00)
[ 1.045433] ppb7: PCI Express capability version 2 <Downstream Port of PCI-E Switch> x4 @ 8.0GT/s
[ 1.045433] pci8 at ppb7 bus 8
[ 1.045433] pci8: i/o space, memory space enabled, rd/line, wr/inv ok
[ 1.045433] ppb8 at pci3 dev 8 function 0: AMD 500 Series PCIe (rev. 0x00)
[ 1.045433] ppb8: PCI Express capability version 2 <Downstream Port of PCI-E Switch> x1 @ 8.0GT/s
[ 1.045433] pci9 at ppb8 bus 9
[ 1.045433] pci9: i/o space, memory space enabled, rd/line, wr/inv ok
[ 1.045433] ppb9 at pci3 dev 9 function 0: AMD 500 Series PCIe (rev. 0x00)
[ 1.045433] ppb9: PCI Express capability version 2 <Downstream Port of PCI-E Switch> x1 @ 8.0GT/s
[ 1.045433] ppb9: link is x1 @ 2.5GT/s
[ 1.045433] pci10 at ppb9 bus 10
[ 1.045433] pci10: i/o space, memory space enabled, rd/line, wr/inv ok
[ 1.045433] re0 at pci10 dev 0 function 0: RealTek 8168/8111 PCIe Gigabit Ethernet (rev. 0x15)
[ 1.045433] re0: interrupting at msix3 vec 0
[ 1.045433] re0: RTL8168H/8111H (0x5400)
[ 1.045433] re0: Ethernet address 58:11:22:c5:d6:1a
[ 1.045433] re0: using 256 tx descriptors
[ 1.045433] rgephy0 at re0 phy 7: RTL8251 1000BASE-T media interface, rev. 0
[ 1.045433] rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, auto
[ 1.045433] pchb1 at pci0 dev 2 function 0: AMD 17h/7xh Host Bridge (rev. 0x00)
[ 1.045433] pchb2 at pci0 dev 3 function 0: AMD 17h/7xh Host Bridge (rev. 0x00)
[ 1.045433] ppb10 at pci0 dev 3 function 1: AMD 17h/7xh PCIe (rev. 0x00)
[ 1.045433] ppb10: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x16 @ 16.0GT/s
[ 1.045433] ppb10: link is x16 @ 2.5GT/s
[ 1.045433] pci11 at ppb10 bus 11
[ 1.045433] pci11: i/o space, memory space enabled, rd/line, wr/inv ok
[ 1.045433] radeon0 at pci11 dev 0 function 0: ATI Technologies Radeon HD 5000/6000/7350/8350 Series (rev. 0x00)
[ 1.045433] hdaudio0 at pci11 dev 0 function 1: HD Audio Controller
[ 1.045433] hdaudio0: interrupting at msi4 vec 0
[ 1.045433] hdaudio0: HDA ver. 1.0, OSS 1, ISS 0, BSS 0, SDO 1, 64-bit
[ 1.045433] hdafg0 at hdaudio0: ATI R6xx HDMI
[ 1.045433] hdafg0: HDMI00 2ch: Digital Out [Jack]
[ 1.045433] hdafg0: 2ch/0ch 32000Hz 44100Hz 48000Hz PCM16 AC3
[ 1.045433] audio0 at hdafg0: playback
[ 1.045433] audio0: slinear_le:16 2ch 48000Hz, blk 1920 bytes (10ms) for playback
[ 1.045433] spkr1 at audio0: PC Speaker (synthesized)
[ 1.045433] wsbell at spkr1 not configured
[ 1.045433] pchb3 at pci0 dev 4 function 0: AMD 17h/7xh Host Bridge (rev. 0x00)
[ 1.045433] pchb4 at pci0 dev 5 function 0: AMD 17h/7xh Host Bridge (rev. 0x00)
[ 1.045433] pchb5 at pci0 dev 7 function 0: AMD 17h/7xh Host Bridge (rev. 0x00)
[ 1.045433] ppb11 at pci0 dev 7 function 1: AMD 17h/7xh PCIe (rev. 0x00)
[ 1.045433] ppb11: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x16 @ 16.0GT/s
[ 1.045433] pci12 at ppb11 bus 12
[ 1.045433] pci12: i/o space, memory space enabled, rd/line, wr/inv ok
[ 1.045433] AMD product 148a (non-essential instrumentation, subclass 0x00) at pci12 dev 0 function 0 not configured
[ 1.045433] pchb6 at pci0 dev 8 function 0: AMD 17h/7xh Host Bridge (rev. 0x00)
[ 1.045433] ppb12 at pci0 dev 8 function 1: AMD 17h/7xh PCIe (rev. 0x00)
[ 1.045433] ppb12: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x16 @ 16.0GT/s
[ 1.045433] pci13 at ppb12 bus 13
[ 1.045433] pci13: i/o space, memory space enabled, rd/line, wr/inv ok
[ 1.045433] AMD Family17h/7xh Reserved SPP (non-essential instrumentation, subclass 0x00) at pci13 dev 0 function 0 not configured
[ 1.045433] amdccp0 at pci13 dev 0 function 1: AMD Cryptographic Coprocessor
[ 1.045433] xhci1 at pci13 dev 0 function 3: AMD Family17h/7xh USB 3.0 Host Controller (rev. 0x00)
[ 1.045433] xhci1: 64-bit DMA
[ 1.045433] xhci1: interrupting at msix5 vec 0
[ 1.045433] xhci1: xHCI version 1.10
[ 1.045433] usb2 at xhci1: USB revision 3.1
[ 1.045433] usb3 at xhci1: USB revision 2.0
[ 1.045433] hdaudio1 at pci13 dev 0 function 4: HD Audio Controller
[ 1.045433] hdaudio1: interrupting at msi6 vec 0
[ 1.045433] hdaudio1: HDA ver. 1.0, OSS 4, ISS 4, BSS 0, SDO 1, 64-bit
[ 1.045433] hdafg1 at hdaudio1: Realtek product 0897
[ 1.045433] hdafg1: DAC00 2ch: Speaker [Jack]
[ 1.045433] hdafg1: DAC01 2ch: HP Out [Jack]
[ 1.045433] hdafg1: ADC02 2ch: Line In [Jack], Mic In [Jack]
[ 1.045433] hdafg1: ADC03 2ch: Mic In [Jack]
[ 1.045433] hdafg1: DIG04 2ch: SPDIF Out [Built-In]
[ 1.045433] hdafg1: 2ch/2ch 32000Hz 44100Hz 48000Hz 88200Hz 96000Hz 192000Hz PCM16 PCM20 PCM24 AC3
[ 1.045433] audio1 at hdafg1: playback, capture, full duplex, independent
[ 1.045433] audio1: slinear_le:16 2ch 48000Hz, blk 1920 bytes (10ms) for playback
[ 1.045433] audio1: slinear_le:16 2ch 48000Hz, blk 1920 bytes (10ms) for recording
[ 1.045433] spkr2 at audio1: PC Speaker (synthesized)
[ 1.045433] wsbell at spkr2 not configured
[ 1.045433] piixpm0 at pci0 dev 20 function 0: AMD X370/X399 SMBus Controller (rev. 0x61)
[ 1.045433] piixpm0: interrupting at SMI,
[ 1.045433] iic0 at piixpm0 port 0: I2C bus
[ 1.045433] iic1 at piixpm0 port 1: I2C bus
[ 1.045433] pcib0 at pci0 dev 20 function 3: AMD FCH LPC (rev. 0x51)
[ 1.045433] pchb7 at pci0 dev 24 function 0: AMD 17h/7xh Data Fabric (rev. 0x00)
[ 1.045433] pchb8 at pci0 dev 24 function 1: AMD 17h/7xh Data Fabric (rev. 0x00)
[ 1.045433] pchb9 at pci0 dev 24 function 2: AMD 17h/7xh Data Fabric (rev. 0x00)
[ 1.045433] pchb10 at pci0 dev 24 function 3: AMD 17h/7xh Data Fabric (rev. 0x00)
[ 1.045433] pchb11 at pci0 dev 24 function 4: AMD 17h/7xh Data Fabric (rev. 0x00)
[ 1.045433] pchb12 at pci0 dev 24 function 5: AMD 17h/7xh Data Fabric (rev. 0x00)
[ 1.045433] pchb13 at pci0 dev 24 function 6: AMD 17h/7xh Data Fabric (rev. 0x00)
[ 1.045433] pchb14 at pci0 dev 24 function 7: AMD 17h/7xh Data Fabric (rev. 0x00)
[ 1.045433] isa0 at pcib0
[ 1.045433] pckbc0 at isa0 port 0x60-0x64
[ 1.045433] acpicpu0 at cpu0: ACPI CPU
[ 1.045433] acpicpu0: C1: FFH, lat 1 us, pow 0 mW
[ 1.045433] acpicpu0: C2: I/O, lat 18 us, pow 0 mW
[ 1.045433] acpicpu0: P0: FFH, lat 1 us, pow 4070 mW, 3700 MHz
[ 1.045433] acpicpu0: P1: FFH, lat 1 us, pow 2800 mW, 2800 MHz
[ 1.045433] acpicpu0: P2: FFH, lat 1 us, pow 1980 mW, 2200 MHz
[ 1.045433] acpicpu1 at cpu1: ACPI CPU
[ 1.045433] acpicpu2 at cpu2: ACPI CPU
[ 1.045433] acpicpu3 at cpu3: ACPI CPU
[ 1.045433] acpicpu4 at cpu4: ACPI CPU
[ 1.045433] acpicpu5 at cpu5: ACPI CPU
[ 1.045433] acpicpu6 at cpu6: ACPI CPU
[ 1.045433] acpicpu7 at cpu7: ACPI CPU
[ 1.045433] acpicpu8 at cpu8: ACPI CPU
[ 1.045433] acpicpu9 at cpu9: ACPI CPU
[ 1.045433] acpicpu10 at cpu10: ACPI CPU
[ 1.045433] acpicpu11 at cpu11: ACPI CPU
[ 1.045433] timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
[ 1.045433] timecounter: Timecounter "TSC" frequency 3693073000 Hz quality 3000
[ 1.094005] uhub0 at usb0: NetBSD (0x0000) xHCI root hub (0x0000), class 9/0, rev 3.00/1.00, addr 0
[ 1.100687] uhub0: 4 ports with 4 removable, self powered
[ 1.100687] uhub1 at usb1: NetBSD (0x0000) xHCI root hub (0x0000), class 9/0, rev 2.00/1.00, addr 0
[ 1.110685] uhub1: 10 ports with 10 removable, self powered
[ 1.110685] uhub2 at usb2: NetBSD (0x0000) xHCI root hub (0x0000), class 9/0, rev 3.00/1.00, addr 0
[ 1.120685] uhub2: 4 ports with 4 removable, self powered
[ 1.120685] uhub3 at usb3: NetBSD (0x0000) xHCI root hub (0x0000), class 9/0, rev 2.00/1.00, addr 0
[ 1.130685] uhub3: 4 ports with 4 removable, self powered
[ 1.130685] ld0: GPT GUID: 6daca67a-2453-4331-8cf9-0c7c5ec8817f
[ 1.130685] dk0 at ld0: "c6830be4-7f3e-4631-b6b7-75ae6428db71", 262144 blocks at 2048, type: msdos
[ 1.130685] dk1 at ld0: "d0ff5477-8cd0-42eb-ae72-b3bdf7644e8d", 3839840256 blocks at 264192, type: ffs
[ 1.130685] dk2 at ld0: "534f14ac-5a35-4a05-9262-6a435d4e75ae", 66924687 blocks at 3840104448, type: swap
[ 1.142220] IPsec: Initialized Security Association Processing.
[ 1.230685] ahcisata0 port 3: device present, speed: 6.0Gb/s
[ 1.230685] ahcisata0 port 2: device present, speed: 6.0Gb/s
[ 1.240685] ahcisata0 port 1: device present, speed: 6.0Gb/s
[ 1.610685] uhub4 at uhub1 port 7: vendor 214b (0x214b) USB2.0 HUB (0x7000), class 9/0, rev 2.00/1.00, addr 1
[ 1.620685] uhub4: single transaction translator
[ 1.640685] uhidev0 at uhub3 port 3 configuration 1 interface 0
[ 1.650685] uhidev0: Logitech (0x046d) USB Keyboard (0xc31c), rev 1.10/64.02, addr 1, iclass 3/1
[ 1.670685] uhub4: 4 ports with 4 removable, self powered
[ 1.670685] ukbd0 at uhidev0
[ 1.690685] wskbd0 at ukbd0: console keyboard
[ 1.700685] uhidev1 at uhub3 port 3 configuration 1 interface 1
[ 1.710685] uhidev1: Logitech (0x046d) USB Keyboard (0xc31c), rev 1.10/64.02, addr 1, iclass 3/0
[ 1.730685] uhidev1: 5 report ids
[ 1.740686] uhid0 at uhidev1 reportid 1: input=1, output=0, feature=0
[ 1.750686] uhid1 at uhidev1 reportid 2: input=1, output=0, feature=0
[ 1.760685] uhid2 at uhidev1 reportid 3: input=3, output=0, feature=0
[ 1.770685] uhid3 at uhidev1 reportid 5: input=0, output=0, feature=5
[ 2.280686] uhidev2 at uhub3 port 4 configuration 1 interface 0
[ 2.290686] uhidev2: Logitech (0x046d) USB-PS/2 Optical Mouse (0xc00e), rev 2.00/11.10, addr 2, iclass 3/1
[ 2.300686] ums0 at uhidev2: 3 buttons and Z dir
[ 2.310686] wsmouse0 at ums0 mux 0
...
From: Robert Elz <kre@munnari.OZ.AU>
To: mlh@goathill.org (MLH)
Cc: gnats-bugs@netbsd.org, port-amd64-maintainer@netbsd.org,
gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on -current)
Date: Sat, 20 May 2023 23:50:10 +0700
Please add the kernel config file for HDMIAUDIO
It looks to me as if your kernel config might be missing the
sd* at scsibus? ...
entry, and so isn't trying to attach any sd devices.
kre
From: mlh@goathill.org (MLH)
To: gnats-bugs@netbsd.org
Cc: port-amd64-maintainer@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org, mlh@goathill.org
Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on
-current)
Date: Sat, 20 May 2023 13:18:10 -0400 (EDT)
Robert Elz wrote:
> The following reply was made to PR port-md64/56987; it has been noted by GNATS.
>
> From: Robert Elz <kre@munnari.OZ.AU>
> To: mlh@goathill.org (MLH)
> Cc: gnats-bugs@netbsd.org, port-amd64-maintainer@netbsd.org,
> gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
> Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on -current)
> Date: Sat, 20 May 2023 23:50:10 +0700
>
> Please add the kernel config file for HDMIAUDIO
>
> It looks to me as if your kernel config might be missing the
>
> sd* at scsibus? ...
>
> entry, and so isn't trying to attach any sd devices.
BTW, four of the devices which no longer work are Garmin-type sports
devices and the fifth is a USB/ethernet hub (loaned out and not
available).
Might it be possible that the sports devices all employ something
different with their usb devices that Garmin used and others follow
for compatibility?
From: mlh@goathill.org (MLH)
To: gnats-bugs@netbsd.org
Cc: port-amd64-maintainer@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org, mlh@goathill.org
Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on
-current)
Date: Sat, 20 May 2023 13:12:52 -0400 (EDT)
Robert Elz wrote:
> The following reply was made to PR port-amd64/56987; it has been noted by GNATS.
>
> From: Robert Elz <kre@munnari.OZ.AU>
> To: mlh@goathill.org (MLH)
> Cc: gnats-bugs@netbsd.org, port-amd64-maintainer@netbsd.org,
> gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
> Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on -current)
> Date: Sat, 20 May 2023 23:50:10 +0700
>
> Please add the kernel config file for HDMIAUDIO
>
> It looks to me as if your kernel config might be missing the
>
> sd* at scsibus? ...
>
> entry, and so isn't trying to attach any sd devices.
----
$ cat HDMIAUDIO
(comments)
include "arch/amd64/conf/GENERIC"
options HDAUDIO_ENABLE_HDMI
----
which has
sd* at scsibus? target ? lun ? # SCSI disk drives
Most other usb devices mount as sd0x just fine.
From: mlh@goathill.org (MLH)
To: gnats-bugs@netbsd.org
Cc: port-amd64-maintainer@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org, mlh@goathill.org
Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on
-current)
Date: Sat, 20 May 2023 17:30:19 -0400 (EDT)
Robert Elz wrote:
> The following reply was made to PR port-amd64/56987; it has been noted by GNATS.
>
> From: Robert Elz <kre@munnari.OZ.AU>
> To: mlh@goathill.org (MLH)
> Cc: gnats-bugs@netbsd.org, port-amd64-maintainer@netbsd.org,
> gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
> Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on -current)
> Date: Sat, 20 May 2023 23:50:10 +0700
>
...
> entry, and so isn't trying to attach any sd devices.
Remember that this failure started after the big changes to USB
drivers, etc. after 9.99.93
From: mlh@goathill.org (MLH)
To: gnats-bugs@netbsd.org
Cc: port-amd64-maintainer@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org, mlh@goathill.org
Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on
-current)
Date: Mon, 5 Jun 2023 20:41:51 -0400 (EDT)
MLH wrote:
> The following reply was made to PR port-amd64/56987; it has been noted by GNATS.
>
> From: mlh@goathill.org (MLH)
> To: gnats-bugs@netbsd.org
> Cc: port-amd64-maintainer@netbsd.org, gnats-admin@netbsd.org,
> netbsd-bugs@netbsd.org, mlh@goathill.org
> Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on
> -current)
> Date: Sat, 20 May 2023 17:30:19 -0400 (EDT)
>
> Robert Elz wrote:
> > The following reply was made to PR port-amd64/56987; it has been noted by GNATS.
> >
> > From: Robert Elz <kre@munnari.OZ.AU>
> > To: mlh@goathill.org (MLH)
> > Cc: gnats-bugs@netbsd.org, port-amd64-maintainer@netbsd.org,
> > gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
> > Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on -current)
> > Date: Sat, 20 May 2023 23:50:10 +0700
> >
> ...
> > entry, and so isn't trying to attach any sd devices.
>
> Remember that this failure started after the big changes to USB
> drivers, etc. after 9.99.93
Any advice on looking into fixing the usb device mounting issues
that were broken with the usb changes last year? And yes, the usb
subsystem is much more stable with those changes, but I really
would like to finish things.
Thanks
From: mlh@goathill.org (MLH)
To: gnats-bugs@netbsd.org
Cc: port-amd64-maintainer@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org, mlh@goathill.org
Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on
-current)
Date: Wed, 19 Jul 2023 11:11:09 -0400 (EDT)
MLH wrote:
>
> Remember that this failure started after the big changes to USB
> drivers, etc. after 9.99.93
debug kernel - NetBSD 10.99.5 (USBDEBUG) with the following:
include "arch/amd64/conf/GENERIC"
options DDB # in-kernel debugger
options USB_DEBUG
options UMASS_DEBUG
options UHUB_DEBUG
options EHCI_DEBUG
- sysctl -w hw.umass.debug=0x70
hw.umass.debug: 0 -> 112
- deviced plugged in
Jul 18 11:27:06 tiamat /netbsd: [ 97.7110237] umass0 at uhub5 port 4 configuration 1 interface 0
Jul 18 11:27:06 tiamat /netbsd: [ 97.7110237] umass0: Lezyne (0x2b29) GPS Device (0x0055), rev 2.00/1.00, addr 4
Jul 18 11:27:06 tiamat /netbsd: [ 97.7110237] umass0: using SCSI over Bulk-Only
Jul 18 11:27:06 tiamat /netbsd: [ 97.7210239] scsibus0 at umass0: 2 targets, 1 lun per target
Jul 18 11:27:06 tiamat /netbsd: [ 97.7210239] uhidev3 at uhub5 port 4 configuration 1 interface 1
Jul 18 11:27:06 tiamat /netbsd: [ 97.7210239] uhidev3: Lezyne (0x2b29) GPS Device (0x0055), rev 2.00/1.00, addr 4, iclass 3/0
Jul 18 11:27:06 tiamat /netbsd: [ 97.7210239] uhid4 at uhidev3: input=64, output=64, feature=0
- sysctl -w hw.umass.debug=0
- vmstat -u usbhist > usbstat
size -> 5126232 Jul 19 09:56 usbstat
vmstat log is at :
http://synthetictransport.com/log/usbstat
From: Taylor R Campbell <riastradh@NetBSD.org>
To: mlh@goathill.org (MLH)
Cc: gnats-bugs@netbsd.org, port-amd64-maintainer@netbsd.org,
gnats-admin@netbsd.org, netbsd-bugs@netbsd.org, mlh@goathill.org
Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on
-current)
Date: Wed, 19 Jul 2023 15:58:33 +0000
> Date: Mon, 5 Jun 2023 20:41:51 -0400 (EDT)
> From: mlh@goathill.org (MLH)
>
> Any advice on looking into fixing the usb device mounting issues
> that were broken with the usb changes last year? And yes, the usb
> subsystem is much more stable with those changes, but I really
> would like to finish things.
The best thing to do is to bisect to find exactly what change broke
it. A lot of things changed between 9.99.93 and 9.99.94 over the
course of four months.
On any reasonably POSIXish system (doesn't have to be your NetBSD
machine), you can do this:
$ git clone https://github.com/NetBSD/src
$ cd src
$ ./build.sh -O ../obj -T ../tools -U -u -m amd64 -j4 tools
$ git bisect start
$ git bisect bad HEAD
$ git bisect good 8abbca48b237c9edc3ffb387e9074ddcff8b645d
And then, at each step, do
$ ./build.sh -O ../obj -T ../tools -U -u -m amd64 -j4 kernel=GENERIC
and try the kernel at ../obj/sys/arch/amd64/compile/GENERIC/netbsd.
- If it works, run `git bisect good'.
- If it fails the same way, `git bisect bad'.
- If it fails to build, or crashes in some other way, tun `git bisect
skip'.
And keep going until it points you to a particular commit.
(f6d3947777a575d460fc1be6c52252513ecfba93 is the commit that bumped
the version to 9.99.92. This range is a little larger than needed,
but that's fine -- bisection is logarithmic, so checking everything
from 9.99.92 to now vs checking everything from 9.99.93 to 9.99.94
will probably only add a couple more iterations.)
Another thing that might help, in case there is a thread that is just
wedged somewhere, is to run:
# crash
crash> ps
crash> ps/w
And, if you're using a kernel from the last week:
crash> show all tstiles
And then share the output. But I suspect it's not a wedged thread;
that would probably manifest in other ways.
It might also help to share dmesg from the working 9.99.93 kernel so
we can look at all of it side-by-side with the broken 9.99.94 kernel
or whatever.
From: Martin Husemann <martin@duskware.de>
To: Taylor R Campbell <riastradh@NetBSD.org>
Cc: MLH <mlh@goathill.org>, gnats-bugs@netbsd.org,
port-amd64-maintainer@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org
Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted
on -current)
Date: Wed, 19 Jul 2023 18:18:57 +0200
On Wed, Jul 19, 2023 at 03:58:33PM +0000, Taylor R Campbell wrote:
> It might also help to share dmesg from the working 9.99.93 kernel so
> we can look at all of it side-by-side with the broken 9.99.94 kernel
> or whatever.
That part is useless in this case - it just shows that no disk (sd0) attaches.
MLH: can you please redo the log capturing with
sysctl -w hw.umass.debug=0x7f0000
please?
Martin
From: mlh@goathill.org (MLH)
To: Martin Husemann <martin@duskware.de>
Cc: Taylor R Campbell <riastradh@NetBSD.org>, MLH <mlh@goathill.org>,
gnats-bugs@netbsd.org, port-amd64-maintainer@netbsd.org,
gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on
-current)
Date: Wed, 19 Jul 2023 14:55:54 -0400 (EDT)
Martin Husemann wrote:
> On Wed, Jul 19, 2023 at 03:58:33PM +0000, Taylor R Campbell wrote:
> > It might also help to share dmesg from the working 9.99.93 kernel so
> > we can look at all of it side-by-side with the broken 9.99.94 kernel
> > or whatever.
>
> That part is useless in this case - it just shows that no disk (sd0) attaches.
>
> MLH: can you please redo the log capturing with
>
> sysctl -w hw.umass.debug=0x7f0000
Done:
- sysctl -w hw.umass.debug=0
- sysctl -w hw.umass.debug=0x7f0000
- plug in device
- vmstat -u usbhist > usbstat
- sysctl -w hw.umass.debug=0
Same filename, new file
http://synthetictransport.com/log/sdbstat
From: Taylor R Campbell <riastradh@NetBSD.org>
To: mlh@goathill.org (MLH)
Cc: Martin Husemann <martin@duskware.de>,
gnats-bugs@netbsd.org, port-amd64-maintainer@netbsd.org,
gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on
-current)
Date: Wed, 19 Jul 2023 19:16:07 +0000
> Date: Wed, 19 Jul 2023 14:55:54 -0400 (EDT)
> From: mlh@goathill.org (MLH)
>
> Done:
>
> - sysctl -w hw.umass.debug=0
> - sysctl -w hw.umass.debug=0x7f0000
> - plug in device
> - vmstat -u usbhist > usbstat
> - sysctl -w hw.umass.debug=0
>
> Same filename, new file
> http://synthetictransport.com/log/sdbstat
Thanks, can you do the same with one of the working kernels so we can
compare side by side?
From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@netbsd.org
Cc: skrll@NetBSD.org
Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted
on -current)
Date: Thu, 20 Jul 2023 12:44:31 +0200
I see we make it up to the scsi layer and start issuing requests:
1689792333.060245 umass_scsipi_request#37@4: async dir=1, cmdlen=6 datalen=36
1689792333.060593 umass_scsipi_request#38@4: async dir=1, cmdlen=12 datalen=16
but I don't see any replies from the device - where would those come in and
would we need even more debug level to see them?
Martin
From: mlh@goathill.org (MLH)
To: gnats-bugs@netbsd.org
Cc: port-amd64-maintainer@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org, mlh@goathill.org
Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on
-current)
Date: Sun, 23 Jul 2023 15:04:12 -0400 (EDT)
Taylor R Campbell wrote:
> The following reply was made to PR port-amd64/56987; it has been noted by GNATS.
>
> From: Taylor R Campbell <riastradh@NetBSD.org>
> To: mlh@goathill.org (MLH)
> Cc: Martin Husemann <martin@duskware.de>,
> gnats-bugs@netbsd.org, port-amd64-maintainer@netbsd.org,
> gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
> Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on
> -current)
> Date: Wed, 19 Jul 2023 19:16:07 +0000
>
> > Date: Wed, 19 Jul 2023 14:55:54 -0400 (EDT)
> > From: mlh@goathill.org (MLH)
> >
> > Done:
> >
> > - sysctl -w hw.umass.debug=0
> > - sysctl -w hw.umass.debug=0x7f0000
> > - plug in device
> > - vmstat -u usbhist > usbstat
> > - sysctl -w hw.umass.debug=0
> >
> > Same filename, new file
> > http://synthetictransport.com/log/sdbstat
>
> Thanks, can you do the same with one of the working kernels so we can
> compare side by side?
I pulled down the .92 sources and built a debug kernel but it always
hangs during boot. I installed it on several (netBSD) install sd
cards for .92 and the debug kernel hangs every time for those so
seems as something is bad with the debug kernel I built.
Maybe I need a .93 debug kernel. How do I get that one? Can someone
build one for me?
Thanks
From: mlh@goathill.org (MLH)
To: gnats-bugs@netbsd.org
Cc: port-amd64-maintainer@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org, mlh@goathill.org
Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on
-current)
Date: Wed, 9 Aug 2023 16:12:48 -0400 (EDT)
Taylor R Campbell wrote:
> The following reply was made to PR port-amd64/56987; it has been noted by GNATS.
>
> > Same filename, new file
> > http://synthetictransport.com/log/sdbstat
>
> Thanks, can you do the same with one of the working kernels so we can
> compare side by side?
After days and days of trying to create a bootable (and easily
recoverable back to my std setup), I need help.
I lost access to my std setup for several days when I installed a
debug kernel to test the above with to my root disk. I managed to
finally recover it using an sdcard with an ietf NetBSD installer
on it. Since that time, all but my std setup now stops with Read-only
file system init failures. I can't get it to breakout to a shell
to do anything.
I have put the installer on several cf cards, both using dd and
manually building and installing many times. Nothing works.
If I could find out how to specify what the path name for ietf
booting a specific kernel filename, I wouldn't need to try to use
the sdcard path. As it is, I can only boot using 'boot -a' and
selecting the root dk(x) needed where 'netbsd' is located. I can't
specify the filename though and I don't want to risk changing
'netbsd' to something else that won't boot (which is what happened
the last time).
Help??
From: mlh@goathill.org (MLH)
To: gnats-bugs@netbsd.org
Cc: port-amd64-maintainer@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org, mlh@goathill.org
Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on
-current)
Date: Wed, 9 Aug 2023 17:47:03 -0400 (EDT)
MLH wrote:
> The following reply was made to PR port-amd64/56987; it has been noted by GNATS.
>
> From: mlh@goathill.org (MLH)
> To: gnats-bugs@netbsd.org
> Cc: port-amd64-maintainer@netbsd.org, gnats-admin@netbsd.org,
> netbsd-bugs@netbsd.org, mlh@goathill.org
> Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on
> -current)
> Date: Wed, 9 Aug 2023 16:12:48 -0400 (EDT)
>
> Taylor R Campbell wrote:
> > The following reply was made to PR port-amd64/56987; it has been noted by GNATS.
> >
> > > Same filename, new file
> > > http://synthetictransport.com/log/sdbstat
> >
> > Thanks, can you do the same with one of the working kernels so we can
> > compare side by side?
>
> After days and days of trying to create a bootable (and easily
> recoverable back to my std setup), I need help.
>
> I lost access to my std setup for several days when I installed a
> debug kernel to test the above with to my root disk. I managed to
> finally recover it using an sdcard with an ietf NetBSD installer
> on it. Since that time, all but my std setup now stops with Read-only
> file system init failures. I can't get it to breakout to a shell
> to do anything.
>
> I have put the installer on several cf cards, both using dd and
> manually building and installing many times. Nothing works.
>
> If I could find out how to specify what the path name for ietf
> booting a specific kernel filename, I wouldn't need to try to use
> the sdcard path. As it is, I can only boot using 'boot -a' and
> selecting the root dk(x) needed where 'netbsd' is located. I can't
> specify the filename though and I don't want to risk changing
> 'netbsd' to something else that won't boot (which is what happened
> the last time).
Ha. ietf -> uefi. frustration mistake
From: mlh@goathill.org (MLH)
To: gnats-bugs@netbsd.org
Cc: port-amd64-maintainer@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org, mlh@goathill.org
Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on
-current)
Date: Thu, 5 Oct 2023 10:44:37 -0400 (EDT)
MLH wrote:
> The following reply was made to PR port-amd64/56987; it has been noted by GNATS.
>
> From: mlh@goathill.org (MLH)
> To: gnats-bugs@netbsd.org
> Cc: port-amd64-maintainer@netbsd.org, gnats-admin@netbsd.org,
> netbsd-bugs@netbsd.org, mlh@goathill.org
> Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on
> -current)
> Date: Wed, 9 Aug 2023 16:12:48 -0400 (EDT)
>
> Taylor R Campbell wrote:
> > The following reply was made to PR port-amd64/56987; it has been noted by GNATS.
> >
> > > Same filename, new file
> > > http://synthetictransport.com/log/sdbstat
> >
> > Thanks, can you do the same with one of the working kernels so we can
> > compare side by side?
BTW, on Android these devices show as "FSL Semi USB drive" but I
haven't seen what this is. Is there a reference to that before the
USB stack was rewritten (which lost the capability to read these
devices)?
Also, has anyone come up with a way to determine boot file path
names for uefi booting yet?
Thanks
From: Taylor R Campbell <riastradh@NetBSD.org>
To: mlh@goathill.org (MLH)
Cc: gnats-bugs@netbsd.org, port-amd64-maintainer@netbsd.org,
gnats-admin@netbsd.org, netbsd-bugs@netbsd.org, mlh@goathill.org
Subject: Re: port-amd64/56987 (Certain usb devices can no longer be mounted on
-current)
Date: Thu, 5 Oct 2023 15:43:56 +0000
> Date: Thu, 5 Oct 2023 10:44:37 -0400 (EDT)
> From: mlh@goathill.org (MLH)
>
> > > > Same filename, new file
> > > > http://synthetictransport.com/log/sdbstat
This URL now returns 404. Can you provide the log at a stable
location, or just put it back up there for now so we can save a copy
of it?
> BTW, on Android these devices show as "FSL Semi USB drive" but I
> haven't seen what this is. Is there a reference to that before the
> USB stack was rewritten (which lost the capability to read these
> devices)?
That's probably just a name that the USB device reports for itself,
plus `USB drive' because it's a USB mass storage class of device
(`hard drive').
(We didn't rewrite the USB stack -- it's almost all the same code as
before. We just made a lot of small changes to fix a lot of little
bugs; perhaps a bug crept into one of those small changes. Many of
these changes in particular were deliberately broken down into
especially small, functionally separate commits -- with changes as
independent as possible -- so that it would be easy for bisection to
narrow down exactly which commit broke anything.)
> Also, has anyone come up with a way to determine boot file path
> names for uefi booting yet?
You can either use:
- esp:/EFI/NetBSD/boot.cfg, on the EFI system partition (esp); or
- /boot.cfg, on the root partition, which is installed by default on
x86.
See boot.cfg(8) for details of the format, and x86/boot(8) for details
of the process. The default x86 boot.cfg is this:
menu=Boot normally:rndseed /var/db/entropy-file;boot
menu=Boot single user:rndseed /var/db/entropy-file;boot -s
menu=Drop to boot prompt:prompt
default=1
timeout=5
clear=1
You can just add another menu entry like this to boot a kernel called
`netbsd.test', placed after the other `menu=...' lines in boot.cfg so
it's not taken as the default:
menu=Boot other kernel:rndseed /var/db/entropy-file;boot netbsd.test
Alternatively, instead of changing boot.cfg, you can move your working
kernel from /netbsd to /onetbsd. It will continue to boot when you do
this: the bootloader will try /netbsd first, then /onetbsd. Then you
can try another kernel at /netbsd, and if it doesn't work, drop to the
bootloader prompt to do `boot /onetbsd' instead.
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.47 2022/09/11 19:34:41 kim Exp $
$NetBSD: gnats_config.sh,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2023
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.
Home