Machine reboot

Machine reboot

[Lukas Hejtmanek]

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?

-- 
Lukáš Hejtmánek

Re: Machine reboot

[Jesper Juhl]

On 05/10/06, Lukas Hejtmanek <xhejtman@mail.muni.cz> wrote:
> 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?
>
You can try playing with different combinations of these options :

CONFIG_APM_ALLOW_INTS
CONFIG_APM_REAL_MODE_POWER_OFF

-- 
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

Re: Machine reboot

[Magnus Damm]

On 10/5/06, Lukas Hejtmanek <xhejtman@mail.muni.cz> wrote:
> 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?

A long shot, but switching to real mode does not work if the cpu is
running in VMX root mode ie on hardware with Intel VT extensions
enabled. So if you are using some kind of kernel virtualization module
on rather new hardware, consider rmmod:ing the module before
rebooting.

I'm about to post patches for kexec that fixes this problem, but I'm
not sure about the current reboot status.

/ magnus

Re: Machine reboot

[Lukas Hejtmanek]

On Thu, Oct 05, 2006 at 01:28:00PM +0200, Jesper Juhl wrote:
> >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?
> >
> You can try playing with different combinations of these options :
> 
> CONFIG_APM_ALLOW_INTS
> CONFIG_APM_REAL_MODE_POWER_OFF

I'm not using APM (as I think my board DP965LT does not support APM).

Also power off works OK (using halt cmd).

-- 
Lukáš Hejtmánek

Re: Machine reboot

[Lukas Hejtmanek]

On Thu, Oct 05, 2006 at 08:58:22PM +0900, Magnus Damm wrote:
> A long shot, but switching to real mode does not work if the cpu is
> running in VMX root mode ie on hardware with Intel VT extensions
> enabled. So if you are using some kind of kernel virtualization module
> on rather new hardware, consider rmmod:ing the module before
> rebooting.
> 
> I'm about to post patches for kexec that fixes this problem, but I'm
> not sure about the current reboot status.

You are right, I'm using Intel Core 2 Duo processor with DP965LT board that is
capable of VT extensions. However, I'm using vanilla 2.6.18 kernel in X86_64,
no additional patches, nor XEN or VMWARE is running (even their modules are
not loaded). Moreover, SYSRQ-B (emergency reboot) works fine. System graceful
reboot does not work.

-- 
Lukáš Hejtmánek

Re: Machine reboot

[Pavel Machek]

On Thu 05-10-06 18:05:18, Lukas Hejtmanek wrote:
> On Thu, Oct 05, 2006 at 08:58:22PM +0900, Magnus Damm wrote:
> > A long shot, but switching to real mode does not work if the cpu is
> > running in VMX root mode ie on hardware with Intel VT extensions
> > enabled. So if you are using some kind of kernel virtualization module
> > on rather new hardware, consider rmmod:ing the module before
> > rebooting.
> > 
> > I'm about to post patches for kexec that fixes this problem, but I'm
> > not sure about the current reboot status.
> 
> You are right, I'm using Intel Core 2 Duo processor with DP965LT board that is
> capable of VT extensions. However, I'm using vanilla 2.6.18 kernel in X86_64,
> no additional patches, nor XEN or VMWARE is running (even their modules are
> not loaded). Moreover, SYSRQ-B (emergency reboot) works fine. System graceful
> reboot does not work.

Of course... copy/paste pieces of sysrq-b sequence into regular
sequence to find out what the critical difference is... no, it will
not be easy.

Perhaps your box *likes* to reboot with apic on or something? Perhaps
device_shutdown() breaks your ability to reboot?

-- 
Thanks for all the (sleeping) penguins.

RE: Machine reboot

[Aleksey Gorelov]

>-----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.

Re: Machine reboot

[Auke Kok]

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

Re: Machine reboot

[Aleksey Gorelov]

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.

Re: Machine reboot

[Auke Kok]

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

Re: Machine reboot

[Lukas Hejtmanek]

On Thu, Oct 12, 2006 at 09:08:34PM -0700, Auke Kok wrote:
> >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 can confirm that rmmod e1000 causes that machine can reboot gracefully.

