linux-kernel - crash related to plugging in and unplugging of sd/mmc readers (and other storage media but not pendrives)

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

Message-ID: <Pine.LNX.4.64.1111011858200.16802@bwv190.internetdsl.tpnet.pl>
Date:	Tue, 1 Nov 2011 19:07:12 +0100 (CET)
From:	Piotr Gluszenia Slawinski <curious@...190.internetdsl.tpnet.pl>
To:	linux-kernel@...r.kernel.org
Subject: crash related to plugging in and unplugging of sd/mmc readers (and
 other storage media but not pendrives)

hello.
to be brief :
linux kernel versions affected :
from 3.1.0-rc4 down to 2.6.26 (did not test anything below)

hardware :
x86 32bit acer aspire 3690

steps to reproduce:
sometimes it works fine - every time.
all 'pendrive' sticks work fine.

yet sometimes plugging in ext hdd,
sdd/mmc card reader, digital camera etc. - yields in 100% cpu consumption,
and no task is listed to do that. unplugging it sometimes just cuts the 
problem. yet soometimes (attached) oops happens. - sometimes first time 
you unplug it, sometimes you're 'lucky'. sometimes it oopses on plugging 
it in.

when there is 'sometimes' period (phase of moon perhaps) - nothing helps. 
you can reboot, curse - it just does not work. so whatever causes it to 
either do work or not has to change somewhere in 'back stages' .

i've observed same behaviour on other computers - amd64 sempron with 
nforce2 chipset, ancient sis-chipset based athlon, and even ancient p3.
with those computers i can resolve it by turning machine off, and 
reordering pci cards. then it's either better or worse - for some time.
there is not any 'specific' card layout making it work - just change seems 
sufficient.

-- 
View attachment "usb_crash_linux_3.0.4.txt" of type "TEXT/plain" (30259 bytes)