public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shawn Starr <Shawn.Starr@Home.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PS hanging in 2.4.1 - More interesting things
Date: Sun, 04 Feb 2001 15:37:35 -0500	[thread overview]
Message-ID: <3A7DBD8F.71941A32@Home.net> (raw)
In-Reply-To: <E14PVka-00026u-00@the-village.bc.nu>

[-- Attachment #1: Type: text/plain, Size: 635 bytes --]

Well, i found something in my logs:

This really is weird :)

Shawn.

Alan Cox wrote:

> > Well, strangely, it stopped as it started?
> > I don't know what caused it to go loopy but then it just stopped. Im using:
> > syslogd -ver
> > syslogd 1.4-0
> >
> > klogd -v
> > klogd 1.4-0
> >
> > I thought this only affected older versions?
>
> Yep. So something else happened in this case. I don't know what but that
> would appear to be a different bug
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/

[-- Attachment #2: dump.log --]
[-- Type: text/plain, Size: 825 bytes --]

Feb  3 18:11:35 coredump syslogd 1.4-0: restart.
Feb  3 18:11:35 coredump syslogd: select: Bad file descriptor
Feb  3 18:12:06 coredump last message repeated 214069 times
Feb  3 18:14:48 coredump syslogd 1.4-0: restart.
Feb  3 18:14:48 coredump syslogd: select: Bad file descriptor
Feb  3 18:21:08 coredump syslogd 1.4-0: restart.
Feb  3 18:21:08 coredump syslogd: select: Bad file descriptor
Feb  3 18:21:34 coredump last message repeated 168154 times
Feb  3 18:24:08 coredump syslogd 1.4-0: restart.
Feb  3 18:24:08 coredump syslogd: select: Bad file descriptor
Feb  3 18:24:39 coredump last message repeated 231290 times
Feb  3 18:26:07 coredump syslogd 1.4-0: restart.
Feb  3 18:27:24 coredump init: Switching to runlevel: 6
Feb  3 18:27:31 coredump exiting on signal 15
Feb  3 18:34:44 coredump syslogd 1.4-0: restart.


  reply	other threads:[~2001-02-04 20:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-03 22:48 PS hanging in 2.4.1 - HAPPENING NOW!!! Shawn Starr
2001-02-03 23:00 ` Shawn Starr
2001-02-03 23:37 ` PS hanging in 2.4.1 - More interesting things Shawn Starr
2001-02-04 11:05   ` Alan Cox
2001-02-04 20:21     ` Shawn Starr
2001-02-04 20:27       ` Alan Cox
2001-02-04 20:37         ` Shawn Starr [this message]
2001-02-04  1:11 ` PS hanging in 2.4.1 - HAPPENING NOW!!! Marko Kreen
2001-02-04  1:06   ` Shawn Starr
2001-02-04  1:19     ` Marko Kreen

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=3A7DBD8F.71941A32@Home.net \
    --to=shawn.starr@home.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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