public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
To: Werner.Beck@Lidl.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops in Kernel 2.4.21-rc1
Date: Tue, 27 May 2003 14:18:37 +0200	[thread overview]
Message-ID: <3ED3579D.7030300@gmx.net> (raw)
In-Reply-To: <OF4CB12D76.81223041-ONC1256D33.0040CFEC-C1256D33.004202DC@eu.lidl.net>

Werner.Beck@Lidl.de wrote:
> Hello,
> I encountered a Kernel oops on two different PCs, both a configured
> identical. The system uses an ISDN connection to an Internet ISP and then
> establishes a VPN tunnel based on PPTP.
> As far as I can see in /var/log/messages the problem occurred on both
> system at the same time at 00:15, but not at the same day and not every

You are using SuSE 7.3, which leads me to the assumption that the
nightly cronjob at 00:15 is triggering this. One of the culprits I can
imagine is the updatedb run at that time. However, this is only
guesswork. The Oops itself does not give me any idea. Perhaps someone
else can help.

> day. No special program is running at that time. Basically it is a SuSE 7.3
> distribution, I made a Kernel upgrade.
> Hardware is a Fujitsu Siemens N300 PC with an IDE (7200 Rpm), Intel 845GI
> Motherboard, an ISDN PBX connected via USB to dial-up, the connection
> wasn't established when the system oopsed.
> Attached are some information.
> (See attached file: info.txt)(See attached file: oops.log)


HTH,
Carl-Daniel
-- 
http://www.hailfinger.org/


  reply	other threads:[~2003-05-27 12:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-27 12:01 Oops in Kernel 2.4.21-rc1 Werner.Beck
2003-05-27 12:18 ` Carl-Daniel Hailfinger [this message]
2003-05-27 13:49 ` Stephan von Krawczynski

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=3ED3579D.7030300@gmx.net \
    --to=c-d.hailfinger.kernel.2003@gmx.net \
    --cc=Werner.Beck@Lidl.de \
    --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