Hi Riccardo, all,
On 17.01.22 21:35, Riccardo Mottola wrote:
Hi,
Riccardo Mottola wrote:
John Paul Adrian Glaubitz wrote:
Not nice. I started compiling some stuff and the box froze, I connected
serial console and could not resume due to Fast Data Access MMU miss"
So, this crash occurs with
Hi,
Riccardo Mottola wrote:
> John Paul Adrian Glaubitz wrote:
>>> Not nice. I started compiling some stuff and the box froze, I connected
>>> serial console and could not resume due to Fast Data Access MMU miss"
>> So, this crash occurs with the latest 5.15 kernel on your T2000?
> exactly
Hi,
John Paul Adrian Glaubitz wrote:
>> Not nice. I started compiling some stuff and the box froze, I connected
>> serial console and could not resume due to Fast Data Access MMU miss"
> So, this crash occurs with the latest 5.15 kernel on your T2000?
exactly latest kernel.
I will retest it
Hi!
On 1/17/22 14:41, Riccardo Mottola wrote:
>>> The good news is that latest kernel installed seems to boot and takes
>>> all CPUs online. How stable it is I don't know, it needs to be tested.
>>
>> Please run some stress tests such as stress-ng and report back.
>
> Not nice. I started
I reply to myself.
I did run the old 5.9 kernel from debian - which has proven quite stable.
I did run the same tests... and I found once error in the console indeed.
[ 380.918996] Unable to handle kernel NULL pointer dereference
[ 380.919198] tsk->{mm,active_mm}->context = 057d
[
Hi Adrian,
John Paul Adrian Glaubitz wrote:
> Did you forget to create an initrd? After installing the kernel, run:
>
> $ update-initramfs -k KERNEL_VERSION -c
I did not run it this way, will do.
I had it however, of a very big size:
316M Jan 14 17:15 initrd.img-5.9.0-rc1+
which filled up my
Hi!
On 1/14/22 17:58, Riccardo Mottola wrote:
> as Frank asked, I compiled myself a kernel using his latest commit
> identified as good:
> 67e306c6906137020267eb9bbdbc127034da3627
>
> and this kernel works, but then fails to load initramfs.
Did you forget to create an initrd? After installing
Hi all,
as Frank asked, I compiled myself a kernel using his latest commit
identified as good:
67e306c6906137020267eb9bbdbc127034da3627
and this kernel works, but then fails to load initramfs.
I don't know if the crash was before or after, so if it is a "proof"
that it is good or it is not
Hi guys,
On 11.12.21 18:59, John Paul Adrian Glaubitz wrote:
On 12/11/21 18:40, Riccardo Mottola wrote:
I remember you bisected about the breaking commits. Has there been any progress?
A better place where to report this issue other than this mailing list?
The proper place is to send an
On 12/11/21 18:40, Riccardo Mottola wrote:
> I remember you bisected about the breaking commits. Has there been any
> progress?
> A better place where to report this issue other than this mailing list?
The proper place is to send an email to the author of the breaking commit and
CC the
Hi Frank,
several months have passed… new kernels came into debian and they still do not
work for me, so let me dig up this matter again.
I can continue using 5.9 for now, but for how long?
On 2021-03-11 23:43:10 +0100 Frank Scheiner wrote:
> From [1] I assume T2 CPUs are not affected, but
Hi Anatoly!
Anatoly Pugachev wrote:
> current grub2 version does not support compressed image kernels, do
> the following:
>
> gzip -dc /boot/vmlinuz-5.12.0-rc5+ > /boot/vmlinux-5.12.0-rc5+
> rm /boot/vmlinuz-5.12.0-rc5+
> update-grub
>
> and reboot
oh yes, that was it. Finally, I could boot my
On Thu, Apr 1, 2021 at 2:40 PM Riccardo Mottola
wrote:
> multix@narya:~/code/linux-stable$ time sudo make install
> sh ./arch/sparc/boot/install.sh 5.12.0-rc5+ arch/sparc/boot/zImage \
> System.map "/boot"
> run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.12.0-rc5+
>
Hi Riccardo,
On Thu, Apr 01, 2021 at 01:43:29PM +0200, Riccardo Mottola wrote:
> > Yep, in your kernel config set:
> > CONFIG_SYSTEM_TRUSTED_KEYS=""
>
> thanks, that was it! Now the kernel build
great!
> Do I need to do somethings special?
>
> make install
> make modules_install
sorry, don't
Hhi Hermann,
hermann.la...@uni-heidelberg.de wrote:
> Yep, in your kernel config set:
> CONFIG_SYSTEM_TRUSTED_KEYS=""
thanks, that was it! Now the kernel build
Do I need to do somethings special?
make install
make modules_install
Which shows:
multix@narya:~/code/linux-stable$ time sudo make
On Thu, Apr 1, 2021 at 12:59 PM Riccardo Mottola
wrote:
> > This seems to only happen when the machines do a long run with high
> > workload and seemingly not when i just power them off again for night
> > with no high workload.
>
> I have a limited experience and can only share that the kernel I
Hi Connor,
Connor McLaughlan wrote:
> can anyone possible give a list of known stable kernel versions for
> SPARC machines? (is there a difference necessary between
> architectures/old vs. newer machines? sun4u/sun4v)?
>
> Also this instability manifests such that the machine is crashing
> during
Hi Riccardo,
On Sat, Mar 27, 2021 at 01:16:11PM -0600, Stan Johnson wrote:
> > I took the config out of /boot/config of a good kernel, updated it with
> > "make oldconfig"
> >
> > During compilation I see:
> >
> > CC init/init_task.o
> > make[1]: *** No rule to make target
> >
Hi Riccardo,
On 3/26/21 6:21 PM, Riccardo Mottola wrote:
> Hi,
> ...
>
> I cloned linux stable. It took 60 minutes...
>
> I took the config out of /boot/config of a good kernel, updated it with
> "make oldconfig"
>
> During compilation I see:
>
> CC init/init_task.o
> make[1]: *** No
Hi,
I was unable to "hack" for some days due to day-job. I have seen Frank
and others have done a great deal.
Still, I wanted to try my own compilation, as a first attempt and also
to build and be able to check eventual patches myself.
On 3/11/21 11:56 PM, Gregor Riepl wrote:
You should
Hi,
On 23.03.21 17:30, Connor McLaughlan wrote:
Hi,
can anyone possible give a list of known stable kernel versions for
SPARC machines? (is there a difference necessary between
architectures/old vs. newer machines? sun4u/sun4v)?
Also this instability manifests such that the machine is
Hi,
can anyone possible give a list of known stable kernel versions for SPARC
machines? (is there a difference necessary between architectures/old vs.
newer machines? sun4u/sun4v)?
Also this instability manifests such that the machine is crashing during
high workload? (halting? rebooting?)
I
Hi Jan,
On 23.03.21 16:36, Jan Engelhardt wrote:
On Tuesday 2021-03-23 16:29, Frank Scheiner wrote:
```
[...]
Begin: Retrying nfs mount ... [ 41.753937] NFS: mount program didn't
pass remote address
mount: Invalid argument
I seem to recall that NFS is one of those filesystems that (a)
On Tuesday 2021-03-23 16:29, Frank Scheiner wrote:
>>
>> while I was able to "install" correctly using a slightly older ISO, I
>> get not a bootable system. The kernel appears to crash very early during
>> boot.
>
> From my current testing it looks like "UltraSPARC IIIi"s are also
> affected by
Hi all,
On 09.03.21 13:23, Riccardo Mottola wrote:
Hi all,
while I was able to "install" correctly using a slightly older ISO, I
get not a bootable system. The kernel appears to crash very early during
boot.
Anybody else has this issue?
Booting `Debian GNU/Linux'
Loading Linux
Hi Adrian,
On 17.03.21 13:39, John Paul Adrian Glaubitz wrote:
On 3/17/21 1:22 PM, Frank Scheiner wrote:
```
johndoe@x4270:~/git-projects/torvalds/linux$ git bisect bad
028abd9222df0cf5855dab5014a5ebaf06f90565 is the first bad commit
[...]
Did you verify that reverting this commit or - if
Hi Frank!
On 3/17/21 1:22 PM, Frank Scheiner wrote:
> Hi Adrian, Riccardo
>
> so I'm finished with bisecting and it points to the following commit as
> first bad commit:
>
> ```
> johndoe@x4270:~/git-projects/torvalds/linux$ git bisect bad
> 028abd9222df0cf5855dab5014a5ebaf06f90565 is the first
Hi Adrian, Riccardo
so I'm finished with bisecting and it points to the following commit as
first bad commit:
```
johndoe@x4270:~/git-projects/torvalds/linux$ git bisect bad
028abd9222df0cf5855dab5014a5ebaf06f90565 is the first bad commit
commit 028abd9222df0cf5855dab5014a5ebaf06f90565
Author:
Hi Adrian,
On 16.03.21 14:27, John Paul Adrian Glaubitz wrote:
Hello Frank!
On 3/16/21 2:07 PM, Frank Scheiner wrote:
After a first cross compile run, I can confirm that 5.10-rc1 is also
broken on my T1000. I'll take this version (parent commit:
33def8498fdde180023444b08e12b72a9efed41d) as
Hello Frank!
On 3/16/21 2:07 PM, Frank Scheiner wrote:
> After a first cross compile run, I can confirm that 5.10-rc1 is also
> broken on my T1000. I'll take this version (parent commit:
> 33def8498fdde180023444b08e12b72a9efed41d) as "bad". But taking v5.9 as
> good means more than 5000 commits
Hi again,
On 16.03.21 14:07, Frank Scheiner wrote:
@Adrian:
After a first cross compile run, I can confirm that 5.10-rc1 is also
broken on my T1000. I'll take this version (parent commit:
33def8498fdde180023444b08e12b72a9efed41d) as "bad". But taking v5.9 as
good means more than 5000 commits in
Hi Riccardo, Adrian,
so I did some testing yesterday and also see your problem on my T1000.
Because of some kernel command line misconfiguration, my machine at
first couldn't find its root FS as it tried to use a non-existent NIC.
This lead to a lot of kernel oopses (I assume at least one per
On Thursday 2021-03-11 23:43, Frank Scheiner wrote:
>>
>> Do you know if I can via serial-console reset the system?
>
> Reset from the serial console might work via the kernel with the [magic
> system request] functionality.
>
> [magic system request]:
>
> How should I proceed? Which kernel sources?
>
> https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s-common-official
>
>
> is 4.3 correct for me? 4.6 ?
You should clone the upstream Git repo, otherwise bisecting will be much
more difficult.
I think these instructions
Hi Riccardo,
On 11.03.21 23:03, Riccardo Mottola wrote:
Hi Frank!
I suppose the Niagara CPU gives the kernel issue
From [1] I assume T2 CPUs are not affected, but yeah, the issue could
be that selective that it only affects the very first generation.
[1]:
> Do you know if I can via serial-console reset the system?
> I tried sending a break on the serial console, but the errors just keep
> running.
> Break is received, since I see it as SC Alert, but I am not put into the
> console, maybe there is some further trick on these newer machine? I am
>
Hi Adrian
John Paul Adrian Glaubitz wrote:
Well, that doesn't really help you though. You want to find the commit in
question,
just the range isn't enough to solve the issue.
Well, a little bit it helped, it is something early in the 5.10 series.
Also I have now an apparently working kernel
Hi Frank!
I suppose the Niagara CPU gives the kernel issue
Frank Scheiner wrote:
If I remember there was a repository with many snapshots of different
versions, already as package, which one can test quickly. That way we
can restrict breakage range without git bisect.
Do you have a link?
I
On 3/10/21 10:17 AM, Riccardo Mottola wrote:
> If I remember there was a repository with many snapshots of different
> versions,
> already as package, which one can test quickly. That way we can restrict
> breakage
> range without git bisect.
Well, that doesn't really help you though. You want
Hi Riccardo,
On 10.03.21 10:17, Riccardo Mottola wrote:
Frank Scheiner wrote:
We have an older UltraSPARC IIIi that has issues with newer kernels, but
usually only after longer operation and the issue might be related to
the
bug that was just fixed recently by Rob Gardner.
Which kernel
Hi Frank,
Frank Scheiner wrote:
We have an older UltraSPARC IIIi that has issues with newer kernels, but
usually only after longer operation and the issue might be related to the
bug that was just fixed recently by Rob Gardner.
Which kernel version will have this bug (which one?) fixed,
On 3/9/21 11:20 PM, John Paul Adrian Glaubitz wrote:
>> Which kernel version will have this bug (which one?) fixed, 5.11.x? I
>> can also check with one of my UltraSPARC IIIi powered systems, too, next
>> week.
>
> I have not uploaded that kernel yet, I have it built locally, PR here [1].
The
On 3/9/21 10:18 PM, Frank Scheiner wrote:
>> The oldest buildd we are running is a T5120 and that's a T2.
>
> And these don't show the problems Riccardo's T1 powered T2000 has?
No, the machine runs stable.
>> We have an older UltraSPARC IIIi that has issues with newer kernels, but
>> usually
On 09.03.21 22:09, John Paul Adrian Glaubitz wrote:
On 3/9/21 9:38 PM, Frank Scheiner wrote:
I have a T1000 with which I could try to reproduce Riccardo's issues.
Hardware wise they should be pretty similar. As the T1000 doesn't have a
CDROM, I'll try to netboot a few newer kernels and report
On 3/9/21 9:38 PM, Frank Scheiner wrote:
> I have a T1000 with which I could try to reproduce Riccardo's issues.
> Hardware wise they should be pretty similar. As the T1000 doesn't have a
> CDROM, I'll try to netboot a few newer kernels and report my findings.
> Will take me until next week
Hi guys,
On 09.03.21 18:31, John Paul Adrian Glaubitz wrote:
Hi!
On 3/9/21 6:26 PM, Riccardo Mottola wrote:
John Paul Adrian Glaubitz wrote:
while I was able to "install" correctly using a slightly older ISO, I get not a
bootable
system. The kernel appears to crash very early during boot.
Hi!
On 3/9/21 6:26 PM, Riccardo Mottola wrote:
> John Paul Adrian Glaubitz wrote:
>>> while I was able to "install" correctly using a slightly older ISO, I get
>>> not a bootable
>>> system. The kernel appears to crash very early during boot.
>> I think this is more likely a hardware issue. We
Hi,
John Paul Adrian Glaubitz wrote:
while I was able to "install" correctly using a slightly older ISO, I get not a
bootable
system. The kernel appears to crash very early during boot.
I think this is more likely a hardware issue. We haven't seen any machines
crashing that
early. Please
Hello Riccardo!
On 3/9/21 1:23 PM, Riccardo Mottola wrote:
> while I was able to "install" correctly using a slightly older ISO, I get not
> a bootable
> system. The kernel appears to crash very early during boot.
I think this is more likely a hardware issue. We haven't seen any machines
Hi all,
while I was able to "install" correctly using a slightly older ISO, I
get not a bootable system. The kernel appears to crash very early during
boot.
Anybody else has this issue?
Booting `Debian GNU/Linux'
Loading Linux 5.10.0-4-sparc64-smp ...
Loading initial ramdisk ...
[
50 matches
Mail list logo
