* How to capture bootstrap oops?
@ 2002-09-29 23:56 cwhmlist
2002-09-30 0:03 ` Andrew Morton
0 siblings, 1 reply; 4+ messages in thread
From: cwhmlist @ 2002-09-29 23:56 UTC (permalink / raw)
To: linux-kernel
I need some help, I'm new to this. I have compliled a 2.5.39 kernel for my quad pentium pro system and it is oopsing on bootup. Unfortunently, it looks like a good portion of the oops scrolls off of the screen. Since I don't have the ability to hook up a serial terminal, how do I capture this oops so I can report it?
Thanks,
Chris
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to capture bootstrap oops?
2002-09-29 23:56 How to capture bootstrap oops? cwhmlist
@ 2002-09-30 0:03 ` Andrew Morton
2002-09-30 1:46 ` Chris Wedgwood
2002-09-30 9:21 ` bert hubert
0 siblings, 2 replies; 4+ messages in thread
From: Andrew Morton @ 2002-09-30 0:03 UTC (permalink / raw)
To: cwhmlist; +Cc: linux-kernel
cwhmlist@bellsouth.net wrote:
>
> I need some help, I'm new to this. I have compliled a 2.5.39 kernel for
> my quad pentium pro system and it is oopsing on bootup. Unfortunently,
> it looks like a good portion of the oops scrolls off of the screen. Since
> I don't have the ability to hook up a serial terminal, how do I capture
> this oops so I can report it?
This might suffice?
--- linux-2.5.39/arch/i386/kernel/traps.c Fri Sep 27 15:09:03 2002
+++ 25/arch/i386/kernel/traps.c Sun Sep 29 17:02:38 2002
@@ -292,6 +292,8 @@ void die(const char * str, struct pt_reg
handle_BUG(regs);
printk("%s: %04lx\n", str, err & 0xffff);
show_registers(regs);
+ for ( ; ; )
+ ;
bust_spinlocks(0);
spin_unlock_irq(&die_lock);
do_exit(SIGSEGV);
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to capture bootstrap oops?
2002-09-30 0:03 ` Andrew Morton
@ 2002-09-30 1:46 ` Chris Wedgwood
2002-09-30 9:21 ` bert hubert
1 sibling, 0 replies; 4+ messages in thread
From: Chris Wedgwood @ 2002-09-30 1:46 UTC (permalink / raw)
To: Andrew Morton; +Cc: cwhmlist, linux-kernel
On Sun, Sep 29, 2002 at 05:03:33PM -0700, Andrew Morton wrote:
cwhmlist@bellsouth.net wrote:
> I need some help, I'm new to this. I have compliled a 2.5.39
> kernel for my quad pentium pro system and it is oopsing on
> bootup. Unfortunently, it looks like a good portion of the oops
> scrolls off of the screen. Since I don't have the ability to
> hook up a serial terminal, how do I capture this oops so I can
> report it?
> This might suffice?
[... patch removed ...]
Or try a serial console (if you have access to such a thing).
--cw
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to capture bootstrap oops?
2002-09-30 0:03 ` Andrew Morton
2002-09-30 1:46 ` Chris Wedgwood
@ 2002-09-30 9:21 ` bert hubert
1 sibling, 0 replies; 4+ messages in thread
From: bert hubert @ 2002-09-30 9:21 UTC (permalink / raw)
To: Andrew Morton; +Cc: cwhmlist, linux-kernel
On Sun, Sep 29, 2002 at 05:03:33PM -0700, Andrew Morton wrote:
> cwhmlist@bellsouth.net wrote:
> >
> > I need some help, I'm new to this. I have compliled a 2.5.39 kernel for
> > my quad pentium pro system and it is oopsing on bootup. Unfortunently,
> > it looks like a good portion of the oops scrolls off of the screen. Since
> > I don't have the ability to hook up a serial terminal, how do I capture
> > this oops so I can report it?
>
> This might suffice?
People also like using digital cameras these days to photograph their oopses
for typing them in later :-)
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
http://www.tk the dot in .tk
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2002-09-30 9:16 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-09-29 23:56 How to capture bootstrap oops? cwhmlist
2002-09-30 0:03 ` Andrew Morton
2002-09-30 1:46 ` Chris Wedgwood
2002-09-30 9:21 ` bert hubert
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox