From: Georg Gast <georg@schorsch-tech.de>
To: linux-rt-users@vger.kernel.org
Subject: Searching a Bug on Raspberry Pi
Date: Sat, 29 Jun 2013 22:14:45 +0200 [thread overview]
Message-ID: <51CF4035.8090100@schorsch-tech.de> (raw)
Hi there!
Currently i try to locate a bug in drivers/mmc/host/sdhci.c on
RaspberryPi. I know it is not the mainline kernel...
Currently i use Kernel 3.8.13 and RT Patch 3.8.13-rt12 on the kernel
found at git://github.com/raspberrypi/linux.git on branch rpi-3.8.y.
The bug shows up at booting and after 3 seconds of booting as it wants
to mount the rootfs in a deadlock. as i compiled sdhci_bcm2708 as a
module i can boot the kernel and system as i pushed the system to a usb
stick. As far as good.
Now i try to find the bug, if the rootfs is on the sdcard. I narrowd the
deadlock down to the following lines:
void sdhci_spin_lock_irqsave(struct sdhci_host *host,unsigned long *flags)
{
return;
#ifdef CONFIG_PREEMPT
if(enable_llm)
{
while(sdhci_locked)
{
preempt_schedule();
}
spin_lock_irqsave(&host->lock,*flags);
disable_irq(host->irq);
if(host->second_irq)
disable_irq(host->second_irq);
local_irq_enable();
}
else
#endif
spin_lock_irqsave(&host->lock,*flags);
}
void sdhci_spin_unlock_irqrestore(struct sdhci_host *host,unsigned long
flags)
{
return;
#ifdef CONFIG_PREEMPT
if(enable_llm)
{
local_irq_disable();
if(host->second_irq)
enable_irq(host->second_irq);
enable_irq(host->irq);
}
#endif
spin_unlock_irqrestore(&host->lock,flags);
}
in drivers/mmc/host/sdhci.c . The both return statements are added by
me. Now i can boot the RT Preempt kernel but it is for sure not the
right fix.
My problem is, that i dont know how those both functions should work
with the rt preempt patch.
What can you suggest me to fix that deadlock? I already bought the book
"Linux Kernel Development" but i dont know how the kernel works exaktly
with the PREEMPT patch. Can you point me to a site which shows how
RTPREEMPT works in the irqsave/restore functions or can you please
describe it to me?
Thank you
Georg
next reply other threads:[~2013-06-29 20:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-29 20:14 Georg Gast [this message]
[not found] ` <CAFSh4Uz7B8L5Y0nsp1bW4pgPkyqHtXDSM0R-PiRLZQfd+URFYw@mail.gmail.com>
2013-06-30 4:42 ` Searching a Bug on Raspberry Pi Georg Gast
2013-07-04 10:45 ` Jeremy Jongepier
-- strict thread matches above, loose matches on Subject: below --
2013-06-29 18:28 Georg Gast
2013-07-04 12:14 ` Kirill Tkhai
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=51CF4035.8090100@schorsch-tech.de \
--to=georg@schorsch-tech.de \
--cc=linux-rt-users@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.