|
Re: 6.3.2 hangs on boot unless USB disabled
|
03/10/2008 9:06 PM
post5673
|
Re: 6.3.2 hangs on boot unless USB disabled
When I boot the 6.3.2 CD I never get the chance to press the spacebar. I'm not sure what this means, but could it be
the issue in 6.3.2 occurs in startup before diskboot runs?
|
|
|
|
Re: 6.3.2 hangs on boot unless USB disabled
|
03/11/2008 6:13 AM
post5674
|
Re: 6.3.2 hangs on boot unless USB disabled
> I'm not sure how much good a 'pci -vvv' will be since the USB controller would
> have to be disabled to boot.
>
> Here is what happens when booting the 6.3.0 CD with the USB enabled in the
> BIOS:
>
> Hit 'space' bar
> F11 (Enumerator disables)
> F4 F5 (Disable the usb enumerator, disable detection for disk controllers
> other than IDE)
> Enter
> F6 (Be Verbose)
> Starting slogger -s32 -l /dev/text
> Starting seedres
> Starting pci-bios
> Range check failed (IO) - Dev 2937 - Vend 8086 - Class c0300 - Addr ff20 -
> Size 20
> Range check failed (IO) - Dev 2938 - Vend 8086 - Class c0300 - Addr ff00 -
> Size 20
> Range check failed (IO) - Dev 2934 - Vend 8086 - Class c0300 - Addr ff80 -
> Size 20
> Range check failed (IO) - Dev 2935 - Vend 8086 - Class c0300 - Addr ff60 -
> Size 20
> Range check failed (IO) - Dev 2936 - Vend 8086 - Class c0300 - Addr ff40 -
> Size 20
> Range check failed (IO) - Dev 2920 - Vend 8086 - Class 1018a - Addr 1f0 - Size
> 8 0
> Range check failed (IO) - Dev 2920 - Vend 8086 - Class 1018a - Addr 170 - Size
> 8 0
>
> System is now hung
The pci expert may correct this:
---
The PCI server code allocates one byte low of PCI memory and one byte high of PCI memory. It keeps these values as the
range of low and high PCI memory. It does the same for I/O space. The server then scans all devices in PCI space and
checks the I/O and memory ranges for each device against the stored range values to see whether they are valid or not.
The is where the "Range check failed" message comes into place.
If a range check fails, the device is placed in the disabled state and is initialized when an application does a
pci_attach_device() function call.
The PCI server code is standard across all platforms and only the low-level, hardware specific portion changes, so there
is a generic portion to all the drivers.
----
> System is now hung
IMHO this is because io-usb is started from diskboot.
Jeevan
|
|
|