mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin Schlemmer [c]" <azarah@nosferatu.za.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.10-rc1-mm5 [u]
Date: Sat, 13 Nov 2004 23:16:33 +0200	[thread overview]
Message-ID: <1100380593.12663.1.camel@nosferatu.lan> (raw)
In-Reply-To: <1100368553.12239.3.camel@nosferatu.lan>

[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]

On Sat, 2004-11-13 at 19:55 +0200, Martin Schlemmer wrote:
> On Thu, 2004-11-11 at 01:23 -0800, Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.10-rc1/2.6.10-rc1-mm5/
> > 
> > 
> > - Various updates to various things.  Nothing really stands out.
> > 
> > - Let me be the first to report this:
> > 
> > 	*** Warning: "kgdb_irq" [drivers/serial/serial_core.ko] undefined!
> > 	*** Warning: "hotplug_path" [drivers/acpi/container.ko] undefined!
> > 
> > 
> > 
> 
> I want to imagine there is some reason why some threading apps will have
> issues?  I have since rc1-mm4 issues with evolution - some threads do
> not seem to come out of sleep or get running time for some reason.
> Unfortunately I cannot find the thread again.  Is there a patch I can
> apply/revert to get it to work for now?
> 

I should note that if I killall -STOP and then killall -CONT all
evolution processes (evolution-data-server-1.0, evolution-alarm-notify
and evolution-2.0) it works again for a while.  The issue happens pretty
quick after I start evo ...


Thanks,

-- 
Martin Schlemmer


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-11-13 21:18 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-11  9:23 2.6.10-rc1-mm5 Andrew Morton
2004-11-11 10:09 ` 2.6.10-rc1-mm5 Magnus Damm
2004-11-11 10:11   ` 2.6.10-rc1-mm5 Andrew Morton
2004-11-11 10:24     ` 2.6.10-rc1-mm5 Magnus Damm
2004-11-11 10:45 ` 2.6.10-rc1-mm5 Brice Goglin
2004-11-11 11:00   ` 2.6.10-rc1-mm5 Stefano Rivoir
2004-11-11 11:13   ` 2.6.10-rc1-mm5 Andrew Morton
2004-11-11 11:04 ` 2.6.10-rc1-mm5 Markus Trippelsdorf
2004-11-11 11:08 ` 2.6.10-rc1-mm5 Andrew Morton
2004-11-11 21:55   ` 2.6.10-rc1-mm5 Martin J. Bligh
2004-11-11 22:14     ` 2.6.10-rc1-mm5 Andrew Morton
2004-11-12  9:27       ` 2.6.10-rc1-mm5 Jens Axboe
2004-11-11 22:41     ` 2.6.10-rc1-mm5 Andrew Morton
2004-11-12 10:50     ` [PATCH] Fix SHMEM options David Howells
2004-11-12 16:45       ` Christoph Hellwig
2004-11-11 12:11 ` 2.6.10-rc1-mm5: yenta_socket issue Rafael J. Wysocki
2004-11-11 12:21   ` Andrew Morton
2004-11-11 12:43     ` Rafael J. Wysocki
2004-11-12  3:55   ` Rusty Russell
2004-11-11 16:50 ` 2.6.10-rc1-mm5: REISER4_LARGE_KEY is still selectable Adrian Bunk
2004-11-12  7:07   ` Vladimir Saveliev
2004-11-12 13:23     ` Adrian Bunk
2004-11-12 16:16       ` DaMouse
2004-11-12 16:37       ` Vladimir Saveliev
2004-11-12 17:15         ` Adrian Bunk
2004-12-11 17:25   ` Hans Reiser
2004-11-11 21:45 ` Reiser{3,4}: problem with the copyright statement Adrian Bunk
2004-11-11 21:59   ` Linus Torvalds
2004-11-12 16:47     ` Christoph Hellwig
2004-11-12 17:06       ` Christoph Hellwig
2004-11-12 17:11         ` Adrian Bunk
2004-11-12 17:13           ` Christoph Hellwig
2004-11-12 19:33             ` Hans Reiser
2004-11-11 22:51   ` Stephen Pollei
2004-11-12  2:08     ` Zan Lynx
2004-11-11 23:28 ` 2.6.10-rc1-mm5: reiser4: print_clog in debug.c useless? Adrian Bunk
2004-11-12  2:39 ` 2.6.10-rc1-mm5: strange fs/reiser4/linux-5_reiser4_syscall.patch Adrian Bunk
2004-11-12 14:30 ` [patch] 2.6.10-rc1-mm5: some reiser4 cleanups Adrian Bunk
2004-11-12 19:00 ` 2.6.10-rc1-mm5 Alexander Nyberg
2004-11-13  0:11 ` 2.6.10-rc1-mm5 Greg KH
2004-11-13 17:55 ` 2.6.10-rc1-mm5 [u] Martin Schlemmer [c]
2004-11-13 21:16   ` Martin Schlemmer [c] [this message]
2004-11-13 21:22     ` Andrew Morton
2004-11-13 22:19       ` Jedi/Sector One
2004-11-13 22:22       ` Martin Schlemmer [c]
2004-11-13 23:24         ` Andrew Morton
2004-11-14  0:07           ` Martin Schlemmer [c]
2004-11-14  9:10           ` Jamie Lokier

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=1100380593.12663.1.camel@nosferatu.lan \
    --to=azarah@nosferatu.za.org \
    --cc=akpm@osdl.org \
    --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

Powered by JetHome