[icecast] Re: Compiling ices
karl at pts.tele2.co.uk
Mon Feb 3 13:27:26 PST 2003
On Mon, 2003-02-03 at 21:02, Marc Remijn wrote:
> Same problem.
> invalid operand: 0000
> CPU: 0
> EIP: 0010:[<d08895b1>] Not tainted
> EFLAGS: 00010006
> eax: 0000000e ebx: 00003556 ecx: cff5b6b8 edx: cff5b6b8
> esi: 0000e000 edi: 00000007 ebp: cd351f64 esp: cd351f4c
> ds: 0018 es: 0018 ss: 0018
> Process ices (pid: 278, stackpage=cd351000)
> Stack: 00000202 cd582c10 00008000 cff5b670 cff5b6b8 0000ffff 00018000 0001c000
> 00010000 00014000 d088711c cff5b670 00000000 cd582c10 ffffffea 00008000
> 00000000 00000000 ce4cdde0 00000000 c012db45 cd582c10 0805a720 00008000
> Call Trace: [<d088711c>] [<c012db45>] [<c0106d7b>]
> Code: 0f 0b 5b 5e 5f 5d 83 c4 18 c3 90 83 ec 04 56 53 8b 44 24 10
> Module Size Used by Not tainted
ok, now you've eliminated both the memory and module cases, try an
updated kernel, latest stable is 2.4.20, although there are some interim
patches which will become 2.4.21 eventually.
If 2.4.20 also shows the same problem then you'll have to report it to
the kernel mailing list or maintainer of the code in question. You'll
need to decode the oops (above) with ksymoops to get a stack trace.
You can try to isolate certain things, ices (in your case) mainly reads
from dsp and writes on network sockets. The encoding part of ices is
very unlikely to cause the panic but the ksymoops output is more likely
to indicate the area of concern.
If you need more help email me directly, as this is not really an ices
or icecast issue.
<p>--- >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.
More information about the Icecast