On 04 Apr 2001 20:42:31 -0400, Unix Admin - Adam Gregoire wrote:
Installed 2.4.3 last night and before 24 hours was up it locked up
again. next please =/
Do you overclock? My board is stable, but I dont use the UDMA100 stuff
(HPT366) and I run the celerons at 433 with 66MHz bus speed. Also
Installed 2.4.3 last night and before 24 hours was up it locked up
again. next please =/
Try one CPU only if you need stability, or buy a new mobo and CPUs...
Actually seriously a mag article (Personal Computer World, UK), by the guy
who got me interested in the BP6, that he was using the VP6
On Wed, Apr 04, 2001 at 08:42:31PM -0400, Unix Admin - Adam Gregoire wrote:
Installed 2.4.3 last night and before 24 hours was up it locked up
again. next please =/
9:33am up 1 day, 18:04, 8 users, load average: 4.24, 4.06, 4.02
Linux grobbebol 2.4.3 #1 SMP Tue Apr 3 14:39:34 GMT 2001
Roeland Th. Jansen wrote:
On Wed, Apr 04, 2001 at 08:42:31PM -0400, Unix Admin - Adam Gregoire wrote:
Installed 2.4.3 last night and before 24 hours was up it locked up
again. next please =/
9:33am up 1 day, 18:04, 8 users, load average: 4.24, 4.06, 4.02
Linux grobbebol 2.4.3 #1
Here look at my uptime stats over the past month or so. Max is 4 days,
but I have ran for almost 3 days at 13.xx load.
1 4 days, 04:30:29 | Linux 2.4.2-ac21Tue Mar 27 20:36:16
2001
2 3 days, 09:26:08 | Linux 2.4.2-ac5 Sun Mar 4
13:27:03 2001
3 3 days,
Compile 100 in a row, sure, I'm on it. I'll even let the box sit in X.
I've set it to do "make clean dep bzImage" 100 times. starting at 10AM
EST
Adam
On 05 Apr 2001 12:37:08 +0200, Rogier Wolff wrote:
Roeland Th. Jansen wrote:
On Wed, Apr 04, 2001 at 08:42:31PM -0400, Unix Admin - Adam
Unix Admin - Adam Gregoire wrote:
Compile 100 in a row, sure, I'm on it. I'll even let the box sit in X.
I've set it to do "make clean dep bzImage" 100 times. starting at 10AM
You might also try some of my CPU testing utilites to validate
your hardware. I would suggest 2*`burnP6` for 1
Well it's been 3h50mins running 4 burnMMX which are all still running
with no errors.
But I can almost say that sometime in the next minute to 4 days that I
will be in X and will click the mouse button and it will lock. I'll keep
you posted.
PS. I have tried both a PS/2 and a USB mouse.
Adam
Installed 2.4.3 last night and before 24 hours was up it locked up
again. next please =/
Adam Gregoire
On 04 Apr 2001 00:35:40 +0200, Zdenek Kabelac wrote:
But now get this It has locked hard no kbd/mouse/network but my ATI
All-In-Wonder was playing TV and sound after this lock.
Well my box is still locking up only in X and only while using mouse.
I'm not sharing any interrupts I have fans all over my box. Tried with
PIO1,2,3,4 UDMA no combination is any different. Tried many kernels
2.2.x 2.4.1 2.4.2 2.4.2-ac5 2.4.2-ac21, tried the noapic option. Four
different video
On Tue, Apr 03, 2001 at 04:56:58AM -0400, Unix Admin - Adam Gregoire wrote:
Well my box is still locking up only in X and only while using mouse.
I'm not sharing any interrupts I have fans all over my box. Tried with
PIO1,2,3,4 UDMA no combination is any different. Tried many kernels
2.2.x
Well my box is still locking up only in X and only while using mouse.
I'm not sharing any interrupts I have fans all over my box. Tried with
PIO1,2,3,4 UDMA no combination is any different. Tried many kernels
2.2.x 2.4.1 2.4.2 2.4.2-ac5 2.4.2-ac21, tried the noapic option. Four
different
I used to have the same problem as you. Luckily, my computer has not
locked up in a while. I still get APIC errors reported, but it does not
lockup my system.
My setup,
Bios QQ
kernel 2.4.1,
(I'll check my version of X probably 4),
450 Mb ram-64+128+256
30Gb on hdt366
2Gb --ide1
10Gb--ide2
On 03 Apr 2001 09:15:52 -0400, Gnea wrote:
On Tue, Apr 03, 2001 at 04:56:58AM -0400, Unix Admin - Adam Gregoire wrote:
Well my box is still locking up only in X and only while using mouse.
I'm not sharing any interrupts I have fans all over my box. Tried with
PIO1,2,3,4 UDMA no combination
I have already tried all of your suggested voodoo to no avail Im using
ati_xv/dri-cvs.
On 03 Apr 2001 07:43:22 -0700, Francisco Rojas wrote:
I used to have the same problem as you. Luckily, my computer has not
locked up in a while. I still get APIC errors reported, but it does not
lockup my
But now get this It has locked hard no kbd/mouse/network but my ATI
All-In-Wonder was playing TV and sound after this lock.
Anyone out there have the slighest clue? I am now totally baffled.
Ive tried 2 QQ bios 2 ru including one without the HPT support.
Please try 2.4.3 -
Ahmon Dancy wrote:
On the topic of various ways to try to fix the lockup problem..
perhaps we should try a different approach.
Does anyone know the exact nature of the lockup? i.e.:
Is the kernel getting stuck in a loop somewhere?
Is the kernel waiting for something to happen that will
On the topic of various ways to try to fix the lockup problem..
perhaps we should try a different approach.
Does anyone know the exact nature of the lockup? i.e.:
Is the kernel getting stuck in a loop somewhere?
Is the kernel waiting for something to happen that will never happen?
Is it
On Wed, 20 Dec 2000, Ahmon Dancy wrote:
Unfortunately, the best person to answer this is probably Andre.. but he
doesn't experience the problem.
Set your latancy to 0x20 or 32, because the PCI Arbitration Bit is
destroyed in 440BX/LX/MX system and any other Intel box that has a PIIX4
that is
On the topic of various ways to try to fix the lockup problem..
perhaps we should try a different approach.
Does anyone know the exact nature of the lockup? i.e.:
I would say that if the lockup would be in spinlock than the NMI oopser
would catch this lock.
Is the kernel getting
On Wed, 20 Dec 2000, Ahmon Dancy wrote:
Unfortunately, the best person to answer this is probably Andre.. but he
doesn't experience the problem.
Set your latancy to 0x20 or 32, because the PCI Arbitration Bit is
destroyed in 440BX/LX/MX system and any other Intel box that has a PIIX4
On Wed, Sep 27, 2000 at 09:30:24AM +0200, Lars Munch wrote:
On Tue, Sep 26, 2000 at 09:52:45PM -0700, Andre Hedrick wrote:
Follow up,
If this is not an overclocking issue, they speak up.
No, I'm not overclocking (don't want to rock the boat).
After changing to UDMA 2 (as Rob
what if you're overclocking the cpus but underclocking the pci bus?
If you are overclocking, go away with the problem, because it is not mine.
As the driver tightens the gaps of wasted cycles the window of
overclocking will collapse.
--
=- To unsubscribe, email [EMAIL PROTECTED] with
On Tue, Sep 26, 2000 at 10:41:24PM -0400, Rahul Karnik wrote:
Did you post this to linux-kernel?
Nope, I'm not on that list. (but I do read kernel traffic :-)
And have you tried the latest kernels?
Some IDE fixes there.
Yes, this was with kernel 2.4.0-test9pre4.
Thanks,
Lars
--
=-
On Tue, Sep 26, 2000 at 09:52:45PM -0700, Andre Hedrick wrote:
Follow up,
If this is not an overclocking issue, they speak up.
No, I'm not overclocking (don't want to rock the boat).
After changing to UDMA 2 (as Rob suggested) my system has
been stable, but then again I have not been
On Tue, 26 Sep 2000, Rahul Karnik wrote:
Did you post this to linux-kernel? And have you tried the latest kernels?
Some IDE fixes there.
I am running a 13.6GB Western Digital drive on the HPT 366 without any
problems but its my Windows 2000 disk that I access in Linux but dont boot
Follow up,
If this is not an overclocking issue, they speak up.
Cheers,
Andre Hedrick
The Linux ATA/IDE guy
--
=- To unsubscribe, email [EMAIL PROTECTED] with the -=
=-body of "unsubscribe linux-abit". -=
Before I disable UDMA/66 and moves the HD to the UDMA/33
controller, I have to ask if there is anything I can do to
fix this, e.g. use the noapic option, disable Sharing PCI
IDE interrupts support, use a different mode in the htp366
bios etc.
Try going into the HPT Bios and changing the
I had the box get twitchy on me with the NIC and the HPT
controller sharing an interrupt. Supposedly PCI supports
it, but there's a lot of card-bus-driver interaction
here, that might explain some of the crashing.
I've got everything on its own interrupt now, and its
stable. (Well, that and
On Sun, Feb 20, 2000 at 05:00:35PM -0500, Matt Yurman wrote:
On Sat, 19 Feb 2000 20:02:49 +0100 (MET), you wrote:
On BP6, most of the lockups seem to be that the whole system freezes,
so either there is a hardware lockup, or somehow Linux happens to
get stuck in a spinlock-deadlock, but
I've also seen this - sometimes the mouse will die and I have to restart X
to restore it. But as for weird keyboard errors, I only see that while
playing Quake 3, and then only occasionally.
cs
On Sun, 20 Feb 2000, Hal Burgiss wrote:
I have had occasional, weird keyboard behavior with
Matt Yurman wrote:
has anyone else noticed that the lockups under high cpu use appear
to be because one cpu drops offline? i would get the same sort of
lockups occasionally, but since i run seti it is more frequent.
This is what I'd expect from a "spinlock programming error".
I'm a device
I'm running stable (have been for months, longest uptime about 100 days
rebooted to upgrade kernel).
my specs:
RedHat 6.1, kernels between 2.2.13preX and 2.2.14pre18
XFree86 3.3.5 SVGA server in use at all times - heavily.
BP6 rev 1 (metal handles)
2xC366@[EMAIL PROTECTED] with Alpha coolers
I am using lm_sensors and haven't found any difference in reliability.
Mike
-Original Message-
From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
Sent: Friday, January 07, 2000 7:26 PM
To:[EMAIL PROTECTED]
Cc:emddjf@office8
Subject: Re: [LINUX-ABIT] Lockups and what to do
PROTECTED]]
Sent:Friday, January 07, 2000 7:26 PM
To: [EMAIL PROTECTED]
Cc: emddjf@office8
Subject: Re: [LINUX-ABIT] Lockups and what to do...
I also suspected lm_sensors as an instability factor. I stopped using
them and my lockups went away. No guarantee that was it though
I am running 2.2.12 and 2.2.13
Mike
-Original Message-
From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
Sent: Friday, January 07, 2000 7:37 PM
To:[EMAIL PROTECTED]
Cc:emddjf@office8
Subject: Re: [LINUX-ABIT] Lockups and what to do...
That's good to know. Which version
On Fri, Jan 07, 2000 at 06:26:04PM -0600, you [Dwayne Jacques Fontenot] claimed:
Once I left my machine up for about 24 hours compiling the kernel in
a loop using both processors (make -j 2). It didn't lock up.
I did that too (make -j3) - no lockup. But once I do 2x100% floating point
I think every one who had lockups need to send a complete report somewhere
(buy date for the motherboard, speed and voltage of CPUs, average temp, all
devices, kernel, modules, ...) to track where it goes wrong.
What do you think of that ?
And who wants to do it ?
Lunar
PS : I bought my Abit
To: [EMAIL PROTECTED]
Subject: Re: [LINUX-ABIT] Lockups and what to do...
As a sanity check, and this is probably the wrong forum to ask, whos is
not
having problems? What are your uptime records?
--
Michael Rasmussen - [EMAIL PROTECTED]
Be Appropriate Follow Your Curiosity
email to page
them won't be very fruitful.
-Original Message-
From: Michael Rasmussen [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 06, 2000 1:43 PM
To: [EMAIL PROTECTED]
Subject: Re: [LINUX-ABIT] Lockups and what to do...
As a sanity check, and this is probably the wrong forum to
eems
clear that from a uniprocessor perspective, the BP6 seems as reliable as
the BE6 board.
Mike
-Original Message-
From: Hal Burgiss [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 06, 2000 4:40 PM
To: Discussion List for Linux on Abit Motherboards
Subject: Re: [LINUX-ABIT] Lockup
41 matches
Mail list logo
