Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 13 Jun 2001 12:18:10 -0700 (PDT)
From:      Matthew Jacob <mjacob@feral.com>
To:        Andrew Gallatin <gallatin@cs.duke.edu>
Cc:        John Baldwin <jhb@FreeBSD.ORG>, freebsd-alpha@FreeBSD.ORG, wilko@FreeBSD.ORG
Subject:   More followup...
Message-ID:  <Pine.BSF.4.21.0106131214490.40934-100000@beppo.feral.com>
In-Reply-To: <15143.44887.290985.930683@grasshopper.cs.duke.edu>

next in thread | previous in thread | raw e-mail | index | archive | help

Hmmm- it seems to me that this indicates that there's a general non-TurboLaser
problem here- this is on a Rawhide:

panic: blockable sleep lock (sleep mutex) Giant @ ../../vm/vm_fault.c:213
cpuid = 0; panic
Stopped at      Debugger+0x34:  zapnot  v0,#0xf,a0      <v0=0x7,a0=0x6>
db> t
Debugger() at Debugger+0x34
panic() at panic+0x178
witness_lock() at witness_lock+0x240
vm_fault() at vm_fault+0x108
trap() at trap+0xf78
XentMM() at XentMM+0x2c
--- memory management fault (from ipl 7) ---
hardclock() at hardclock+0x308
handleclock() at handleclock+0x22c
alpha_clock_interrupt() at alpha_clock_interrupt+0x68
interrupt() at interrupt+0xb8
XentInt() at XentInt+0x28
--- interrupt (from ipl 4) ---
XentInt() at XentInt
--- interrupt (from ipl 3) ---
_end() at _end+0x9e58

The 'blockable sleep lock mutex' is bogus- what is clearly broken here is
having a fault in hardclock.


Oh- yeah- about TurboLaser? Somehow it got broken recently such that it no
longer even boots UP for me past CAM. 

Working on FreeBSD (alpha) is like experiencing what the character in the
first sentence in 100 Years of Solitude experienced. Only 3 times a week, 40
weeks a year.

-matt





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0106131214490.40934-100000>