Page MenuHomeFreeBSD

physmem: Move the ram0 device earlier in the boot
ClosedPublic

Authored by andrew on Jan 31 2025, 3:12 PM.
Tags
None
Referenced Files
F111868942: D48766.id150456.diff
Sun, Mar 9, 2:05 PM
Unknown Object (File)
Sun, Feb 23, 12:37 AM
Unknown Object (File)
Thu, Feb 20, 8:17 AM
Unknown Object (File)
Fri, Feb 14, 11:26 PM
Unknown Object (File)
Tue, Feb 11, 5:56 PM
Unknown Object (File)
Tue, Feb 11, 12:44 PM
Unknown Object (File)
Sun, Feb 9, 10:15 PM
Unknown Object (File)
Sat, Feb 8, 10:26 PM
Subscribers

Details

Summary

If the ram driver is unable to reserve a memory range it will panic
with no real information why. Move this driver earlier in the boot so
any devices that cause the conflict will fail to attach.

This should make it easier to debug why the conflict exists.

Sponsored by: Arm Ltd

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision is now accepted and ready to land.Jan 31 2025, 3:16 PM

Yes, this is smarter.

I kind of regret adding this thing. Although it is conceptually helpful/correct, its positive practical impact has so far been zero, while it has created several headaches.

Yes, this is smarter.

I kind of regret adding this thing. Although it is conceptually helpful/correct, its positive practical impact has so far been zero, while it has created several headaches.

Meh, it'll turn its life around- more failure to attach because of it rather than panicking will trend it back towards positive practical impact and fewer headaches, and it's a pretty small diff to get there.