Re: fedora 37 network issues with current kernel vmlinuz-6.2.10-200.fc37.x86_64

> > I have a VLAN on 201 and PPPoE setup (century link ISP). > > > > This has worked fine for some time, and it works with kernel: > > > > vmlinuz-6.2.9-200.fc37.x86_64 > > > > But fails with the most recent kernel: > > > > vmlinuz-6.

Re: fedora 37 network issues with current kernel vmlinuz-6.2.10-200.fc37.x86_64

me time, and it works with kernel: > > vmlinuz-6.2.9-200.fc37.x86_64 > > But fails with the most recent kernel: > > vmlinuz-6.2.10-200.fc37.x86_64 > > Any hints or pointers to open issues for this? Opened a bug for this: https:

fedora 37 network issues with current kernel vmlinuz-6.2.10-200.fc37.x86_64

I don't know exactly what's wrong, it's been a while since I setup the network for this. I have a VLAN on 201 and PPPoE setup (century link ISP). This has worked fine for some time, and it works with kernel: vmlinuz-6.2.9-200.fc37.x86_64 But fails with the mos

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.

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.

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.

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

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.

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

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.

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

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.

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

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

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.

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

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.

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

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 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

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.

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

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.

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=/bo

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.

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

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.

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 t

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.

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_6

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.

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

Re: Fedora 23 KDE spin / XEN / virt-manager and vmlinuz-4.3.3-301.fc23.x86_64

On 01/18/2016 03:05 PM, Outback Dingo wrote: > a recent update installed kernel-4.3.3 so i reset the xen efi > configuration, booted got into the desktop no problems. The issue > arises when trying to launch vms from virt-manager, it always throws > a virt-manager viewer connection to hypervisor

Re: Fedora 23 KDE spin / XEN / virt-manager and vmlinuz-4.3.3-301.fc23.x86_64

On 01/19/2016 10:42 AM, Outback Dingo wrote: > > > On Tue, Jan 19, 2016 at 4:32 PM, Cole Robinson > wrote: > > On 01/18/2016 03:05 PM, Outback Dingo wrote: > > So my environment > > > > Fedora 23 KDE spin > > XEN-4.5.2 and kernel 4.2.8 booted via

Re: Fedora 23 KDE spin / XEN / virt-manager and vmlinuz-4.3.3-301.fc23.x86_64

On Tue, Jan 19, 2016 at 4:32 PM, Cole Robinson wrote: > On 01/18/2016 03:05 PM, Outback Dingo wrote: > > So my environment > > > > Fedora 23 KDE spin > > XEN-4.5.2 and kernel 4.2.8 booted via EFI where everything works fine > using > > virt-manager to manage vms under XEN, all is good. > > > > a

Re: Fedora 23 KDE spin / XEN / virt-manager and vmlinuz-4.3.3-301.fc23.x86_64

On 01/18/2016 03:05 PM, Outback Dingo wrote: > So my environment > > Fedora 23 KDE spin > XEN-4.5.2 and kernel 4.2.8 booted via EFI where everything works fine using > virt-manager to manage vms under XEN, all is good. > > a recent update installed kernel-4.3.3 so i reset the xen efi configuratio

Re: Fedora 23 KDE spin / XEN / virt-manager and vmlinuz-4.3.3-301.fc23.x86_64

On Mon, Jan 18, 2016 at 9:12 PM, jd1008 wrote: > > > On 01/18/2016 01:05 PM, Outback Dingo wrote: > >> So my environment >> >> Fedora 23 KDE spin >> XEN-4.5.2 and kernel 4.2.8 booted via EFI where everything works fine >> using virt-manager to manage vms under XEN, all is good. >> >> a recent upd

Re: Fedora 23 KDE spin / XEN / virt-manager and vmlinuz-4.3.3-301.fc23.x86_64

On 01/18/2016 01:05 PM, Outback Dingo wrote: So my environment Fedora 23 KDE spin XEN-4.5.2 and kernel 4.2.8 booted via EFI where everything works fine using virt-manager to manage vms under XEN, all is good. a recent update installed kernel-4.3.3 so i reset the xen efi configuration, boot

Fedora 23 KDE spin / XEN / virt-manager and vmlinuz-4.3.3-301.fc23.x86_64

So my environment Fedora 23 KDE spin XEN-4.5.2 and kernel 4.2.8 booted via EFI where everything works fine using virt-manager to manage vms under XEN, all is good. a recent update installed kernel-4.3.3 so i reset the xen efi configuration, booted got into the desktop no problems. The issue arise

Re: vmlinuz

On Mon, 2012-08-06 at 21:24 +0800, Ed Greshko wrote: > So, I downloaded the kernel-3.5.0-2.fc17.x86_64.rpm and extracted its > vmlinuz-3.5.0-2.fc17.x86_64 and did a diff of what is on my system and > what is on a VM. They are all identical. Yes, I realise that I mixed up vmlinux and ini

