public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Auke Kok <auke-jan.h.kok@intel.com>
To: Ryan Richter <ryan@tau.solarneutrino.net>,
	"Allan, Bruce W" <bruce.w.allan@intel.com>
Cc: Lukas Hejtmanek <xhejtman@mail.muni.cz>,
	Aleksey Gorelov <dared1st@yahoo.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Machine restart doesn't work - Intel 965G, 2.6.19-rc2
Date: Sat, 21 Oct 2006 10:56:33 -0700	[thread overview]
Message-ID: <453A5F51.9080803@intel.com> (raw)
In-Reply-To: <20061021173402.GA30750@tau.solarneutrino.net>

Ryan Richter wrote:
> On Fri, Oct 20, 2006 at 08:06:10PM +0200, Lukas Hejtmanek wrote:
>> On Fri, Oct 20, 2006 at 10:57:29AM -0700, Auke Kok wrote:
>>> To all that are seeing this problem:
>>>
>>> can you send me (off-list is OK) the motherboard number+name, the BIOS 
>>> versions (+ where you downloaded them from) that you have tried and for 
>>> each version, whether it worked without this workaround or not?
 >>
>> Three days ago, Intel released a new BIOS version that claims to fix
>> this issue.
>>
>> I've tested it with 2.6.18 kernel which was unable to restart, it
>> works now so it seems that fix was successful.
> 
> I just tried the 1458 BIOS without the workaround and it's working fine.

okay, looks like the latest BIOS fixes it (hang on reboot/restart) for everyone. Thanks 
for reporting back in, I'll make sure my colleagues write this down for everyone.

Cheers,

Auke

  reply	other threads:[~2006-10-21 17:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-13 21:40 Machine restart doesn't work - Intel 965G, 2.6.19-rc2 Aleksey Gorelov
2006-10-13 21:42 ` Ryan Richter
2006-10-13 21:45   ` Lukas Hejtmanek
2006-10-13 21:46     ` Ryan Richter
2006-10-13 21:49       ` Lukas Hejtmanek
2006-10-13 21:51         ` Ryan Richter
2006-10-17 18:00         ` Ryan Richter
2006-10-17 20:53           ` Aleksey Gorelov
2006-10-17 21:17             ` Machine restart doesn't work - Intel 965G, 2.6.19-rc2 / e1000? Auke Kok
2006-10-17 22:14               ` dared1st
2007-11-20 14:38               ` e1000 driver problems Lukas Hejtmanek
2007-11-26 23:26                 ` Kok, Auke
2007-11-27 15:07                   ` Lukas Hejtmanek
2007-11-27 16:48                     ` Kok, Auke
2007-11-27 17:31                       ` Lukas Hejtmanek
2006-10-17 22:27             ` Machine restart doesn't work - Intel 965G, 2.6.19-rc2 Ryan Richter
2006-10-20 17:57               ` Auke Kok
2006-10-20 18:06                 ` Lukas Hejtmanek
2006-10-21 17:34                   ` Ryan Richter
2006-10-21 17:56                     ` Auke Kok [this message]
2006-10-20 18:07                 ` Ryan Richter
2006-10-20 18:17                   ` Auke Kok
2006-10-20 18:29                     ` Lukas Hejtmanek
2006-10-23 20:52                   ` Aleksey Gorelov
2006-10-13 21:50       ` Aleksey Gorelov
  -- strict thread matches above, loose matches on Subject: below --
2006-10-13 21:25 Ryan Richter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=453A5F51.9080803@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=bruce.w.allan@intel.com \
    --cc=dared1st@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ryan@tau.solarneutrino.net \
    --cc=xhejtman@mail.muni.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox