Hi. On Tue, 2005-03-01 at 12:10, Robert Hancock wrote: > Bernd Schubert wrote: > Essentially the tg3 Ethernet driver is trying to allocate memory to > store a received packet, and is unable to do so. Since this is done > inside interrupt context, this allocation has to be serviced from > physical memory. Order 1 means it only wanted one page of memory, and
Minor point, I know, but it's 2 pages of memory. If it couldn't get an order zero page, that would be even greater hernia material! Regards, Nigel > since that failed it looks like the system must have been awfully short > on available physical RAM.. it could be some kind of kernel memory leak > or VM issue, though this condition may not be entirely unexpected in > certain cases, like if the system has little physical RAM free at a > certain point and then a flood of network packets arrive. -- Nigel Cunningham Software Engineer, Canberra, Australia http://www.cyclades.com Bus: +61 (2) 6291 9554; Hme: +61 (2) 6292 8028; Mob: +61 (417) 100 574 Maintainer of Suspend2 Kernel Patches http://softwaresuspend.berlios.de - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
