From: "Jos� Luis Domingo L�pez" <jldomingo@crosswinds.net>
To: linux-kernel@vger.kernel.org
Subject: Re: bug in kernel 2.2.19
Date: Fri, 13 Apr 2001 11:41:15 +0000 [thread overview]
Message-ID: <20010413114115.A668@dardhal.mired.net> (raw)
In-Reply-To: <20010413085623.A280@pisidlo.sh.cvut.cz>
In-Reply-To: <20010413085623.A280@pisidlo.sh.cvut.cz>; from J.Gregor@sh.cvut.cz on Fri, Apr 13, 2001 at 08:56:23AM +0200
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1130 bytes --]
On Friday, 13 April 2001, at 08:56:23 +0200,
Jan Gregor wrote:
> Hi
> Kernel 2.2.19 downloaded from www.kernel.org sometimes when I boot from lilo
> reports after "uncompressing linux ..." and blank line shows "crc error"
> and halts.
> [...]
>
Same behavior here, as I reported some days ago on this same list (with no
response). 2.2.19 halts nearly always on boot, just before "Uncompressing
linux...". 2.2.18 reboots at the same point in the boot process, but the
system ends up booting about 10-20% of the times. I've had no problems with
Debian Potato's 2.2.17 kernel version.
However, booting any of the above kernels from a floppy works fine 100% of
times. So I wonder if this could be a problem with my hard disk's cache or
something related. I've observed that the "Loading linux" progress
indicator is much faster with kernels that give problems than with kernels
that don't.
--
José Luis Domingo López
Linux Registered User #189436 Debian GNU/Linux Potato (P166 64 MB RAM)
jdomingo EN internautas PUNTO org => ¿ Spam ? Atente a las consecuencias
jdomingo AT internautas DOT org => Spam at your own risk
prev parent reply other threads:[~2001-04-13 9:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-13 6:56 Jan Gregor
2001-04-13 11:41 ` Jos� Luis Domingo L�pez [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=20010413114115.A668@dardhal.mired.net \
--to=jldomingo@crosswinds.net \
--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
all inboxes | Powered by JetHome®