Robert Mustacchi
👤 PersonAppearances Over Time
Podcast Appearances
Yeah, I think this is actually where, you know, I think the big thing is, you know, there's a lot of fights between what's being done by the OS and what's being done by the BMC in those systems. Because basically the BMC is basically where there's a whole bunch of value add from the vendor for varying degrees of value.
Yeah, I think this is actually where, you know, I think the big thing is, you know, there's a lot of fights between what's being done by the OS and what's being done by the BMC in those systems. Because basically the BMC is basically where there's a whole bunch of value add from the vendor for varying degrees of value.
Yeah. Just the features of that, the out of building had were challenging.
Yeah. Just the features of that, the out of building had were challenging.
Just totally divorced from reality. And it's gotten slightly better than when it first came out as an empty schema. But yeah, as I'm trying to look through this to see some of the other things, like obviously some of the classics, dealing with firmware, you know, the different kind of architectural challenges we had there.
Just totally divorced from reality. And it's gotten slightly better than when it first came out as an empty schema. But yeah, as I'm trying to look through this to see some of the other things, like obviously some of the classics, dealing with firmware, you know, the different kind of architectural challenges we had there.
We actually were thinking about how do we eliminate the BIOS in UEFI and basically just do a small, basically let the bootloader take care of a whole bunch of stuff. That for us was IPXI at the time. So it's just like, how do we basically just get out of these different layers that are differently broken?
We actually were thinking about how do we eliminate the BIOS in UEFI and basically just do a small, basically let the bootloader take care of a whole bunch of stuff. That for us was IPXI at the time. So it's just like, how do we basically just get out of these different layers that are differently broken?
I think this is during the, as we were writing this, this is one of those times where we had, I think it was like a, oh, like a Dell, maybe like Haswell era server. And after we typed reboot, it would just hang in the BIOS. Like, after we, you know, like, we just reboot, like... And it would only happen on a warm reboot. And there's a lot of back and forth of being like, well, it's your fault.
I think this is during the, as we were writing this, this is one of those times where we had, I think it was like a, oh, like a Dell, maybe like Haswell era server. And after we typed reboot, it would just hang in the BIOS. Like, after we, you know, like, we just reboot, like... And it would only happen on a warm reboot. And there's a lot of back and forth of being like, well, it's your fault.
You know, don't tell us this. And it's like, and you're trying to like, you know, some of us would say it less politely. You know, I think, you know, this is where we had good cop, bad cop, and psycho cop. But it's like, hey, the BIOS has just like erased all of our program text. And it's taken over. And its job is to restore it from an arbitrary state. So how exactly is it our fault?
You know, don't tell us this. And it's like, and you're trying to like, you know, some of us would say it less politely. You know, I think, you know, this is where we had good cop, bad cop, and psycho cop. But it's like, hey, the BIOS has just like erased all of our program text. And it's taken over. And its job is to restore it from an arbitrary state. So how exactly is it our fault?
But actually, that in and of itself is a lesson as to one of the things that we actually did in Oxide, which is getting rid of two different reboot paths to actually simplify the system and streamline
But actually, that in and of itself is a lesson as to one of the things that we actually did in Oxide, which is getting rid of two different reboot paths to actually simplify the system and streamline
streamline things so that is you know in a standard system if you type reboot it's not going to do a full post it's not going to go reset everything ufi is going to kind of be clever and or the real reality is the cpu actually isn't going to erase everything so even if you reassert the reset line if you're in this acpi s5 state there's a whole bunch of state that stays across that so
streamline things so that is you know in a standard system if you type reboot it's not going to do a full post it's not going to go reset everything ufi is going to kind of be clever and or the real reality is the cpu actually isn't going to erase everything so even if you reassert the reset line if you're in this acpi s5 state there's a whole bunch of state that stays across that so
That all of a sudden means there's two different initialization paths. Some of this data you'll see in some of these data sheets described as being in certain power wells or as sticky across resets. And so we're just like,
That all of a sudden means there's two different initialization paths. Some of this data you'll see in some of these data sheets described as being in certain power wells or as sticky across resets. And so we're just like,
have none of that let's let's kill all power and that actually made it easier for us to build a more reliable system with actually less uh you know with less code pads to actually think about because we can actually say there is no worm reset there is no way there then at the end of the day what that means for customers is that hey it works more reliably more of the time because a lot of the challenges here is that you have all these different code paths and
have none of that let's let's kill all power and that actually made it easier for us to build a more reliable system with actually less uh you know with less code pads to actually think about because we can actually say there is no worm reset there is no way there then at the end of the day what that means for customers is that hey it works more reliably more of the time because a lot of the challenges here is that you have all these different code paths and