panic after starting X with r238120

[swills]

Hi,

After updating to r238120, I get a panic whenever X starts up. It works for a few seconds, then panics. The messages don't look too useful to me, but here they are:

Unread portion of the kernel message buffer:
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 3610 (kdm_greet)
trap number             = 12
panic: page fault
cpuid = 0

(kgdb) bt
#0  doadump (textdump=dwarf2_read_address: Corrupted DWARF expression.
) at pcpu.h:224
#1  0xffffffff8087ef79 in kern_reboot (howto=dwarf2_read_address: Corrupted DWARF expression.
) at kern_shutdown.c:449
#2  0xffffffff8087f413 in panic (fmt=dwarf2_read_address: Corrupted DWARF expression.
) at kern_shutdown.c:637
#3  0xffffffff80b77d08 in trap_fatal (frame=dwarf2_read_address: Corrupted DWARF expression.
) at trap.c:852
#4  0xffffffff80b78012 in trap_pfault (frame=dwarf2_read_address: Corrupted DWARF expression.
) at trap.c:678
#5  0xffffffff80b777aa in trap (frame=Variable "frame" is not available.
) at trap.c:456
#6  0xffffffff80b62142 in calltrap () at /tmp/exception-vH8hmc.s:179
#7  0xffffffff80b6f6b0 in pmap_enter (pmap=dwarf2_read_address: Corrupted DWARF expression.
) at pmap.c:3587
#8  0xffffffff80adafa0 in vm_fault_hold (map=dwarf2_read_address: Corrupted DWARF expression.
) at vm_fault.c:935
#9  0xffffffff80ad9787 in vm_fault (map=Variable "map" is not available.
) at vm_fault.c:229
#10 0xffffffff80b77f26 in trap_pfault (frame=dwarf2_read_address: Corrupted DWARF expression.
) at trap.c:736
#11 0xffffffff80b77670 in trap (frame=Variable "frame" is not available.
) at trap.c:358
#12 0xffffffff80b62142 in calltrap () at /tmp/exception-vH8hmc.s:179
#13 0x00000008040d7796 in ?? ()
Previous frame inner to this frame (corrupt stack?)
Current language:  auto; currently minimal
(kgdb)

Something I saw in a previous panic made me think this was drm related, but I don't see it in this particular one.

Steve

_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

[swills]

Setting kern.ipc.shm_use_phys back to 0 (the default) fixed it. I had set it to 1 for some reason that I can't recall.

Steve

On Jul 4, 2012, at 5:41 PM, Steve Wills wrote:

> Hi,
>
> After updating to r238120, I get a panic whenever X starts up. It works for a few seconds, then panics. The messages don't look too useful to me, but here they are:
>
> Unread portion of the kernel message buffer:
> processor eflags        = interrupt enabled, resume, IOPL = 0
> current process         = 3610 (kdm_greet)
> trap number             = 12
> panic: page fault
> cpuid = 0
>
> (kgdb) bt
> #0  doadump (textdump=dwarf2_read_address: Corrupted DWARF expression.
> ) at pcpu.h:224
> #1  0xffffffff8087ef79 in kern_reboot (howto=dwarf2_read_address: Corrupted DWARF expression.
> ) at kern_shutdown.c:449
> #2  0xffffffff8087f413 in panic (fmt=dwarf2_read_address: Corrupted DWARF expression.
> ) at kern_shutdown.c:637
> #3  0xffffffff80b77d08 in trap_fatal (frame=dwarf2_read_address: Corrupted DWARF expression.
> ) at trap.c:852
> #4  0xffffffff80b78012 in trap_pfault (frame=dwarf2_read_address: Corrupted DWARF expression.
> ) at trap.c:678
> #5  0xffffffff80b777aa in trap (frame=Variable "frame" is not available.
> ) at trap.c:456
> #6  0xffffffff80b62142 in calltrap () at /tmp/exception-vH8hmc.s:179
> #7  0xffffffff80b6f6b0 in pmap_enter (pmap=dwarf2_read_address: Corrupted DWARF expression.
> ) at pmap.c:3587
> #8  0xffffffff80adafa0 in vm_fault_hold (map=dwarf2_read_address: Corrupted DWARF expression.
> ) at vm_fault.c:935
> #9  0xffffffff80ad9787 in vm_fault (map=Variable "map" is not available.
> ) at vm_fault.c:229
> #10 0xffffffff80b77f26 in trap_pfault (frame=dwarf2_read_address: Corrupted DWARF expression.
> ) at trap.c:736
> #11 0xffffffff80b77670 in trap (frame=Variable "frame" is not available.
> ) at trap.c:358
> #12 0xffffffff80b62142 in calltrap () at /tmp/exception-vH8hmc.s:179
> #13 0x00000008040d7796 in ?? ()
> Previous frame inner to this frame (corrupt stack?)
> Current language:  auto; currently minimal
> (kgdb)
>
> Something I saw in a previous panic made me think this was drm related, but I don't see it in this particular one.
>
> Steve
>
> _______________________________________________
> [hidden email] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "[hidden email]"

_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

[Alan Cox-9]

On Wed, Jul 4, 2012 at 4:57 PM, Steve Wills <[hidden email]> wrote:

> Setting kern.ipc.shm_use_phys back to 0 (the default) fixed it. I had set
> it to 1 for some reason that I can't recall.
>
>
That shouldn't cause a crash in pmap_enter().  What is line 3587 of pmap.c
in your sources?  You mentioned DRM.  Are you using the new Intel graphics
driver?

Alan
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

[swills]

On 07/05/12 03:00, Alan Cox wrote:
> On Wed, Jul 4, 2012 at 4:57 PM, Steve Wills <[hidden email]> wrote:
>
>> Setting kern.ipc.shm_use_phys back to 0 (the default) fixed it. I had set
>> it to 1 for some reason that I can't recall.
>>
>>
> That shouldn't cause a crash in pmap_enter().  What is line 3587 of pmap.c
> in your sources?

3587                                 if ((newpte & PG_RW) == 0)

> You mentioned DRM.  Are you using the new Intel graphics
> driver?
>

No, I'm using ATI Radeon.

Steve
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

[Steve Wills-2]

Following up to myself, with some things I should have mentioned before:

On 07/05/12 19:59, Steve Wills wrote:

> On 07/05/12 03:00, Alan Cox wrote:
>> On Wed, Jul 4, 2012 at 4:57 PM, Steve Wills <[hidden email]> wrote:
>>
>>> Setting kern.ipc.shm_use_phys back to 0 (the default) fixed it. I had set
>>> it to 1 for some reason that I can't recall.
>>>
>>>
>> That shouldn't cause a crash in pmap_enter().  What is line 3587 of pmap.c
>> in your sources?
>
> 3587                                 if ((newpte & PG_RW) == 0)
>
>> You mentioned DRM.  Are you using the new Intel graphics
>> driver?
>>
>
> No, I'm using ATI Radeon.
>

For what it's worth, I discovered that twm and xterm don't trigger the
issue, but konsole and other kde things do, which is what led me to
discover that setting kern.ipc.shm_use_phys back to default fixed it.

This wasn't the case before, I think the last time I updated was about a
month ago, May 6.

Also, I have these other shared memory related settings in sysctl.conf:

kern.ipc.shmmax=67108864
kern.ipc.shmall=32768
kern.ipc.shm_allow_removed=1

I'm wondering if this is an indication that I have/had some bad settings
and they finally bit me, or if this is an indication of a bug.

Thanks,
Steve
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

[Jean-Sébastien Pédron]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08.07.2012 05:14, Steve Wills wrote:
> For what it's worth, I discovered that twm and xterm don't trigger
> the issue, but konsole and other kde things do, which is what led
> me to discover that setting kern.ipc.shm_use_phys back to default
> fixed it.

I encountered the same issue with x11-wm/awesome, but everything's ok
with twm. A kernel from 2012-06-23 doesn't crash but a kernel from
2012-07-03 does crash.

Here're the sysctls/tunables I have regarding shm:

In /boot/loader.conf:
kern.ipc.shmmni="1024"
kern.ipc.shmseg="1024"

In /etc/sysctl.conf:
kern.ipc.shmmax=2147483648
kern.ipc.shm_use_phys=1
kern.ipc.shm_allow_removed=1

- --
Jean-Sébastien Pédron

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/5QesACgkQa+xGJsFYOlPRwQCcClck3824nWltHoIVzuzmLBLz
dyUAoIhVeREUZH26QdcJkyyXfna9LYQQ
=mKU0
-----END PGP SIGNATURE-----
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

[Konstantin Belousov]

On Sun, Jul 08, 2012 at 10:16:44AM +0200, Jean-S?bastien P?dron wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 08.07.2012 05:14, Steve Wills wrote:
> > For what it's worth, I discovered that twm and xterm don't trigger
> > the issue, but konsole and other kde things do, which is what led
> > me to discover that setting kern.ipc.shm_use_phys back to default
> > fixed it.
>
> I encountered the same issue with x11-wm/awesome, but everything's ok
> with twm. A kernel from 2012-06-23 doesn't crash but a kernel from
> 2012-07-03 does crash.
>
> Here're the sysctls/tunables I have regarding shm:
>
> In /boot/loader.conf:
> kern.ipc.shmmni="1024"
> kern.ipc.shmseg="1024"
>
> In /etc/sysctl.conf:
> kern.ipc.shmmax=2147483648
> kern.ipc.shm_use_phys=1
> kern.ipc.shm_allow_removed=1
>

You know, this is not much useful ? Backtrace is.

[Alan Cox-9]

On Sun, Jul 8, 2012 at 3:16 AM, Jean-Sébastien Pédron
<[hidden email]>wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 08.07.2012 05:14, Steve Wills wrote:
> > For what it's worth, I discovered that twm and xterm don't trigger
> > the issue, but konsole and other kde things do, which is what led
> > me to discover that setting kern.ipc.shm_use_phys back to default
> > fixed it.
>
> I encountered the same issue with x11-wm/awesome, but everything's ok
> with twm. A kernel from 2012-06-23 doesn't crash but a kernel from
> 2012-07-03 does crash.
>
>

In r237513 on 6/23 I made a mistake that was corrected in r238124 on 7/5.
I can vaguely see a connection between kern.ipc.shm_use_phys and the
problem fixed in r238124.  So, I'd like to know if this problem still
exists.  Wait, however, until you see Kostik commit a change to
vm_pageout.c, before you update your system.


Here're the sysctls/tunables I have regarding shm:

>
> In /boot/loader.conf:
> kern.ipc.shmmni="1024"
> kern.ipc.shmseg="1024"
>
> In /etc/sysctl.conf:
> kern.ipc.shmmax=2147483648
> kern.ipc.shm_use_phys=1
> kern.ipc.shm_allow_removed=1
>
> - --
> Jean-Sébastien Pédron
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.19 (FreeBSD)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk/5QesACgkQa+xGJsFYOlPRwQCcClck3824nWltHoIVzuzmLBLz
> dyUAoIhVeREUZH26QdcJkyyXfna9LYQQ
> =mKU0
> -----END PGP SIGNATURE-----
> _______________________________________________
> [hidden email] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "[hidden email]"
>

_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

[swills]

On 07/08/12 13:56, Alan Cox wrote:
>
>
>> In r237513 on 6/23 I made a mistake that was corrected in r238124 on 7/5.
>> I can vaguely see a connection between kern.ipc.shm_use_phys and the
>> problem fixed in r238124.  So, I'd like to know if this problem still
>> exists.  Wait, however, until you see Kostik commit a change to
>> vm_pageout.c, before you update your system.
>
>

I booted r238261 with kern.ipc.shm_use_phys=1 and the problem seems to
have disappeared. Thanks!

Steve
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

[Jean-Sébastien Pédron]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08.07.2012 15:06, Konstantin Belousov wrote:
> You know, this is not much useful ? Backtrace is.

Sorry, I forgot to mention that I had the same backtrace than Steve.

I'll buildworld again (probably not today) and report back.

- --
Jean-Sébastien Pédron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/6kY4ACgkQa+xGJsFYOlMvHgCeNW76VSjVkf4/on2LYFKGR5Bs
R7UAoNYkQtmvpzlblqd3mudp57Kg2K22
=oIqg
-----END PGP SIGNATURE-----
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"