public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helmut Grohne <helmut@subdivi.de>
To: linux-kernel@vger.kernel.org
Subject: PROBLEM: random crashes while loading modules into 2.6.36-rc8
Date: Sun, 17 Oct 2010 21:52:06 +0200	[thread overview]
Message-ID: <20101017195206.GA22229@alf.mars> (raw)

[-- Attachment #1: Type: text/plain, Size: 952 bytes --]

I tried to use vanilla 2.6.36-rc8 and failed. While trying track down
the random oopses, bugs and lockups the problem appeared to get broader
and broader. In fact the best description I can come up with is loading
a module with at least one dependency.

Steps to reproduce:
1) Get 2.6.36-rc8.
2) Use my config (attached).
3) Compile it on amd64. (I used gcc 4:4.4.5-1 from Debian Sid.)
4) Get qemu. (I used 0.12.5+dfsg-2 from Debian Sid.)
5) Create an initramfs that contains the modules and some shell.
6) qemu-system-x86_64 -m 256 -kernel vmlinuz-2.6.36-rc8 -initrd foo.cpio.gz
7) load a module. If it does not crash, try more.

This is also reproducible without qemu for me. The most reliable module
was sky2 (both inside and outside qemu). Also loading ohci_hcd caused a
variety of oopses and bugs on my system. Note that not all modules
caused problems. For instance the dependencies for sky2 (bitrev and
crc32) could be loaded just fine.

Helmut

[-- Attachment #2: config.gz --]
[-- Type: application/octet-stream, Size: 24644 bytes --]

             reply	other threads:[~2010-10-17 19:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-17 19:52 Helmut Grohne [this message]
2010-10-19 16:23 ` "solved" PROBLEM: random crashes while loading modules into 2.6.36-rc8 Helmut Grohne

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=20101017195206.GA22229@alf.mars \
    --to=helmut@subdivi.de \
    --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