[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46CF7C3F.10707@imap.cc>
Date: Sat, 25 Aug 2007 02:47:59 +0200
From: Tilman Schmidt <tilman@...p.cc>
To: Andrew Morton <akpm@...ux-foundation.org>
CC: linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
john stultz <johnstul@...ibm.com>, Andi Kleen <ak@...e.de>,
Len Brown <lenb@...nel.org>, linux-acpi@...r.kernel.org,
Dave Jones <davej@...emonkey.org.uk>,
Thomas Renninger <trenn@...e.de>,
Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>
Subject: Re: 2.6.23-rc3-mm1
Am 25.08.2007 02:07 schrieb Andrew Morton:
> On Sat, 25 Aug 2007 01:27:25 +0200
> Tilman Schmidt <tilman@...p.cc> wrote:
>
>> Am 22.08.2007 11:06 schrieb Andrew Morton:
>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc3/2.6.23-rc3-mm1/
>> After applying Matthew Wilcox' patch to include/linux/isa.h
>
> which patch is that?
The one allowing drivers/scsi/advansys.c to compile with CONFIG_ISA=n:
Date: Wed, 22 Aug 2007 10:28:02 -0600
From: Matthew Wilcox <matthew@....cx>
Subject: Re: drivers/scsi/advansys.c - ld error ( Re: 2.6.23-rc3-mm1 )
Message-ID: <20070822162802.GJ9163@...isc-linux.org>
When CONFIG_ISA is disabled, the isa_driver support will not be compiled
in. Define stubs so that we don't get link-time errors.
>> this compiles
>> and boots on my Intel/openSUSE 10.2 test machine but throws out the
>> following messages I don't remember ever seeing with other kernels:
>>
>> - on console early during boot, also in SuSE's /var/log/boot.msg:
>>
>> your system time is not correct:
>> Wed Jul 13 13:15:31 UTC 1910
>> setting system time to:
>> Tue Jul 24 00:00:00 UTC 2007
>
> What architecture?
i386. The machine is a Pentium D 940 which would be x86_64 capable,
but I'm still running 32 bit kernels on it.
> if x86_64 then perhaps something went wrong with the old x86_64 dynticks
> leftovers which were in rc3-mm1. I've just merged a shiny fresh new series
> so perhaps things there got fixed. Please retest next -mm.
Will do that anyway.
> Perhaps it would be helpful if you could do a
>
> diff -u dmesg-2.6.23-rc3 dmesg-2.6.26-rc3-mm1
I hope the attached helps. I created it by taking /var/log/boot.msg
of the two systems, removing everything after "Kernel logging stopped",
editing out the printk timestamps and then running diff -u on them,
so it should be more or less the dmesg diff. I did not edit out any
of the differences because I'm lazy. (And also because I wasn't so sure
what would or wouldn't be interesting for you.)
--
Tilman Schmidt E-Mail: tilman@...p.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
View attachment "bootmsg.diff" of type "text/plain" (24982 bytes)
Download attachment "signature.asc" of type "application/pgp-signature" (254 bytes)
Powered by blists - more mailing lists