[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20887.simon.1185278411@5ec7c279.invalid>
Date: Tue, 24 Jul 2007 13:00:11 +0100
From: "Simon Arlott" <simon@...e.lp0.eu>
To: "Kay Sievers" <kay.sievers@...y.org>
Cc: "Greg KH" <gregkh@...e.de>,
"Cornelia Huck" <cornelia.huck@...ibm.com>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: sysfs/udev broken in latest git?
On Tue, July 24, 2007 12:55, Kay Sievers wrote:
> On 7/24/07, Simon Arlott <simon@...e.lp0.eu> wrote:
>> On Tue, July 24, 2007 10:20, Kay Sievers wrote:
>> > On 7/24/07, Greg KH <gregkh@...e.de> wrote:
>> >> On Tue, Jul 24, 2007 at 10:03:14AM +0200, Cornelia Huck wrote:
>> >> > On Tue, 24 Jul 2007 00:25:40 -0700,
>> >> > Greg KH <gregkh@...e.de> wrote:
>> >> >
>> >> > > On Tue, Jul 24, 2007 at 07:39:38AM +0100, Simon Arlott wrote:
>> >> > > > The following commit appears to break some of my udev rules (I don't
>> >> > > > have the time to finish the bisect right now, but there's only four
>> >> > > > changes showing in "git bisect visualize" - this one is tagged
>> >> > > > bisect/bad, and the other three are docs/docs/unrelated).
>> >> > > >
>> >> > > > Neither of these symlinks get created by udev on kernels marked bad
>> >> > > > (see bisect log below):
>> >> > > >
>> >> > > > ACTION=="add", \
>> >> > > > KERNEL=="event*", \
>> >> > > > SUBSYSTEM=="input", \
>> >> > > > SYSFS{description}=="i8042 KBD port", \
>> >> > > > NAME="input/%k", \
>> >> > > > SYMLINK="input/i8042-kbd", \
>> >> > > > MODE="0640", \
>> >> > > > GROUP="event"
>> >> > > >
>> >> > > > ACTION=="add", \
>> >> > > > KERNEL=="event*", \
>> >> > > > SUBSYSTEM=="input", \
>> >> > > > SYSFS{manufacturer}=="Logitech", \
>> >> > > > SYSFS{product}=="USB-PS/2 Optical Mouse", \
>> >> > > > NAME="input/%k", \
>> >> > > > SYMLINK="input/logitech-mouse", \
>> >> > > > MODE="0640", \
>> >> > > > GROUP="event"
>> >
>> > Simon, please run:
>> > udevinfo --attribute-walk --path=<devpath>
>> > for the mouse on the working and the non-working kernel.
>>
>> On the working kernel:
>>
>> looking at device '/devices/pci0000:00/0000:00:0c.0/usb2/2-2/2-2:1.0':
>
> Please start with the event* device your rule catches, not the usb one.
>
looking at device '/class/input/event4':
KERNEL=="event4"
SUBSYSTEM=="input"
DRIVER==""
ATTR{dev}=="13:68"
looking at device '/class/input/input4':
KERNEL=="input4"
SUBSYSTEM=="input"
DRIVER==""
ATTR{modalias}=="input:b0003v046DpC044e0110-e0,1,2,k110,111,112,113,114,115,116,117,r0,1,6,8,amlsfw"
ATTR{uniq}==""
ATTR{phys}=="usb-0000:00:0c.0-2/input0"
ATTR{name}=="Logitech USB-PS/2 Optical Mouse"
looking at parent device '/devices/pci0000:00/0000:00:0c.0/usb2/2-2/2-2:1.0':
KERNELS=="2-2:1.0"
SUBSYSTEMS=="usb"
DRIVERS=="usbhid"
ATTRS{modalias}=="usb:v046DpC044d2710dc00dsc00dp00ic03isc01ip02"
ATTRS{bInterfaceProtocol}=="02"
ATTRS{bInterfaceSubClass}=="01"
ATTRS{bInterfaceClass}=="03"
ATTRS{bNumEndpoints}=="01"
ATTRS{bAlternateSetting}==" 0"
ATTRS{bInterfaceNumber}=="00"
looking at parent device '/devices/pci0000:00/0000:00:0c.0/usb2/2-2':
KERNELS=="2-2"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{product}=="USB-PS/2 Optical Mouse"
ATTRS{manufacturer}=="Logitech"
ATTRS{quirks}=="0x0"
ATTRS{maxchild}=="0"
ATTRS{version}==" 2.00"
ATTRS{devnum}=="3"
ATTRS{busnum}=="2"
ATTRS{speed}=="1.5"
ATTRS{bMaxPacketSize0}=="8"
ATTRS{bNumConfigurations}=="1"
ATTRS{bDeviceProtocol}=="00"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceClass}=="00"
ATTRS{bcdDevice}=="2710"
ATTRS{idProduct}=="c044"
ATTRS{idVendor}=="046d"
ATTRS{bMaxPower}==" 98mA"
ATTRS{bmAttributes}=="a0"
ATTRS{bConfigurationValue}=="1"
ATTRS{bNumInterfaces}==" 1"
ATTRS{configuration}==""
ATTRS{dev}=="189:130"
looking at parent device '/devices/pci0000:00/0000:00:0c.0/usb2':
KERNELS=="usb2"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{serial}=="0000:00:0c.0"
ATTRS{product}=="UHCI Host Controller"
ATTRS{manufacturer}=="Linux 2.6.22-git uhci_hcd"
ATTRS{quirks}=="0x0"
ATTRS{maxchild}=="2"
ATTRS{version}==" 1.10"
ATTRS{devnum}=="1"
ATTRS{busnum}=="2"
ATTRS{speed}=="12"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{bNumConfigurations}=="1"
ATTRS{bDeviceProtocol}=="00"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceClass}=="09"
ATTRS{bcdDevice}=="0206"
ATTRS{idProduct}=="0000"
ATTRS{idVendor}=="0000"
ATTRS{bMaxPower}==" 0mA"
ATTRS{bmAttributes}=="e0"
ATTRS{bConfigurationValue}=="1"
ATTRS{bNumInterfaces}==" 1"
ATTRS{configuration}==""
ATTRS{dev}=="189:128"
looking at parent device '/devices/pci0000:00/0000:00:0c.0':
KERNELS=="0000:00:0c.0"
SUBSYSTEMS=="pci"
DRIVERS=="uhci_hcd"
ATTRS{msi_bus}==""
ATTRS{broken_parity_status}=="0"
ATTRS{enable}=="1"
ATTRS{modalias}=="pci:v00001106d00003038sv00001106sd00003038bc0Csc03i00"
ATTRS{local_cpus}=="1"
ATTRS{irq}=="11"
ATTRS{class}=="0x0c0300"
ATTRS{subsystem_device}=="0x3038"
ATTRS{subsystem_vendor}=="0x1106"
ATTRS{device}=="0x3038"
ATTRS{vendor}=="0x1106"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
ATTRS{uevent}==""
I'm sure this only output the first two sections for the non-working kernel, but the "device" symlink
existed in /class/input/input3/:
looking at device '/class/input/event3':
KERNEL=="event3"
SUBSYSTEM=="input"
DRIVER==""
ATTR{dev}=="13:67"
looking at device '/class/input/input3':
KERNEL=="input3"
SUBSYSTEM=="input"
DRIVER==""
ATTR{uniq}==""
ATTR{phys}=="isa0060/serio0/input0"
ATTR{name}=="AT Translated Set 2 keyboard"
looking at parent device '/devices/platform/i8042/serio0':
KERNELS=="serio0"
SUBSYSTEMS=="serio"
DRIVERS=="atkbd"
ATTRS{err_count}=="0"
ATTRS{softraw}=="1"
ATTRS{softrepeat}=="0"
ATTRS{set}=="2"
ATTRS{scroll}=="0"
ATTRS{extra}=="0"
ATTRS{bind_mode}=="auto"
ATTRS{modalias}=="serio:ty06pr00id00ex00"
ATTRS{description}=="i8042 KBD port"
looking at parent device '/devices/platform/i8042':
KERNELS=="i8042"
SUBSYSTEMS=="platform"
DRIVERS=="i8042"
ATTRS{modalias}=="i8042"
ATTRS{uevent}==""
looking at parent device '/devices/platform':
KERNELS=="platform"
SUBSYSTEMS==""
DRIVERS==""
ATTRS{uevent}==""
--
Simon Arlott
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists