From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754526AbYERRuG (ORCPT ); Sun, 18 May 2008 13:50:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752603AbYERRty (ORCPT ); Sun, 18 May 2008 13:49:54 -0400 Received: from pentafluge.infradead.org ([213.146.154.40]:52865 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752587AbYERRtx (ORCPT ); Sun, 18 May 2008 13:49:53 -0400 Date: Sun, 18 May 2008 10:47:49 -0700 From: Greg KH To: Andrew Morton Cc: Sitsofe Wheeler , linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org Subject: Re: [BUG] unable to handle kernel paging request in next-20080516 Message-ID: <20080518174749.GA22939@kroah.com> References: <20080518021423.3dcf0ddd.akpm@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080518021423.3dcf0ddd.akpm@linux-foundation.org> User-Agent: Mutt/1.5.16 (2007-06-09) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, May 18, 2008 at 02:14:23AM -0700, Andrew Morton wrote: > > (cc's added) > > On Sat, 17 May 2008 12:50:24 +0000 (UTC) Sitsofe Wheeler wrote: > > > Sometimes when booting next-20080516 on Ubuntu Gutsy an oops then a panic > > will occur. At first I thought it might be provoked by vga=0x164 but this > > does not appear to be the case and the issue is seemingly random. I've > > hand transcribed the oops so there may be errors in it but hopefully it > > will still help: > > > > BUG: unable to handle kernel paging request at e6f17fac > > IP: [] scsi_bus_uevent+0x1/0x17 > > *pde = 2714b163 *pte = 26f17160 > > Oops: 0000 [#1] DEBUG_PAGEALLOC > > last sysfs file: > > > > Pid: 1, comm: swapper Not tainted (2.6.26-rc2-next-20080516skw #30) > > EIP: 0060:[] EFLAGS: 00010282 CPU: 0 > > EIP is at scsi_bus_uevent+0x1/0x17 > > EAX: e6f18014 EBX: e6f18014 ECX: c02604d5 EDX: e7173000 > > ESI: e7173000 EDI: e7173000 EBP: e7851ca0 ESP: e7851c90 > > DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 > > Process swapper (pid: 1, ti=e7850000 task=e7848000 task.ti=e7850000) > > Stack: e7851ca0 c0237f3a c0237eac 00000000 e7851ce4 c01da36d 00000000 e6f180fc > > e7835000 c03ebf42 e7163240 c03af631 c040b050 c040b598 00000000 e6f18014 > > 00000000 e7851cdc 00000000 e6f18014 00000000 e7851cec c01da52a e7851d2c > > Call Trace: > > [] ? dev_uevent+0x8e/0xca > > [] ? dev_uevent+0x0/0xca > > [] ? kobject_uevent_env+0x14c/0x2ff > > [] ? kobject_uevent_env+0xa/0xc > > [] ? device_add+0x2bf/0x3f0 > > [] ? mutex_unlock+0x8/0xa > > [] ? scsi_sysfs_add_sdev+0x39/0x1d3 > > [] ? scsi_probe_and_add_lun+0x714/0x08 > > [] ? __scsi_add_device+0x85/0xab > > [] ? ata_scsi_scan_host+0x7f/0x15e > > [] ? ata_host_register+0x1c8/0x1e5 > > [] ? ata_pci_sff_activate_host+0x179/0x19f > > [] ? ata_sff_interupt+0x0/0x1d7 > > [] ? ata_pci_sff_init_one+0x97/0xe1 > > [] ? via_init_one+0x1da/0x1e3 > > [] ? pci_device_probe+0x39/0x59 > > [] ? driver_probe_device+0x9f/0x119 > > [] ? __driver_attach+0x3d/0x5f > > [] ? bus_for_each_dev+0x3e/0x60 > > [] ? driver_attach+0x14/0x16 > > [] ? __driver_attach+0x0/0x5f > > [] ? bus_add_driver+0x99/0x1a0 > > [] ? driver_register+0x71/0xcd > > [] ? __pci_register_driver+0x53/0x81 > > [] ? kernel_init+0x0/0xc4 > > [] ? via_init+0x14/0x16 > > [] ? trace_softirqs_on+0x78/0x7e > > [] ? trace_hardirqs_on_thunk+0xc/0x10 > > [] ? restore_nocheck_notrace+0x0/0xe > > [] ? kernel_init+0x0/0x1c4 > > [] ? kernel_init+0x0/0x1c4 > > [] ? kernel_thread_helper+0x7/0x10 > > ======================= > > > > I thought we'd already fixed this? I have a patch for it, posted to lkml on Friday (or was it thursday...) Then on Friday I went and audited all users of device_create and found 5 other places where this same problem will occur (or something almost like it) and fixed them up and Cc:ed the subsystem maintainers that were affected. I wanted a round of tests in linux-next to happen before sending them all to Linus. I'll do that on Monday as they missed the last linux-next release. If you want to test them out yourself, the patches are this one first: http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-01-driver-core.current/driver-core-add-device_create_vargs-and-device_create_drvdata.patch and then add any one of the rest of the patches in the directory at: http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-01-driver-core.current/ depending on the subsystem you are having problems with. There are 12 different ones in there. hope this helps, greg k-h