Subj : USB locking up To : Ky Moffet From : Barry Martin Date : Wed Sep 23 2020 08:26:00 Hi Ky! > Created a script to log some of the (lm-)sensors values to a file: > while true; do echo $( date '+%H:%M:%S' ), $( sensors | grep 'V' | sed > -r 's/^.* {8}\+(.*)øC .*$/\1/' ) >> > '/home/barry/Sensors_Log/Log.txt' ; sleep 0; done > Probably sloppy cookbook coding but does what I want: monitor voltages. KM> It looks like gibberish to me, so you're ahead! I have no idea what the stuff is between 'sed' and the redirect '>>' -- that was extracted from the 'cookbook'. Probably don't need as the original was for monitoring CPU temperature -- IIRC the "C" in that statement should be øC. Anyway, did plug in a memory card adapter and that made things lock up. Yea!! Unfortunately the Log file was 0 bytes after the reboot. And of course the adapter worked fine after that. > Did a test by plugging in a thumbdrive. Did not cause a lockup (not > surprised) but suppose good for a baseline. > > +12 Started at 12.10 then to 12.05. Don't think the drop had > anything to do with the insertion and removal of the thumbdrive. KM> Probably not. Thinking not also. > +5 Constant 5.01. Not that the thumbdrive draws that much but > half-figured would vary at least a hundreth of a volt. KM> You'd think? Well, here's a thought... maybe voltage is not KM> reaching the ports? USB tester is about 4 bucks... I have previously tested the voltage and appears OK. OTOH maybe not as closely as should: may have been more "yes there is a good 5v output [it's not at 4.5]" type of look. And somehow I half-remember just inserting the tester locked it up once -- does have to have data pass-through..... > Vcore Did vary but is constanty changing anyway. 0.91. 1.18, 1.27, > 1.25, 1.28, 1.12. KM> That's CPU voltage; modern CPUs only use what they need at the KM> moment. Right. Suppose only would be significant if spiked into the 2v range when a thumbdrive was plugged in. We're not sure what we're looking for. > Will randomly start the script and plug something in to see if can > capture a lockup. KM> Good, uh, bad luck? LIS at the top, did have a lockup but no log file created. Not sure if the script was running correctly as I do recall not being able to see the filesize for some reason. > .. One more time.....which one is Shinola? KM> The one that's not shiny. Ah! ¯ BarryMartin3@ ® ¯ @MyMetronet.NET ® .... The people who don't make mistakes are the people not doing anything. --- MultiMail/Win32 v0.47 þ wcECHO 4.2 ÷ ILink: The Safe BBS þ Bettendorf, IA --- QScan/PCB v1.20a / 01-0462 * Origin: ILink: CFBBS | cfbbs.no-ip.com | 856-933-7096 (454:1/1) .