From: Aleksey Gorelov <dared1st@yahoo.com>
To: Auke Kok <sofar@foo-projects.org>
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 17:05:56 -0700 (PDT) [thread overview]
Message-ID: <20061013000556.89570.qmail@web83108.mail.mud.yahoo.com> (raw)
In-Reply-To: <452ED33A.6000106@foo-projects.org>
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.
and this device is Gb ethernet, e1000 is perfect candidate to look at. And yes, removing e1000
before reboot works around the issue.
I'm afraid this is now common issue across Intel 965 board series, at least with their latest BIOS
updates.
Aleks.
next prev parent reply other threads:[~2006-10-13 0:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 23:24 Aleksey Gorelov
2006-10-12 23:43 ` Auke Kok
2006-10-13 0:05 ` Aleksey Gorelov [this message]
2006-10-13 4:08 ` Auke Kok
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=20061013000556.89570.qmail@web83108.mail.mud.yahoo.com \
--to=dared1st@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=pavel@suse.cz \
--cc=sofar@foo-projects.org \
--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
all inboxes | Powered by JetHome®