I currently have Icecast 2.3.1 running with Darkice on a Fedora Core 4 box (with the 2.6.14 kernel). We have three streams running (all mp3) @ 128kbs, 64kbs, and 24kbs. I am consistently seeing the following error: kernel: Unable to handle kernel paging request at virtual address ffffffff It does appear to be icecast causing the error. Oddly, when this first started showing up, it would crash icecast entirely - meaning I couldn't get any stream. Now, it seems that icecast continues to run, but only one or two of the streams will fail. Any ideas? I have a friend who's also looking around, but we're pretty stumped as to what's causing the error. Thanks, Bryan P.S. This is a brand new hard drive, and a brand new installation of fedora core and icecast. The computer itself is about 3 years old (Dell).
Bryan Brown wrote:> I currently have Icecast 2.3.1 running with Darkice on a Fedora Core 4 > box (with the 2.6.14 kernel). We have three streams running (all mp3) @ > 128kbs, 64kbs, and 24kbs. > > I am consistently seeing the following error: > > kernel: Unable to handle kernel paging request at virtual address ffffffff > > It does appear to be icecast causing the error. Oddly, when this first > started showing up, it would crash icecast entirely - meaning I couldn't > get any stream. Now, it seems that icecast continues to run, but only > one or two of the streams will fail. > > Any ideas? I have a friend who's also looking around, but we're pretty > stumped as to what's causing the error.While icecast could be a trigger case in your setup, there isn't anything within icecast that is known to do this, and depending on what the actual cause is will also affect how icecast runs afterwards. I do see a 2.6.15 out so there may already be a fix, but you'll have to decode that oops output for the 2.6.14 to see where it fails if you want to investigate it. There is information out there to do the decode but we can't say based on what you've said whether it's a driver bug or bad hardware. karl.
On Thu, 2006-01-12 at 10:20 -0800, Bryan Brown wrote:> I currently have Icecast 2.3.1 running with Darkice on a > Fedora Core 4 box (with the 2.6.14 kernel). > I am consistently seeing the following error: > kernel: Unable to handle kernel paging request at virtual > address ffffffff > It does appear to be icecast causing the error.I compiled Icecast 2.3.1 on a Fedora core 4/2.6.14 and saw no problem. I also run the icecast server on it, no problem. Can you assume your hardware is 100% OK? -- A powerfull GroupWare, CMS, CRM, ECM: CPS (Open Source & GPL). Opengroupware, SPIP, Plone, PhpBB, JetSpeed... are good: CPS is better. http://www.cps-project.org for downloads & documentation. Free hosting of CPS groupware: http://www.objectis.org.
Rakotomandimby Mihamina wrote:> I compiled Icecast 2.3.1 on a Fedora core 4/2.6.14 and saw no problem. > I also run the icecast server on it, no problem. > Can you assume your hardware is 100% OK?Well... no. I can't really assume anything at this point. The computer itself isn't *that* old (3 to 4 years), so having the original hard drive crash was a bit of a surprise. The strange part is it varies so wildly. I'll get anywhere from two hours to 5 days of uptime before either icecast or the system crashes - all with the same error. John Hebert wrote: > This may be a long shot, but I smell bad hardware. > > Copy the drive to a similar box and test. If that > isn't possible, try testing your RAM with mem86. I did install the old hard drive in a new box, but it wouldn't even take a reinstall. The RAM is a good place start, but at this point, I may just save myself the trouble and purchase a new box. In any case, the feedback was very helpful. Thanks folks. Bryan
Rakotomandimby Mihamina wrote:> On Thu, 2006-01-12 at 10:20 -0800, Bryan Brown wrote: > > I compiled Icecast 2.3.1 on a Fedora core 4/2.6.14 and saw no problem. > I also run the icecast server on it, no problem. > Can you assume your hardware is 100% OK? >Question about you're configuration: Are you using a live encoder, and if so, which one? At this point I'm suspecting that something in DarkIce is causing Icecast to initiate the error. I ran memtest86 for 2 hours, no errors detected. The next step is to rebuild the kernel, which I *really* don't want to do - at least I don't have time for it in the immediate future. Anyway, just curious. Thanks. Bryan
Just for documentation, I wanted to follow up on how we resolved this... We ended up replacing the memory, motherboard and processor - in that order. Luckily, we got the motherboard and processor replaced under warranty. It appears that something was wrong with processor. Nothing else we replaced solved the problem. Dell decided, when replacing the motherboard, NOT to replace the CPU chip - which resulted in them making two trips out here instead of one. In any case, thanks to everyone who provided feedback. It did end up being a hardware problem. Bryan P.S. The Gentoo installation of Icecast/Darkice was ridiculously simple. The Gentoo installation itself, on the other hand.... Bryan Brown wrote:> I currently have Icecast 2.3.1 running with Darkice on a Fedora Core 4 > box (with the 2.6.14 kernel). We have three streams running (all mp3) @ > 128kbs, 64kbs, and 24kbs. > > I am consistently seeing the following error: > > kernel: Unable to handle kernel paging request at virtual address ffffffff > > It does appear to be icecast causing the error. Oddly, when this first > started showing up, it would crash icecast entirely - meaning I couldn't > get any stream. Now, it seems that icecast continues to run, but only > one or two of the streams will fail. > > Any ideas? I have a friend who's also looking around, but we're pretty > stumped as to what's causing the error. > > Thanks, > > Bryan > > P.S. This is a brand new hard drive, and a brand new installation of > fedora core and icecast. The computer itself is about 3 years old (Dell). > _______________________________________________ > Icecast mailing list > Icecast@xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > >