[parisc-linux] 9000/819/K210

[parisc-linux] 9000/819/K210

[Stephan Trajkoff]

Hello,
anybody has PDF with specification of this server?
Is there any PCI ot EISA slots???
I can't compile kernel stable...

-->> FREE Perl CGI scripts add WEB ACCESS to your
-->> POP E-Mail accounts! Download today!! http://www.adjeweb.com

Re: [parisc-linux] 9000/819/K210

[Grant Grundler]

"Stephan Trajkoff" wrote:
> Hello,
> anybody has PDF with specification of this server?

All sorts of manuals for K-class here:
	http://docs.hp.com/hpux/hw/index.html

> Is there any PCI ot EISA slots???

No.

> I can't compile kernel stable...

Can you post the error messages and describe the steps you used to build?

grant

Re: [parisc-linux] 9000/819/K210

[Stephan Trajkoff]

Hello,
TEAM from esiee.fr told me that it is common SMP problem...
after heavy compilation, 'w' and 'ps ax' don't work

Re: [parisc-linux] 9000/819/K210

[Grant Grundler]

Stephan Trajkoff wrote:
> Hello,
> TEAM from esiee.fr told me that it is common SMP problem...
> after heavy compilation, 'w' and 'ps ax' don't work

My a500 has been running -pa52 and iteratively built 88 linux kernels
since yesterday. Both w and ps ax still work. Something else must be
triggering the problem.

grant

Re: [parisc-linux] 9000/819/K210

[Thibaut VARENE]

Le lundi 8 juillet 2002, =E0 06:32 , Grant Grundler a =E9crit :

> Stephan Trajkoff wrote:
>> Hello,
>> TEAM from esiee.fr told me that it is common SMP problem...
>> after heavy compilation, 'w' and 'ps ax' don't work
>
> My a500 has been running -pa52 and iteratively built 88 linux kernels
pa52 ? Well, if you're one step further than everyone, that's kinda=20
cheating :^)
> since yesterday. Both w and ps ax still work. Something else must be
> triggering the problem.
Do you mean that the hangs Ryan and I are studying should be solved by=20=

your changes ?
Anyway, I have noticed that on J5k and A500, using the 'normal IO' mode=20=

for the SYM53C8XX driver
seems to decrease risk of such hangs (running 2 setis on both machines=20=

and building ISOs on the
A500 for about 4 days, pa46 on both, without hangs, where the A500 could=20=

only run for about
3 hours is the same conditions with the MMIO mode, 1 day in the best=20
case.)

But I had not enough time to investigate further, so it should only be=20=

considered as a
*interesting coincidence* :)

I have now installed pa51 on these boxes, so I'll keep checking for=20
hangs.


Thibaut VARENE
PA/Linux ESIEE Team
http://pateam.esiee.fr/

Re: [parisc-linux] 9000/819/K210

[Grant Grundler]

Thibaut VARENE wrote:
> pa52 ? Well, if you're one step further than everyone, that's kinda=20
> cheating :^)

yeah...I was going to test/commit the lvm10 patch but didn't have extra disks
to trash on that box...

> > since yesterday. Both w and ps ax still work. Something else must be
> > triggering the problem.
> Do you mean that the hangs Ryan and I are studying should be solved by=20=
> your changes ?

no. Just providing another data point...

> Anyway, I have noticed that on J5k and A500, using the 'normal IO' mode=20=
> for the SYM53C8XX driver seems to decrease risk of such hangs (running
> 2 setis on both machines and building ISOs on the A500 for about 4 days,
> pa46 on both, without hangs,

Did you stop the machine at this point or did it hang?
ie has anyone seen a hang when sym53c8xx driver was using IO port space?

> where the A500 could only run for about
> 3 hours is the same conditions with the MMIO mode, 1 day in the best=20
> case.)

This really suggests the problem is with disk IO and not compilation.
And it stinks like a "PCI Posted Write" problem.

Have you been able to get a TOC dump and decode where it was hung?

> But I had not enough time to investigate further, so it should only be=20=
> considered as a *interesting coincidence* :)

ok.

> I have now installed pa51 on these boxes, so I'll keep checking for=20
> hangs.

Finding the address of where the CPUs are spinning or hung would be good.
BTW, this is with SMP or non-SMP kernels?

grant

Re: [parisc-linux] 9000/819/K210

[Thibaut VARENE]

Le lundi 8 juillet 2002, =E0 10:27 , Grant Grundler a =E9crit :
>
>> Anyway, I have noticed that on J5k and A500, using the 'normal IO'=20
>> mode=3D20=3D
>> for the SYM53C8XX driver seems to decrease risk of such hangs =
(running
>> 2 setis on both machines and building ISOs on the A500 for about 4=20
>> days,
>> pa46 on both, without hangs,
>
> Did you stop the machine at this point or did it hang?
> ie has anyone seen a hang when sym53c8xx driver was using IO port =
space?
I had to stop the box, no hang, just some kernel upgrade needed...
>
>> where the A500 could only run for about
>> 3 hours is the same conditions with the MMIO mode, 1 day in the =
best=3D20
>> case.)
>
> This really suggests the problem is with disk IO and not compilation.
> And it stinks like a "PCI Posted Write" problem.
yup, also what I thought, though no big knowledge on that topic...
Anyway I'm pretty convinced this is a I/O pb, which seems to be =
confirmed
by the observations Ryan and I made:
all stuck processes are always in 'down_read' or 'down_write' state when
hanging...
>
> Have you been able to get a TOC dump and decode where it was hung?
No, I have just got some 't' SysRq dump (special 't', from Ryan's patch)
Anyway next time it will hang i'll try to dump.
The fact is that hangs i got till now aren't 'deadly' ones in the =
meaning
that I've always been able to reboot the box more or less gently (i.e.
most of the time via 'S.U.B.' SysRqs), that's why I didn't think about=20=

TOC,
because the box wasn't technically *dead*, and I tried to avoid data=20
corruption :)
>
>> I have now installed pa51 on these boxes, so I'll keep checking =
for=3D20
>> hangs.
>
> Finding the address of where the CPUs are spinning or hung would be=20
> good.
Sure. I'm supposed to find this in PDC after a TOC, right ?

> BTW, this is with SMP or non-SMP kernels?
All problems are coming on SMP kernels. I've never seen such hangs on UP
systems (thank God, it would be awful to restart our webserver every=20
day!)

I'm currently stressing a bit a B2000 to confirm that (seti+kernel=20
builds...)


Thibaut VARENE
PA/Linux ESIEE Team
http://pateam.esiee.fr/

Re: [parisc-linux] 9000/819/K210

[Grant Grundler]

Thibaut VARENE wrote:
> > ie has anyone seen a hang when sym53c8xx driver was using IO port =
> space?
> I had to stop the box, no hang, just some kernel upgrade needed...

ok.

> Anyway I'm pretty convinced this is a I/O pb, which seems to be =
> confirmed
> by the observations Ryan and I made:
> all stuck processes are always in 'down_read' or 'down_write' state when
> hanging...

hmm...I've not mucked with the semaphore code and don't pretend to
understand it.

> No, I have just got some 't' SysRq dump (special 't', from Ryan's patch)

This is better than TOC for the reasons you mentioned. 
Please post whatever output you can get from SysRq and
don't bother with the TOC unless the SysRq doesn't work.

> All problems are coming on SMP kernels. I've never seen such hangs on UP
> systems (thank God, it would be awful to restart our webserver every=20
> day!)

ok.

thanks,
grant