Upon invoking KDB from command line <esc>KDB, kdb crashes. Here is what I
get: (This only happens when invoked by keyboard, any thoughts why?)
=================================
[ INFO: inconsistent lock state ]
2.6.22 #9
---------------------------------
inconsistent {hardirq-on-W} -> {in-hardirq-W} usage.
swapper/0 [HC1[1]:SC0[0]:HE0:SE1] takes:
(kdb_printf_lock){+-..}, at: [<c01e4949>] kdb_printf+0x179/0x300
{hardirq-on-W} state was registered at:
[<c0135be3>] __lock_acquire+0x4f3/0xbb0
[<c0136751>] lock_acquire+0x61/0x80
[<c031ba3c>] _spin_lock+0x2c/0x40
[<c01e4949>] kdb_printf+0x179/0x300
[<c0409503>] kdb_cmd_init+0x43/0xa0
[<c04095b6>] kdb_init+0x56/0xe0
[<c03f8a15>] start_kernel+0x175/0x290
[<00000000>] 0x0
[<ffffffff>] 0xffffffff
irq event stamp: 506284
hardirqs last enabled at (506283): [<c0100a14>] default_idle+0x44/0x60
hardirqs last disabled at (506284): [<c0102cb4>] common_interrupt+0x24/0x40
softirqs last enabled at (506280): [<c011d673>] __do_softirq+0xa3/0xc0
softirqs last disabled at (506273): [<c011d6d6>] do_softirq+0x46/0x50
other info that might help us debug this:
2 locks held by swapper/0:
#0: (&irq_lists[i].lock){++..}, at: [<c020da4a>]
serial8250_interrupt+0x2a/0x150
#1: (&port_lock_key){++..}, at: [<c020da93>]
serial8250_interrupt+0x73/0x150
stack backtrace:
[<c0102faa>] show_trace_log_lvl+0x1a/0x30
[<c0102fd2>] show_trace+0x12/0x20
[<c01030f5>] dump_stack+0x15/0x20
[<c01348f3>] print_usage_bug+0x153/0x170
[<c0134e8f>] mark_lock+0x57f/0x590
[<c0135d51>] __lock_acquire+0x661/0xbb0
[<c0136751>] lock_acquire+0x61/0x80
[<c031ba3c>] _spin_lock+0x2c/0x40
[<c01e4949>] kdb_printf+0x179/0x300
[<c01e072c>] kdb_local+0x6c/0x650
[<c01e0e13>] kdb_main_loop+0x93/0x1d0
[<c0266736>] kdba_main_loop+0x36/0x50
[<c01e12c6>] kdb+0x356/0x900
[<c020d73b>] receive_chars+0x28b/0x330
[<c020db64>] serial8250_interrupt+0x144/0x150
[<c0140278>] handle_IRQ_event+0x28/0x60
[<c01413c5>] handle_level_irq+0x65/0xe0
[<c0104713>] do_IRQ+0x43/0xa0
[<c0102cbe>] common_interrupt+0x2e/0x40
[<c0100a9a>] cpu_idle+0x5a/0x70
[<c0318ded>] rest_init+0x3d/0x40
[<c03f8a8f>] start_kernel+0x1ef/0x290
[<00000000>] 0x0
=======================
Regards, Hasan R.
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
> Scott Lurndal
> Sent: Thursday, July 17, 2008 4:32 PM
> To: Hasan Rashid; Keith Owens
> Cc: Jay Lan; [email protected]
> Subject: RE: kdb has no working console and has switched itself off
>
> it is <esc>KDB now instead of ctrl-a.
>
>
> scott
>
> -----Original Message-----
> From: Hasan Rashid [mailto:[EMAIL PROTECTED]
> Sent: Thu 7/17/2008 4:26 PM
> To: 'Keith Owens'
> Cc: Scott Lurndal; 'Jay Lan'; [email protected]
> Subject: RE: kdb has no working console and has switched itself off
>
> Keith,
> I replaced the boot arguments to (uart) what you see now.
> Kernel command line: auto BOOT_IMAGE=kiCkaSs ro root=301
> console=ttyS0,19200n8 console=uart,io,0x3f8,19200n8 reboot=hard
> hdb=noprobe
> hdc=noprobe hdd=noprobe
> ide_setup: hdb=noprobe
> ide_setup: hdc=noprobe
> ide_setup: hdd=noprobe
> Initializing CPU#0
> Early serial console at I/O port 0x3f8 (options '19200n8')
> kdb version 4.4 by Keith Owens, Scott Lurndal. Copyright SGI, All Rights
> Reserved
> kdb_cmd[0]: defcmd archkdb "" "First line arch debugging"
> kdb_cmd[7]: defcmd archkdbcpu "" "archkdb with only tasks on cpus"
> kdb_cmd[14]: defcmd archkdbshort "" "archkdb with less detailed backtrace"
> kdb_cmd[21]: defcmd archkdbcommon "" "Common arch debugging"
>
> Kdb gets initialized and setup with early console detection. Now when I
> press CTRL+A nothing happens. How do I invoke kdb prompt?
>
> TIA!
>
> Regards, Hasan R.
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
> Of
> > Keith Owens
> > Sent: Thursday, July 17, 2008 2:48 PM
> > To: Hasan Rashid
> > Cc: 'Scott Lurndal'; 'Jay Lan'; [email protected]
> > Subject: Re: kdb has no working console and has switched itself off
> >
> > "Hasan Rashid" (on Thu, 17 Jul 2008 13:34:30 -0700) wrote:
> > >Scott,
> > >
> > >I compiled my kernel with the following:
> > >
> > ># Hardware I/O ports
> > >#
> > >CONFIG_SERIO=y
> > >CONFIG_SERIO_SERPORT=y
> > >
> > >#
> > ># Character devices
> > >#
> > ># CONFIG_VT is not set
> > ># CONFIG_SERIAL_NONSTANDARD is not set
> > >
> > >#
> > ># Serial drivers
> > >#
> > >CONFIG_SERIAL_8250=y
> > >CONFIG_SERIAL_8250_CONSOLE=y
> > >CONFIG_SERIAL_8250_PCI=y
> > >CONFIG_SERIAL_8250_NR_UARTS=1
> > >CONFIG_SERIAL_8250_RUNTIME_UARTS=1
> > ># CONFIG_SERIAL_8250_EXTENDED is not set
> > >
> > ># Non-8250 serial port support
> > >#
> > >CONFIG_SERIAL_CORE=y
> > >CONFIG_SERIAL_CORE_CONSOLE=y
> > >CONFIG_UNIX98_PTYS=y
> > >CONFIG_LEGACY_PTYS=y
> > >CONFIG_LEGACY_PTY_COUNT=256
> > >
> > >> -----Original Message-----
> > >> From: Scott Lurndal [mailto:[EMAIL PROTECTED]
> > >> Sent: Thursday, July 17, 2008 1:06 PM
> > >> To: Hasan Rashid
> > >> Cc: 'Jay Lan'; [email protected]
> > >> Subject: Re: kdb has no working console and has switched itself off
> > >>
> > >> On Thu, Jul 17, 2008 at 12:47:32PM -0700, Hasan Rashid wrote:
> > >> > This is only with the 2.6.22.19 kernel. I have a similar device
> (WRAP
> > >> board)
> > >> > with the same setup, just a serial port connected to my computer
> and
> > KDB
> > >> > works just fine on that.
> > >> >
> > >> > ....
> > >> > .....
> > >> > kdb: Initialization failed - no console. kdb is disabled.
> > >> > kdb version 4.4 by Keith Owens, Scott Lurndal. Copyright SGI, All
> > Rights
> > >>
> > >> Did you build your 2.6.22.19 with CONFIG_SERIAL_CONSOLE,
> > >> CONFIG_SERIAL_8250_CONSOLE or CONFIG_SERIAL_CORE_CONSOLE?
> >
> > Your serial console is not being detected early enough (or not at all).
> > You might need boot parameters console=ttyS0[,options] or
> > console=uart,io,<addr>[,options] to ensure that the serial console is
> > detected before kdb starts. See linux/Documentation/kernel-
> > parameters.txt.
> > There was a change to the kernel about a year ago to avoid probing
> > non-existent serial hardware. That change avoided errors on some
> > hardware, but unfortunately required extra boot parameters for early
> > console bringup.
> >
> > ---------------------------
> > Use http://oss.sgi.com/ecartis to modify your settings or to
> unsubscribe.
>
>
>
> ---------------------------
> Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.
---------------------------
Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.
