[correcting lamont's e-mail] LaMont: have you been seeing further "random segfault" bugs on peri/penalosa over the past week or two? Is this something you can monitor for us?
Rest inline.. On Thu, Sep 10, 2009 at 12:10:28PM -0400, Carlos O'Donell wrote: > On Tue, Sep 8, 2009 at 11:53 PM, dann frazier<da...@dannf.org> wrote: > > We have been running with UP kernels for quite some time, and they > > haven't proven to be any more stable. Most recently I've upgraded > > peri/penalosa to 2.6.31-rc6-based kernels since they were inclusive of > > the various changes I was pointed to on this list (thanks John/Helge). > > Where exactly did you get this kernel, do you have a URL reference? The debian kernel team does nightly snapshot builds of our source. I took this source & built the parisc64 (UP) flavor: http://people.debian.org/~dannf/tmp/ > > > peri has been surprisingly stable - uptime of 2 weeks so far, and it > > seems to be under pretty steady build load. > > That sounds great. da...@peri:~$ uptime 16:56:09 up 15 days, 17:13, 2 users, load average: 2.25, 2.39, 2.31 > > penalosa is a different story - it has been very unstable with uptimes > > of several hours at most. The hardware/kernel packages are identical > > to that of peri (afaict), so I'm not sure why. The failure mode > > results in infinite panics being printed to the console - but every > > time I've seen it I haven't had enough console history to see the > > beginning of this crash. I am now logging the console to see if I can > > capture that. It is of course possible that penalosa is having > > hardware problems - but I don't know of a way to prove this > > conclusively. We could maybe swap disks to see if the failure follows > > the disks or the hardware (though that doesn't eliminate a disk > > problem). > > The way to prove this is to put an instrumented kernel on penalosa. > > I think the way forward is: > * You get me a console trace. > * I give you an instrumented kernel/initrd. > * Repeat. *nod* fyi, now that I've started logging the console, penalosa has become strangely stable: da...@penalosa:~$ uptime 16:57:22 up 1 day, 20:00, 2 users, load average: 1.99, 2.46, 2.30 The first several boots on this kernel wouldn't make it more than an hour or two. > Are you allowed to boot a kernel/initrd that I send you? I don't see why not, assuming these changes don't add a risk of producing bad binaries. > > Note that I don't monitor the build output, so I don't know if we're > > still seeing the same level of random segfaults in userland. > > LaMont? > > Cheers, > Carlos. -- dann frazier -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org