Re: Lenovo 050 desktop crashing
On 2015-02-25, Sharon Kimble boudic...@skimble.plus.com wrote: Nope, its a Lenovo 050 Desktop from ebuyer Lenovo E50. -- The world is full of shipping clerks who have read the Harvard Classics. — Charles Bukowski -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnmermin.354.cu...@einstein.electron.org
Re: Lenovo 050 desktop crashing
Patrick Bartek nemomm...@gmail.com writes: On Tue, 24 Feb 2015, Sharon Kimble wrote: Patrick Bartek nemomm...@gmail.com writes: On Tue, 24 Feb 2015, Sharon Kimble wrote: I have just bought a new computer,a Lenovo 050 desktop. Its working I couldn't find an 050 model. Did you mean H50? Nope, its a Lenovo 050 Desktop from ebuyer http://www.ebuyer.com/658956-lenovo-e50-desktop-pc-90bx0018uk Couldn't find that model listed anywhere. Even searched ebuyer's site. Nothing. Just trying to get the specs on it. Curious. No matter as it seems installing watchdog solved your problem. Although, why watchdog wasn't installed in the first place or why it needed to be installed at all. ??? It's not on my Wheezy system, and I have no problems. Of course, my current system is 1 to 8 years old depending on which part. ;-) It seems that something was calling watchdog, which wasn't installed, so it seems that everything froze because of it. reasonably okay except for the occasional crashes. For instance, I've had it a fortnight now and its longest uptime has been just over 3 days, even though its on all the time! What OS did it come with Windows 7 or 8? Did the machine crash when running Windows? If yes, you could have a hardware problem. If no, then it's probably a Linux problem. 8.1, which was very soon removed to install wheezy to upgrade to jessie. You seemed to have installed Jessie 32-bit based on your other posting -- installed watchedog . . . i386. What version of Jessie? It's at RC1 as of 25 Jan. It was installed on 10th February, a netinstall of wheezy. Then upgraded to jessie on the same day. Dual boot or did you wipe out Windows? GNOME3 desktop? Fluxbox, I went into gnome once whilst I installed fluxbox, and there I remain. When GNOME went to 3, I stopped using GNOME. It caused more problems than it was worth. Even installing another environment or just using a window manager, it still got in the way. Ultimately, when I upgraded to Debian Wheezy (from Fedora 12) I did a netinstall, Basic System. Added what I wanted -- X, etc. -- service by service, app by app. You should be able to choose which environment or window manager you want on the login page. If you set Fluxbox as the Default, system should boot to it the next time and every time until you change it. Here's what I'd do. Start over from zero. You could have a corrupted install. Wipe out your current Jessie. Download and install the most current 64-bit version. Do a checksum on the download itself and the CD or DVD after burning. Depending on your Internet connection, a netinstall CD will get you an up-to-date system when the install is completed. Everything is working okay, that crashing was the only problem, so thanks, but I'm staying with it as it is. The setup was missing watchdog which is now installed. But it is a good idea to get a new 64-bit version, my install disk was burnt on 28 May 2013 so it does need to be replaced. You said you upgraded from Wheezy. When or if, you reinstall Jessie, just get the latest version and do a clean install. I've never done a distribution upgrade that didn't require fixing in some way or other. Clean installs are the least problematical. Good advice, which I'm going to follow. Thanks Sharon. -- A taste of linux = http://www.sharons.org.uk my git repo = https://bitbucket.org/boudiccas/dots TGmeds = http://www.tgmeds.org.uk Debian testing, fluxbox 1.3.6, emacs 24.4.1.0 signature.asc Description: PGP signature
Re: Lenovo 050 desktop crashing
David Christensen dpchr...@holgerdanske.com writes: On 02/24/2015 03:23 AM, Sharon Kimble wrote: I have just bought a new computer,a Lenovo 050 desktop. Its working reasonably okay except for the occasional crashes. ... It has crashed when I've been using it, and its crashed overnight whilst I've been asleep! There does not seem to be any pattern to it, or any noticeable trigger. A failing power supply and/or off-spec memory module can cause unpredictable lock-up's. I use an inexpensive ATX power supply tester for quick pass/fail testing: http://www.newegg.com/Product/Product.aspx?Item=N82E16899129001 I use memtest86+ for checking RAM: http://www.memtest.org/ Run memtest86+ for at least 12 hours; better 24. I've seen machines with infrequent lock-up problems pass an hour or more of testing, only to fail once or twice in later hours. If your new computer fails either of the above, return it. If the memory and power supply test out okay, then understand that the whole point of the Debian testing release is to find bugs. Here is your opportunity to do so. This is the second release that I've run as testing, so I'm well used to sorting stuff out when it breaks, but this situation had me beat as it had never happened before! On 02/24/2015 10:56 AM, Sharon Kimble wrote: It was installed on 10th February, a netinstall of wheezy. Then upgraded to jessie on the same day. On 02/24/2015 10:56 AM, Sharon Kimble wrote: But it is a good idea to get a new 64-bit version, my install disk was burnt on 28 May 2013 so it does need to be replaced. If you're going to re-install, a fresh ISO would be a good idea. I typically run amd64 on compatible hardware, but i386 with PAE (default) supports more than 4 GB of RAM too. Installing and running Wheezy for a week or so should narrow the possibilities. Its something that I'm bearing in mind if I need it for the future. Sharon. -- A taste of linux = http://www.sharons.org.uk my git repo = https://bitbucket.org/boudiccas/dots TGmeds = http://www.tgmeds.org.uk Debian testing, fluxbox 1.3.6, emacs 24.4.1.0 signature.asc Description: PGP signature
Re: Lenovo 050 desktop crashing
Eike Lantzsch zp6...@gmx.net writes: On Tuesday 24 February 2015 18:56:23 Sharon Kimble wrote: Patrick Bartek nemomm...@gmail.com writes: On Tue, 24 Feb 2015, Sharon Kimble wrote: I have just bought a new computer,a Lenovo 050 desktop. Its working I couldn't find an 050 model. Did you mean H50? Nope, its a Lenovo 050 Desktop from ebuyer. reasonably okay except for the occasional crashes. For instance, I've had it a fortnight now and its longest uptime has been just over 3 days, even though its on all the time! What OS did it come with Windows 7 or 8? Did the machine crash when running Windows? If yes, you could have a hardware problem. If no, then it's probably a Linux problem. 8.1, which was very soon removed to install wheezy to upgrade to jessie. You seemed to have installed Jessie 32-bit based on your other posting -- installed watchedog . . . i386. What version of Jessie? It's at RC1 as of 25 Jan. It was installed on 10th February, a netinstall of wheezy. Then upgraded to jessie on the same day. Dual boot or did you wipe out Windows? GNOME3 desktop? Fluxbox, I went into gnome once whilst I installed fluxbox, and there I remain. Here's what I'd do. Start over from zero. You could have a corrupted install. Wipe out your current Jessie. Download and install the most current 64-bit version. Do a checksum on the download itself and the CD or DVD after burning. Depending on your Internet connection, a netinstall CD will get you an up-to-date system when the install is completed. Everything is working okay, that crashing was the only problem, so thanks, but I'm staying with it as it is. The setup was missing watchdog which is now installed. But it is a good idea to get a new 64-bit version, my install disk was burnt on 28 May 2013 so it does need to be replaced. It has crashed when I've been using it, and its crashed overnight whilst I've been asleep! There does not seem to be any pattern to it, or any noticeable trigger. When it crashes, the screen freezes, and both the usb keyboard and mouse freeze, and can not be used. Sounds like a kernel crash. Does the screen go black (or another color) like the computer was turned off, or does the desktop image remain? When it crashed *everything* just froze, the keyboard, the desktop, the monitor, time stood still! Did you, by any chance, install a 3.19-trunk Kernel? That one crashes on my desktop too while 3.18 works flawlessly. Eike Nope, its a 3.16.0-4-686-pae, bog-standard kernel. Sharon. -- A taste of linux = http://www.sharons.org.uk my git repo = https://bitbucket.org/boudiccas/dots TGmeds = http://www.tgmeds.org.uk Debian testing, fluxbox 1.3.6, emacs 24.4.1.0 signature.asc Description: PGP signature
Re: Lenovo 050 desktop crashing
On 02/25/2015 06:11 AM, Sharon Kimble wrote: You said you upgraded from Wheezy. When or if, you reinstall Jessie, just get the latest version and do a clean install. I've never done a distribution upgrade that didn't require fixing in some way or other. Clean installs are the least problematical. Good advice, which I'm going to follow. Thanks Sharon. Something I would like for you to try first before you do anything else is to do a search for free and non-free firmware and install what is missing from your system and then install the package upgrade-system and run 'upgrade-system' from the console, let it do what it wants to do even though what it will want to do may scare you, this software script has never let me down, never, and I run many systems from stable to sid. If more people ran upgrade-system I would see less problems in this group. -- Jimmy Johnson Debian - Wheezy - KDE 4.8.4 - AMD64 - EXT4 at sda1 Registered Linux User #380263 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54edf259.1040...@gmail.com
Re: Lenovo 050 desktop crashing
On 02/24/2015 01:56 PM, Sharon Kimble wrote: When it crashed *everything* just froze, the keyboard, the desktop, the monitor, time stood still! I agree with the previous reply from Patrick. Install 64 bit Jessie fresh. I don't have anything 32bit installed to my machine, and don't miss it. But, if you only have 1 gig of ram, then you might have to go 32bit. Consider the tired feet remedy; Let it soak. Give your install some time to settle in, before adding new things. You might consider holding off on glance https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772113 .. as the segfault is a known error being worked on. :) Ric -- My father, Victor Moore (Vic) used to say: There are two Great Sins in the world... ..the Sin of Ignorance, and the Sin of Stupidity. Only the former may be overcome. R.I.P. Dad. http://linuxcounter.net/user/44256.html -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54eceb57.3080...@gmail.com
Re: Lenovo 050 desktop crashing
On Tuesday 24 February 2015 18:56:23 Sharon Kimble wrote: Patrick Bartek nemomm...@gmail.com writes: On Tue, 24 Feb 2015, Sharon Kimble wrote: I have just bought a new computer,a Lenovo 050 desktop. Its working I couldn't find an 050 model. Did you mean H50? Nope, its a Lenovo 050 Desktop from ebuyer. reasonably okay except for the occasional crashes. For instance, I've had it a fortnight now and its longest uptime has been just over 3 days, even though its on all the time! What OS did it come with Windows 7 or 8? Did the machine crash when running Windows? If yes, you could have a hardware problem. If no, then it's probably a Linux problem. 8.1, which was very soon removed to install wheezy to upgrade to jessie. You seemed to have installed Jessie 32-bit based on your other posting -- installed watchedog . . . i386. What version of Jessie? It's at RC1 as of 25 Jan. It was installed on 10th February, a netinstall of wheezy. Then upgraded to jessie on the same day. Dual boot or did you wipe out Windows? GNOME3 desktop? Fluxbox, I went into gnome once whilst I installed fluxbox, and there I remain. Here's what I'd do. Start over from zero. You could have a corrupted install. Wipe out your current Jessie. Download and install the most current 64-bit version. Do a checksum on the download itself and the CD or DVD after burning. Depending on your Internet connection, a netinstall CD will get you an up-to-date system when the install is completed. Everything is working okay, that crashing was the only problem, so thanks, but I'm staying with it as it is. The setup was missing watchdog which is now installed. But it is a good idea to get a new 64-bit version, my install disk was burnt on 28 May 2013 so it does need to be replaced. It has crashed when I've been using it, and its crashed overnight whilst I've been asleep! There does not seem to be any pattern to it, or any noticeable trigger. When it crashes, the screen freezes, and both the usb keyboard and mouse freeze, and can not be used. Sounds like a kernel crash. Does the screen go black (or another color) like the computer was turned off, or does the desktop image remain? When it crashed *everything* just froze, the keyboard, the desktop, the monitor, time stood still! Did you, by any chance, install a 3.19-trunk Kernel? That one crashes on my desktop too while 3.18 works flawlessly. Eike -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2665452.LUiPIJaFZ8@lxcl01
Re: Lenovo 050 desktop crashing
On Tue, Feb 24, 2015 at 11:23:08AM +, Sharon Kimble wrote: I have just bought a new computer,a Lenovo 050 desktop. Its working reasonably okay except for the occasional crashes. For instance, I've had it a fortnight now and its longest uptime has been just over 3 days, even though its on all the time! It has crashed when I've been using it, and its crashed overnight whilst I've been asleep! There does not seem to be any pattern to it, or any noticeable trigger. When it crashes, the screen freezes, and both the usb keyboard and mouse freeze, and can not be used. In its most recent crash, it shows this in logwatch the following day --8---cut here---start-8--- - Kernel Begin WARNING: Segmentation Faults in these executables Watchdog : 2 Time(s) You appear to be running a watchdog process, which is crashing. A hardware watchdog will, generally speaking, work as follows: at boot, it will do nothing, but when an application writes a specific command to it, it will start a timer (30 seconds, 60 seconds, etc. Often configurable). When the timer expires, the watchdog will cause the computer to reset. However, when the application writes the command to the watchdog again, the timer is reset back to the start. So, as long as the watchdog process is alive, it is able to keep resetting the clock and the machine works fine. But if the processes stops (because the machine has hung, or the system is too busy), then the timer will expire, the machine will reboot and you can get back to work. In your case, though, it looks like the watchdog process is dying because of a Segmentation Fault (see the full logs or a core file for full details). At that point, even though the rest of the system is running fine, no-one is resetting the watchdog clock. WARNING: Kernel Errors Present INFO: recovery required on readonly filesyste ...: 1 Time(s) mce: [Hardware Error]: Machine check ...: 4 Time(s) You are seeing Machine Check Exceptions. These may or may not be a problem. This is usually the CPU saying I ran into an error. This could be the cause of your Segmentation Fault, for example - the watchdog executes an invalid command, the processor complains and the watchdog receives a SegFault as a result. I suspect the difference between this and a SIGILL (Illegal Instruction) is that, while the instruction is technically valid, the data or the state of the processor or something like that is resulting in an error. It IS possible that the code is perfectly correct, but the processor is calculating the wrong answer (because of a hardware error). -- Kernel End - - Connections (secure-log) Begin New Users: glances (123) New Groups: glances (134) Changed password expiry for users: glances : 1 Time(s) **Unmatched Entries** lightdm: pam_ck_connector(lightdm:session): nox11 mode, ignoring PAM_TTY :0: 1 Time(s) systemd-logind: New seat seat0.: 1 Time(s) systemd-logind: Watching system buttons on /dev/input/event3 (Power Button): 1 Time(s) systemd-logind: Watching system buttons on /dev/input/event4 (Sleep Button): 1 Time(s) systemd-logind: Watching system buttons on /dev/input/event5 (Power Button): 1 Time(s) systemd-logind: Watching system buttons on /dev/input/event7 (Video Bus): 1 Time(s) usermod: change user 'glances' password: 1 Time(s) You've included this information. Did you not create the user glances yourself? -- Connections (secure-log) End - --8---cut here---end---8--- What should I - a) - install, to get a better idea of why its crashing? b) - do to stop/get round the crashing please? Thanks Sharon. -- A taste of linux = http://www.sharons.org.uk my git repo = https://bitbucket.org/boudiccas/dots TGmeds = http://www.tgmeds.org.uk Debian testing, fluxbox 1.3.6, emacs 24.4.1.0 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150224114840.gb23...@darac.org.uk
Re: Lenovo 050 desktop crashing
Darac Marjal mailingl...@darac.org.uk writes: On Tue, Feb 24, 2015 at 11:23:08AM +, Sharon Kimble wrote: I have just bought a new computer,a Lenovo 050 desktop. Its working reasonably okay except for the occasional crashes. For instance, I've had it a fortnight now and its longest uptime has been just over 3 days, even though its on all the time! It has crashed when I've been using it, and its crashed overnight whilst I've been asleep! There does not seem to be any pattern to it, or any noticeable trigger. When it crashes, the screen freezes, and both the usb keyboard and mouse freeze, and can not be used. In its most recent crash, it shows this in logwatch the following day --8---cut here---start-8--- - Kernel Begin WARNING: Segmentation Faults in these executables Watchdog : 2 Time(s) You appear to be running a watchdog process, which is crashing. A hardware watchdog will, generally speaking, work as follows: at boot, it will do nothing, but when an application writes a specific command to it, it will start a timer (30 seconds, 60 seconds, etc. Often configurable). When the timer expires, the watchdog will cause the computer to reset. However, when the application writes the command to the watchdog again, the timer is reset back to the start. So, as long as the watchdog process is alive, it is able to keep resetting the clock and the machine works fine. But if the processes stops (because the machine has hung, or the system is too busy), then the timer will expire, the machine will reboot and you can get back to work. Or in my case just freeze everything! In your case, though, it looks like the watchdog process is dying because of a Segmentation Fault (see the full logs or a core file for full details). At that point, even though the rest of the system is running fine, no-one is resetting the watchdog clock. WARNING: Kernel Errors Present INFO: recovery required on readonly filesyste ...: 1 Time(s) mce: [Hardware Error]: Machine check ...: 4 Time(s) You are seeing Machine Check Exceptions. These may or may not be a problem. This is usually the CPU saying I ran into an error. This could be the cause of your Segmentation Fault, for example - the watchdog executes an invalid command, the processor complains and the watchdog receives a SegFault as a result. I suspect the difference between this and a SIGILL (Illegal Instruction) is that, while the instruction is technically valid, the data or the state of the processor or something like that is resulting in an error. It IS possible that the code is perfectly correct, but the processor is calculating the wrong answer (because of a hardware error). So can I get round it by stopping or disabling the watchdog? I don't know what its doing and haven't deliberately installed it. It just seems to have appeared from somewhere! -- Kernel End - - Connections (secure-log) Begin New Users: glances (123) New Groups: glances (134) Changed password expiry for users: glances : 1 Time(s) **Unmatched Entries** lightdm: pam_ck_connector(lightdm:session): nox11 mode, ignoring PAM_TTY :0: 1 Time(s) systemd-logind: New seat seat0.: 1 Time(s) systemd-logind: Watching system buttons on /dev/input/event3 (Power Button): 1 Time(s) systemd-logind: Watching system buttons on /dev/input/event4 (Sleep Button): 1 Time(s) systemd-logind: Watching system buttons on /dev/input/event5 (Power Button): 1 Time(s) systemd-logind: Watching system buttons on /dev/input/event7 (Video Bus): 1 Time(s) usermod: change user 'glances' password: 1 Time(s) You've included this information. Did you not create the user glances yourself? No, the user glances was auto-created when I installed glances yesterday. Sharon. -- Connections (secure-log) End - --8---cut here---end---8--- What should I - a) - install, to get a better idea of why its crashing? b) - do to stop/get round the crashing please? Thanks Sharon. -- A taste of linux = http://www.sharons.org.uk my git repo = https://bitbucket.org/boudiccas/dots TGmeds = http://www.tgmeds.org.uk Debian testing, fluxbox 1.3.6, emacs 24.4.1.0 signature.asc Description: PGP signature
Re: Lenovo 050 desktop crashing
On Tue, 24 Feb 2015 11:23:08 + Sharon Kimble boudic...@skimble.plus.com wrote: I have just bought a new computer,a Lenovo 050 desktop. Its working reasonably okay except for the occasional crashes. For instance, I've had it a fortnight now and its longest uptime has been just over 3 days, even though its on all the time! It has crashed when I've been using it, and its crashed overnight whilst I've been asleep! There does not seem to be any pattern to it, or any noticeable trigger. When it crashes, the screen freezes, and both the usb keyboard and mouse freeze, and can not be used. In its most recent crash, it shows this in logwatch the following day snip What should I - a) - install, to get a better idea of why its crashing? b) - do to stop/get round the crashing please? Hard to say without more information. The next time it crashes, you might want to note the time, and look at messages in /var/log/dmesg and /var/log/kern.log for messages around that time period, and post them here and/or post a link to a pastebin of the logs. Then it might be easier to figure out what is going on. Hope you can do that, and that it will help. Trouble with new computers is never any fun :-( Petter -- I'm ionized Are you sure? I'm positive. pgphTg56KE3SB.pgp Description: OpenPGP digital signature
Re: Lenovo 050 desktop crashing
Petter Adsen pet...@synth.no writes: On Tue, 24 Feb 2015 11:23:08 + Sharon Kimble boudic...@skimble.plus.com wrote: I have just bought a new computer,a Lenovo 050 desktop. Its working reasonably okay except for the occasional crashes. For instance, I've had it a fortnight now and its longest uptime has been just over 3 days, even though its on all the time! It has crashed when I've been using it, and its crashed overnight whilst I've been asleep! There does not seem to be any pattern to it, or any noticeable trigger. When it crashes, the screen freezes, and both the usb keyboard and mouse freeze, and can not be used. In its most recent crash, it shows this in logwatch the following day snip What should I - a) - install, to get a better idea of why its crashing? b) - do to stop/get round the crashing please? Hard to say without more information. The next time it crashes, you might want to note the time, and look at messages in /var/log/dmesg and /var/log/kern.log for messages around that time period, and post them here and/or post a link to a pastebin of the logs. Then it might be easier to figure out what is going on. Hope you can do that, and that it will help. Trouble with new computers is never any fun :-( Thanks Petter, I've made a note of this for when it next happens. Sharon. -- A taste of linux = http://www.sharons.org.uk my git repo = https://bitbucket.org/boudiccas/dots TGmeds = http://www.tgmeds.org.uk Debian testing, fluxbox 1.3.6, emacs 24.4.1.0 signature.asc Description: PGP signature
Re: Lenovo 050 desktop crashing
Darac Marjal mailingl...@darac.org.uk writes: On Tue, Feb 24, 2015 at 11:23:08AM +, Sharon Kimble wrote: I have just bought a new computer,a Lenovo 050 desktop. Its working reasonably okay except for the occasional crashes. For instance, I've had it a fortnight now and its longest uptime has been just over 3 days, even though its on all the time! It has crashed when I've been using it, and its crashed overnight whilst I've been asleep! There does not seem to be any pattern to it, or any noticeable trigger. When it crashes, the screen freezes, and both the usb keyboard and mouse freeze, and can not be used. In its most recent crash, it shows this in logwatch the following day --8---cut here---start-8--- - Kernel Begin WARNING: Segmentation Faults in these executables Watchdog : 2 Time(s) You appear to be running a watchdog process, which is crashing. A hardware watchdog will, generally speaking, work as follows: at boot, it will do nothing, but when an application writes a specific command to it, it will start a timer (30 seconds, 60 seconds, etc. Often configurable). When the timer expires, the watchdog will cause the computer to reset. However, when the application writes the command to the watchdog again, the timer is reset back to the start. So, as long as the watchdog process is alive, it is able to keep resetting the clock and the machine works fine. But if the processes stops (because the machine has hung, or the system is too busy), then the timer will expire, the machine will reboot and you can get back to work. After looking more closely I don't have watchdog installed! There is no conf file for it, there is no executable for it, there is no man page for it, and apt-cache-policy shows --8---cut here---start-8--- acp watchdog watchdog: Installed: (none) Candidate: 5.14-3 Version table: 5.14-3 0 500 http://mirror.bytemark.co.uk/debian/ jessie/main i386 Packages --8---cut here---end---8--- which is why the machine freezes when its called, and also why it segfaults! Logically then, if the machine freezes without it, I need to install it, which I've just done. And so I'll just wait and see what happens now. Thanks all Sharon. In your case, though, it looks like the watchdog process is dying because of a Segmentation Fault (see the full logs or a core file for full details). At that point, even though the rest of the system is running fine, no-one is resetting the watchdog clock. WARNING: Kernel Errors Present INFO: recovery required on readonly filesyste ...: 1 Time(s) mce: [Hardware Error]: Machine check ...: 4 Time(s) You are seeing Machine Check Exceptions. These may or may not be a problem. This is usually the CPU saying I ran into an error. This could be the cause of your Segmentation Fault, for example - the watchdog executes an invalid command, the processor complains and the watchdog receives a SegFault as a result. I suspect the difference between this and a SIGILL (Illegal Instruction) is that, while the instruction is technically valid, the data or the state of the processor or something like that is resulting in an error. It IS possible that the code is perfectly correct, but the processor is calculating the wrong answer (because of a hardware error). -- Kernel End - - Connections (secure-log) Begin New Users: glances (123) New Groups: glances (134) Changed password expiry for users: glances : 1 Time(s) **Unmatched Entries** lightdm: pam_ck_connector(lightdm:session): nox11 mode, ignoring PAM_TTY :0: 1 Time(s) systemd-logind: New seat seat0.: 1 Time(s) systemd-logind: Watching system buttons on /dev/input/event3 (Power Button): 1 Time(s) systemd-logind: Watching system buttons on /dev/input/event4 (Sleep Button): 1 Time(s) systemd-logind: Watching system buttons on /dev/input/event5 (Power Button): 1 Time(s) systemd-logind: Watching system buttons on /dev/input/event7 (Video Bus): 1 Time(s) usermod: change user 'glances' password: 1 Time(s) You've included this information. Did you not create the user glances yourself? -- Connections (secure-log) End - --8---cut here---end---8--- What should I - a) - install, to get a better idea of why its crashing? b) - do to stop/get round the crashing please? Thanks Sharon. -- A taste of linux = http://www.sharons.org.uk my git repo = https://bitbucket.org/boudiccas/dots TGmeds = http://www.tgmeds.org.uk Debian testing, fluxbox 1.3.6, emacs 24.4.1.0 -- A taste of linux = http://www.sharons.org.uk my git repo =
Re: Lenovo 050 desktop crashing
On Tue, 24 Feb 2015, Sharon Kimble wrote: I have just bought a new computer,a Lenovo 050 desktop. Its working I couldn't find an 050 model. Did you mean H50? reasonably okay except for the occasional crashes. For instance, I've had it a fortnight now and its longest uptime has been just over 3 days, even though its on all the time! What OS did it come with Windows 7 or 8? Did the machine crash when running Windows? If yes, you could have a hardware problem. If no, then it's probably a Linux problem. You seemed to have installed Jessie 32-bit based on your other posting -- installed watchedog . . . i386. What version of Jessie? It's at RC1 as of 25 Jan. Dual boot or did you wipe out Windows? GNOME3 desktop? Here's what I'd do. Start over from zero. You could have a corrupted install. Wipe out your current Jessie. Download and install the most current 64-bit version. Do a checksum on the download itself and the CD or DVD after burning. Depending on your Internet connection, a netinstall CD will get you an up-to-date system when the install is completed. It has crashed when I've been using it, and its crashed overnight whilst I've been asleep! There does not seem to be any pattern to it, or any noticeable trigger. When it crashes, the screen freezes, and both the usb keyboard and mouse freeze, and can not be used. Sounds like a kernel crash. Does the screen go black (or another color) like the computer was turned off, or does the desktop image remain? In its most recent crash, it shows this in logwatch the following day --8---cut here---start-8--- [snip] B -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150224100636.5d897...@debian7.boseck208.net
Re: Lenovo 050 desktop crashing
Patrick Bartek nemomm...@gmail.com writes: On Tue, 24 Feb 2015, Sharon Kimble wrote: I have just bought a new computer,a Lenovo 050 desktop. Its working I couldn't find an 050 model. Did you mean H50? Nope, its a Lenovo 050 Desktop from ebuyer. reasonably okay except for the occasional crashes. For instance, I've had it a fortnight now and its longest uptime has been just over 3 days, even though its on all the time! What OS did it come with Windows 7 or 8? Did the machine crash when running Windows? If yes, you could have a hardware problem. If no, then it's probably a Linux problem. 8.1, which was very soon removed to install wheezy to upgrade to jessie. You seemed to have installed Jessie 32-bit based on your other posting -- installed watchedog . . . i386. What version of Jessie? It's at RC1 as of 25 Jan. It was installed on 10th February, a netinstall of wheezy. Then upgraded to jessie on the same day. Dual boot or did you wipe out Windows? GNOME3 desktop? Fluxbox, I went into gnome once whilst I installed fluxbox, and there I remain. Here's what I'd do. Start over from zero. You could have a corrupted install. Wipe out your current Jessie. Download and install the most current 64-bit version. Do a checksum on the download itself and the CD or DVD after burning. Depending on your Internet connection, a netinstall CD will get you an up-to-date system when the install is completed. Everything is working okay, that crashing was the only problem, so thanks, but I'm staying with it as it is. The setup was missing watchdog which is now installed. But it is a good idea to get a new 64-bit version, my install disk was burnt on 28 May 2013 so it does need to be replaced. It has crashed when I've been using it, and its crashed overnight whilst I've been asleep! There does not seem to be any pattern to it, or any noticeable trigger. When it crashes, the screen freezes, and both the usb keyboard and mouse freeze, and can not be used. Sounds like a kernel crash. Does the screen go black (or another color) like the computer was turned off, or does the desktop image remain? When it crashed *everything* just froze, the keyboard, the desktop, the monitor, time stood still! Sharon.. -- A taste of linux = http://www.sharons.org.uk my git repo = https://bitbucket.org/boudiccas/dots TGmeds = http://www.tgmeds.org.uk Debian testing, fluxbox 1.3.6, emacs 24.4.1.0 signature.asc Description: PGP signature
Re: Lenovo 050 desktop crashing
On Tue, 24 Feb 2015, Sharon Kimble wrote: Patrick Bartek nemomm...@gmail.com writes: On Tue, 24 Feb 2015, Sharon Kimble wrote: I have just bought a new computer,a Lenovo 050 desktop. Its working I couldn't find an 050 model. Did you mean H50? Nope, its a Lenovo 050 Desktop from ebuyer Couldn't find that model listed anywhere. Even searched ebuyer's site. Nothing. Just trying to get the specs on it. Curious. No matter as it seems installing watchdog solved your problem. Although, why watchdog wasn't installed in the first place or why it needed to be installed at all. ??? It's not on my Wheezy system, and I have no problems. Of course, my current system is 1 to 8 years old depending on which part. ;-) reasonably okay except for the occasional crashes. For instance, I've had it a fortnight now and its longest uptime has been just over 3 days, even though its on all the time! What OS did it come with Windows 7 or 8? Did the machine crash when running Windows? If yes, you could have a hardware problem. If no, then it's probably a Linux problem. 8.1, which was very soon removed to install wheezy to upgrade to jessie. You seemed to have installed Jessie 32-bit based on your other posting -- installed watchedog . . . i386. What version of Jessie? It's at RC1 as of 25 Jan. It was installed on 10th February, a netinstall of wheezy. Then upgraded to jessie on the same day. Dual boot or did you wipe out Windows? GNOME3 desktop? Fluxbox, I went into gnome once whilst I installed fluxbox, and there I remain. When GNOME went to 3, I stopped using GNOME. It caused more problems than it was worth. Even installing another environment or just using a window manager, it still got in the way. Ultimately, when I upgraded to Debian Wheezy (from Fedora 12) I did a netinstall, Basic System. Added what I wanted -- X, etc. -- service by service, app by app. You should be able to choose which environment or window manager you want on the login page. If you set Fluxbox as the Default, system should boot to it the next time and every time until you change it. Here's what I'd do. Start over from zero. You could have a corrupted install. Wipe out your current Jessie. Download and install the most current 64-bit version. Do a checksum on the download itself and the CD or DVD after burning. Depending on your Internet connection, a netinstall CD will get you an up-to-date system when the install is completed. Everything is working okay, that crashing was the only problem, so thanks, but I'm staying with it as it is. The setup was missing watchdog which is now installed. But it is a good idea to get a new 64-bit version, my install disk was burnt on 28 May 2013 so it does need to be replaced. You said you upgraded from Wheezy. When or if, you reinstall Jessie, just get the latest version and do a clean install. I've never done a distribution upgrade that didn't require fixing in some way or other. Clean installs are the least problematical. B -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150224161714.0cc24...@debian7.boseck208.net
Re: Lenovo 050 desktop crashing
On 02/24/2015 03:23 AM, Sharon Kimble wrote: I have just bought a new computer,a Lenovo 050 desktop. Its working reasonably okay except for the occasional crashes. ... It has crashed when I've been using it, and its crashed overnight whilst I've been asleep! There does not seem to be any pattern to it, or any noticeable trigger. A failing power supply and/or off-spec memory module can cause unpredictable lock-up's. I use an inexpensive ATX power supply tester for quick pass/fail testing: http://www.newegg.com/Product/Product.aspx?Item=N82E16899129001 I use memtest86+ for checking RAM: http://www.memtest.org/ Run memtest86+ for at least 12 hours; better 24. I've seen machines with infrequent lock-up problems pass an hour or more of testing, only to fail once or twice in later hours. If your new computer fails either of the above, return it. If the memory and power supply test out okay, then understand that the whole point of the Debian testing release is to find bugs. Here is your opportunity to do so. On 02/24/2015 10:56 AM, Sharon Kimble wrote: It was installed on 10th February, a netinstall of wheezy. Then upgraded to jessie on the same day. On 02/24/2015 10:56 AM, Sharon Kimble wrote: But it is a good idea to get a new 64-bit version, my install disk was burnt on 28 May 2013 so it does need to be replaced. If you're going to re-install, a fresh ISO would be a good idea. I typically run amd64 on compatible hardware, but i386 with PAE (default) supports more than 4 GB of RAM too. Installing and running Wheezy for a week or so should narrow the possibilities. HTH, David -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54ed3c4e.3080...@holgerdanske.com
