linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Sergey Senozhatsky <sergey.senozhatsky@mail.by>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Kernel Testers List <kernel-testers@vger.kernel.org>
Subject: Re: [Bug #13522] BUG: scheduling while atomic
Date: Mon, 29 Jun 2009 22:15:09 -0700	[thread overview]
Message-ID: <20090629221509.1d307184@infradead.org> (raw)
In-Reply-To: <20090629162853.GB3461@localdomain.by>

On Mon, 29 Jun 2009 19:28:53 +0300
Sergey Senozhatsky <sergey.senozhatsky@mail.by> wrote:

> On (06/29/09 15:41), Alan Cox wrote:
> > > This message has been generated automatically as a part of a
> > > report of recent regressions.
> > > 
> > > The following bug entry is on the current list of known
> > > regressions from 2.6.30.  Please verify if it still should be
> > > listed and let me know (either way).
> > 
> > Yes although getting people seeing to test with might_sleep()
> > checks in the tty layer demonstrate the tty layer isn't calling
> > into ppp with irqs disabled when it shouldn't so I'm at a loss as
> > to whether this is a network bug, a scheduler bug or something else.
> > 
> > The schedule error in __tasklet_schedule() is itself rather
> > peicular.
> > 
> 
> Hello Alan, Rafael,
> 
> BUG is still here...


can you enable CONFIG_DEBUG_INFO, and then run this through
scripts/markup_oops.pl ? With a bit of luck it'll point to the exact
code that's going wrong...


-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  parent reply	other threads:[~2009-06-30  5:14 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-28 23:51 2.6.31-rc1-git3: Reported regressions from 2.6.30 Rafael J. Wysocki
2009-06-28 23:51 ` [Bug #13522] BUG: scheduling while atomic Rafael J. Wysocki
2009-06-29 14:41   ` Alan Cox
2009-06-29 16:02     ` Sergey Senozhatsky
2009-06-29 16:28     ` Sergey Senozhatsky
2009-06-29 16:33       ` Alan Cox
2009-06-30  5:15       ` Arjan van de Ven [this message]
2009-06-30  7:20         ` Sergey Senozhatsky
2009-06-30 21:59         ` Sergey Senozhatsky
2009-06-29  0:11 ` [Bug #13610] radeon kms invalid edid data at lvds Rafael J. Wysocki
2009-06-29  0:18   ` Dave Airlie
2009-06-29 23:27     ` Rafael J. Wysocki
2009-06-29  0:11 ` [Bug #13601] Hard crash connecting via Huawei E169 + umtsmon Rafael J. Wysocki
2009-06-29  0:11 ` [Bug #13592] Root partition is not found Rafael J. Wysocki
2009-06-30 19:42   ` François Valenduc
2009-06-30 22:43     ` Rafael J. Wysocki
2009-06-29  0:11 ` [Bug #13627] Tunnel device ignores TCP/UDP traffic Rafael J. Wysocki
2009-07-01 14:34   ` Jeff Chua
2009-07-01 15:13     ` Herbert Xu
2009-07-01 16:14       ` Jeff Chua
2009-07-01 16:22         ` Herbert Xu
2009-06-29  0:11 ` [Bug #13633] [bisected] No sound on HDA Intel (ALC268) Rafael J. Wysocki
2009-06-29  2:16   ` Brian Rogers
2009-06-29 23:29     ` Rafael J. Wysocki
2009-06-29  0:11 ` [Bug #13650] Problem with alloc_arch_preferred_bootmem() on powerpc Rafael J. Wysocki
2009-06-29  0:11 ` [Bug #13643] Touchpad lost synchronization after resume from suspend to RAM Rafael J. Wysocki
2009-06-29  0:11 ` [Bug #13652] scheduling while atomic: pptpgw Rafael J. Wysocki
2009-06-29  0:11 ` [Bug #13645] NULL pointer dereference at (null) (level2_spare_pgt) Rafael J. Wysocki
2009-06-29  0:11 ` [Bug #13653] system hangs after resume from suspend to disk, mce related Rafael J. Wysocki
2009-06-29  0:44   ` Hidetoshi Seto
2009-06-29 23:30     ` Rafael J. Wysocki
2009-06-29  0:11 ` [Bug #13655] [Oops] 2.6.31-rc1: tun Rafael J. Wysocki
2009-06-29  3:44   ` Sergei Trofimovich
2009-06-29 23:31     ` Rafael J. Wysocki
2009-06-29  0:11 ` [Bug #13654] possible recursive locking detected at kmem_cache_free Rafael J. Wysocki
2009-06-29  0:11 ` [Bug #13658] parisc: multiple PCI BAR collisions Rafael J. Wysocki
2009-06-29  0:11 ` [Bug #13657] Linux-2.6.31-rc1 Fails To Recognize Some USB Disks Rafael J. Wysocki
2009-06-29  0:11 ` [Bug #13656] 2.6.31-rc1 crashes randomly on my Machine Rafael J. Wysocki
2009-06-29  0:11 ` [Bug #13659] iwlagn (4965): no wireless due to RFKILL problem Rafael J. Wysocki
2009-06-29  0:11 ` [Bug #13661] warning in smp_call_function_single while S2R Rafael J. Wysocki
2009-06-29  0:11 ` [Bug #13662] broken alpha smp build Rafael J. Wysocki
2009-06-29  0:11 ` [Bug #13666] WARNING: at mm/page_alloc.c:1743 __alloc_pages_nodemask Rafael J. Wysocki
2009-06-30  0:06   ` David Rientjes
2009-06-30  2:16     ` David Miller
2009-06-30 13:58       ` Arnaldo Carvalho de Melo
2009-06-29  0:11 ` [Bug #13665] commit 69c854817566 causes OOMs Rafael J. Wysocki
2009-06-29  0:11 ` [Bug #13667] drm: display arifacts when X.Org is stopped Rafael J. Wysocki
  -- strict thread matches above, loose matches on Subject: below --
2009-07-06 23:42 2.6.31-rc2: Reported regressions from 2.6.30 Rafael J. Wysocki
2009-07-06 23:42 ` [Bug #13522] BUG: scheduling while atomic Rafael J. Wysocki
2009-07-07 16:27   ` Sergey Senozhatsky
2009-07-07 20:35     ` Rafael J. Wysocki

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=20090629221509.1d307184@infradead.org \
    --to=arjan@infradead.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=kernel-testers@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=sergey.senozhatsky@mail.by \
    /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;
as well as URLs for NNTP newsgroup(s).