From: Pavel Machek <pavel@ucw.cz>
To: drzeus-mmc@drzeus.cx, kernel list <linux-kernel@vger.kernel.org>
Subject: 2.6.21-rc4: mmc fails to work, then oopses
Date: Thu, 22 Mar 2007 12:37:42 +0100 [thread overview]
Message-ID: <20070322113742.GA7198@elf.ucw.cz> (raw)
[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]
Hi!
(Machine was suspended/resumed before this).
mount /dev/mmc1 /mnt
Buffer I/O error on device mmcblk0p1, logical block 1
BUG: unable to handle kernel NULL pointer dereference at virtual
address 00000024
printing eip:
c04cb2ec
*pde = 00000000
Oops: 0000 [#1]
SMP
Modules linked in:
CPU: 0
EIP: 0060:[<c04cb2ec>] Not tainted VLI
EFLAGS: 00010097 (2.6.21-rc4 #413)
EIP is at mmc_prep_request+0x2c/0x50
eax: 00000000 ebx: ecad6134 ecx: 00000000 edx: ecad6134
esi: ecad6134 edi: f797369c ebp: c04cb490 esp: ecb89f98
ds: 007b es: 007b fs: 00d8 gs: 0000 ss: 0068
Process mmcqd (pid: 7143, ti=ecb88000 task=c230c570 task.ti=ecb88000)
Stack: f7bd5470 c02450f8 00000003 00000000 00000000 ecad6134 f797369c
f7bd5470
f797369c c04cb547 fffffffc f7fc1d08 c013cfbc ffffffff ffffffff
c013ced0
00000000 00000000 00000000 c0104beb f7fc1d00 00000000 00000000
00000000
Call Trace:
[<c02450f8>] elv_next_request+0x88/0x140
[<c04cb547>] mmc_queue_thread+0xb7/0xe0
[<c013cfbc>] kthread+0xec/0xf0
[<c013ced0>] kthread+0x0/0xf0
[<c0104beb>] kernel_thread_helper+0x7/0x1c
=======================
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: delme.gz --]
[-- Type: application/octet-stream, Size: 22688 bytes --]
next reply other threads:[~2007-03-22 11:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 11:37 Pavel Machek [this message]
2007-03-22 12:04 ` 2.6.21-rc4: mmc fails to work, then oopses Pierre Ossman
2007-03-29 21:46 ` Pavel Machek
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=20070322113742.GA7198@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=drzeus-mmc@drzeus.cx \
--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