In message <[EMAIL PROTECTED]> Matthew Dillon writes:
: Forget the drilling! Blood conducts electricity... simply *installing*
: a motherboard in those fraggin sharp-edged sheet metal chassis is enough!
I've had one or two cheapo mo-bos that haven't worked at 100MHz after
spattering huma
:>ECC doesn't protect against certain types of motherboard address line
:> errors (since although the ECC is correct, the selected address is wrong, so
:> thus the data is wrong). There's parity protection on parts of the CPU
:> address bus, but I don't believe there is any protection between
> >On Thu, Oct 07, 1999 at 10:09:23AM -0700, Matthew Dillon wrote:
> >
> >> Intel's ECC implementation is not perfect (1), but it's good enough to
> >> catch these sorts of problems.
> >
> >Just as an interesting side note, we had a motherboard which
> >supported ECC ram and had ECC ram i
>On Thu, Oct 07, 1999 at 10:09:23AM -0700, Matthew Dillon wrote:
>
>> Intel's ECC implementation is not perfect (1), but it's good enough to
>> catch these sorts of problems.
>
>Just as an interesting side note, we had a motherboard which
>supported ECC ram and had ECC ram in it and which
On Thu, Oct 07, 1999 at 10:09:23AM -0700, Matthew Dillon wrote:
> Intel's ECC implementation is not perfect (1), but it's good enough to
> catch these sorts of problems.
Just as an interesting side note, we had a motherboard which
supported ECC ram and had ECC ram in it and which was cr
> :Hi again,
> :
> : Whoops: a few hours after downgrading to 3.1-STABLE I had a double fault
> :error (strange, it didn't look like a normal panic screen, just the
> :message and the content of three registers, then the syncing disks
> :message). It seems that I might be wrong about hardware not
:Hi again,
:
: Whoops: a few hours after downgrading to 3.1-STABLE I had a double fault
:error (strange, it didn't look like a normal panic screen, just the
:message and the content of three registers, then the syncing disks
:message). It seems that I might be wrong about hardware not being the
:p
Hi again,
On Wed, 6 Oct 1999, Adrian Penisoara wrote:
> hi again,
>
> On Tue, 5 Oct 1999, Matthew Dillon wrote:
>
> > : The problem is that the machine is completely locked, I can't get into
> > :the debugger with CTR-ALT-ESC; no panics so there are no coredumps
> > :catched. Any advise ? Coul
hi again,
On Tue, 5 Oct 1999, Matthew Dillon wrote:
> : The problem is that the machine is completely locked, I can't get into
> :the debugger with CTR-ALT-ESC; no panics so there are no coredumps
> :catched. Any advise ? Could you escape in the debugger when you were hit
> :by these bugs ?
>
>
: The problem is that the machine is completely locked, I can't get into
:the debugger with CTR-ALT-ESC; no panics so there are no coredumps
:catched. Any advise ? Could you escape in the debugger when you were hit
:by these bugs ?
If it's completely locked up and ctl-alt-esc doesn't work (an
Hi,
On Mon, 4 Oct 1999, Adrian Penisoara wrote:
>
> I have a -stable production server that keeps (solidly) blocking pretty
> often (I don't get over 3 days uptimes). If you need details just let me
> know.
Just to let you know: syncing every second in a loop like this:
while true
do
Hi,
On Mon, 4 Oct 1999, Matthew Dillon wrote:
> : Excuse my intrusion, but could you be so kind to tell me whether you had
> :the time to build patches for these MMAP-related freezes ? If not could
> :you recommend me some workarounds ?
> :
> : I have a -stable production server that keeps (soli
: Excuse my intrusion, but could you be so kind to tell me whether you had
:the time to build patches for these MMAP-related freezes ? If not could
:you recommend me some workarounds ?
:
: I have a -stable production server that keeps (solidly) blocking pretty
:often (I don't get over 3 days uptim
On Mon, 4 Oct 1999, Adrian Penisoara wrote:
>
> Excuse my intrusion, but could you be so kind to tell me whether you had
> the time to build patches for these MMAP-related freezes ? If not could
> you recommend me some workarounds ?
doubling the ram from 384 -> 768 meg appears to have fixed it
Hi,
On Mon, 14 Jun 1999, Matthew Dillon wrote:
>
> :>
> :> David, can you email this program to me please?
> :>
> :> Also, which FreeBSD release does this occur on?
> :>
> :> I've got about 6 mmap-related bugs on my plate at the moment. 3 of them
> :> have been identified (
:Anyway, I have a simple program that mmap()s a 1Gig file into memory,
:madvise()s it that it will be doing random access. If I quit and restart
:this program a couple of times (yes, it close()s and munmap()s the segment),
:my system will hard lock. By dropping into DDB once I found that it was
:Over the past week and a bit, the INN -CURRENT source tree had a major
:upheaval of code, in order to fix the major problem where reader speed
:sucked. What used to take >1min to load up a newsgruop now generally
:takes mere seconds (no exaggeration, try it)...
:
:The problem is that the new cod
On Wed, 9 Jun 1999, The Hermit Hacker wrote:
> Did try this...actually went to the Livingston WWW site, and they "fixed
> this bug" around release 3.1.4 of ComOS :( The 'send break' just gets
> ignored...
The bug they fixed was that sending a telnet BRK sequence during an
administrative session
>>> And today's trick question...how do you send a break? :( I'm telnet'd
>>> into a Livingston Portmaster, with 'telnet -E' to disable the telnet
>>> break...
>> Any particular reason you're using the -E option? The easiest way to send
>> a serial break on most terminal servers is hitting the tel
On Wed, 9 Jun 1999, Jasper O'Malley wrote:
> On Wed, 9 Jun 1999, The Hermit Hacker wrote:
>
> > And today's trick question...how do you send a break? :( I'm telnet'd
> > into a Livingston Portmaster, with 'telnet -E' to disable the telnet
> > break...
>
> Any particular reason you're using the
On Wed, 9 Jun 1999, The Hermit Hacker wrote:
> And today's trick question...how do you send a break? :( I'm telnet'd
> into a Livingston Portmaster, with 'telnet -E' to disable the telnet
> break...
Any particular reason you're using the -E option? The easiest way to send
a serial break on most
On Wed, 9 Jun 1999, David E. Cross wrote:
> You have more than enough space to do it to. Swap memory is not dumped, only
> RAM is... typicall it is dumped to the swap partition. In this case you
> have well more than enough.
Ah, okay, then I mis-read the error ;( I have 1.6gig of swap spread
You have more than enough space to do it to. Swap memory is not dumped, only
RAM is... typicall it is dumped to the swap partition. In this case you
have well more than enough.
If your /etc/fstab showed "/dev/da3s1b" as your 1.6 gig swap partition, you
would add "dumpon=/dev/da3s1b" to your /et
On Wed, 9 Jun 1999, David E. Cross wrote:
> by "break" I mean a serial break condition. Take the Tx line out of your
> box and bring it negative 3-5 volts for a short time, that will be a break.
>
> Seriously, the break will need to be sent from the piece of equipment that is
> connected to the
by "break" I mean a serial break condition. Take the Tx line out of your
box and bring it negative 3-5 volts for a short time, that will be a break.
Seriously, the break will need to be sent from the piece of equipment that is
connected to the other end of the serial line. It isn't a telnet iss
On Wed, 9 Jun 1999, David E. Cross wrote:
> I believe I stumbled over this as well. (As a side note, you can run DDB
> over a serial console too, just compile with DDB, and DDB_UNATTENDED so your
> system will come back if it unexpectedly panics; on the serial console send
> a 'break').
And tod
I believe I stumbled over this as well. (As a side note, you can run DDB
over a serial console too, just compile with DDB, and DDB_UNATTENDED so your
system will come back if it unexpectedly panics; on the serial console send
a 'break').
Anyway, I have a simple program that mmap()s a 1Gig file i
Over the past week and a bit, the INN -CURRENT source tree had a major
upheaval of code, in order to fix the major problem where reader speed
sucked. What used to take >1min to load up a newsgruop now generally
takes mere seconds (no exaggeration, try it)...
The problem is that the new code make
28 matches
Mail list logo
