mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adam Voigt <adam@cryptocomm.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel Itself Reports Bug, Continuous OOPS's, and Phantom NIC Card
Date: 27 Mar 2003 10:42:02 -0500	[thread overview]
Message-ID: <1048779722.1873.13.camel@beowulf.cryptocomm.com> (raw)
In-Reply-To: <1048776183.1873.2.camel@beowulf.cryptocomm.com>

Sorry, the Kernel mailing list server won't let me attach the
files, so here are URL's:

http://64.238.252.49:8080/dmesg.txt
http://64.238.252.49:8080/lsmod.txt
http://64.238.252.49:8080/lspci.txt
http://64.238.252.49:8080/messages.txt

On Thu, 2003-03-27 at 09:42, Adam Voigt wrote:
    Distro: Redhat 8.0
    Kernel: Redhat 2.4.18-27.8.0 (Latest)
    Mobo: Aptron P4VXAD
    CPU: 2.4 GHZ Intel Pentium 4
    RAM: 512 MB
    Kernel Params: ide=nodma, pci=biosirq (the dmesg suggested it =))
    
    Leaving the computer running all night, with only a CPU
    intensive task (i.e., seti@home), produced the attached
    message log, of what appear to be almost on-the-clock
    hourly OOPS's. This ofcourse led me to believe it was something
    in my cron schedule, only problem is, it's empty, so it's
    either syslogd or a built in system hourly task (no problems
    on 8 other machines with this same kernel, distro, and config).
    
    Behavior with the OOPS's, is sporatic, I can turn the machine
    on, wait ten minutes, and log in, and do a "ls" and it will
    OOPS, other times it will be hours before I see them.
    
    One other problem, probably unrelated, the BIOS and the Kernel
    both report seeing a "Realtek 8139" NIC on the computer, though
    no such card exists and it is not built onto the mobo, only a
    3COM 3c59x (PCI Card).
    
    Included in the messages the kernel seemed to want me to
    report to the list two bug reports =), seeing as how it even
    has "cut here" in the messages file. Attached, is the full
    /var/log/message, at the end of the file, the machine just quit,
    as when I came in, no display would come up. I've also attached
    the output from dmesg, lsmod, and lspci, if you need anything else,
    or have any ideas, PLEASE don't hesitate to tell me.
    
    -- 
    Adam Voigt (adam@cryptocomm.com)
    The Cryptocomm Group
    My GPG Key: http://64.238.252.49:8080/adam_at_cryptocomm.asc
-- 
Adam Voigt (adam@cryptocomm.com)
The Cryptocomm Group
My GPG Key: http://64.238.252.49:8080/adam_at_cryptocomm.asc


  reply	other threads:[~2003-03-27 15:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-27 14:42 Adam Voigt
2003-03-27 15:42 ` Adam Voigt [this message]
2003-03-27 17:04 ` Alan Cox
2003-03-27 17:07   ` Adam Voigt
2003-03-27 17:28     ` Alan Cox
2003-03-27 17:55       ` Adam Voigt
2003-03-27 19:09         ` Alan Cox
2003-03-28 16:03           ` Adam Voigt

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=1048779722.1873.13.camel@beowulf.cryptocomm.com \
    --to=adam@cryptocomm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®