Re: Alloc memory errors....
Derric, > 10:09:29 CRS8ASRM *8 qeth: no memory for packet from hsi1 means, that the network device driver qeth receives an incoming packet. It has to allocate memory for it before the qeth driver can give this packet to the upper layers in the Linux network stack. Since in your case memory allocation has failed, the qeth driver can only drop this packet. If this message is seen quite rarely, it may not hurt since reliable networking protocols can handle this. If it is seen quite often, it indicates a general problem with the size of your virtual memory. Regards, Ursula Braun IBM Germany -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Alloc memory errors....
Tom Shilson wrote: > The 2-order v. 5-order have to do with the amount of memory requested. The > memory manager pools each have a single request size for efficiency. I > have forgotten the relationship between order number and amount of memory > requested. Very good explanation, Tom. The size = 2 ^ order * PAGE: Order 0 = 2^0 = 1 Page = 4K Order 1 = 2^1 = 2 Pages = 8K Order 2 = 2^2 = 4 Pages = 16K ... You usually only see this message if the requester of the memory sits in kernel space. Note that some kernel components continue normal operation even if their memory allocation fails. Our dasd device driver is a very good example for that. This message therefore does not always indicate an error. -- Carsten Otte has stopped smoking: Ich habe in 10 Monate, 5 Tage und 14 Stunden schon 1.486,05 Euro gespart anstatt 6.191,90 Zigaretten zu kaufen. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Alloc memory errors....
Linux on 390 Port wrote on 03/29/2007 03:31:32 PM: > To clarify when we start seeing the slow downs I have been getting some > TCP dumps to analyze. > That's why we see the interface going into promiscuous mode. If you don't need promiscuous mode you can specify with a tcpdump option to not turn it on. -p, perhaps? If the interface is already in promiscuous mode, tcpdump will *not* turn it off. tom -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Alloc memory errors....
The 2-order v. 5-order have to do with the amount of memory requested. The memory manager pools each have a single request size for efficiency. I have forgotten the relationship between order number and amount of memory requested. Tom Shilson Powered by Penguins Unix Team / IT Server Services Tel: 651-733-7591 tshilson at mmm dot com Fax: 651-736-7689 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Alloc memory errors....
To clarify when we start seeing the slow downs I have been getting some TCP dumps to analyze. That's why we see the interface going into promiscuous mode. I have yet to identify any errors in the dumps however. But our application starts spitting out Java 330 errors and costumers start reporting corrupted data transfers. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Thursday, March 29, 2007 3:20 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Alloc memory errors >>> On Thu, Mar 29, 2007 at 4:08 PM, in message <[EMAIL PROTECTED]>, "Goodwin, Derric" <[EMAIL PROTECTED]> wrote: > I'm seeing the following errors in syslog for interface hsi1: > > > > 10:05:36 CRS8ASRM *8 device hsi1 entered promiscuous mode > > 10:05:36 CRS8ASRM *8 Mar 23 10:05:14 crs8asrm kernel: device hsi1 > entered promis This message typically means that someone (with root access) is doing network sniffing from inside your system. It could definitely have an impact on your network application's performance. You should find out who's doing that, and why, regardless of the follow-on errors. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Alloc memory errors....
>>> On Thu, Mar 29, 2007 at 4:08 PM, in message <[EMAIL PROTECTED]>, "Goodwin, Derric" <[EMAIL PROTECTED]> wrote: > I'm seeing the following errors in syslog for interface hsi1: > > > > 10:05:36 CRS8ASRM *8 device hsi1 entered promiscuous mode > > 10:05:36 CRS8ASRM *8 Mar 23 10:05:14 crs8asrm kernel: device hsi1 > entered promis This message typically means that someone (with root access) is doing network sniffing from inside your system. It could definitely have an impact on your network application's performance. You should find out who's doing that, and why, regardless of the follow-on errors. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Alloc memory errors....
A memory allocation failure. You may need a larger virtual machine. Goodwin, Derric wrote: I'm seeing the following errors in syslog for interface hsi1: 10:05:36 CRS8ASRM *8 device hsi1 entered promiscuous mode 10:05:36 CRS8ASRM *8 Mar 23 10:05:14 crs8asrm kernel: device hsi1 entered promis 10:09:29 CRS8ASRM *8 __alloc_pages: 2-order allocation failed (gfp=0x20/0) 10:09:29 CRS8ASRM *8 NET: 9 messages suppressed. 10:09:29 CRS8ASRM *8 qeth: no memory for packet from hsi1 10:09:29 CRS8ASRM *8 __alloc_pages: 2-order allocation failed (gfp=0x20/0) The _alloc_pages: 2-order error I have seen on other systems with the 2 ranging from 0 to 5 or higher numbers. On this system it's always 2... This may be a dumb question but does anyone know what the numbers represent? What's the difference between a 2 and a 5 for instance. When we start logging these errors our application performance takes a dive. Thanks for any insight. --- Derric Goodwin Distributed Systems Integration Acxiom/TransUnion. Chicago, Il. Ph:(312)985-3312 email: [EMAIL PROTECTED] -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com Catch the WAVV! http://www.wavv.org WAVV 2007 - Green Bay, WI - May 18-22, 2007 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Alloc memory errors....
I'm seeing the following errors in syslog for interface hsi1: 10:05:36 CRS8ASRM *8 device hsi1 entered promiscuous mode 10:05:36 CRS8ASRM *8 Mar 23 10:05:14 crs8asrm kernel: device hsi1 entered promis 10:09:29 CRS8ASRM *8 __alloc_pages: 2-order allocation failed (gfp=0x20/0) 10:09:29 CRS8ASRM *8 NET: 9 messages suppressed. 10:09:29 CRS8ASRM *8 qeth: no memory for packet from hsi1 10:09:29 CRS8ASRM *8 __alloc_pages: 2-order allocation failed (gfp=0x20/0) The _alloc_pages: 2-order error I have seen on other systems with the 2 ranging from 0 to 5 or higher numbers. On this system it's always 2... This may be a dumb question but does anyone know what the numbers represent? What's the difference between a 2 and a 5 for instance. When we start logging these errors our application performance takes a dive. Thanks for any insight. --- Derric Goodwin Distributed Systems Integration Acxiom/TransUnion. Chicago, Il. Ph:(312)985-3312 email: [EMAIL PROTECTED] -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
