Update from r347952 to r348848

[driesm.michiels]

Hi stable mailing list!

 

Today I tried updating my machine to r348848 from r347952. It didn't go as
smooth as I would've hoped (normally its just fine).

After doing the upgrade using the standard upgrade from source procedure I
went ahead and booted my machine.

During booting I got black screened (after the messages below) and booting
got stuck from there.

*   Loading kernel modules:
*   Anon_inodefs_init:
*   Sysctl_warn_reuse: can't re-use a leaf (compat.linuxkpi.debug)!
*   Black screen and booting stops

 

I went ahead and reverted to a ZFS snapshot preupdate so all is fine again.

Any pointers as to where the regression might be? I did a clean build to
update.

 

Regards,

Dries

 

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

Re: FreeBSD 11.3-BETA3 Now Available

[Glen Barber]

On Sat, Jun 08, 2019 at 01:39:49PM +0300, Slawa Olhovchenkov wrote:
> On Fri, Jun 07, 2019 at 10:26:34PM +, Glen Barber wrote:
> 
> > The third BETA build of the 11.3-RELEASE release cycle is now available.
> 
> Can some one from re@ do MFC r348772 to 11.3-RELEASE before release?
> This is important fix.

The MFC timer for the change in question is 2 weeks, presumably to allow
time to detect any issues in 13-CURRENT before the merge is done to
stable/12 and stable/11.  The change in question was committed three
days ago.

I have CC'd the original committer, nonetheless.

Glen



signature.asc
Description: PGP signature

Re: FreeBSD 11.3-BETA3 Now Available

[Slawa Olhovchenkov]

On Mon, Jun 10, 2019 at 03:13:31PM +, Glen Barber wrote:

> On Sat, Jun 08, 2019 at 01:39:49PM +0300, Slawa Olhovchenkov wrote:
> > On Fri, Jun 07, 2019 at 10:26:34PM +, Glen Barber wrote:
> > 
> > > The third BETA build of the 11.3-RELEASE release cycle is now available.
> > 
> > Can some one from re@ do MFC r348772 to 11.3-RELEASE before release?
> > This is important fix.
> 
> The MFC timer for the change in question is 2 weeks, presumably to allow
> time to detect any issues in 13-CURRENT before the merge is done to
> stable/12 and stable/11.  The change in question was committed three
> days ago.
> 
> I have CC'd the original committer, nonetheless.

I am ask about include MFCed commit in RELEASE image, not in stable
trunk.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Update from r347952 to r348848

[Johannes Lundberg]

Hi

What graphics driver do you have installed?

This error should not happen if you have the latest drm-kmod package.
Try 'pkg update && pkg install drm-kmod'.

On 6/10/19 5:26 AM, driesm.michi...@gmail.com wrote:
> Hi stable mailing list!
>
>  
>
> Today I tried updating my machine to r348848 from r347952. It didn't go as
> smooth as I would've hoped (normally its just fine).
>
> After doing the upgrade using the standard upgrade from source procedure I
> went ahead and booted my machine.
>
> During booting I got black screened (after the messages below) and booting
> got stuck from there.
>
> * Loading kernel modules:
> * Anon_inodefs_init:
> * Sysctl_warn_reuse: can't re-use a leaf (compat.linuxkpi.debug)!
> * Black screen and booting stops
>
>  
>
> I went ahead and reverted to a ZFS snapshot preupdate so all is fine again.
>
> Any pointers as to where the regression might be? I did a clean build to
> update.
>
>  
>
> Regards,
>
> Dries
>
>  
>
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

RE: Update from r347952 to r348848

[driesm.michiels]

> From: Johannes Lundberg 
> 
> Hi
> 
> What graphics driver do you have installed?

I have drm-kmod installed and rebuild/reinstall every time I install my kernel 
by setting PORTS_MODULES = graphics/drm-kmod in make.conf
I have an Intel(R) Xeon(R) CPU E3-1245 v5 @ 3.50GHz with skylake graphics so 
using the i915 kms driver.

