On Fri, Apr 08, 2005 at 10:14:17AM -0700, Doug White wrote:
> > Fatal trap 12: page fault while in kernel mode
> > fault virtual address = 0x20202020
>
> Hm, something ran into a bunch of ASCII spaces..
>
> Can you jump to frame #6 and print *kbp? It appears the kernel malloc
> bucket list
Hi all,
warning: This report might be somewhat vague.
For quite a while now I`ve been plagued with the problem that logging out from a
serial console causes the box to panic. For a while I`ve been sure this was
isolated to one of my boxen, because it`s been acting up in other ways as well,
but tod
On Sun, 10 Apr 2005 [EMAIL PROTECTED] wrote:
warning: This report might be somewhat vague. For quite a while now I`ve
been plagued with the problem that logging out from a serial console
causes the box to panic. For a while I`ve been sure this was isolated to
one of my boxen, because it`s been a
Hi,
As I'm without a TV at the moment, I decided to plug my XBox into my TV card
(via bktr driver) and attempt to play the brilliant Burnout 3 via my monitor
and mplayer. Unfortunately, as soon as things get busy (as they inevitably do
in this game), the screen started to show signs of interlac
Peter Jeremy wrote:
On Sat, 2005-Apr-09 14:51:41 -0500, Ash wrote:
This is consistent with the kernel continuing to run normally but being
unable to schedule userland processes - usually due to a deadlock.
Do the caps-lock, num-lock, scroll-lock buttons on a local keyboard
still toggle the relevant
On Sun, Apr 10, 2005 at 02:39:00PM +0100, Mark Dixon wrote:
>
> Does anyone know if there is a simple switch that needs setting somewhere to
> make the card not do this, or if its simply a performance problem with
> something (my computer, mplayer, bktr driver) not being able to keep up with
>
Ash wrote:
>
>
> I was hoping that someone on the list may have run into a similar
> issue with 5_4_0 so that I could at least figure out how to reproduce
> the problem rather than simply waiting for the machine to hang again.
> Patience is not my greatest virtue :)
>
I'm seeing a similar sympto
I have twice so far had the kernel syslog a stack backtrace with no
other information. Inspection of the kernel source, to the best of my
limited understanding, suggests that getdirtybuf() was handed a buffer
without an associated vnode. Kernel config file and make.conf attached.
Should I be con
Brandon S. Allbery KF8NH presumably uttered the following on 04/10/05 15:16:
I have twice so far had the kernel syslog a stack backtrace with no
other information. Inspection of the kernel source, to the best of my
limited understanding, suggests that getdirtybuf() was handed a buffer
without an
I recently notice these errors in my dmesg. Can somebody help explain
this to me. Do I need to worry about this?
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD-K6(tm) 3D+ Processor (400.91-MHz 586-class CPU)
Origin = "AuthenticAMD" Id = 0x591 Stepping = 1
Features=0x8021bf
AMD
I forgot to add this part :-)
FreeBSD 5.3-RELEASE #3: Sun Apr 10 17:11:03 PDT 2005
Eric Marquez wrote:
I recently notice these errors in my dmesg. Can somebody help explain
this to me. Do I need to worry about this?
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD-K6(tm) 3D+ Processo
On Sun, Apr 10, 2005 at 05:23:56PM -0700, Eric Marquez <[EMAIL PROTECTED]> was
witnessed plotting the following conspiracy:
> I recently notice these errors in my dmesg. Can somebody help explain
> this to me. Do I need to worry about this?
>
> Timecounter "i8254" frequency 1193182 Hz quality
On Friday, 8 April 2005 at 13:04:18 -0700, David O'Brien wrote:
> On Tue, Apr 05, 2005 at 10:09:11AM +0930, Greg 'groggy' Lehey wrote:
>> The moral of the story is, I suppose, "don't buy the MSI K8T
>> Master2-FAR". I was warned about the motherboard before I bought it,
>
> WHY?? There is nothin
FYI: I have posted a CFD to freebsd-doc for some proposed changes to
the above article to try to address some common problems we keep seeing
with incoming PRs. Discussion should take place there.
mcl
___
freebsd-stable@freebsd.org mailing list
http://
It appears that this commit is good.
Testing has been limited so far, but I've been unable to get it to misbehave.
--
--
Karl Denninger ([EMAIL PROTECTED]) Internet Consultant & Kids Rights Activist
http://www.denninger.netMy home on the net - links to everything I do!
http://scubaforum.
At 09:17 AM 09/04/2005 -0600, Scott Long wrote this to All:
All,
Thanks to the keen eye of David Sze, the cause of the instability in the
ips driver in FreeBSD 4.x might have been found. If it's affecting you,
please try the attached patch and let me know the results. I'll commit it
when everyo
David Sze wrote:
At 09:17 AM 09/04/2005 -0600, Scott Long wrote this to All:
All,
Thanks to the keen eye of David Sze, the cause of the instability in
the ips driver in FreeBSD 4.x might have been found. If it's
affecting you,
please try the attached patch and let me know the results. I'll
com
17 matches
Mail list logo
