From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: monte <monte@eslashlonghorns.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel bug
Date: Sun, 13 Apr 2008 20:20:41 +0200 [thread overview]
Message-ID: <9a8748490804131120p4dfa2af1j4ead4f28ada45d4f@mail.gmail.com> (raw)
In-Reply-To: <48022F82.80704@eslashlonghorns.com>
On 13/04/2008, monte <monte@eslashlonghorns.com> wrote:
> Since I am new at this, this is the info you may need.
>
There's a very good document describing information kernel developers
may need when reporting kernel bugs. It's called 'REPORTING-BUGS' and
can be found in the root of the kernel source tree - here's a link to
an online copy: http://lxr.linux.no/linux+v2.6.24.4/REPORTING-BUGS
> I am trying to using Ubuntu hardy (development branch), Kernel 2.6.24-16,
That's a distribution kernel, not a stock kernel.org kernel. As a
general rule, kernel developers at kernel.org have a hard time
providing help with distribution kernels since almost all
distributions take the kernel.org kernel and then add patches of their
own to it. This makes it hard for kernel.org people to know if the bug
you have hit is due to a distribution specific patch or not.
For this reason it's generally a good idea to verify the problem with
a kernel.org kernel - usually testing the latest released kernel as
well as the latest pre-release kernel and providing information on
whether or not the problem occurs with them is very valuable info (in
this case, the kernels to test would then be 2.6.24.4 and 2.6.25-rc9,
sources for both are available at http://kernel.org/ ).
> and get the following error
>
> error 18: selected cylinder exceeds maximum supported by BIOS.
>
That's not a kernel problem. It's a problem with your bootloader.
For details on this specific error and what to do about it, take a
look at http://wiki.linuxquestions.org/wiki/GRUB#Error_18
> This started with kernel 2.6.24-15. Currently I have to boot into kernel
> 2.6.24-14.
>
I'd guess that you do not have a sepperate /boot partitions where you
keep your kernels (or if you do it's not at the start of your disk).
The fact that your 2.6.24-14 kernel boots and your 2.6.24-15 does not
probably has to do with the -14 one being placed within the first 1024
cyl of the disk (probably purely by luck) and the -15 was placed
elsewhere. The way to ensure that they always end up within the first
1024cyl that your BIOS can handle is by having a /boot partition at
the start of the disk that is <=512MB and then always place your
kernels there.
> My BIOS are Award Modular Bios v4.51PC, with Award Plug and Play Bios ext
> v1.0A
>
If a BIOS update is available it's possible it could resolve the issue
by allowing the BIOS to see more than the first 1024 cylinders of the
disk, but with a system as old as this I doubt it very much.
Hope that helps you.
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2008-04-13 18:20 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-13 16:06 monte
2008-04-13 18:20 ` Jesper Juhl [this message]
2008-04-13 18:33 ` Alan Cox
[not found] <200907311139.55095.christoph.thielecke@gmx.de>
2009-07-31 16:01 ` Linus Torvalds
2009-07-31 16:26 ` Eric Paris
-- strict thread matches above, loose matches on Subject: below --
2008-09-10 20:35 Todor Gyumyushev
2008-09-11 3:21 ` Aaron Straus
2008-03-29 9:05 Olver Eduardo Ramos
2008-03-30 1:06 ` Rafael J. Wysocki
2007-09-19 21:43 Kernel bug Branislav Bozgai
2007-09-24 15:33 ` Mel Gorman
2007-08-19 18:33 kernel bug Costas Sismanis
2006-12-22 11:59 Kernel BUG Rudy Zijlstra
2006-12-22 13:42 ` Peter Zijlstra
2005-11-26 1:23 Kernel bug Vympel
2005-11-27 12:51 ` Hugh Dickins
2005-11-03 18:10 Kernel BUG Mark Fortescue
2005-11-03 18:59 ` Trond Myklebust
2005-11-03 23:15 ` Mark Fortescue
2005-11-04 10:08 ` Mark Fortescue
2003-03-26 23:57 Perez-Gonzalez, Inaky
2003-03-27 14:23 ` Hugh Dickins
2003-03-26 13:13 kasper_k_jensen
2003-01-25 22:56 Kernel bug Massimiliano C. - Uf0On|in3
2003-01-19 18:01 Christophe Dupre
2003-01-07 9:17 kernel BUG Sönke Ruempler
2002-12-07 10:09 Kernel BUG Henrik Steffen
2002-12-08 1:47 ` Alan Cox
2002-11-27 11:31 kernel bug sanket rathi
2002-11-27 10:45 sanket rathi
2002-11-27 9:50 sanket rathi
2002-11-27 10:10 ` Arjan van de Ven
2002-06-28 19:54 kernel BUG Eric Weiss
2002-06-28 19:26 ew
2002-06-27 19:23 Chaoyang Deng
2002-06-28 5:58 ` Austin Gonyou
2002-06-28 14:00 ` Mike Black
2002-05-21 14:01 kernel bug Chen Hao
2001-11-25 18:03 Kernel Bug gonzalo.ab
2001-11-25 23:59 ` Adam Schrotenboer
2001-03-06 19:55 kernel bug ernte23
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=9a8748490804131120p4dfa2af1j4ead4f28ada45d4f@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=monte@eslashlonghorns.com \
/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®