Bug#398962: [2.6.18] Platform devices incorrectly provide $MODALIAS?

2006-12-12 Thread Andreas Barth 
severity 398962 important
thanks

* Joey Hess ([EMAIL PROTECTED]) [061127 12:13]:
 Frans Pop wrote:
  He has suggested working around this by excluding loading drivers for 
  platform devices in udev. However, Sven Luther noted that e.g. the 
  Pegasos marvell gigabit ethernet port is a platform device for which the 
  driver should be loaded.
 
 udev 0.103-1 works around the problem as follows:
 
 # this driver is broken and should not be loaded automatically (see #398962)
 SUBSYSTEM==platform, ENV{MODALIAS}==i82365, GOTO=hotplug_driver_loaded
 
 So at least for the Pegasos marvell gigabit ethernet, the module will still
 load. I don't know if it or other platform modules will still perhaps have
 problems due to this bug.
 
 
 Once the new udev reaches testing, I wouldn't consider this bug as RC
 anymore, unless new problems come to light with other platform devices.

  udev |   udev |0.103-1 |   testing | source, alpha, amd64, 
arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc

downgrading to important now.


Cheers,
Andi
-- 
  http://home.arcor.de/andreas-barth/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#398962: [2.6.18] Platform devices incorrectly provide $MODALIAS?

2006-11-28 Thread Kay Sievers 
On Tue, 2006-11-28 at 08:12 +0100, Bastian Blank wrote:
 On Mon, Nov 27, 2006 at 03:45:36PM +0100, Kay Sievers wrote:
 For now you can just
  blacklist all platform events like Marco already suggested.
 
 Nope. modprobe don't have the knowledge that this is an alias.

Exactly, that's the root of the problem. But it isn't what Marco put in
the Debian package, and I was referring to.

Kay



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#398962: [2.6.18] Platform devices incorrectly provide $MODALIAS?

2006-11-27 Thread Kay Sievers 

On 11/25/06, Frans Pop [EMAIL PROTECTED] wrote:

In Debian we are currently seeing some problems with drivers that are
repeatedly loaded unsuccessfully:
kernel: Intel ISA PCIC probe: not found.
FATAL: Error inserting i82365: no such device
kernel: Intel ISA PCIC probe: not found.
[...]

According to Marco d'Itri this could be because platform devices in
recent kernels provide $MODALIAS while they should not. So udev will
always try loading again the driver after it has been loaded.

He has suggested working around this by excluding loading drivers for
platform devices in udev. However, Sven Luther noted that e.g. the
Pegasos marvell gigabit ethernet port is a platform device for which the
driver should be loaded.

Can anyone shed some light on this and suggest a solution?


The only sane solution is to fix the kernel platform-subsystem to use
aliases instead of direct module names. In the bug you mentioned, the
platform device requests its _own_ module, the one which has just
created the device again. This misuse of modalias causes a
modprobe-loop when the init of the module fails.
The author of that code seems ignorant to the issues he creates by
doing that, but we hope to get that fixed. For now you can just
blacklist all platform events like Marco already suggested.

Kay


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#398962: [2.6.18] Platform devices incorrectly provide $MODALIAS?

2006-11-27 Thread Joey Hess 
Frans Pop wrote:
 He has suggested working around this by excluding loading drivers for 
 platform devices in udev. However, Sven Luther noted that e.g. the 
 Pegasos marvell gigabit ethernet port is a platform device for which the 
 driver should be loaded.

udev 0.103-1 works around the problem as follows:

# this driver is broken and should not be loaded automatically (see #398962)
SUBSYSTEM==platform, ENV{MODALIAS}==i82365, GOTO=hotplug_driver_loaded

So at least for the Pegasos marvell gigabit ethernet, the module will still
load. I don't know if it or other platform modules will still perhaps have
problems due to this bug.


Once the new udev reaches testing, I wouldn't consider this bug as RC
anymore, unless new problems come to light with other platform devices.

-- 
see shy jo


signature.asc
Description: Digital signature

Bug#398962: [2.6.18] Platform devices incorrectly provide $MODALIAS?

2006-11-27 Thread Bastian Blank 
On Mon, Nov 27, 2006 at 03:45:36PM +0100, Kay Sievers wrote:
For now you can just
 blacklist all platform events like Marco already suggested.

Nope. modprobe don't have the knowledge that this is an alias.

Bastian

-- 
I have never understood the female capacity to avoid a direct answer to
any question.
-- Spock, This Side of Paradise, stardate 3417.3


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#398962: [2.6.18] Platform devices incorrectly provide $MODALIAS?

2006-11-25 Thread Frans Pop 
Hi,

In Debian we are currently seeing some problems with drivers that are 
repeatedly loaded unsuccessfully:
kernel: Intel ISA PCIC probe: not found.
FATAL: Error inserting i82365: no such device
kernel: Intel ISA PCIC probe: not found.
[...]

According to Marco d'Itri this could be because platform devices in 
recent kernels provide $MODALIAS while they should not. So udev will 
always try loading again the driver after it has been loaded.

He has suggested working around this by excluding loading drivers for 
platform devices in udev. However, Sven Luther noted that e.g. the 
Pegasos marvell gigabit ethernet port is a platform device for which the 
driver should be loaded.

Can anyone shed some light on this and suggest a solution?

See http://bugs.debian.org/398962 for details.

Thanks in advance,
Frans Pop

P.S. Please keep the debian BTS CCed on replies.


pgpngVD266zoT.pgp
Description: PGP signature