It happens now and then that our SuSE-8.1 server (P4-2.4G, 1G, 160G, G550) hangs heavily with Caps Lock and Scroll Lock flashing. Does anyone on the list know what could be the reason for such a behavior? I'm a bit suspicious about the temperature in the box. Thanks for your suggestions, -- Ch
* Christian Andersson (chrisand@cs.lth.se) [021107 14:11]: -> ->It happens now and then that our SuSE-8.1 server (P4-2.4G, 1G, 160G, G550) ->hangs heavily with Caps Lock and Scroll Lock flashing. Does anyone on the ->list know what could be the reason for such a behavior? I'm a bit suspicious ->about the temperature in the box. My AMD box did this with 8.1 and the only thing that I could find that might be the cause was a bios conflict. I returned to 8.0 then I was told it was a bios issue. I haven't tried 8.1 again yet. I didn't think it was CPU temp because I put this massive CPU cooler on and put a 7200rpm fan in the case. Along with a 480W power supply to handle all of it. With the new CPU cooler the CPU is about 10C cooler then it was with the old fan... It's odd because 8.0 works perfectly with this machine. I may try 8.1 again with the new bios..don't know. You may want to check the bios revision your machine has...it could be the cause. I'm leaning toward blaming the .19 kernel's interaction with the bios of certain machines. -- Ben Rosenberg ---===---===---===--- mailto:ben@whack.org Tell me what you believe.. I tell you what you should see.
Ben Rosenberg wrote:
* Christian Andersson (chrisand@cs.lth.se) [021107 14:11]: -> ->It happens now and then that our SuSE-8.1 server (P4-2.4G, 1G, 160G, G550) ->hangs heavily with Caps Lock and Scroll Lock flashing. Does anyone on the ->list know what could be the reason for such a behavior? I'm a bit suspicious ->about the temperature in the box.
My AMD box did this with 8.1 and the only thing that I could find that might be the cause was a bios conflict. I returned to 8.0 then I was told it was a bios issue. I haven't tried 8.1 again yet. I didn't think it was CPU temp because I put this massive CPU cooler on and put a 7200rpm fan in the case. Along with a 480W power supply to handle all of it. With the new CPU cooler the CPU is about 10C cooler then it was with the old fan...
It's odd because 8.0 works perfectly with this machine. I may try 8.1 again with the new bios..don't know.
You may want to check the bios revision your machine has...it could be the cause. I'm leaning toward blaming the .19 kernel's interaction with the bios of certain machines.
I live in Manchester, England, where overheating is scarcely a problem, and unfortunately have had a couple of the hard locks you describe (lights, etc) on previously immaculately reliable hardware. I pounded the RAM for several hours with memtest86 without it showing any sign of faults. It is a complete hard lock, keyboard, ssh access from other machines, etc., all gone. However, I'll check to see if there are further BIOS revisions available for the mainboard. The locks don't appear to me to have been associated with load. Cheers all Fergus
-- Ben Rosenberg ---===---===---===--- mailto:ben@whack.org Tell me what you believe.. I tell you what you should see.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Wednesday 13 November 2002 14:40, Fergus Wilde wrote:
I live in Manchester, England, where overheating is scarcely a problem,
Well, the possible overheating problems in Sweden are probably restricted to our computing hardware... ;) Thanks anyway, and sorry to the list... -- Ch
I live in Manchester, England, where overheating is scarcely a problem, and unfortunately have had a couple of the hard locks you I live in Sheffield, England which is even cooler ;o) Have a look at IRQs being assigned automatically by the BIOS. I found
On Wednesday 13 November 2002 1:40 pm, Fergus Wilde wrote: that I had "hard lockups" which actually weren't [occasionaly interrupts would get through, but it appeared to lock hard otherwise] and I found that by actually specifying the interrupts in the BIOS [Assigning a specific IRQ to an INT] rather than letting it "automatically" decided [I chose figures based on looking at the alt+F10 message screen upon bootup] that if I specified the IRQs the hardware wants [as close as possible] then the lockups don't happen. Just a thought. :o) Jon
On Wednesday 13 November 2002 1:40 pm, Fergus Wilde wrote:
I live in Manchester, England, where overheating is scarcely a problem, and unfortunately have had a couple of the hard locks you describe (lights, etc) on previously immaculately reliable hardware. I pounded the RAM for several hours with memtest86 without it showing any sign of faults. It is a complete hard lock, keyboard, ssh access from other machines, etc., all gone. However, I'll check to see if there are further BIOS revisions available for the mainboard. The locks don't appear to me to have been associated with load.
I suspect the IRQ approach has something to do with it. I got this when, for want of something better to do, I put a USB2 PCI card into the PC, booted, and tried rchotplug restart. I don't know if USB2 is useable yet, but I decided I wasn't so anxious to get it working that I could put up with hardlocks, so the card came out! Kevin
On Wednesday 13 November 2002 08:40, Fergus Wilde wrote:
Ben Rosenberg wrote:
* Christian Andersson (chrisand@cs.lth.se) [021107 14:11]: -> ->It happens now and then that our SuSE-8.1 server (P4-2.4G, 1G, 160G, G550) ->hangs heavily with Caps Lock and Scroll Lock flashing. Does anyone on the ->list know what could be the reason for such a behavior? I'm a bit suspicious ->about the temperature in the box.
Yes, I recieve the same error when running X. It did not occur using 8.0 I suspect it is related to the new ACPI code, but I cannot get a kernel to compile with the ACPI/APM code disabled at this time to verify this will resolve the issue. Doug
On Wed, 13 Nov 2002, Doug Glenn wrote:
On Wednesday 13 November 2002 08:40, Fergus Wilde wrote:
Ben Rosenberg wrote:
* Christian Andersson (chrisand@cs.lth.se) [021107 14:11]: -> ->It happens now and then that our SuSE-8.1 server (P4-2.4G, 1G, 160G, G550) ->hangs heavily with Caps Lock and Scroll Lock flashing. Does anyone on the ->list know what could be the reason for such a behavior? I'm a bit suspicious ->about the temperature in the box.
Yes, I recieve the same error when running X. It did not occur using 8.0
I suspect it is related to the new ACPI code, but I cannot get a kernel to compile with the ACPI/APM code disabled at this time to verify this will re
Do you use reiserfs? I had this problem until using the reiserfs fix mentioned here earlier. Preston
On Wednesday 13 November 2002 08:40, Fergus Wilde wrote: Yes, I recieve the same error when running X. It did not occur using 8.0
I suspect it is related to the new ACPI code, but I cannot get a kernel to compile with the ACPI/APM code disabled at this time to verify this
Hmm, we also had this problem on several PCs. But they are all SuSE 7.3 Prof. We only figgured out that this problem seems to be connected to MSI Motherboards.
On Thursday 14 November 2002 17:08, Claudia Goldbrunner wrote:
Hmm, we also had this problem on several PCs. But they are all SuSE 7.3 Prof. We only figgured out that this problem seems to be connected to MSI Motherboards.
I had a brand new and fancy MSI K7T266 Pro2-RU replaced by a simple ASUS A7S333 motherboard. The MSI had problems with IDE. Just before a lock up, I could sometime see that the kernel tried to reset the IDE channel of my HD, but failed to do so. After the lock up, the Caps-Lock and Num-Lock leds were blinking simultanious, never the Scroll-Lock led. It also had problems with my IDE DVD and CDRW. For instance, SuSE 8.1 failed to install with this motherboard. After installing some packages, it failed to read and install a lot other packages. In my log files I could see a lot of error messages, something like 'hdX unsupported command'. After I had replaced the motherboard, almost as cheap as an extra PCI IDE controller, my system works as it should, i.e. an almost constant uptime. I just had 2 X Windows lockups during useage of Konqeror. Regards, Cees.
Well, I finally gave up with the Suse kernel and went with the stock kernel. I disabled power management and it compiled without the Apic related errors I was getting with the Suse source. Now all is left to do is finish installing the modules, reboot and wait for progress. I tend to leave my systems on all the time, so these lockups have really been a lot of heartburn. I also just started movie editing to move all my video off of tape onto CDs so I have been greatly annoyed with the lockups. All that remains is to see if the settings will still match so I can have sound :) Then it is waiting to see if it locks up. I will know within 4 hours. Doug
The 02.11.14 at 21:18, Doug Glenn wrote:
been a lot of heartburn. I also just started movie editing to move all my video off of tape onto CDs so I have been greatly annoyed with the lockups.
Quick question: what do you use for that? I'm thinking of doing it as well. -- Cheers, Carlos Robinson
Hmm, we also had this problem on several PCs. But they are all SuSE 7.3 Prof. We only figgured out that this problem seems to be connected to MSI Motherboards.
I had a brand new and fancy MSI K7T266 Pro2-RU replaced by a simple ASUS A7S333 motherboard.
The MSI had problems with IDE. Just before a lock up, I could sometime see that the kernel tried to reset the IDE channel of my HD, but failed to do so. After the lock up, the Caps-Lock and Num-Lock leds were blinking simultanious, never the Scroll-Lock led.
It also had problems with my IDE DVD and CDRW. For instance, SuSE 8.1 failed to install with this motherboard. After installing some packages, it failed to read and install a lot other packages. In my log files I could see a lot of error messages, something like 'hdX unsupported command'.
After I had replaced the motherboard, almost as cheap as an extra PCI IDE controller, my system works as it should, i.e. an almost constant uptime. I just had 2 X Windows lockups during useage of Konqeror.
Regards, Cees.
We have the same problem with Chaintech 7SID motherboards when installing SuSE 8.0, but in 7.2 and 7.3 the installation works as expected. In 8.1 the system hangs when the installation is about to install files (or sometimes when trying to format the harddisk). With these boards we have not yet been to install SuSE at all. Bo -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Friday 15 November 2002 10:09, Bo Jacobsen wrote:
We have the same problem with Chaintech 7SID motherboards when installing SuSE 8.0, but in 7.2 and 7.3 the installation works as expected. In 8.1 the system hangs when the installation is about to install files (or sometimes when trying to format the harddisk). With these boards we have not yet been to install SuSE at all.
Not sure who all this applies to, but if you have anything by VIA on your board, chances are the kernel panics (machine hanging/blinking LEDs) will be fixed by using Mantel's kernel build. It has a VIA Southbridge fix in it. I had kernel panics with 8.1, and installing Mantel's kernel build with the VIA fix stopped this. Now running over 2 weeks with no problem. I was able to get an install complete, and it would run for at least 15 minutes before the kernel panic. So I started the computer, installed Mantel's kernel build which I'd already downloaded. Ran "mk_initrd", then rebooted. (Using Grub. If using Lilo, run "lilo" as well of course.) ftp://ftp.mirror.ac.uk/sites/ftp.suse.com/pub/people/mantel/next/RPM/ Several RPMs there. Download the one right for you. ;-) Even if you don't have anything VIA in your computer, give his build a try. That's not the only fix done in those kernel builds. Later, Joe
On Friday 15 November 2002 03:00 am, Joe Sullivan wrote:
I had kernel panics with 8.1, and installing Mantel's kernel build with the VIA fix stopped this. Now running over 2 weeks with no problem.
ftp://ftp.mirror.ac.uk/sites/ftp.suse.com/pub/people/mantel/next/RPM/ Several RPMs there. Download the one right for you. ;-)
Gotta Agree with that. Mantel is one of (maybe the principal) SuSE Kernal Hacker, and his kernels fixed up my Sony Viao where everything works. -- _________________________________________________ No I Don't Yahoo! And I'm getting pretty sick of being asked if I do. _________________________________________________ John Andersen / Juneau Alaska
The 02.11.14 at 17:08, Claudia Goldbrunner wrote:
Hmm, we also had this problem on several PCs. But they are all SuSE 7.3 Prof.
Yes, I had lockups with that version, and I know of more people that had it, with different hardware all of us: but we all used suse 7.3. [...] I have just looked up our conversation of that time, and two used reiser and the other one I don't know. -- Cheers, Carlos Robinson
Christian Andersson wrote:
It happens now and then that our SuSE-8.1 server (P4-2.4G, 1G, 160G, G550) hangs heavily with Caps Lock and Scroll Lock flashing. Does anyone on the list know what could be the reason for such a behavior? I'm a bit suspicious about the temperature in the box.
Thanks for your suggestions,
In my case the problem disappeared after installing the later build of the 2.4.19 kernel available on the ftp site. YMMV HTH Fergus
-- Ch
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (13)
-
Ben Rosenberg -
Bo Jacobsen -
Carlos E. R. -
Cees van de Griend -
Christian Andersson -
Claudia Goldbrunner -
Doug Glenn -
Fergus Wilde -
Joe Sullivan -
John Andersen -
Kevin Donnelly -
Preston Crawford -
The Purple Tiger