Re: Quigon... the evil router.

[Dan Brosemer <odin@cleannorth.org>]

On Thu, Jun 21, 2001 at 06:49:43PM -0400, Jay Gostlin wrote:
> Is it an overheating issue....or a system conflict of some sort?

Thanks for the tips.

> >A while ago, we tried a new CPU fan and thermal grease to no effect.

I don't think it's overheating.  It has a crystal cooler, and a load of
grease.

Conflicts... hrm...

Using irqs:
0 - system
1 - keyboard
3 - tty01
4 - tty00
5 - 1st NIC (ec0)
6 - floppy
7 - printer
9 - 2nd NIC (vr0)
12 - 3rd NIC (rl0)
14 - IDE

IO:
0x60  keyboard
0x250 first nic
0x378 printer
0xf0  FPU
0x3f8 tty00
0x2f8 tty01
0x3f0 floppy

shmem:
0xd8000 - first NIC

drq:
2 - floppy

No, I don't see any conflicts, unless you know of another resource I should
look for conflicts in.

Here's a posting made just today on the openbsd-misc mailing list:

> I had a similar problem w/ 2.8. Every 4 or so days, the machine would
> lock, I could press enter at the console and the text would scroll, but I
> couldn't enter ddb, and there was no kernel panic.
> 
> I would suggest you get a serious memory testing program in case you have
> bad RAM. (I would think almost any other h/w failure would cause a panic
> or at least something more useful.)
> 
> I upgraded to 2.9 and it went away *after* I compiled a minimal kernel.

So maybe my 2.9 upgrade will help.  Maybe I should pull out my memtest86
floppies...

Here's hoping.

-Dan

-- 
"There are two limits that this standard places on the number of
characters in a line. Each line of characters MUST be no more than
998 characters, and SHOULD be no more than 78 characters, excluding
the CRLF."       -- rfc2822 - Internet Message Format