linux-kernel - [REGRESSION] 3.13-rc2: locks up hard on trying to transfer a file to mmc based internal SD card slot

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-next>] [day] [month] [year] [list]

Message-ID: <4578341.ZjSDW1Al5s@merkaba>
Date:	Sat, 30 Nov 2013 14:53:51 +0100
From:	Martin Steigerwald <Martin@...htvoll.de>
To:	linux-kernel@...r.kernel.org, linux-mmc@...r.kernel.org
Subject: [REGRESSION] 3.13-rc2: locks up hard on trying to transfer a file to mmc based internal SD card slot

Just added linux-mmc. And I might git-bisect that at some time, but I do not 
intend to do it during my precious weekend. The chances of me bisecting it 
increase with workable suggestions on how to cut down the amount of iterations 
needed and avoid testing highly experimental between 3.12 and 3.13-rc1 kernels 
on a production laptop. I may be willing to test a patch or two. As I see 
there seem to have been quite some changes in MMC subsystem.

Hi!

Just does that on a ThinkPad T520 with:

merkaba:~> lspci -nn | grep MMC
0d:00.0 System peripheral [0880]: Ricoh Co Ltd PCIe SDXC/MMC Host Controller 
[1180:e823] (rev 08)

Mouse pointer freezes, no Ctrl-Alt-F1.

merkaba:~> fdisk -l /dev/mmcblk0

Disk /dev/mmcblk0: 31.4 GB, 31439454208 bytes
255 heads, 63 sectors/track, 3822 cylinders, total 61405184 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

        Device Boot      Start         End      Blocks   Id  System
/dev/mmcblk0p1            8192    61405183    30698496    c  W95 FAT32 (LBA

merkaba:/sys/block/mmcblk0#2> grep . * 2>/dev/null
alignment_offset:0
capability:10
dev:179:0
discard_alignment:0
ext_range:8
force_ro:0
inflight:       0        0
range:8
removable:0
ro:0
size:61405184
stat:     176       33     1672      102        0        0        0        0        
0      102      102
uevent:MAJOR=179
uevent:MINOR=0
uevent:DEVNAME=mmcblk0
uevent:DEVTYPE=disk

I do not want to take the time to diagnose this further, especially as its one 
of those nasty "I just lock up and I don´t tell you what went wrong" kind of 
bugs. Thats just not a nice way to tell that there has been an error.

If there is any five or ten minute information gathering task, I am willing to 
provide more information, but right now there is no chance on Earth that I 
will be bisecting while having a long list of more interesting things to do 
than that.

Thus for now I just use 3.12 kernel again. Maybe I will try with some rc5 or 
so again.

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7
--
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/