All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.26.6-rt11: BUGs (sleeping function called from invalid context)
Date: Sat, 08 Nov 2008 09:47:38 +0100	[thread overview]
Message-ID: <1226134058.2697.1100.camel@twins> (raw)
In-Reply-To: <1226101937.7647.13.camel@localhost.localdomain>

On Fri, 2008-11-07 at 15:52 -0800, Fernando Lopez-Lezcano wrote:
> On Fri, 2008-11-07 at 22:47 +0100, Peter Zijlstra wrote:
> > On Fri, 2008-11-07 at 13:35 -0800, Fernando Lopez-Lezcano wrote:
> > > On Fri, 2008-11-07 at 20:16 +0100, Peter Zijlstra wrote:
> > > > On Fri, 2008-11-07 at 14:01 -0500, Steven Rostedt wrote:
> > > > > Peter, I think we've seen this before. It is the highmem code sleeping.
> > > > 
> > > > I've been working on an alternative kmap_atomic implementation for -rt,
> > > > the below has been build and booted but not stressed, anybody care to
> > > > give it a spin ?
> > > 
> > > I'll give it a try. Anything in particular I should try to do? Or not
> > > do? Or watch for?
> > 
> > Lots of I/O should stress the i386 highmem stuff. If all is well it
> > works, if not, crashes and splats.
> 
> Crashes and splats on boot... sorry, I don't have a way to capture the
> kernel oops (or whatever happens, I can only see the end of the
> printout)
> 
> -- Fernando
> 
> PS: things left on the screen (top to bottom):
> 
> ? speedstep_detect_processor
> ? __copy_from_user_ll_noccache_nozero
> iov_iter_copy_from_user_atomic
> ? generic_file_buffered_write
> generic_file_buffered_write
> ? avs_has_perm_noaudit
> ? __rt_spin_lock
> ? selinux_inode_need_killpriv
> ? __rt_spin_lock
> mnt_drop_write
> __generic_file_aio_write_nolock
> generic_file_aio_write
> do_sync_write
> ? __enqueue_entity
> ? autoremove_wake_function
> ? selinux_file_oermission
> ? security_file_permission
> ? do_sync_write
> vfs_write
> sys_write
> ? schedule_tail
> ? ret_from_fork
> ? thread_kernel_helper

Oh well, thanks for trying, I guess I need to go run this on real
hardware, which means finding where I left this i386 distro on the test
boxen :-)

  reply	other threads:[~2008-11-08  8:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-07 18:50 2.6.26.6-rt11: BUGs (sleeping function called from invalid context) Fernando Lopez-Lezcano
2008-11-07 19:01 ` Steven Rostedt
2008-11-07 19:16   ` Peter Zijlstra
2008-11-07 21:35     ` Fernando Lopez-Lezcano
2008-11-07 21:47       ` Peter Zijlstra
2008-11-07 23:52         ` Fernando Lopez-Lezcano
2008-11-08  8:47           ` Peter Zijlstra [this message]
2008-11-08 18:28             ` Fernando Lopez-Lezcano
2009-01-16 20:16   ` Fernando Lopez-Lezcano
2009-01-16 20:41     ` Steven Rostedt
2009-01-16 20:49     ` Steven Rostedt
2009-01-16 23:06       ` Fernando Lopez-Lezcano
2009-01-17  0:37         ` Steven Rostedt
2009-01-19 20:36           ` Fernando Lopez-Lezcano

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=1226134058.2697.1100.camel@twins \
    --to=peterz@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nando@ccrma.Stanford.EDU \
    --cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.