Bug#545364: Maybe kernel problem?
On Mittwoch, 9. September 2009, Philipp Marek wrote: I found out that if I use linux-image-2.6.30-1-amd64=2.6.30-5 (instead of -6) my system boots again. With the last apt-get clean the -5 was deleted, and so I was stuck with -6. But - surprise, surprise! - the system booted cleanly next time. So it's probably not a kernel problem per se ... the same kernel binary sometimes works, and sometimes doesn't. Bootloader? Alignment? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545364: Maybe kernel problem?
I've got this too. I found out that if I use linux-image-2.6.30-1-amd64=2.6.30-5 (instead of -6) my system boots again. But I'm not sure whether it's simply a kernel problem, or just related because of some size difference in the image. My out-of-range pointer is 0x6401900; in case the video hardware helps to find some common bit, it's a ATI Technologies Inc RS482 [Radeon Xpress 200]. Regards, Phil -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org