Re: [arch-general] Fwd: Kernel panic - after upgrade
2015-02-01 13:42 GMT+01:00 Guus Snijders <gsnijders@gmail.com>:
Op 1 feb. 2015 12:41 schreef "Csányi Pál" <csanyipal@gmail.com> het volgende:
2015-01-31 23:12 GMT+01:00 Guus Snijders <gsnijders@gmail.com>:
2015-01-31 21:20 GMT+01:00 Christian Demsar <vixsomnis@fastmail.com>: [...]
At this point, I'd backup configuration files and home directories and do a full reinstall. Sounds like there's something going terribly wrong. Hopefully that works...
Hmm, I'd first check if dmesg shows SATA error (bus reset, seek failed, etc) and if that is not the case, I'd do a memory test (memtest86 is very nice for this). Seeing that the OP is getting kernel panics, my first guess is memory problems (I fail to see how a bad HDD would cause panics), but I might be wrong...
The output of dmesg is here: http://pastebin.com/9TnBGHqn
I did not see any suspicious in it. Am I right?
A couple of things i noticed: -Nvidea complaining about not having a textmode driver configured - ext4 mentions 14 errors on sda4
I'm not sure if these are serious or not. Could you try the memtest first? Bad memory can cause very strange errors and is easy to test (takes time, though).
Before I start the memtest I ask an advice: how long should I run the memtest? -- Regards from Pal
Just do two or three passes that should be enough. Am 01.02.2015 um 13:48 schrieb Csányi Pál: > 2015-02-01 13:42 GMT+01:00 Guus Snijders <gsnijders@gmail.com>: >> Op 1 feb. 2015 12:41 schreef "Csányi Pál" <csanyipal@gmail.com> het >> volgende: >> >>> 2015-01-31 23:12 GMT+01:00 Guus Snijders <gsnijders@gmail.com>: >>>> 2015-01-31 21:20 GMT+01:00 Christian Demsar <vixsomnis@fastmail.com>: >>>> [...] >>>>> At this point, I'd backup configuration files and home directories and >>>>> do a full reinstall. Sounds like there's something going terribly >>>>> wrong. >>>>> Hopefully that works... >>>> Hmm, I'd first check if dmesg shows SATA error (bus reset, seek >>>> failed, etc) and if that is not the case, I'd do a memory test >>>> (memtest86 is very nice for this). >>>> Seeing that the OP is getting kernel panics, my first guess is memory >>>> problems (I fail to see how a bad HDD would cause panics), but I might >>>> be wrong... >>> The output of dmesg is here: >>> http://pastebin.com/9TnBGHqn >>> >>> I did not see any suspicious in it. Am I right? >> A couple of things i noticed: >> -Nvidea complaining about not having a textmode driver configured >> - ext4 mentions 14 errors on sda4 >> >> I'm not sure if these are serious or not. Could you try the memtest first? >> Bad memory can cause very strange errors and is easy to test (takes time, >> though). > Before I start the memtest I ask an advice: how long should I run the memtest? >
2015-02-01 17:42 GMT+01:00 Marcel Kleinfeller <marcel@oompf.de>:
Just do two or three passes that should be enough. Am 01.02.2015 um 13:48 schrieb Csányi Pál:
2015-02-01 13:42 GMT+01:00 Guus Snijders <gsnijders@gmail.com>:
Op 1 feb. 2015 12:41 schreef "Csányi Pál" <csanyipal@gmail.com> het volgende:
2015-01-31 23:12 GMT+01:00 Guus Snijders <gsnijders@gmail.com>:
2015-01-31 21:20 GMT+01:00 Christian Demsar <vixsomnis@fastmail.com>: [...]
At this point, I'd backup configuration files and home directories and do a full reinstall. Sounds like there's something going terribly wrong. Hopefully that works...
Hmm, I'd first check if dmesg shows SATA error (bus reset, seek failed, etc) and if that is not the case, I'd do a memory test (memtest86 is very nice for this). Seeing that the OP is getting kernel panics, my first guess is memory problems (I fail to see how a bad HDD would cause panics), but I might be wrong...
The output of dmesg is here: http://pastebin.com/9TnBGHqn
I did not see any suspicious in it. Am I right?
A couple of things i noticed: -Nvidea complaining about not having a textmode driver configured - ext4 mentions 14 errors on sda4
I'm not sure if these are serious or not. Could you try the memtest first? Bad memory can cause very strange errors and is easy to test (takes time, though).
Before I start the memtest I ask an advice: how long should I run the memtest?
I did the memtest twice: yesterday two pass with 0 error and today two pass with 0 error, all together this takes 8 h 30 min. So I can tell that the RAM is all right on this desktop PC box, right? What do you advices me, what to do further? Should I try to investigate the sda4 error or not? Can I do something with the nvidia error? Or just do a fresh install of my Arch system ( but first backup /etc/ and $HOME directory with all my setup? ) -- Regards from Pal
On Mon, 2 Feb 2015 17:29:25 +0100, Csányi Pál wrote:
So I can tell that the RAM is all right on this desktop PC box, right?
Most likely the main memory is _not_ defect. However, when passing the memtest it's without guarantee that the RAM is ok and if there would have been errors, it also wouldn't necessarily mean that the RAM is broken. Memtest isn't perfect. But since we are talking about "Voodoo", have you checked, if your power supply is able to handle the worst case scenario? Have you replaced the battery? Power supply and the battery unlikely are the culprits either, but both could cause "Voodoo" too. I suspect that it's a software issue or unlikely a very wicked hardware issue. Have you checked the homepage of your mobo regarding BIOS updates (or whatever the "BIOS" is called nowadays). Are there changelogs that ever mentioned Linux incompatibilities? The very last thing I would do, is to care about strange "Voodoo". I would test Arch's Linux LTS, downgrade systemd and similar. Most likely it's a user issue, or a complete incompatibility to Linux of some hardware component. I returned several times hardware that was mentioned by the vendors by Linux communities as Linux compatible and not seldom it put out, that there was one revision, chipset nobody cared about, neither the communities, nor the vendors or nobody did use all features of the hardware. Backup your current install and make a clean new install. Replace the default kernel with https://www.archlinux.org/packages/core/x86_64/linux-lts/ or with linux-rt-lts from the Arch Audio repository or from AUR, since it's 3.10..., don't worry about the Rt-patch, when instlling it just for testing purpose.
2015-02-02 18:27 GMT+01:00 Ralf Mardorf <ralf.mardorf@rocketmail.com>:
On Mon, 2 Feb 2015 17:29:25 +0100, Csányi Pál wrote:
So I can tell that the RAM is all right on this desktop PC box, right?
Most likely the main memory is _not_ defect. However, when passing the memtest it's without guarantee that the RAM is ok and if there would have been errors, it also wouldn't necessarily mean that the RAM is broken. Memtest isn't perfect. But since we are talking about "Voodoo", have you checked, if your power supply is able to handle the worst case scenario? Have you replaced the battery? Power supply and the battery unlikely are the culprits either, but both could cause "Voodoo" too.
I don't know how to check if my power supply is able to handle the worst case scenario? No, I haven't replaced the battery.
Have you checked the homepage of your mobo regarding BIOS updates (or whatever the "BIOS" is called nowadays). Are there changelogs that ever mentioned Linux incompatibilities?
No, I did not checked that. I did not dare even to update the BIOS.
The very last thing I would do, is to care about strange "Voodoo". I would test Arch's Linux LTS, downgrade systemd and similar.
Most likely it's a user issue, or a complete incompatibility to Linux of some hardware component. I returned several times hardware that was mentioned by the vendors by Linux communities as Linux compatible and not seldom it put out, that there was one revision, chipset nobody cared about, neither the communities, nor the vendors or nobody did use all features of the hardware.
This hardware on which I'm running my Arch linux system I have used since 3-4 years. During this time I did run on this hardware Debian GNU/Linux SID, Arch linux, Parabolagnulinux and finally Arch linux again. Wowever, so far I did not have any hardware issues, as far as I know.
Backup your current install and make a clean new install. Replace the default kernel with https://www.archlinux.org/packages/core/x86_64/linux-lts/ or with linux-rt-lts from the Arch Audio repository or from AUR, since it's 3.10..., don't worry about the Rt-patch, when instlling it just for testing purpose.
I shall do that. Thank you for your advices and support. -- Regards from Pal
On Mon, 2 Feb 2015 19:27:57 +0100 Csányi Pál <csanyipal@gmail.com> wrote:
2015-02-02 18:27 GMT+01:00 Ralf Mardorf <ralf.mardorf@rocketmail.com>:
On Mon, 2 Feb 2015 17:29:25 +0100, Csányi Pál wrote:
So I can tell that the RAM is all right on this desktop PC box, right?
Most likely the main memory is _not_ defect. However, when passing the memtest it's without guarantee that the RAM is ok and if there would have been errors, it also wouldn't necessarily mean that the RAM is broken. Memtest isn't perfect. But since we are talking about "Voodoo", have you checked, if your power supply is able to handle the worst case scenario? Have you replaced the battery? Power supply and the battery unlikely are the culprits either, but both could cause "Voodoo" too.
I don't know how to check if my power supply is able to handle the worst case scenario? Put your machine under heavy load and connect a digital volt meter to the +5 0v lines ie Red and Black wires going to a floppy drive cable then check the yellow and black 12 volts if they vary too much under load but recover when load is removed the the PSU is not big enough .
No, I haven't replaced the battery.
Have you checked the homepage of your mobo regarding BIOS updates (or whatever the "BIOS" is called nowadays). Are there changelogs that ever mentioned Linux incompatibilities?
No, I did not checked that. I did not dare even to update the BIOS.
The very last thing I would do, is to care about strange "Voodoo". I would test Arch's Linux LTS, downgrade systemd and similar.
Most likely it's a user issue, or a complete incompatibility to Linux of some hardware component. I returned several times hardware that was mentioned by the vendors by Linux communities as Linux compatible and not seldom it put out, that there was one revision, chipset nobody cared about, neither the communities, nor the vendors or nobody did use all features of the hardware.
This hardware on which I'm running my Arch linux system I have used since 3-4 years. During this time I did run on this hardware Debian GNU/Linux SID, Arch linux, Parabolagnulinux and finally Arch linux again. Wowever, so far I did not have any hardware issues, as far as I know.
Backup your current install and make a clean new install. Replace the default kernel with https://www.archlinux.org/packages/core/x86_64/linux-lts/ or with linux-rt-lts from the Arch Audio repository or from AUR, since it's 3.10..., don't worry about the Rt-patch, when instlling it just for testing purpose.
I shall do that. Thank you for your advices and support.
Pete . -- Illegitimi non carborundum . ro for the purists out there Noli nothis permittere te terere.
2015-02-02 18:27 GMT+01:00 Ralf Mardorf <ralf.mardorf@rocketmail.com>:
Most likely it's a user issue,
I confess I did many times system upgrade without taking into account the advice given here: https://wiki.archlinux.org/index.php/General_recommendations <quoted> it is imperative to keep up to date with changes in Arch Linux that require manual intervention before upgrading your system. Subscribe to the arch-announce mailing list or check the front page Arch news every time before you update. etc.. </quote>
Backup your current install and make a clean new install. Replace the default kernel with https://www.archlinux.org/packages/core/x86_64/linux-lts/ or with linux-rt-lts from the Arch Audio repository or from AUR, since it's 3.10..., don't worry about the Rt-patch, when instlling it just for testing purpose.
I did so. I have now a fresh install of Arch linux with kernel 3.14.31-1-lts . -- Regards from Pal
participants (4)
-
Csányi Pál
-
Marcel Kleinfeller
-
pete nikolic
-
Ralf Mardorf