linux-kernel - Re: Regression (gdm no longer shuts down)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 27 Mar 2008 09:26:17 +0100
From:	Jean Delvare <khali@...ux-fr.org>
To:	Trent Piepho <xyzzy@...akeasy.org>
Cc:	Ken Moffat <zarniwhoop@...world.com>,
	Dave Airlie <airlied@...il.com>, I2C <i2c@...sensors.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: Regression (gdm no longer shuts down) - 2.4.24.x and 2.6.25

On Wed, 26 Mar 2008 18:35:10 -0700 (PDT), Trent Piepho wrote:
> On Wed, 26 Mar 2008, Jean Delvare wrote:
> > Totally unrelated, but FYI: the chip at 0x50 is an EDID EEPROM in your
> > display (which the radeonfb driver can use to switch to the correct
> > resolution / refresh rate.)
> [...]
> > any of these chips. So, the mysterious effect of unloading the
> > i2c-viapro driver can't be explained by an i2c chip driver detaching
> > from its device. So, again, I really can't see how i2c can be involved
> > in your problem.
> 
> Maybe the radeonfb driver is trying to talk to EDID EEPROMs on all I2C
> adapters it finds?  When it tries to using the i2c-viapro adapter, it
> hangs.

No, the radeonfb driver only probes for EEPROMs on (at most) its 4 own
I2C buses. It doesn't even know about the other I2C buses on the system.

Note that I am using radeonfb and i2c-viapro myself, so if there was a
conflict between both drivers, I think would know by now. I've not
experienced the problem reported by Ken. But I don't use gdm.

Note that I am using the X.org radeon driver. Ken did not tell which X
driver he was using, maybe it matters.

-- 
Jean Delvare
--
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/