From: "Daniele C." <legolas558@users.sourceforge.net>
To: stable@kernel.org, neilb@suse.de
Cc: linux-raid@vger.kernel.org
Subject: [GIT BISECT] kernel early crash in 2.6.34~2.6.35-rc1
Date: Wed, 02 Jun 2010 03:14:41 +0200 [thread overview]
Message-ID: <4C05B081.2000904@users.sourceforge.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello there,
I have individuated a bad commit which causes an early crash in some SSB/CPI routine; sorry can't be more precise right now, it would require serial debugging to get the dump.
Last good commit: 240ed68eb567d80dd6bab739341999a5ab0ad55d
First bad commit: 6e4513972a5ad28517477d21f301a02ac7a0df76
Hardware: laptop Maxdata PRO 7000DX (apparently Fujitsu Amilo V2000 clone)
Crash is also present in HEAD (currently 67a3e12b05e055c0415c556a315a3d3eb637e29e).
I have given a look to the commitdiff but it looks too much complex for me to individuate where's the issue at first glance.
Can somebody please give a look and/or narrow it down to a patch?
Thanks,
- --
Daniele C.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJMBbCBAAoJEON28As9epPATXIH/RbBVXobBPXhon529E5Cov2m
Rw9d3/VhY9pNLIk9UbtkuJslG6o96GQjTqqNK4M95RE43QYpzqx1Gw5r84H1j2NZ
qxEb+GmHYj8ltdsUmQJXc4b4iIrqJVSjfInbzftKrgKdFybxDJF1Byl1FpXXyFqC
TVEHsXhaTpnqylVTbQuweCPgv7MDWBO9MxMJoBQSvXNqefqlfyrgWeT5Eimg73mz
mgNQKE8aAOYF3d3ZxgIN43jun5VmFxMC8t4E8d68/yA0g9VFW04iSecY9ZeJgmZR
gHNrhwP/JzEja+FErRDGliQdyeFleV3rcsmWH7xwHecc2HcVt73BkpWR1qYwdwQ=
=Dtjt
-----END PGP SIGNATURE-----
next reply other threads:[~2010-06-02 1:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 1:14 Daniele C. [this message]
2010-06-02 1:29 ` [GIT BISECT] kernel early crash in 2.6.34~2.6.35-rc1 Neil Brown
2010-06-02 16:52 ` Daniele C.
2010-06-02 21:38 ` Neil Brown
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=4C05B081.2000904@users.sourceforge.net \
--to=legolas558@users.sourceforge.net \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.