Jason Wessel <[email protected]> writes:
>> I think that yes, it probably is compiled with CONFIG_SMP=y. That never
>> used to be a problem before. Is it a problem now? Strangely I used
>> the same .config to manually build the 2.2.7 kgdb git snapshot I pulled
>> down and that kernel seems to run correctly.
>
> In the kernels I have tested, it seems to boot fine with CONFIG_SMP on
> or off. The extended patch series does initialize the exception
> handlers earlier than without the extended patch series. It is possible
> that there may be additional logic added by the Fedora Kernel vs the
> kernel.org kernel which is what kgdb and the extended kgdb patch set is
> regression tested with.
Well, I decided to ignore the Fedora kernel and just build your snapshot
kernel. That boots. Unfortunately I still can't get it to work like
the old kgdb -- I still can't get the kernel printk output messages
through kgdb like I used to. But I need those in order to debug this
bootup problem I'm having.
I'm currently booting with:
kgdb8250=ttyS0,115200 kgdbwait kgdbcon=ttyS0,115200
What am I missing to get the printk output to kgdb like I used to?
> Jason.
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[email protected] PGP key available
------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations
Conference from O'Reilly Media. Velocity features a full day of
expert-led, hands-on workshops and two days of sessions from industry
leaders in dedicated Performance & Operations tracks. Use code vel09scf
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
_______________________________________________
Kgdb-bugreport mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
