Date: Fri, 13 Oct 2006 23:41:45 +0200
From: Lukas Hejtmanek <xhejtman@mail.muni.cz>
To: Aleksey Gorelov <dared1st@yahoo.com>
Cc: Auke Kok <auke-jan.h.kok@intel.com>, linux-kernel@vger.kernel.org
Subject: Re: Machine reboot
Message-ID: <20061013214145.GJ3039@mail.muni.cz>
References: <20061013162210.GG3039@mail.muni.cz> <20061013202224.95503.qmail@web83115.mail.mud.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-2
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20061013202224.95503.qmail@web83115.mail.mud.yahoo.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1309
Lines: 31

On Fri, Oct 13, 2006 at 01:22:24PM -0700, Aleksey Gorelov wrote:
> > Good news, as of kernel 2.6.19-rc1-git9, BIOS does *not* hang with both e1000 as
> > module or built in kernel.
> > 
> > The previous version of kernel was 2.6.18 which hangs the BIOS.
> > 
> > Aleksey:
> > are you sure that it is not the same in your case? Did you not switch kernel
> > version between e1000 as a module and built in kernel?
> 
> As far as I understand, you've udpated the whole kernel, not just the
> driver. I've tried using  driver from 2.6.19-rc2 as well as v7.2.9 from 
> Intel's website - same story - still no reboot. Did you try just updating 
> driver (without whole kernel) ? 

I've rechecked behaviour of e1000 driver. For me, it looks like this:

2.6.18 (vanilla): e1000 as a module - system reboots OK.
                  e1000 built in    - system hangs after KBD reset or tripple
		                      fault

2.6.19-rc1-git9 (vanilla): e1000 as a module - system reboots OK.
                           e1000 built in    - system reboots OK.

-- 
Luk?? Hejtm?nek
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/