Sachin Sant writes:
>>> The problem was introduced in 6.4.0-rc7-next-20230619. I tried git bisect,
>>> but unsure of the
>>> result reported by it. Bisect points to following patch
>>>
>>> # git bisect bad
>>> 70c94cc2eefd4f98d222834cbe7512804977c2d4 is the first bad commit
>>> commit 70c94cc2ee
>> The problem was introduced in 6.4.0-rc7-next-20230619. I tried git bisect,
>> but unsure of the
>> result reported by it. Bisect points to following patch
>>
>> # git bisect bad
>> 70c94cc2eefd4f98d222834cbe7512804977c2d4 is the first bad commit
>> commit 70c94cc2eefd4f98d222834cbe7512804977
Sachin Sant writes:
> 6.4.0-rc7-next-20230620 fails to boot on IBM Power LPAR with following
>
> [ 5.548368] BUG: Unable to handle kernel data access at 0x95bdcf954bc34e73
> [ 5.548380] Faulting instruction address: 0xc0548090
> [ 5.548384] Oops: Kernel access of bad area, sig: 11 [#1]
> [
On Tue, Jun 20, 2023 at 05:41:57PM +0530, Sachin Sant wrote:
> 6.4.0-rc7-next-20230620 fails to boot on IBM Power LPAR with following
Sorry for hijacking this thread -- I've been seeing another crash on
NV since -rc1 but I haven't had the time to bisect. Just FYI.
[0.814500] BUG: Unable to ha
6.4.0-rc7-next-20230620 fails to boot on IBM Power LPAR with following
[ 5.548368] BUG: Unable to handle kernel data access at 0x95bdcf954bc34e73
[ 5.548380] Faulting instruction address: 0xc0548090
[ 5.548384] Oops: Kernel access of bad area, sig: 11 [#1]
[ 5.548387] LE PAGE_SIZE=64K MMU=
