linux-mips
[Top] [All Lists]

Re: Qube2 slowly dies

To: "Kevin D. Kissell" <kevink@paralogos.com>
Subject: Re: Qube2 slowly dies
From: Glyn Astill <glynastill@yahoo.co.uk>
Date: Mon, 15 Jun 2009 21:34:57 +0000 (GMT)
Cc: linux-mips@linux-mips.org
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s1024; t=1245101697; bh=sBeAL6SOj1vhW4UcbOM5ggHmKlPJWpahel2mbl2/18A=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding; b=zzhRwQ8920Ir00z0T80x14H6PDVN74rMmQOgFDutQYvtJPfcx0JZwf1cX2D+30YtRT3D/yA2q+yrV89T/VSopaIRr/EyduSroGondn3fQe2zvR3XyoIWjSXenzrWGru1GRr68s2XO3zac9Qymi6bX2cN2J3MDbbKQSalKVentdk=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Z3v+hc4G8OWSTtKNfAEvq0QVTfKu6oRAc/3h0tdpdr63WzzqurE+GlmrD4t3yHPfUxuibcFRnQ+8VgQA00oP+OeeflUgSpNhV0iKKZnIZKx3tQn5Rko0qLCLqI3belE/lwsqzGLVAD6koiFnnc2RW4gJOsGfAGzUZFTBJCo3PKg=;
Original-recipient: rfc822;linux-mips@linux-mips.org
Sender: linux-mips-bounce@linux-mips.org


--- On Fri, 12/6/09, Kevin D. Kissell <kevink@paralogos.com> wrote:
>   
>     Your description sounds an awful lot
> like failures I've seen when 
> interrupts get lost or blocked for some reason (could be
> hardware, the 
> kernel, or some interaction between them).  Have you
> looked at 
>  to see if "Spurious" interrupts are
> occurring, or if 
> the rate of serviced timer and I/O interrupts decreases or
> increases as 
> the system degrades?
>     
>   
>   
> No I haven't checked - but I will. What would I be
> looking for that would stick out as "spurious"?
> The type of interrupt, qty or random interrupts appearing
> and dissapearing?
>   
> 
> There's a separate counter, and /proc/interrupts
> report, for spurious
> interrupts.
> 
>

I've just tested it and I see no extra counters appearing, unless the cascade 
is an issue

deb:~#  cat /proc/interrupts
           CPU0
  0:          1          XT-PIC  timer
  2:          0          XT-PIC  cascade
  8:          2          XT-PIC  rtc0
  9:          0          XT-PIC  ohci_hcd:usb1, ehci_hcd:usb2, ohci_hcd:usb3
 14:       3166          XT-PIC  ide0
 15:          0          XT-PIC  ide1
 18:          0            MIPS  cascade
 19:       4399            MIPS  eth0
 21:        361            MIPS  serial
 22:          0            MIPS  cascade
 23:     274025            MIPS  timer
 32:          2         GT641xx  gt641xx_timer0


When the machine starts to go, the cpu time column in top sometimes shows nan - 
surely that shouldn't happen -it should be either 0 or >0 
 
Any other ides chaps?


      

<Prev in Thread] Current Thread [Next in Thread>