public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "jeev" <naptime@cervnet.com>
To: "'Dan Chen'" <crimsun@email.unc.edu>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Linux 2.4.17 problem.
Date: Sun, 20 Jan 2002 00:08:18 -0800	[thread overview]
Message-ID: <002d01c1a189$9f45ae60$0200a8c0@mainframe> (raw)
In-Reply-To: <20020120062620.GA25787@opeth.ath.cx>

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

Also this is an asus a7v133 motherboard with an athlon 1.4ghz, just
curious to see if others have these sorts of problems. Also forgot to
add this:

EXT2-fs error (device ide0(3,1)): ext2_free_blocks: bit already cleared
for block 7942458

Got that while rm'ing a 100meg file as root.

j

> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel-
> owner@vger.kernel.org] On Behalf Of Dan Chen
> Sent: Saturday, January 19, 2002 10:26 PM
> To: jeev
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: Linux 2.4.17 problem.
> 
> Would you run those through ksymoops and repost?
> 
> On Sat, Jan 19, 2002 at 09:24:56PM -0800, jeev wrote:
> > Hi, im running slackware with the kernel 2.4.17, when I tar -zxvf a
big
> > file, ie. hlds_l_3108_full.tar.gz.
> >
> > It cuts off saying format violated..
> > This is an amd 1.4ghz with 768 mbram 41gb 7200rpm harddrive (brand
new
> > stuff)
> 
> --
> Dan Chen                 crimsun@email.unc.edu
> GPG key:   www.unc.edu/~crimsun/pubkey.gpg.asc

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3224 bytes --]

      parent reply	other threads:[~2002-01-20  8:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-20  5:24 Linux 2.4.17 problem jeev
2002-01-20  6:26 ` Dan Chen
2002-01-20  6:31   ` jeev
2002-01-20  7:25   ` jeev
2002-01-20  8:08   ` jeev [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='002d01c1a189$9f45ae60$0200a8c0@mainframe' \
    --to=naptime@cervnet.com \
    --cc=crimsun@email.unc.edu \
    --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