From: Soeren Sonnenburg <kernel@nn7.de>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
"Rafael J\. Wysocki" <rjw@sisk.pl>,
linux-pm@lists.linux-foundation.org, Pavel Machek <pavel@suse.cz>
Subject: Re: Can't s2ram 22-rc2 [Was: 2.6.22-rc2 BUG: at slub_def.h:77]
Date: Mon, 21 May 2007 11:55:52 +0200 [thread overview]
Message-ID: <1179741352.4980.11.camel@localhost> (raw)
In-Reply-To: <46515A7D.20003@gmail.com>
On Mon, 2007-05-21 at 10:38 +0200, Jiri Slaby wrote:
> Played with Cc list.
>
> Soeren Sonnenburg napsal(a):
> > On Mon, 2007-05-21 at 10:09 +0200, Jiri Slaby wrote:
> >> Soeren Sonnenburg napsal(a):
> >>> a regression (well I switched to slub) happens on boot...
> >
> >>> BUG: at include/linux/slub_def.h:77 kmalloc_index()
> >>> [<c0176448>] get_slab+0x1c8/0x250
> > [...]
> >> Could you try this patch:
> >> http://lkml.org/lkml/2007/5/19/171
> >
> > yes, that does fix the issue (at least I don't see the BUG: anymore on
> > boot). however I can no longer s2ram on 22rc2.
>
> Whit what kind of error or what happens?
pci_device_suspend(): usb_hcd_pci_suspend+0x0/0x170() returns -16
suspend_device(): pci_device_suspend+0x0/0x60() returns -16
Could not suspend device 0000:00:1d.0: error -16
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)
lspci/dmesg are in this mail:
http://marc.info/?l=linux-kernel&m=117973679209855&w=2
Soeren
--
Sometimes, there's a moment as you're waking, when you become aware of
the real world around you, but you're still dreaming.
next prev parent reply other threads:[~2007-05-21 9:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 6:22 2.6.22-rc2 BUG: at include/linux/slub_def.h:77 kmalloc_index() Soeren Sonnenburg
2007-05-21 8:09 ` Jiri Slaby
2007-05-21 8:34 ` Soeren Sonnenburg
2007-05-21 8:38 ` Can't s2ram 22-rc2 [Was: 2.6.22-rc2 BUG: at slub_def.h:77] Jiri Slaby
2007-05-21 9:55 ` Soeren Sonnenburg [this message]
2007-05-21 11:04 ` 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=1179741352.4980.11.camel@localhost \
--to=kernel@nn7.de \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@suse.cz \
--cc=rjw@sisk.pl \
/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).