From: Auke Kok <auke-jan.h.kok@intel.com>
To: Aleksey Gorelov <dared1st@yahoo.com>
Cc: xhejtman@mail.muni.cz, linux-kernel@vger.kernel.org,
magnus.damm@gmail.com, pavel@suse.cz
Subject: Re: Machine reboot
Date: Thu, 12 Oct 2006 21:08:34 -0700 [thread overview]
Message-ID: <452F1142.3000400@intel.com> (raw)
In-Reply-To: <20061013000556.89570.qmail@web83108.mail.mud.yahoo.com>
Aleksey Gorelov wrote:
> Auke Kok <sofar@foo-projects.org> wrote:
>> Aleksey Gorelov wrote:
>>>> -----Original Message-----
>>>> From: linux-kernel-owner@vger.kernel.org
>>>> [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Lukas
>>>> Hejtmanek
>>>> Sent: Thursday, October 05, 2006 3:53 AM
>>>> To: linux-kernel@vger.kernel.org
>>>> Subject: Machine reboot
>>>>
>>>> Hello,
>>>>
>>>> I'm facing troubles with machine restart. While sysrq-b
>>>> restarts machine, reboot
>>>> command does not. Using printk I found that kernel does not
>>>> hang and issues
>>>> reset properly but BIOS does not initiate boot sequence. Is
>>>> there something
>>>> I could do?
>>> I have similar issue on Intel DG965WH board. Did you try to shutdown network interface and
>>> 'rmmod e1000' right before reboot ? In my case machine reboots fine after that.
>>>
>>> Aleks.
>>
>> interesting, do you do that because it specifically fixes a problem you have? if so, I'd
>> like to know about it :)
>>
>> Auke
>>
> I'm just trying to localize the issue.
> Since right before machine stalls during reboot I see something like
>
> ACPI: PCI interrupt for device 000:00:19.0 disabled
> Restarting system.
that's quite a normal message, not sure why that would constitute a problem.
> and this device is Gb ethernet, e1000 is perfect candidate to look at. And yes, removing e1000
> before reboot works around the issue.
Have you tried to only `ifconfig ethX down` ? my own i965 board shuts down perfectly
fine without unloading the e1000 driver.
> I'm afraid this is now common issue across Intel 965 board series, at least with their latest BIOS
> updates.
first time I've heard of it!
I'm unsure my BIOS version will be the same as it's a devel system for our drivers, but
still I have never heard of anyone requiring the full unload of the NIC driver to be
able to shutdown.
Would you be able to debug a failed shutdown perhaps and capture the console output?
when exactly does it `stall` ? What other interrupts are assigned on your system? Did
other BIOS versions work correctly?
Auke
next prev parent reply other threads:[~2006-10-13 4:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 23:24 Machine reboot Aleksey Gorelov
2006-10-12 23:43 ` Auke Kok
2006-10-13 0:05 ` Aleksey Gorelov
2006-10-13 4:08 ` Auke Kok [this message]
2006-10-13 9:16 ` Lukas Hejtmanek
2006-10-13 14:36 ` Auke Kok
2006-10-13 15:25 ` Lukas Hejtmanek
2006-10-13 16:22 ` Lukas Hejtmanek
2006-10-13 20:22 ` Aleksey Gorelov
2006-10-13 21:41 ` Lukas Hejtmanek
2006-10-13 23:22 ` Aleksey Gorelov
2006-10-14 10:51 ` Lukas Hejtmanek
2006-10-13 15:30 ` Arjan van de Ven
2006-10-13 16:26 ` Lukas Hejtmanek
2006-10-13 20:27 ` Aleksey Gorelov
2006-10-13 20:30 ` Lukas Hejtmanek
2006-10-13 21:36 ` Aleksey Gorelov
-- strict thread matches above, loose matches on Subject: below --
2006-10-05 10:52 Lukas Hejtmanek
2006-10-05 11:28 ` Jesper Juhl
2006-10-05 13:59 ` Lukas Hejtmanek
2006-10-05 11:58 ` Magnus Damm
2006-10-05 16:05 ` Lukas Hejtmanek
2006-10-08 18:51 ` Pavel Machek
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=452F1142.3000400@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=dared1st@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=pavel@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.