Re: ucom debug not working on releng/14
bob prohaska <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.arm |
|---|---|
| Message-ID | <[email protected]> |
On Tue, Oct 24, 2023 at 09:43:53AM -0600, Warner Losh wrote: > I thought that was a loader tuneable... have you tried it there? > It works on arm64 (Pi3 and Pi4) in sysctl.conf. Adding hw.usb.ucom.debug="1" to /boot/loader.conf doesn't seem to make any difference, during boot the armv7 releng/14 host still reports sysctl: unknown oid 'hw.usb.ucom.debug' at line 10 I should have stated that it works on -current with Pi3 and Pi4 but does not work on Pi2 (armv7) with stable/12 and releng/14. There's presently no -current armv7 host to test. Thanks for writing! bob prohaska > Warner > > On Tue, Oct 24, 2023, 9:34 AM bob prohaska <[email protected]> wrote: > > > A Pi2 running armv7 releng/14 reports > > > > sysctl: unknown oid 'hw.usb.ucom.debug' at line 10 > > > > when booting. > > > > The intent was to understand why it drops ssh connections > > when they are used to communicate with an ftdi usb-serial > > adapter. A few other hosts running -current accept the > > debug setting and generate copious output in response. > > > > Man pages suggest the option is available on stable, > > -current and releng/, but it seems to actually work > > only on -current, at least for armv7. > > > > Thanks for reading, and any hints what might be done wrong. > > > > bob prohaska > > > > > >