From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751284AbWC1TcB (ORCPT ); Tue, 28 Mar 2006 14:32:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751287AbWC1TcA (ORCPT ); Tue, 28 Mar 2006 14:32:00 -0500 Received: from smtp.osdl.org ([65.172.181.4]:64641 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S1751284AbWC1TcA (ORCPT ); Tue, 28 Mar 2006 14:32:00 -0500 Date: Tue, 28 Mar 2006 11:31:50 -0800 From: Andrew Morton To: "Don Dupuis" Cc: linux-kernel@vger.kernel.org Subject: Re: Oops at __bio_clone with 2.6.16-rc6 anyone?????? Message-Id: <20060328113150.0acf2b60.akpm@osdl.org> In-Reply-To: <632b79000603280735w1908684djab2798c3f35cfebb@mail.gmail.com> References: <632b79000603271917h4104049dh9b6b8251feac0437@mail.gmail.com> <20060327200134.7369c7f8.akpm@osdl.org> <632b79000603280735w1908684djab2798c3f35cfebb@mail.gmail.com> X-Mailer: Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org "Don Dupuis" wrote: > > Yes it does also happen on 2.6.16 > (please don't top-post). > > On 3/27/06, Andrew Morton wrote: > > "Don Dupuis" wrote: > > > > > > I will get this oops during reboots. It doesn't happen everytime, but > > > It happens on this system at least 1 to 2 out of 10 reboots. The > > > machine is a Dell Powervault 745n. Here is the oops output: > > > > > > Mar 20 22:27:49 (none) kernel: EXT3-fs: mounted filesystem with > > > journal data mode. > > > Mar 20 22:27:49 (none) kernel: Unable to handle kernel paging request > > > at virtual address f8000000 > > > Mar 20 22:27:49 (none) kernel: printing eip: > > > Mar 20 22:27:49 (none) kernel: c0156db1 > > > Mar 20 22:27:49 (none) kernel: *pde = 00000000 > > > Mar 20 22:27:49 (none) kernel: Oops: 0000 [#1] > > > Mar 20 22:27:49 (none) kernel: SMP > > > Mar 20 22:27:49 (none) kernel: Modules linked in: > > > Mar 20 22:27:49 (none) kernel: CPU: 0 > > > Mar 20 22:27:50 (none) kernel: EIP: 0060:[] Not tainted VLI > > > Mar 20 22:27:50 (none) kernel: EFLAGS: 00010206 (2.6.16-rc6 #3) > > > Mar 20 22:27:50 (none) kernel: EIP is at __bio_clone+0x29/0x9b > > > Mar 20 22:27:50 (none) kernel: eax: 00000300 ebx: f68f3700 ecx: > > > 00000002 edx: f7fffc80 > > > Mar 20 22:27:50 (none) kernel: esi: f8000000 edi: f7f3d378 ebp: > > > f7c44b98 esp: f7c44b84 > > > Mar 20 22:27:50 (none) kernel: ds: 007b es: 007b ss: 0068 > > > Mar 20 22:27:50 (none) kernel: Process ldconfig (pid: 581, > > > threadinfo=f7c44000 task=f7db9070) > > > Mar 20 22:27:50 (none) kernel: Stack: <0>f7d3b458 f68f3700 f68f3700 > > > f7fffc80 f65b4640 f7c44ba8 c0156e4e f7d4c664 > > > Mar 20 22:27:50 (none) kernel: 00000010 f7c44bf4 c02c8346 > > > 00000080 00000000 00000e00 c0154b1b 00000000 > > > Mar 20 22:27:50 (none) kernel: 0000007f 00000080 f7fffc80 > > > f7d4a740 f7d44400 f7fffc80 f7d3b458 c01579c3 > > > Mar 20 22:27:50 (none) kernel: Call Trace: > > > Mar 20 22:27:50 (none) kernel: [] show_stack_log_lvl+0xa8/0xb0 > > > Mar 20 22:27:50 (none) kernel: [] show_registers+0x109/0x171 > > > Mar 20 22:27:50 (none) kernel: [] die+0xfb/0x16f > > > Mar 20 22:27:50 (none) kernel: [] do_page_fault+0x359/0x48b > > > Mar 20 22:27:50 (none) kernel: [] error_code+0x4f/0x54 > > > Mar 20 22:27:50 (none) kernel: [] bio_clone+0x2b/0x31 > > > Mar 20 22:27:50 (none) kernel: [] make_request+0x208/0x3d4 > > > Mar 20 22:27:50 (none) kernel: [] make_request+0xd3/0x3d4 > > > Mar 20 22:27:50 (none) kernel: [] generic_make_request+0xf5/0x105 > > > Mar 20 22:27:50 (none) kernel: [] submit_bio+0xa1/0xa9 > > > Mar 20 22:27:50 (none) kernel: [] mpage_bio_submit+0x1c/0x21 > > > Mar 20 22:27:50 (none) kernel: [] do_mpage_readpage+0x30b/0x44d > > > Mar 20 22:27:50 (none) kernel: [] mpage_readpages+0x8d/0xf1 > > > Mar 20 22:27:50 (none) kernel: [] ext3_readpages+0x14/0x16 > > > Mar 20 22:27:50 (none) kernel: [] read_pages+0x26/0xc6 Jens points out that the "dm: bio split bvec fix" patch which went into 2.6.16.1 might fix this. Can you try it please?