Re: DRM: radeonkms no longer usable following a switch to stable, FreeBSD 12.0-BETA1

[Graham Perrin]

On 22/10/2018 04:34, Graham Perrin wrote:
> …
> /usr/local/bin/xauth: (stdin):1:  bad "remove" command line
> /usr/local/bin/xauth: (stdin):2:  bad "add" command line
> /usr/local/bin/xauth: (stdin):1:  bad "remove" command line
> /usr/local/bin/xauth: (stdin):2:  bad "add" command line
> …
>
> What next? Any suggestions?

tl;dr worked around by stepping away from stable; I stepped up to 13.0-CURRENT.

Summary information:  
.

___
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"

Warning about $local_unbound_tls not being set properly, on first boot of 12.0-BETA1

[Rebecca Cran]

After installing 12.0-BETA1, on the first boot I noticed a warning about 
$local_unbound_tls not being set properly.


It looks like that flag was only added recently by Dag-Erling, in "Add 
support for DNS-over-TLS to the local_unbound service."



--
Rebecca

___
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"

tmpfs corrupt file (aarch64/12.0-ALPHA5)

[Ronald Klop]

Hello,

I'm running this small script which generates changelog file in gzipped  
JSON format.


TMPDIR=/var/tmp
START=1
END=$(( $START + $STEP - 1 ))
while test $START -lt 30
do
svnlite log --xml -r $START:$END -v ~/src/freebsd-base >  
$TMPDIR/bla.xml

bin/xml2json.py > $TMPDIR/commits.$START-$END.json
gzip -f $TMPDIR/commits.$START-$END.json
START=$(( $START + $STEP ))
END=$(( $START + $STEP - 1 ))
done

So $TMPDIR/bla.xml is overwritten every iteration.
Well:
- If $TMPDIR=/var/tmp which is on UFS the script works.
- If %TMPDIR=/tmp which is tmpfs the xml2json.py script very often gives  
errors about the XML structure of bla.xml like if the file is truncated or  
empty.


So it looks like something is happening on tmpfs that the data is not yet  
'synced'. Can this be a threading/cpu-cache issue on aarch64?


This is on an RPI3B+.
FreeBSD rpi3 12.0-ALPHA5 FreeBSD 12.0-ALPHA5 #5 r338616: Wed Sep 12  
22:23:05 CEST 2018  
builder@rpi3:/data/src/obj-head/data/src/head/arm64.aarch64/sys/GENERIC-NODEBUG   
arm64


Can I do more testing or provide more information before creating a PR  
about this?


Regards,
Ronald.
___
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: Facing kernel panic during early boot from 12.0 ALPHA9

[Mark Johnston]

On Tue, Oct 23, 2018 at 07:10:02PM +0530, Rajesh Kumar wrote:
> Hi Mark,
> 
> > From the db> prompt, could you please run "show page" and "show pageq",
> > and post the output?
> 
> The system gets hung when it runs to db prompt. I only have the option to
> force shutdown at that point.  Is there any other way, I can collect what
> you need?

Just a followup for the list: the issue should be fixed by the
following two patches:
https://reviews.freebsd.org/D17418
https://reviews.freebsd.org/D17704
___
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: Has anything changed from 11.2 to 12.0 in PCI MSI/MSIX path?

[Rajesh Kumar]

Hi John,

Thanks a lot. It helps. I backported the changes to 11.2 and tried booting
in my board with success without any need for the said tunables.

I see those changes are marked for MFC after 2 Weeks. But I don't see them
still in stable/11 branch.  So, will it be taken into stable/11 branch by
any chance? If not, can the backported changes be submitted for review to
take into stable/11 branch?

On Thu, Oct 25, 2018 at 1:17 AM John Baldwin  wrote:

> On 10/24/18 3:40 AM, Rajesh Kumar wrote:
> > Hi,
> >
> > I have a amd64 based board. When I tried to boot 11.1 (or) 11.2 in that,
> I
> > needed the following tunables to be set from loader prompt to get it
> booted
> > (otherwise machine reboots continuously).
> >
> > hw.usb.xhci.msi=0
> > hw.usb.xhci.msix=0
> > hw.pci.enable_msi=0
> > hw.pci.enable_msix=0
> >
> > But, when I tried with 12.0 - ALPHA4, I could able to get it booted
> without
> > any tunables.  So, has anything changed significantly on PCI MSI/MSI-X
> > path?
> >
> > Note: I have a forum topic with my observations about the issue on
> > 11.1/11.2 in the following thread
> >
> https://forums.freebsd.org/threads/freebsd-11-1-installation-fails-and-rebooting.65814/
> >
> > Let me know if you need any details.
>
> I believe this was fixed by r338360.
>
> --
> 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: pkg problem on FreeBSD 13.0-CURRENT

[Pieper, Jeffrey E]

This was build this morning and includes: 

