lkml.org 
[lkml]   [2006]   [Oct]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
DateThu, 12 Oct 2006 21:08:34 -0700
FromAuke Kok <>
SubjectRe: Machine reboot
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
-
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/

\
 
 \ /
  Last update: 2006-10-13 06:13    [from the cache]
©2003-2010