On Wed, May 17, 2000 at 03:27:11PM +1000, Anand Kumria wrote: > On Tue, May 16, 2000 at 02:51:12PM -0400, Josh Kuperman wrote: > > I am baffled by some odd behavior, which seem to have started after I > > upgraded to the frozen/potato dist of debian-sparc. I have no reason > > Such as? A few examples and someone else may have encountered the same > thing.
I have already mentioned some of them on this list: 1a. esp0: Gross Error sreg=51 1b. esp0: Gross Error sreg=53 This should be a SCSI error, but I didn't see it happen until after I upgraded. On the other hand I didn't start looking through the dmesg and syslog files closely until I noticed other problems. 2. When I start Squid the following, as shown bellow from /var/log/squid/cache.log, happens. I'm running on the kernel-image-2.2.15-sun4dm-smp kernel. Ben told me he is running a 2.2.15 sun4u kernel and is having no problems at all with Squid. The machine has 512M of RAM, and a 9G Seagate Barracuda Disk drive. 2000/05/17 09:36:09| Starting Squid Cache version 2.2.STABLE5 for sparc-debian-l inux-gnu... 2000/05/17 09:36:09| Process ID 350 2000/05/17 09:36:09| With 1024 file descriptors available 2000/05/17 09:36:09| helperOpenServers: Starting 5 'dnsserver' processes 2000/05/17 09:36:09| assertion failed: StatHist.c:93: "((int) floor(0.99L + stat HistVal(H, 0) - min)) == 0" It could be a problem specific to the kernel I'm running. It might be hardware in the machine, perhaps the floating point unit, has failed. I could move things try a different mother board(?) but I'd want to pin things down. I could try a single processor kernel or actually remove a processor. I'm not really sure what info is useful to post as far as getting help with diagnosing the problems. > > > to believe that the distribution itself is responsible for any of the > > particulars, but I'd like to check. Is there an easy way to check. > > > > I have ideas, but I suspect they are all bad ideas. > > > > 1. Install an old version on a different disk/partition. (I have spare > > disks and partitions - I'm just not sure how to do this.) > > Another option is to install it in a chroot environment. I believe > that is how a few other developer hadnle developing for slink, potato > and woody. How would I do that? Would it provide a good way to test to see if the kernel or libraries are causing the problems I mentioned above? > > > Anand -- Josh Kuperman [EMAIL PROTECTED]
