Mailinglist Archive: opensuse-bugs (4653 mails)

< Previous Next >
[Bug 575647] New: cdc-acm shows dev ttyACM0, ttyACM1 on 1st usb plugin, ttyACM1, ttyACM2 on subsequent plugins.
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 1 Feb 2010 08:44:57 +0000
  • Message-id: <bug-575647-21960@xxxxxxxxxxxxxxxxxxxxxxxx/>

Summary: cdc-acm shows dev ttyACM0, ttyACM1 on 1st usb plugin,
ttyACM1, ttyACM2 on subsequent plugins.
Classification: openSUSE
Product: openSUSE 11.2
Version: Final
Platform: i586
OS/Version: openSUSE 11.2
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
AssignedTo: kernel-maintainers@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: miles.maybee@xxxxxxxxx
QAContact: qa@xxxxxxx
Found By: ---
Blocker: ---

Created an attachment (id=339881)
--> (
excerpt of /var/log/messages

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:
Gecko/20091201 SUSE/3.5.6-1.1.1 Firefox/3.5.6

Fresh install of Suse 11.2, disabled network manager in the install dialogs,
because of problems related to the /etc/resolv.conf bug which apparently will
not be fixed. Yes, that's worth repeating. I had to completely reinstall to get
rid of a problem that won't be fixed. So, I'm using ifup. I defined my modem, a
Sony-Ericsson TM506 HSDPA device using the Yast modem dialog as ttyACM0,
installed kinternet, and connected, no problem. Installed updates. My phone is
also my Internet connection at my present location, and the usb cord connection
will occasionally disconnect. Upon reconnecting the cord, my modem no longer
worked. Inspection of /var/log/messages showed that the modem device name were
now changed to ttyACM1 and ttyACM2. I have 3 workarounds: 1) reboot when this
happens (just kidding, though that *does* work); 2) issue modprobe -r cdc-acm;
modprobe cdc-acm or 3) go back into yast and define modem1 pointing to ttyACM1
with the exact configuration of modem0. Option 3 is better, but it's still a
bug. I've been using linux since 1994, and it took me a while to figure out the
problem. A newbie would just conclude that the modem had quit working.

Reproducible: Always

Steps to Reproduce:
1. plug in the usb modem.
2. unplug it.
3. plug it in again.
Actual Results:
The devices are effectively renamed, though ttyACM1 *does* appear in both sets
of names, a fact my workaround takes advantage of ;).

Expected Results:
The devices should be named consistently ttyACM0 and ttyACM1.

The attachment is an excerpt from /var/log/messages which should provide enough
info. it shows the behavior from the second plugin and then the results of
modprobe -r cdc-acm; modprobe cdc-acm
and the reconnect via kinternet. The kernel message:
sysfs: cannot create duplicate filename '/dev/char/166:0'
is particularly interesting.

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >