On Sun, 5 Mar 2017 04:10:26 -0800 David Wolfskill wrote
> On Sat, Mar 04, 2017 at 10:08:45PM -0800, Chris H wrote:
> > Thanks for the reply.
> > I rebooted to kernel.old, so I could get the exact
> > src revision I built this on. It's r314640
> >
> > Any news as to whether it's safe to update sr
On Sat, Mar 04, 2017 at 10:08:45PM -0800, Chris H wrote:
> Thanks for the reply.
> I rebooted to kernel.old, so I could get the exact
> src revision I built this on. It's r314640
>
> Any news as to whether it's safe to update src, and
> build a usable kernel?
>
I (try to -- and usually succe
On Sun, 5 Mar 2017 09:50:49 AM Andriy Gapon wrote:
> On 05/03/2017 08:08, Chris H wrote:
> > Thanks for the reply.
> > I rebooted to kernel.old, so I could get the exact
> > src revision I built this on. It's r314640
> >
> > Any news as to whether it's safe to update src, and
> > build a usable ke
>>
> >> On Sat, 4 Mar 2017 07:38:55 PM Chris H wrote:
> >>
> >> [remove 12-CURRENT history & hardware summary]
> >>
> >>> I finished the
> >>> buildworld, and finished the build/install kernel, and
> >>> (attempted) to boot
rld, and finished the build/install kernel, and
>>> (attempted) to boot to single user. But got a trap
>>> shortly into booting the new kernel;
>>>
>>> kernel trap 12 with interrupts disabled
>>>
>>> Fatal trap 12: page fault in kern
On Sat, 4 Mar 2017 10:34:39 PM Chris H wrote:
> On Sun, 05 Mar 2017 14:26:31 +0800 Alastair Hogge wrote
>
> > On Sat, 4 Mar 2017 10:08:45 PM Chris H wrote:
> > > Thanks for the reply.
> > > I rebooted to kernel.old, so I could get the exact
> > > src revision I built this on. It's r314640
> > >
On Sun, 05 Mar 2017 14:26:31 +0800 Alastair Hogge wrote
> On Sat, 4 Mar 2017 10:08:45 PM Chris H wrote:
> > Thanks for the reply.
> > I rebooted to kernel.old, so I could get the exact
> > src revision I built this on. It's r314640
> >
> > Any news as to whether it's safe to update src, and
> >
On Sat, 4 Mar 2017 10:08:45 PM Chris H wrote:
> Thanks for the reply.
> I rebooted to kernel.old, so I could get the exact
> src revision I built this on. It's r314640
>
> Any news as to whether it's safe to update src, and
> build a usable kernel?
I am not able to boot a kernel > r314627. I cur
; Core HW ID = 0
> CPU0 (BSP): APIC ID: 0
> Core HW ID = 1
> CPU1 (AP): APIC ID: 1
> Core HW ID = 2
> CPU2 (AP): APIC ID: 2
> Core HW ID = 3
> CPU3 (AP): APIC
Hi *,
On Sat, 4 Mar 2017 07:38:55 PM Chris H wrote:
[remove 12-CURRENT history & hardware summary]
> I finished the
> buildworld, and finished the build/install kernel, and
> (attempted) to boot to single user. But got a trap
> shortly into booting the new kernel;
>
&g
out a fresh copy
of src && ports, last night (PST) to begin a fresh
buildworld/kernel installworld/kernel. I finished the
buildworld, and finished the build/install kernel, and
(attempted) to boot to single user. But got a trap
shortly into booting the new kernel;
kernel trap 12 with interr
d headed in to work.
When I reconnected after getting in to work, I saw that the $SUBJECT
panic had occurred (cut/paste from serial console):
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0xe5
fault code
On 9 Nov, I wrote:
> I just got one of these shortly after I rebooted my November 7th
> -CURRENT box. DDB doesn't show much interesting.
>
> kernel trap 12 with interrupts disabled
>
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 0; apic id
I just got one of these shortly after I rebooted my November 7th
-CURRENT box. DDB doesn't show much interesting.
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0xbc04d753
fault
>Date: Mon, 8 Jul 2002 16:44:20 -0700 (PDT)
>From: David Wolfskill <[EMAIL PROTECTED]>
>OK; implementing rev. 1.12 of src/sys/vm/vm_zeroidle.c allowed me to
>boot my (SMP) build machine & login:
>freebeast(5.0-C)[1] uname -a
>FreeBSD freebeast.catwhisker.org 5.0-CURRENT FreeBSD 5.0-CURRENT #9: M
OK; implementing rev. 1.12 of src/sys/vm/vm_zeroidle.c allowed me to
boot my (SMP) build machine & login:
freebeast(5.0-C)[1] uname -a
FreeBSD freebeast.catwhisker.org 5.0-CURRENT FreeBSD 5.0-CURRENT #9: Mon Jul 8
16:28:30 PDT 2002
[EMAIL PROTECTED]:/common/S4/obj/usr/src/sys/FREEBEAST i3
CVSup started at 0347 hrs. Pacfic Daylight (7 hrs. west of GMT/UTC)
from cvsup14.freebsd.org. Build/install/mergemaster was uneventful.
Reboot after mergemaster proceeded as if nothing strange was about
to happen, then (cut/pasted from serial console):
...
SMP: enabled INTs: 2, 3, 4, 6, 7, 9, 10
ask(p, p->p_stats->p_prof.pr_addr,
> p->p_stats->p_prof.pr_ticks);
> + mtx_lock_spin(&sched_lock);
> + /* XXX why not unlock Giant? */
> }
> ---
I tested this, and it works!
No more `kernel trap 12 with interrup
On 31-May-01 Bruce Evans wrote:
> On Wed, 30 May 2001, David Taylor wrote:
>
>> When trying to profile ircd-hybrid-7 on -CURRENT (I tried using a pre-vm
>> madness version first, then tried a version cvsuped today), I reliably get
>> lots of:
>>
>> ker
On Wed, 30 May 2001, David Taylor wrote:
> When trying to profile ircd-hybrid-7 on -CURRENT (I tried using a pre-vm
> madness version first, then tried a version cvsuped today), I reliably get
> lots of:
>
> kernel trap 12 with interrupts disabled
>
> messages on the
On Wed, 30 May 2001, David Taylor wrote:
> When trying to profile ircd-hybrid-7 on -CURRENT (I tried using a pre-vm
> madness version first, then tried a version cvsuped today), I reliably get
> lots of:
>
> kernel trap 12 with interrupts disabled
>
> messages on the
When trying to profile ircd-hybrid-7 on -CURRENT (I tried using a pre-vm
madness version first, then tried a version cvsuped today), I reliably get
lots of:
kernel trap 12 with interrupts disabled
messages on the console (one every 5-10 seconds, when the ircd is reasonably
loaded).
I
r the two 'kernel trap 12 with interrupts
disabled' messages, the hot key does not work anymore.
Using gdb on rpc.lockd and some ddb single-stepping, I was able to
see that the freeze occurs somewhere during the first call to
callrpc().
I'll try a remote GDB session and see if it he
Le 2001-05-29, Andrew Gallatin écrivait :
> Did you also rebuild your kernel?
Yep, I did buildworld buildkenrnel installkernel installworld,
then mergemaster and reboot.
> In order for a bug report like this to be useful, you need to supply a
> backtrace from ddb or gdb. See the Kernel Debuggi
Thomas Quinot [[EMAIL PROTECTED]] wrote:
> In the hope to check for any recent improvements with lockd,
> I cvsupped this morning and remade world. I now have a very
Did you also rebuild your kernel?
In order for a bug report like this to be useful, you need to supply a
backtrace from ddb or gdb
rpc.statd are
mentioned in the 'Starting final network daemons' phase.
BUT:
* ps ax shows no trace of rpc.lockd
* an attempt to manually launch rpc.lockd immediately results in
a hard freeze with message 'Kernel trap 12 with interrupts
disabled (repeated twice).
* laun
tor. From there I have not been able to get any debugging info.
Last night I did a power off/on reset and went to bed. This morning I had
a login with a nice bold "kernel trap 12 with interrupts disabled" that
happened a couple of hours later after cvsuping and initiating a make world.
I
I had
a login with a nice bold "kernel trap 12 with interrupts disabled" that
happened a couple of hours later after cvsuping and initiating a make world.
I'm going to see if I can get it to do it again although I was able to do a
make world and kernel yesterday with no problem. T
On Sat, 19 May 2001 22:48:51 -0400, Alfred Perlstein <[EMAIL PROTECTED]> said:
> You'll have to provide more info before anyone can help you.
Well, that would require the kernel offering me more information.
> Can you at least get a DDB traceback?
I have never succeeded in getting that
* Michael Harnois <[EMAIL PROTECTED]> [010519 22:44] wrote:
> is the message I get as soon as I'm done booting with a kernel build
> from this evening's cvsup. No other messages ... sorry, no serial
> console ...
You'll have to provide more info before anyone can help you.
Can you at least get a
is the message I get as soon as I'm done booting with a kernel build
from this evening's cvsup. No other messages ... sorry, no serial
console ...
--
Michael D. Harnois[EMAIL PROTECTED]
Redeemer Lutheran Church Washburn, Iowa
Censorship is the stron
On Fri, 9 Feb 2001, Alexander Leidinger wrote:
> On 9 Feb, Bruce Evans wrote:
>
> > Pagefaults occur in copyin() (called from addupc_task() which is called
> > from ast()) while sched_lock is held. This is not good. Incrementing
> > the profiling counters is supposed to be pushed to ordinary
On 9 Feb, Bruce Evans wrote:
> Pagefaults occur in copyin() (called from addupc_task() which is called
> from ast()) while sched_lock is held. This is not good. Incrementing
> the profiling counters is supposed to be pushed to ordinary process
> context so that things like copyin() can work (t
On Thu, 8 Feb 2001, Alexander Leidinger wrote:
> if I run a program compiled with gcc's function profiling option I get
> "kernel trap 12 with interrupts disabled".
This happens with the standard profiling option -pg.
Pagefaults occur in copyin() (called from addupc_task()
Alexander Leidinger wrote:
> Hi,
>
> if I run a program compiled with gcc's function profiling option I get
> "kernel trap 12 with interrupts disabled".
The same is here.
-Maxim
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Hi,
if I run a program compiled with gcc's function profiling option I get
"kernel trap 12 with interrupts disabled".
If I run it withhin X11, the machine deadlocks hard (no response from
the numlock led on the keyboard), withhin a virtual console I get a lot
of "kernel trap
On 23-Oct-00 The Hermit Hacker wrote:
> kernel of today, during a make world, generates:
>
> Oct 23 18:32:18 thelab /boot/kernel/kernel: kernel trap 12 with interrupts
> disabled
> Oct 23 18:32:32 thelab /boot/kernel/kernel: kernel trap 12 with interrupts
> disabled
kernel of today, during a make world, generates:
Oct 23 18:32:18 thelab /boot/kernel/kernel: kernel trap 12 with interrupts disabled
Oct 23 18:32:32 thelab /boot/kernel/kernel: kernel trap 12 with interrupts disabled
Oct 23 18:32:39 thelab /boot/kernel/kernel: kernel trap 12 with interrupts
I got the same with addition that the machine hangs:(
Val
On Wed, 18 Oct 2000, Manfred Antar wrote:
> With current kernel I'm getting alot of :
> kernel trap 12 with interrupts disabled
> kernel trap 12 with interrupts disabled
> kernel trap 12 with interrupts disabled
>
With current kernel I'm getting alot of :
kernel trap 12 with interrupts disabled
kernel trap 12 with interrupts disabled
kernel trap 12 with interrupts disabled
kernel trap 12 with interrupts disabled
kernel trap 12 with interrupts disabled
Kernel from yesterday did not do this.
Every
40 matches
Mail list logo