> 
> This error should not happen if you have the latest drm-kmod package.
> Try 'pkg update && pkg install drm-kmod'.
> 
> On 6/10/19 5:26 AM, driesm.michi...@gmail.com wrote:
> > Hi stable mailing list!
> >
> >
> >
> > Today I tried updating my machine to r348848 from r347952. It didn't
> > go as smooth as I would've hoped (normally its just fine).
> >
> > After doing the upgrade using the standard upgrade from source
> > procedure I went ahead and booted my machine.
> >
> > During booting I got black screened (after the messages below) and
> > booting got stuck from there.
> >
> > *   Loading kernel modules:
> > *   Anon_inodefs_init:
> > *   Sysctl_warn_reuse: can't re-use a leaf (compat.linuxkpi.debug)!
> > *   Black screen and booting stops
> >
> >
> >
> > I went ahead and reverted to a ZFS snapshot preupdate so all is fine again.
> >
> > Any pointers as to where the regression might be? I did a clean build
> > to update.
> >
> >
> >
> > Regards,
> >
> > Dries
> >
> >
> >
> > ___
> > freebsd-stable@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > To unsubscribe, send any mail to "freebsd-stable-
> unsubscr...@freebsd.org"

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

Re: Update from r347952 to r348848

[Johannes Lundberg]

drm-kmod is a meta port. Show me 'pkg info | grep drm' to see what is
actually installed.

On 6/10/19 12:33 PM, driesm.michi...@gmail.com wrote:
>
>> From: Johannes Lundberg 
>>
>> Hi
>>
>> What graphics driver do you have installed?
> I have drm-kmod installed and rebuild/reinstall every time I install my 
> kernel by setting PORTS_MODULES = graphics/drm-kmod in make.conf
> I have an Intel(R) Xeon(R) CPU E3-1245 v5 @ 3.50GHz with skylake graphics so 
> using the i915 kms driver.
>
>> This error should not happen if you have the latest drm-kmod package.
>> Try 'pkg update && pkg install drm-kmod'.
>>
>> On 6/10/19 5:26 AM, driesm.michi...@gmail.com wrote:
>>> Hi stable mailing list!
>>>
>>>
>>>
>>> Today I tried updating my machine to r348848 from r347952. It didn't
>>> go as smooth as I would've hoped (normally its just fine).
>>>
>>> After doing the upgrade using the standard upgrade from source
>>> procedure I went ahead and booted my machine.
>>>
>>> During booting I got black screened (after the messages below) and
>>> booting got stuck from there.
>>>
>>> *   Loading kernel modules:
>>> *   Anon_inodefs_init:
>>> *   Sysctl_warn_reuse: can't re-use a leaf (compat.linuxkpi.debug)!
>>> *   Black screen and booting stops
>>>
>>>
>>>
>>> I went ahead and reverted to a ZFS snapshot preupdate so all is fine again.
>>>
>>> Any pointers as to where the regression might be? I did a clean build
>>> to update.
>>>
>>>
>>>
>>> Regards,
>>>
>>> Dries
>>>
>>>
>>>
>>> ___
>>> freebsd-stable@freebsd.org mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
>>> To unsubscribe, send any mail to "freebsd-stable-
>> unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Update from r347952 to r348848

[Dries Michiels]

pkg info | grep drm
drm-kmod-g20181126 Metaport of DRM modules for the linuxkpi-based 
KMS components
drm-next-kmod-4.11.g20181027   DRM modules for the linuxkpi-based KMS components
libdrm-2.4.96,1Userspace interface to kernel Direct Rendering 
Module services

Running 12-STABLE on my system.

Get Outlook for Android


From: Johannes Lundberg 
Sent: Monday, June 10, 2019 9:59:36 PM
To: driesm.michi...@gmail.com; freebsd-stable@freebsd.org
Subject: Re: Update from r347952 to r348848

drm-kmod is a meta port. Show me 'pkg info | grep drm' to see what is
actually installed.

