[icecast] Re: Compiling ices

[Rene Pfeiffer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Feb 02, 2003 at 2348 +0100, Marc Remijn appeared and said:
> > On Fri, 2003-01-31 at 06:39, Marc Remijn wrote:
> > ...
> >
> > > Kernel output:
> > >
> > > invalid operand: 0000
> > > CPU:    0
> > > EIP:    0010:[<d08e25b1>]    Tainted: PF
> > > EFLAGS: 00010006
> > > eax: 0000000e   ebx: 00003556   ecx: ce44c728   edx: ce44c728
> > > esi: 0000e000   edi: 00000007   ebp: c288bf64   esp: c288bf4c
> > > ds: 0018   es: 0018   ss: 0018
> > > Process ices (pid: 2707, stackpage=c288b000)
> > > Stack: 00000202 cc3fbac0 00008000 ce44c6e0 ce44c728 0000ffff 00018000
> 0001c000
> > >        00010000 00014000 d08e011c ce44c6e0 00000000 cc3fbac0 ffffffea
> 00008000
> > >        00000000 00000000 c4745ea0 00000000 c012db45 cc3fbac0 0805c720
> 00008000
> > > Call Trace: [<d08e011c>] [<c012db45>] [<c0106d7b>]
> > >
> > > Code: 0f 0b 5b 5e 5f 5d 83 c4 18 c3 90 83 ec 04 56 53 8b 44 24 10
> >
> > This isn't from ices, this is from the kernel. Something went wrong
> > during the time ices was running.  [...]
> >
> > There are a few possibilities that could cause this kernel panic, [...]
> 
> Hmm. This machine has been working for years without any problem. I
> installed more memory, but with this memory it has been running for months
> now, also without problems. There are quite a number of fans in the case.

Memory modules can age and can create the funniest problems when under
different load. I have a machine that handles RSYNC copies of several
GBs perfectly and every application that tries to shove the very same
GBs over NFS to the fileserver crashes with similar error messages as
you have provided. Maybe ices also stresses some memory pages more or
different to other applications. Try running memtest86 on your machine
if you can take it offline for a couple of hours (or days). You can also
test your modules in a different machine if you need the machine in
question.

> > The main thing that can be done to remove the possibility of a kernel
> > panic is having a recent kernel. The gcc release you have should be
> > fine.
> 
> I might build a new kernel to see if that solves the problem.

It might not. Which GCC and which kernel did you use?

Cheers,
Lynx.

- -- 
 GNU/Linux Manages! - Linux Solution Provider
  RP551296-NICAT    - Free Software for Open Minds

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+PaJReMu5lRpXJ7kRAkepAKDYDmiVpL3UKYHZCN1hFmKwFDommgCfahUl
m46c6G97b0N9ZQ1poE6eQl4=
=QL+t
-----END PGP SIGNATURE-----
--- >8 ----
List archives:  http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to 'icecast-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.