Re: Hundreds of kernel crash messages after Fedora 26 upgrade. We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64 crashed.

[stan]

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.  If you wanted to get
something like that Ubuntu LTS in the Fedora model, you could look at
CentOS.  It's more for the use case you seem to desire.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Hundreds of kernel crash messages after Fedora 26 upgrade. We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64 crashed.

[Sudhir Khanger]

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 send an email to users-le...@lists.fedoraproject.org

Re: Hundreds of kernel crash messages after Fedora 26 upgrade. We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64 crashed.

[stan]

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 reporting
> the old kernel.

Yes, this sounds right.  I guess the question then is, how does the OP
rescue abrt-oops from this loop?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Hundreds of kernel crash messages after Fedora 26 upgrade. We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64 crashed.

[Tom Horsley]

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 and over again
because it failed to record that it already told you. That
would explain why running a new kernel still keeps reporting
the old kernel.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Hundreds of kernel crash messages after Fedora 26 upgrade. We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64 crashed.

[stan]

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 developer if you want to report the issue. We're sorry,
> it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.10-300.fc26.x86_64
> crashed. Please contact the developer if you want to report the
> issue. We're sorry, it looks like a problem occurred. If you'd like
> to help resolve the issue, please send a report.

Well, there is the big hammer that puts a band-aid on this.

systemctl stop abrt-oops.service
systemctl mask abrt-oops.service

It doesn't solve anything, but it stops the messages from being
generated.  You lose any abrt-oops functionality, though.

Are the messages really appearing as they did above?  For both kernel
images, 11.9 and 11.10?  You can only be running one kernel, how can
oops be generating for both?

I wonder if there is some configuration that your user has that is
causing the issue.  Could you create a new user, and then log in as
that user instead of your current user to see if the issue continues.
You would have to do this before you stopped and masked the service.

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.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Hundreds of kernel crash messages after Fedora 26 upgrade. We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64 crashed.

[Ron Yorston]

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

Re: Hundreds of kernel crash messages after Fedora 26 upgrade. We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64 crashed.

[Sudhir Khanger]

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

Re: Hundreds of kernel crash messages after Fedora 26 upgrade. We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64 crashed.

[Ron Yorston]

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.fedoraproject.org

Re: Hundreds of kernel crash messages after Fedora 26 upgrade. We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64 crashed.

[Sudhir Khanger]

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...@lists.fedoraproject.org

Re: Hundreds of kernel crash messages after Fedora 26 upgrade. We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64 crashed.

[Ron Yorston]

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 
>'DropNotReportableOopses' is not configured
>Jul 15 10:35:06 workstation abrt-server[5959]: Preserving oops '.' because 
>DropNotReportableOopses is 'no'

I had a similar problem.

You can, at least, make abrt shut up by adding the line

   DropNotReportableOopses = yes

to the file /etc/abrt/abrt.conf.  That doesn't tackle the underlying
problem, though.

In my case the issue seems to be the one in this bug report:

   https://bugzilla.redhat.com/show_bug.cgi?id=1408858

which is about the accelerometer on some Acer laptops.  Disabling the
related service stopped the oopses:

   systemctl stop iio-sensor-proxy.service
   systemctl mask iio-sensor-proxy.service

Your problem may be different, though.

Ron
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Hundreds of kernel crash messages after Fedora 26 upgrade. We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64 crashed.

[Sudhir Khanger]

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 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 'DropNotReportableOopses' 
is not configured
Jul 15 10:35:06 workstation abrt-server[5959]: Preserving oops '.' because 
DropNotReportableOopses is 'no'
Jul 15 10:35:06 workstation abrt-dump-journal-oops[1256]: 
abrt-dump-journal-oops: Found oopses: 2
Jul 15 10:35:06 workstation abrt-dump-journal-oops[1256]: 
abrt-dump-journal-oops: Creating problem directories
Jul 15 10:35:06 workstation abrtd[890]: Too many clients, refusing connections 
to '/var/run/abrt/abrt.socket'
Jul 15 10:35:06 workstation abrt-notification[6205]: System encountered a 
non-fatal error in ??()

Thanks.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Hundreds of kernel crash messages after Fedora 26 upgrade. We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64 crashed.

[Samuel Sieb]

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.11.10-300.fc26.x86_64 
crashed. Please contact the developer if you want to report the issue.
We're sorry, it looks like a problem occurred. If you'd like to help resolve 
the issue, please send a report.


In a terminal can you run "sudo journalctl -b" and see if you can find 
the crash info?  You should be able to press "G" (that's a *capital* G) 
to get to the most recent entries, then you can scroll back if necessary.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Hundreds of kernel crash messages after Fedora 26 upgrade. We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64 crashed.

[Sudhir Khanger]

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're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.10-300.fc26.x86_64 
crashed. Please contact the developer if you want to report the issue.
We're sorry, it looks like a problem occurred. If you'd like to help resolve 
the issue, please send a report.


I am so regretting upgrading to Fedora 26.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Hundreds of kernel crash messages after Fedora 26 upgrade. We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64 crashed.

[Samuel Sieb]

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't submit. How do I resolve it.


Is there any information about the crash?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Hundreds of kernel crash messages after Fedora 26 upgrade. We're sorry, it looks like BOOT_IMAGE=/boot/vmlinuz-4.11.9-300.fc26.x86_64 crashed.

[stan]

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 1000 of reports that I can't submit. How do I resolve
> it.

Do you have another kernel you can boot into?  I see that there is a 
later kernel available at koji.
https://koji.fedoraproject.org/koji/buildinfo?buildID=917926
You could download the needed rpms and locally install them using
dnf -C install
from the directory where they are.  It might even be available in
updates-testing if you enable the updates-testing repository
in /etc/yum.repos.d.  Set the enabled= line to 1 from 0, and disable it
after you are done by setting it back to 0.
Or try an earlier kernel
https://koji.fedoraproject.org/koji/buildinfo?buildID=913371
if there isn't one available to you in the boot menu.  There is
something seriously wrong if the kernel continues crashing.  

You could also try a different desktop.  It's possible that there is a
bug in Plasma that is causing the crashes.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org