On 6/10/19 12:33 PM, driesm.michi...@gmail.com wrote:
>
>> From: Johannes Lundberg 
>>
>> Hi
>>
>> What graphics driver do you have installed?
> I have drm-kmod installed and rebuild/reinstall every time I install my 
> kernel by setting PORTS_MODULES = graphics/drm-kmod in make.conf
> I have an Intel(R) Xeon(R) CPU E3-1245 v5 @ 3.50GHz with skylake graphics so 
> using the i915 kms driver.
>
>> This error should not happen if you have the latest drm-kmod package.
>> Try 'pkg update && pkg install drm-kmod'.
>>
>> On 6/10/19 5:26 AM, driesm.michi...@gmail.com wrote:
>>> Hi stable mailing list!
>>>
>>>
>>>
>>> Today I tried updating my machine to r348848 from r347952. It didn't
>>> go as smooth as I would've hoped (normally its just fine).
>>>
>>> After doing the upgrade using the standard upgrade from source
>>> procedure I went ahead and booted my machine.
>>>
>>> During booting I got black screened (after the messages below) and
>>> booting got stuck from there.
>>>
>>> *   Loading kernel modules:
>>> *   Anon_inodefs_init:
>>> *   Sysctl_warn_reuse: can't re-use a leaf (compat.linuxkpi.debug)!
>>> *   Black screen and booting stops
>>>
>>>
>>>
>>> I went ahead and reverted to a ZFS snapshot preupdate so all is fine again.
>>>
>>> Any pointers as to where the regression might be? I did a clean build
>>> to update.
>>>
>>>
>>>
>>> Regards,
>>>
>>> Dries
>>>
>>>
>>>
>>> ___
>>> freebsd-stable@freebsd.org mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
>>> To unsubscribe, send any mail to "freebsd-stable-
>> unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Update from r347952 to r348848

[Johannes Lundberg]

drm-next-kmod has been replaced by several packages. Not sure why 'pkg
install drm-kmod' doesn't replace it with the new one.

Try 'pkg delete drm-kmod drm-next-kmod && pkg install drm-kmod'

You should get drm-fbsd12.0-kmod-4.16.g20190430.


On 6/10/19 1:05 PM, Dries Michiels wrote:
> pkg info | grep drm
> drm-kmod-g20181126 Metaport of DRM modules for the
> linuxkpi-based KMS components
> drm-next-kmod-4.11.g20181027   DRM modules for the linuxkpi-based KMS
> components
> libdrm-2.4.96,1    Userspace interface to kernel Direct
> Rendering Module services
>
> Running 12-STABLE on my system.
>
> Get Outlook for Android 
>
> 
> *From:* Johannes Lundberg 
> *Sent:* Monday, June 10, 2019 9:59:36 PM
> *To:* driesm.michi...@gmail.com; freebsd-stable@freebsd.org
> *Subject:* Re: Update from r347952 to r348848
>  
> drm-kmod is a meta port. Show me 'pkg info | grep drm' to see what is
> actually installed.
>
> On 6/10/19 12:33 PM, driesm.michi...@gmail.com wrote:
> >
> >> From: Johannes Lundberg 
> >>
> >> Hi
> >>
> >> What graphics driver do you have installed?
> > I have drm-kmod installed and rebuild/reinstall every time I install
> my kernel by setting PORTS_MODULES = graphics/drm-kmod in make.conf
> > I have an Intel(R) Xeon(R) CPU E3-1245 v5 @ 3.50GHz with skylake
> graphics so using the i915 kms driver.
> >
> >> This error should not happen if you have the latest drm-kmod package.
> >> Try 'pkg update && pkg install drm-kmod'.
> >>
> >> On 6/10/19 5:26 AM, driesm.michi...@gmail.com wrote:
> >>> Hi stable mailing list!
> >>>
> >>>
> >>>
> >>> Today I tried updating my machine to r348848 from r347952. It didn't
> >>> go as smooth as I would've hoped (normally its just fine).
> >>>
> >>> After doing the upgrade using the standard upgrade from source
> >>> procedure I went ahead and booted my machine.
> >>>
> >>> During booting I got black screened (after the messages below) and
> >>> booting got stuck from there.
> >>>
> >>> *   Loading kernel modules:
> >>> *   Anon_inodefs_init:
> >>> *   Sysctl_warn_reuse: can't re-use a leaf (compat.linuxkpi.debug)!
> >>> *   Black screen and booting stops
> >>>
> >>>
> >>>
> >>> I went ahead and reverted to a ZFS snapshot preupdate so all is
> fine again.
> >>>
> >>> Any pointers as to where the regression might be? I did a clean build
> >>> to update.
> >>>
> >>>
> >>>
> >>> Regards,
> >>>
> >>> Dries
> >>>
> >>>
> >>>
> >>> ___
> >>> freebsd-stable@freebsd.org mailing list
> >>> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> >>> To unsubscribe, send any mail to "freebsd-stable-
> >> unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

[igb] wake on lan not working with Intel I210 for FreeBSD-12.0?

[Nikita Druba]

Hi to all!

After updating my server to 12.0-RELENG "wake on lan" function stopped 
working in my configuration. It was in April. I tried fresh kernel 
sources from 12.0-RELENG, but no result.

I have Intel I210 Gigabit Network Connection, driver igb.

rc.conf at server that I use for waking up:

ifconfig_igb0="-wol_ucast -wol_mcast wol_magic"

powered on at another server by:

wake igb0 11:22:33:44:55:66;

I tried to change sysctl by
dev.igb.0.wake=0 -> 1
but no result.

Its very important function for my backup scheme. Can anybody confirm 
this bug? May be I'm wrong, then what can I do to fix "wake up" 
function? Because all, that I found not working.


Thanx in advance.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238411
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Kernel panic on 12-STABLE-r348203 amd64

[Kubilay Kocak]

On 6/06/2019 5:04 am, Mark Saad wrote:

On Wed, Jun 5, 2019 at 2:42 PM Mark Saad  wrote:


On Wed, Jun 5, 2019 at 12:29 PM Mark Saad  wrote:


All
  I was wondering if anyone could shed some light on this boot panic I
saw yesterday. This is on a Dell R630 with Bios 2.9.1  booting
12.0-STABLE-r348203 amd64.
I reverted this back to 12.0-RELEASE-p4 and its fine .

The only custom options I had were in loader.conf

kern.geom.label.gptid.enable="0"
ipmi_load="YES"
boot_multicons="YES"
boot_serial="YES"
console="comconsole,vidconsole"
net.inet.tcp.tso="0"
cc_htcp_load="YES"
autoboot_delay="5"
hw.mfi.mrsas_enable="1"
hw.usb.no_pf="1"# Disable USB packet filtering
hw.usb.no_shutdown_wait="1"
hw.vga.textmode="1" # Text mode
machdep.hyperthreading_allowed="0"

Any ideas ?

Screen shot here
https://imgur.com/a/nGvHtIs

--
mark saad | nones...@longcount.org


Plain text version of the crash

Loading kernel...
/boot/kernel/kernel text=0x168d811 data=0x1cf968+0x768c80
syms=[0x8+0x1778e8+0x8   /
+0x194f1d]
Loading configured modules...
/boot/kernel/ipmi.ko size 0x11e10 at 0x2645000
loading required module 'smbus'
/boot/kernel/smbus.ko size 0x2ef0 at 0x2657000
/boot/entropy size=0x1000
/boot/kernel/cc_httcp.ko size 0x2330 at 0x265b000
---<>---c_hmodule 'smbus'
Copyright (c) 1992-2019 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
 The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 12.0-STABLE r348693 GENERIC amd64
FreeBSD clang version 8.0.0 (tags/RELEASE_800/final 356365) (based on
LLVM 8.0.0)
panic: UMA zone "UMA Zones": Increase vm.boot_pages
cpuid = 0
time = 1
KDB: stack backtrace:
#0 0x80c16df7 at ??+0
#1 0x80bcaccd at ??+0
#2 0x80bcab23 at ??+0
#3 0x80f0b03c at ??+0
#4 0x80f08d8d at ??+0
#5 0x80f0bb3d at ??+0
#6 0x80f0b301 at ??+0
#7 0x80f0b3d1 at ??+0
#8 0x80f066c4 at ??+0
#9 0x80f0543f at ??+0
#10 0x80f23aef at ??+0
#11 0x80f1133b at ??+0
#12 0x80b619c8 at ??+0
#13 0x8036a02c at ??+0
Uptime: 1s


Also increasing the vm.boot_pages to 128 in the loader works. Anyone
know why ? This box has 64G ram.

--
mark saad | nones...@longcount.org


So after some poking in the bios this has to do with how the Dell NUMA
options are set. If the system is set Cluster On Die mode, you get a
kernel panic
Home Snoop or Early Snoop no issue.




Hi Mark,

Could you report this bug (Bugzilla) if you haven't already, providing:

- exact freebsd version(s) reproducible with
- panic/backtrace output as an attachment. Ideally with a debug kernel
- /var/run/dmesg.boot output (as an attachment) in a verbose boot
- if you can test a current snapshot, that would be great
- any other system information you believe might be helpful in isolating 
root cause(s) or potential fixes


Thanks!
Feel free to CC me on it
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"