Bug#278724: [(fwd): Bug#278724: [Sarge]: xserver-xfree86 freeze on errors from gv|xmms|lopster]
* Branden Robinson <branden@debian.org> [101204, 03:13]:
> On Fri, Nov 05, 2004 at 09:27:56PM +0100, Ennio-Sr wrote:
> > 2) Can you reproduce the problem with xserver-xfree86-dbg?
> >
> > ## Yes, I can, but no core file is created, despite following step by
> > ## step the instructions listed in the 'form letter'.
> > ## The only core file I could see is the /proc/kcore, which I think
> > ## you're not intered in. [read more at the bottom]
>
> Correct; we're not interested in /proc/kcore. :)
>
> I apologize for the boilerplate not being precisely applicable to your
> case.
>
> It's remotely possible you could have caused a core dump yourself by simply
> signalling the process.
>
> That is, identify the process ID of the X server and then use "kill -QUIT"
> or "kill -ABRT" on it.
>
> However, I suspect in this case that wouldn't have worked, because your
> display adapter had things hosed at the bus level.
>
> On the other hand, if that *does* work, it would be useful to know, because
> the core dump (once parsed by GDB) would tell us what function the X server
> was in when it locked up the display adapter. And that in turn might point
> in the direction of a fix.
>
> --
> G. Branden Robinson | My first priority in any attack is
Hi Branden!
I'm following up after some time to my previous answer on your last
message.
Finally I was again in a position to try again what you suggested, but
to no avail: whatever I did from my note book, the screen on my PC
remained well fixed on that frozen page showing the error I reported
before. PC's keyboard was of course completely frozen and the only
command which would be felt through the ssh connection was 'reboot' !
For what is worth I'm reporting the commands I gave:
On my PC's XF86Config-4 I put again the value 'DefaultDepth 24'
then I gave the command from root:
# startx $/which x-terminal-emulator)
and when X came on I gave the fatal
# gv pippo
The error window came out and the PC was frozen.
I connected from a notebook and killed one after another all the
processes relating to the gv command, i.e.:
# kill -QUIT proc.no. ## gv pippo
# kill -ABRT " ## xterm -class UxTerm -title uxterm -u8
# kill -ABRT " ## usr/bin/X11*X -dpi 100 -nolisten tcp
# kill -QUIT " ## bash (which will not disappear from ps aux
## list as the previous processes did)
This is the full list of what I did from my notebook:
1132 ps aux |grep root
1133 kill -QUIT 2231
1134 kill -ABRT 2231
(not found)
1135 ps aux |grep root
1136 kill -ABRT 2225
1137 ps aux |grep root
1138 kill -ABRT 2222
1139 ps aux |grep root
1140 kill -QUIT 1616
1141 ps aux |grep root
1142 ps aux |grep tty1
1143 kill -QUIT 1616
1144 ps aux |grep tty1
1145 ps aux |grep tty1 |less
1146 kill -QUIT 4616
1147 kill -QUIT 1836
1148 ps aux |grep tty1
1149 kill -ABRT 1616
1150 ps aux |grep tty1
1151 ps aux | less
1154 ps aux | grep xinit
1155 reboot
Of course, no core was produced.
Sorry I cannot be more helpful ;(
Best regards,
Ennio.
--
[Perche' usare Win$ozz (dico io) se ..."anche uno sciocco sa farlo. \\?//
Fa' qualche cosa di cui non sei capace!" (diceva Henry Miller) ] (°|°)
[Why use Win$ozz (I say) if ... "even a fool can do that. )=(
Do something you aren't good at!" (as Henry Miller used to say) ]
Reply to: