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
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
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
On Sun, 5 Mar 2017 09:50:49 +0200 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,
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 kernel?
Sorry about the breakage.
The fix is in r314700.
>
> On
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.
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
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
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?
Thanks.
--Chris
On Sun, 05 Mar 2017 12:01:29 +0800 Alastair Hogge wrote
> Hi *,
>
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;
>
> kernel trap 12 with
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 = 00
fault virtual address = 0xbc04d753
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 to
This may not help much unless there is some common ground to be found.
I have been having problems with my old K6-2 300Mhz laptop hanging in X with
linux-communicator. 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 forgot to add that I'm not seeing any of this with the PIII's that I have
running current and usually updated daily.
This may not help much unless there is some common ground to be found.
I have been having problems with my old K6-2 300Mhz laptop hanging in X with
linux-communicator. From
* 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 DDB
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 (they
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 process
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
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() which is called
from
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
Oct 23 18:32:39 thelab
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
kernel trap 12 with
21 matches
Mail list logo