Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261578AbVEYWYk (ORCPT ); Wed, 25 May 2005 18:24:40 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261574AbVEYWYk (ORCPT ); Wed, 25 May 2005 18:24:40 -0400 Received: from fire.osdl.org ([65.172.181.4]:9096 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S261554AbVEYWYP (ORCPT ); Wed, 25 May 2005 18:24:15 -0400 Date: Wed, 25 May 2005 15:24:49 -0700 From: Andrew Morton To: andrei@arhont.com Cc: linux-kernel@vger.kernel.org, video4linux-list@redhat.com Subject: Re: amd64 2.6.11 oops on modprobe Message-Id: <20050525152449.16daf241.akpm@osdl.org> In-Reply-To: <1110024688.5494.2.camel@whale.core.arhont.com> References: <1110024688.5494.2.camel@whale.core.arhont.com> X-Mailer: Sylpheed version 1.0.0 (GTK+ 1.2.10; i386-vine-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 Content-Length: 2777 Lines: 70 Andrei Mikhailovsky wrote: > > I get the oops during the boot up process. This did not happen in > 2.6.10/2.6.9. Is this bug still present in 2.6.12-rc5? Thanks. > Here is the output from dmesg: > > Unable to handle kernel paging request at ffffffff880db000 RIP: > {:saa7110:saa7110_write_block+127} > PGD 103027 PUD 105027 PMD 3ee64067 PTE 0 > Oops: 0000 [1] > CPU 0 > Modules linked in: adv7175 saa7110 zr36067 videocodec videodev sata_nv > libata snd_intel8x0 snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm > snd_timer snd snd_page_alloc i2c_nforce2 it87 eeprom i2c_sensor i2c_isa > sk98lin > Pid: 2604, comm: modprobe Not tainted 2.6.11-amd64 > RIP: 0010:[] > {:saa7110:saa7110_write_block+127} > RSP: 0018:ffff81003f6c5b78 EFLAGS: 00010287 > RAX: 000000000000139f RBX: 00000000ffffec36 RCX: 000000000000002a > RDX: 000000000000009f RSI: 0000000000000001 RDI: ffffffff880bf838 > RBP: 000000000000139f R08: 0000000000000000 R09: ffff81003efd63a8 > R10: 0000000000000001 R11: ffffffff802f75d0 R12: ffffffff880db000 > R13: ffff81003f3e0200 R14: ffff81003e0df200 R15: 0000000000000001 > FS: 00002aaaaaac5520(0000) GS:ffffffff80500180(0000) > knlGS:0000000000000000 > CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b > CR2: ffffffff880db000 CR3: 000000003e125000 CR4: 00000000000006e0 > Process modprobe (pid: 2604, threadinfo ffff81003f6c4000, task > ffff81003ed59700) > Stack: 0000000000000076 0000000000000000 0000000000000000 > 0000000000000000 > 0000000000000000 ffffffffffff0000 ffffffffffffffff > ffff81003e0df228 > ffff002a0001004e ffff81003f6c5b78 > Call Trace:{:saa7110:saa7110_detect_client+0} > {:saa7110:saa7110_detect_client+388} > {i2c_probe+642} > {i2c_add_adapter+468} > {i2c_bit_add_bus+840} > {:zr36067:init_dc10_cards+1536} > {sys_init_module+5857} > {do_lookup+55} > {prio_tree_insert+48} > {:zr36067:init_dc10_cards+0} > {sys_mmap+191} {system_call > +126} > > > Code: 41 0f b6 04 24 ff c5 49 ff c4 41 88 44 15 00 88 04 0c 8b 44 > RIP {:saa7110:saa7110_write_block+127} RSP > > CR2: ffffffff880db000 > > If anyone need more debugging info, I am ready to help > > > -- > Andrei Mikhailovsky > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/