If we've encountered unrecognized chipset don't access hardware
anymore. Previously it tried to access interrupt register to disable interrupts which could result in hang if the hardware was not properly initialized by system BIOS/ACPI. Tested by: Benjamin Hansmann (benjamin.hansmann AT rub dot de) MFC after: 3 days
This commit is contained in:
parent
f13a826083
commit
ad6d01d151
@ -1579,8 +1579,8 @@ mskc_attach(device_t dev)
|
||||
sc->msk_hw_id > CHIP_ID_YUKON_FE) {
|
||||
device_printf(dev, "unknown device: id=0x%02x, rev=0x%02x\n",
|
||||
sc->msk_hw_id, sc->msk_hw_rev);
|
||||
error = ENXIO;
|
||||
goto fail;
|
||||
mtx_destroy(&sc->msk_mtx);
|
||||
return (ENXIO);
|
||||
}
|
||||
|
||||
SYSCTL_ADD_PROC(device_get_sysctl_ctx(dev),
|
||||
|
Loading…
Reference in New Issue
Block a user