Re: Re: SD Driver : FAT: FAT read failed (blocknr 8) in sd card error while removing sd card during writing

Re: Re: SD Driver : FAT: FAT read failed (blocknr 8) in sd card error while removing sd card during writing

[MADHAV SINGHCHAUHAN]

Card removal not detected by driver? 
You should see a line of log if card removal is detected: 
card xxxx removed 

Would you describe how do you detect card removal/insertion on your board? 

Regards, 
-Ethan 

On Thu, Jul 8, 2010 at 6:05 PM, hardik patel <hk5patel@gmail.com> wrote: 
> I have sd card on board ... During recording/writing SD card, remove 
> SD card ... then i am getting endless error in dmesg as below : 
> 
> end_request: I/O error, dev mmcblk0, sector 24 
> FAT: FAT read failed (blocknr 8) 
> mmcblk0: error -110 sending status comand<3>mmcblk0: error -110 
> sending read/write command, response 0x0, card status 0x0 
> Block mmc_blk_issue_rq function call 346 
> end_request: I/O error, dev mmcblk0, sector 4 
> FAT: FAT read failed (blocknr 4) 
> MMC: killing requests for dead queue 
> end_request: I/O error, dev mmcblk0, sector 8 
> FAT: FAT read failed (blocknr 8) 
> FAT: FAT read failed (blocknr 4) 
> FAT: FAT read failed (blocknr 8) 
> FAT: FAT read failed (blocknr 4) 
> FAT: FAT read failed (blocknr 8) 
> FAT: FAT read failed (blocknr 4) 
> FAT: FAT read failed (blocknr 8) 
> 
> How to stop this message ... what is ideal situation when we remove 
> card while writing ...... can u help me what to do ? 
> 
>>When we insert the card hot plug dameon start sending the request to block layer  and kernel block layer
>>start sending the request to card.But when you remove the card in between request queue is not flushed properly..
>>so you need to flush your request queue at appropriate time.Also please note that even that you flush your request queue
>>at appropriate time some messages will come.
> where is the problem here? sd host controler driver problem or block 
> driver problem or file system problem 
> 
> Note: I have formatted sd card with FAT32 file system . 
> 
> 
> 
> With EXT3 File system : 
> 
> Remove SD card while writing/recording we got error messages like 
> below. but this is not endless. After some time it stops. 
> 
> ============================== 
> ============= 
> end_request: I/O error, dev mmcblk0, sector 156536 
> mmcblk0: error -110 sending status comand<3>mmcblk0: error -110 
> sending read/write command, response 0x0, card status 0x0 
> mmcblk0: error -110 requesting status 
> end_request: I/O error, dev mmcblk0, sector 4736 
> Aborting journal on device mmcblk0p1. 
> ext3_abort called. 
> EXT3-fs error (device mmcblk0p1): ext3_journal_start_sb: Detected 
> aborted journal 
> Remounting filesystem read-only 
> end_request: I/O error, dev mmcblk0, sector 4448 
> journal commit I/O error 
> =========================================== 
> -- 
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in 
> the body of a message to majordomo@vger.kernel.org 
> More majordomo info at ?http://vger.kernel.org/majordomo-info.html 
> 
-- 
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in 
the body of a message to majordomo@vger.kernel.org 
More majordomo info at  http://vger.kernel.org/majordomo-info.html 

 
 
 
 

Re: Re: SD Driver : FAT: FAT read failed (blocknr 8) in sd card error while removing sd card during writing

[hardik patel]

Hi Madhav,

thanks for your interest... I have card detect register so mmc_get_cd
function i can check whether card is inserted or not ... so in sd host
controller driver can detect that properly... but i think block driver
does not detect that .... where i have to flush my request queue... i
have gone through block.c and queue.c file which generate mmc_block.ko
file but not sure where to modify... can any one guide me more


