On Sep 12 2023, Liam R. Howlett wrote:
> * Andreas Schwab [230912 14:15]:
>> Any news? This is still broken.
>
> I have a proposed fix. I seem to have caused a pre-existing problem to
> show up. Please see if the attached works for you, and I'll send it
> to a lot of people.
Thanks, it fixes
* Andreas Schwab [230912 14:15]:
> Any news? This is still broken.
I have a proposed fix. I seem to have caused a pre-existing problem to
show up. Please see if the attached works for you, and I'll send it
to a lot of people.
Thanks,
Liam
>From 9ef8f834bb0342dc26464b9dd0165929d3e6a7e5 Mon
Any news? This is still broken.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
On Aug 31 2023, Michael Ellerman wrote:
> Andreas Schwab writes:
>> This breaks booting on ppc32:
>
> Does enabling CONFIG_DEBUG_ATOMIC_SLEEP fix the crash?
Yes, it does.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now
Andreas Schwab writes:
> This breaks booting on ppc32:
Does enabling CONFIG_DEBUG_ATOMIC_SLEEP fix the crash? It did for me on
qemu.
cheers
> Kernel attemptd to writ user page (1ff0) - exploit attempt? (uid: 0)
> BUG: Unable to handle kernel data access on write at 0x1ff0
> Faulting
This breaks booting on ppc32:
Kernel attemptd to writ user page (1ff0) - exploit attempt? (uid: 0)
BUG: Unable to handle kernel data access on write at 0x1ff0
Faulting instruction address: 0xc0009554
Vector: 300 (Data Access) at [c0b09d10]
pc: c0009554: do_softirq_own_stack+0x18/0x30
