Bootloader really does not dig us out properly.

Date: 2012-03-18 10:03 pm (UTC)
From: (Anonymous)
There is a reason. We need a boot option that will do what you did on systems that are problem. Leave the boot services memory alone until we know what is causing trouble.

Next is lock the boot services memory until after the kernel knows it has passed a safe point in init that should have caught up with rogues normally by reseting everything that can be. To reset a card you don't need its firmware thank you pci spec. Once the card is reset it will forget all dma transfers it had been requested todo.

Remember after resetting everything most likely will lose like the EFI provided file-system driver and other things as well. So when you do the reset you better not need anything EFI is providing.

Reason for this way what comes to my mind is firmware updates so cure one driver get a new problem driver.

So the wifi driver is still on what other dma transfers are still on we don't exactly know. This is why I see the flush everything point is the only way. Really there is no reason why the Linux kernel could not be altered to be directly loaded by EFI.
From:
Anonymous
OpenID
Identity URL: 
User
Account name:
Password:
If you don't have an account you can create one now.
Subject:
HTML doesn't work in the subject.

Message:

If you are unable to use this captcha for any reason, please contact us by email at support@dreamwidth.org


 
Notice: This account is set to log the IP addresses of everyone who comments.
Links will be displayed as unclickable URLs to help prevent spam.

Profile

Matthew Garrett

About Matthew

Power management, mobile and firmware developer on Linux. Security developer at Nebula. Ex-biologist. @mjg59 on Twitter. Content here should not be interpreted as the opinion of my employer.

Expand Cut Tags

No cut tags