Re: soreceive: not M_DATA, found 131
From: Jean-Pierre Radley (jpr_at_jpr.com)
Date: 06/04/04
- Next message: Gary L. Burnore: "Re: soreceive: not M_DATA, found 131"
- Previous message: Gary L. Burnore: "soreceive: not M_DATA, found 131"
- In reply to: Gary L. Burnore: "soreceive: not M_DATA, found 131"
- Next in thread: Gary L. Burnore: "Re: soreceive: not M_DATA, found 131"
- Reply: Gary L. Burnore: "Re: soreceive: not M_DATA, found 131"
- Reply: Gary L. Burnore: "Followup: soreceive: not M_DATA, found 131"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 4 Jun 2004 14:37:18 -0400
Gary L. Burnore typed (on Fri, Jun 04, 2004 at 02:13:51PM -0400):
| Just started getting these on console this morning. NOTHING changed on
| this server for years. The closest thing I find in google is a
| conversation JPR had with someone about CPU2. May have been NIC
| related, but the guy didn't say what the result of his testing found.
|
|
| Error from syslog:
|
| Jun 4 13:53:41 dtbsx WARNING: soreceive: unexpected message type
| x00000083
| Jun 4 13:53:42 dtbsx WARNING: soreceive: not M_DATA, found 131
|
|
| Is this likely a dying NIC too?
|
| Everything else works fine in and outbound.
Have you read TA # 125539?
-- JP
- Next message: Gary L. Burnore: "Re: soreceive: not M_DATA, found 131"
- Previous message: Gary L. Burnore: "soreceive: not M_DATA, found 131"
- In reply to: Gary L. Burnore: "soreceive: not M_DATA, found 131"
- Next in thread: Gary L. Burnore: "Re: soreceive: not M_DATA, found 131"
- Reply: Gary L. Burnore: "Re: soreceive: not M_DATA, found 131"
- Reply: Gary L. Burnore: "Followup: soreceive: not M_DATA, found 131"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|