On Thu, 13 Jan 2005, Doug White wrote:
#7 0xe93a0018 in ?? ()
#8 0xc0580010 in kvprintf (fmt=0xc7b04c60 "?6w?\v6t?\v6t?", func=0x59,
arg=0xe93ad9bc, radix=-1067875706, ap=0xc3839674 "\001")
at /usr/src/sys/kern/subr_prf.c:643
#9 0xc058940a in selwakeuppri (sip=0x0, pri=0)
at /usr/
On Wed, 5 Jan 2005, Mitch Parks wrote:
> It seems both my test and production boxes are not stable with 5.3-Release.
> I'm hoping for some insight in how to make at least the production box
> not crash.
[...]
> #7 0xe93a0018 in ?? ()
> #8 0xc0580010 in kvprintf (fmt=0xc7b04c60 "?6w?\v6t?\v6t?"
On Thu, 6 Jan 2005, Mike Tancsa wrote:
> At 06:29 PM 05/01/2005, Mitch Parks wrote:
> >It seems both my test and production boxes are not stable with
> >5.3-Release. I'm hoping for some insight in how to make at least the
> >production box not crash.
> >The crashes have been at different times o
At 06:29 PM 05/01/2005, Mitch Parks wrote:
It seems both my test and production boxes are not stable with
5.3-Release. I'm hoping for some insight in how to make at least the
production box not crash.
The crashes have been at different times of the day and I've found no
suspicious log activity.
It seems both my test and production boxes are not stable with 5.3-Release.
I'm hoping for some insight in how to make at least the production box
not crash.
Production Box: Dell 2600, Dual 2.8 Xeon, 2Gb ram, onboard (amr) RAID. This
box was stable running 5.1, 5.2, and 5.2.1, but has crashed/r
