Peter Wemm wrote:
> Mike Silbersack wrote:
> > On Tue, 26 Feb 2002, Peter Wemm wrote:
> > > Mike Silbersack wrote:
> > > > Hm, sounds like UP got optimized out.
> > > Gah! That would be a first. :(
> > Well, until I can build a working kernel, I'll just assume that it's a
> > feature.
> FWIW, tur
On Tue, Feb 26, 2002 at 09:29:51PM -0800, Peter Wemm wrote:
> FWIW, turning off PG_G see_ms to help. Change in pmap.c:
> #if !defined(SMP) || defined(ENABLE_PG_G)
> to:
> #if /*!defined(SMP) ||*/ defined(ENABLE_PG_G)
> and see how you go. This got me past atkbd0, but it is a very worrying
> sign
Mike Silbersack wrote:
> On Wed, 27 Feb 2002, Mike Silbersack wrote:
>
>
>>Disabling PG_G allows it to work here again as well. Given the problems
>>we're experiencing, backing out the pmap changes of the last two days
>>seems like a good idea.
>>
>>Mike "Silby" Silbersack
>>
>
> Well, I sorta
On Wed, 27 Feb 2002, Mike Silbersack wrote:
> Disabling PG_G allows it to work here again as well. Given the problems
> we're experiencing, backing out the pmap changes of the last two days
> seems like a good idea.
>
> Mike "Silby" Silbersack
Well, I sorta take that back. The box has been up
On Tue, 26 Feb 2002, Peter Wemm wrote:
> FWIW, turning off PG_G see_ms to help. Change in pmap.c:
> #if !defined(SMP) || defined(ENABLE_PG_G)
> to:
> #if /*!defined(SMP) ||*/ defined(ENABLE_PG_G)
> and see how you go. This got me past atkbd0, but it is a very worrying
> sign. I now get a vnod
Mike Silbersack wrote:
>
> On Tue, 26 Feb 2002, Peter Wemm wrote:
>
> > Mike Silbersack wrote:
> > >_
> > > Hm, sounds like UP got optimized out.
> >
> > Gah! That would be a first. :(
>
> Well, until I can build a working kernel, I'll just assume that it's a
> feature.
FWIW, turning off PG_G
On Tue, 26 Feb 2002, Peter Wemm wrote:
> Mike Silbersack wrote:
> >
> > Hm, sounds like UP got optimized out.
>
> Gah! That would be a first. :(
Well, until I can build a working kernel, I'll just assume that it's a
feature.
Mike "Silby" Silbersack
To Unsubscribe: send mail to [EMAIL PROTEC
Mike Silbersack wrote:
>
> On Tue, 26 Feb 2002, David Wolfskill wrote:
>
> > >Date: Tue, 26 Feb 2002 19:46:59 + (GMT)
> > >From: Mike Silbersack <[EMAIL PROTECTED]>
> >
> > >Using ACPI doesn't help here either. Hmph. Can I get a kernel dump that
> > >early in the boot process? The dumpon
On Tue, 26 Feb 2002, David Wolfskill wrote:
> >Date: Tue, 26 Feb 2002 19:46:59 + (GMT)
> >From: Mike Silbersack <[EMAIL PROTECTED]>
>
> >Using ACPI doesn't help here either. Hmph. Can I get a kernel dump that
> >early in the boot process? The dumpon manpage doesn't suggest a way as
> >far
On Tue, 26 Feb 2002, Mike Silbersack wrote:
> I reverted that change, and the double panic still occured. :|
>
> FWIW, you're correct in that I'm not using the acpi module.
>
> Mike "Silby" Silbersack
Using ACPI doesn't help here either. Hmph. Can I get a kernel dump that
early in the boot p
On Tue, 2002-02-26 at 17:38, Peter Wemm wrote:
> You may like to try reverting this change:
A great idea, but unfortunately, incorrect ...
--
Michael D. Harnois bilocational bivocational
Pastor, Redeemer Lutheran ChurchWashburn, Iowa
1L, UST School of Law
On Tue, 26 Feb 2002, Peter Wemm wrote:
> Mike Silbersack wrote:
> > I'm experiencing the same double panic on boot that PHK is now; are we the
> > only ones, or is it just that nobody else has updated recently?
>
> If you are not using acpica, then you're probably using vm86 for pcibios
> calls
On 26-Feb-2002 (17:27:19/GMT) Mike Silbersack wrote:
> I'm experiencing the same double panic on boot that PHK is
> now; are we the only ones, or is it just that nobody else
> has updated recently?
Mee too, just survied to 4 auto-reboot without messages...
Trying with a boot -v I see a keyboard
Mike Silbersack wrote:
> I'm experiencing the same double panic on boot that PHK is now; are we the
> only ones, or is it just that nobody else has updated recently?
If you are not using acpica, then you're probably using vm86 for pcibios
calls. I've been told that I've broken bios.c..
You may
I'm experiencing the same double panic on boot that PHK is now; are we the
only ones, or is it just that nobody else has updated recently?
Mike "Silby" Silbersack
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On 24-Feb-01 Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Bruce
> Evans writes:
>: It seems to be another trap while holding sched_lock. This should be
>: fatal, but the problem is only detected because trap() enables
>: interrupts. Then an interrupt causes bad things to happen. Unfortu
On 24-Feb-01 Julian Elischer wrote:
> Warner Losh wrote:
>>
>> I've added INVARIANTS and WITNESS to my kernel. Today I get a random
>> panic on boot sometimes:
>>
>> lock order reseral (this doesn't cause the panic, but
>> does seem to happen all th
In message <[EMAIL PROTECTED]> Warner Losh writes:
: I note that this doesn't happen when the disks are clean on boot, but
: does happen when they are dirty. The kernel is as of a cvsup 3pm MST
: today. The kernel from 1am last night doesn't seem to have this
: problem.
Doesn't seem to have thi
Warner Losh wrote:
>
> I've added INVARIANTS and WITNESS to my kernel. Today I get a random
> panic on boot sometimes:
>
> lock order reseral (this doesn't cause the panic, but
> does seem to happen all the time)
> 1st vnode interlock last acquired
In message <[EMAIL PROTECTED]> Bruce Evans
writes:
: It seems to be another trap while holding sched_lock. This should be
: fatal, but the problem is only detected because trap() enables
: interrupts. Then an interrupt causes bad things to happen. Unfortunately,
: the above omits the critical
On Fri, 23 Feb 2001, Warner Losh wrote:
> I've added INVARIANTS and WITNESS to my kernel. Today I get a random
> panic on boot sometimes:
>
> lock order reseral(this doesn't cause the panic, but
> does seem to happen all the time)
> 1st vnode interlock
I've added INVARIANTS and WITNESS to my kernel. Today I get a random
panic on boot sometimes:
lock order reseral (this doesn't cause the panic, but
does seem to happen all the time)
1st vnode interlock last acquired @ ../../usr/ffs/ffs_fsops.c:396
> Today's current (buildworld+build kernel), check out at ~10.00 GMT.
> I have this problem during 6-7 days, the stable version for me:
> FreeBSD newsfeed.gamma.ru 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Mon Oct 2 21:56:00
>MSD 2000 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NEWSFEED i386
> I haven
Today's current (buildworld+build kernel), check out at ~10.00 GMT.
I have this problem during 6-7 days, the stable version for me:
FreeBSD newsfeed.gamma.ru 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Mon Oct 2 21:56:00 MSD
2000 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NEWSFEED i386
I haven't any pr
24 matches
Mail list logo