On Thu, Jul 8, 2010 at 6:35 PM, MADHAV SINGHCHAUHAN
<singh.madhav@samsung.com> wrote:
> Card removal not detected by driver?
> You should see a line of log if card removal is detected:
> card xxxx removed
>
> Would you describe how do you detect card removal/insertion on your board?
>
> Regards,
> -Ethan
>
> On Thu, Jul 8, 2010 at 6:05 PM, hardik patel <hk5patel@gmail.com> wrote:
>> I have sd card on board ... During recording/writing SD card, remove
>> SD card ... then i am getting endless error in dmesg as below :
>>
>> end_request: I/O error, dev mmcblk0, sector 24
>> FAT: FAT read failed (blocknr 8)
>> mmcblk0: error -110 sending status comand<3>mmcblk0: error -110
>> sending read/write command, response 0x0, card status 0x0
>> Block mmc_blk_issue_rq function call 346
>> end_request: I/O error, dev mmcblk0, sector 4
>> FAT: FAT read failed (blocknr 4)
>> MMC: killing requests for dead queue
>> end_request: I/O error, dev mmcblk0, sector 8
>> FAT: FAT read failed (blocknr 8)
>> FAT: FAT read failed (blocknr 4)
>> FAT: FAT read failed (blocknr 8)
>> FAT: FAT read failed (blocknr 4)
>> FAT: FAT read failed (blocknr 8)
>> FAT: FAT read failed (blocknr 4)
>> FAT: FAT read failed (blocknr 8)
>>
>> How to stop this message ... what is ideal situation when we remove
>> card while writing ...... can u help me what to do ?
>>
>>>When we insert the card hot plug dameon start sending the request to block layer  and kernel block layer
>>>start sending the request to card.But when you remove the card in between request queue is not flushed properly..
>>>so you need to flush your request queue at appropriate time.Also please note that even that you flush your request queue
>>>at appropriate time some messages will come.
>> where is the problem here? sd host controler driver problem or block
>> driver problem or file system problem
>>
>> Note: I have formatted sd card with FAT32 file system .
>>
>>
>>
>> With EXT3 File system :
>>
>> Remove SD card while writing/recording we got error messages like
>> below. but this is not endless. After some time it stops.
>>
>> ==============================
>> =============
>> end_request: I/O error, dev mmcblk0, sector 156536
>> mmcblk0: error -110 sending status comand<3>mmcblk0: error -110
>> sending read/write command, response 0x0, card status 0x0
>> mmcblk0: error -110 requesting status
>> end_request: I/O error, dev mmcblk0, sector 4736
>> Aborting journal on device mmcblk0p1.
>> ext3_abort called.
>> EXT3-fs error (device mmcblk0p1): ext3_journal_start_sb: Detected
>> aborted journal
>> Remounting filesystem read-only
>> end_request: I/O error, dev mmcblk0, sector 4448
>> journal commit I/O error
>> ===========================================
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at ?http://vger.kernel.org/majordomo-info.html
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>
>
>
>
>
>
>



-- 
Regards,
Hardik

"If you are doing what you have always been doing then expect what you
have always been getting."

Re: Re: SD Driver : FAT: FAT read failed (blocknr 8) in sd card error while removing sd card during writing

[Madhav Chauhan]

On Thu, Jul 8, 2010 at 11:38 PM, hardik patel <hk5patel@gmail.com> wrote:
> Hi Madhav,
>
> thanks for your interest... I have card detect register so mmc_get_cd
> function i can check whether card is inserted or not ... so in sd host
> controller driver can detect that properly... but i think block driver
> does not detect that .... where i have to flush my request queue... i
> have gone through block.c and queue.c file which generate mmc_block.ko
> file but not sure where to modify... can any one guide me more

Which Kernel version you are using??
>
>
> On Thu, Jul 8, 2010 at 6:35 PM, MADHAV SINGHCHAUHAN
> <singh.madhav@samsung.com> wrote:
>> Card removal not detected by driver?
>> You should see a line of log if card removal is detected:
>> card xxxx removed
>>
>> Would you describe how do you detect card removal/insertion on your board?
>>
>> Regards,
>> -Ethan
>>
>> On Thu, Jul 8, 2010 at 6:05 PM, hardik patel <hk5patel@gmail.com> wrote:
>>> I have sd card on board ... During recording/writing SD card, remove
>>> SD card ... then i am getting endless error in dmesg as below :
>>>
>>> end_request: I/O error, dev mmcblk0, sector 24
>>> FAT: FAT read failed (blocknr 8)
>>> mmcblk0: error -110 sending status comand<3>mmcblk0: error -110
>>> sending read/write command, response 0x0, card status 0x0
>>> Block mmc_blk_issue_rq function call 346
>>> end_request: I/O error, dev mmcblk0, sector 4
>>> FAT: FAT read failed (blocknr 4)
>>> MMC: killing requests for dead queue
>>> end_request: I/O error, dev mmcblk0, sector 8
>>> FAT: FAT read failed (blocknr 8)
>>> FAT: FAT read failed (blocknr 4)
>>> FAT: FAT read failed (blocknr 8)
>>> FAT: FAT read failed (blocknr 4)
>>> FAT: FAT read failed (blocknr 8)
>>> FAT: FAT read failed (blocknr 4)
>>> FAT: FAT read failed (blocknr 8)
>>>
>>> How to stop this message ... what is ideal situation when we remove
>>> card while writing ...... can u help me what to do ?
>>>
>>>>When we insert the card hot plug dameon start sending the request to block layer  and kernel block layer
>>>>start sending the request to card.But when you remove the card in between request queue is not flushed properly..
>>>>so you need to flush your request queue at appropriate time.Also please note that even that you flush your request queue
>>>>at appropriate time some messages will come.
>>> where is the problem here? sd host controler driver problem or block
>>> driver problem or file system problem
>>>
>>> Note: I have formatted sd card with FAT32 file system .
>>>
>>>
>>>
>>> With EXT3 File system :
>>>
>>> Remove SD card while writing/recording we got error messages like
>>> below. but this is not endless. After some time it stops.
>>>
>>> ==============================
>>> =============
>>> end_request: I/O error, dev mmcblk0, sector 156536
>>> mmcblk0: error -110 sending status comand<3>mmcblk0: error -110
>>> sending read/write command, response 0x0, card status 0x0
>>> mmcblk0: error -110 requesting status
>>> end_request: I/O error, dev mmcblk0, sector 4736
>>> Aborting journal on device mmcblk0p1.
>>> ext3_abort called.
>>> EXT3-fs error (device mmcblk0p1): ext3_journal_start_sb: Detected
>>> aborted journal
>>> Remounting filesystem read-only
>>> end_request: I/O error, dev mmcblk0, sector 4448
>>> journal commit I/O error
>>> ===========================================
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at ?http://vger.kernel.org/majordomo-info.html
>>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>>
>>
>>
>>
>>
>>
>>
>
>
>
> --
> Regards,
> Hardik
>
> "If you are doing what you have always been doing then expect what you
> have always been getting."
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Re: Re: SD Driver : FAT: FAT read failed (blocknr 8) in sd card error while removing sd card during writing

