All of lore.kernel.org
 help / color / mirror / Atom feed
* Re: Kexec not working as expected from inside X
@ 2009-11-30  7:57 Bernhard Walle
  2009-11-30 14:50 ` David N. Lombard
  0 siblings, 1 reply; 4+ messages in thread
From: Bernhard Walle @ 2009-11-30  7:57 UTC (permalink / raw)
  To: Mayank Kaushik; +Cc: kexec


Mayank Kaushik schrieb:
>
> Is it something in the nvidia driver that's causing this to not work?
> Any clues on what's going wrong, or how I can debug this further?

You should attach a serial console to debug that. Is that possible on
your system. It's also possible to use a USB-to-RS232 converter on the
machine that should be debugged. However, that only works after the USB
drivers have been loaded, so much later than a real serial console.

Of course it would make sense to try without the "nvidia" driver. Just
edit your xorg.conf and replace "nvidia" with "nv". You don't have any
3D graphics then, but it's only for a test. :-)


Regards,
Bernhard






_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Kexec not working as expected from inside X
  2009-11-30  7:57 Kexec not working as expected from inside X Bernhard Walle
@ 2009-11-30 14:50 ` David N. Lombard
  2009-11-30 16:12   ` Mayank Kaushik
  0 siblings, 1 reply; 4+ messages in thread
From: David N. Lombard @ 2009-11-30 14:50 UTC (permalink / raw)
  To: Bernhard Walle; +Cc: Mayank Kaushik, kexec

On Mon, Nov 30, 2009 at 12:57:40AM -0700, Bernhard Walle wrote:
> 
> Mayank Kaushik schrieb:
> >
> > Is it something in the nvidia driver that's causing this to not work?
> > Any clues on what's going wrong, or how I can debug this further?
> 
> You should attach a serial console to debug that. Is that possible on
> your system. It's also possible to use a USB-to-RS232 converter on the
> machine that should be debugged. However, that only works after the USB
> drivers have been loaded, so much later than a real serial console.

A normal serial console will do for this particular task, but when you need
very early debugging, there's also a "USB debug" cable.  AFAICT, this is a
sole-source item from Ajays Technology and only sold at
<http://www.semiconductorstore.com/cart/pc/viewprd.asp?idProduct=12083>

See Documentation/x86/earlyprintk.txt on using the device...

It's on my XMAS wish list ;)

-- 
David N. Lombard, Intel, Irvine, CA
I do not speak for Intel Corporation; all comments are strictly my own.

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Kexec not working as expected from inside X
  2009-11-30 14:50 ` David N. Lombard
@ 2009-11-30 16:12   ` Mayank Kaushik
  0 siblings, 0 replies; 4+ messages in thread
From: Mayank Kaushik @ 2009-11-30 16:12 UTC (permalink / raw)
  To: Bernhard Walle, Mayank Kaushik, kexec


[-- Attachment #1.1: Type: text/plain, Size: 1125 bytes --]

On Mon, Nov 30, 2009 at 8:50 AM, David N. Lombard <dnlombar@ichips.intel.com
> wrote:

> On Mon, Nov 30, 2009 at 12:57:40AM -0700, Bernhard Walle wrote:
> >
> > Mayank Kaushik schrieb:
> > >
> > > Is it something in the nvidia driver that's causing this to not work?
> > > Any clues on what's going wrong, or how I can debug this further?
> >
> > You should attach a serial console to debug that. Is that possible on
> > your system. It's also possible to use a USB-to-RS232 converter on the
> > machine that should be debugged. However, that only works after the USB
> > drivers have been loaded, so much later than a real serial console.
>
> A normal serial console will do for this particular task, but when you need
> very early debugging, there's also a "USB debug" cable.  AFAICT, this is a
> sole-source item from Ajays Technology and only sold at
> <http://www.semiconductorstore.com/cart/pc/viewprd.asp?idProduct=12083>
>
> See Documentation/x86/earlyprintk.txt on using the device...
>
> It's on my XMAS wish list ;)
>

Thanks, there should be one of those lying around at work, I'll give it a
try.

thanks,
Mayank

[-- Attachment #1.2: Type: text/html, Size: 1670 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Kexec not working as expected from inside X
@ 2009-11-30  0:40 Mayank Kaushik
  0 siblings, 0 replies; 4+ messages in thread
From: Mayank Kaushik @ 2009-11-30  0:40 UTC (permalink / raw)
  To: kexec


[-- Attachment #1.1: Type: text/plain, Size: 2329 bytes --]

Hi everyone,

I'm running Fedora 8, kernel 2.6.24.3-50.fc8. I was experiencing
frequent kernel hangs, so to get to the bottom of it I setup kexec/
kdump with this kernel. I did it according to the documentation in
<kernel_src>/Documentation/
kdump/kdump.txt. I'm running Xorg with the
closed-source binary nvidia driver. I did the following:

1) Ensured that my running kernel supported kexec (as given in the
documentation above), obtained the vmlinux for it from the fedora
debug yum repos.
2) Built a new crash-dump kernel (linux-2.6.23.17-kdump).
3) Appended the following lines to my /etc/rc.sysinit:

921 echo "1" > /proc/sys/kernel/sysrq
922 savetextmode
923 # Tell kexec which kernel and ramdisk to use
924 kexec -p /usr/src/kernels/linux-2.6.23.17/vmlinux --initrd=/boot/
initrd-2.6.23.17-kdump.img --args-linux --append="root=LABEL=/ 1
irqpoll maxcpus=1"
925
926 DATE=`date +%Y-%m-%d-%T`
927 NAME=`uname -r`
928 if [ "$NAME" == "2.6.23.17-kdump" ]; then
929   echo -e "Creating crash dump..\n"
930   mkdir -p /var/crash/127.0.0.1-$DATE
931   cp /proc/vmcore /var/crash/127.0.0.1-$DATE/vmcore-incomplete
932   if [ $? == 0 ]
933   then
934       mv /var/crash/127.0.0.1-$DATE/vmcore-incomplete /var/crash/
127.0.0.1-$DATE/vmcore
935       echo -e "Done, rebooting..\n"
936       reboot -f
937   fi
938 fi

The above is supposed to dump the vmcore to my /var/crash/ directory
as soon as the kdump kernel boots after a hang. The motivation for
doing this was that I get kernel hangs while running X, and pressing
<Alt>+<Sysrq> causes the screen to get garbled when the kdump kernel
boots, so I don't have a chance of doing this manually.

I've tested the above while in runlevel 3 while I'm inside a VT,
everything works as expected (I see the kdump kernel boot up and copy
the kdump), and I can see the vmcore end up inside /var/crash/. But
when I try the same while X is running, the screen gets garbled while
the kdump kernel boots, but nothing happens! The kernel does not
reboot, and neither does it copy the vmcore to /var/crash. It is
responsive though, I can toggle the CapsLock key, but the screen is
blank.

Is it something in the nvidia driver that's causing this to not work?
Any clues on what's going wrong, or how I can debug this further?

(Please CC me in the reply, I'm not on this list)

Thanks!
-Mayank

[-- Attachment #1.2: Type: text/html, Size: 2761 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2009-11-30 16:12 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-11-30  7:57 Kexec not working as expected from inside X Bernhard Walle
2009-11-30 14:50 ` David N. Lombard
2009-11-30 16:12   ` Mayank Kaushik
  -- strict thread matches above, loose matches on Subject: below --
2009-11-30  0:40 Mayank Kaushik

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.