Project

General

Profile

Actions

Bug #2465

closed

OSX Hard Lockup When Radio Disconnected

Added by JC Wren almost 9 years ago. Updated about 4 years ago.

Status:
Rejected
Priority:
High
Assignee:
-
Category:
-
Target version:
-
Start date:
03/29/2015
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
Baofeng BF-888S
Platform:
MacOS
Debug Log:
I read the instructions above:

Description

This is more or less a reiteration of issue #2301. Disconnecting the radio will always cause OSX to lock up hard. No mouse movement, keyboard non-responsive, etc. Closing the program (clover-Q) will also cause this lock-up, however it's not 100% as reliable as unplugging the radio or USB adapter.

It makes radio programming very frustrating under OSX.


Related issues

Has duplicate Bug #2301: OS X Freezes between walkie swapsClosed02/07/2015

Actions
Actions #1

Updated by Jim Unroe almost 9 years ago

  • Status changed from New to Feedback

Does your programming cable have a Prolific type chip in it and if it does, are you using one of the "generic" drivers linked to on the "MacOS_Tips":http://chirp.danplanet.com/projects/chirp/wiki/MacOS_Tips page?

Jim KC9HI

Actions #2

Updated by JC Wren almost 9 years ago

kextstat reports this is the Prolific PL-2303 driver, version 1.5.1. -- com.prolific.driver.PL2303 (1.5.1) <81 38 5 4 3>

I don't know if this is a counterfeit part or not. It's an actual Baofeng cable, but of course that doesn't mean it's an authentic Prolific part.

OSX version is 10.10.2.

Chirp is programming the radio, in case I wasn't clear on that. The lock-up will occur unplugging the radio, unplugging the cable, and usually when closing the program, regardless if the radio is powered on or not. I've not been able to make the hang occur when closing the program and I HAVEN'T opened a connection to the radio.

Actions #3

Updated by Tom Hayward almost 9 years ago

What happens when you open/close/read/write/unplug the serial port using another serial application? Here's some instruction for doing this with screen: http://pbxbook.com/other/mac-tty.html

The reason I ask is that there are three things that can cause a complete lockup:

OS bug

driver bug

hardware issue, such as power supply or memory failure

Chirp, as application software, does not have the permissions required to take over your system like that. My money is on the lockup being caused by your USB serial driver.

Actions #4

Updated by Dan Smith about 4 years ago

  • Status changed from Feedback to Rejected

As Tom said, the only thing that can cause an OS hard lock up is out of chirp's control. Serial drivers on OSX are really (really) terrible for the most part, so it is not at all surprising to suspect a driver bug there. I'd recommend FTDI-based cables when possible as those drivers seem to be the best (although not amazing).

I'm closing this for clarity.

Actions

Also available in: Atom PDF