Hi, I have a fedora35 system that uses rsync to operate as a backup server.
It has a 8TB RAID5 array, and for the last few days, has
crashed/segfaulted in what appears to be the same time that it starts to
backup a particular remote host. This indicates to me that perhaps the
there is some spot on
#x27;s still a legit
kernel crash.
aops:ext4_da_aops ino:bca118c dentry name:"rsyslog.log"
flags:
0x17c0060010(lru|mappedtodisk|reclaim|node=0|zone=2|lastcpupid=0x1f)
raw: 0017c0060010 e613d17e0208 e613d17e00c8 8e452d1070d0
raw: 02fd3d40 000
d. I've
since removed the huge log file and disabled the log entry in
rsyslog.conf, so I'll now continue to watch it, but it's still a legit
kernel crash.
aops:ext4_da_aops ino:bca118c dentry name:"rsyslog.log"
flags:
0x17c0060010(lru|mappedtodisk|reclaim|node=0|z
Hi,
> >> Here's a bit of the kernel message from dmesg
> >> [ cut here ]
> >> WARNING: CPU: 4 PID: 633983 at kernel/exit.c:739 do_exit+0x37/0xa90
> >> general protection fault, probably for non-canonical address
> >> 0xcc2a8cfcb62a56a1: [#1] SMP PTI
> >> CPU: 4 PID: 63
Gordon Messmer writes:
On 2/12/22 14:59, Alex wrote:
Here's a bit of the kernel message from dmesg
[ cut here ]
WARNING: CPU: 4 PID: 633983 at kernel/exit.c:739 do_exit+0x37/0xa90
general protection fault, probably for non-canonical address
0xcc2a8cfcb62a56a1: [#1]
On Sun, 13 Feb 2022 10:41:36 -0800
Gordon Messmer wrote:
> bio_crypt_clone suggests something wrong in an encrypted block device.
> Maybe corrupt data that rsync traverses during the backup?
Perhaps run the same rsync command with a -v option in a terminal
and see if the crash happens on the sa
On 2/12/22 14:59, Alex wrote:
Here's a bit of the kernel message from dmesg
[ cut here ]
WARNING: CPU: 4 PID: 633983 at kernel/exit.c:739 do_exit+0x37/0xa90
general protection fault, probably for non-canonical address
0xcc2a8cfcb62a56a1: [#1] SMP PTI
CPU: 4 PID: 63398
cess causing it.
Yes, there is an automated backup using rsync around that time, but
there should be no userland process that could ever cause a kernel
crash.
CPU: 4 PID: 633983 Comm: rsync Not tainted 5.14.18-200.fc34.x86_64 #1
Thanks,
Alex
On 2/12/22 15:59, Alex wrote:
Anyone else experiencing similar problems with the latest kernels?
The fact that it happens at the same time every day makes me wonder if
there's some job that's in process causing it.
___
users mailing list -- users@l
Hi,
I have a fedora34 system that I'm using as a mail server, and for the
past few weeks, it's had a kernel crash at 6:30am every morning.
Sometimes it results in the server going catatonic and unresponsive,
and other times it just seems to report the kernel crash and continue
running.
On 12/31/21 12:52, Robert Moskowitz wrote:
On 12/31/21 15:32, Samuel Sieb wrote:
On 12/31/21 08:57, Robert Moskowitz wrote:
I was downloading some mp4 lectures in Firefox and getting ready to
respond to the save to dialog when the system hung hard requiring a
power cycle. Couple not even sw
On 12/31/21 15:32, Samuel Sieb wrote:
On 12/31/21 08:57, Robert Moskowitz wrote:
I was downloading some mp4 lectures in Firefox and getting ready to
respond to the save to dialog when the system hung hard requiring a
power cycle. Couple not even switch to a non-graphic session to
login as r
On 12/31/21 08:57, Robert Moskowitz wrote:
I was downloading some mp4 lectures in Firefox and getting ready to
respond to the save to dialog when the system hung hard requiring a
power cycle. Couple not even switch to a non-graphic session to login
as root.
I had just done a dnf update that
On Fri, 31 Dec 2021 12:31:44 -0500
Robert Moskowitz wrote:
> So it seems not to be my problem?
I guess not.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduc
On 12/31/21 12:23, Tom Horsley wrote:
On Fri, 31 Dec 2021 12:14:23 -0500
Robert Moskowitz wrote:
How do I know if I am using nouveau and then how to switch to nvidia?
Run:
lspci | fgrep VGA
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Kabini [Radeon HD 8330]
On Fri, 31 Dec 2021 12:14:23 -0500
Robert Moskowitz wrote:
> How do I know if I am using nouveau and then how to switch to nvidia?
Run:
lspci | fgrep VGA
if that mentions an NVIDIA video card, then fedora will have used
the nouveau drivers by default. You could also run lsmod and see
if it ment
On 12/31/21 12:10, Tom Horsley wrote:
If you are using the nouveau video drivers, try switching to the
rpmfusion nvidia drivers. Every new release I try to use the
nouveau drivers, and within a couple of weeks, I always
get crashes like this, almost always when using a browser. So
I switch to n
If you are using the nouveau video drivers, try switching to the
rpmfusion nvidia drivers. Every new release I try to use the
nouveau drivers, and within a couple of weeks, I always
get crashes like this, almost always when using a browser. So
I switch to nvidia, and the crashes stop.
_
I was downloading some mp4 lectures in Firefox and getting ready to
respond to the save to dialog when the system hung hard requiring a
power cycle. Couple not even switch to a non-graphic session to login
as root.
I had just done a dnf update that installed the new 5.15.11 kernel (was
runni
How one configured crash dumps had not significantly changed in a long
time (from what I know).
If the hardware gets a significant hardware error and does not deliver
an NMI to the os, but does force a hw reset, then you won't get a
crashdump.
On Thu, Feb 27, 2020 at 7:54 PM George R Goffe via u
On Fri, 2020-02-28 at 01:53 +, George R Goffe via users wrote:
> Hi,
>
> I'm trying to help shoot a possible kernel bug which may create a dump. I'm
> trying to find doc on how to enable the crashdump "features" of my FC33
> (Rawhide) system.
>
> tldp.org seems to be out of date
> docs.fedo
Hi,
I'm trying to help shoot a possible kernel bug which may create a dump. I'm
trying to find doc on how to enable the crashdump "features" of my FC33
(Rawhide) system.
tldp.org seems to be out of date
docs.fedoraproject.org doesn't seem to have a search facility...
Can anyone give me a hint
On Sun, 16 Jul 2017 03:46:17 -
"Sudhir Khanger" wrote:
> Hi,
>
> I installed Ubuntu LTS because I can't have my system breaking every
> six months. I had already wasted 24 hours and I couldn't waste
> anymore. Thank you so much for your help.
Yeah, you're probably not a good fit for Fedora.
Hi,
I installed Ubuntu LTS because I can't have my system breaking every six
months. I had already wasted 24 hours and I couldn't waste anymore. Thank you
so much for your help.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe sen
On Sat, 15 Jul 2017 13:28:54 -0400
Tom Horsley wrote:
> I'd almost wonder if there was only one actual crash, and
> abrt keeps telling you about the same one over and over again
> because it failed to record that it already told you. That
> would explain why running a new kernel still keeps repor
On Sat, 15 Jul 2017 10:04:45 -0700
stan wrote:
> I know little about abrt, and why it would be generating these oops,
> and why it isn't paying attention to its configuration file settings.
I'd almost wonder if there was only one actual crash, and
abrt keeps telling you about the same one over an
On Sat, 15 Jul 2017 04:18:07 -
"Sudhir Khanger" wrote:
> I just installed 4.11.10-300.fc26.x86_64. And the problem continues.
>
> I am getting the following messages every second.
>
> We're sorry, it looks like
> BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64 crashed. Please
> contact the
Sudhir Khanger wrote:
>I restarted the system. And also tried restarting abrtd.
In that case I'm out of ideas.
Sorry,
Ron
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Hi Ron,
I restarted the system. And also tried restarting abrtd.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Sudhir Khanger wrote:
>That didn't help. I am continuing to see the abrt notification.
Did you restart abrtd?
systemctl restart abrtd
Ron
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedor
Hi,
>DropNotReportableOopses = yes
That didn't help. I am continuing to see the abrt notification.
I have so far 10,000 entries in the ABRT window.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@list
Sudhir Khanger wrote:
>Jul 15 10:35:05 workstation abrt-dump-journal-oops[1256]: Reported 2 kernel
>oopses to Abrt
>Jul 15 10:35:06 workstation abrt-server[5959]: Can't find a meaningful
>backtrace for hashing in '.'
>Jul 15 10:35:06 workstation abrt-server[5959]: Option
>'DropNotReportableOopse
Hi,
I have just rebuilt the boot images after running the following command.
dracut --regenerate-all --force
Let's see how long it works. I have 6000+ unreportable errors in the ABRT
window.
Still no luck.
Jul 15 10:35:05 workstation abrt-dump-journal-oops[1256]: Reported 2 kernel
oopses to
On 07/14/2017 09:18 PM, Sudhir Khanger wrote:
I am getting the following messages every second.
We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64
crashed. Please contact the developer if you want to report the issue.
We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4
Hi,
Thanks for your reply.
I just installed 4.11.10-300.fc26.x86_64. And the problem continues.
I am getting the following messages every second.
We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64
crashed. Please contact the developer if you want to report the issue.
We
On 07/14/2017 08:19 AM, Sudhir Khanger wrote:
I have been getting these messages on my system every second after upgrading
from Fedora 25 to Fedora 26 Plasma Desktop.
We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64
crashed.
I already have 1000 of reports that I can'
On Fri, 14 Jul 2017 15:19:41 -
"Sudhir Khanger" wrote:
> I have been getting these messages on my system every second after
> upgrading from Fedora 25 to Fedora 26 Plasma Desktop.
>
> We're sorry, it looks like
> BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64 crashed.
>
> I already have 10
Hello,
I have been getting these messages on my system every second after upgrading
from Fedora 25 to Fedora 26 Plasma Desktop.
We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64
crashed.
I already have 1000 of reports that I can't submit. How do I resolve it.
_
I finally set aside time to try to upgrade my Fedora 14 box to F16,
but I'me failing at the first hurdle.
Anaconda is crashing out with a kernel bug shortly after selecting
the OS to update:
kernel bug security/selinux/ss/services.c:655
invalid opcode [#1] SMP
Pid: 855, comm: anaco
Hi,
This is F16 live-cd lxde i686.
I filed a BZ report 752329 - kernel crash and other errors.
JB
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki
On Wed, 2010-08-18 at 12:03 -0400, Steve Blackwell wrote:
> sensors indicated the the CPU fan and the power supply rails are
> monitored. Does anyone know if I can put something in smartd.conf to
> get reports on them and if so what?
SMART is for hard drives. If you want to monitor other things,
On Tue, 17 Aug 2010 18:07:18 +0300
Gilboa Davara wrote:
> On Tue, 2010-08-17 at 09:44 -0400, Steve Blackwell wrote:
> > I leave my computer on 24/7 so that my backups can run at night.
> > Lately, it has been crashing during the night usually leaving no
> > trace of what happened. Last night it c
On 19 August 2010 00:41, Steve Blackwell wrote:
>
> Running sensors-detect produced the same /etc/sysconfig/lm_sensors
> file that I already had. Running sensors shows this:
>
> +3.3 Voltage: +1.68 V (min = +3.00 V, max = +3.60 V)
> +5.0 Voltage: +1.62 V (min = +4.50 V, max = +5.50 V
On Wed, 18 Aug 2010 11:44:53 +1000
David wrote:
> On 18 August 2010 09:22, Bill Davidsen wrote:
> >>
> > If this line is for real:
> > 194 Temperature_Celsius 0x0022 116 253 000 Old_age
> > Always
> > - 34
> >
> > Then your drive is running hotter than boiling water and has
On Wed, 2010-08-18 at 10:41 -0400, Steve Blackwell wrote:
> On Wed, 18 Aug 2010 08:44:16 +0300
> Gilboa Davara wrote:
>
> > On Tue, 2010-08-17 at 13:08 -0400, Steve Blackwell wrote:
> > > On Wed, 18 Aug 2010 02:12:16 +0930
> > > Tim wrote:
> > >
> > > > On Tue, 2010-08-17 at 12:05 -0400, Steve
On Wed, 18 Aug 2010 08:44:16 +0300
Gilboa Davara wrote:
> On Tue, 2010-08-17 at 13:08 -0400, Steve Blackwell wrote:
> > On Wed, 18 Aug 2010 02:12:16 +0930
> > Tim wrote:
> >
> > > On Tue, 2010-08-17 at 12:05 -0400, Steve Blackwell wrote:
> > > > I've been looking at my logs some more. I don't u
On Tue, 2010-08-17 at 12:48 -0400, Steve Blackwell wrote:
> On Tue, 17 Aug 2010 12:05:44 -0400
> Steve Blackwell wrote:
>
> > On Tue, 17 Aug 2010 18:07:18 +0300
> > Gilboa Davara wrote:
> >
> > > On Tue, 2010-08-17 at 09:44 -0400, Steve Blackwell wrote:
> > > > I leave my computer on 24/7 so th
On Tue, 2010-08-17 at 13:08 -0400, Steve Blackwell wrote:
> On Wed, 18 Aug 2010 02:12:16 +0930
> Tim wrote:
>
> > On Tue, 2010-08-17 at 12:05 -0400, Steve Blackwell wrote:
> > > I've been looking at my logs some more. I don't understand these
> > > messages:
> > >
> > > Aug 17 10:30:50 steve ke
On 18 August 2010 09:22, Bill Davidsen wrote:
>>
> If this line is for real:
> 194 Temperature_Celsius 0x0022 116 253 000 Old_age Always
> - 34
>
> Then your drive is running hotter than boiling water and has been close to
> melting point of solder. In spite of that the erro
Steve Blackwell wrote:
> This happened in the middle of the backup which started at 1:00am and
> finished (successfully) at 1:28am so perhaps the backup blocked the kjournald
> process but it didn't crash the computer because there are later messages in
> the backup log and the messages file.
>
On Wed, 18 Aug 2010 02:12:16 +0930
Tim wrote:
> On Tue, 2010-08-17 at 12:05 -0400, Steve Blackwell wrote:
> > I've been looking at my logs some more. I don't understand these
> > messages:
> >
> > Aug 17 10:30:50 steve kernel: CPU0: Temperature above threshold, cpu
> > clock throttled (total ev
On Tue, 17 Aug 2010 12:05:44 -0400
Steve Blackwell wrote:
> On Tue, 17 Aug 2010 18:07:18 +0300
> Gilboa Davara wrote:
>
> > On Tue, 2010-08-17 at 09:44 -0400, Steve Blackwell wrote:
> > > I leave my computer on 24/7 so that my backups can run at night.
> > > Lately, it has been crashing during
On Tue, 2010-08-17 at 12:05 -0400, Steve Blackwell wrote:
> I've been looking at my logs some more. I don't understand these
> messages:
>
> Aug 17 10:30:50 steve kernel: CPU0: Temperature above threshold, cpu
> clock throttled (total events = 455)
> Aug 17 10:30:50 steve kernel: CPU1: Temperatu
On 08/17/2010 06:44 AM, Steve Blackwell wrote:
> I leave my computer on 24/7 so that my backups can run at night.
> Lately, it has been crashing during the night usually leaving no trace
> of what happened. Last night it crashed but left this
> in /var/log/messages:
>
> Aug 17 01:04:56 steve kern
On Tue, 17 Aug 2010 18:07:18 +0300
Gilboa Davara wrote:
> On Tue, 2010-08-17 at 09:44 -0400, Steve Blackwell wrote:
> > I leave my computer on 24/7 so that my backups can run at night.
> > Lately, it has been crashing during the night usually leaving no
> > trace of what happened. Last night it c
On Tue, 2010-08-17 at 09:44 -0400, Steve Blackwell wrote:
> I leave my computer on 24/7 so that my backups can run at night.
> Lately, it has been crashing during the night usually leaving no trace
> of what happened. Last night it crashed but left this
> in /var/log/messages:
>
> Aug 17 01:04:56
I leave my computer on 24/7 so that my backups can run at night.
Lately, it has been crashing during the night usually leaving no trace
of what happened. Last night it crashed but left this
in /var/log/messages:
Aug 17 01:04:56 steve kernel: INFO: task kjournald:1960 blocked for more than
120 sec
Clemens Eisserer wrote:
>
> As far as I know this is not a crash, but rather an unoptimal (slower)
> path taken somewhere.
> I don't thing there's neet to worry about this...
>
> - Clemens
>
>
OK thanks
--
View this message in context:
http://n3.nabb
tting crash infos...
> Jan 30 14:19:56 home1 named[1064]: client 127.0.0.1#44889: RFC 1918 response
> from Internet for 1.122.168.192.in-addr.arpa
> Jan 30 14:20:12 home1 abrtd: Creating report...
> Jan 30 14:20:12 home1 abrtd: Getting local universal unique identification
> Jan 30 14
30 14:20:12 home1 abrtd: Creating report...
Jan 30 14:20:12 home1 abrtd: Getting local universal unique identification
Jan 30 14:20:12 home1 abrtd: Getting local universal unique identification
Anyone interpret this for me?
Tnanks
--
View this message in context:
http://n3.nabble.com/Kernel-cras
60 matches
Mail list logo
