5 May
2004
5 May
'04
8:28 a.m.
Having seen the recommendations for gcdmaster, and because my partner
has lots of tapes she wants to archive to CD, I installed it on her
(recent Debian snapshot) system.
It worked very nicely for about 5-10 minutes and then crashed with a
segfault, whilst editing track marks. Repeatedly.
Anyone know what environmental factors can affect this? Somebody must
have it running more stable than that to abe able to use it. The version
of gcdmaster seems to be the latest - 1.1.7
Hardware: AMD Duron 1300, 512M RAM, onboard CMI sound chip,
run-of-the-mill IDE drive. Lots of USB devices (printer,
mouse, KB, scanner)
Software: Kernel 2.4.25, Gnome 2.4 desktop.
If it doesn't work we'll be back to doing it the hard way with Audacity,
which at least works.
I might try with a small enough audio file to fit all in memory, in case
it's a VM problem. And better check there is a swap partition - I'm sure I
installed one....!
Any suggestions gratefully welcomed.
PS just seen that version 1.1.8 is available. Better try that too...
--
Anahata
anahata(a)treewind.co.uk Tel: 01638 720444
http://www.treewind.co.uk Mob: 07976 263827
5 May
5 May
8:43 a.m.
1.1.8 is the last: http://cdrdao.sourceforge.net/download.html
======= On Wednesday 05 May 2004 16:07, Anahata wrote: =======
Having seen the recommendations for gcdmaster, and because my partner
has lots of tapes she wants to archive to CD, I installed it on her
(recent Debian snapshot) system.
It worked very nicely for about 5-10 minutes and then crashed with a
segfault, whilst editing track marks. Repeatedly.
Anyone know what environmental factors can affect this? Somebody must
have it running more stable than that to abe able to use it. The version
of gcdmaster seems to be the latest - 1.1.7
Hardware: AMD Duron 1300, 512M RAM, onboard CMI sound chip,
run-of-the-mill IDE drive. Lots of USB devices (printer,
mouse, KB, scanner)
Software: Kernel 2.4.25, Gnome 2.4 desktop.
If it doesn't work we'll be back to doing it the hard way with Audacity,
which at least works.
I might try with a small enough audio file to fit all in memory, in case
it's a VM problem. And better check there is a swap partition - I'm sure I
installed one....!
Any suggestions gratefully welcomed.
PS just seen that version 1.1.8 is available. Better try that too...
--
Anahata
anahata(a)treewind.co.uk Tel: 01638 720444
http://www.treewind.co.uk Mob: 07976 263827
2:27 p.m.
On Wed, May 05, 2004 at 01:07:51PM +0100, Anahata wrote:
Having seen the recommendations for gcdmaster, and
because my partner
has lots of tapes she wants to archive to CD, I installed it on her
(recent Debian snapshot) system.
It worked very nicely for about 5-10 minutes and then crashed with a
segfault, whilst editing track marks. Repeatedly.
Anyone know what environmental factors can affect this? Somebody must
have it running more stable than that to abe able to use it. The version
of gcdmaster seems to be the latest - 1.1.7
hmmm...no crashes with gcdmaster here. I have ~700 Meg of RAM and a 1.2 gig
swap partition and I have been loading a 546 Meg file and playing with it
the past while. Box has a PIII Coppermine chip. Seems stable for me on
Fedora Core linux and the latest gcdmaster code. One thing I would check is to ensure that
you have the right options for your CD in /etc/cdrdao.conf or the equivalent
~/.cdrdao.conf. One thing that I wish gcdmaster would have is better options for
manipulation of the actual cdrdao commands.
--
Jack Bowling
mailto: jbinpg(a)shaw.ca
5:51 p.m.
It worked very nicely for about 5-10 minutes and then
crashed with a
segfault, whilst editing track marks. Repeatedly.
I smell a heat problem, or something silly like a glibc or g++
mismatch/build issue. C++ programs built with pre gcc-3.2 compilers
shouldn't be mixed with libraries built with post gcc-3.2 compilers [and
vice-versa].
Anyone know what environmental factors can affect
this? Somebody must
have it running more stable than that to abe able to use it. The version
of gcdmaster seems to be the latest - 1.1.7
Hardware: AMD Duron 1300,
^^^^^^^^^^^^^^^^^^^^^^^^
Oooooh, I really smell a heat problem if those Durons are anything like the
Thunderbird Athlons.
Install the lm_sensors drivers <http://secure.netroedge.com/~lm78/> and try
to get a "sensors" output of your CPU's temperature just after a segfault.
The Dark Lord prefers Liquid Nitrogen Cooling on his servers, since they are
hallmarks of Quality,
=MB=
--
A focus on Quality.
6:48 p.m.
On Wed, May 05, 2004 at 02:43:41PM -0700, Malcolm Baldridge wrote:
Durons don't run particularly hot, and this one's got a Zalman flower
clooler on it - they're pretty good but I might check the BIOS
temperature reading.
I smell a heat problem
Nothing else breaks that badly.
or something silly like a glibc or g++
mismatch/build issue. C++ programs built with pre gcc-3.2 compilers
shouldn't be mixed with libraries built with post gcc-3.2 compilers [and
vice-versa].
Wouldn't know about that, but upgrading to ver 1.1.8 made it behave a
lot better. Usable, but not perfect. It's possible the earlier version
wasn't fully compatible with Gnome 2.4
Hardware: AMD
Duron 1300,
Oooooh, I really smell a heat problem if those Durons are anything like the
Thunderbird Athlons. Install the lm_sensors drivers
<http://secure.netroedge.com/~lm78/> and try
to get a "sensors" output of your CPU's temperature just after a segfault.
It would be good if I could get that working.
--
Anahata
anahata(a)treewind.co.uk -+- http://www.treewind.co.uk
Home: 01638 720444 Mob: 07976 263827
7:44 p.m.
Nothing else breaks that badly.
Not knowing the specifics of the code in question, it's possible that
(buggy?) code which burns alot of CPU would show up a heat problem where a
properly functioning program which doesn't sit-and-spin would not.
If you can rebuild your kernel 6 times in a row (make clean ; make bzImage ;
make clean ; make bzImage) etc, without getting a signal 11 from gcc, then
heat's most likely not your problem. "sensors" will be more scientific
about this.
It's just that 5-10 minutes is a "long time" in code execution time frames.
Possibilities include:
1) Hardware fault [heat or bad ram]
2) Memory leak [bad or mismatched libraries, or old/mismatched ALSA
libs+drivers?]
See if you can lengthen the amount of time the program can run by killing
off all but the most necessary background tasks. If there's a correlation
between runtime and the amount of free memory at the time you run this tool,
then 2) is pretty much your issue.
If you've done some "partial upgrades" of various components, you may want
to look into a "rebuild" of your library infrastructures.
In the end, even Dear Frodo couldn't bear to destroy Quality,
=MB=
--
A focus on Quality.
7739
days inactive
7739
days old
linux-audio-user@lists.linuxaudio.org
5 comments
4 participants
participants (4)
-
Anahata -
Andrew Gaydenko -
Jack Bowling -
Malcolm Baldridge