public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Riccardo Magliocchetti <riccardo.magliocchetti@gmail.com>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: kernel oops with latest git v2.6.29-9516-g0221c81
Date: Mon, 06 Apr 2009 23:41:28 +0200	[thread overview]
Message-ID: <49DA7708.3040201@gmail.com> (raw)
In-Reply-To: <49DA69DD.2090203@linux.intel.com>

Arjan van de Ven ha scritto:
> Arkadiusz Miskiewicz wrote:
>> On Monday 06 of April 2009, Riccardo Magliocchetti wrote:
>>> Hi,
>>>
>>> i've updated the kernel to latest git and now it's oopsing.
>>>
>>> I've uploaded 3 pictures taken from a camera here:
>>>
>>> http://yfrog.com/41oops1j
>>> http://yfrog.com/bcoops2j
>>> http://yfrog.com/bcoops3j
>>
>> You hit the same thing as me:
> 
> I'm not so sure of that.
> 
> All the oopses from the URL above seem to have the "F" flag set for the 
> modules, which implies that
> the modules you're using don't match the kernel you are running. That's 
> a pretty bad deal
> in general, and more likely than not to be the cause of any weird 
> crashes you're getting...

Ok so i've started bisecting and taking care of removing the old modules 
at each step, this is what i have done for today, will continue tomorrow:

$ git bisect log
git bisect start
# bad: [0221c81b1b8eb0cbb6b30a0ced52ead32d2b4e4c] Merge branch 
'audit.b62' of 
git://git.kernel.org/pub/scm/linux/kernel/git/viro/audit-current
git bisect bad 0221c81b1b8eb0cbb6b30a0ced52ead32d2b4e4c
# good: [c4361bb64b81f5b81a7a08d58654493385a2f2b2] Merge branch 'master' 
of git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6
git bisect good c4361bb64b81f5b81a7a08d58654493385a2f2b2
# good: [6555be0a1c25576be6270bb43f1bd444df7d86f8] Staging: comedi: 
Remove mpc8260cpm_private typedef
git bisect good 6555be0a1c25576be6270bb43f1bd444df7d86f8
# good: [645dae969c3b8651c5bc7c54a1835ec03820f85f] tracing, net: fix net 
tree and tracing tree merge interaction
git bisect good 645dae969c3b8651c5bc7c54a1835ec03820f85f
# good: [7ec0a7290797f57b780f792d12f4bcc19c83aa4f] ACPI: processor: use 
.notify method instead of installing handler directly
git bisect good 7ec0a7290797f57b780f792d12f4bcc19c83aa4f

thanks,
riccardo

  reply	other threads:[~2009-04-06 21:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06 20:09 kernel oops with latest git v2.6.29-9516-g0221c81 Riccardo Magliocchetti
2009-04-06 20:34 ` Arkadiusz Miskiewicz
2009-04-06 20:45   ` Arjan van de Ven
2009-04-06 21:41     ` Riccardo Magliocchetti [this message]
2009-04-08  8:50   ` Riccardo Magliocchetti

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=49DA7708.3040201@gmail.com \
    --to=riccardo.magliocchetti@gmail.com \
    --cc=a.miskiewicz@gmail.com \
    --cc=arjan@linux.intel.com \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox