-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
-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
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
On Sun, Jul 8, 2012 at 3:16 AM, Jean-Sébastien Pédron
dumbb...@freebsd.orgwrote:
-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
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
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 swi...@freebsd.org wrote:
Setting kern.ipc.shm_use_phys back to 0 (the default) fixed it. I had set
it
On Wed, Jul 4, 2012 at 4:57 PM, Steve Wills swi...@freebsd.org 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
On 07/05/12 03:00, Alan Cox wrote:
On Wed, Jul 4, 2012 at 4:57 PM, Steve Wills swi...@freebsd.org 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
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
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
10 matches
Mail list logo
