From: Steven Cole <elenstev@mesatop.com>
To: Thomas Molina <tmolina@cox.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.39 Oops on boot (device_attach+0x3a)
Date: 30 Sep 2002 21:38:33 -0600 [thread overview]
Message-ID: <1033443514.3100.24.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0209302147380.961-100000@dad.molina>
On Mon, 2002-09-30 at 20:50, Thomas Molina wrote:
> On 30 Sep 2002, Steven Cole wrote:
>
> > I tried to boot 2.5.39 on my home machine and got the
> > following oops on boot with CONFIG_KALLSYMS=y (thanks Ingo!).
> >
> > *pde = 00000000
> > Oops: 0002
> >
> > CPU: 0
> > EIP: 0060:[<c01a7979>] Not tainted
> > EFLAGS: 00010286
> > EIP is at attach+0x1d/0x30
> > eax: c0276724 ebx: 00000000 ecx: c40c8060 edx: c40c8078
> > esi: c0276700 edi: 00000000 ebp: 00000000 esp: c40ddf94
> > ds: 0068 es: 0068 ss: 0068
> > Process swapper (pid: 1, threadinfo=c40dc000 task=c40da040)
> > Stack: 00000000 c01a7a5a c40c8060 c40c8060 c01a7c20 c40c8060 c40c8060 c40c8060
> > c40d7720 c028b879 c40c8060 00000001 c02b9bf4 00000000 00000000 00000000
> > c027e6f2 c0105030 c010504c c0105030 00000000 00000000 00000000 c0105495
> > Call Trace:
> > [<c01a7a5a>] device_attach+0x3a/0x40
> > [<c01a7c20>] device_register+0xd0/0x120
> > [<c0105030>] init+0x0/0x160
> > [<c010504c>] init+0x1c/0x160
> > [<c0105030>] init+0x0/0x160
> > [<c0105495>] kernel_thread_helper+0x5/0x10
> >
>
> I believe the oops on boot people have been seeing in 2.5.39 may be
> related to problems inserting ide-scsi modules (sr_mod, mod_scsi,
> ide-scsi). Since I have to get up early tomorrow I'm going to beg off for
> tonight, but I can reliably produce the above oops. I'll provide full
> data and explanations when I'm not so tired.
>
It's good that the above oops can be reproduced, so here is some more
info on my setup:
[steven@localhost linux-2.5.39-linus]$ grep "=m" .config
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_PC_CML1=m
CONFIG_PRINTER=m
CONFIG_AUTOFS_FS=m
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_NLS_ISO8859_1=m
[steven@localhost linux-2.5.39-linus]$ grep SCSI .config
# SCSI device support
# CONFIG_SCSI is not set
# Old non-SCSI/ATAPI CD-ROM drives
# CONFIG_CD_NO_IDESCSI is not set
[steven@localhost linux-2.5.39-linus]$ find . -name Makefile | xargs grep sr_mod
./drivers/scsi/Makefile:obj-$(CONFIG_BLK_DEV_SR) += sr_mod.o
./drivers/scsi/Makefile:sr_mod-objs := sr.o sr_ioctl.o sr_vendor.o
[steven@localhost linux-2.5.39-linus]$ grep BLK_DEV_SR .config
[steven@localhost linux-2.5.39-linus]$
So, I'm not sure that a scsi-related module is the cause here.
Cheers,
Steven
next prev parent reply other threads:[~2002-10-01 3:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 1:13 2.5.39 Oops on boot (device_attach+0x3a) Steven Cole
2002-10-01 2:50 ` Thomas Molina
2002-10-01 3:38 ` Steven Cole [this message]
2002-10-01 8:10 ` Thomas Molina
2002-10-01 5:39 ` Greg KH
2002-10-01 8:15 ` Thomas Molina
2002-10-01 14:24 ` Steven Cole
2002-10-01 17:06 ` Steven Cole
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=1033443514.3100.24.camel@localhost.localdomain \
--to=elenstev@mesatop.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tmolina@cox.net \
/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).