Re: irq flood with mmc boot partitions on s3c2416 with 3.0rc1

["Heiko Stübner" <heiko@sntech.de>]

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

Hi again,

sorry for having taken so long, but university-work called :-)

Am Montag 20 Juni 2011, 21:34:53 schrieb Andrei Warkentin:
> On Sun, Jun 19, 2011 at 9:23 AM, Heiko Stübner <heiko@sntech.de> wrote:
> > Am Samstag 18 Juni 2011, 22:56:11 schrieb Daniel Mack:
> The log you sent out seems a bit short (it's covers < 1s of boot time
> - usb0: no IPv6 routers present is the last line ). Can you send -
> 1) A full log with errors without any of my patches.
> 2) A full log with just the first patch.
> 3) A full log with just the second patch.
I have attached a log with mmc-debugging enabled. 
The relevant parts start around line 2634 ("waiting for /dev to be fully 
populated" - the udev start). The culprit (Hynix-nand) is mmc1.

Switching the patches on and off will have to wait until the weekend. But I can 
say the error (irq message and register dump [and them looping endlessly]) has 
not not changed from before your patches.

I'm curious, is mmc_blk_resume (which is modified by your second patch) called 
at other times than when waking up from system suspend? [i.e. during system 
startup]

> I'm interested in knowing what the pattern of access to boot0 and
> boot1 is that causes these failures - does it only report I/O errors
> for for certain blocks (say, above some number) or for all of them.
it doesn't report io-errors at all. It send endless loops of CMD13 calls with 
the same argument and receives interrupts it does not expect :-)


Thanks again for your time
Heiko

[-- Attachment #2: dmesg-debug_20110629.txt.gz --]
[-- Type: application/x-gzip, Size: 11750 bytes --]