Hello Tai,
No problem at all, I have installed deb package from unstable into my
Stable system. No new deps, so everything went smoothly. Older dbgsym
package has been removed in the process.
I will monitor for any regressions and let you know if I have any.
On 02/02/2024 12:00, Taihsiang Ho
Hi piorunz,
The issue and the corresponding backport should have been included in
the latest version in unstable/testing with version 0.8.0-2. If you
have a moment, would you mind a try?
Cheers,
Tai
On Sat, Jan 6, 2024 at 11:30 AM piorunz wrote:
>
> Hello Tai,
>
> Thanks for your reply.
>
>
Hello Tai,
Thanks for your reply.
Patch attached, for Debian Stable, following this commit for upstream
version:
https://github.com/mchehab/rasdaemon/commit/f1ea76375281001cdf4a048c1a4a24d86c6fbe48
It's 1 line change in 1 file (ras-events.c).
--- ras-events.c2024-01-06
Hi piorunz,
Thanks for testing. I will work on bug 1059484 first, and don't have
ETA of the backport. Feel free to send me a patch of the backport if
you are interested.
-tai
On Mon, Dec 11, 2023 at 8:26 PM piorunz wrote:
>
> On 11/12/2023 14:20, Russell Coker wrote:
> > We have 2 different
Hi all,
I can happily report no further crashes of rasdaemon. And no SIGBUS,
since one-line patch.
If you prefer, you can close this bug report. I will report once again
if I have any more problems.
And SIGBUS patch definitely worth importing to Debian Stable for wider
audience if this has not
On 11/12/2023 14:20, Russell Coker wrote:
We have 2 different issues here. The first one is a SEGV related to sqlite,
that might be a sqlite bug. Have you tried writing a simple sqlite program or
using a sqlite utility to see if it also crashes?
Sorry, I have no ability to write such a
We have 2 different issues here. The first one is a SEGV related to sqlite,
that might be a sqlite bug. Have you tried writing a simple sqlite program or
using a sqlite utility to see if it also crashes?
The issue being discussed now is separate. As most of this bug report is now
about the
Hi Tai,
No problem at all.
I have changed return sysconf(_SC_NPROCESSORS_ONLN); in line 331 of
ras-events.c, compiled and installed it. Restarted the rasdaemon
service, SIGBUS has not been generated (yet, usually it is). Will let
you know again after 24 hours if problem has come back or not.
Hi Piorunz,
Do you mind verifying if your issue is related to
https://github.com/mchehab/rasdaemon/issues/77 ? If yes, we can
consider to backport the corresponding upstream fix.
Kind regards,
Tai
On Mon, Dec 11, 2023 at 10:15 AM piorunz wrote:
>
> On 11/12/2023 04:20, Russell Coker wrote:
> >
On 11/12/2023 04:20, Russell Coker wrote:
If you stop rasdaemon, move aside /var/lib/rasdaemon/ras-mc_event.db, and then
start it again does it still crash?
Thanks for your reply. I stopped the service, moved ras-mc_event.db, and
started service again. File has been recreated. No crashes so
If you stop rasdaemon, move aside /var/lib/rasdaemon/ras-mc_event.db, and then
start it again does it still crash?
--
My Main Blog http://etbe.coker.com.au/
My Documents Bloghttp://doc.coker.com.au/
Package: rasdaemon
Version: 0.6.8-1.1
Severity: important
X-Debbugs-Cc: pior...@gmx.com
Dear Maintainer,
rasdaemon crashes frequently on my system.
No user input is required at all. I just find crash logs in dmesg every now and
then.
crash from today: attached in dmesg.txt file
gdb backtrace:
12 matches
Mail list logo
