From: Alexey Fisher <bug-track-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org>
To: "R. J. Wysocki" <Rafal.Wysocki-/6eP1D/FSf3VItvQsEIGlw@public.gmane.org>
Cc: kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: SLAB break supsned and cpu-hotplug on SMP, using SLUB instead.
Date: Fri, 13 Jun 2008 23:22:31 +0200 [thread overview]
Message-ID: <1213392151.11059.2.camel@zwerg> (raw)
In-Reply-To: <200806132307.19393.Rafal.Wysocki-/6eP1D/FSf3VItvQsEIGlw@public.gmane.org>
Am Freitag, den 13.06.2008, 23:07 +0200 schrieb R. J. Wysocki:
> On Friday, 13 of June 2008, Alexey Fisher wrote:
> > I found that SLAB breaking supsned and cpu-hotplug on my PC. I didn't
> > get to bisect it, so i think it is just the part of SLAB. At the moment
> > i converted my kernel to SLUB and it working just fine, about 10
> > suspends and no reboot or crush ... it ist a record for my PC.
> >
> > Easy way to reproduce is to compile SLAB kernel and
> > echo 0 > /sys/devices/system/cpu/cpu1/online
> > echo 1 > /sys/devices/system/cpu/cpu1/online
> >
> > other work around to make my PC working stable are kernel options: nosmp
> > or mem=1024M
> > kernel 2.6.26-rc6-00028-gc6d8f40 #68 SMP PREEMPT
>
> Is this a regression from 2.6.25?
No. I can find this bug till 2.6.20... with 2.6.19 and 2.6.18 it getting
more unstable.
--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-06-13 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 20:39 SLAB break supsned and cpu-hotplug on SMP, using SLUB instead Alexey Fisher
2008-06-13 21:07 ` R. J. Wysocki
[not found] ` <200806132307.19393.Rafal.Wysocki-/6eP1D/FSf3VItvQsEIGlw@public.gmane.org>
2008-06-13 21:22 ` Alexey Fisher [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=1213392151.11059.2.camel@zwerg \
--to=bug-track-m18mab7tlt0ycq4ww13eyl6hyfs7nttn@public.gmane.org \
--cc=Rafal.Wysocki-/6eP1D/FSf3VItvQsEIGlw@public.gmane.org \
--cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.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