mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Bernd Schubert <bs@q-leap.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.23 regression: do_nanosleep will not return
Date: Mon, 8 Oct 2007 23:48:12 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.0.9999.0710082337480.25146@localhost.localdomain> (raw)
In-Reply-To: <fed93g$eq4$1@sea.gmane.org>


On Mon, 8 Oct 2007, Bernd Schubert wrote:

> Hi,
> 
> we have a system here were e.g. "sleep 1" will never finish. This is an 
> issue of 2.6.23, on all older kernel versions it did work fine.
> 
> Seems to hang in do_nanosleep() 
> 
> [  153.775792] sleep         S 0000000000000000     0  5372   5341              
> [  153.782385]  ffff81007f0a9ea8 0000000000000082 0000000000000000 0000000000008efc                                                                             
> [  153.790635]  ffff81007f0a9e48 ffffffff802447b4 ffff81007f0c3080 0000000300000000                                                                             
> [  153.798938]  ffff81007f0c39c8 ffff81007f0c37c0 000000004001d908 0000000000000000                                                                             
> [  153.806991] Call Trace:                                                      
> [  153.809937]  [<ffffffff8048e4cd>] do_nanosleep+0x42/0x75                     
> [  153.815727]  [<0000000000000001>]                                            
> [  153.819383]                                                                  
> [  153.775792] sleep         S 0000000000000000     0  5372   5341              
> 
> 
> [  330.669444] SysRq : Show Pending Timers                                      
> [  330.673552] Timer List Version: v0.3                                         
> [  330.677326] HRTIMER_MAX_CLOCK_BASES: 2                                       
> [  330.681282] now at 255011372633 nsecs                                        
> [  330.829981] active timers:                                                   
> [  330.832859]  #0: <ffff81007f0e3de8>, hrtimer_wakeup, S:01                    
> [  330.838805]  # expires at 260156346358 nsecs [in 5144973725 nsecs]           
> 
> [  337.046189] now at 261387685432 nsecs                                        
> [  337.194966] active timers:                                                   
> [  337.197834]  #0: <ffff81007f0e3de8>, hrtimer_wakeup, S:01                    
> [  337.203793]  # expires at 260156346358 nsecs [in 18446744072478212542 nsecs] 

timer already expired ---------^^^^^^^^^^^^
(~1.2 seconds)

hmm, signedness problem (only in the display) ---------^^^^^^^^^^^^^^^^^^^

Can you please put a complete system description, your .config and a boot 
log into bugzilla ?

Thanks,

	tglx


      parent reply	other threads:[~2007-10-08 21:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-08 12:50 Bernd Schubert
2007-10-08 13:20 ` Bernd Schubert
2007-10-08 14:32   ` Rik van Riel
2007-10-08 15:01     ` Bernd Schubert
2007-10-08 15:16       ` Peter Zijlstra
2007-10-08 19:23       ` Rafael J. Wysocki
2007-10-08 21:48 ` Thomas Gleixner [this message]

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=alpine.LFD.0.9999.0710082337480.25146@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=bs@q-leap.de \
    --cc=linux-kernel@vger.kernel.org \
    /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®