From: "J . A . Magallon" <jamagallon@able.es>
To: Rasmus Andersen <rasmus@jaquet.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reproducable oops in 2.2.17 and 2.2.18pre21
Date: Sat, 18 Nov 2000 02:15:41 +0100 [thread overview]
Message-ID: <20001118021541.A726@werewolf.able.es> (raw)
In-Reply-To: <20001117144938.F12733@jaquet.dk>
In-Reply-To: <20001117144938.F12733@jaquet.dk>; from rasmus@jaquet.dk on Fri, Nov 17, 2000 at 14:49:38 +0100
On Fri, 17 Nov 2000 14:49:38 Rasmus Andersen wrote:
> Hi.
>
> I get an oops reproducably with 2.2.17 and 2.2.18pre21 on a stock RH 6.2
> system. I cannot trigger it with the RH supplied kernel (2.2.14-5.0).
> I also got it with 2.2.17pre10 which prompted me to upgrade the kernel.
> I initially suspected bad RAM but have exchanged the RAM with memtest86'ed
> RAM for no improvement.
>
> What I do: I try to back the system up with tar zcvf /var/backup.tar.gz
> -X exclude /lib /sbin /var /bin /etc /boot /home /root /usr
> (the exclude file contains the path of the file itself, i.e.,
> /var/ backup.tar.gz).
>
Exclude /dev and /proc also, /lost+found if you have it, and /mnt if you
only want that drive. Perhaps things like /proc/kcore make trouble...
--
Juan Antonio Magallon Lacarta #> cd /pub
mailto:jamagallon@able.es #> more beer
-
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/
prev parent reply other threads:[~2000-11-18 1:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-17 13:49 Reproducable oops in 2.2.17 and 2.2.18pre21 Rasmus Andersen
2000-11-17 15:43 ` Marcelo Tosatti
2000-11-18 1:15 ` J . A . Magallon [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=20001118021541.A726@werewolf.able.es \
--to=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=rasmus@jaquet.dk \
/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