> 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?

Up to version 0864 it restarts normally. Any higher version causes hang on
restart if e1000 driver is loaded.

I've tried to report it to Intel but they replied that Linux is unsupported on
this board...

It's not an issue in the Linux kernel. Using various printk I can see that
tripple fault or reset via KBD is issued and followed by hang of the BIOS. 

For i965 chipsets, the BIOS is *a lot* buggy :(

-- 
Lukáš Hejtmánek

Re: Machine reboot

[Auke Kok]

Lukas Hejtmanek wrote:
> On Thu, Oct 12, 2006 at 09:08:34PM -0700, Auke Kok wrote:
>>> 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 can confirm that rmmod e1000 causes that machine can reboot gracefully.
> 
>> 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?
> 
> Up to version 0864 it restarts normally. Any higher version causes hang on
> restart if e1000 driver is loaded.
> 
> I've tried to report it to Intel but they replied that Linux is unsupported on
> this board...
> 
> It's not an issue in the Linux kernel. Using various printk I can see that
> tripple fault or reset via KBD is issued and followed by hang of the BIOS. 
> 
> For i965 chipsets, the BIOS is *a lot* buggy :(

that's depressing, can you send me the output of `dmidecode` of the latest BIOS? Perhaps 
I can reproduce it myself with that version.

Auke

Re: Machine reboot

[Lukas Hejtmanek]

[-- Attachment #1: Type: text/plain, Size: 306 bytes --]

On Fri, Oct 13, 2006 at 07:36:01AM -0700, Auke Kok wrote:
> >For i965 chipsets, the BIOS is *a lot* buggy :(
> 
> that's depressing, can you send me the output of `dmidecode` of the latest 
> BIOS? Perhaps I can reproduce it myself with that version.

output of dmidecode is attached.

-- 
Lukáš Hejtmánek

[-- Attachment #2: dmidecode --]
[-- Type: text/plain, Size: 9908 bytes --]

# dmidecode 2.8
SMBIOS 2.4 present.
35 structures occupying 1629 bytes.
Table at 0x000E4390.

Handle 0x0000, DMI type 4, 35 bytes
Processor Information
	Socket Designation: LGA 775
	Type: Central Processor
	Family: <OUT OF SPEC>
	Manufacturer: Intel(R) Corporation
	ID: F6 06 00 00 FF FB EB BF
	Version: Intel(R) Core(TM)2 CPU          6400  @ 2.13GHz
	Voltage: 1.6 V
	External Clock: 266 MHz
	Max Speed: 4000 MHz
	Current Speed: 2133 MHz
	Status: Populated, Enabled
	Upgrade: Other
	L1 Cache Handle: 0x0003
	L2 Cache Handle: 0x0001
	L3 Cache Handle: Not Provided
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified

Handle 0x0001, DMI type 7, 19 bytes
Cache Information
	Socket Designation: Unknown
	Configuration: Enabled, Not Socketed, Level 2
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 2048 KB
	Maximum Size: 2048 KB
	Supported SRAM Types:
		Asynchronous
	Installed SRAM Type: Asynchronous
	Speed: Unknown
	Error Correction Type: Single-bit ECC
	System Type: Unified
	Associativity: 8-way Set-associative

Handle 0x0002, DMI type 7, 19 bytes
Cache Information
	Socket Designation: Unknown
	Configuration: Enabled, Not Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 32 KB
	Maximum Size: 32 KB
	Supported SRAM Types:
		Asynchronous
	Installed SRAM Type: Asynchronous
	Speed: Unknown
	Error Correction Type: Single-bit ECC
	System Type: Instruction
	Associativity: 8-way Set-associative

Handle 0x0003, DMI type 7, 19 bytes
Cache Information
	Socket Designation: Unknown
	Configuration: Enabled, Not Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 32 KB
	Maximum Size: 32 KB
	Supported SRAM Types:
		Asynchronous
	Installed SRAM Type: Asynchronous
	Speed: Unknown
	Error Correction Type: Single-bit ECC
	System Type: Data
	Associativity: 8-way Set-associative

Handle 0x0004, DMI type 0, 24 bytes
BIOS Information
	Vendor: Intel Corp.
	Version: MQ96510J.86A.1250.2006.1005.1532
	Release Date: 10/05/2006
	Address: 0xF0000
	Runtime Size: 64 kB
	ROM Size: 1024 kB
	Characteristics:
		PCI is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		Boot from CD is supported
		Selectable boot is supported
		EDD is supported
		8042 keyboard services are supported (int 9h)
		Serial services are supported (int 14h)
		Printer services are supported (int 17h)
		CGA/mono video services are supported (int 10h)
		ACPI is supported
		USB legacy is supported
		ATAPI Zip drive boot is supported
		BIOS boot specification is supported
		Function key-initiated network boot is supported
		Targeted content distribution is supported
	BIOS Revision: 0.0
	Firmware Revision: 0.0

Handle 0x0005, DMI type 1, 27 bytes
System Information
	Manufacturer:                                 
	Product Name:                                 
	Version:                         
	Serial Number:                                 
	UUID: 52871F95-040B-11DB-AFD2-0013200B4F9E
	Wake-up Type: Power Switch
	SKU Number: Not Specified
	Family: Not Specified

Handle 0x0006, DMI type 2, 20 bytes
Base Board Information
	Manufacturer: Intel Corporation
	Product Name: DP965LT
	Version: AAD41694-203
	Serial Number: AZLT62600926
	Asset Tag: Base Board Asset Tag
	Features:
		Board is a hosting board
		Board is replaceable
	Location In Chassis: Base Board Chassis Location
	Chassis Handle: 0x0007
	Type: Unknown
	Contained Object Handles: 0

Handle 0x0007, DMI type 3, 17 bytes
Chassis Information
	Manufacturer:                                 
	Type: Unknown
	Lock: Not Present
	Version:                         
	Serial Number:                                 
	Asset Tag:                                 
	Boot-up State: Safe
	Power Supply State: Safe
	Thermal State: Other
	Security Status: Other
	OEM Information: 0x00000000

Handle 0x0008, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: PRIMARY
	Internal Connector Type: On Board IDE
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x0009, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: SECONDARY
	Internal Connector Type: On Board IDE
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x000A, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: ATX_PWR
	Internal Connector Type: Other
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x000B, DMI type 9, 13 bytes
System Slot Information
	Designation: PCIE X16 SLOT
	Type: x16 PCI Express
	Current Usage: In Use
	Length: Short
	Characteristics:
		3.3 V is provided

Handle 0x000C, DMI type 9, 13 bytes
System Slot Information
	Designation: PCIE X1 SLOT 1
	Type: x1 PCI Express
	Current Usage: Available
	Length: Short
	Characteristics:
		3.3 V is provided
		PME signal is supported
		SMBus signal is supported

Handle 0x000D, DMI type 9, 13 bytes
System Slot Information
	Designation: PCIE X1 SLOT 2
	Type: x1 PCI Express
	Current Usage: Available
	Length: Short
	Characteristics:
		3.3 V is provided
		PME signal is supported
		SMBus signal is supported

Handle 0x000E, DMI type 9, 13 bytes
System Slot Information
	Designation: PCIE X1 SLOT 3
	Type: x1 PCI Express
	Current Usage: Available
	Length: Short
	Characteristics:
		3.3 V is provided
		PME signal is supported
		SMBus signal is supported

Handle 0x000F, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI SLOT 1
	Type: 32-bit PCI
	Current Usage: Available
	Length: Long
	ID: 1
	Characteristics:
		3.3 V is provided
		PME signal is supported
		SMBus signal is supported

Handle 0x0010, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI SLOT 2
	Type: 32-bit PCI
	Current Usage: In Use
	Length: Long
	ID: 2
	Characteristics:
		3.3 V is provided
		PME signal is supported
		SMBus signal is supported

Handle 0x0011, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI SLOT 3
	Type: 32-bit PCI
	Current Usage: Available
	Length: Long
	ID: 3
	Characteristics:
		3.3 V is provided
		PME signal is supported
		SMBus signal is supported

Handle 0x0012, DMI type 10, 6 bytes
On Board Device Information
	Type: Video
	Status: Disabled
	Description: Intel(R) Extreme Graphics 3 Controller

Handle 0x0013, DMI type 10, 6 bytes
On Board Device Information
	Type: Ethernet
	Status: Enabled
	Description: Intel (R) 82562 Ethernet Device

Handle 0x0014, DMI type 10, 6 bytes
On Board Device Information
	Type: Sound
	Status: Disabled
	Description: Intel(R) Azalia Audio Device

Handle 0x0015, DMI type 13, 22 bytes
BIOS Language Information
	Installable Languages: 1
		enUS
	Currently Installed Language: enUS

Handle 0x0016, DMI type 32, 20 bytes
System Boot Information
	Status: No errors detected

Handle 0x0017, DMI type 16, 15 bytes
Physical Memory Array
	Location: System Board Or Motherboard
	Use: System Memory
	Error Correction Type: None
	Maximum Capacity: 8 GB
	Error Information Handle: Not Provided
	Number Of Devices: 4

Handle 0x0018, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x0017
	Error Information Handle: Not Provided
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 512 MB
	Form Factor: DIMM
	Set: None
	Locator: J6H1
	Bank Locator: CHAN A DIMM 0
	Type: DDR2
	Type Detail: Synchronous
	Speed: 667 MHz (1.5 ns)
	Manufacturer: 0x7F98000000000000
	Serial Number: 0x6C2F674F
	Asset Tag: Unknown
	Part Number: 0x000000000000000000000000000000000000

Handle 0x0019, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x0001FFFFFFF
	Range Size: 512 MB
	Physical Device Handle: 0x0018
	Memory Array Mapped Address Handle: 0x001E
	Partition Row Position: 1
	Interleave Position: 1
	Interleaved Data Depth: 1

Handle 0x001A, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x0017
	Error Information Handle: Not Provided
	Total Width: Unknown
	Data Width: Unknown
	Size: No Module Installed
	Form Factor: DIMM
	Set: None
	Locator: J6H2
	Bank Locator: CHAN A DIMM 1
	Type: DDR2
	Type Detail: None
	Speed: Unknown
	Manufacturer: NO DIMM
	Serial Number: NO DIMM
	Asset Tag: NO DIMM
	Part Number: NO DIMM

Handle 0x001B, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x0017
	Error Information Handle: Not Provided
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 512 MB
	Form Factor: DIMM
	Set: None
	Locator: J6J1
	Bank Locator: CHAN B DIMM 0
	Type: DDR2
	Type Detail: Synchronous
	Speed: 667 MHz (1.5 ns)
	Manufacturer: 0x7F98000000000000
	Serial Number: 0x6C2F724F
	Asset Tag: Unknown
	Part Number: 0x000000000000000000000000000000000000

Handle 0x001C, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00020000000
	Ending Address: 0x0003FFFFFFF
	Range Size: 512 MB
	Physical Device Handle: 0x001B
	Memory Array Mapped Address Handle: 0x001E
	Partition Row Position: 2
	Interleave Position: 2
	Interleaved Data Depth: 1

Handle 0x001D, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x0017
	Error Information Handle: Not Provided
	Total Width: Unknown
	Data Width: Unknown
	Size: No Module Installed
	Form Factor: DIMM
	Set: None
	Locator: J6J2
	Bank Locator: CHAN B DIMM 1
	Type: DDR2
	Type Detail: None
	Speed: Unknown
	Manufacturer: NO DIMM
	Serial Number: NO DIMM
	Asset Tag: NO DIMM
	Part Number: NO DIMM

Handle 0x001E, DMI type 19, 15 bytes
Memory Array Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x0003FFFFFFF
	Range Size: 1 GB
	Physical Array Handle: 0x0017
	Partition Width: 0

Handle 0x001F, DMI type 187, 9 bytes
OEM-specific Type
	Header and Data:
		BB 09 1F 00 18 00 03 9B 02

Handle 0x0020, DMI type 187, 9 bytes
OEM-specific Type
	Header and Data:
		BB 09 20 00 1B 00 03 9B 02

Handle 0x0021, DMI type 136, 6 bytes
OEM-specific Type
	Header and Data:
		88 06 21 00 5A 5A

Handle 0xFEFF, DMI type 127, 4 bytes
End Of Table

Re: Machine reboot

[Arjan van de Ven]

> For i965 chipsets, the BIOS is *a lot* buggy :(

have you run the Linux firmware test kit on it?

see http://www.linuxfirmwarekit.org

Re: Machine reboot

[Lukas Hejtmanek]

On Fri, Oct 13, 2006 at 07:36:01AM -0700, Auke Kok wrote:
> >It's not an issue in the Linux kernel. Using various printk I can see that
> >tripple fault or reset via KBD is issued and followed by hang of the BIOS. 
> >
> >For i965 chipsets, the BIOS is *a lot* buggy :(
> 
> that's depressing, can you send me the output of `dmidecode` of the latest 
> BIOS? Perhaps I can reproduce it myself with that version.

Good news, as of kernel 2.6.19-rc1-git9, BIOS does *not* hang with both e1000 as
module or built in kernel.

The previous version of kernel was 2.6.18 which hangs the BIOS.

Aleksey:
are you sure that it is not the same in your case? Did you not switch kernel
version between e1000 as a module and built in kernel?

-- 
Lukáš Hejtmánek

Re: Machine reboot

[Lukas Hejtmanek]

On Fri, Oct 13, 2006 at 05:30:36PM +0200, Arjan van de Ven wrote:
> 
> > For i965 chipsets, the BIOS is *a lot* buggy :(
> 
> have you run the Linux firmware test kit on it?
> 
> see http://www.linuxfirmwarekit.org

I did. It complains about EDD as fatal error, some warnings about ACPI and
MMCONFIG, otherwise it says passed.

However, I suspect another BIOS bug:
ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not
present [20060707]
ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not
present [20060707]

(BIOS announces 4 processors while 1 dual core is present).

-- 
Lukáš Hejtmánek

Re: Machine reboot

[Aleksey Gorelov]

--- Lukas Hejtmanek <xhejtman@mail.muni.cz> wrote:

> On Fri, Oct 13, 2006 at 07:36:01AM -0700, Auke Kok wrote:
> > >It's not an issue in the Linux kernel. Using various printk I can see that
> > >tripple fault or reset via KBD is issued and followed by hang of the BIOS. 
> > >
> > >For i965 chipsets, the BIOS is *a lot* buggy :(
> > 
> > that's depressing, can you send me the output of `dmidecode` of the latest 
> > BIOS? Perhaps I can reproduce it myself with that version.
> 
> Good news, as of kernel 2.6.19-rc1-git9, BIOS does *not* hang with both e1000 as
> module or built in kernel.
> 
> The previous version of kernel was 2.6.18 which hangs the BIOS.
> 
> Aleksey:
> are you sure that it is not the same in your case? Did you not switch kernel
> version between e1000 as a module and built in kernel?

  As far as I understand, you've udpated the whole kernel, not just the driver. I've tried using
driver from 2.6.19-rc2 as well as v7.2.9 from Intel's website - same story - still no reboot. Did
you try just updating driver (without whole kernel) ? 

Aleks.

Re: Machine reboot

[Aleksey Gorelov]

--- Auke Kok <auke-jan.h.kok@intel.com> wrote:

>
> >> 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.
It's not the problem at all, but served as a hint for me to try unloading driver.
However, from latest Lukas's findings, it seems that something (_not_ in the e1000 driver) in
between 2.6.18 & 2.6.19-rc2 fixes it. 

Aleks.

Re: Machine reboot

[Lukas Hejtmanek]

On Fri, Oct 13, 2006 at 01:27:52PM -0700, Aleksey Gorelov wrote:
> It's not the problem at all, but served as a hint for me to try unloading driver.
> However, from latest Lukas's findings, it seems that something (_not_ in the e1000 driver) in
> between 2.6.18 & 2.6.19-rc2 fixes it. 

Does 2.6.19-rc1 work for you? Both with module and built in e1000 driver?

-- 
Lukáš Hejtmánek

Re: Machine reboot

[Aleksey Gorelov]

--- Lukas Hejtmanek <xhejtman@mail.muni.cz> wrote:

> On Fri, Oct 13, 2006 at 01:27:52PM -0700, Aleksey Gorelov wrote:
> > It's not the problem at all, but served as a hint for me to try unloading driver.
> > However, from latest Lukas's findings, it seems that something (_not_ in the e1000 driver) in
> > between 2.6.18 & 2.6.19-rc2 fixes it. 
> 
> Does 2.6.19-rc1 work for you? Both with module and built in e1000 driver?
> 
  I did not try that yet. But it looks like another person on the list just complained about
reboot issue on Intel 965 with 2.6.18, .19-rc1, and .19-rc2...

Aleks.

Re: Machine reboot

[Lukas Hejtmanek]

On Fri, Oct 13, 2006 at 01:22:24PM -0700, Aleksey Gorelov wrote:
> > Good news, as of kernel 2.6.19-rc1-git9, BIOS does *not* hang with both e1000 as
> > module or built in kernel.
> > 
> > The previous version of kernel was 2.6.18 which hangs the BIOS.
> > 
> > Aleksey:
> > are you sure that it is not the same in your case? Did you not switch kernel
> > version between e1000 as a module and built in kernel?
> 
> As far as I understand, you've udpated the whole kernel, not just the
> driver. I've tried using  driver from 2.6.19-rc2 as well as v7.2.9 from 
> Intel's website - same story - still no reboot. Did you try just updating 
> driver (without whole kernel) ? 

I've rechecked behaviour of e1000 driver. For me, it looks like this:

2.6.18 (vanilla): e1000 as a module - system reboots OK.
                  e1000 built in    - system hangs after KBD reset or tripple
		                      fault

2.6.19-rc1-git9 (vanilla): e1000 as a module - system reboots OK.
                           e1000 built in    - system reboots OK.

-- 
Lukáš Hejtmánek

Re: Machine reboot

[Aleksey Gorelov]

--- Auke Kok <auke-jan.h.kok@intel.com> wrote:

> > 
> > For i965 chipsets, the BIOS is *a lot* buggy :(
> 
> that's depressing, can you send me the output of `dmidecode` of the latest BIOS? Perhaps 
> I can reproduce it myself with that version.
> 
Hi, Auke

 It looks like the reason for reboot failure is unability of BIOS to reboot if network pci device
is in D3 state. Once I've added 
 	pci_set_power_state(pdev, PCI_D0);
as a last line to e1000_shutdown() method, board started rebooting again.
Moreover, here is what I found in release notes to the latest BIOS (from October 5, 2006):
"Fixed an issue where system not able to shutdown to S5 if the LAN is set to D3 mode."
This may have affected reboot with LAN in D3 negatively.
  I guess you are in the best position of all of us to bring the issue to Intel BIOS team. 

Aleks.
   

Re: Machine reboot

[Lukas Hejtmanek]

On Fri, Oct 13, 2006 at 04:22:48PM -0700, Aleksey Gorelov wrote:
>  It looks like the reason for reboot failure is unability of BIOS to reboot if network pci device
> is in D3 state. Once I've added 
>  	pci_set_power_state(pdev, PCI_D0);
> as a last line to e1000_shutdown() method, board started rebooting again.
> Moreover, here is what I found in release notes to the latest BIOS (from October 5, 2006):
> "Fixed an issue where system not able to shutdown to S5 if the LAN is set to D3 mode."
> This may have affected reboot with LAN in D3 negatively.
>   I guess you are in the best position of all of us to bring the issue to Intel BIOS team. 

The fixed shutdown to S5 is present in latest BIOS version only.
However, the bug has been present since 1162 BIOS version.    

-- 
Lukáš Hejtmánek