We have been running 2.4.17-may with the timer patch and have been doing a
battery of tests for a class that we are preparing and it is behaving
perfectly. We have tested QDIO, guest lans, all sorts of journaling file
systems, ACL/EA, devfs .... It hasn't crashed since we brought it up -
about 2 weeks... Carlos :-)
Saying goes: Great minds think alike - I say: Great minds think for
themselves!
Carlos A. Ordonez
IBM Corporation
Server Consolidation
|---------+--------------------------->
| | Mike Kershaw |
| | <[EMAIL PROTECTED]|
| | ist.edu> |
| | Sent by: Linux |
| | on 390 Port |
| | <[EMAIL PROTECTED]|
| | RIST.EDU> |
| | |
| | |
| | 06/20/2002 12:30|
| | PM |
| | Please respond |
| | to Linux on 390 |
| | Port |
| | |
|---------+--------------------------->
>-------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| From:
|
| Subject: 2.4.17-may timer pop problems
|
|
|
>-------------------------------------------------------------------------------------------------------------------------------|
I'm running 2.4.17-may with the no timer patch, qdio, and guest lans.
I've noticed it has the highly unfortunate tendency to just completely drop
dead with no errors on the console. The console drops into CP READ on
any attempt to interact with the linux/390 system, and will not resume.
a re-IPL is the only route left.
No panic message or anything useful.
It doesn't seem to be load dependent - happens fully idle, happens in the
middle of compiling. Happens doing network traffic, happens sitting there
doing nothing, happens with the console attached and with the console
disconnected (hey, it was worth a shot). Usually happens within 15-25
minutes
of IPL.
Anyone else encounter this?
-m
--
Michael Kershaw
[EMAIL PROTECTED]
Linux Systems Programmer, Information Technology
"Don't worry, I'm sure they'll listen to Reason." -- Fisheye, Snowcrash
