Re: ffs_truncate3 panics

[Rick Macklem]

Konstantin Belousov wrote:
[stuff snipped]
>> >Can you print the only buffer on the clean queue when the panic occur ?
>> ffst3 vtyp=1 bodirty=0 boclean=1
>> buf at 0x428a110
>> b_flags = 0x20001020, b_xflags=0x2, b_vflags=0x0
>> b_error = 0, b_bufsize = 4096, b_bcount = 4096, b_resid = 0
>> b_bufobj = (0xfd8ba94), b_data = 0x517, b_blkno = -1, b_lblkno = -1, 
>> b_dep = 0
>> b_kvabase = 0x517, b_kvasize = 32768
>So the buffer was indeed for extended attrs, and never written to the disk.
>I am quite interested what was the inode content prior to the truncation,
>esp. the di_extsize.
Just in case it wasn't clear, this buffer is on the clean list and not the 
dirty one.
(Does this mean it somehow got onto the "clean list" without being written to 
disk?)

>Could you try to formulate a way to reproduce the panic so that Peter
>can recreate it, please ?
I doubt it. It would require him doing a pNFS setup with multiple systems.
(At least that is the only way I reproduce it and I sometimes go a week of 
testing
 before I see them.)
It would be great to have more testers for the pNFS server stuff, but I doubt it
would fit into Peter's setup?

I can add printf()s anywhere you suggest, but I'm not sure how you would catch
this case sooner? (For example, I could print out di_extsize at the beginning of
ffs_truncate(), if that would help?)

rick
[more stuff snipped]
___
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: IPMI SOL seems to not accept characters after getty starts

[Warner Losh]

On Wed, Aug 8, 2018 at 6:03 PM, Allan Jude  wrote:

> On 2018-08-08 19:21, Sean Bruno wrote:
> >
> >
> > On 08/08/18 17:13, Warner Losh wrote:
> >>
> >>
> >> On Wed, Aug 8, 2018 at 4:39 PM, Sean Bruno  >> > wrote:
> >>
> >> tl;dr pxeboot new x86 host, ipmi sol works in loader, not after
> >> multiuser.
> >>
> >> The FreeBSD cluster just acquired 4x Supermicro X11DDW-L and I am
> having
> >> the hardest time with the IPMI SOL interface.
> >>
> >> I have configured "COM2" as the IPMI SOL interface and enabled
> console
> >> redirection.  Netbooting via pxeboot works well and the loader menu
> is
> >> interactive and responds.
> >>
> >> After NFS booting into freebsd (current or stable/11), getty fires
> up
> >> and attaches to ttyu0.  It prompts me correctly, but it does not
> accept
> >> my keystrokes.
> >>
> >> If I do not configure /etc/ttys to enable a tty unconditionally (on
> vs
> >> onifconsole), I see dmesg/kernel boot messages but never get a tty.
> >>
> >> Its as though FreeBSD does *not* recognize the IPMI SOL port as the
> >> console or something and I'm super confused.  Any thoughts here?
> >>
> >>
> >> Works fine for me.
> >>
> >> So, let's start with your /boot.config (or /boot/config) loader.conf and
> >> device,hints settings. Also BIOS or UEFI?
> >>
> >> Warner
> >>
> >
> > Works for you on this exact Supermicro?
> >
> > I am using the defaults all around.  This is booting BIOS mode PXE, all
> > console output appears on the IPMI SOL interface.  Driving the beastie
> > menu in pxeboot/loader works fine.  When the loader hands the uart off
> > to the kernel, I see all boot output and "everything is fine"
> >
> > The problem arises when trying to login.  I see the amnesiac login
> > prompt, but no key strokes are registered.
> >
> > loader.conf:
> > console="comconsole"
> > comconsole_speed="115200"
> >
> > boot.config:
> > 
> >
> > sean
> >
> >
>
> If it is COM2, don't you also need:
> comconsole_port="0x2f8"
>
> And possibly device.hints:
> hint.uart.1.flags="0x10"
>
> to mark it as a serial console?
>

What does the amnesiac login message say is the tty?

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: IPMI SOL seems to not accept characters after getty starts

[Allan Jude]

On 2018-08-08 19:21, Sean Bruno wrote:
> 
> 
> On 08/08/18 17:13, Warner Losh wrote:
>>
>>
>> On Wed, Aug 8, 2018 at 4:39 PM, Sean Bruno > > wrote:
>>
>> tl;dr pxeboot new x86 host, ipmi sol works in loader, not after
>> multiuser.
>>
>> The FreeBSD cluster just acquired 4x Supermicro X11DDW-L and I am having
>> the hardest time with the IPMI SOL interface.
>>
>> I have configured "COM2" as the IPMI SOL interface and enabled console
>> redirection.  Netbooting via pxeboot works well and the loader menu is
>> interactive and responds.
>>
>> After NFS booting into freebsd (current or stable/11), getty fires up
>> and attaches to ttyu0.  It prompts me correctly, but it does not accept
>> my keystrokes.
>>
>> If I do not configure /etc/ttys to enable a tty unconditionally (on vs
>> onifconsole), I see dmesg/kernel boot messages but never get a tty.
>>
>> Its as though FreeBSD does *not* recognize the IPMI SOL port as the
>> console or something and I'm super confused.  Any thoughts here?
>>
>>
>> Works fine for me.
>>
>> So, let's start with your /boot.config (or /boot/config) loader.conf and
>> device,hints settings. Also BIOS or UEFI?
>>
>> Warner
>>  
> 
> Works for you on this exact Supermicro?
> 
> I am using the defaults all around.  This is booting BIOS mode PXE, all
> console output appears on the IPMI SOL interface.  Driving the beastie
> menu in pxeboot/loader works fine.  When the loader hands the uart off
> to the kernel, I see all boot output and "everything is fine"
> 
> The problem arises when trying to login.  I see the amnesiac login
> prompt, but no key strokes are registered.
> 
> loader.conf:
> console="comconsole"
> comconsole_speed="115200"
> 
> boot.config:
> 
> 
> sean
> 
> 

If it is COM2, don't you also need:
comconsole_port="0x2f8"

And possibly device.hints:
hint.uart.1.flags="0x10"

to mark it as a serial console?

-- 
Allan Jude



signature.asc
Description: OpenPGP digital signature

Re: programs like gdb core dump

[Erich Dollansky]

Hi,

here we are:

http://sumeritec/FreeBSD/fortune.core
http://sumeritec/FreeBSD/gdb.core

The fortune core is from the same source as the now running system. The
gdb core should be but I am not 100% sure.

Revision: Revision: 337343

Erich


On Wed, 8 Aug 2018 08:57:06 -0700
John Baldwin  wrote:

> On 8/7/18 7:00 PM, Erich Dollansky wrote:
> > Hi,
> > 
> > On Tue, 7 Aug 2018 11:59:11 -0700
> > John Baldwin  wrote:
> >   
> >> On 8/6/18 8:11 PM, Erich Dollansky wrote:  
> >>> On Mon, 6 Aug 2018 15:57:53 -0700
> >>> John Baldwin  wrote:
> >>> 
>  On 8/4/18 4:38 PM, Erich Dollansky wrote:
> >   
> > Bad system call (core dumped)  
> 
>  Did you upgrade from stable/11 with a world that is still
>  stable/11? If so, did you make sure your kernel config includes
>  COMPAT_FREEBSD11? (GENERIC should include this)
> 
> >>>
> >>> I never have had a machine running 11. This machine is on 12 since
> >>> 2 or 3 years. I will check if this configuration was properly set
> >>> on that machine.
> >>
> >> Ahh, a fairly old 12 world with a recent 12 kernel will still need
> >> COMPAT_FREEBSD11.
> >>  
> > 
> > even when kernel and world are on '1200076' as provided by uname
> > -U/-K, COMPAT_FREEBSD11 is required at the moment. The system is
> > currently on r337343.  
> 
> Hmm, plain 12.0 binaries that are up to date should not need
> COMPAT_FREEBSD11. Do you have any of the core dumps from before handy?
> 

___
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: IPMI SOL seems to not accept characters after getty starts

[Warner Losh]

On Wed, Aug 8, 2018 at 5:21 PM, Sean Bruno  wrote:

>
>
> On 08/08/18 17:13, Warner Losh wrote:
> >
> >
> > On Wed, Aug 8, 2018 at 4:39 PM, Sean Bruno  > > wrote:
> >
> > tl;dr pxeboot new x86 host, ipmi sol works in loader, not after
> > multiuser.
> >
> > The FreeBSD cluster just acquired 4x Supermicro X11DDW-L and I am
> having
> > the hardest time with the IPMI SOL interface.
> >
> > I have configured "COM2" as the IPMI SOL interface and enabled
> console
> > redirection.  Netbooting via pxeboot works well and the loader menu
> is
> > interactive and responds.
> >
> > After NFS booting into freebsd (current or stable/11), getty fires up
> > and attaches to ttyu0.  It prompts me correctly, but it does not
> accept
> > my keystrokes.
> >
> > If I do not configure /etc/ttys to enable a tty unconditionally (on
> vs
> > onifconsole), I see dmesg/kernel boot messages but never get a tty.
> >
> > Its as though FreeBSD does *not* recognize the IPMI SOL port as the
> > console or something and I'm super confused.  Any thoughts here?
> >
> >
> > Works fine for me.
> >
> > So, let's start with your /boot.config (or /boot/config) loader.conf and
> > device,hints settings. Also BIOS or UEFI?
> >
> > Warner
> >
>
> Works for you on this exact Supermicro?
>
> I am using the defaults all around.  This is booting BIOS mode PXE, all
> console output appears on the IPMI SOL interface.  Driving the beastie
> menu in pxeboot/loader works fine.  When the loader hands the uart off
> to the kernel, I see all boot output and "everything is fine"
>
> The problem arises when trying to login.  I see the amnesiac login
> prompt, but no key strokes are registered.
>

OK. That's super weird. Interrupt configuration issue?


> loader.conf:
> console="comconsole"
> comconsole_speed="115200"
>
> boot.config:
> 
>

x11 supermicro, though not that exact one.

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: IPMI SOL seems to not accept characters after getty starts

[Sean Bruno]

On 08/08/18 17:13, Warner Losh wrote:
> 
> 
> On Wed, Aug 8, 2018 at 4:39 PM, Sean Bruno  > wrote:
> 
> tl;dr pxeboot new x86 host, ipmi sol works in loader, not after
> multiuser.
> 
> The FreeBSD cluster just acquired 4x Supermicro X11DDW-L and I am having
> the hardest time with the IPMI SOL interface.
> 
> I have configured "COM2" as the IPMI SOL interface and enabled console
> redirection.  Netbooting via pxeboot works well and the loader menu is
> interactive and responds.
> 
> After NFS booting into freebsd (current or stable/11), getty fires up
> and attaches to ttyu0.  It prompts me correctly, but it does not accept
> my keystrokes.
> 
> If I do not configure /etc/ttys to enable a tty unconditionally (on vs
> onifconsole), I see dmesg/kernel boot messages but never get a tty.
> 
> Its as though FreeBSD does *not* recognize the IPMI SOL port as the
> console or something and I'm super confused.  Any thoughts here?
> 
> 
> Works fine for me.
> 
> So, let's start with your /boot.config (or /boot/config) loader.conf and
> device,hints settings. Also BIOS or UEFI?
> 
> Warner
>  

Works for you on this exact Supermicro?

I am using the defaults all around.  This is booting BIOS mode PXE, all
console output appears on the IPMI SOL interface.  Driving the beastie
menu in pxeboot/loader works fine.  When the loader hands the uart off
to the kernel, I see all boot output and "everything is fine"

The problem arises when trying to login.  I see the amnesiac login
prompt, but no key strokes are registered.

loader.conf:
console="comconsole"
comconsole_speed="115200"

boot.config:


sean




signature.asc
Description: OpenPGP digital signature

Re: IPMI SOL seems to not accept characters after getty starts

[Warner Losh]

On Wed, Aug 8, 2018 at 4:39 PM, Sean Bruno  wrote:

> tl;dr pxeboot new x86 host, ipmi sol works in loader, not after multiuser.
>
> The FreeBSD cluster just acquired 4x Supermicro X11DDW-L and I am having
> the hardest time with the IPMI SOL interface.
>
> I have configured "COM2" as the IPMI SOL interface and enabled console
> redirection.  Netbooting via pxeboot works well and the loader menu is
> interactive and responds.
>
> After NFS booting into freebsd (current or stable/11), getty fires up
> and attaches to ttyu0.  It prompts me correctly, but it does not accept
> my keystrokes.
>
> If I do not configure /etc/ttys to enable a tty unconditionally (on vs
> onifconsole), I see dmesg/kernel boot messages but never get a tty.
>
> Its as though FreeBSD does *not* recognize the IPMI SOL port as the
> console or something and I'm super confused.  Any thoughts here?
>

Works fine for me.

So, let's start with your /boot.config (or /boot/config) loader.conf and
device,hints settings. Also BIOS or UEFI?

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"

IPMI SOL seems to not accept characters after getty starts

[Sean Bruno]

tl;dr pxeboot new x86 host, ipmi sol works in loader, not after multiuser.

The FreeBSD cluster just acquired 4x Supermicro X11DDW-L and I am having
the hardest time with the IPMI SOL interface.

I have configured "COM2" as the IPMI SOL interface and enabled console
redirection.  Netbooting via pxeboot works well and the loader menu is
interactive and responds.

After NFS booting into freebsd (current or stable/11), getty fires up
and attaches to ttyu0.  It prompts me correctly, but it does not accept
my keystrokes.

If I do not configure /etc/ttys to enable a tty unconditionally (on vs
onifconsole), I see dmesg/kernel boot messages but never get a tty.

Its as though FreeBSD does *not* recognize the IPMI SOL port as the
console or something and I'm super confused.  Any thoughts here?

sean



signature.asc
Description: OpenPGP digital signature

Re: ffs_truncate3 panics

[Konstantin Belousov]

On Wed, Aug 08, 2018 at 12:30:54PM +, Rick Macklem wrote:
> Konstantin Belousov wrote:
> >On Tue, Aug 07, 2018 at 12:28:33PM +, Rick Macklem wrote:
> >> Hi,
> >>
> >> During testing of the pNFS server I get an ffs_truncate3 panic every once 
> >> in a while.
> >> A few things that might be relevant:
> >> - Seems to happen more often when soft update journaling is enabled, but 
> >> will
> >>   happen when it is disabled.
> >> - Normally happens when a fairly large subtree of the file system is being 
> >> removed.
> - Oh, and this is an old i386 with 256Mbytes (not one of them new fangled 
> computers,
>where memory is in Gbytes;-)
> 
> >>
> >> These file systems are a bit odd, since all the regular files in them are 
> >> empty but
> >> have extended attributes that are accessed during the subtree removal. (The
> >> extended attributes tell the server where the data files are.)
> >>
> >> I replaced the panic() with a printf() and every time the printf() 
> >> happens...
> >> bo->bo_dirty.bv_cnt == 0 and bo->bo_clean.bv_cnt == 1.
> >> After one of these printf()s, the system continues to run ok. When the file
> >> system is fsck'd after this has occurred, it passes fine and I haven't 
> >> seen and
> >> indication of file system corruption after running with this file system 
> >> for
> >> quite a while after the printf()s first occurred.
> >The lack of corruption is, most likely, because the files are removed.
> >Would the files truncated to zero length and then extended, I am almost
> >sure that a corruption occur.
> >
> >Can you print the only buffer on the clean queue when the panic occur ?
> ffst3 vtyp=1 bodirty=0 boclean=1
> buf at 0x428a110
> b_flags = 0x20001020, b_xflags=0x2, b_vflags=0x0
> b_error = 0, b_bufsize = 4096, b_bcount = 4096, b_resid = 0
> b_bufobj = (0xfd8ba94), b_data = 0x517, b_blkno = -1, b_lblkno = -1, 
> b_dep = 0
> b_kvabase = 0x517, b_kvasize = 32768
So the buffer was indeed for extended attrs, and never written to the disk.
I am quite interested what was the inode content prior to the truncation,
esp. the di_extsize.

Could you try to formulate a way to reproduce the panic so that Peter
can recreate it, please ?

> 
> >Also, it is interesting to know the initial length of the file.
> Since they are regular files, they are 0 length. (Just inodes with extended 
> attributes.)
> 
> >>
> >> Since the panic() only occurs when "options INVARIANTS" is enabled and I 
> >> don't
> >> see evidence of file system corruption, I'm wondering if this panic() is 
> >> valid and
> >> needed?
> 
> rick
___
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: Vbox causing host crash/reboot on 12-current

[Danilo Egêa Gondolfo]

On Wed, Aug 8, 2018 at 5:25 PM Vladimir Kondratyev 
wrote:

> Hi
>
> I am sure that crashes was caused by SMAP as I am faced with them too.
> I have made following patch to fix panic (attached)
> Apply it to portstree and rebuild emulators/virtualbox-ose-kmod
>
> P.S. It is POC so no arch/SMAP autodetection
>
> On 8/7/18 6:14 PM, AN wrote:
> > Update:
> >
> > I found the revision:
> > https://svnweb.freebsd.org/base?view=revision&revision=336876
> >
> > Use SMAP on amd64.
> >
> > Could this possibly cause VBox to crash and reboot the system?  Is
> > there a sysctl to disable?
> >
> > Thanks
> >
> > On Tue, Aug 7, 2018 at 10:46 AM, AN  wrote:
> >> I recently started having severe instability on a workstation with
> >> VirtualBox.  I'm not sure if it was caused by the recent large ports
> >> update, or a recent commit that affected SMAP.  I can't seem to find
> >> that revision, would someone please post it and also the workaround to
> >> disable it, I would like to try it after work and see if disabling it
> >> allows VBox to work.  Is anyone else seeing this effect with Vbox?
> >>
> >> What I'm seeing is that as soon as a VM is started it reboots the
> >> host, totally reproducible every time.  I tried to rebuild VBox and
> >> kmod, and also some qt5 ports but still not working.  Any help is
> >> appreciated, thanks for reading.
> >>
> >> Regards
> > ___
> > 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"
>


Same problem here, but I'm getting two different panics:

Fatal trap 12: page fault while in kernel mode
cpuid = 3; apic id = 03
fault virtual address   = 0x28
fault code  = supervisor read data, page not present
instruction pointer = 0x20:0x80c7e806
stack pointer   = 0x28:0xfe009ced64c0
frame pointer   = 0x28:0xfe009ced64f0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 42332 (VBoxNetAdpCtl)

and

Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 02
fault virtual address   = 0x804209ab8
fault code  = supervisor read data, protection violation
instruction pointer = 0x20:0x835cc164
stack pointer   = 0x28:0xfe00b33031f0
frame pointer   = 0x28:0xfe00b33031f0
code segment= base r
x0, limit 0xf, type
0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0

current process = 21985 (VBoxHeadless)
___
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: Vbox causing host crash/reboot on 12-current

[Vladimir Kondratyev]

Hi

I am sure that crashes was caused by SMAP as I am faced with them too.
I have made following patch to fix panic (attached)
Apply it to portstree and rebuild emulators/virtualbox-ose-kmod

P.S. It is POC so no arch/SMAP autodetection

On 8/7/18 6:14 PM, AN wrote:
> Update:
>
> I found the revision:
> https://svnweb.freebsd.org/base?view=revision&revision=336876
>
> Use SMAP on amd64.
>
> Could this possibly cause VBox to crash and reboot the system?  Is
> there a sysctl to disable?
>
> Thanks
>
> On Tue, Aug 7, 2018 at 10:46 AM, AN  wrote:
>> I recently started having severe instability on a workstation with
>> VirtualBox.  I'm not sure if it was caused by the recent large ports
>> update, or a recent commit that affected SMAP.  I can't seem to find
>> that revision, would someone please post it and also the workaround to
>> disable it, I would like to try it after work and see if disabling it
>> allows VBox to work.  Is anyone else seeing this effect with Vbox?
>>
>> What I'm seeing is that as soon as a VM is started it reboots the
>> host, totally reproducible every time.  I tried to rebuild VBox and
>> kmod, and also some qt5 ports but still not working.  Any help is
>> appreciated, thanks for reading.
>>
>> Regards
> ___
> 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"


Index: emulators/virtualbox-ose/files/patch-smap
===
--- emulators/virtualbox-ose/files/patch-smap	(nonexistent)
+++ emulators/virtualbox-ose/files/patch-smap	(working copy)
@@ -0,0 +1,36 @@
+--- src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c.orig	2018-08-08 22:32:59.741196000 +0300
 src/VBox/HostDrivers/Support/freebsd/SUPDrv-freebsd.c	2018-08-08 22:52:49.842726000 +0300
+@@ -44,6 +44,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ 
+ #include "../SUPDrvInternal.h"
+ #include 
+@@ -310,6 +311,9 @@ static int VBoxDrvFreeBSDIOCtl(struct cd
+ {
+ PSUPDRVSESSION pSession;
+ devfs_get_cdevpriv((void **)&pSession);
++int rc;
++
++stac();
+ 
+ /*
+  * Deal with the fast ioctl path first.
+@@ -318,9 +322,13 @@ static int VBoxDrvFreeBSDIOCtl(struct cd
+ || ulCmd == SUP_IOCTL_FAST_DO_HM_RUN
+ || ulCmd == SUP_IOCTL_FAST_DO_NOP)
+ && pSession->fUnrestricted == true)
+-return supdrvIOCtlFast(ulCmd, *(uint32_t *)pvData, &g_VBoxDrvFreeBSDDevExt, pSession);
++rc = supdrvIOCtlFast(ulCmd, *(uint32_t *)pvData, &g_VBoxDrvFreeBSDDevExt, pSession);
++else
++rc = VBoxDrvFreeBSDIOCtlSlow(pSession, ulCmd, pvData, pTd);
+ 
+-return VBoxDrvFreeBSDIOCtlSlow(pSession, ulCmd, pvData, pTd);
++clac();
++
++return rc;
+ }
+ 
+ 

Property changes on: emulators/virtualbox-ose/files/patch-smap
___
Added: fbsd:nokeywords
## -0,0 +1 ##
+yes
\ No newline at end of property
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+text/plain
\ No newline at end of property
___
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: kldref: unhandled relocation type 2

[Steve Kargl]

On Wed, Aug 08, 2018 at 06:27:21PM +0100, Warner Losh wrote:
> On Wed, Aug 8, 2018 at 6:19 PM, Steve Kargl <
> s...@troutmask.apl.washington.edu> wrote:
> >
> > Thanks for info.
> >
> > I'll note that freshly built kldxref gives the same messages.
> >
> > % /usr/obj/usr/src/i386.i386/usr.sbin/kldxref/kldxref /boot/kernel
> > kldxref: unhandled relocation type 2
> > (40+ messages...)
> >
> 
> Oh, wait: relocation type, not module info That's not me, that's ed and
> the new linker I think, or Dimitry and the new clang...
> 

Too late.  Already rebooted with new kernel. :-)

It would be nice if the warning included the name of
the symbol/module that is causing the problem.  I guess
I'll peak at kldxref sources.

-- 
Steve
___
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: kldref: unhandled relocation type 2

[Warner Losh]

On Wed, Aug 8, 2018 at 6:19 PM, Steve Kargl <
s...@troutmask.apl.washington.edu> wrote:

> On Wed, Aug 08, 2018 at 06:14:19PM +0100, Warner Losh wrote:
> > On Wed, Aug 8, 2018 at 5:58 PM, Steve Kargl <
> > s...@troutmask.apl.washington.edu> wrote:
> >
> > > Just build a new world and kernel.  Upon doing "make installkernel",
> > > I see at the end of the process
> > >
> > > kldxref /boot/kernel
> > > kldxref: unhandled relocation type 2
> > > kldxref: unhandled relocation type 2
> > > kldxref: unhandled relocation type 2
> > > (40 more messages)
> > > kldxref: unhandled relocation type 2
> > >
> > > The currently running kernel (as I don't want to reboot
> > > if the above messages signal a problem) is
> > >
>
> (snip for brevity)
>
> >
> > Yes. You need a new kldxref installed.
> >
>
> Thanks for info.
>
> I'll note that freshly built kldxref gives the same messages.
>
> % /usr/obj/usr/src/i386.i386/usr.sbin/kldxref/kldxref /boot/kernel
> kldxref: unhandled relocation type 2
> (40+ messages...)
>

Oh, wait: relocation type, not module info That's not me, that's ed and
the new linker I think, or Dimitry and the new clang...

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: kldref: unhandled relocation type 2

[Steve Kargl]

On Wed, Aug 08, 2018 at 06:14:19PM +0100, Warner Losh wrote:
> On Wed, Aug 8, 2018 at 5:58 PM, Steve Kargl <
> s...@troutmask.apl.washington.edu> wrote:
> 
> > Just build a new world and kernel.  Upon doing "make installkernel",
> > I see at the end of the process
> >
> > kldxref /boot/kernel
> > kldxref: unhandled relocation type 2
> > kldxref: unhandled relocation type 2
> > kldxref: unhandled relocation type 2
> > (40 more messages)
> > kldxref: unhandled relocation type 2
> >
> > The currently running kernel (as I don't want to reboot
> > if the above messages signal a problem) is
> >

(snip for brevity)

> 
> Yes. You need a new kldxref installed.
> 

Thanks for info.

I'll note that freshly built kldxref gives the same messages.

% /usr/obj/usr/src/i386.i386/usr.sbin/kldxref/kldxref /boot/kernel
kldxref: unhandled relocation type 2
(40+ messages...)

-- 
Steve
___
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: kldref: unhandled relocation type 2

[Warner Losh]

On Wed, Aug 8, 2018 at 5:58 PM, Steve Kargl <
s...@troutmask.apl.washington.edu> wrote:

> Just build a new world and kernel.  Upon doing "make installkernel",
> I see at the end of the process
>
> kldxref /boot/kernel
> kldxref: unhandled relocation type 2
> kldxref: unhandled relocation type 2
> kldxref: unhandled relocation type 2
> (40 more messages)
> kldxref: unhandled relocation type 2
>
> The currently running kernel (as I don't want to reboot
> if the above messages signal a problem) is
>
> % uname -a
> FreeBSD mobile 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r334872: \
> Sat Jun 16 12:48:50 PDT 2018 src/i386.i386/sys/GENERIC  i386
>
> My sources are from yesterday.
>
> % svn info /usr/src | more
> Path: .
> Working Copy Root Path: /usr/src
> URL: svn://svn.freebsd.org/base/head
> Relative URL: ^/head
> Repository Root: svn://svn.freebsd.org/base
> Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
> Revision: 337442
> Node Kind: directory
> Schedule: normal
> Last Changed Author: eadler
> Last Changed Rev: 337442
> Last Changed Date: 2018-08-07 18:33:36 -0700 (Tue, 07 Aug 2018)
>
>
> So, is the above message benign?


Yes. You need a new kldxref installed.

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"

kldref: unhandled relocation type 2

[Steve Kargl]

Just build a new world and kernel.  Upon doing "make installkernel",
I see at the end of the process

kldxref /boot/kernel
kldxref: unhandled relocation type 2
kldxref: unhandled relocation type 2
kldxref: unhandled relocation type 2
(40 more messages)
kldxref: unhandled relocation type 2

The currently running kernel (as I don't want to reboot
if the above messages signal a problem) is

% uname -a
FreeBSD mobile 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r334872: \
Sat Jun 16 12:48:50 PDT 2018 src/i386.i386/sys/GENERIC  i386

My sources are from yesterday.

% svn info /usr/src | more
Path: .
Working Copy Root Path: /usr/src
URL: svn://svn.freebsd.org/base/head
Relative URL: ^/head
Repository Root: svn://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 337442
Node Kind: directory
Schedule: normal
Last Changed Author: eadler
Last Changed Rev: 337442
Last Changed Date: 2018-08-07 18:33:36 -0700 (Tue, 07 Aug 2018)


So, is the above message benign?

-- 
Steve
___
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: programs like gdb core dump

[John Baldwin]

On 8/7/18 7:00 PM, Erich Dollansky wrote:
> Hi,
> 
> On Tue, 7 Aug 2018 11:59:11 -0700
> John Baldwin  wrote:
> 
>> On 8/6/18 8:11 PM, Erich Dollansky wrote:
>>> On Mon, 6 Aug 2018 15:57:53 -0700
>>> John Baldwin  wrote:
>>>   
 On 8/4/18 4:38 PM, Erich Dollansky wrote:  
> 
> Bad system call (core dumped)

 Did you upgrade from stable/11 with a world that is still
 stable/11? If so, did you make sure your kernel config includes
 COMPAT_FREEBSD11? (GENERIC should include this)
  
>>>
>>> I never have had a machine running 11. This machine is on 12 since
>>> 2 or 3 years. I will check if this configuration was properly set
>>> on that machine.  
>>
>> Ahh, a fairly old 12 world with a recent 12 kernel will still need
>> COMPAT_FREEBSD11.
>>
> 
> even when kernel and world are on '1200076' as provided by uname -U/-K,
> COMPAT_FREEBSD11 is required at the moment. The system is currently on
> r337343.

Hmm, plain 12.0 binaries that are up to date should not need COMPAT_FREEBSD11.
Do you have any of the core dumps from before handy?

-- 
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: ffs_truncate3 panics

[Conrad Meyer]

On Wed, Aug 8, 2018 at 5:30 AM, Rick Macklem  wrote:
> - Oh, and this is an old i386 with 256Mbytes (not one of them new fangled 
> computers,
>where memory is in Gbytes;-)

Have you run memtest86+ recently?

Best,
Conrad
___
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: ffs_truncate3 panics

[Rick Macklem]

Konstantin Belousov wrote:
>On Tue, Aug 07, 2018 at 12:28:33PM +, Rick Macklem wrote:
>> Hi,
>>
>> During testing of the pNFS server I get an ffs_truncate3 panic every once in 
>> a while.
>> A few things that might be relevant:
>> - Seems to happen more often when soft update journaling is enabled, but will
>>   happen when it is disabled.
>> - Normally happens when a fairly large subtree of the file system is being 
>> removed.
- Oh, and this is an old i386 with 256Mbytes (not one of them new fangled 
computers,
   where memory is in Gbytes;-)

>>
>> These file systems are a bit odd, since all the regular files in them are 
>> empty but
>> have extended attributes that are accessed during the subtree removal. (The
>> extended attributes tell the server where the data files are.)
>>
>> I replaced the panic() with a printf() and every time the printf() happens...
>> bo->bo_dirty.bv_cnt == 0 and bo->bo_clean.bv_cnt == 1.
>> After one of these printf()s, the system continues to run ok. When the file
>> system is fsck'd after this has occurred, it passes fine and I haven't seen 
>> and
>> indication of file system corruption after running with this file system for
>> quite a while after the printf()s first occurred.
>The lack of corruption is, most likely, because the files are removed.
>Would the files truncated to zero length and then extended, I am almost
>sure that a corruption occur.
>
>Can you print the only buffer on the clean queue when the panic occur ?
ffst3 vtyp=1 bodirty=0 boclean=1
buf at 0x428a110
b_flags = 0x20001020, b_xflags=0x2, b_vflags=0x0
b_error = 0, b_bufsize = 4096, b_bcount = 4096, b_resid = 0
b_bufobj = (0xfd8ba94), b_data = 0x517, b_blkno = -1, b_lblkno = -1, b_dep 
= 0
b_kvabase = 0x517, b_kvasize = 32768

>Also, it is interesting to know the initial length of the file.
Since they are regular files, they are 0 length. (Just inodes with extended 
attributes.)

>>
>> Since the panic() only occurs when "options INVARIANTS" is enabled and I 
>> don't
>> see evidence of file system corruption, I'm wondering if this panic() is 
>> valid and
>> needed?

rick
___
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: panic after ifioctl/if_clone_destroy

[Hans Petter Selasky]

On 08/06/18 21:43, Matthew Macy wrote:

The struct thread is typesafe. The problem is that the link is no longer
typesafe now that it’s not part of the thread. Thanks for pointing this
out. I’ll commit a fix later today.



Is there a patch yet?

--HPS

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