Hello,
this seems to be the same issue as here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069102
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069092
And the fix seems to be prepared here:
https://salsa.debian.org/kernel-team/linux/-/commit/37a0ac93027302ffbfae41ddc844312e88e72eef
Dear Maintainer,
I tried to find out where exactly the stack smashing takes place.
And found the ioctl SIOCCHGTUNNEL did write more than the 52 bytes
allocated in variable old_p, by that overwriting the stack canary.
Kind regards,
Bernhard
(gdb)
0x5557589f 62 {
1: x/i $pc
=> 0
On Thu, 12 Jan 2023 18:31:37 + =?UTF-8?Q?Julian_Gro=c3=9f?=
wrote:
My computer just froze on Kernel version 5.19.11-1. Though nothing got
logged.
Now I don't know if this is the same issue and newer kernels just behave
better in terms of logging, or if this is a different issue..
I gue
Hello Jim,
I am not involved in packaging, but came to this report by chance.
The attached file contains all the changes you devs have made in the kernel
configs from 5.10.28 (-6 package) to 5.10.38/.40 (-7 package). It was made with
meld.
~10 kernel parameters have changed and led to this mess
Hello,
just for the record.
Upstream seems to have fixed this in [1] which
is included in kernel v5.8 and later.
Kind regards,
Bernhard
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/tools/perf/ui/browsers/hists.c?id=d61cbb859b45fdb6b4997f2d51834fae41af0e94
Control: fixed -1 linux/5.10.28-1
Dear Maintainer,
I got that Thinkpad T60 back, and did upgrade
the installation to bullseye.
I can now confirm that the nokaslr workaround is not
needed any more, hibernate and resume is working for
me with current kernel 5.10.0-6-686-pae/5.10.28-1 in testing.
Dear Maintainer,
just a side note:
The visible segfaults might be related to #977945.
Unknown if they have any effect on suspending.
Kind regards,
Bernhard
Dear Maintainer,
I investigated a bit further and came across this document [1].
There it is stated that in Linux usually a single qxl device with
multiple outputs [2] is used and in Windows multiple qxl devices with
a single output each [3].
Using with a Linux guest the suggested multiple output
Hello Paul,
is it possible to install the package systemd-coredump on
the systems showing this crash?
Then after the next crash in the output of 'journalctl --no-pager'
should the segfault appear followed by a backtrace
that you could forward to this bug.
This should clarify which function calls
Dear Maintainer,
this bug sounds similar to this one:
https://bugs.debian.org/927163
Kind regards,
Bernhard
Dear Maintainer,
bug #925424 seems to be about the same issue.
Kind regards,
Bernhard
Dear Maintainer,
I observed such logging, too. My system is similar to the submitters one.
Found two occourences in still available kern.log* files. (See attached file.)
One was most probably related to a "GPU fault" 25 seconds before,
running 4.19.0-8-amd64/4.19.98-1.
The other was while not bei
Dear Maintainer,
crash happened again today when stopping a qemu VM with
the quit command at the qemu prompt.
Found the "refcount_t: underflow" already once at 2020-01-07,
but there the system could continue to run more than a day.
All occourences are with:
[0.00] Linux version 4.19.0-7-a
Control: forwarded -1 https://marc.info/?l=linux-kernel&m=157973791626377&w=2
Control: tags -1 + upstream
Hello Salvatore,
thanks for the link.
I tried to get in contact with upstream.
Kind regards,
Bernhard
https://www.spinics.net/lists/kernel/msg3384013.html
https://marc.info/?l=linux-kernel&
Hello Salvatore,
> Can you report the issue directly upstream?
Will do, but I am not sure exactly to where.
I found the MAINTAINERS file and I guess if there
is no "B:" line it has to be reported to the "L:" list ?
Kind regards,
Bernhard
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/
Dear Maintainer,
I could reproduce using linux-perf-5.2 and it is
also visible in linux-perf-5.4 5.4.8-1,
by just pressing enter.
The crash happens because in line 3172
function hist_browser__selected_entry returns
browser->he_selection, which is at this time a
null pointer.
This null pointer gets
fixed 932550 4.19.67-1
Hello,
maybe the following report is related:
https://bugs.debian.org/928736
Kind regards,
Bernhard
Dear Maintainer,
this issue seems to start since patch:
features/all/lockdown/0031-tracefs-Restrict-tracefs-when-the-kernel-is-locked-d.patch
Therefore a vanialla build does not show this issue.
With either of the following changes on top of all
debian patches, the exception does not happen.
Control: found -1 linux/5.2.6-1
Dear Maintainer,
the bugreport https://bugs.debian.org/934292
seems about the same issue.
The issue can be reproduced by just accessing the file below.
root@debian:~# strace -f powertop
execve("/usr/sbin/powertop", ["powertop"], 0x7fff5df92d08 /* 11 vars */) = 0
Hello,
the information might not yet be enough for
the maintainers to help.
Maybe you could install the package systemd-coredump.
In the output of 'journalctl --no-pager' should then
the segfaults appear too, followed by a backtrace
that you could forward to this bug.
Kind regards,
Bernhard
Hello Marcus Lundblad,
I don't know if it is related - I own a Baytrail
device that contains also these axp devices.
Back in late 2017 I got some help from Hans de Goede,
who worked that time in that area.
There my battery information was also missing with
the stock debian kernel.
He suggested to
Hello Jean-Dominique Frattini,
I am not involved in packaging any of these packages,
but I noted that you opened the last three days nearly
the same issue against three different packages?
What are you trying to achive that way?
And you noted versions contained in current Buster,
but you claim it i
Hello Everyone,
I also tried to install current testing to a qnap ts-119P II.
On Tue, 29 Jan 2019 21:43:50 +0100 =?UTF-8?Q?Uwe_Kleine-K=c3=b6nig?=
wrote:
> On 1/27/19 12:13 PM, Lukas Straub wrote:
> > Package: linux
> > Version: 4.19.12-1
> >
> > Hello Everyone,
> > I tried the latest Buster In
Package: src:linux
Version: 4.19.12-1
Severity: normal
Dear Maintainer,
I received following crash while having a cifs filesystem mounted
from a qemu VM running on the same host.
Unfortunately forgot to unmount and shut down the VM.
Then after some minutes system froze and restarted.
If it may b
Control: fixed 911392 linux/4.19.12-1
Dear Maintainer,
did an update on that testsystem and the error
does not show up with at least 4.19.12-1.
Kind regards,
Bernhard
Hello,
might this just another cases of similar bugs 908924/908382/911392?
Is this still an issue with current version 4.19.12-1 ?
Kind regards,
Bernhard
signature.asc
Description: OpenPGP digital signature
Hello,
missed following bug while listing maybe related ones:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911320
Kind regards,
Bernhard
Hello,
I installed a Thinkpad T60 last year around 16.19.2016 with Debian Testing.
With the kernel contained at that time suspend to disk was working well.
(linux-image-4.6.0-1-686-pae 4.6.4-1, [1])
Just recently I got this system back and upgraded it to current Stretch.
(linux-image-4.9.0-3-686-
Hello hikaru,
just saw your report and tried if I could reproduce your issue.
But probably you want to reproduce these steps on your hardware to verify
that this is really the issue on real hardware.
These steps I tried to reproduce:
- install a qemu virtual machine with current jessie with some
Had no chance to attach the mentioned dmesg in text mode of reportbug.
Kind regards,
Bernhard
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 3.16.0-4-686-pae (debian-kerne
Package: src:linux
Version: 3.16.7-ckt4-3
Severity: normal
Dear Maintainer,
I upgraded a Wheezy installation to Testing/Jessie. All in all it was without
big surprises.
Except that most of the time after some time (e.g. 15 seconds) after the login
via kdm into
the kde desktop the system hangs.
32 matches
Mail list logo
