Speicherzugrifffehler beim auslesen von Easymouse2 Serial

[tztztz]

Hallo,

möchte gern eine weitere Easymouse2 in meinen Server einbinden, leider wird mir beim auslesen der Serial eine Fehlermeldung generiert.

Zur Info es hängen bereits 5 Easymouse am Raspberry via Aktiv-USB -Hub welche per "40-usbadapter.rules" eingebunden sind.

uname -a
Linux raspberrypi 3.6.11+ #358 PREEMPT Tue Jan 15 00:45:33 GMT 2013 armv6l GNU/Linux

apt-get update && apt-get upgrade -y
wurde ausgeführt!

ls -la /usr/bin/rpi-update
-rwxr-xr-x 1 root root 6510 Jan 19 12:16 /usr/bin/rpi-update

df -h
Dateisystem GröÃe Benutzt Verf. Verw% Eingehängt auf
rootfs 7,2G 1,7G 5,1G 26% /
/dev/root 7,2G 1,7G 5,1G 26% /
devtmpfs 85M 0 85M 0% /dev
tmpfs 19M 260K 19M 2% /run
tmpfs 5,0M 0 5,0M 0% /run/lock
tmpfs 37M 0 37M 0% /run/shm
/dev/mmcblk0p1 56M 17M 40M 31% /boot
tmpfs 100M 8,0K 100M 1% /tmp
tmpfs 20M 0 20M 0% /var/tmp
tmpfs 70M 3,4M 67M 5% /var/log
tmpfs 150M 0 150M 0% /var/cache/apt/archives

Fehlermeldung:

Spoiler

root@raspberrypi ~ > udevadm info -n /dev/ttyUSB0 -a

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

looking at device '/devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.0/ttyU SB0/tty/ttyUSB0':
KERNEL=="ttyUSB0"
SUBSYSTEM=="tty"
DRIVER==""

looking at parent device '/devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1 .0/ttyUSB0':
KERNELS=="ttyUSB0"
SUBSYSTEMS=="usb-serial"
DRIVERS=="ftdi_sio"
ATTRS{port_number}=="0"
ATTRS{latency_timer}=="1"

looking at parent device '/devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1 .0':
KERNELS=="1-1.3:1.0"
SUBSYSTEMS=="usb"
DRIVERS=="ftdi_sio"
ATTRS{bInterfaceClass}=="ff"
ATTRS{bInterfaceSubClass}=="ff"
ATTRS{bInterfaceProtocol}=="ff"
ATTRS{bNumEndpoints}=="02"
ATTRS{supports_autosuspend}=="1"
ATTRS{bAlternateSetting}==" 0"
ATTRS{bInterfaceNumber}=="00"
ATTRS{interface}=="FT232R USB UART"

looking at parent device '/devices/platform/bcm2708_usb/usb1/1-1/1-1.3':
KERNELS=="1-1.3"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{devpath}=="1.3"
ATTRS{idVendor}=="0403"
ATTRS{speed}=="12"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="8"
ATTRS{busnum}=="1"
ATTRS{devnum}=="5"
ATTRS{configuration}==""
ATTRS{bMaxPower}==" 90mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="a0"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="0"
ATTRS{bcdDevice}=="0600"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{serial}=="A******k"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="75415762"
ATTRS{ltm_capable}=="no"
ATTRS{manufacturer}=="FTDI"
ATTRS{removable}=="removable"
ATTRS{idProduct}=="6001"
ATTRS{bDeviceClass}=="00"
ATTRS{product}=="FT232R USB UART"

looking at parent device '/devices/platform/bcm2708_usb/usb1/1-1':
KERNELS=="1-1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{devpath}=="1"
ATTRS{idVendor}=="0424"
ATTRS{speed}=="12"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{busnum}=="1"
ATTRS{devnum}=="2"
ATTRS{configuration}==""
ATTRS{bMaxPower}==" 2mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="3"
ATTRS{bcdDevice}=="0200"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="47"
ATTRS{ltm_capable}=="no"
ATTRS{removable}=="unknown"
ATTRS{idProduct}=="9512"
ATTRS{bDeviceClass}=="09"

looking at parent device '/devices/platform/bcm2708_usb/usb1':
KERNELS=="usb1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="01"
ATTRS{devpath}=="0"
ATTRS{idVendor}=="1d6b"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{authorized_default}=="1"
ATTRS{busnum}=="1"
ATTRS{devnum}=="1"
ATTRS{configuration}==""
ATTRS{bMaxPower}==" 0mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="1"
ATTRS{bcdDevice}=="0306"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{serial}=="bcm2708_usb"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="26"
ATTRS{ltm_capable}=="no"
ATTRS{manufacturer}=="Linux 3.6.11+ dwc_otg_hcd"
ATTRS{removable}=="unknown"
ATTRS{idProduct}=="0002"
ATTRS{bDeviceClass}=="09"
ATTRS{product}=="DWC OTG Controller"

looking at parent device '/devices/platform/bcm2708_usb':
KERNELS=="bcm2708_usb"
SUBSYSTEMS=="platform"
DRIVERS=="dwc_otg"
ATTRS{hnp}=="HstNegScs = 0x0"
ATTRS{srp}=="SesReqScs = 0x1"
ATTRS{regvalue}=="invalid offset"
ATTRS{hsic_connect}=="HSIC Connect = 0x1"
ATTRS{guid}=="GUID = 0x2708a000"
ATTRS{mode}=="Mode = 0x1"
ATTRS{srpcapable}=="SRPCapable = 0x1"
ATTRS{regdump}=="Register Dump"
ATTRS{gpvndctl}=="GPVNDCTL = 0x00000000"
ATTRS{ggpio}=="GGPIO = 0x00000000"
ATTRS{hprt0}=="HPRT0 = 0x00021405"
ATTRS{wr_reg_test}=="Time to write GNPTXFSIZ reg 10000000 times: 380 msecs ( 38 jiffies)"
ATTRS{hcd_frrem}=="HCD Dump Frame Remaining"
ATTRS{mode_ch_tim_en}=="Mode Change Ready Timer Enable = 0x0"
ATTRS{gnptxfsiz}=="GNPTXFSIZ = 0x01000306"
ATTRS{remote_wakeup}=="Remote Wakeup Sig = 0 Enabled = 0 LPM Remote Wakeup = 0"
ATTRS{busconnected}=="Bus Connected = 0x1"
ATTRS{hcddump}=="HCD Dump"
ATTRS{gotgctl}=="GOTGCTL = 0x001c0001"

Message from syslogd@raspberrypi at Jan 20 10:44:10 ...
kernel:[75365.773800] Internal error: Oops: 27 [#1] PREEMPT ARM

Message from syslogd@raspberrypi at Jan 20 10:44:10 ...
kernel:[75365.797188] Process udevadm (pid: 13262, stack limit = 0xc7a18268)

Message from syslogd@raspberrypi at Jan 20 10:44:10 ...
kernel:[75365.799039] Stack: (0xc7a19ea0 to 0xc7a1a000)

Message from syslogd@raspberrypi at Jan 20 10:44:10 ...
kernel:[75365.800871] 9ea0: c7a18000 c00cf868 000080d0 beb6a4a0 50fbca79 50fbca 79 00000000 00000002

Message from syslogd@raspberrypi at Jan 20 10:44:10 ...
kernel:[75365.804608] 9ec0: ca811c70 c3cd9a20 00000000 00000ac4 000081a4 c7a19f 78 00000001 c9929000

Message from syslogd@raspberrypi at Jan 20 10:44:10 ...
kernel:[75365.808481] 9ee0: ffffff9c f29a80e0 c7a18000 c9a8e000 c05312a0 c9b24e e0 c9b24ef8 c7a19f88

Message from syslogd@raspberrypi at Jan 20 10:44:10 ...
kernel:[75365.812520] 9f00: beb6a50c 00001000 ca971588 c02803d8 c0516168 c02349 a8 ca97158c c0516168

Message from syslogd@raspberrypi at Jan 20 10:44:10 ...
kernel:[75365.816710] 9f20: c03b7ad0 c011e97c 00000001 c9b2d468 00000000 c9b2d4 60 beb6a50c 00001000

Message from syslogd@raspberrypi at Jan 20 10:44:10 ...
kernel:[75365.820939] 9f40: c7a18000 c7a19f88 c7a18000 00000000 beb6bde4 c00c17 f0 c9b2d468 c3f678c0

Message from syslogd@raspberrypi at Jan 20 10:44:10 ...
kernel:[75365.825267] 9f60: c9b2d460 00000000 00000000 c9b2d460 beb6a50c 000010 00 00000000 c00c18fc

Message from syslogd@raspberrypi at Jan 20 10:44:10 ...
kernel:[75365.829640] 9f80: 00000024 00000000 00000000 00000000 01695598 000302 18 00000003 00000003

Message from syslogd@raspberrypi at Jan 20 10:44:10 ...
kernel:[75365.834202] 9fa0: c000dbe8 c000da60 01695598 00030218 00000003 beb6a5 0c 00001000 00000000

Message from syslogd@raspberrypi at Jan 20 10:44:10 ...
kernel:[75365.838922] 9fc0: 01695598 00030218 00000003 00000003 01694e28 000000 00 00026df8 beb6bde4

Message from syslogd@raspberrypi at Jan 20 10:44:10 ...
kernel:[75365.843820] 9fe0: 00000100 beb6a498 0001b978 b6eeb2bc 60000010 000000 03 b6f2271c b6f220f8

Message from syslogd@raspberrypi at Jan 20 10:44:10 ...
kernel:[75365.880021] Code: e28330e0 e1530004 e58d3044 9a000029 (e5d42000)
Speicherzugriffsfehler

 

[chrisbi]

AW: Speicherzugrifffehler beim auslesen von Easymouse2 Serial

Raspbian / Raspberry hat noch so seine Probleme mit udevadm.

Kuck mal hier: Talk Undefinierbare Fehlermeldung bei offener Konsole Raspberry / IPC auch im Syslog

Gesendet von meinem GT-I9000 mit Tapatalk 2

 

[tztztz]

AW: Speicherzugrifffehler beim auslesen von Easymouse2 Serial

Ich habe das Problem (was natürlich an sich noch weiter besteht beim auslesen) umgangen
das ich alle Reader abgeklemmt habe und nur den neuen angeschlossen habe.

Den ersten Reader liest udevadm info -n /dev/ttyUSB0 -a ja aus und somit habe ich die Serial heraus gefunden und in die Rules eintragen können.

 

[aragorn]

AW: Speicherzugrifffehler beim auslesen von Easymouse2 Serial

das hab ich mit laila auch getestet aber hatte nur kurzfristig geholfen - der udevadm befehl sorgt trotzdem für probleme also am besten garnicht erst benutzen

" lsusb -v | grep iSerial " funktioniert auch super und ist zudem wesendlich kürzer und auch leichter zu merken