linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: andrei@arhont.com
Cc: linux-kernel@vger.kernel.org, dst@bostream.nu
Subject: Re: amd64 2.6.11 oops on modprobe
Date: Sun, 06 Mar 2005 21:01:53 -0800	[thread overview]
Message-ID: <422BE041.3070103@osdl.org> (raw)
In-Reply-To: <1110115990.5611.2.camel@whale.core.arhont.com>

Andrei Mikhailovsky wrote:
> Hi Randy,
> 
> Done the kstack=32, here is the output:
> 
> cat /proc/cmdline 
> root=/dev/hda2 ro kstack=32 console=tty0
> 
> P.S. Yeah, this oops is repeatable; hapens everytime

I have one other request.  Load each (related) module one at a time,
to make sure that there is no module racing going on here.

Something like (but I'm not sure about the order of these  modprobes):

echo /bin/true > /proc/sys/kernel/hotplug

modprobe zr36067
modprobe videocodec
modprobe zr36060
modprobe adv7175
modprobe saa7110

> Output-----
> 
> Unable to handle kernel paging request at ffffffff880db000 RIP: 
> <ffffffff880d909f>{:saa7110:saa7110_write_block+127}
> PGD 103027 PUD 105027 PMD 3de65067 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: 3213, comm: modprobe Not tainted 2.6.11-amd64
> RIP: 0010:[<ffffffff880d909f>]
> <ffffffff880d909f>{:saa7110:saa7110_write_block+127}
> RSP: 0018:ffff81003e9a3b78  EFLAGS: 00010287
> RAX: 000000000000139f RBX: 00000000ffffec36 RCX: 000000000000002a
> RDX: 000000000000009f RSI: 0000000000000001 RDI: ffffffff880bf838
> RBP: 000000000000139f R08: 0000000000000000 R09: ffff8100067713a8
> R10: 0000000000000001 R11: ffffffff802f75d0 R12: ffffffff880db000
> R13: ffff810037277400 R14: ffff81003e4efe00 R15: 0000000000000001
> FS:  00002aaaaaac5520(0000) GS:ffffffff80500180(0000)
> knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: ffffffff880db000 CR3: 000000003fa2b000 CR4: 00000000000006e0
> Process modprobe (pid: 3213, threadinfo ffff81003e9a2000, task
> ffff81003e8096c0)
> Stack: 0000000000000076 0000000000000000 0000000000000000
> 0000000000000000 
>        0000000000000000 ffffffffffff0000 ffffffffffffffff
> ffff81003e4efe28 
>        ffff002a0001004e ffff81003e9a3b78 ffff81003e4efe28
> ffff810037277400 
>        ffff81003e4efe00 0000000000000000 ffff81003e4eff70
> ffffffff880bf808 
>        ffffffff880d9930 ffffffff880d9ab4 0000000000000000
> 0000000000000000 
>        000000000000004e 0000000000000000 000000000000004e
> 0000000000000003 
>        ffffffff880dab60 ffffffff802f6812 0000000000000000
> ffffffff880dab50 
>        ffffffff880bf808 ffffffff880bf9a8 ffffffff880bf908
> ffffffff80474f90 
> Call Trace:<ffffffff880d9930>{:saa7110:saa7110_detect_client+0} 
>        <ffffffff880d9ab4>{:saa7110:saa7110_detect_client+388} 
>        <ffffffff802f6812>{i2c_probe+642}
> <ffffffff802f4c24>{i2c_add_adapter+468} 
>        <ffffffff802f7928>{i2c_bit_add_bus+840}
> <ffffffff880d7600>{:zr36067:init_dc10_cards+1536} 
>        <ffffffff801468e1>{sys_init_module+5857}
> <ffffffff80174de7>{do_lookup+55} 
>        <ffffffff8021f440>{prio_tree_insert+48}
> <ffffffff880d7000>{:zr36067:init_dc10_cards+0} 
>        <ffffffff80113fff>{sys_mmap+191} <ffffffff8010e1fa>{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 <ffffffff880d909f>{:saa7110:saa7110_write_block+127} RSP
> <ffff81003e9a3b78>
> CR2: ffffffff880db000
> 
> ---Output end---
> 
> If you need any further info, please let me know
> 
> --
> Andrei
> 
> On Sat, 2005-03-05 at 16:53 -0800, Randy.Dunlap wrote:
> 
>>Andrei Mikhailovsky wrote:
>>
>>>I get the oops during the boot up process. This did not happen in
>>>2.6.10/2.6.9.
>>>
>>>Here is the output from dmesg:
>>>
>>>Unable to handle kernel paging request at ffffffff880db000 RIP: 
>>><ffffffff880d909f>{: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:[<ffffffff880d909f>]
>>><ffffffff880d909f>{: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:<ffffffff880d9930>{:saa7110:saa7110_detect_client+0} 
>>>       <ffffffff880d9ab4>{:saa7110:saa7110_detect_client+388} 
>>>       <ffffffff802f6812>{i2c_probe+642}
>>><ffffffff802f4c24>{i2c_add_adapter+468} 
>>>       <ffffffff802f7928>{i2c_bit_add_bus+840}
>>><ffffffff880d7600>{:zr36067:init_dc10_cards+1536} 
>>>       <ffffffff801468e1>{sys_init_module+5857}
>>><ffffffff80174de7>{do_lookup+55} 
>>>       <ffffffff8021f440>{prio_tree_insert+48}
>>><ffffffff880d7000>{:zr36067:init_dc10_cards+0} 
>>>       <ffffffff80113fff>{sys_mmap+191} <ffffffff8010e1fa>{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 <ffffffff880d909f>{:saa7110:saa7110_write_block+127} RSP
>>><ffff81003f6c5b78>
>>>CR2: ffffffff880db000


-- 
~Randy

  parent reply	other threads:[~2005-03-07  5:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-05 12:11 amd64 2.6.11 oops on modprobe Andrei Mikhailovsky
2005-03-06  0:53 ` Randy.Dunlap
2005-03-06 13:33   ` Andrei Mikhailovsky
2005-03-07  3:52     ` Randy.Dunlap
2005-03-07  5:01     ` Randy.Dunlap [this message]
2005-03-07 21:47     ` Randy.Dunlap
2005-03-08 19:15       ` Jean Delvare
2005-03-08 19:25         ` [PATCH 2.6] Fix i2c messsage flags in video drivers Jean Delvare
2005-03-09 18:40           ` Chris Wright
2005-03-09 21:55             ` Jean Delvare
2005-03-09 22:40               ` Ronald S. Bultje
2005-03-10 10:56                 ` Jean Delvare
2005-03-10  0:47                   ` Ronald S. Bultje
2005-03-10 11:50                     ` Jean Delvare
2005-03-10  1:33                       ` Ronald S. Bultje
2005-03-09 23:28               ` Chris Wright
2005-03-21 22:47 ` amd64 2.6.11 oops on modprobe Andrew Morton
2005-05-25 22:24 ` Andrew Morton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=422BE041.3070103@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=andrei@arhont.com \
    --cc=dst@bostream.nu \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).