From: Shawn Starr <spstarr@sh0n.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [BUG][2.5.64bk4] Weird problem with 2 PCs
Date: Sun, 9 Mar 2003 21:58:20 -0500 [thread overview]
Message-ID: <200303092158.20664.spstarr@sh0n.net> (raw)
In-Reply-To: <200303091749.40739.spstarr@sh0n.net>
Can't be, everything is grounded. If i disconnect the serial and reboot the
A7M266-D it doesn't hang the IBM. I can only suspect the serial ground pin is
bad. I will tomorrow try 2.4.2x and see if this occurs. If it does NOT. Then
we have a problem here and finding it is going to be tough :-(
Shawn.
On Sunday 09 March 2003 5:49 pm, Shawn Starr wrote:
> I don't have an oops/panic to give because the box won't dump one on this
> issue.
>
> I have two PCs, an A7M266-D Athlon MP 2000+ and an IBM 300PL 6892-N2U PIII
> (Katmai) 450Mhz. If I leave the IBM machine on for a few hours or so, it's
> idle and just handling my mail/dns. The problem happens when I turn on the
> A7M266-D the other box locks up and reboots (due to panic=80).
> ksyslog/klogd aren't dumping any oopes to my logfile so I'm unable to
> capture the bug.
>
> 1. The PCs are connected via a router to my network.
>
> 2. The PCs are connected via serial port together (possibly causing the
> oops with interrupts?)
>
> Note, when I turn off and on the A7M266-D the IBM will not panic. It's only
> when the IBM is powered on for a few hours (if thats any help in narrowing
> down things).
>
> When It did panic, It reported __run_timers and a held spinlock by
> linux/timer.c but the EIP was 00000000 (garbage).
>
> Anyone else noticing strange things like this? This is really annoying :-(
prev parent reply other threads:[~2003-03-10 2:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-09 22:49 [BUG][2.5.64bk4] Weird problem with 2 PCs Shawn Starr
2003-03-09 23:06 ` Lionel Bouton
2003-03-10 2:58 ` Shawn Starr [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200303092158.20664.spstarr@sh0n.net \
--to=spstarr@sh0n.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.