Re: UML failing at "Failed to initialize default registers" on kernel 5.10

2025-01-20 Thread Glenn Washburn
On Mon, 20 Jan 2025 10:56:36 +0100 Benjamin Berg wrote: > On Mon, 2025-01-20 at 07:07 +0100, Thomas Meyer wrote: > > > > > > Am 20. Januar 2025 00:25:35 MEZ schrieb Glenn Washburn > > : > > > Hi Benjamin, > > > > > > After applying the close_range patch, I'm now getting a failure at > > > runt

Re: UML failing at "Failed to initialize default registers" on kernel 5.10

2025-01-20 Thread Benjamin Berg
On Mon, 2025-01-20 at 07:07 +0100, Thomas Meyer wrote: > > > Am 20. Januar 2025 00:25:35 MEZ schrieb Glenn Washburn > : > > Hi Benjamin, > > > > After applying the close_range patch, I'm now getting a failure at > > runtime where the last line printed from UML is "Failed to > > initialize > > de

Re: UML failing at "Failed to initialize default registers" on kernel 5.10

2025-01-19 Thread Thomas Meyer
Am 20. Januar 2025 00:25:35 MEZ schrieb Glenn Washburn : >Hi Benjamin, > >After applying the close_range patch, I'm now getting a failure at >runtime where the last line printed from UML is "Failed to initialize >default registers". The host is on Debian 11 at kernel 5.10.216. I've >bisected th

UML failing at "Failed to initialize default registers" on kernel 5.10

2025-01-19 Thread Glenn Washburn
Hi Benjamin, After applying the close_range patch, I'm now getting a failure at runtime where the last line printed from UML is "Failed to initialize default registers". The host is on Debian 11 at kernel 5.10.216. I've bisected the issue and it looks like the bad commit is: 3f17fed2149 ("um: swit