Hi,
For some odd reason, using Azureus seems to kill my machine with annoying frequency (either hangs it or resets it). Now, I'm not sure if this is a Java problem, an Azureus problem (Azureus is a java bittorrent client) or a kernel problem.
If I run Azureus with kernel-2.6.10-1.1063_FC4 everything is fine and happy, files download and the world spins on. Run it on anything newer that 1063_FC4 and I get the shut downs and lock ups.
Anyone else seeing this or is it just me?
TTFN
Paul
I haven't personally seen it - but you migth want to report a bug in the allmigtht bugzilla...
ons, 09.02.2005 kl. 01.16 skrev Paul:
Hi,
For some odd reason, using Azureus seems to kill my machine with annoying frequency (either hangs it or resets it). Now, I'm not sure if this is a Java problem, an Azureus problem (Azureus is a java bittorrent client) or a kernel problem.
If I run Azureus with kernel-2.6.10-1.1063_FC4 everything is fine and happy, files download and the world spins on. Run it on anything newer that 1063_FC4 and I get the shut downs and lock ups.
Anyone else seeing this or is it just me?
TTFN
Paul
On Wed, 09 Feb 2005 00:16:29 +0000, Paul paul@all-the-johnsons.co.uk wrote:
For some odd reason, using Azureus seems to kill my machine with annoying frequency (either hangs it or resets it). Now, I'm not sure if this is a Java problem, an Azureus problem (Azureus is a java bittorrent client) or a kernel problem.
Anyone else seeing this or is it just me?
Yes, I have, using Azureus under Sun 1.5.0 (and now _01). Lockups (usually so hard I can't alt-sysrq-b), and sometimes spontaneous reboots. I also can't get through more than a couple eps of Buffy in mplayer without lockage, and running folding@home overnight seems to do the trick too.
I've tried backing off to the 741 kernel (FC3), and while that's better, it's still not crash-free. Unfortunately, my hardware has a bad history, and I'm still in the process of making sure it's not at fault before I bugzilla anything. I had a power supply die last year, which may have been the reason my GeForce 256 died somewhat later... I'm now running on a borrowed Permedia 2V card, the health of which the lender wasn't entirely sure of either. I'm planning on picking up a cheapie GF4MX card today to see if that helps things.
If you haven't already, definitely give your hardware at least an overnight run of memtest86+. I found that with my bios set to 'turbo', the memory timings were just a little too aggressive such that I was getting a few sporadic errors on test 6 in high memory. An initial 1-pass run I had done when I first enabled the setting hadn't exposed that problem. Setting it back to 'normal' fixed the memory errors, but unfortunately hasn't ended the crashes.
Of course, it's all moot right now because I have yet to get a single oops or panic message to report...
Other than the video cards, my hardware is an Athlon 1700+ (1466 MHz) on a Soyo SY-K7V Dragon Plus mobo (VIA KT266A), plus an extra ethernet card (tulip), SCSI (2940UW), and an extra Promise 100TX controller. Lots of drives. Any similarities to your hardware?
I run with vm.swappiness set to 0, but I'm not sure if that has any bearing on the problem.
--wes
Hi,
Anyone else seeing this or is it just me?
Yes, I have, using Azureus under Sun 1.5.0 (and now _01). Lockups (usually so hard I can't alt-sysrq-b), and sometimes spontaneous reboots. I also can't get through more than a couple eps of Buffy in mplayer without lockage, and running folding@home overnight seems to do the trick too.
I don't get a problem with mplayer or xine, just Azureus and have started to wonder if there is some form of conflict between gcj and the Sun JVM (someone else needs to answer it as I don't have a clue about it)
I've tried backing off to the 741 kernel (FC3), and while that's better, it's still not crash-free.
1063_FC4 is lovely and stable on all of my boxes with 1115 being awful and the current 1137_FC4 being nice again - synaptics is still screwed on that kernel though, but not as badly kernels post 1105.
If you haven't already, definitely give your hardware at least an overnight run of memtest86+.
I'll give that shot. However, as I have plenty of other things running on it all of the time, I can't see it being a memory problem.
Other than the video cards, my hardware is an Athlon 1700+ (1466 MHz) on a Soyo SY-K7V Dragon Plus mobo (VIA KT266A), plus an extra ethernet card (tulip), SCSI (2940UW), and an extra Promise 100TX controller. Lots of drives. Any similarities to your hardware?
Sempron 2400+, Gigabyte mobo, GF4MX (64Mb), 1Gb matched DDR 333 and a whole pile of other cards in there (including an extra IDE card, SCSI, video cap and other fun things!). Looks like other than the maker of the processor, not a lot ;-)
TTFN
Paul
Ok, following up on this, I dropped in a new video card this weekend (generic Radeon 7000), and my system crashes have gone away. So the video card was indeed the culprit, must have been locking the PCI bus or something.
Now I can leave mplayer looping overnight or run folding@home without any problems. However...
With the latest rawhide kernels, I still can't run azureus for very long. Not a crash, but the OOM killer seems to take it (and other things) out abnormally early. The thing is, it happens in situations where, near as I can tell, I'm not that low on memory. I do have only 256 MB RAM, and the kernel slab debug is using a lot of memory as I documented in an earlier post to fedora-devel-list, but it seems like the swap (and I've got 512 MB of it) has hardly been touched when this happens. I am running with vm.swappiness=0, but that's supposed to just keep it from swapping until it *has* to, not stop swapping altogether (and it isn't).
Actually, I just had the OOM killer take out firefox while I was bugzilla'ing something else :( Here's what it has to say for itself. This is under kernel-2.6.10-1.1141_FC4(.i686):
http://kuoi.asui.uidaho.edu/~wes/oom-sucks.txt
Anyone here that can tell if that was premature? Or should I post that to the fedora-devel-list?
--wes
tir, 15.02.2005 kl. 07.34 skrev Wes Shull:
Ok, following up on this, I dropped in a new video card this weekend (generic Radeon 7000), and my system crashes have gone away. So the video card was indeed the culprit, must have been locking the PCI bus or something.
Now I can leave mplayer looping overnight or run folding@home without any problems. However...
With the latest rawhide kernels, I still can't run azureus for very long. Not a crash, but the OOM killer seems to take it (and other things) out abnormally early. The thing is, it happens in situations where, near as I can tell, I'm not that low on memory. I do have only 256 MB RAM, and the kernel slab debug is using a lot of memory as I documented in an earlier post to fedora-devel-list, but it seems like the swap (and I've got 512 MB of it) has hardly been touched when this happens. I am running with vm.swappiness=0, but that's supposed to just keep it from swapping until it *has* to, not stop swapping altogether (and it isn't).
Actually, I just had the OOM killer take out firefox while I was bugzilla'ing something else :( Here's what it has to say for itself. This is under kernel-2.6.10-1.1141_FC4(.i686):
Yeah, the OOM is "a bit" rash and stupid. I had a pc which i sent a 25 pages pdf (or was it ps) document to the printer - which was controlled by gimp-print.
Needless to say, the system ran out of its 128 MB's of RAM in about 2 secounds, trashing the harddrive for about 10 minutes, killing off about *everything* (including gnome dock etc.) - *EXEPT* the wild goose gs (ghostscrip) prosess eating 100 MB's of RAM and 500 MB's of swap. I eventually resorted to the power-cutting method of killing the process...
When speaking of videocards and instability - i had a Vodoo PCI card which had the bad habbit of suddenly resetting itself without warning. I cant forget the first time it happened - i was showing some techy Linux for about the first time. I was really, really impressed, and i was just coming around to "stability". Then it happened. The monitor (i have 10 kg's of glass and vacum sitting on my desktop, its a shame the vacum dosn't lift the monitor more...) made a *click*, and went to black with rolling stripes on the screen. I thing about the only open app was evolution...
The pc didn't actually *crash* - it just locked up the PCI bus or something. At least it seemed like it was probing for HW all the time - the floppy/cdrom blinked (just as it does when inserting a usb mass storage device, and hotplug loads the mass storage driver) constantly - and the switch told a tale of loosing the network connection every 10 secounds... Anyway, i was able to ssh in, and restart the machine.
this was during fc1, i.e. the Linux 2.4 days.
Kyrre
-
Kyrre Ness Sjobak -
Paul F. Johnson -
Wes Shull