I tried with IOMMU Enabled, and with IOMMU disabled and iommu=soft inSeems like an update to kernel 5.10.43 failed part way through, so had
Grub - no improvement.
I suspect the problem lies in the graphical environment - the screen
froze for about 20 minutes but is now responding again. While frozen,
the system still served files via NFS to other systems. Certaily some of
the freezes seemed to occur in connection with mouse movements/button presses.
Thought I might follow the wiki How to set up the graphical server with Nouveau as an alternative to the nVidia driver. Now I get "Invalid magic number" message, but there seems to be no posts that correct this. An
ideas please?
On 21/06/2021 15:41, Grimble wrote:
I tried with IOMMU Enabled, and with IOMMU disabled and iommu=soft inSeems like an update to kernel 5.10.43 failed part way through, so had
Grub - no improvement.
I suspect the problem lies in the graphical environment - the screen
froze for about 20 minutes but is now responding again. While frozen,
the system still served files via NFS to other systems. Certaily some of
the freezes seemed to occur in connection with mouse movements/button
presses.
Thought I might follow the wiki How to set up the graphical server with
Nouveau as an alternative to the nVidia driver. Now I get "Invalid magic
number" message, but there seems to be no posts that correct this. An
ideas please?
to drop back to 5.10.41. Change to nouveau worked but I'm not optimistic
the problem's solved - Chrome bombed as soon as I launched it.
On Tue, 22 Jun 2021 14:19:09 -0400, grimble <grimble@nomail.afraid.org> wrote:
On 21/06/2021 15:41, Grimble wrote:
I tried with IOMMU Enabled, and with IOMMU disabled and iommu=soft inSeems like an update to kernel 5.10.43 failed part way through, so had
Grub - no improvement.
I suspect the problem lies in the graphical environment - the screen
froze for about 20 minutes but is now responding again. While frozen,
the system still served files via NFS to other systems. Certaily some of >>> the freezes seemed to occur in connection with mouse movements/button
presses.
Thought I might follow the wiki How to set up the graphical server with
Nouveau as an alternative to the nVidia driver. Now I get "Invalid magic >>> number" message, but there seems to be no posts that correct this. An
ideas please?
to drop back to 5.10.41. Change to nouveau worked but I'm not optimistic
the problem's solved - Chrome bombed as soon as I launched it.
More info about how the update failed is needed. Did it run out of space?
Regards, Dave Hodgins
I noticed several of the 5.10.43
files in /boot, such as vmlinuz- and sysvers- were 0 B.
On Wed, 23 Jun 2021 14:56:33 +0100, Grimble wrote:
I noticed several of the 5.10.43
files in /boot, such as vmlinuz- and sysvers- were 0 B.
Then those are failures. /boot should look something like this snippet:
239K Jun 11 02:33 config-5.10.43-desktop-1.mga8
4.0K Dec 26 08:34 dracut
4.0K Jun 14 09:21 grub2
17M Jun 14 09:12 initrd-5.10.43-desktop-1.mga8.img
33 Jun 14 09:13 initrd-desktop.img -> initrd-5.10.43-desktop-1.mga8.img
33 Jun 14 09:13 initrd.img -> initrd-5.10.43-desktop-1.mga8.img
193K Jun 11 02:33 symvers-5.10.43-desktop-1.mga8.xz
4.8M Jun 11 02:33 System.map-5.10.43-desktop-1.mga8
30 Jun 14 09:13 vmlinuz -> vmlinuz-5.10.43-desktop-1.mga8
7.7M Jun 11 02:33 vmlinuz-5.10.43-desktop-1.mga8
30 Jun 14 09:13 vmlinuz-desktop -> vmlinuz-5.10.43-desktop-1.mga8
On 23/06/2021 17:41, Bit Twister wrote:
On Wed, 23 Jun 2021 14:56:33 +0100, Grimble wrote:Thanks, Bit. Fortunately 5.10.45 installed without problems.
I noticed several of the 5.10.43
files in /boot, such as vmlinuz- and sysvers- were 0 B.
Then those are failures. /boot should look something like this snippet:
239K Jun 11 02:33 config-5.10.43-desktop-1.mga8
4.0K Dec 26 08:34 dracut
4.0K Jun 14 09:21 grub2
17M Jun 14 09:12 initrd-5.10.43-desktop-1.mga8.img
33 Jun 14 09:13 initrd-desktop.img -> initrd-5.10.43-desktop-1.mga8.img >> 33 Jun 14 09:13 initrd.img -> initrd-5.10.43-desktop-1.mga8.img
193K Jun 11 02:33 symvers-5.10.43-desktop-1.mga8.xz
4.8M Jun 11 02:33 System.map-5.10.43-desktop-1.mga8
30 Jun 14 09:13 vmlinuz -> vmlinuz-5.10.43-desktop-1.mga8
7.7M Jun 11 02:33 vmlinuz-5.10.43-desktop-1.mga8
30 Jun 14 09:13 vmlinuz-desktop -> vmlinuz-5.10.43-desktop-1.mga8
However,
we're still trying to find the root cause of this instability.
On Thu, 24 Jun 2021 12:55:34 +0100, Grimble wrote:<Snipping out all your useful code >
On 23/06/2021 17:41, Bit Twister wrote:
On Wed, 23 Jun 2021 14:56:33 +0100, Grimble wrote:Thanks, Bit. Fortunately 5.10.45 installed without problems.
I noticed several of the 5.10.43
files in /boot, such as vmlinuz- and sysvers- were 0 B.
Then those are failures. /boot should look something like this snippet:
239K Jun 11 02:33 config-5.10.43-desktop-1.mga8
4.0K Dec 26 08:34 dracut
4.0K Jun 14 09:21 grub2
17M Jun 14 09:12 initrd-5.10.43-desktop-1.mga8.img
33 Jun 14 09:13 initrd-desktop.img -> initrd-5.10.43-desktop-1.mga8.img
33 Jun 14 09:13 initrd.img -> initrd-5.10.43-desktop-1.mga8.img
193K Jun 11 02:33 symvers-5.10.43-desktop-1.mga8.xz
4.8M Jun 11 02:33 System.map-5.10.43-desktop-1.mga8
30 Jun 14 09:13 vmlinuz -> vmlinuz-5.10.43-desktop-1.mga8
7.7M Jun 11 02:33 vmlinuz-5.10.43-desktop-1.mga8
30 Jun 14 09:13 vmlinuz-desktop -> vmlinuz-5.10.43-desktop-1.mga8
Well that is a step forward. Since the old kernels did not compile you
might consider using mcc to remove them.
However,
we're still trying to find the root cause of this instability.
Yes I have been following the thread. Maybe enabling core dump might give
you a chance to find out why.
On 24/06/2021 13:13, Bit Twister wrote:
On Thu, 24 Jun 2021 12:55:34 +0100, Grimble wrote:<Snipping out all your useful code >
On 23/06/2021 17:41, Bit Twister wrote:
On Wed, 23 Jun 2021 14:56:33 +0100, Grimble wrote:Thanks, Bit. Fortunately 5.10.45 installed without problems.
I noticed several of the 5.10.43
files in /boot, such as vmlinuz- and sysvers- were 0 B.
Then those are failures. /boot should look something like this snippet: >>>>
239K Jun 11 02:33 config-5.10.43-desktop-1.mga8
4.0K Dec 26 08:34 dracut
4.0K Jun 14 09:21 grub2
17M Jun 14 09:12 initrd-5.10.43-desktop-1.mga8.img
33 Jun 14 09:13 initrd-desktop.img -> initrd-5.10.43-desktop-1.mga8.img
33 Jun 14 09:13 initrd.img -> initrd-5.10.43-desktop-1.mga8.img
193K Jun 11 02:33 symvers-5.10.43-desktop-1.mga8.xz
4.8M Jun 11 02:33 System.map-5.10.43-desktop-1.mga8
30 Jun 14 09:13 vmlinuz -> vmlinuz-5.10.43-desktop-1.mga8
7.7M Jun 11 02:33 vmlinuz-5.10.43-desktop-1.mga8
30 Jun 14 09:13 vmlinuz-desktop -> vmlinuz-5.10.43-desktop-1.mga8 >>>>
Well that is a step forward. Since the old kernels did not compile you
might consider using mcc to remove them.
However,
we're still trying to find the root cause of this instability.
Yes I have been following the thread. Maybe enabling core dump might give
you a chance to find out why.
Did all that, launched firefox, got immediate message:
Exiting due to channel error
Crash annotation GraphicsCriticalError Receive IPC close with reason=AbnormalShutdown (t=1.32075)
So, now I have 550MB of crash data. What to do with it?
Did all that, launched firefox, got immediate message:
Exiting due to channel error
Crash annotation GraphicsCriticalError Receive IPC close with reason=AbnormalShutdown (t=1.32075)
So, now I have 550MB of crash data. What to do with it?
<Snipping out all your useful code >
On Fri, 25 Jun 2021 17:18:50 +0100, Grimble wrote:
Did all that, launched firefox, got immediate message:
Exiting due to channel error
Crash annotation GraphicsCriticalError Receive IPC close with
reason=AbnormalShutdown (t=1.32075)
So, now I have 550MB of crash data. What to do with it?
Delete it unless you want to just practice on it. The kill command was
just to cause firefox to create a dump and that you can create a core file.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 75:57:32 |
Calls: | 6,657 |
Calls today: | 3 |
Files: | 12,203 |
Messages: | 5,332,730 |
Posted today: | 1 |