From: Pavel Machek <pavel@ucw.cz>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Ben Collins <ben.collins@ubuntu.com>,
kernel list <linux-kernel@vger.kernel.org>,
linux1394-devel@lists.sourceforge.net
Subject: Re: regression: fireware causes oops during system
Date: Sun, 16 Sep 2007 19:57:53 +0200 [thread overview]
Message-ID: <20070916175753.GC11983@elf.ucw.cz> (raw)
In-Reply-To: <46E6F076.5000006@s5r6.in-berlin.de>
On Tue 2007-09-11 21:45:58, Stefan Richter wrote:
> >> On Tue, 2007-09-11 at 21:00 +0200, Pavel Machek wrote:
> >>> I noticed empty suspend stopped working around 2.6.23-rc4, and it is
> >>> still present in 2.6.23-rc6.
> ...
> >>> Unsetting
> >>>
> >>> CONFIG_IEEE1394=y
> >>>
> >>> solves the problem.
> ...
>
> Between -rc3 and -rc4:
>
> ieee1394: sbp2: fix sbp2_remove_device for error cases
> a2ee3f9bbb0ce57102dad8928d54f59acdc4b8f7
> should not occur in suspend path
Plus I do not have firewire attached disk here, so sbp2 should not be
used, right?
> Between -rc1 and -rc2:
>
> ieee1394: sbp2: more correct Kconfig dependencies
> e4f8cac5e07528f7e0bc21d3682c16c9de993ecb
> unrelated
>
> ieee1394: revert "sbp2: enforce 32bit DMA mapping"
> a9c2f18800753c82c45fc13b27bdc148849bdbb2
> unrelated
>
> (not via linux1394-2.6.git)
> raw1394 __user annotation
> 5b26e64ea39e45802c5736c8261bf8a8704d212f
> unrelated
>
> So it must be something older which was somehow uncovered.
> Dmesg with the oops or/and bisection would be good.
The others look even more innocent. I wonder if this may have been
responsible?
commit 831441862956fffa17b9801db37e6ea1650b0f69
tree b0334921341f8f1734bdd3243de76d676329d21c
parent 787d2214c19bcc9b6ac48af0ce098277a801eded
author Rafael J. Wysocki <rjw@sisk.pl> Tue, 17 Jul 2007 04:03:35 -0700
committer Linus Torvalds <torvalds@woody.linux-foundation.org> Tue, 17
Jul 2007 10:23:02 -0700
Freezer: make kernel threads nonfreezable by default
Or this one?
commit 20c2df83d25c6a95affe6157a4c9cac4cf5ffaac
tree 415c4453d2b17a50abe7a3e515177e1fa337bd67
parent 64fb98fc40738ae1a98bcea9ca3145b89fb71524
author Paul Mundt <lethal@linux-sh.org> Fri, 20 Jul 2007 10:11:58
+0900
committer Paul Mundt <lethal@linux-sh.org> Fri, 20 Jul 2007 10:11:58
+0900
mm: Remove slab destructors from kmem_cache_create().
Slab destructors were no longer supported after Christoph's
c59def9f222d44bb7e2f0a559f2906191a0862d7 change. They've been
BUGs for both slab and slub, and slob never supported them
either.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2007-09-16 17:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 19:00 Pavel Machek
2007-09-11 19:08 ` Ben Collins
2007-09-11 19:29 ` Stefan Richter
2007-09-11 19:45 ` Stefan Richter
2007-09-16 17:54 ` Pavel Machek
2007-09-16 18:41 ` Stefan Richter
2007-09-16 19:52 ` Rafael J. Wysocki
2007-09-16 19:58 ` Stefan Richter
2007-09-16 20:16 ` Rafael J. Wysocki
2007-10-05 7:08 ` Pavel Machek
2007-10-05 21:28 ` Rafael J. Wysocki
2007-09-16 17:57 ` Pavel Machek [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=20070916175753.GC11983@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=ben.collins@ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
/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