// #eevblog — 2018-12-03
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
00:07:28 <Tezzers> ThunderSqueak: You play around with any digital P25 stuff?
00:10:47 <ThunderSqueak> nope
00:28:32 Quit: ThunderSqueak ([email protected]) Quit: Leaving
00:50:34 <Ampera> T3sl4, that only works with diet coke.
00:51:08 * T3sl4 hugs Ampera with a diet coke and mentos
00:53:01 * Ampera returns the hug, now soaked
00:55:07 <T3sl4> mmm, stickyhugs
01:00:18 <Ampera> but diet coke isn't sticky
01:01:34 Quit: merlin077 ([email protected]) EOF from client
01:01:47 Join: merlin077 ([email protected]) to #EEVblog
01:03:56 Quit: IvanTheBastard ([email protected]) Ping timeout: 121 seconds
01:05:27 Join: IvanTheBastard ([email protected]) to #EEVblog
01:05:27 Quit: IvanTheBastard ([email protected]) Changing hosts
01:06:38 * steve30 hugs T3sl4
01:07:13 <Ampera> lol, I had the weather set to celsius, and was sort of thrown when everything was in the very low single digits
01:07:16 <T3sl4> *hugs*
01:09:27 * steve30 makes coffee
01:10:19 <T3sl4> woo, coffee
01:24:10 <steve30> i have a headache
01:34:31 <T3sl4> :/
01:34:39 <T3sl4> i have a hot cocoa ^-^
01:37:30 <Tezzers> T3sl4: Turning into Fellbuendel? <_<
01:37:45 * T3sl4 shrugs, meows at Tezzers
01:38:42 <T3sl4> nah, but i'm game to play along when it comes to scritches and :3's
01:40:53 <Tezzers> And ^-^ too apparently :v
01:41:07 <T3sl4> =^.^=
01:41:14 <Tezzers> Fuckin' nekos
01:41:29 * steve30 purrs at T3sl4
01:41:45 <T3sl4> https://i.imgur.com/X5A0sDB.jpg
01:43:21 <steve30> I want some food
02:06:17 Join: andtfoot ([email protected]) to #EEVblog
02:24:33 Quit: andtfoot ([email protected]) Quit: Leaving
02:45:36 <DHess_US> Nothing suprising here. The medical industry has it even worse. https://www.theregister.co.uk/2018/11/30/pwned_via_oscilloscope/
02:50:14 <T3sl4> it's always been my understanding that lab equipment is something that should only ever be on an isolated internal network
02:50:24 <T3sl4> anyone exposing that to the internet deserves what they get
02:52:52 <DHess_US> Yep, but I have heard of company policies which didn't even allow that.
02:53:34 <DHess_US> The details in the story are pretty minor. I'd be more worried about a network connected instrument being compromised such that it compromises the rest of the network.
02:53:42 <DHess_US> Funny it was Siglent though.
02:54:12 <DHess_US> Things are even worse now with some instruments including WiFi.
02:55:50 <T3sl4> yep
02:56:35 <coppice> throughout life security is something its hard to get people to take seriously
02:58:51 <coppice> DHess_US: the first one that they found was insecure would have been whichever one they tried first
03:05:24 <DHess_US> https://ascienceenthusiast.com/neil-degrasse-tyson-releases-statement-accused-sexual-misconduct/
05:02:23 <DHess_US> It is beginning to seem that the watchdog timer blue screen problem on my Windows 10 test system was caused by the motherboard's JMicron IDE port. I had a pair of drives plugged into it for testing and removing them apparently stopped the crashes even though they were not doing anything.
05:24:30 <T3sl4> what's the difference between a jmicron and a regular IDE
05:29:38 <DHess_US> This is a high end motherboard from several years ago and I think what was going on was that Intel had dropped IDE support and at the time had not added SATA 3 support yet. So the motherboard includes a JMicron controller to add an IDE port and a Marvell controller to add a pair of 6 Gb/s SATA ports.
05:30:07 <T3sl4> oh, so an additional bridge chip instead of being in the superio
05:30:23 <DHess_US> They probably figured the IDE port was needed because even then SATA optical drives were not common.
05:30:38 <DHess_US> Exactly. Intel's south bridge did not include IDE.
05:31:07 <DHess_US> But there was still demand because optical drives made the change to SATA slower than hard drives.
05:31:18 <T3sl4> yup
05:32:20 <DHess_US> As to why it was causing the crashes, I have no idea. It might be a driver issue but since it is a test system and in its final configuration I will not be using the IDE port, I am not inclinded to investigate it. If I did, my next step would be to try an updated driver for the JMicron controller.
05:32:59 <T3sl4> also didn't know PCs bothered with watchdog
05:33:31 <DHess_US> Diagnosis was pretty much to start by disabling or removing the most likely cause. The JMIcron controller with a couple of IDE drives attached was the second thing I tried.
05:34:13 <DHess_US> It isn't what it seems. The watchdog timer error means communications was lost between processor cores.
05:34:59 <DHess_US> That is likely a driver failure which locked up one of the cores.
08:00:46 Quit: arekm ([email protected]) Quit: Lost terminal
08:27:57 Quit: Crazor ([email protected]) Client exited
08:28:42 Join: Crazor ([email protected]) to #EEVblog
08:29:01 Quit: Crazor ([email protected]) Client exited
11:29:14 Quit: racingchuck ([email protected]) Quit: Connection closed for inactivity
15:00:39 Join: ThunderSqueak ([email protected]) to #EEVblog
15:21:14 <Ampera> Hey, since I'm on holiday, I'm likely going to not be on IRC as much as I otherwise would.
15:22:20 <Ampera> In the event that you have something to message me, I might not get it, as my tablet doesn't keep track of IRC while suspended, and I can't be arsed to go look at the ZNC logs
15:30:30 <DHess_US> That is why I remote into my server which runs my IRC client among other things.
15:30:56 <DHess_US> Dual 900MHz Pentium 3 Xeon baby!
15:32:50 <DHess_US> I know a couple of people who use a Raspberri Pi running Linux to host their IRC client.
16:05:23 <Ampera> The issue is I can't easily do that without a command line IRC server.
16:05:35 <Ampera> I've already got SSH into my machine, I just need to figure out what client to use over command line
16:05:41 <Ampera> irssi doesn't seem to work too well
16:11:33 <mrpackethead> what is this austnet thing.
16:11:42 <mrpackethead> and why is anyone bothering
16:12:47 <mrpackethead> Ampera. at least here, Neutral is bonded to earth.
16:12:54 <mrpackethead> at the distribution board
16:13:04 <mrpackethead> that shojld answer your question
16:14:35 <Ampera> mrpackethead, you've been winging on about austnet for fucking days
16:14:41 <Ampera> either fuck off or shut the fuck up about ot
16:14:43 <Ampera> *it
16:15:13 <Ampera> However as for that, I presumed as much, I just wasn't completely sure.
16:27:02 <Ampera> Alright, that's set then.
16:27:21 <Ampera> I'm now using WeeChat, which looks like HexChat if it were stuffed into a terminal
16:30:30 <Ampera> Screen works too, I should be able to pop back in.
16:37:14 <mrpackethead> Ampera, its the eevblog way of doign things. Its all about whinging about thigns we dont' think are good. Look to the leader Dave.
16:37:16 <mrpackethead> :-)
16:39:26 <Ampera> Except Dave doesn't ususally go on chat rooms to complain about them, and then go on the associated forums to complain about them more.
16:40:01 <Ampera> Furthermore, you've only gone on about how you don't like /afternet/, and haven't done anything in a manner that's constructive or even vaguely worthwhile to anybody.
16:42:25 <Tezzers> Ampera: I was told in high school the reason for the polarized plug was metal appliances. Say you have a fridge. Unpolarized plug. You have a motor bolted to the frame of the fridge, has a bad winding, bad wire, whatever. Brings the whole chassis up to 120V potential. Mom has one hand on the sink or the grounded gas stove, and she reaches over and touches the fridge. Zap.
16:42:47 <mrpackethead> creating a new channel has just diluted things
16:42:54 <Tezzers> If the plug is polarized, then you can guarantee that the neutral is tied to the frame of the motor.
16:42:59 <Tezzers> Idk if tha'ts bullshit or not though.
16:43:17 <mrpackethead> Teezers, Neutral shoud'nt be attached to the frame of a motor
16:43:23 <mrpackethead> that would be badness
16:43:50 <Tezzers> But yeah, neutral is bonded to ground at the main panel or at the service disconnecting means...in most cases. You still have special circumstances like seperately derived neutrals from transformers or isolated ground systems.
16:44:09 <mrpackethead> Teezers, yes that is correct
16:44:22 <Tezzers> mrpackethead: That's what I'd think, but I was told that's what they did in the years ago in the days before polarized plugs but it never sounded right
16:44:51 <Tezzers> mrpackethead: I wouldh ope so, I spent a few months learning the 2008 NEC <_<
16:45:13 <mrpackethead> if you have an RCD.. think what woudl happen if your Netural was attached to the 'frame' or chasis
16:45:35 <Tezzers> mrpackethead: RCD didn't exist in the 50's and 60's
16:46:09 <mrpackethead> i've just installed 6 6mA RCD's on our new factory workbenches
16:46:19 <Tezzers> Back in the days of knob and tube and cloth wire and no such thing as an EGC
16:46:19 <mrpackethead> so called 'medical' grade ones.
16:46:40 <mrpackethead> as we often have things open and live
16:46:52 <Tezzers> At work we're not allowed to probe anything at 120V for testing. Strictly forbidden.
16:47:00 <Tezzers> You're allowed only for zero potential confirmation.
16:47:26 <Tezzers> If you want to probe something thath as 120V inside the box you have to remove power, lock it out, attach probes, and turn it on and look at voltage hands free.
16:48:05 <mrpackethead> i'm often working at 415V AC
16:48:19 <Tezzers> If you MUST measure live, you have to do paperwork, then your boss has to sign off on it, and their supervisor has to sign off on it. You have to have work planning justifying why you can't pconnect probes with power disconnected. How you're going to mitigate the risk.
16:48:22 <mrpackethead> ( 3phase between phases )
16:48:24 <Tezzers> It's fucking bullshit.
16:48:37 <Tezzers> And they just changed the rules and came out with new training that's even MORE restrictive.
16:48:59 <Tezzers> Anything over 50VDC you MUST shut it off and lock it out before doing anything with an open chassis.
16:49:21 <mrpackethead> we have some pretty interesting rules as well
16:49:45 <Tezzers> Oh, and if you're working on cord and plug connected equipment...only ONE person is allowed to work on it, PERIOD. Because it is only possible for ONE person to be in control of the cord. If you have two people working on it, one of them might plug it in while the other has their hands in it
16:50:18 <Tezzers> Like, are you shitting me? So, if I'm working on a power supply, I can't ask another guy to take a look at something and be next to him while he does it because then NEITHER of us is said to have "EXCLUSIVE CONTROL"
16:51:04 <mrpackethead> i can understand that
16:53:59 <mrpackethead> I have more problems with our POE stuff
18:33:36 <Halcyon> Afternoon all
18:39:59 <T3sl4> mronign
18:49:19 * Halcyon fondles T3sl4 a little
18:49:43 * T3sl4 buttbumps Halcyon
18:50:14 <Halcyon> :D
18:52:05 <Halcyon> YAY! A new Mike Jeavons week on!
20:30:37 Join: Crazor ([email protected]) to #EEVblog
22:00:02 Join: Guest|24882 ([email protected]) to #EEVblog
22:02:04 Quit: Guest|24882 ([email protected]) Quit: http://www.kiwiirc.com/ - A hand crafted IRC client
23:41:03 Quit: merlin077 ([email protected]) Ping timeout: 121 seconds
Search this day's buffer: