Re: hint.uart.1 in device.hints causes freeze at boot

[John Baldwin]

On Friday, February 26, 2016 11:08:37 PM Warner Losh wrote:
> On Fri, Feb 26, 2016 at 6:49 PM, Marcel Moolenaar  wrote:
> 
> Any reason not to add .disabled=1 to all the entries that are there,
> with the possible exception of uart.0? At least for i386 and amd64?
> Bonus points for writing code that filters those out when there's
> no ACPI. While PNPBIOS could also supply this info, I doubt that you
> could find hardware that has pnpbios data and not ACPI data except
> maybe some of the soekris boxes to test against.
> 
> Better still would be to split the current GENERIC.hints into two bits.
> One that was strictly for legacy (!ACPI and !PNPBIOS) situations, and
> one that we always load. There look to be at least a couple of hints
> that are universally relevant still. I might have a 200MHz pentium I
> can test this with...

If there was an easy way to load a new hints file we could ship a
/boot/legacy.hints and have a note in the handbook / FAQ about using it if
needed.  We could even have smarts in the loader to suck it in perhaps if
!ACPI and !PnPBIOS.

> As near as I can tell, only the following are relevant:
> hint.fd.0.at="fdc0"
> hint.fd.0.drive="0"
> hint.fd.1.at="fdc0"
> hint.fd.1.drive="1"
> hint.acpi_throttle.0.disabled="1"
> hint.p4tcc.0.disabled="1"

hint.sc.0.at is relevant if you want to use sc(4) instead of vt(4).  For a
long time I've booted machines that only had that hint.  The npx.0 hint used
to matter (but no longer does).

I think we should definitely trim the hints file for amd64.  amd64 pretty
much mandates ACPI.  For i386 I would be fine with a the legacy.hints route
even if it wasn't automagical but something you had to manually load.  The
only thing about the hints that is still somewhat useful on x86 is enabling
serial console (though boot -h and/or console=comconsole already does that)
and enabling remote GDB.  (hint.uart.1.flags=0x80 is shorter and doesn't
require remembering random I/O port addresses like the hw.uart route for
GDB.)

-- 
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: hint.uart.1 in device.hints causes freeze at boot

[Warner Losh]

On Fri, Feb 26, 2016 at 6:49 PM, Marcel Moolenaar  wrote:

>
> > On Feb 26, 2016, at 7:48 AM, Lundberg, Johannes <
> johan...@brilliantservice.co.jp> wrote:
> >
> > Hi
> >
> > Not sure if it's ok to cross post but I wasn't sure which list to send
> to.
> >
> > On Intel Atom X5-Z8300 SoC (CherryTrail) the install memstick image
> (amd64)
> > halts during boot because of uart.1 settings in device hints.
>
> I have found that FreeBSD’s default device.hints file has fallen
> behind on reality and is indeed causing problems on more modern
> H/W, like the H/W you mention.
>
> >
> > I'm sure it is there for a reason so what is the alternative actions? Is
> > the solution to get a bootable Atom SoC image to create yet another
> > distribution or can the installer choose the proper device.hints
> > dynamically during boot?
>
> FreeBSD should really get rid of any default hints by now; or at least
> limit the hints to what is absolutely certain to be needed or to be
> correct.
>

Any reason not to add .disabled=1 to all the entries that are there,
with the possible exception of uart.0? At least for i386 and amd64?
Bonus points for writing code that filters those out when there's
no ACPI. While PNPBIOS could also supply this info, I doubt that you
could find hardware that has pnpbios data and not ACPI data except
maybe some of the soekris boxes to test against.

Better still would be to split the current GENERIC.hints into two bits.
One that was strictly for legacy (!ACPI and !PNPBIOS) situations, and
one that we always load. There look to be at least a couple of hints
that are universally relevant still. I might have a 200MHz pentium I
can test this with...

As near as I can tell, only the following are relevant:
hint.fd.0.at="fdc0"
hint.fd.0.drive="0"
hint.fd.1.at="fdc0"
hint.fd.1.drive="1"
hint.acpi_throttle.0.disabled="1"
hint.p4tcc.0.disabled="1"

and maybe

hint.apm.0.disabled="1"

The floppy is for systems that have it, but won't add a floppy controller.
APM hasn't been relevant since ~100MHz Pentium. The last two I'm
unsure of.

