Re: Bug#603767: gdm: starts on v8 instead of vt7
On Thu, Nov 18, 2010 at 11:41:37AM +1100, dave b wrote: So what's kind of why i asked about how you were trying to find the bug. Don't tell me to search through lots of C code point it out! I don't have time for that and you seemed to know more! Please calm down and don't shout at me. I'm not willing to be treated this way. I don't have time for that. I never told you to search through lots of C code, neither do I know more. Besides my ability to successfully reproduce this on 2 systems with different hardware all I have are dark memories and wild guesses. I know the issue exists, I know it's nothing really new, and I know that all I have to do to work around it is to avoid GDM restarts. I never tried really hard to track it down, I just never wanted to spend the time it would take. This thread showed up on debian-devel@ and I just added my 2 cents in the hope that somebody probably could gain some ideas from it. Regarding the wild guesses: I personally somehow believe that any of the Gnome daemons transparently started in the background of Gnome applications causes this permanent VT allocation. As I said - it's nothing more than a wild guess - a gut instinct if you like. I cannot prove it. Of course, I already tried to find processes lingering around after stopping GDM - with no success. An idea to trace this down would be to track the processes which increase/decrease the tty usage count in the kernel. I have no idea if this is already possible with the current kernel infrastructure or how, but I'd be willing to run patched kernels to track it. We so then the question is what happens if it is 'busy' and we attempt to use it anyways ;) ? I don't think this should be the way to choose. I would personally prefer solving the cause over working around the result. regards Mario -- If you think technology can solve your problems you don't understand technology and you don't understand your problems. -- Bruce Schneier signature.asc Description: Digital signature
Re: Bug#603767: gdm: starts on v8 instead of vt7
Salvo Tomaselli tipos...@tiscali.it wrote: Well, to me, it does indeed appear to be a GDM bug: I can not reproduce this permanent VT allocation with either KDM, XDM or startx. The issue It happens to me with kdm. Before or after you logged in to a session? Is it reproducible for you by just restarting kdm without being logged in through it before? regards Mario -- Sique Huch? 802.1q? Was sucht das denn hier? Wie kommt das ans TAGgeslicht? -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrniea6dd.9qh.mario.ho...@darkside.dyn.samba-tng.org
Re: Bug#603767: gdm: starts on v8 instead of vt7
On 18 November 2010 23:14, Mario 'BitKoenig' Holbe mario.ho...@tu-ilmenau.de wrote: On Thu, Nov 18, 2010 at 11:41:37AM +1100, dave b wrote: So what's kind of why i asked about how you were trying to find the bug. Don't tell me to search through lots of C code point it out! I don't have time for that and you seemed to know more! Please calm down and don't shout at me. I'm not willing to be treated this way. I don't have time for that. Sorry what? I think email isn't a very good medium and you misunderstood me :/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktim0sg0rsiwjhq4kcwfw+5auiire4dztzvk45...@mail.gmail.com
Re: Bug#603767: gdm: starts on v8 instead of vt7
reassign 603767 general thanks Le mercredi 17 novembre 2010 à 13:47 +1100, david b a écrit : After upgrading from lenny to squeeze, gdm starts on vt8 always (even after restarting it). It should start on vt7 as this is the expected behaviour. I noticed this happens often to me too, and I can assure you it’s not a GDM bug. The Linux VT interface wrongly reports vt7 as being in use, before gdm is even started. It does not happen on all systems, so it might be related to KMS - for example it happens with my radeon-based system. Which graphics hardware are you using? Cheers, -- .''`. : :' : “You would need to ask a lawyer if you don't know `. `' that a handshake of course makes a valid contract.” `--- J???rg Schilling -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1289982974.14876.4.ca...@meh
Processed: Re: Bug#603767: gdm: starts on v8 instead of vt7
Processing commands for cont...@bugs.debian.org: reassign 603767 general Bug #603767 [gdm] gdm: starts on v8 instead of vt7 Bug reassigned from package 'gdm' to 'general'. thanks Stopping processing here. Please contact me if you need assistance. -- 603767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603767 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.128998298225711.transcr...@bugs.debian.org
Re: Bug#603767: gdm: starts on v8 instead of vt7
I noticed this happens often to me too, and I can assure you it’s not a GDM bug. The Linux VT interface wrongly reports vt7 as being in use, before gdm is even started. It does not happen on all systems, so it might be related to KMS - for example it happens with my radeon-based system. Which graphics hardware are you using? Oh snap! radeon with KMS. So this is interesting then. So it didn't happen when I rebooted just then. That is I now have vt7 working. Actually imho this is an xorg or gdm bug. Because I was using kvm, the new xorg (from squeeze well a slightly older version) and the same kernel -- 2.6.36 on debian lenny without this problem. So I think it may not be a kernel bug. What makes you think it is a kernel bug? -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlkti=sbm0_ss9wc6npokubnefw3rflwv0tc4ev-...@mail.gmail.com
Bug#603767: gdm: starts on v8 instead of vt7
On Wed, Nov 17, 2010 at 09:36:14AM +0100, Josselin Mouette wrote: Le mercredi 17 novembre 2010 à 13:47 +1100, david b a écrit : After upgrading from lenny to squeeze, gdm starts on vt8 always (even after restarting it). It should start on vt7 as this is the expected behaviour. I noticed this happens often to me too, and I can assure you it’s not a GDM bug. The Linux VT interface wrongly reports vt7 as being in use, before gdm is even started. It does not happen on all systems, so it might be related to KMS - for example it happens with my radeon-based system. I can confirm that a gdm3 restart might lead to either one of vt[789] with no specific rule. I had some issues to track down which needed several restarts and I simply tired which console was finally used. I have not made any stats but at most times it was on vt8 but vt9 happened as well and also I once found it back on vt7. Which graphics hardware are you using? Intel based laptop. Hope this helps Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101117085646.gb12...@an3as.eu
Bug#603767: gdm: starts on v8 instead of vt7
I am using gdm and not gdm3. If you can give me more details as to why you think it is a kernel bug that would be good ^ ^ (also the ordering of this bug report on the website rather weird...) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktin1nbkd3esv7gnqv4hkj0ug=vu9u2b-pp2jl...@mail.gmail.com
Re: Bug#603767: gdm: starts on v8 instead of vt7
On Wed, Nov 17, 2010 at 09:36:14AM +0100, Josselin Mouette wrote: Le mercredi 17 novembre 2010 à 13:47 +1100, david b a écrit : After upgrading from lenny to squeeze, gdm starts on vt8 always (even after restarting it). It should start on vt7 as this is the expected I noticed this happens often to me too, and I can assure you it???s not a GDM bug. The Linux VT interface wrongly reports vt7 as being in use, before gdm is even started. Well, to me, it does indeed appear to be a GDM bug: I can not reproduce this permanent VT allocation with either KDM, XDM or startx. The issue does only show up with GDM. And it does never show up when starting GDM the first time after boot, GDM needs to be stopped and started again for the issue to show up here on my systems. It does not happen on all systems, so it might be related to KMS - for example it happens with my radeon-based Which graphics hardware are you using? I can reproduce this on Intel graphics (KMS) and VIA Chrome graphics (no KMS, afaik). regards Mario -- The secret that the NSA could read the Iranian secrets was more important than any specific Iranian secrets that the NSA could read. -- Bruce Schneier signature.asc Description: Digital signature
Re: Bug#603767: gdm: starts on v8 instead of vt7
Well, to me, it does indeed appear to be a GDM bug: I can not reproduce this permanent VT allocation with either KDM, XDM or startx. The issue does only show up with GDM. And it does never show up when starting GDM the first time after boot, GDM needs to be stopped and started again for the issue to show up here on my systems. It happens to me with kdm. I am using intel with KMS. -- Salvo Tomaselli signature.asc Description: This is a digitally signed message part.
Re: Bug#603767: gdm: starts on v8 instead of vt7
Le mercredi 17 novembre 2010 à 17:15 +0100, Mario 'BitKoenig' Holbe a
écrit :
Well, to me, it does indeed appear to be a GDM bug: I can not reproduce
this permanent VT allocation with either KDM, XDM or startx. The issue
does only show up with GDM. And it does never show up when starting GDM
the first time after boot, GDM needs to be stopped and started again for
the issue to show up here on my systems.
Try the attached C code, it will show you what the kernel says, which is
what GDM bases its decisions upon.
The VT allocation code has not changed a single bit in gdm between the
lenny and squeeze versions. In gdm3 a very similar code is used, which
is why both behave the same in squeeze.
--
.''`.
: :' : “You would need to ask a lawyer if you don't know
`. `' that a handshake of course makes a valid contract.”
`--- J???rg Schilling
#include sys/types.h
#include sys/stat.h
#include fcntl.h
#include sys/ioctl.h
#include stdio.h
#include linux/vt.h
int main (int argc, char ** argv)
{
int fd,i;
struct vt_stat vtstat;
fd = open (/dev/tty0, O_WRONLY|O_NOCTTY, 0);
ioctl (fd, VT_GETSTATE, vtstat);
for (i=1; i12; i++) {
printf(tty%i %s\n, i, vtstat.v_state(1i)?busy:free);
}
return 0;
}
Re: Bug#603767: gdm: starts on v8 instead of vt7
On Wed, Nov 17, 2010 at 06:01:53PM +0100, Josselin Mouette wrote: Le mercredi 17 novembre 2010 à 17:15 +0100, Mario 'BitKoenig' Holbe a écrit : Well, to me, it does indeed appear to be a GDM bug: I can not reproduce this permanent VT allocation with either KDM, XDM or startx. The issue does only show up with GDM. And it does never show up when starting GDM the first time after boot, GDM needs to be stopped and started again for the issue to show up here on my systems. Try the attached C code, it will show you what the kernel says, which is what GDM bases its decisions upon. Well, as I already said in my previous mail (using deallocvt there), it says busy... I started on a fresh booted system, GDM running (on vt7), switched back to vt1 and logged in as root: r...@darkside:~# deallocvt 7 VT_DISALLOCATE: Device or resource busy deallocvt: could not deallocate console 7 r...@darkside:~# /tmp/vtmap tty1 busy tty2 busy tty3 busy tty4 busy tty5 busy tty6 busy tty7 busy tty8 free tty9 free tty10 free tty11 free r...@darkside:~# /etc/init.d/gdm3 stop Stopping GNOME Display Manager: gdm3. r...@darkside:~# /tmp/vtmap tty1 busy tty2 busy tty3 busy tty4 busy tty5 busy tty6 busy tty7 busy tty8 free tty9 free tty10 free tty11 free r...@darkside:~# deallocvt 7 VT_DISALLOCATE: Device or resource busy deallocvt: could not deallocate console 7 r...@darkside:~# Before stopping GDM, tty7 is busy as expected. After stopping GDM, tty7 is still busy. The VT allocation code has not changed a single bit in gdm between the lenny and squeeze versions. In gdm3 a very similar code is used, which is why both behave the same in squeeze. Well, it's probably not a direct GDM bug but some bug in the Gnome backend? I believe to remember for such permanent VT allocation a while ago when I didn't use any display manager at all (but startx and FVWM as window manager) triggered by running some Gnome application(s). I just cannot currently find such an application that would trigger it. regards Mario -- It is a capital mistake to theorize before one has data. Insensibly one begins to twist facts to suit theories instead of theories to suit facts. -- Sherlock Holmes by Arthur Conan Doyle signature.asc Description: Digital signature
Re: Bug#603767: gdm: starts on v8 instead of vt7
So what's kind of why i asked about how you were trying to find the bug. Don't tell me to search through lots of C code point it out! I don't have time for that and you seemed to know more! We so then the question is what happens if it is 'busy' and we attempt to use it anyways ;) ? -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlkti=3sycu_xccbc=gtvvym8xo8omrq4ko3rus=...@mail.gmail.com
Re: Bug#603767: gdm: starts on v8 instead of vt7
This appears to be a duplicate of 596700. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1758119783.480227.1290049344906.javamail.r...@md01.wow.synacor.com
