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]

Message-ID: <20080327120011.GA5296@deepthought>
Date:	Thu, 27 Mar 2008 12:00:11 +0000
From:	Ken Moffat <zarniwhoop@...world.com>
To:	Jean Delvare <khali@...ux-fr.org>
Cc:	Trent Piepho <xyzzy@...akeasy.org>,
	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 Thu, Mar 27, 2008 at 09:26:17AM +0100, Jean Delvare wrote:
> 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.
> 
 I was going to delay replying, because I had nothing to report -
tried changing the interesting differences in the 64-bit .config
where it looked as if I had strayed from what is in the current
defconfig, no change.  Tried removing radeonfb (oh, the horrible
screen size of 80x25!), no change.  I haven't looked in detail at
drivers.

 For Trent: if I use the ('bad') system as normal, log out to gdm,
then log in again it is fine.  That involves the screen going black
and then gdm restarts X, paints the background and puts up a window.
It's only attempts to shut down or restart (reboot) which dismiss the
gdm dialog window but leave the background in place - on 'good'
kernels, the screen goes black and then the console messages appear
as soon as I click the confirm or ok or whatever button.

 I'm on xorg-7.3 on this system with xorg-server-1.4.0.90 and
xf86-video-ati ('ati') - until yesterday evening I was still using
6.7.196, then I upgraded to 6.8.0 but that too changed nothing.

 I'll try -rc7, just in case, then I'll see if I can change the
32-bit config to provoke the problem.  I see debian users have been
hitting a race with gdm, but this isn't debian (it's all compiled
from source) and I do have dbus-1.1.2 and dbus-glib-0.74 installed.

 Thanks for the suggestions.

Ken
-- 
das eine Mal als Tragödie, das andere Mal als Farce
--
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/