Warner

Warner
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: hint.uart.1 in device.hints causes freeze at boot

[Marcel Moolenaar]

> On Feb 26, 2016, at 7:48 AM, Lundberg, Johannes 
>  wrote:
> 
> Hi
> 
> Not sure if it's ok to cross post but I wasn't sure which list to send to.
> 
> On Intel Atom X5-Z8300 SoC (CherryTrail) the install memstick image (amd64)
> halts during boot because of uart.1 settings in device hints.

I have found that FreeBSD’s default device.hints file has fallen
behind on reality and is indeed causing problems on more modern
H/W, like the H/W you mention.

> 
> I'm sure it is there for a reason so what is the alternative actions? Is
> the solution to get a bootable Atom SoC image to create yet another
> distribution or can the installer choose the proper device.hints
> dynamically during boot?

FreeBSD should really get rid of any default hints by now; or at least
limit the hints to what is absolutely certain to be needed or to be
correct.

--
Marcel Moolenaar
mar...@xcllnt.net





signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: hint.uart.1 in device.hints causes freeze at boot

[Lundberg, Johannes]

Yes. Doing that or removing it from device.hints and it will boot properly.
I haven't really dug any deeper as to why, yet.


On Fri, Feb 26, 2016 at 9:56 AM, Ian Lepore  wrote:

> On Fri, 2016-02-26 at 09:48 -0600, Lundberg, Johannes wrote:
> > Hi
> >
> > Not sure if it's ok to cross post but I wasn't sure which list to
> > send to.
> >
> > On Intel Atom X5-Z8300 SoC (CherryTrail) the install memstick image
> > (amd64)
> > halts during boot because of uart.1 settings in device hints.
> >
> > I'm sure it is there for a reason so what is the alternative actions?
> > Is
> > the solution to get a bootable Atom SoC image to create yet another
> > distribution or can the installer choose the proper device.hints
> > dynamically during boot?
> >
> > Best regards
> >
>
> There's not a lot of information to go on here... at what point does it
> halt?  Why do you think it's related to the uart 1 hint?  Does it help
> to set hint.uart.1.disabled=1 in loader before booting?
>
> -- Ian
>
>

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
秘密保持について：この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。
もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、
複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。
---
CONFIDENTIALITY NOTE: The information in this email is confidential
and intended solely for the addressee.
Disclosure, copying, distribution or any other action of use of this
email by person other than intended recipient, is prohibited.
If you are not the intended recipient and have received this email in
error, please destroy the original message.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: hint.uart.1 in device.hints causes freeze at boot

[Ian Lepore]

On Fri, 2016-02-26 at 09:48 -0600, Lundberg, Johannes wrote:
> Hi
> 
> Not sure if it's ok to cross post but I wasn't sure which list to
> send to.
> 
> On Intel Atom X5-Z8300 SoC (CherryTrail) the install memstick image
> (amd64)
> halts during boot because of uart.1 settings in device hints.
> 
> I'm sure it is there for a reason so what is the alternative actions?
> Is
> the solution to get a bootable Atom SoC image to create yet another
> distribution or can the installer choose the proper device.hints
> dynamically during boot?
> 
> Best regards
> 

There's not a lot of information to go on here... at what point does it
halt?  Why do you think it's related to the uart 1 hint?  Does it help
to set hint.uart.1.disabled=1 in loader before booting?

-- Ian

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

hint.uart.1 in device.hints causes freeze at boot

[Lundberg, Johannes]

Hi

Not sure if it's ok to cross post but I wasn't sure which list to send to.

On Intel Atom X5-Z8300 SoC (CherryTrail) the install memstick image (amd64)
halts during boot because of uart.1 settings in device hints.

I'm sure it is there for a reason so what is the alternative actions? Is
the solution to get a bootable Atom SoC image to create yet another
distribution or can the installer choose the proper device.hints
dynamically during boot?

Best regards

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
秘密保持について：この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。
もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、
複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。
---
CONFIDENTIALITY NOTE: The information in this email is confidential
and intended solely for the addressee.
Disclosure, copying, distribution or any other action of use of this
email by person other than intended recipient, is prohibited.
If you are not the intended recipient and have received this email in
error, please destroy the original message.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"