Bug#683839: modemmanager fiddles with ttyUSB devices without asking first
On 11.09.2012 22:07, Ian Jackson wrote: Michael Biebl writes (Re: Bug#683839: modemmanager fiddles with ttyUSB devices without asking first): A whitelist is not an acceptable solution with the amount of new devices popping up every day. This would be a losing battle. Then the question is whether it is better to ask users a question when they try to use what may be a modem, or to risk destroying hardware or injuring people. Not sure if this addresses your issue fully, but thought it might be interesting nonetheless: https://bugzilla.gnome.org/show_bug.cgi?id=647556 http://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=8450b7b2a39a6e1c9fda950dc3f821984c73c56b Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#683839: modemmanager fiddles with ttyUSB devices without asking first
Add radio interfaces to the list of devices that have suffered from modem manager's interference. When modem manager asserts RTS, a radio may be destroyed or an operator placed into violation of the law if the radio is not correctly configured for transmission. I concur with the other comments that a blacklist is not the right way to fix this. But I will be absolutely delighted to have one versus nothing at all. The following link contains udev rules for blacklisting two affected radio interfaces. https://bugzilla.redhat.com/show_bug.cgi?id=771010 Many thanks, - Bill -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683839: modemmanager fiddles with ttyUSB devices without asking first
On 19.09.2012 16:51, Maximilian Gaukler wrote: this also breaks apcupsd when connecting a UPS through a USB-serial converter. It took some time to find this out, so I am not very amused. https://bugzilla.redhat.com/show_bug.cgi?id=544121 is a related bug report. This behaviour is not okay because modem-manager is installed by default and there is no simple standardised way for other applications to stop it from interfering with a particular device. You could try the workaround described at https://bugzilla.redhat.com/show_bug.cgi?id=544121#c54 for now -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#683839: modemmanager fiddles with ttyUSB devices without asking first
Hi, this also breaks apcupsd when connecting a UPS through a USB-serial converter. It took some time to find this out, so I am not very amused. This behaviour is not okay because modem-manager is installed by default and there is no simple standardised way for other applications to stop it from interfering with a particular device. Because the status lines are changed when opening and closing a device, some boards like Arduino-based 3D printer controls even reset because of modem-manager testing them! We need to find some solution so that this autoprobing is not active by default (only enabled after user interaction), since it is impossible to change every single control software using a serial port. Thanks Max Gaukler -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683839: modemmanager fiddles with ttyUSB devices without asking first
On 22.08.2012 19:18, Ian Jackson wrote: Michael Biebl writes (Re: Bug#683839: modemmanager fiddles with ttyUSB devices without asking first): Please attach the output of udevadm info --attribute-walk --name=/dev/ttyUSB0 This should include the VID/PID and driver name which should be enough to blacklist this particular device. For the reasons I have explained in my bug report, a blacklist is not the appropriate way to deal with this. There should be a whitelist instead. A whitelist is not an acceptable solution with the amount of new devices popping up every day. This would be a losing battle. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#683839: modemmanager fiddles with ttyUSB devices without asking first
Michael Biebl writes (Re: Bug#683839: modemmanager fiddles with ttyUSB devices without asking first): A whitelist is not an acceptable solution with the amount of new devices popping up every day. This would be a losing battle. Then the question is whether it is better to ask users a question when they try to use what may be a modem, or to risk destroying hardware or injuring people. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683839: modemmanager fiddles with ttyUSB devices without asking first
Michael Biebl writes (Re: Bug#683839: modemmanager fiddles with ttyUSB devices without asking first): Please attach the output of udevadm info --attribute-walk --name=/dev/ttyUSB0 This should include the VID/PID and driver name which should be enough to blacklist this particular device. For the reasons I have explained in my bug report, a blacklist is not the appropriate way to deal with this. There should be a whitelist instead. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683839: modemmanager fiddles with ttyUSB devices without asking first
On 04.08.2012 19:52, Ian Jackson wrote: I have been having trouble getting our reprap (open hardware 3D printer) connecting reliably. Sometimes the host control softare gets EBUSY and at other times it appears to suffer protocol violations during startup. The reprap shows up as a ttyUSB emulated serial device. Please attach the output of udevadm info --attribute-walk --name=/dev/ttyUSB0 This should include the VID/PID and driver name which should be enough to blacklist this particular device. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#683839: modemmanager fiddles with ttyUSB devices without asking first
Package: modemmanager Version: 0.4+git.20100624t180933.6e79d15-2 Severity: serious I have been having trouble getting our reprap (open hardware 3D printer) connecting reliably. Sometimes the host control softare gets EBUSY and at other times it appears to suffer protocol violations during startup. The reprap shows up as a ttyUSB emulated serial device. EBUSY indicates that something else on the system is opening the serial port. Having investigated this, in particular grepping the logs, I see things like this: /var/log/daemon.log:Aug 4 14:04:09 zealot modem-manager: (ttyUSB0): probe requested by plugin 'Generic' /var/log/daemon.log:Aug 4 14:04:20 zealot modem-manager: (ttyUSB0) closing serial device... /var/log/daemon.log:Aug 4 14:04:21 zealot modem-manager: (ttyUSB0) opening serial device... /var/log/daemon.log:Aug 4 14:04:27 zealot modem-manager: (ttyUSB0) closing serial device... It is not appropriate for a package like modemmanager to unconditionally open and probe serial devices. Serial devices, including both conventional ttyS* devices and USB-serial adapters such as ttyUSB, might be connected to arbitrary hardware. Indeed serial ports are often used for connection to ad-hoc peripherals such as the microcontrollers controlling machine tools and other real-world physical systems. Sending probe messages to them might cause arbitrarily weird or dangerous behaviour, since such peripherals by their nature speak their own private protocols. Even opening the port might interfere with control software. The modemmanager package should therefore obtain permission before allowing probing of arbitrary serial ports. (Automatic probing, without permission, of serial ports which modemmanager knows, eg via the USB device ID or kernel device name, are actually modems is fine.) The default value for this permission must be off. I don't know exactly how I got modemmanager installed, but the most likely cause is the Recommends from network-manager, which I do use on this system. I did try to get my GSM/HSPA modem connection working with network-manager, but failed; I use a simple shell script to invoke pppd by hand for that; so luckily for me I am able to deinstall modemmanager. Users who are using modemmanager for their network connection /and/ also trying to do machinery control with the same computer would probably benefit from a more selective workaround which disables the scan for certain devices. Severity justification: This behaviour of modemmanager can undoubtedly cause trouble for unrelated software on the system. It might cause machinery connected to the computer to malfunction, perhaps causing physical damage or even personal injury. These latter consequences are perhaps unlikely but it is difficult to analyse the risk because we can't know what protocols such hardware speaks. Thanks, Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
