All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Blizbor <kernel@globalintech.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [crash] 2.4.22 and Can't locate module char-major-30
Date: Wed, 8 Dec 2004 20:15:57 -0200	[thread overview]
Message-ID: <20041208221557.GA2403@dmt.cyclades> (raw)
In-Reply-To: <41B75D85.8060302@globalintech.pl>

On Wed, Dec 08, 2004 at 09:01:09PM +0100, Blizbor wrote:
> I have defined "*.* /dev/pty/1" in the /etc/syslogd.conf and the last 
> line I saw before crash was
> 
> Dec  8 19:29:42 oracle-srv-03 modprobe: modprobe: Can't locate module 
> char-major-30

>From devices.txt:

 30 char        iBCS-2 compatibility devices
                  0 = /dev/socksys      Socket access
                  1 = /dev/spx          SVR3 local X interface
                  2 = /dev/inet/arp     Network access
                  2 = /dev/inet/icmp    Network access
                  2 = /dev/inet/ip      Network access
                  2 = /dev/inet/udp     Network access
                  2 = /dev/inet/tcp     Network access

                Additionally, iBCS-2 requires /dev/nfsd to be a link
                to /dev/socksys, and /dev/X0R to be a link to
                /dev/null.


You probably have some application trying to access this device(s).  Do you?

> Could these two things be related ?
>
> What can cause such a crash ?

It should not have nothing to do with the crash, did you get any oops or similar? 

> I have RH 9 with custom compiled kernel and it was working about 300 days
> without any problems.
> I'm using e100, ide, ext3, jfs and oracle 9i on this machine.

Suggest you to upgrade to a newer kernel. 

      reply	other threads:[~2004-12-09 18:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-08 20:01 [crash] 2.4.22 and Can't locate module char-major-30 Blizbor
2004-12-08 22:15 ` Marcelo Tosatti [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=20041208221557.GA2403@dmt.cyclades \
    --to=marcelo.tosatti@cyclades.com \
    --cc=kernel@globalintech.pl \
    --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.