[hardik patel]

I am using 2.6.30 linux kernel version ...

On Fri, Jul 9, 2010 at 9:20 AM, Madhav Chauhan <madhav.imsec@gmail.com> wrote:
> On Thu, Jul 8, 2010 at 11:38 PM, hardik patel <hk5patel@gmail.com> wrote:
>> Hi Madhav,
>>
>> thanks for your interest... I have card detect register so mmc_get_cd
>> function i can check whether card is inserted or not ... so in sd host
>> controller driver can detect that properly... but i think block driver
>> does not detect that .... where i have to flush my request queue... i
>> have gone through block.c and queue.c file which generate mmc_block.ko
>> file but not sure where to modify... can any one guide me more
>
> Which Kernel version you are using??
>>
>>
>> On Thu, Jul 8, 2010 at 6:35 PM, MADHAV SINGHCHAUHAN
>> <singh.madhav@samsung.com> wrote:
>>> Card removal not detected by driver?
>>> You should see a line of log if card removal is detected:
>>> card xxxx removed
>>>
>>> Would you describe how do you detect card removal/insertion on your board?
>>>
>>> Regards,
>>> -Ethan
>>>
>>> On Thu, Jul 8, 2010 at 6:05 PM, hardik patel <hk5patel@gmail.com> wrote:
>>>> I have sd card on board ... During recording/writing SD card, remove
>>>> SD card ... then i am getting endless error in dmesg as below :
>>>>
>>>> end_request: I/O error, dev mmcblk0, sector 24
>>>> FAT: FAT read failed (blocknr 8)
>>>> mmcblk0: error -110 sending status comand<3>mmcblk0: error -110
>>>> sending read/write command, response 0x0, card status 0x0
>>>> Block mmc_blk_issue_rq function call 346
>>>> end_request: I/O error, dev mmcblk0, sector 4
>>>> FAT: FAT read failed (blocknr 4)
>>>> MMC: killing requests for dead queue
>>>> end_request: I/O error, dev mmcblk0, sector 8
>>>> FAT: FAT read failed (blocknr 8)
>>>> FAT: FAT read failed (blocknr 4)
>>>> FAT: FAT read failed (blocknr 8)
>>>> FAT: FAT read failed (blocknr 4)
>>>> FAT: FAT read failed (blocknr 8)
>>>> FAT: FAT read failed (blocknr 4)
>>>> FAT: FAT read failed (blocknr 8)
>>>>
>>>> How to stop this message ... what is ideal situation when we remove
>>>> card while writing ...... can u help me what to do ?
>>>>
>>>>>When we insert the card hot plug dameon start sending the request to block layer  and kernel block layer
>>>>>start sending the request to card.But when you remove the card in between request queue is not flushed properly..
>>>>>so you need to flush your request queue at appropriate time.Also please note that even that you flush your request queue
>>>>>at appropriate time some messages will come.
>>>> where is the problem here? sd host controler driver problem or block
>>>> driver problem or file system problem
>>>>
>>>> Note: I have formatted sd card with FAT32 file system .
>>>>
>>>>
>>>>
>>>> With EXT3 File system :
>>>>
>>>> Remove SD card while writing/recording we got error messages like
>>>> below. but this is not endless. After some time it stops.
>>>>
>>>> ==============================
>>>> =============
>>>> end_request: I/O error, dev mmcblk0, sector 156536
>>>> mmcblk0: error -110 sending status comand<3>mmcblk0: error -110
>>>> sending read/write command, response 0x0, card status 0x0
>>>> mmcblk0: error -110 requesting status
>>>> end_request: I/O error, dev mmcblk0, sector 4736
>>>> Aborting journal on device mmcblk0p1.
>>>> ext3_abort called.
>>>> EXT3-fs error (device mmcblk0p1): ext3_journal_start_sb: Detected
>>>> aborted journal
>>>> Remounting filesystem read-only
>>>> end_request: I/O error, dev mmcblk0, sector 4448
>>>> journal commit I/O error
>>>> ===========================================
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at ?http://vger.kernel.org/majordomo-info.html
>>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>> --
>> Regards,
>> Hardik
>>
>> "If you are doing what you have always been doing then expect what you
>> have always been getting."
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>



-- 
Regards,
Hardik

"If you are doing what you have always been doing then expect what you
have always been getting."