commit f37256a01fe12fe4d65128c82c6804d47dd511c1
Author: kib 
Date:   Thu Oct 25 13:37:57 2018 +

Bump base OpenSSL libraries versions to avoid conflict with port's 
libraries.

Reported by:many
Reviewed by:gjb
Sponsored by:   The FreeBSD Foundation
MFC after:  3 hours

Jeff


On 10/25/18, 9:52 AM, "Sean Bruno"  wrote:



On 10/25/18 10:29 AM, Pieper, Jeffrey E wrote:
> I'm seeing:
> 
> Installing pkg-1.10.5_5...
> Extracting pkg-1.10.5_5: 100%
> ld-elf.so.1: Shared object "libssl.so.9" not found, required by "pkg"
> 
> Thanks,
> Jeff

Is this before or after the move of libssl.so.9 -> libssl.so.111 ?

https://svnweb.freebsd.org/changeset/base/339709

sean



___
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: pkg problem on FreeBSD 13.0-CURRENT

[Per Gunnarsson]

I rebuilt pkg from ports and it seems to work now. When I think about it
there was a note in UPDATING that I maybe should have read.

20181009:
    OpenSSL has been updated to version 1.1.1.  This update included
    additional various API changes througout the base system.  It is
    important to rebuild third-party software after upgrading.  The
value
    of __FreeBSD_version has been bumped accordingly.

On 10/25/18 6:29 PM, Pieper, Jeffrey E wrote:
> I'm seeing:
>
> Installing pkg-1.10.5_5...
> Extracting pkg-1.10.5_5: 100%
> ld-elf.so.1: Shared object "libssl.so.9" not found, required by "pkg"
>
> Thanks,
> Jeff
>
> On 10/25/18, 9:18 AM, "owner-freebsd-curr...@freebsd.org on behalf of Kurt 
> Jaeger"  
> wrote:
>
> Hi!
> 
> > On 10/25/18 5:19 PM, Sean Bruno wrote:
> > > pkg-static install -f pkg
> > 
> > It works better now, but there are some complaints.
> 
> If it's only the certificate issue, try this:
> 
> cd /usr/local/etc
> cp pkg.conf.sample pkg.conf
> vi pkg.conf
> -
> PKG_ENV : {
> SSL_NO_VERIFY_PEER: 1
> }
> -
> 
> -- 
> p...@freebsd.org +49 171 3101372  2 years to go !
> ___
> 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"
> 
>

___
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: 12-BETA1 contains warning about non-PNP ISA device

[Warner Losh]

On Thu, Oct 25, 2018 at 10:46 AM Warner Losh  wrote:

>
>
> On Thu, Oct 25, 2018 at 10:26 AM Rebecca Cran 
> wrote:
>
>> On 10/25/18 10:20 AM, Rebecca Cran wrote:
>>
>> >
>> > uart0 pnpinfo _HID=AMDI0020 _UID=0 at handle=\_SB_.FUR0
>> > uart1 pnpinfo _HID=AMDI0020 _UID=1 at handle=\_SB_.FUR1
>> > uart2 pnpinfo _HID=AMDI0020 _UID=2 at handle=\_SB_.FUR2
>> > uart3 pnpinfo _HID=AMDI0020 _UID=3 at handle=\_SB_.FUR3
>>
>>
>> Also, in case it's useful - the output of "devinfo -v | grep -i uart":
>>
>>
>>  uart0 pnpinfo _HID=AMDI0020 _UID=0 at handle=\_SB_.FUR0
>>  unknown pnpinfo _HID=UTK0001A _UID=0 at handle=\_SB_.FUR0.UART
>> (disabled)
>>  uart1 pnpinfo _HID=AMDI0020 _UID=1 at handle=\_SB_.FUR1
>>  unknown pnpinfo _HID=UTK0001B _UID=1 at handle=\_SB_.FUR1.UART
>> (disabled)
>>  uart2 pnpinfo _HID=AMDI0020 _UID=2 at handle=\_SB_.FUR2
>>  uart3 pnpinfo _HID=AMDI0020 _UID=3 at handle=\_SB_.FUR3
>>
>
> Oh! that looks mostly right, though IIRC the higher UIDs might be
> something else. Harmless enough for now, though.
>
> I also think you might be able to test if we can remove a special case
> kludge we have for the AMDI0020 device since it looks like it has STA_ that
> might be sane now. Are you up for that?
>

Oh, wait, no. Other aml dumps show it's still lame :(

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: pkg problem on FreeBSD 13.0-CURRENT

[Pieper, Jeffrey E]

This a new build from distfiles (generated from src) with no packages installed.

Thanks,
Jeff

On 10/25/18, 9:48 AM, "Ben Widawsky"  wrote:

You'll need to update base first, and ideally update all your packages 
before
make delete-old and make delete-old-libs

On 18-10-25 16:29:59, Pieper, Jeffrey E wrote:
> I'm seeing:
> 
> Installing pkg-1.10.5_5...
> Extracting pkg-1.10.5_5: 100%
> ld-elf.so.1: Shared object "libssl.so.9" not found, required by "pkg"
> 
> Thanks,
> Jeff
> 
> On 10/25/18, 9:18 AM, "owner-freebsd-curr...@freebsd.org on behalf of 
Kurt Jaeger"  
wrote:
> 
> Hi!
> 
> > On 10/25/18 5:19 PM, Sean Bruno wrote:
> > > pkg-static install -f pkg
> > 
> > It works better now, but there are some complaints.
> 
> If it's only the certificate issue, try this:
> 
> cd /usr/local/etc
> cp pkg.conf.sample pkg.conf
> vi pkg.conf
> -
> PKG_ENV : {
> SSL_NO_VERIFY_PEER: 1
> }
> -
> 
> -- 
> p...@freebsd.org +49 171 3101372  2 years to go !
> ___
> 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"
> 
> 
> ___
> 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"


___
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: pkg problem on FreeBSD 13.0-CURRENT

[Ben Widawsky]

You'll need to update base first, and ideally update all your packages before
make delete-old and make delete-old-libs

On 18-10-25 16:29:59, Pieper, Jeffrey E wrote:
> I'm seeing:
> 
> Installing pkg-1.10.5_5...
> Extracting pkg-1.10.5_5: 100%
> ld-elf.so.1: Shared object "libssl.so.9" not found, required by "pkg"
> 
> Thanks,
> Jeff
> 
> On 10/25/18, 9:18 AM, "owner-freebsd-curr...@freebsd.org on behalf of Kurt 
> Jaeger"  
> wrote:
> 
> Hi!
> 
> > On 10/25/18 5:19 PM, Sean Bruno wrote:
> > > pkg-static install -f pkg
> > 
> > It works better now, but there are some complaints.
> 
> If it's only the certificate issue, try this:
> 
> cd /usr/local/etc
> cp pkg.conf.sample pkg.conf
> vi pkg.conf
> -
> PKG_ENV : {
> SSL_NO_VERIFY_PEER: 1
> }
> -
> 
> -- 
> p...@freebsd.org +49 171 3101372  2 years to go !
> ___
> 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"
> 
> 
> ___
> 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"
___
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: pkg problem on FreeBSD 13.0-CURRENT

[Sean Bruno]

On 10/25/18 10:29 AM, Pieper, Jeffrey E wrote:
> I'm seeing:
> 
> Installing pkg-1.10.5_5...
> Extracting pkg-1.10.5_5: 100%
> ld-elf.so.1: Shared object "libssl.so.9" not found, required by "pkg"
> 
> Thanks,
> Jeff

Is this before or after the move of libssl.so.9 -> libssl.so.111 ?

https://svnweb.freebsd.org/changeset/base/339709

sean



signature.asc
Description: OpenPGP digital signature

Re: 12-BETA1 contains warning about non-PNP ISA device

[Rebecca Cran]

On 10/25/18 10:46 AM, Warner Losh wrote:



Oh! that looks mostly right, though IIRC the higher UIDs might be 
something else. Harmless enough for now, though.



Thanks.



I also think you might be able to test if we can remove a special case 
kludge we have for the AMDI0020 device since it looks like it has STA_ 
that might be sane now. Are you up for that?




Sure!


--
Rebecca

___
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: 12-BETA1 contains warning about non-PNP ISA device

[Warner Losh]

On Thu, Oct 25, 2018 at 10:26 AM Rebecca Cran  wrote:

> On 10/25/18 10:20 AM, Rebecca Cran wrote:
>
> >
> > uart0 pnpinfo _HID=AMDI0020 _UID=0 at handle=\_SB_.FUR0
> > uart1 pnpinfo _HID=AMDI0020 _UID=1 at handle=\_SB_.FUR1
> > uart2 pnpinfo _HID=AMDI0020 _UID=2 at handle=\_SB_.FUR2
> > uart3 pnpinfo _HID=AMDI0020 _UID=3 at handle=\_SB_.FUR3
>
>
> Also, in case it's useful - the output of "devinfo -v | grep -i uart":
>
>
>  uart0 pnpinfo _HID=AMDI0020 _UID=0 at handle=\_SB_.FUR0
>  unknown pnpinfo _HID=UTK0001A _UID=0 at handle=\_SB_.FUR0.UART
> (disabled)
>  uart1 pnpinfo _HID=AMDI0020 _UID=1 at handle=\_SB_.FUR1
>  unknown pnpinfo _HID=UTK0001B _UID=1 at handle=\_SB_.FUR1.UART
> (disabled)
>  uart2 pnpinfo _HID=AMDI0020 _UID=2 at handle=\_SB_.FUR2
>  uart3 pnpinfo _HID=AMDI0020 _UID=3 at handle=\_SB_.FUR3
>

