public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Roberto Slepetys Ferreira" <slepetys@homeworks.com.br>
To: "Jim Gifford" <jim@jg555.com>, <linux-kernel@vger.kernel.org>
Subject: Re: Probably 2.4 kernel or AIC7xxx module trouble
Date: Thu, 3 Jul 2003 17:15:51 -0300	[thread overview]
Message-ID: <01f101c3419f$e6d30360$3300a8c0@Slepetys> (raw)
In-Reply-To: 13e101c3419d$f62f9410$3400a8c0@W2RZ8L4S02

Hi Jim,
It's exacly the same problem, after about 12-24 hour everything locks up,
but I can still ping (sometimes).

But the syslog stops, and I only reboot by hardware, because the CTL+ALT+DEL
doesn't works, and the terminal either.

It's a SMP (dual pentium III) too, but after some tests with single CPU and
NOAPIC parameter to the kernel, the trouble continues.

I have no clue for what kind of tests I can do to generate the trouble, or
for what logs, or files to look for.

[]s
Slepetys



> Roberto,
>     How does this problem manifest itself. I think it's the same problem
> that I'm having. Let me know what you think. I'm using the megaraid driver
> and aic7xxx driver. After about a 12-20 hour period, everything locks up,
> but there is not error message. The kernel sysreq information does work
and
> I'm able to reboot.
>
> top - 12:59:05 up  3:02,  2 users,  load average: 4.17, 4.35, 4.38
> Tasks: 122 total,   5 running, 117 sleeping,   0 stopped,   0 zombie
>  Cpu0 :  25.0% user,  50.0% system,  25.0% nice,   0.0% idle
>  Cpu1 :  62.5% user,  31.2% system,   0.0% nice,   6.2% idle
> Mem:   1033896k total,   823636k used,   210260k free,   160412k buffers
> Swap:  1060280k total,        0k used,  1060280k free,   352848k cached
>
>
> ----- Original Message ----- 
> From: "Roberto Slepetys Ferreira" <slepetys@homeworks.com.br>
> To: "Roberto Slepetys Ferreira" <slepetys@homeworks.com.br>; "Justin T.
> Gibbs" <gibbs@scsiguy.com>; <linux-kernel@vger.kernel.org>
> Sent: Thursday, July 03, 2003 11:29 AM
> Subject: Re: Probably 2.4 kernel or AIC7xxx module trouble
>
>
> > Ops....
> > The linux box halted again, after 12 hours operating normaly.
> >
> > The more strange is that there isn't any message in the
/var/log/message,
> > the system simples stop to respond, and some strange behavior is that
the
> > TOP comand gaves me :
> >
> > 15:10:15     up   33 min, 1 user, load average: 1.06, 1.17, 1.14
> > 91 processes: 90 sleeping, 1 running, 0 zombie, 0 stopped
> > CPU0 states:   0.0% user   3.1% system    0.0% nice   0.0% iowait  96.2%
> > idle
> > CPU1 states:   0.0% user   0.1% system    0.0% nice   0.0% iowait  99.2%
> > idle
> > Mem:   513172k av,  437740k used,   75432k free,       0k shrd,   17500k
> > buff
> >                     258436k actv,   41792k in_d,   76644k in_c
> > Swap: 1060088k av,      44k used, 1060044k free                  339860k
> > cached
> >
> >   PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME CPU
COMMAND
> >     9 root      16   0     0    0     0 SW    0.8  0.0   0:02   0
> > kscand/Normal
> >    31 root      15   0     0    0     0 DW    0.5  0.0   0:05   0
> raid1syncd
> >  2425 root      15   0  1088 1088   864 R     0.2  0.2   0:00   1 top
> >     1 root      15   0   396  396   344 S     0.0  0.0   0:03   1 init
> >     2 root      RT   0     0    0     0 SW    0.0  0.0   0:00   0
> > migration/0
> > ... others...
> >
> > Meanning that the Load Average is incompatible with the use of the CPUs.
> >
> > I really have no idea where to find some clue about what is going on.
> >
> > Thanks
> > Roberto Slepetys
> >
> >
> >
> > ----- Original Message ----- 
> > From: "Roberto Slepetys Ferreira" <slepetys@homeworks.com.br>
> > To: "Justin T. Gibbs" <gibbs@scsiguy.com>;
<linux-kernel@vger.kernel.org>
> > Sent: Wednesday, July 02, 2003 6:00 PM
> > Subject: Re: Probably 2.4 kernel or AIC7xxx module trouble
> >
> >
> > > Hi,
> > >
> > > I upgraded it for the 6.2.36, using RPM and I am making some heavy
> tests.
> > >
> > > Until now, it's ok, and for this kind of tests, the old configuration
> gave
> > > some trouble.
> > >
> > > Thanks
> > > Slepetys
> > >
> > > ----- Original Message ----- 
> > > From: "Justin T. Gibbs" <gibbs@scsiguy.com>
> > > To: "Roberto Slepetys Ferreira" <slepetys@homeworks.com.br>;
> > > <linux-kernel@vger.kernel.org>
> > > Sent: Wednesday, July 02, 2003 12:14 PM
> > > Subject: Re: Probably 2.4 kernel or AIC7xxx module trouble
> > >
> > >
> > > > > The system halts easily if I do a large I/O, like reindexing a
> > database,
> > > > > giving me some messages like: (scsi0:A:1:0): Locking max tag count
> at
> > > 128...
> > > >
> > > > The "Locking max tag count" messages are normal.  It means the SCSI
> > > > driver was able to determine the maximum queue depth of your drive.
> > > >
> > > > 6.2.8 is rather old.  I don't know that upgrading the aic7xxx driver
> > > > will solve your problem, but it might be worth a shot.  The latest
> > > > is available here:
> > > >
> > > > http://people.FreeBSD.org/~gibbs/linux/SRC/
> > > >
> > > > After upgrading, you should be at 6.2.36.
> > > >
> > > > --
> > > > Justin
> >
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel"
in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> >
>
>



  parent reply	other threads:[~2003-07-03 19:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-02 14:44 Probably 2.4 kernel or AIC7xxx module trouble Roberto Slepetys Ferreira
2003-07-02 15:14 ` Justin T. Gibbs
2003-07-02 21:00   ` Roberto Slepetys Ferreira
2003-07-03 18:29     ` Roberto Slepetys Ferreira
     [not found]       ` <13e101c3419d$f62f9410$3400a8c0@W2RZ8L4S02>
2003-07-03 20:15         ` Roberto Slepetys Ferreira [this message]
2003-07-03 21:20           ` Justin T. Gibbs
2003-07-03 23:04             ` Jim Gifford
2003-07-05 20:15               ` Justin T. Gibbs
2003-07-05 20:28                 ` Jim Gifford
2003-07-03 22:49       ` Matthias Andree
2003-07-03 23:09         ` Jim Gifford
     [not found] <4R5X.8bo.19@gated-at.bofh.it>
     [not found] ` <4Rzh.h8.25@gated-at.bofh.it>
     [not found]   ` <4WSg.5H7.21@gated-at.bofh.it>
     [not found]     ` <5h0y.5ht.25@gated-at.bofh.it>
     [not found]       ` <5iIR.7Cp.11@gated-at.bofh.it>
     [not found]         ` <5iIQ.7Cp.9@gated-at.bofh.it>
     [not found]           ` <5jOA.14o.9@gated-at.bofh.it>
     [not found]             ` <5lnu.2l7.13@gated-at.bofh.it>
2003-07-04 17:36               ` Roberto Slepetys Ferreira
2003-07-05 20:27                 ` Justin T. Gibbs
     [not found]       ` <5ldB.2cK.1@gated-at.bofh.it>
2003-07-04 17:38         ` Roberto Slepetys Ferreira

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='01f101c3419f$e6d30360$3300a8c0@Slepetys' \
    --to=slepetys@homeworks.com.br \
    --cc=jim@jg555.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox