theZacAttacks
Posts: 6
Joined: Fri Jul 27, 2012 5:47 pm
Location: North Carolina

udevadm info causing kernel panic

Fri Aug 03, 2012 1:03 pm

Whenever I run

Code: Select all

udevadm info --attribute-walk --name=usbdev1.3 | less
to get info on my keyboard, my RPi throws a kernel panic, and I have to do a hard reboot. Anyone else having this problem?

I'm running the Raspbian image, by the way.

waldo
Posts: 12
Joined: Sat Sep 01, 2012 5:55 am

Re: udevadm info causing kernel panic

Sat Sep 01, 2012 5:58 am

Yes.

The particular spot where it crashes, (for me) is when trying to do a register dump:

Code: Select all

  looking at parent device '/devices/platform/bcm2708_usb':
    KERNELS=="bcm2708_usb"
    SUBSYSTEMS=="platform"
    DRIVERS=="dwc_otg"
    ATTRS{modalias}=="platform:bcm2708_usb"
    ATTRS{regoffset}=="0xffffffff"
    ATTRS{regvalue}=="invalid offset"
    ATTRS{mode}=="Mode = 0x1"
    ATTRS{hnpcapable}=="HNPCapable = 0x1"
    ATTRS{srpcapable}=="Mode = 0x1"
    ATTRS{hsic_connect}=="HSIC Connect = 0x1"
    ATTRS{inv_sel_hsic}=="Invert Select HSIC = 0x0"
    ATTRS{hnp}=="HstNegScs = 0x0"
    ATTRS{srp}=="SesReqScs = 0x1"
    ATTRS{buspower}=="Bus Power = 0x1"
    ATTRS{bussuspend}=="Bus Suspend = 0x0"
    ATTRS{busconnected}=="Bus Connected = 0x1"
    ATTRS{gotgctl}=="GOTGCTL = 0x001c0001"
    ATTRS{gusbcfg}=="GUSBCFG = 0x20001700"
    ATTRS{grxfsiz}=="GRXFSIZ = 0x00000306"
    ATTRS{gnptxfsiz}=="GNPTXFSIZ = 0x01000306"
    ATTRS{gpvndctl}=="GPVNDCTL = 0x00000000"
    ATTRS{ggpio}=="GGPIO = 0x00000000"
    ATTRS{guid}=="GUID = 0x2708a000"
    ATTRS{gsnpsid}=="GSNPSID = 0x4f54280a"
    ATTRS{devspeed}=="Device Speed = 0x0"
    ATTRS{enumspeed}=="Device Enumeration Speed = 0x1"
    ATTRS{hptxfsiz}=="HPTXFSIZ = 0x02000406"
    ATTRS{hprt0}=="HPRT0 = 0x00001005"
    ATTRS{remote_wakeup}=="Remote Wakeup Sig = 0 Enabled = 0 LPM Remote Wakeup = 0"
    ATTRS{regdump}=="Register Dump"
Me also on the Raspbian image.

samsamsam
Posts: 36
Joined: Fri Aug 17, 2012 11:36 am

Re: udevadm info causing kernel panic

Sat Sep 01, 2012 9:24 pm

I have this same problem... However my system still working after traces crash stack.

42devil
Posts: 1
Joined: Sun Nov 11, 2012 11:17 am

Re: udevadm info causing kernel panic

Sun Nov 11, 2012 11:20 am

I'm having the same issue with USB cardprogrammers. When i try to do a udevadm info /dev/ttyUSB0 --attribute-walk the Raspberry hangs i need to do a hard reboot.
The drivers used are FTDI_SIO. OS is archlinux for ARM, i have also tried Raspberry Weezy, with exactly the same result.

Any ideas?

keble
Posts: 36
Joined: Tue Apr 03, 2012 4:46 pm

Re: udevadm info causing kernel panic

Tue Jan 08, 2013 8:48 pm

Me too. I'm using this article;
http://www.weather-watch.com/smf/index. ... ic=39257.0
to work out udev rules for my USB-attached android.

The suggested script uses udevadm info -a -p $DEVICE. udevadm starts but then there's a message 'Entering kbd ... Due to oops @some_address' then the Pi hangs.

Looks like there's a gremlin in the works?
unname gives: Linux raspberrypi 3.2.27+ #250 PREEMPT thu Oct 18

I'm new to a lot of this, finding my way!

I'd appreciate any help.

Martek
Posts: 1
Joined: Tue Jan 22, 2013 1:15 am

Re: udevadm info causing kernel panic

Tue Jan 22, 2013 1:24 am

Same here. It crashes at bcm2708_usb.. Any help??

ssjoholm
Posts: 1
Joined: Sun Apr 14, 2013 3:02 pm

Re: udevadm info causing kernel panic

Sun Apr 14, 2013 3:08 pm

Hi,

I noted the same issue, when I tried to list information about the connected KM8090 Velleman Relay board. The relay board has external power, so there is no problem driving it via RPI USB connector.

Print system version
* uname
Linux rpi80.local 3.6.11+ #408 PREEMPT Wed Apr 10 20:33:39 BST 2013 armv6l GNU/Linux
* Version
Linux version 3.6.11+ ([email protected]) (gcc version 4.7.2 20120731 (prerelease) (crosstool-NG linaro-1.13.1+bzr2458 - Linaro GCC 2012.08) ) #408 PREEMPT Wed Apr 10 20:33:39 BST 2013
* /etc/os-release
PRETTY_NAME="Debian GNU/Linux 7.0 (wheezy)"
NAME="Debian GNU/Linux"
VERSION_ID="7.0"
VERSION="7.0 (wheezy)"
ID=debian
ANSI_COLOR="1;31"
HOME_URL="http://www.debian.org/"
SUPPORT_URL="http://www.debian.org/support/"
BUG_REPORT_URL="http://bugs.debian.org/"
* Broadcom firmware version
Apr 2 2013 22:57:46
Copyright (c) 2012 Broadcom
version 381148 (release)
Done

# udevadm info --name=/dev/ttyACM0 --attribute-walk

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.2/1-1.2:1.0/tty/ttyACM0':
KERNEL=="ttyACM0"
SUBSYSTEM=="tty"
DRIVER==""

looking at parent device '/devices/platform/bcm2708_usb/usb1/1-1/1-1.2/1-1.2:1.0':
KERNELS=="1-1.2:1.0"
SUBSYSTEMS=="usb"
DRIVERS=="cdc_acm"
ATTRS{bInterfaceClass}=="02"
ATTRS{bmCapabilities}=="2"
ATTRS{bInterfaceSubClass}=="02"
ATTRS{bInterfaceProtocol}=="01"
ATTRS{bNumEndpoints}=="01"
ATTRS{supports_autosuspend}=="1"
ATTRS{bAlternateSetting}==" 0"
ATTRS{bInterfaceNumber}=="00"

looking at parent device '/devices/platform/bcm2708_usb/usb1/1-1/1-1.2':
KERNELS=="1-1.2"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{devpath}=="1.2"
ATTRS{idVendor}=="10cf"
ATTRS{speed}=="12"
ATTRS{bNumInterfaces}==" 2"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="8"
ATTRS{busnum}=="1"
ATTRS{devnum}=="4"
ATTRS{configuration}==""
ATTRS{bMaxPower}=="100mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="c0"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="0"
ATTRS{bcdDevice}=="0001"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="24"
ATTRS{ltm_capable}=="no"
ATTRS{removable}=="removable"
ATTRS{idProduct}=="8090"
ATTRS{bDeviceClass}=="02"

looking at parent device '/devices/platform/bcm2708_usb/usb1/1-1':
KERNELS=="1-1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="02"
ATTRS{devpath}=="1"
ATTRS{idVendor}=="0424"
ATTRS{speed}=="480"
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}=="35"
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}=="25"
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 = 0x00001005"
ATTRS{wr_reg_test}=="Time to write GNPTXFSIZ reg 10000000 times: 350 msecs (35 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"

!!! Here Raspberry Pi freezes and power on/off is required !!!

Anywhere these kind of issues can be reported?

Regards,
Sebastian

Return to “Troubleshooting”