Bug#456273: Bug #456273
- To: Moritz Muehlenhoff <jmm@inutil.org>
- Cc: 456273@bugs.debian.org, jmm@debian.org
- Subject: Bug#456273: Bug #456273
- From: Paul Gear <paul@gear.dyndns.org>
- Date: Thu, 01 Jan 2009 10:51:32 +1000
- Message-id: <495C1394.5040505@gear.dyndns.org>
- Reply-to: Paul Gear <paul@gear.dyndns.org>, 456273@bugs.debian.org
- In-reply-to: <20081226175430.GA12288@galadriel.inutil.org>
- References: <476B1E73.9080701@gear.dyndns.org> <20071221114318.GA16896@stro.at> <4776F13F.1040800@gear.dyndns.org> <478BF98B.6090005@gear.dyndns.org> <20080115002021.GV9040@baikonur.stro.at> <478FAF34.6030201@gear.dyndns.org> <20080122114501.GA4394@stro.at> <4796656F.5090507@gear.dyndns.org> <20080122220758.GC5009@baikonur.stro.at> <20081226175430.GA12288@galadriel.inutil.org>
Moritz Muehlenhoff wrote:
> On Tue, Jan 22, 2008 at 11:07:58PM +0100, maximilian attems wrote:
>> On Wed, Jan 23, 2008 at 07:51:43AM +1000, Paul Gear wrote:
>>> I assume by kerneloops you mean the ksymoops package? Is there anything
>>> special i need to do to enable serial output?
>> no i mean the kerneloops package.
>>
>> yes a serial cable and the corresponding console boot arg.
>>
>>>> sorry for loosing track but you are already running 2.6.24-rc8?
>>> No, but i've only tried up to 2.6.24-rc7. Nothing since 2.6.18-4 has
>>> worked on my system, except for Xen kernels. I'll install 2.6.24-rc8
>>> and test now.
>> ok.
>>
>>> Is there an easy way i can get a diff of the source differences between
>>> 2.6.18-4 and 2.6.18-5 so i can better report the issues to upstream?
>> yes if you checkout the subversion etch tree the series file nr 5 would
>> have the patches that had been added and you could do a binary search on
>> them enabling only half and so on until the faulty patch shows up.
>
> Does this error still occur with more recent kernel versions?
The following kernels work:
linux-image-2.6.18-3-amd64 2.6.18-7
linux-image-2.6.18-3-vserver-amd64 2.6.18-7
linux-image-2.6.18-4-amd64 2.6.18.dfsg.1-12etch2
linux-image-2.6.18-4-vserver-amd64 2.6.18.dfsg.1-12etch2
linux-image-2.6.18-4-xen-vserver-amd64 2.6.18.dfsg.1-12etch2
linux-image-2.6.18-6-xen-vserver-amd64 2.6.18.dfsg.1-23etch1
linux-image-2.6.26-bpo.1-xen-amd64 2.6.26-12~bpo40+1
The following kernels don't:
linux-image-2.6.18-6-amd64 2.6.18.dfsg.1-23etch1
linux-image-2.6.18-6-vserver-amd64 2.6.18.dfsg.1-23etch1
linux-image-2.6.22-3-amd64 2.6.22-6~bpo40+1
linux-image-2.6.22-3-vserver-amd64 2.6.22-6~bpo40+1
linux-image-2.6.23-1-amd64 2.6.23-2
linux-image-2.6.24-etchnhalf.1-amd64 2.6.24-6~etchnhalf.7
linux-image-2.6.24-rc6-amd64
2.6.24~rc6-1~experimental.1~snapshot.10030
linux-image-2.6.24-rc7-amd64
2.6.24~rc7-1~experimental.1~snapshot.10109
linux-image-2.6.24-rc8-amd64
2.6.24~rc8-1~experimental.2~snapshot.10176
linux-image-2.6.26-bpo.1-amd64 2.6.26-12~bpo40+1
linux-image-2.6.26-bpo.1-vserver-amd64 2.6.26-12~bpo40+1
I'm no expert, but i can't help but think that there is a bug in this
model of the Intel 965G/ICH8 chipset that the normal kernel is
exercising (due to a change that happened at 2.6.18-4) but Xen is not,
due to different behaviour of the AGP or MM subsystem.
Paul
Reply to: