linux-kernel - Re: Machine reboot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061013000556.89570.qmail@web83108.mail.mud.yahoo.com>
Date:	Thu, 12 Oct 2006 17:05:56 -0700 (PDT)
From:	Aleksey Gorelov <dared1st@...oo.com>
To:	Auke Kok <sofar@...-projects.org>
Cc:	xhejtman@...l.muni.cz, linux-kernel@...r.kernel.org,
	magnus.damm@...il.com, pavel@...e.cz
Subject: Re: Machine reboot


Auke Kok <sofar@...-projects.org> wrote:
> Aleksey Gorelov wrote:
> >> -----Original Message-----
> >> From: linux-kernel-owner@...r.kernel.org 
> >> [mailto:linux-kernel-owner@...r.kernel.org] On Behalf Of Lukas 
> >> Hejtmanek
> >> Sent: Thursday, October 05, 2006 3:53 AM
> >> To: linux-kernel@...r.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.


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