Oh! that looks mostly right, though IIRC the higher UIDs might be something
else. Harmless enough for now, though.

I also think you might be able to test if we can remove a special case
kludge we have for the AMDI0020 device since it looks like it has STA_ that
might be sane now. Are you up for that?

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: pkg problem on FreeBSD 13.0-CURRENT

[Warner Losh]

On Thu, Oct 25, 2018 at 10:17 AM Kurt Jaeger  wrote:

> Hi!
>
> > On 10/25/18 5:19 PM, Sean Bruno wrote:
> > > pkg-static install -f pkg
> >
> > It works better now, but there are some complaints.
>
> If it's only the certificate issue, try this:
>
> cd /usr/local/etc
> cp pkg.conf.sample pkg.conf
> vi pkg.conf
> -
> PKG_ENV : {
> SSL_NO_VERIFY_PEER: 1
> }
> -
>

The issues I've hit needing pkg-static to power through are all
shared-library issues.

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: pkg problem on FreeBSD 13.0-CURRENT

[Pieper, Jeffrey E]

I'm seeing:

Installing pkg-1.10.5_5...
Extracting pkg-1.10.5_5: 100%
ld-elf.so.1: Shared object "libssl.so.9" not found, required by "pkg"

Thanks,
Jeff

On 10/25/18, 9:18 AM, "owner-freebsd-curr...@freebsd.org on behalf of Kurt 
Jaeger"  wrote:

Hi!

> On 10/25/18 5:19 PM, Sean Bruno wrote:
> > pkg-static install -f pkg
> 
> It works better now, but there are some complaints.

If it's only the certificate issue, try this:

cd /usr/local/etc
cp pkg.conf.sample pkg.conf
vi pkg.conf
-
PKG_ENV : {
SSL_NO_VERIFY_PEER: 1
}
-

-- 
p...@freebsd.org +49 171 3101372  2 years to go !
___
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"


___
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: 12-BETA1 contains warning about non-PNP ISA device

[Rebecca Cran]

On 10/25/18 10:20 AM, Rebecca Cran wrote:



    uart0 pnpinfo _HID=AMDI0020 _UID=0 at handle=\_SB_.FUR0
    uart1 pnpinfo _HID=AMDI0020 _UID=1 at handle=\_SB_.FUR1
    uart2 pnpinfo _HID=AMDI0020 _UID=2 at handle=\_SB_.FUR2
    uart3 pnpinfo _HID=AMDI0020 _UID=3 at handle=\_SB_.FUR3



Also, in case it's useful - the output of "devinfo -v | grep -i uart":


    uart0 pnpinfo _HID=AMDI0020 _UID=0 at handle=\_SB_.FUR0
    unknown pnpinfo _HID=UTK0001A _UID=0 at handle=\_SB_.FUR0.UART 
(disabled)

    uart1 pnpinfo _HID=AMDI0020 _UID=1 at handle=\_SB_.FUR1
    unknown pnpinfo _HID=UTK0001B _UID=1 at handle=\_SB_.FUR1.UART 
(disabled)

    uart2 pnpinfo _HID=AMDI0020 _UID=2 at handle=\_SB_.FUR2
    uart3 pnpinfo _HID=AMDI0020 _UID=3 at handle=\_SB_.FUR3


--

Rebecca

___
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: 12-BETA1 contains warning about non-PNP ISA device

[Rebecca Cran]

On 10/25/18 10:18 AM, Warner Losh wrote:



That seems incorrect. It looks like we're attaching too much. what does
devinfo -v | grep uart tell you?



    uart0 pnpinfo _HID=AMDI0020 _UID=0 at handle=\_SB_.FUR0
    uart1 pnpinfo _HID=AMDI0020 _UID=1 at handle=\_SB_.FUR1
    uart2 pnpinfo _HID=AMDI0020 _UID=2 at handle=\_SB_.FUR2
    uart3 pnpinfo _HID=AMDI0020 _UID=3 at handle=\_SB_.FUR3


--
Rebecca

___
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: 12-BETA1 contains warning about non-PNP ISA device

[Warner Losh]

On Thu, Oct 25, 2018 at 10:16 AM Rebecca Cran  wrote:

> On 10/25/18 10:00 AM, Warner Losh wrote:
>
> >
> > I suspect you can just lose those hints in the hints file and be fine.
> The
> > uart should attach via acpi. The keyboard won't, however, since it isn't
> > enabled. Can you try removing these lines from your hints file and see if
> > the problem persists? Note this is for debugging purposes only.
> >
> > hint.atkbdc.0.at="isa"
> > hint.uart.0.at="isa"
>
>
> That seems to work. After also removing uart1 from the hints file, I get:
>
>
> uart0: <16x50 with 256 byte FIFO> iomem
> 0xfedc9000-0xfedc9fff,0xfedc7000-0xfedc7fff irq 3 on acpi0
> uart1: <16x50 with 256 byte FIFO> iomem
> 0xfedca000-0xfedcafff,0xfedc8000-0xfedc8fff irq 4 on acpi0
> uart2: <16x50 with 256 byte FIFO> iomem
> 0xfedce000-0xfedcefff,0xfedcc000-0xfedccfff irq 3 on acpi0
> uart3: <16x50 with 256 byte FIFO> iomem
> 0xfedcf000-0xfedc,0xfedcd000-0xfedcdfff irq 4 on acpi0
>

That seems incorrect. It looks like we're attaching too much. what does
devinfo -v | grep uart tell you?

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: 12-BETA1 contains warning about non-PNP ISA device

[Rebecca Cran]

On 10/25/18 10:00 AM, Warner Losh wrote:



I suspect you can just lose those hints in the hints file and be fine. The
uart should attach via acpi. The keyboard won't, however, since it isn't
enabled. Can you try removing these lines from your hints file and see if
the problem persists? Note this is for debugging purposes only.

hint.atkbdc.0.at="isa"
hint.uart.0.at="isa"



That seems to work. After also removing uart1 from the hints file, I get:


uart0: <16x50 with 256 byte FIFO> iomem 
0xfedc9000-0xfedc9fff,0xfedc7000-0xfedc7fff irq 3 on acpi0
uart1: <16x50 with 256 byte FIFO> iomem 
0xfedca000-0xfedcafff,0xfedc8000-0xfedc8fff irq 4 on acpi0
uart2: <16x50 with 256 byte FIFO> iomem 
0xfedce000-0xfedcefff,0xfedcc000-0xfedccfff irq 3 on acpi0
uart3: <16x50 with 256 byte FIFO> iomem 
0xfedcf000-0xfedc,0xfedcd000-0xfedcdfff irq 4 on acpi0



--
Rebecca

___
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: pkg problem on FreeBSD 13.0-CURRENT

[Kurt Jaeger]

Hi!

> On 10/25/18 5:19 PM, Sean Bruno wrote:
> > pkg-static install -f pkg
> 
> It works better now, but there are some complaints.

If it's only the certificate issue, try this:

cd /usr/local/etc
cp pkg.conf.sample pkg.conf
vi pkg.conf
-
PKG_ENV : {
SSL_NO_VERIFY_PEER: 1
}
-

-- 
p...@freebsd.org +49 171 3101372  2 years to go !
___
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: pkg problem on FreeBSD 13.0-CURRENT

[Per Gunnarsson]

On 10/25/18 5:19 PM, Sean Bruno wrote:
> pkg-static install -f pkg

It works better now, but there are some complaints.


root@konjak:/usr # pkg-static install -f pkg
pkg-static: Warning: Major OS version upgrade detected.  Running
"pkg-static install -f pkg" recommended
Updating FreeBSD repository catalogue...
pkg-static: Repository FreeBSD load error: access repo
file(/var/db/pkg/repo-FreeBSD.sqlite) failed: No such file or directory
Fetching meta.txz: 100%    944 B   0.9kB/s    00:01   
pkg-static: error reading public key:
error::lib(0):func(0):reason(0)
pkg-static: No trusted certificate has been used to sign the repository
repository FreeBSD has no meta file, using default settings
Fetching packagesite.txz: 100%    6 MiB   2.2MB/s    00:03   
pkg-static: error reading public key:
error::lib(0):func(0):reason(0)
pkg-static: No trusted certificate has been used to sign the repository
Unable to update repository FreeBSD
Error updating repositories!



signature.asc
Description: OpenPGP digital signature

Re: 12-BETA1 contains warning about non-PNP ISA device

[Warner Losh]

On Thu, Oct 25, 2018 at 9:35 AM Rebecca Cran  wrote:

> On 10/25/18 5:02 AM, Rodney W. Grimes wrote:
>
> > Can you please reply with the specific device.
> > If you have seen one it may be an issue to removing it,
> > especially if this is on a "new AMD" system.
>
>
> This is a new Ryzen system. For me, I get warnings about atkbdc0 and uart0:
>
>
> atkbdc0:  at port 0x60,0x64 on isa0
> atkbd0:  irq 1 on atkbdc0
> kbd0 at atkbd0
> atkbd0: [GIANT-LOCKED]
> atkbdc0: non-PNP ISA device will be removed from GENERIC in FreeBSD 12.
> uart0: <16550 or compatible> at port 0x3f8 irq 4 flags 0x10 on isa0
> uart0: non-PNP ISA device will be removed from GENERIC in FreeBSD 12.
>

I suspect you can just lose those hints in the hints file and be fine. The
uart should attach via acpi. The keyboard won't, however, since it isn't
enabled. Can you try removing these lines from your hints file and see if
the problem persists? Note this is for debugging purposes only.

hint.atkbdc.0.at="isa"
hint.uart.0.at="isa"

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: savecore: BFD: BFD 2.17.50 [FreeBSD] 2007-07-03 assertion fail /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elf64-x86-64.c:276

[John Baldwin]

On 10/25/18 2:14 AM, Marcin Cieslak wrote:
> On Wed, 24 Oct 2018, John Baldwin wrote:
> 
>> On 10/23/18 10:58 AM, Marcin Cieslak wrote:
>>> This GDB was configured as "amd64-marcel-freebsd"...BFD: 
>>> /boot/kernel/kernel: invalid relocation type 37
>>> BFD: BFD 2.17.50 [FreeBSD] 2007-07-03 assertion fail 
>>> /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elf64-x86-64.c:276
>>>
>>> The kernel has been built on 11.1 with LD=/usr/bin/ld.lld
>>>
>>> Is this something that matters at all?
>>
>> It is not something that is likely to be fixed.  If you pkg install gdb from
>> ports, is the kgdb it includes able to examine the crash dump?
> 
> Not really (using 8.2 from ports):
> 
> # /usr/local/bin/kgdb82 -n 5 /usr/obj/usr/src/sys/GENERIC/kernel.debug
> GNU gdb (GDB) 8.2 [GDB v8.2 for FreeBSD]
> Copyright (C) 2018 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later 
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> Type "show copying" and "show warranty" for details.
> This GDB was configured as "x86_64-portbld-freebsd11.1".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> .
> Find the GDB manual and other documentation resources online at:
> .
> 
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from /usr/obj/usr/src/sys/GENERIC/kernel.debug...done.
> thread.c:93: internal-error: struct thread_info *inferior_thread(): Assertion 
> `tp' failed.
> A problem internal to GDB has been detected,
> further debugging may prove unreliable.
> Quit this debugging session? (y or n) 

This usually means the kernel image you are using doesn't match the vmcore, so
it's reading garbage data from the vmcore since the symbol offsets are wrong.

You can test this by doing what crashinfo does: compare the version string in 
the
/var/crash/info.5 file with 'p version' in kgdb (or gdb) of the kernel without
a vmcore.

-- 
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: 12-BETA1 contains warning about non-PNP ISA device

[Rebecca Cran]

On 10/25/18 5:02 AM, Rodney W. Grimes wrote:


Can you please reply with the specific device.
If you have seen one it may be an issue to removing it,
especially if this is on a "new AMD" system.



This is a new Ryzen system. For me, I get warnings about atkbdc0 and uart0:


atkbdc0:  at port 0x60,0x64 on isa0
atkbd0:  irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbdc0: non-PNP ISA device will be removed from GENERIC in FreeBSD 12.
uart0: <16550 or compatible> at port 0x3f8 irq 4 flags 0x10 on isa0
uart0: non-PNP ISA device will be removed from GENERIC in FreeBSD 12.


Yes, and they well be removed from GENERIC in BETA2,
as I just approved the RFA to merge that fix to stable/12.



Thanks, good to know they haven't been forgotten about.


--
Rebecca

___
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: pkg problem on FreeBSD 13.0-CURRENT

[Sean Bruno]

On 10/25/18 6:57 AM, Kurt Jaeger wrote:
> Hi!
> 
>> FreeBSD konjak 13.0-CURRENT FreeBSD 13.0-CURRENT r339705 GENERIC  amd64
>>
>> pkg-static install -f pkg
>> pkg-static: Warning: Major OS version upgrade detected.  Running
>> "pkg-static install -f pkg" recommended
>> Updating FreeBSD repository catalogue...
>> pkg-static: Repository FreeBSD load error: access repo
>> file(/var/db/pkg/repo-FreeBSD.sqlite) failed: No such file or directory
>> pkg-static: http://pkg.FreeBSD.org/FreeBSD:13:amd64/latest/meta.txz: Not
>> Found
> 
> The package builders are not yet providing packages for 13.0-CURRENT.
> 
> It's being worked on, but will take a little more time.
> 


Portmgr has pushed out packages for 13, give 'em a spin and see what
happens.

sean



signature.asc
Description: OpenPGP digital signature

Re: 12-BETA1 contains warning about non-PNP ISA device

[Rodney W. Grimes]

> On Thu, Oct 25, 2018 at 8:10 AM Eric van Gyzen  wrote:
> 
> > On 10/25/18 6:57 AM, Rodney W. Grimes wrote:
> > >>> I noticed a warning on a new AMD system running 12-BETA1:
> > >>>
> > >>> non-PNP ISA device will be removed from GENERIC in FreeBSD 12.
> > >> Can you please reply with the specific device.
> > >> If you have seen one it may be an issue to removing it,
> > >> especially if this is on a "new AMD" system.
> > >
> > > Further investigation shows me that this comes from
> > > generic code in sys/isa/isa_common.c, and does not
> > > come from any specific driver markings.
> >
> > My new Ryzen says:
> >
> > atkbdc0: non-PNP ISA device will be removed from GENERIC in FreeBSD 12.
> >
> > Believe it or not, my motherboard has a PS/2 connector, so I could
> > actually use this driver someday.
> >
> 
> I'll look into this. Rest assured, we won't be removing this. In theory,
> all such devices should be attaching via ACPI.
> 
> Can you send me the output of 'devinfo -v' off list?

I suspect something funny happens when there is already a
USB keyboard plugged in that has been enumerated by ACPI,
I would be willing to speculate that it leaves the legacy
port visible as a legacy non PnP/Non ACPI device.

-- 
Rod Grimes rgri...@freebsd.org
___
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: 12-BETA1 contains warning about non-PNP ISA device

[Warner Losh]

On Thu, Oct 25, 2018 at 8:10 AM Eric van Gyzen  wrote:

> On 10/25/18 6:57 AM, Rodney W. Grimes wrote:
> >>> I noticed a warning on a new AMD system running 12-BETA1:
> >>>
> >>> non-PNP ISA device will be removed from GENERIC in FreeBSD 12.
> >> Can you please reply with the specific device.
> >> If you have seen one it may be an issue to removing it,
> >> especially if this is on a "new AMD" system.
> >
> > Further investigation shows me that this comes from
> > generic code in sys/isa/isa_common.c, and does not
> > come from any specific driver markings.
>
> My new Ryzen says:
>
> atkbdc0: non-PNP ISA device will be removed from GENERIC in FreeBSD 12.
>
> Believe it or not, my motherboard has a PS/2 connector, so I could
> actually use this driver someday.
>

I'll look into this. Rest assured, we won't be removing this. In theory,
all such devices should be attaching via ACPI.

Can you send me the output of 'devinfo -v' off list?

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: 12-BETA1 contains warning about non-PNP ISA device

[Eric van Gyzen]

On 10/25/18 6:57 AM, Rodney W. Grimes wrote:

I noticed a warning on a new AMD system running 12-BETA1:

non-PNP ISA device will be removed from GENERIC in FreeBSD 12.

Can you please reply with the specific device.
If you have seen one it may be an issue to removing it,
especially if this is on a "new AMD" system.


Further investigation shows me that this comes from
generic code in sys/isa/isa_common.c, and does not
come from any specific driver markings.


My new Ryzen says:

atkbdc0: non-PNP ISA device will be removed from GENERIC in FreeBSD 12.

Believe it or not, my motherboard has a PS/2 connector, so I could 
actually use this driver someday.


Eric
___
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: pkg problem on FreeBSD 13.0-CURRENT

[Kurt Jaeger]

Hi!

> FreeBSD konjak 13.0-CURRENT FreeBSD 13.0-CURRENT r339705 GENERIC  amd64
> 
> pkg-static install -f pkg
> pkg-static: Warning: Major OS version upgrade detected.  Running
> "pkg-static install -f pkg" recommended
> Updating FreeBSD repository catalogue...
> pkg-static: Repository FreeBSD load error: access repo
> file(/var/db/pkg/repo-FreeBSD.sqlite) failed: No such file or directory
> pkg-static: http://pkg.FreeBSD.org/FreeBSD:13:amd64/latest/meta.txz: Not
> Found

The package builders are not yet providing packages for 13.0-CURRENT.

It's being worked on, but will take a little more time.

-- 
p...@freebsd.org +49 171 3101372  2 years to go !
___
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"

pkg problem on FreeBSD 13.0-CURRENT

[Per Gunnarsson]

FreeBSD konjak 13.0-CURRENT FreeBSD 13.0-CURRENT r339705 GENERIC  amd64

pkg-static install -f pkg
pkg-static: Warning: Major OS version upgrade detected.  Running
"pkg-static install -f pkg" recommended
Updating FreeBSD repository catalogue...
pkg-static: Repository FreeBSD load error: access repo
file(/var/db/pkg/repo-FreeBSD.sqlite) failed: No such file or directory
pkg-static: http://pkg.FreeBSD.org/FreeBSD:13:amd64/latest/meta.txz: Not
Found
repository FreeBSD has no meta file, using default settings
pkg-static:
http://pkg.FreeBSD.org/FreeBSD:13:amd64/latest/packagesite.txz: Not Found
Unable to update repository FreeBSD
Error updating repositories!

Regards,

Per Gunnarsson

___
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: 12-BETA1 contains warning about non-PNP ISA device

[Rodney W. Grimes]

> > I noticed a warning on a new AMD system running 12-BETA1:  
> > 
> > non-PNP ISA device will be removed from GENERIC in FreeBSD 12.  
> Can you please reply with the specific device.
> If you have seen one it may be an issue to removing it,
> especially if this is on a "new AMD" system.

Further investigation shows me that this comes from
generic code in sys/isa/isa_common.c, and does not
come from any specific driver markings.

> > It looks like it was introduced by Warner in r327120. Should those devices 
> > have been removed already?
> 
> Yes, and they well be removed from GENERIC in BETA2,
> as I just approved the RFA to merge that fix to stable/12.

That is an incorrect statement, what I approved does not
in any way effect this error that I can tell.

Thanks,
-- 
Rod Grimes rgri...@freebsd.org
___
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"

fix WARNING pid 24503 (uhsoctl): ioctl sign-extension ioctl ffffffff8044692b

[Marcin Cieslak]

The following patch seems to fix the signed ioctl value warnings
in uhsoctl().

The code is the same in the current and stable branches.

Marcin

Index: usr.sbin/uhsoctl/uhsoctl.c
===
--- usr.sbin/uhsoctl/uhsoctl.c  (revision 339406)
+++ usr.sbin/uhsoctl/uhsoctl.c  (working copy)
@@ -360,7 +360,7 @@
 
 /* Add/remove IP address from an interface */
 static int
-ifaddr_ad(int d, const char *ifnam, struct sockaddr *sa, struct sockaddr *mask)
+ifaddr_ad(unsigned long d, const char *ifnam, struct sockaddr *sa, struct 
sockaddr *mask)
 {
struct ifaliasreq req;
int fd, error;


smime.p7s
Description: S/MIME Cryptographic Signature

Re: 12-BETA1 contains warning about non-PNP ISA device

[Rodney W. Grimes]

> I noticed a warning on a new AMD system running 12-BETA1:  
> 
> non-PNP ISA device will be removed from GENERIC in FreeBSD 12.  
Can you please reply with the specific device.
If you have seen one it may be an issue to removing it,
especially if this is on a "new AMD" system.

> 
> It looks like it was introduced by Warner in r327120. Should those devices 
> have been removed already?

Yes, and they well be removed from GENERIC in BETA2,
as I just approved the RFA to merge that fix to stable/12.

Thanks,
-- 
Rod Grimes rgri...@freebsd.org
___
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: Regression of dtrace on 13-CURRENT

[Yasuhiro KIMURA]

From: Yasuhiro KIMURA 
Subject: Regression of dtrace on 13-CURRENT
Date: Thu, 25 Oct 2018 14:46:00 +0900 (JST)

> So there is regression about dtrace between r339436 and r339548.

I submitted this problem to Bugzilla.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232675

---
Yasuhiro KIMURA
___
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: savecore: BFD: BFD 2.17.50 [FreeBSD] 2007-07-03 assertion fail /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elf64-x86-64.c:276

[Marcin Cieslak]

On Wed, 24 Oct 2018, John Baldwin wrote:

> On 10/23/18 10:58 AM, Marcin Cieslak wrote:
> > This GDB was configured as "amd64-marcel-freebsd"...BFD: 
> > /boot/kernel/kernel: invalid relocation type 37
> > BFD: BFD 2.17.50 [FreeBSD] 2007-07-03 assertion fail 
> > /usr/src/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elf64-x86-64.c:276
> > 
> > The kernel has been built on 11.1 with LD=/usr/bin/ld.lld
> > 
> > Is this something that matters at all?
> 
> It is not something that is likely to be fixed.  If you pkg install gdb from
> ports, is the kgdb it includes able to examine the crash dump?

Not really (using 8.2 from ports):

# /usr/local/bin/kgdb82 -n 5 /usr/obj/usr/src/sys/GENERIC/kernel.debug
GNU gdb (GDB) 8.2 [GDB v8.2 for FreeBSD]
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-portbld-freebsd11.1".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/obj/usr/src/sys/GENERIC/kernel.debug...done.
thread.c:93: internal-error: struct thread_info *inferior_thread(): Assertion 
`tp' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) 

With regular base kgdb I can open it but I can't get any backtrace or anything:

Cannot access memory at address 0x0
(kgdb) info reg
rax0x0  0
rbx0x0  0
rcx0x0  0
rdx0x0  0
rsi0x0  0
rdi0x0  0
rbp0x0  0x0
rsp0x0  0x0
r8 0x0  0
r9 0x0  0
r100x0  0
r110x0  0
r120x0  0
r130x0  0
r140x0  0
r150x0  0
rip0x0  0
eflags 0x0  0
cs 0x0  0
ss 0x0  0
ds 0x0  0
es 0x0  0
fs 0x0  0
gs 0x0  0

What should I try next? at what stage is bfd involved in the savecore process?

Marcin


smime.p7s
Description: S/MIME Cryptographic Signature

Información importante al cliente. - clave (10535)

[current]

___
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"