From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932567AbXCJJVl (ORCPT ); Sat, 10 Mar 2007 04:21:41 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S933426AbXCJJVl (ORCPT ); Sat, 10 Mar 2007 04:21:41 -0500 Received: from mail.kroah.org ([69.55.234.183]:55262 "EHLO perch.kroah.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932567AbXCJJVj (ORCPT ); Sat, 10 Mar 2007 04:21:39 -0500 Date: Sat, 10 Mar 2007 01:18:20 -0800 From: Greg KH To: Andrew Morton , jkosina@suse.cz Cc: Mariusz Kozlowski , linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net Subject: Re: 2.6.21-rc3-mm1 Message-ID: <20070310091820.GB30495@kroah.com> References: <20070307201839.6f45735b.akpm@linux-foundation.org> <200703100933.35743.m.kozlowski@tuxland.pl> <20070310005828.0ab608b1.akpm@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070310005828.0ab608b1.akpm@linux-foundation.org> User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Mar 10, 2007 at 12:58:28AM -0800, Andrew Morton wrote: > > On Sat, 10 Mar 2007 09:33:35 +0100 Mariusz Kozlowski wrote: > > Hello, > > > > > - The wireless changes in here need a lot of testers, please. It is major > > > rework. > > > > Works for me ... so far ;-) Anyway to the point: > > > > When moving my laptop I reattached the usb mouse. Then I found this in syslog: > > > > usb 2-1: new low speed USB device using uhci_hcd and address 3 > > usb 2-1: new device found, idVendor=046d, idProduct=c00e > > usb 2-1: new device strings: Mfr=1, Product=2, SerialNumber=0 > > usb 2-1: Product: USB-PS/2 Optical Mouse > > usb 2-1: Manufacturer: Logitech > > usb 2-1: configuration #1 chosen from 1 choice > > khubd: page allocation failure. order:5, mode:0xd0 > > [] show_trace_log_lvl+0x1a/0x30 > > [] show_trace+0x12/0x14 > > [] dump_stack+0x16/0x18 > > [] __alloc_pages+0x2e4/0x303 > > [] cache_alloc_refill+0x2e4/0x516 > > [] kmem_cache_zalloc+0x78/0x7c > > [] hid_parse_report+0xce/0x26b > > [] hid_probe+0x264/0xdba > > [] usb_probe_interface+0x5a/0x89 > > [] driver_probe_device+0x86/0x178 > > [] __device_attach+0x8/0xa > > [] bus_for_each_drv+0x4a/0x68 > > [] device_attach+0x8b/0xd2 > > [] bus_attach_device+0x40/0x84 > > [] device_add+0x5d0/0x6c8 > > [] usb_set_configuration+0x2d6/0x4c6 > > [] generic_probe+0x15c/0x251 > > [] usb_probe_device+0x36/0x3c > > [] driver_probe_device+0x86/0x178 > > [] __device_attach+0x8/0xa > > [] bus_for_each_drv+0x4a/0x68 > > [] device_attach+0x8b/0xd2 > > [] bus_attach_device+0x40/0x84 > > [] device_add+0x5d0/0x6c8 > > [] usb_new_device+0x128/0x196 > > [] hub_thread+0x28a/0xb4a > > [] kthread+0xa2/0xc9 > > [] kernel_thread_helper+0x7/0x18 > > ======================= > > hid_parse_report() is doing kmalloc(128k kbytes). We canot sanely support > that and the code shold be rewritten to not do that. A simple though > somewhat lame fix would be to switch to vmalloc(). > > It's been this way for some time, so it's odd that the failures have just > popped up now. Jiri is the person to ask about this now. Jiri, any thoughts about this? thanks, greg k-h