From: Mattia Dongili <malattia@linux.it>
To: Andrew Morton <akpm@osdl.org>, Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org, reiserfs-dev@namesys.com,
linux-acpi@vger.kernel.org
Subject: Re: 2.6.15-mm2: reiser3 oops on suspend and more (bonus oops shot!)
Date: Wed, 11 Jan 2006 19:40:28 +0100 [thread overview]
Message-ID: <20060111184027.GB4735@inferi.kami.home> (raw)
In-Reply-To: <15632.83.103.117.254.1136989660.squirrel@picard.linux.it> <20060111100016.GC2574@elf.ucw.cz> <20060110170037.4a614245.akpm@osdl.org>
Hello,
I gave -mm3 a run:
On Tue, Jan 10, 2006 at 05:00:37PM -0800, Andrew Morton wrote:
> Mattia Dongili <malattia@linux.it> wrote:
[...]
> > 1- reiser3 oopsed[1] twice while suspending to ram. It seems
> > reproducible (have some activity on the fs and suspend)
>
> No significant reiser3 changes in there, so I'd be suspecting something
> else has gone haywire.
It's still there. But I caught it during normal runtime, a couple more
pictures (yes, I'm going to try to setup a netconsole):
the oops (sorry, it sucks, probably useless):
http://oioio.altervista.org/linux/dsc03136.jpg
a screen with the call traces, the keyboard was still active and sysrq
combos worked. It showed many processes stuck within reiser's log writer:
http://oioio.altervista.org/linux/dsc03138.jpg
going to revert the
> > 3- This laptop experienced 2 long stalls (20~25 sec) during boot,
> > apparently after scanning usb_storage devices and starting portmap.
umph... it's still here call traces:
http://oioio.altervista.org/linux/portmap_stall_trace1
[...]
> There's not much point in fiddling with -mm2. If git7 is OK then please
> test the next -mm and if it still fails then yes, doing a bisection would
> really help.
>
> <types madly>
>
> See http://www.zip.com.au/~akpm/linux/patches/stuff/bisecting-mm-trees.txt
give me some hours for this.
Anyway I'd like to try to revert some reiser3 changes first and see if
the oops goes (I can leave with a longer boot but I'm worried about my
root fs :))
> > 4- I'm also affected by the ACPI Misaligned resource pointer error.
still here:
# grep -e 'Jan 11.*Misaligned.*' /var/log/syslog
Jan 11 18:07:10 inferi kernel: **** SET: Misaligned resource pointer: cff4b7e2 Type 07 Len 0
Jan 11 18:07:10 inferi kernel: **** SET: Misaligned resource pointer: cff4b7e2 Type 07 Len 0
Jan 11 18:07:10 inferi kernel: **** SET: Misaligned resource pointer: cff4b2e2 Type 07 Len 0
Jan 11 18:07:10 inferi kernel: **** SET: Misaligned resource pointer: cf657902 Type 07 Len 0
Jan 11 18:07:10 inferi kernel: **** SET: Misaligned resource pointer: cf657602 Type 07 Len 0
Jan 11 18:07:10 inferi kernel: **** SET: Misaligned resource pointer: cf657402 Type 07 Len 0
Jan 11 18:07:10 inferi kernel: **** SET: Misaligned resource pointer: cf657402 Type 07 Len 0
Jan 11 18:18:53 inferi kernel: **** SET: Misaligned resource pointer: cf657d02 Type 07 Len 0
Jan 11 18:21:14 inferi kernel: **** SET: Misaligned resource pointer: cf657d02 Type 07 Len 0
DSDT and lspci can be found here if useful:
http://oioio.altervista.org/linux/DSDT.aml
http://oioio.altervista.org/linux/DSDT.dsl
http://oioio.altervista.org/linux/lspci-v
On Wed, Jan 11, 2006 at 11:00:16AM +0100, Pavel Machek wrote:
[...]
> > > 1- reiser3 oopsed[1] twice while suspending to ram. It seems
> > > reproducible (have some activity on the fs and suspend)
[...]
> Suspend to *RAM*? That really does not do anything that should kill
Sorry, it seems it has nothing to do with s2ram.
--
mattia
:wq!
next prev parent reply other threads:[~2006-01-11 18:40 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 23:55 2.6.15-mm2: reiser3 oops on suspend and more (bonus oops shot!) Mattia Dongili
2006-01-11 1:00 ` Andrew Morton
2006-01-11 10:00 ` Pavel Machek
2006-01-11 11:24 ` Mattia Dongili
2006-01-11 18:40 ` Mattia Dongili [this message]
2006-01-12 22:08 ` first bisection results in -mm3 [was: Re: 2.6.15-mm2: reiser3 oops on suspend and more (bonus oops shot!)] Mattia Dongili
2006-01-12 23:26 ` john stultz
2006-01-14 12:08 ` Mattia Dongili
2006-01-16 20:16 ` john stultz
2006-01-16 20:40 ` Mattia Dongili
2006-01-16 21:42 ` john stultz
2006-01-16 22:19 ` Andi Kleen
2006-01-16 22:41 ` john stultz
2006-01-17 16:43 ` Mattia Dongili
2006-01-17 16:45 ` Mattia Dongili
2006-01-17 0:49 ` john stultz
2006-01-17 17:49 ` Mattia Dongili
2006-01-17 19:11 ` john stultz
2006-01-17 22:49 ` Mattia Dongili
2006-01-18 10:47 ` Mattia Dongili
2006-01-24 22:27 ` john stultz
2006-01-24 23:04 ` Mattia Dongili
2006-01-24 23:48 ` john stultz
2006-01-25 0:12 ` john stultz
2006-01-25 18:12 ` Mattia Dongili
2006-01-11 10:02 ` 2.6.15-mm2: reiser3 oops on suspend and more (bonus oops shot!) Pavel Machek
2006-01-11 14:27 ` Mattia Dongili
2006-01-15 22:14 ` 2.6.15-mm3 bisection: git-xfs.patch makes reiserfs oops Mattia Dongili
2006-01-15 22:48 ` Nathan Scott
2006-01-15 23:22 ` Mattia Dongili
2006-01-16 9:29 ` Hans Reiser
2006-01-16 11:48 ` Christoph Hellwig
2006-01-16 15:50 ` Mattia Dongili
2006-01-17 3:27 ` Hans Reiser
2006-01-16 11:51 ` Mattia Dongili
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=20060111184027.GB4735@inferi.kami.home \
--to=malattia@linux.it \
--cc=akpm@osdl.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=reiserfs-dev@namesys.com \
/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).