Re: vmlinuz

On Mon, 2012-08-06 at 09:03 -0700, Richard Vickery wrote: > Fwiw, you ought to be placing your comments here in the thread "boot, > linux text" as this is where Dave's comments are. He did, as I did, replied directly to a post. That's where *replies* belong, to the post they're in response to. Y

Re: vmlinuz

ne. Beside that it is a redundant point to ask > a question on behalf of someone who was already making the same request for > help, if I asked in that thread, it could have been ignored as was the guy > who had the problem. > > I looked in that thread and I didn't see any direct

Re: vmlinuz

on on behalf of someone who was already making the same request for > help, if I asked in that thread, it could have been ignored as was the guy > who had the problem. I looked in that thread and I didn't see any direct question about vmlinuz. Besides, I didn't answer or respon

Re: vmlinuz

On Mon, Aug 6, 2012 at 6:21 PM, Ed Greshko wrote: > On 08/07/2012 09:07 AM, Richard Vickery wrote: > > On Mon, Aug 6, 2012 at 1:10 PM, Ed Greshko ed.gres...@greshko.com>> wrote: > > > > On 08/07/2012 12:03 AM, Richard Vickery wrote: > > > Fwiw, you ought to be placing your comments here

Re: vmlinuz

s no working network >> hardware, or drivers for all your disc drives, et cetera). >> > > FWIW, I'd not give vmlinuz much thought > > So, I downloaded the kernel-3.5.0-2.fc17.x86_64.rpm and extracted its vmlinuz-3.5.0-2.fc17.x86_64 and did a diff of what is on my sy

Re: vmlinuz

On 08/07/2012 09:07 AM, Richard Vickery wrote: > On Mon, Aug 6, 2012 at 1:10 PM, Ed Greshko > wrote: > > On 08/07/2012 12:03 AM, Richard Vickery wrote: > > Fwiw, you ought to be placing your comments here in the thread "boot, > linux text" as this is where D

Re: vmlinuz

On Mon, Aug 6, 2012 at 1:10 PM, Ed Greshko wrote: > On 08/07/2012 12:03 AM, Richard Vickery wrote: > > Fwiw, you ought to be placing your comments here in the thread "boot, > linux text" as this is where Dave's comments are. > > No, I shouldn't. I am answering a comment made by Tim in this threa

Re: vmlinuz

On 08/07/2012 12:03 AM, Richard Vickery wrote: > Fwiw, you ought to be placing your comments here in the thread "boot, linux > text" as this is where Dave's comments are. No, I shouldn't. I am answering a comment made by Tim in this thread. -- Programming today is a race between software engi

Re: vmlinuz

On Mon, Aug 6, 2012 at 11:28 AM, Suvayu Ali wrote: > On Mon, Aug 06, 2012 at 09:03:16AM -0700, Richard Vickery wrote: > > Fwiw, you ought to be placing your comments here in the thread "boot, > linux > > text" as this is where Dave's comments are. > > > > On Aug 6, 2012 6:25 AM, "Ed Greshko" wrot

Re: vmlinuz

On Mon, Aug 06, 2012 at 09:03:16AM -0700, Richard Vickery wrote: > Fwiw, you ought to be placing your comments here in the thread "boot, linux > text" as this is where Dave's comments are. > > On Aug 6, 2012 6:25 AM, "Ed Greshko" wrote: > > On 08/06/2012 07:43 PM, Tim wrote: > > On Sun,

Re: vmlinuz

7;t have what someone else needs to boot up, or may > > boot up but be lacking something important (such as no working network > > hardware, or drivers for all your disc drives, et cetera). > > > > FWIW, I'd not give vmlinuz much thought > > So, I downloaded th

Re: vmlinuz

cluding the things you need for your PC > to boot. It mightn't have what someone else needs to boot up, or may > boot up but be lacking something important (such as no working network > hardware, or drivers for all your disc drives, et cetera). > FWIW, I'd not give vmlinuz

Re: vmlinuz

On Sun, 2012-08-05 at 22:37 -0700, Richard Vickery wrote: > is it possible to use an image from another user Maybe... If I recall correctly, it's custom-built for your computer's hardware when the kernel is installed, including the things you need for your PC to boot. It mightn't have what someo

Re: vmlinuz

On 06.08.2012 07:37, Richard Vickery wrote: > Hi everyone: > > Had a question about a boot image from Dave. I don't know if it is vmlinuz, > but there is a image file missing that prevents him from booting up. Is it > possible to use an image from another user, or does he nee

vmlinuz

Hi everyone: Had a question about a boot image from Dave. I don't know if it is vmlinuz, but there is a image file missing that prevents him from booting up. Is it possible to use an image from another user, or does he need to re-install it? -- users mailing list users@lists.fedoraproject.o