linux-kernel - Re: zaurus: mmcblk0: error -110

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 12 Apr 2011 21:39:44 +0200
From:	Cyril Hrubis <metan@....cz>
To:	Chris Ball <cjb@...top.org>
Cc:	pavel@....cz, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, eric.y.miao@...il.com,
	utx@...guin.cz, zaurus-devel@...ts.linuxtogo.org,
	marek.vasut@...il.com, linux-mmc@...r.kernel.org
Subject: Re: zaurus: mmcblk0: error -110

Hi!
> > When I insert the mmc card to zaurus, it gets properly detected and prints some
> > info into console. Mounting reading/writing files works fine.
> >
> > However when the card is removed (doesn't need to be mounted before), the
> > removal is most likely not detected, so when I insert it again, no info is
> > printed into console and moreover when I try to mount it zaurus goes into
> > infinite loop printing:
> >
> > Buffer I/O error on device mmcblk0p1, logical block 9
> > mmcblk0: error -110 sending status command
> > mmcblk0: error -110 sending read/write command, response 0xb00, card status 0xb00
> > end_request: I/O error, dev mmcblk0, sector 257
> > Buffer I/O error on device mmcblk0p1, logical block 10
> > ...
> >
> > Related part of the .config:
> >
> > #
> > # OTG and related infrastructure
> > #
> > # CONFIG_USB_GPIO_VBUS is not set
> > # CONFIG_USB_ULPI is not set
> > # CONFIG_NOP_USB_XCEIV is not set
> > CONFIG_MMC=y
> > # CONFIG_MMC_DEBUG is not set
> > CONFIG_MMC_UNSAFE_RESUME=y
> 
> Your symptoms match the bug that was fixed by:
> 
> bad3babace2ee4d ("mmc: fix CONFIG_MMC_UNSAFE_RESUME regression")
> 
> but this fix made it into 2.6.38, so if you're using 2.6.38 final then
> you shouldn't be seeing this.  Could you confirm that you have this
> patch?

It seems that the pxa tree I have is still based on 2.6.38-rc8.

And yes, turning CONFIG_MMC_UNSAFE_RESUME off seems to fix that problem.

I'll try to update the kernel tree and try again with CONFIG_MMC_UNSAFE_RESUME
enabled.

-- 
metan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/