[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: sarge + 2.6.12 kernel panic



original post:

Just installed sarge, got fresh kernel sources for 2.6.12, used an oldconfig from a previously successful 2.6.11 kernel, and compiled. Unfortunately when I tried to boot that kernel I got this:

	attempt to access beyond end of device
	hda2: rw=16, want=8, limit=2
	kernel panic - not syncing: I/O error reading memory image

I accepted the default sarge partitioning scheme for a desktop machine, so / is on hda1, and hda2 is an extended partition containing logical partitions hda5 and hda6 (I wonder why those numbers?).

I have found some references to this issue but they're a little over my head.

The default kernel boots fine, and there are few significant differences in the configs., that I can see anyway.

Does anyone know about this issue, or how to fix it?
Please CC me.

Thanks,

John

request for more information:

<>I have a box upgraded from woody to sarge.

Are you using grub or lilo? (Although I didn't do a fresh install


<>as you did, I suspect that you are using grub.

Posting the differences in your config file might help. Also lspci
results.

I'm probably as clueless as you, but the extra information might help.



Dennis Carr wrote:

		(stuff deleted)

At any rate, this has been popping up on the IRC channel as well - people
upgrading kernel from 2.6.8 to beyond on sarge have invariably experienced
problems and I suspect that this is the reason that the current kernel
image source and tree are still at 2.6.8, backports notwithstanding.

Just my $.42.

-Dennis Carr



I am also subscribed to the Debian kernel list where they seem to be discussing 2.6.12 for Debian. The config file from that package might be helpful!
The subject title is

Re: goals for 2.6.12-2 (and beyond)

I lifted this from the following bug report which has the location of 2.6.12 that I used:

Bug#317787: kernel-source-2.6.10: md memory leak
maximilian attems <debian@sternwelten.at>
07/11/05 13:38

no 2.6.10 is unsupported, we are switching to 2.6.12 atm
there is some delay due to the new unified packaging,
but if you just need x86 version you can test those out:
http://charm.itp.tuwien.ac.at/~mattems/


Anyway, John, (the original poster), is having trouble going from 2.6.11 to 2.6.12. If he will post more information about his bootup environment such as whether he's using grub or lilo and some details about his hard drive configuration, types, etc. then someone on the list may have
the specific information that he needs.


--
(Mr.) Gayle Lee Fairless, http://counter.li.org/, No. 365760.
Linux Gcomm 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686 GNU/Linux
Linux Gcomm 2.6.11-1-686 #1 Mon Jun 20 22:00:38 MDT 2005 i686 GNU/Linux
Linux Gcomm 2.6.12-1-686 #1 Fri Jun 24 12:17:14 CEST 2005 i686 GNU/Linux



Reply to: