Hello John,
I'll work on this bug. I'll update my findings here in this bug thread.
Currently, I have checked that on p9 this image is working fine with
kernel > 6.8. I'll work on p8 issue.
Thanks and regards
Aditi
On Tue, 22 Oct 2024 12:37:13 +0200 John Paul Adria
Hello John,
I'm working on this bug. Surperisingly, on p9 this image is working fine
with kernel > 6.8. Looking into p8 issue.
I'll update regarding this ASP.
Thanks and regards
Aditi
On Tue, 22 Oct 2024 12:37:13 +0200 John Paul Adrian Glaubitz
wrote:
> Hello,
>
>
Hello John,
I'll work on this bug. I'll update my findings here in this bug thread.
Currently, I have checked that on p9 this image is working fine with
kernel > 6.8. I'll work on p8 issue.
Thanks and regards
Aditi
On Wed, 23 Oct 2024 15:57:13 +0200 John Paul Adria
Hello,
On Tue, 2024-10-22 at 12:37 +0200, John Paul Adrian Glaubitz wrote:
> I have reopened this bug as this problem even shows on ppc64el again
> with the latest netinst daily build downloaded from [1]. I have tested
> the image on an IBM 8247-42L inside a PowerKVM virtual machine.
Here is a sh
Hello,
I have reopened this bug as this problem even shows on ppc64el again
with the latest netinst daily build downloaded from [1]. I have tested
the image on an IBM 8247-42L inside a PowerKVM virtual machine.
Removing the patch again fixes the problem for me. However, at least on
big-endian ppc
Pierre,
I actually tried to check for this kernel bug (OOPS) on the latest
vanilla kernel and I wasn't able to reproduce it (with my test
powerpc64 lpar), so let me manually update kernel on gcc203 to the
latest vanilla stable (something like v6.12-rc4), up until more recent
debian sid/uns
Hi Dave,
On Fri, 2024-08-16 at 11:17 -0400, Dave Vasilevsky wrote:
> > Could you verify that this change actually fixes the problem? This would
> > save me some work.
>
> Verified with PPC qemu. I fail to boot with "You can’t boot a kdump kernel
> from OF" wit
> Could you verify that this change actually fixes the problem? This would
save me some work.
Verified with PPC qemu. I fail to boot with "You can’t boot a kdump kernel
from OF" with CONFIG_CRASH_DUMP on, and I boot fine with it disabled.
Details:
* Tested against the Debian 6.10.
Hello
I have upgraded one of my bookworm PPC system from
linux-image-6.1.0-21-powerpc64le to linux-image-6.1.0-23-powerpc64le
This is a 8335-GCA POWER8 machine.
With this new kernel I got the following crash:
8.164930] Kernel attempted to read user page (0) - exploit attempt? (uid: 0
, 2024, at 5:09 PM, Reimar Döffinger
>>>> wrote:
>>>>
>>>> Hi!
>>>> The newest 6.9 powerpc kernel build seems to be incompatible with
>>>> OpenFirmware boot,
>>>> so boot fails on my PowerPC macMini.
>>&g
> On 6 Jul 2024, at 18:18, John Paul Adrian Glaubitz
> wrote:
>
> Hi Reimar,
>
>> On Jul 6, 2024, at 5:45 PM, Reimar Döffinger
>> wrote:
>>
>>> Could you verify that this change actually fixes the problem? This would
>>> save me some
t;
>>>> Could you verify that this change actually fixes the problem? This would
>>>> save me some work.
>>>
>>> I checked the kernel source, the error message is under a if
>>> (PHYSICAL_START > 0), so that I am quite certain is the issue.
Hi Reimar,
> On Jul 6, 2024, at 5:45 PM, Reimar Döffinger wrote:
>
>> Could you verify that this change actually fixes the problem? This would
>> save me some work.
>
> I checked the kernel source, the error message is under a if (PHYSICAL_START
> > 0), so
> On 6 Jul 2024, at 17:26, Reimar Döffinger wrote:
>
>
>> On 6 Jul 2024, at 17:17, John Paul Adrian Glaubitz
>> wrote:
>>
>> Hi Reimar,
>>
>>> On Jul 6, 2024, at 5:09 PM, Reimar Döffinger
>>> wrote:
>>>
>>>
> On 6 Jul 2024, at 17:17, John Paul Adrian Glaubitz
> wrote:
>
> Hi Reimar,
>
>> On Jul 6, 2024, at 5:09 PM, Reimar Döffinger
>> wrote:
>>
>> Hi!
>> The newest 6.9 powerpc kernel build seems to be incompatible with
>> OpenFirmware b
Hi Reimar,
> On Jul 6, 2024, at 5:09 PM, Reimar Döffinger wrote:
>
> Hi!
> The newest 6.9 powerpc kernel build seems to be incompatible with
> OpenFirmware boot,
> so boot fails on my PowerPC macMini.
> The error message is
> "Error: You can't boot a kdump ke
Hi!
The newest 6.9 powerpc kernel build seems to be incompatible with OpenFirmware
boot,
so boot fails on my PowerPC macMini.
The error message is
"Error: You can't boot a kdump kernel from OF!"
The error message seems not entirely accurate, it seems the issue is that
CONFIG_PHYSI
On my PowerBook G4 which is quite similar, everything works regarding
the screen.
So not just "something latest" in the kernel nor it is a specific
hardware error of your computer.
Although it almost never work on boot, the amount of "increase
brightness" one needs to g
4" and it works. Boot messages, console and
> X11 (but read below).
As mentioned in the bug report, it's the internal connector, i.e. the LCD.
> What happens is that perhaps you see the kernel booting, but then loose
> the "login" and have a black screen (but you can type
Hi Adrian,
John Paul Adrian Glaubitz wrote:
just as a heads-up: I'm not getting a video signal with my iBook G4 with
the latest kernel. dmesg shows error messages that seem to be related to
the problem:
[ 14.222735] radeon :00:10.0: [drm] bpp/depth value of 16/16 not supp
Hello,
just as a heads-up: I'm not getting a video signal with my iBook G4 with
the latest kernel. dmesg shows error messages that seem to be related to
the problem:
[ 14.222735] radeon :00:10.0: [drm] bpp/depth value of 16/16 not supported
[ 14.222774] radeon :00:10.0: [drm
te -> upgrade on my Power Mac G4 and noticed
>> that it provides the new kernel version 6.5.0-2 .
>
> That's not the kernel version, but the ABI version of the kernel.
>
> The kernel version is 6.5.6 and the version of the kernel package is 6.5.6-1.
>
>> This ap
Hi Rick!
On Wed, 2023-10-11 at 01:20 -0700, Rick Thomas wrote:
> I just did an update -> upgrade on my Power Mac G4 and noticed
> that it provides the new kernel version 6.5.0-2 .
That's not the kernel version, but the ABI version of the kernel.
The kernel version is 6.5.6 and
Wow!
I just did an update -> upgrade on my Power Mac G4 and noticed that it provides
the new kernel version 6.5.0-2 .
This appears to have fixed the panic-on-boot bug in version 6.5.0-1 .
Big thanks for all your efforts!
Rick
Hi Adrian,
On 10/1/23 2:31 PM, John Paul Adrian Glaubitz wrote:
> ...
> You can build a kernel with Debian's configuration. You just have to disable
> the kernel config options CONFIG_SYSTEM_TRUSTED_KEY and CONFIG_MODULE_SIG_KEY.
> ...
I think the problem with the references to
On Sun, 2023-10-01 at 12:56 -0600, Stan Johnson wrote:
> On a PowerMac G4 MDD (2 CPUs, 2 GiB), I tested the following stock
> kernels with a current Debian SID installation:
>
> v6.5 : smp works, non-smp crashes (oops panic)
> v6.6-rc3 : smp works, non-smp works
>
> Since th
On 9/28/23 2:38 AM, Dan Whitehouse wrote:
> Hi all,
> I am seeing a kernel panic on my PowerMac3,1 MacRISC Power Macintosh
> running debian with kernel 6.5.0-1.
>
> It seems to be working well with:
>
> Linux powermac-g4 6.4.0-4-powerpc #1 Debian 6.4.13-1 (2023-08-31) p
> On Sep 30, 2023, at 4:25 PM, DistroHopper39B Business
> wrote:
>
>
> This patch worked for me. I have a successful 6.5.3 built and running on my
> PowerBook G4 (with CONFIG_KFENCE=y as well).
Please report that back to the patch author.
Use the Tested-by tag. [1]
Adrian
> [1] https://
This patch worked for me. I have a successful 6.5.3 built and running on my
PowerBook G4 (with CONFIG_KFENCE=y as well).
On Sat, Sep 30, 2023 at 7:57 AM Dan Whitehouse wrote:
> After following Adrians advice and contacting the kernel devs I received
> the following response:
>
>
After following Adrians advice and contacting the kernel devs I received the
following response:
https://lore.kernel.org/linuxppc-dev/2d5d9c82-427e-9384-3ffe-fddf6e1d4...@csgroup.eu/
I've not tried rebuilding yet, but maybe this is worth trying.
Thanks,
Dan
> On 30 Sep 2023,
I rebuilt the kernel with CONFIG_KFENCE=n and the kernel panic persists
(same error). I used the source from the linux-source-6.5 package in Debian
sid.
On 9/28/23 2:38 AM, Dan Whitehouse wrote:
> Hi all,
> I am seeing a kernel panic on my PowerMac3,1 MacRISC Power Macintosh
> running debian with kernel 6.5.0-1.
>
> It seems to be working well with:
>
> Linux powermac-g4 6.4.0-4-powerpc #1 Debian 6.4.13-1 (2023-08-31) p
has this
> issue; both those kernels boot fine, so it’s not an upstream issue.
I wouldn't rule out that it's not an upstream issue. Could be that it's
triggered
by kernel configuration option that the Debian kernel has set but the kernel
built
by ArchPOWER hasn't.
Adri
000 9421f
> > e0 7c0802a6 3d20c141 93e1001c 90010024 83e9c294 <943f1ff0> 7fe1fb78
> 48b24909 80
> > 1
> > 0.00] ---[ end trace ]---
> > 0.00]
> > 0.00] Kernel panic - not syncing: Attempted to kill the idle
> task!
> >
; 0.00] Code: 7d2a01a4 4c00012c 4b28 7c0802a6 90010004 6000
> 9421f
> e0 7c0802a6 3d20c141 93e1001c 90010024 83e9c294 <943f1ff0> 7fe1fb78 48b24909
> 80
> 10000
> 0.00] ---[ end trace ]---
> 0.00]
> 0.00] Kernel pan
trace ]---
0.00]
0.00] Kernel panic - not syncing: Attempted to kill the idle task!
0.00] ---[ end Kernel panic - not syncing: Attempted to kill the idle t
ask! ]---
--
Dan Whitehouse
GPG: 3AA4 369C 86E1 4939 D420 AB25 D0DC 7BDD CA92 AD2E
Telephone: +44(0)203 0955088
Hi all,
I am seeing a kernel panic on my PowerMac3,1 MacRISC Power Macintosh
running debian with kernel 6.5.0-1.
It seems to be working well with:
Linux powermac-g4 6.4.0-4-powerpc #1 Debian 6.4.13-1 (2023-08-31) ppc
GNU/Linux
I have a photo of the panic screen which I can attach if useful
Hello!
On Sun, 2023-05-07 at 20:54 -0400, Ben Westover wrote:
> When I ran apt upgrade on my iMac G3, the kernel and GRUB packages
> failed to configure. The step that failed in each case was update-grub
> or grub-install, which failed when trying to write to the /boot/grub HFS
&g
Hello,
On 5/7/23 10:15 PM, Paul Wise wrote:
Possibly the filesystem is damaged, I suggest you check dmesg for
errors when mounting it read-write and check the filesystem using the
fsck tool from the hfsprogs package in your live environment.
Yep, you were right. If I had just checked dmesg, I
Hi Bob,
On 5/7/23 9:40 PM, Bob McGowan wrote:
I would suggest you run an fsck on the filesystem and see if there are
any problems.
Filesystems may be considered "required" for the system to function and
be mounted read-only when problems are detected, to prevent further
problems from develop
Possibly the filesystem is damaged, I suggest you check dmesg for
errors when mounting it read-write and check the filesystem using the
fsck tool from the hfsprogs package in your live environment.
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally sig
Bob
On 5/7/23 05:54 PM, Ben Westover wrote:
Hello,
When I ran apt upgrade on my iMac G3, the kernel and GRUB packages
failed to configure. The step that failed in each case was update-grub
or grub-install, which failed when trying to write to the /boot/grub
HFS partition because it'
Hello,
When I ran apt upgrade on my iMac G3, the kernel and GRUB packages
failed to configure. The step that failed in each case was update-grub
or grub-install, which failed when trying to write to the /boot/grub HFS
partition because it's a "Read-only filesystem."
Investiga
Hi Adrian!
* John Paul Adrian Glaubitz [2022-03-15 08:44
+0100]:
> Hi Elimar!
>
> On 1/19/22 14:35, Elimar Riesebieter wrote:
> > kernel build fails on powerpc 32bit no matter what version is used
> > (5.14-5.16):
> >
> > {standard input}: Assembler messages:
Hi Elimar!
On 1/19/22 14:35, Elimar Riesebieter wrote:
> kernel build fails on powerpc 32bit no matter what version is used
> (5.14-5.16):
>
> {standard input}: Assembler messages:
> {standard input}:29: Error: unrecognized opcode: `dssall'
> make[5]: *** [scripts/M
Hello Mike!
On 1/30/22 20:47, Mike wrote:
> The behavior of binutils is probably correct. 'dssall' needs altivec and that
> was disabled for arch/powerpc/lib an mm etc
Of course, the behavior is correct. If you look at the binutils bug report I
filed
in this context, you see that it was closed
The behavior of binutils is probably correct. 'dssall' needs altivec and
that was disabled for arch/powerpc/lib an mm etc
-Mike
On Sun, Jan 30, 2022, 12:56 John Paul Adrian Glaubitz <
glaub...@physik.fu-berlin.de> wrote:
> Hello Mike!
>
> On 1/30/22 12:11, Mike wrote:
> > This works :
> https://
Hello Mike!
On 1/30/22 12:11, Mike wrote:
> This works :
> https://github.com/threader/linux/commit/226efa05733457bb5c483f30aab6d5c6a304422c,
> but in doing so I was allerted to 'lwsync' not being enabled on 32bit, and so
> will have to check
> out the assembly after enabled. So it works but I h
he same experience?
> >
> > No fix with binutils 2.37.90.20220123-2
>
> That's not surprising because the bug must be fixed on the kernel side,
> not binutils. See the explanation here [1].
>
> Adrian
>
> > [1] https://sourceware.org/bugzilla/show_bug.c
Hello Elimar!
On 1/29/22 14:56, Elimar Riesebieter wrote:
>> I assume the latest binutils (2.37.50.20220106-2) don't work
>> properly. Anyone made the same experience?
>
> No fix with binutils 2.37.90.20220123-2
That's not surprising because the bug must be f
* Elimar Riesebieter [2022-01-19 14:35 +0100]:
> Hi all,
>
> kernel build fails on powerpc 32bit no matter what version is used
> (5.14-5.16):
>
> {standard input}: Assembler messages:
> {standard input}:29: Error: unrecognized opcode: `dssall'
> make[5]: **
I just made the huge mistake of hibernating and resuming, I'm going trough
the process of rescue and all, thankfully I had a 2016 cd in the drive.
I'll read up once the sheer panic settles.
-Michael
On Wed, Jan 26, 2022, 21:22 John Paul Adrian Glaubitz <
glaub...@physik.fu-berlin.de> wrote:
> Hi
Hi Michael!
On 1/13/22 01:17, John Paul Adrian Glaubitz wrote:
> On 1/9/22 23:17, John Paul Adrian Glaubitz wrote:
>> On 1/7/22 12:20, John Paul Adrian Glaubitz wrote:
Can you separately test with (on the host):
# echo 0 > /sys/module/kvm_hv/parameters/dynamic_mt_modes
>>>
>>> I'm
I remembered something about 'lwsync' i read about it in 2013
suddenly, and came to the following proposal to deal with remove the
PPC64 requirement for BARRIER_LWSYNC, but i've literally really just
started poking about the kernel side of powerpc and reading around.
But i do remem
I've sent in a patch with my remaining concerns attached to the mailing
lists and set up a linux-next branch finally.
https://github.com/threader/linux/tree/master-build-ppc
In regards to asm/io.h:
---
Will there come a mail saying this broke the PPC6'ish based CPU
someone made in their garage? An
It should be just CONFIG_POWER6_CPU unless ppc64 also require this?iv
-Mike
On Sat, Jan 22, 2022, 10:36 Mike wrote:
> I think I need to add a || CONFIG_POWER6_CPU to that 'stbcix' condition..
>
> -Mike
>
>
>
> On Sat, Jan 22, 2022, 09:42 John Paul Adrian Glaubitz <
> glaub...@physik.fu-berlin.d
I think I need to add a || CONFIG_POWER6_CPU to that 'stbcix' condition..
-Mike
On Sat, Jan 22, 2022, 09:42 John Paul Adrian Glaubitz <
glaub...@physik.fu-berlin.de> wrote:
> Hello Mike!
>
> On 1/21/22 23:07, Mike wrote:
> > Waiting for git to do it's thing, but do we need a voodoo priest(es)
Hello Mike!
On 1/21/22 23:07, Mike wrote:
> Waiting for git to do it's thing, but do we need a voodoo priest(es)
> here? The attached patch is building.
I will have a look at this issue next week myself. We need to make sure
that it not only fixes 32-bit PowerPC but also 64-bit PowerPC big-endian
ry changing it to #ifdef CONFIG_PPC64? I'm building
> now.
>
> Michael
>
> On Thu, Jan 20, 2022, 10:05 John Paul Adrian Glaubitz
> wrote:
>>
>> Hi Mike!
>>
>> On 1/20/22 09:46, Mike wrote:
>> >> So, in order to fix this issue, someone needs
t;
> On 1/20/22 09:46, Mike wrote:
> >> So, in order to fix this issue, someone needs to update the kernel to
> work with the new binutils version.
> >
> > That's what the patch does, I did a full Debian kernel build, but I'm
> having trouble explaining myself
Wtf, I'll work it out in a smoke.
On Thu, Jan 20, 2022, 10:05 John Paul Adrian Glaubitz <
glaub...@physik.fu-berlin.de> wrote:
> Hi Mike!
>
> On 1/20/22 09:46, Mike wrote:
> >> So, in order to fix this issue, someone needs to update the kernel to
> wo
Hi Mike!
On 1/20/22 09:46, Mike wrote:
>> So, in order to fix this issue, someone needs to update the kernel to work
>> with the new binutils version.
>
> That's what the patch does, I did a full Debian kernel build, but I'm having
> trouble explaining myself wi
> So, in order to fix this issue, someone needs to update the kernel to
work with the new binutils version.
That's what the patch does, I did a full Debian kernel build, but I'm
having trouble explaining myself with my left hand.
On Thu, Jan 20, 2022, 09:41 Mike wrote:
> It did
7;t finalize
> > the patch according to suggestions, my finger broke.
>
> This is actually a more complex issue, in particular the assembler was
> changed on PowerPC when handling the .machine directive, see [1].
>
> So, in order to fix this issue, someone needs to update the
ive, see [1].
So, in order to fix this issue, someone needs to update the kernel to
work with the new binutils version.
Adrian
> [1] https://sourceware.org/bugzilla/show_bug.cgi?id=28794#c2
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `
ebian) 2.37.50.20220106
> gcc version 11.2.0 (Debian 11.2.0-13)
> ld.lld is missing but with LLVM/CLANG and LD=ld.bfd
> arch/powerpc/kernel/vdso32/gettimeofday.S:72:8:
> error: unsupported directive '.stabs'.stabs
> "_restgpr_31_x:F-1",36,0,0,_restgpr_31_x; .g
Hello!
On 1/19/22 14:35, Elimar Riesebieter wrote:
> kernel build fails on powerpc 32bit no matter what version is used
> (5.14-5.16):
>
> {standard input}: Assembler messages:
> {standard input}:29: Error: unrecognized opcode: `dssall'
> make[5]: *** [scripts/M
* Elimar Riesebieter [2022-01-19 17:02 +0100]:
> * Elimar Riesebieter [2022-01-19 14:35 +0100]:
>
> > Hi all,
> >
> > kernel build fails on powerpc 32bit no matter what version is used
> > (5.14-5.16):
> >
> > {standard input}: Assembler
Hi Elimar!
On 1/19/22 17:02, Elimar Riesebieter wrote:
>> kernel build fails on powerpc 32bit no matter what version is used
>> (5.14-5.16):
>>
>> {standard input}: Assembler messages:
>> {standard input}:29: Error: unrecognized opcode: `dssall'
>>
* Elimar Riesebieter [2022-01-19 14:35 +0100]:
> Hi all,
>
> kernel build fails on powerpc 32bit no matter what version is used
> (5.14-5.16):
>
> {standard input}: Assembler messages:
> {standard input}:29: Error: unrecognized opcode: `dssall'
> make[5]: **
Hi all,
kernel build fails on powerpc 32bit no matter what version is used
(5.14-5.16):
{standard input}: Assembler messages:
{standard input}:29: Error: unrecognized opcode: `dssall'
make[5]: *** [scripts/Makefile.build:271: arch/powerpc/mm/mmu_context.o]
Error 1
make[4]: *** [sc
Hi Michael!
On 1/9/22 23:17, John Paul Adrian Glaubitz wrote:
> On 1/7/22 12:20, John Paul Adrian Glaubitz wrote:
>>> Can you separately test with (on the host):
>>>
>>> # echo 0 > /sys/module/kvm_hv/parameters/dynamic_mt_modes
>>
>> I'm trying to turn off "dynamic_mt_modes" first and see if that
Hi Michael!
On 1/7/22 12:20, John Paul Adrian Glaubitz wrote:
>> Can you separately test with (on the host):
>>
>> # echo 0 > /sys/module/kvm_hv/parameters/dynamic_mt_modes
>
> I'm trying to turn off "dynamic_mt_modes" first and see if that makes any
> difference.
>
> I will report back.
So f
Hi Michael!
On 1/6/22 11:58, Michael Ellerman wrote:
>> We're currently running 5.15.x on the host system and the guests and the
>> testsuite
>> for gcc-9 still reproducibly kills the KVM host.
>
> Have you been able to try the different -smp options I suggested?
>
> Can you separately test wit
John Paul Adrian Glaubitz writes:
> Hi Michael!
>
> Sorry for the long time without any responses. Shall we continue debugging
> this?
Yes!
Sorry also that I haven't been able to fix it yet, I had to stop chasing
this bug and work on other things before the end of the year.
> We're currently r
Hi Michael!
Sorry for the long time without any responses. Shall we continue debugging this?
We're currently running 5.15.x on the host system and the guests and the
testsuite
for gcc-9 still reproducibly kills the KVM host.
Adrian
On 11/1/21 07:53, Michael Ellerman wrote:
> Sure, will give th
On Fri, Oct 29, 2021 at 02:33:12PM +0200, John Paul Adrian Glaubitz wrote:
> Hi Nicholas!
>
> On 10/29/21 02:41, Nicholas Piggin wrote:
> > Soft lockup should mean it's taking timer interrupts still, just not
> > scheduling. Do you have the hard lockup detector enabled as well? Is
> > there anyth
Hello,
On Thu, Oct 28, 2021 at 04:15:19PM +0200, John Paul Adrian Glaubitz wrote:
> Hi!
>
> On 10/28/21 16:05, John Paul Adrian Glaubitz wrote:
> > The following packages were being built at the same time:
> >
> > - guest 1: virtuoso-opensource and openturns
> > - guest 2: llvm-toolchain-13
> >
the host. I will update the
> guest to 5.15-rc7 now as well and see how that goes.
OK, so I'm definitely able to crash the 5.15 kernel as well:
[57031.404944] watchdog: BUG: soft lockup - CPU#24 stuck for 14957s!
[migration/24:14]
[57035.420898] watchdog: BUG: soft lockup - CPU#48 stuck
Hi Michael!
On 11/1/21 07:53, Michael Ellerman wrote:
> Sure, will give that a try.
>
> I was able to crash my machine over the weekend, building openjdk, but I
> haven't been able to reproduce it for ~24 hours now (I didn't change
> anything).
I made another experiment and upgraded the host to
build -d sid --arch=ppc64 --no-arch-all gcc-11_11.2.0-10.dsc
>
> Could you try gcc-10 instead? It's testsuite has crashed the host for me
> with a patched kernel twice now.
>
> $ dget -u
> https://deb.debian.org/debian/pool/main/g/gcc-10/gcc-10_10.3.0-12.dsc
> $ sbuild -d si
you try gcc-10 instead? It's testsuite has crashed the host for me
with a patched kernel twice now.
$ dget -u https://deb.debian.org/debian/pool/main/g/gcc-10/gcc-10_10.3.0-12.dsc
$ sbuild -d sid --arch=powerpc --no-arch-all gcc-10_10.3.0-12.dsc
$ sbuild -d sid --arch=ppc64 --no-arch-all gcc-10_1
But looking at the documentation [1] it seems we could
use it to print a backtrace once the lockup occurs.
> Do you have the full dmesg / kernel log for this boot?
I do, uploaded the messages file here:
https://people.debian.org/~glaubitz/messages-kvm-lockup.gz
Also, I noticed there is actually a ba
or 335s! [CPU
> 2/KVM:1836]
> [194914.011217] watchdog: BUG: soft lockup - CPU#152 stuck for 335s! [CPU
> 3/KVM:1837]
> [194921.959133] watchdog: BUG: soft lockup - CPU#24 stuck for 336s!
> [khugepaged:318]
Soft lockup should mean it's taking timer interrupts still, just not
sch
Hi!
On 10/28/21 16:05, John Paul Adrian Glaubitz wrote:
> The following packages were being built at the same time:
>
> - guest 1: virtuoso-opensource and openturns
> - guest 2: llvm-toolchain-13
>
> I really did a lot of testing today with no issues and just after I sent my
> report
> to oss-s
Hi Michael!
On 10/28/21 13:20, John Paul Adrian Glaubitz wrote:
> It seems I also can no longer reproduce the issue, even when building the
> most problematic
> packages and I think we should consider it fixed for now. I will keep
> monitoring the server,
> of course, and will let you know in ca
Hello!
On 10/28/21 15:52, John Paul Adrian Glaubitz wrote:
> I am not sure what triggered my previous crash but I don't think it's related
> to this
> particular bug. I will keep monitoring the server in any case and open a new
> bug report
> in case I'm running into similar issues.
This is ver
Hello!
An update to this post with oss-security CC'ed.
On 10/26/21 10:48, John Paul Adrian Glaubitz wrote:
> I have tested these patches against 5.14 but it seems the problem [1] still
> remains for me
> for big-endian guests. I built a patched kernel yesterday, rebooted the KVM
Hi Michael!
On 10/28/21 08:39, Michael Ellerman wrote:
>>> No, I will try that now.
>
> That completed fine on my BE VM here.
>
> I ran these in two tmux windows:
> $ sbuild -d sid --arch=powerpc --no-arch-all gcc-11_11.2.0-10.dsc
> $ sbuild -d sid --arch=ppc64 --no-arch-all gcc-11_11.2.0-10
s very good news!
>
>> I also have a standalone reproducer I'll send you.
>
> Thanks, that would be helpful!
>
>>> Also, I'll try a kernel from git with Debian's config.
>>>
>>>> I guess we have yet another bug.
>>>>
>>&
ed host?
Yes, the parallel builds of glibc you described crashed the unpatched
host 100% reliably for me.
I also have a standalone reproducer I'll send you.
> If the unpatched host crashes for you but the patched doesn't, I will
> make sure I didn't accidentally miss anyth
that passes for me with a patched host.
>>
>> Did you manage to crash the unpatched host?
>
> Yes, the parallel builds of glibc you described crashed the unpatched
> host 100% reliably for me.
OK, that is very good news!
> I also have a standalone reproducer I'll send y
oesn't, I will make sure I didn't accidentally
miss anything.
Also, I'll try a kernel from git with Debian's config.
> I guess we have yet another bug.
>
> I tried the following in a debian BE VM and it completed fine:
>
> $ dget -u http://ftp.debian.or
John Paul Adrian Glaubitz writes:
> Hi Michael!
Hi Adrian,
Thanks for testing ...
>> The Linux kernel for powerpc since v5.2 has a bug which allows a
>> malicious KVM guest to crash the host, when the host is running on
>> Power8.
>>
>> Only machines using
Excerpts from John Paul Adrian Glaubitz's message of October 26, 2021 6:48 pm:
> Hi Michael!
>
>> The Linux kernel for powerpc since v5.2 has a bug which allows a
>> malicious KVM guest to crash the host, when the host is running on
>> Power8.
>>
>> On
Hi Michael!
> The Linux kernel for powerpc since v5.2 has a bug which allows a
> malicious KVM guest to crash the host, when the host is running on
> Power8.
>
> Only machines using Linux as the hypervisor, aka. KVM, powernv or bare
> metal, are affected by the bug. Machines r
at (text) fb console. Logging in via ssh
and
running "ls -Rail /usr/include" generated errors (and a hung ssh
session). Once errors started, they repeated for almost every command.
See pb3400c-63e3756d1bdf-1.txt.
2) Wallstreet
vmlinux-5.13.0-pmac-4-g63e3756d1bd-1
X login failed, there wer
errors (and a hung ssh
session). Once errors started, they repeated for almost every command.
See pb3400c-63e3756d1bdf-1.txt.
2) Wallstreet
vmlinux-5.13.0-pmac-4-g63e3756d1bd-1
X login failed, there were errors ("Oops: Kernel access of bad area",
"Oops: Exception in kernel mode&qu
session). Once errors started, they repeated for almost every command.
> See pb3400c-63e3756d1bdf-1.txt.
>
> 2) Wallstreet
> vmlinux-5.13.0-pmac-4-g63e3756d1bd-1
> X login failed, there were errors ("Oops: Kernel access of bad area",
> "Oops: Exception in ker
-e
CONFIG_VMAP_STACK
$ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- -j4 clean olddefconfig
vmlinux
$ egrep "CONFIG_PPC_KUAP|CONFIG_VMAP_STACK" .config
$ strings vmlinux |grep "Linux version"
If that kernel produces errors, I'd try a second build a
1 - 100 of 5319 matches
Mail list logo
