mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: jmerkey@wolfmountaingroup.com
To: jmerkey@wolfmountaingroup.com
Cc: "Parag Warudkar" <parag.warudkar@gmail.com>,
	jmerkey@wolfmountaingroup.com,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] mdb-2.6.27-rc2-ia32-08-07-08.patch
Date: Fri, 8 Aug 2008 07:23:15 -0600 (MDT)	[thread overview]
Message-ID: <36420.166.70.238.45.1218201795.squirrel@webmail.wolfmountaingroup.com> (raw)
In-Reply-To: <37357.166.70.238.45.1218201115.squirrel@webmail.wolfmountaingroup.com >

>> Jeff,
>>
>> This definitely looks interesting and it even worked for me - breaking
>> in couple of times, trying various commands and resuming back to X all
>> works. Never tried a kernel debugger before but most things were
>> obvious after I figured out that I need to be on the VT to be able to
>> press break and be dropped into the debugger.
>>
>> That said, it triggers soft lockups on all the suspended CPUs - not a
>> big deal and probably expected, but I guess that can be cured by
>> touching the soft lockup watch dog or something?
>
> Yep.
>
> It does with this kprobes interface, I noticed it last night.  I will run
> this down.  I am touching the watchdog in the keyboard handler.
>
> Jeff


Reproduced it.   It just spits out the noisy message but the system
continues and the processors resume running.  This is is an esoteric
issue, but I will run it down.  It does not happen on kernel versions
prior to 2.6.26.

Jeff

>
>>
>> Thanks
>>
>> Parag
>>
>
>
>



  parent reply	other threads:[~2008-08-08 13:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-08  4:33 Parag Warudkar
2008-08-08 13:11 ` jmerkey
     [not found]   ` <37357.166.70.238.45.1218201115.squirrel@webmail.wolfmountaingroup.com >
2008-08-08 13:23     ` jmerkey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-08-07 14:29 jmerkey
2008-08-07 15:49 ` Stefan Richter
2008-08-07 15:59   ` Stefan Richter
2008-08-07 15:56     ` jmerkey
2008-08-07 16:46       ` Stefan Richter
2008-08-07 16:33         ` jmerkey
2008-08-07 17:19           ` Stefan Richter
2008-08-07 17:33             ` Stefan Richter
2008-08-07 17:52               ` jmerkey
2008-08-07 17:52             ` jmerkey
2008-08-07 16:04   ` jmerkey
2008-08-09  5:07   ` Jeremy Fitzhardinge
2008-08-09  8:04     ` Stefan Richter
2008-08-09 14:44       ` jmerkey
2008-08-08  2:18 ` Parag Warudkar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=36420.166.70.238.45.1218201795.squirrel@webmail.wolfmountaingroup.com \
    --to=jmerkey@wolfmountaingroup.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=parag.warudkar@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®