Re: kern/52259: NetBSD-current won't boot on i386 or amd64 unless athn is disabled.

["Thomas Mueller" <mueller6725%twc.com@localhost>]

The following reply was made to PR kern/52259; it has been noted by GNATS.

From: "Thomas Mueller" <mueller6725%twc.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/52259: NetBSD-current won't boot on i386 or amd64 unless
        athn is disabled.
Date: Mon, 29 May 2017 17:22:29 +0000

 The following reply was made to PR kern/52259; it has been noted by GNATS.
   
 > From: Martin Husemann <martin%duskware.de@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 Cc:
 > Subject: Re: kern/52259: NetBSD-current won't boot on i386 or amd64 unless
 >  athn is disabled.
 > Date: Mon, 29 May 2017 10:57:52 +0200
  
 >  On Mon, May 29, 2017 at 08:55:01AM +0000, Thomas Mueller wrote:
 >  >  Would pcictl be of any use on a USB or quasi-USB device?  What is for USB?
  >
 >  >  athn, in contrast to ath, is (quasi-)USB, not PCI.
  
 >  Sorry (there are various variants of athn, I have one that attaches at PCI).
  
 >  If yours attaches to usb, a usbdevs -v output for that device would be
 >  helpfull.
 
 If I need to disable athn, or keep it out of kernel config, I suppose 
 usbdevs -v wouldn't find it?
 
 But I could boot an earlier NetBSD kernel, 7.99.15 or a 7.99.1 installation 
 and try usbdevs -v from there.
 
 Or I could even try usbconfig or usbdump from FreeBSD, although FreeBSD has no support for athn.
 
 I reply to gnats-bugs%netbsd.org@localhost because that's what the Reply-To: header says.
 
 Tom