Subject: Re: ksoftirqd using 100% CPU
On 2/10/2012 at 11:33 AM, Alan Altmark alan_altm...@us.ibm.com wrote:
On Friday, 02/10/2012 at 10:21 EST, Ron Foster at Baldor-IS
rfos...@baldor.com wrote:
I did not know that we could open a PMR with IBM directly.
Only if your Linux support contract
On Thu, Feb 09, 2012 at 04:43:25PM -0600, Ron Foster at Baldor-IS wrote:
The only messages I can find have to do with a hipersockets time out.
Feb 9 11:21:39 bus0104 kernel: NETDEV WATCHDOG: hsi0: transmit timed out
Feb 9 11:21:39 bus0104 kernel: qeth: Recovery of device 0.0.5100
started
On Fri, Feb 10th, 2012 at 11:00 PM, Joerg Reuter wrote:
On Thu, Feb 09, 2012 at 04:43:25PM -0600, Ron Foster at Baldor-IS wrote:
The only messages I can find have to do with a hipersockets time out.
Feb 9 11:21:39 bus0104 kernel: NETDEV WATCHDOG: hsi0: transmit timed
out
Feb 9
@VM.MARIST.EDU
Subject: Re: ksoftirqd using 100% CPU
On Fri, Feb 10th, 2012 at 11:00 PM, Joerg Reuter wrote:
On Thu, Feb 09, 2012 at 04:43:25PM -0600, Ron Foster at Baldor-IS wrote:
The only messages I can find have to do with a hipersockets time out.
Feb 9 11:21:39 bus0104 kernel: NETDEV
To: LINUX-390@VM.MARIST.EDU
Subject: Re: ksoftirqd using 100% CPU
On Thu, Feb 09, 2012 at 04:43:25PM -0600, Ron Foster at Baldor-IS wrote:
The only messages I can find have to do with a hipersockets time out.
Feb 9 11:21:39 bus0104 kernel: NETDEV WATCHDOG: hsi0: transmit timed out
Feb 9 11:21:39
On Friday, 02/10/2012 at 10:21 EST, Ron Foster at Baldor-IS
rfos...@baldor.com wrote:
I did not know that we could open a PMR with IBM directly.
Only if your Linux support contract is with IBM.
Alan Altmark
Senior Managing z/VM and Linux Consultant
IBM System Lab Services and Training
On 2/10/2012 at 11:33 AM, Alan Altmark alan_altm...@us.ibm.com wrote:
On Friday, 02/10/2012 at 10:21 EST, Ron Foster at Baldor-IS
rfos...@baldor.com wrote:
I did not know that we could open a PMR with IBM directly.
Only if your Linux support contract is with IBM.
But, if you've already
Hello listers,
Last night I upgraded one of the Linux guests used by our developers to
kernel level 2.6.16.60-0.95.1-default. (Latest SLES10 SP4 kernel) By
about 11:30 AM this morning, I was getting complaints from our
developers that the system was hanging. Looking around, I saw that
