From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Yermandu Patapitafious
<yermandu.dev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
i2c <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: i915 and boot freeze
Date: Tue, 24 May 2011 09:30:51 +0200 [thread overview]
Message-ID: <20110524093051.5682e769@endymion.delvare> (raw)
In-Reply-To: <BANLkTimZC9vOUu8On5DHkz5qxo8EfLKYYQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi Yermandu,
Please pay attention when writing and proofread yourself before
sending. You certainly meant i915, not i195, in the subject line. I've
fixed it. This is important if you want to get the attention of the
relevant maintainers and developers.
On Mon, 23 May 2011 19:33:15 -0300, Yermandu Patapitafious wrote:
> since kernel .39 i can not boot, when kernel go to gmbus start the issue.
> I try capture a dump with kexec, but no success, so i have the idea to
> make video booting,
> kernel version 2.6.39-02745-g0b26d47 and 2.6.39 vanilla same problem.
What is the last kernel that works for you?
Are you running self-built or distribution kernels?
Can we please see the kernel configuration file? You seem to have
verbose debugging options enabled (CONFIG_DEBUG_KOBJECT at least.) it
makes the logs harder to read.
> http://www.vimeo.com/24138372
Unfortunately the beginning is pretty hard to read. It would be great
if you were able to get us the kernel logs in a text form, using some
form of serial console.
I see references to i2c_for_each_dev, a new function which only i2c-dev
and i2c-core are using at the moment. So if you have CONFIG_I2C_CHARDEV
set, and this is a self-built kernel, try again without it just to get
it out of the picture.
Note that logs from a pure 2.6.39 kernel would probably be more useful
than from a later git snapshot. The 2.6.40 development branch is very
young and could have other problems.
Alternatively, if you are familiar with git, a git bisection would help
too.
--
Jean Delvare
next prev parent reply other threads:[~2011-05-24 7:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 22:33 i195 and boot freeze Yermandu Patapitafious
[not found] ` <BANLkTimZC9vOUu8On5DHkz5qxo8EfLKYYQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-05-24 7:30 ` Jean Delvare [this message]
[not found] ` <20110524093051.5682e769-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2011-05-25 13:38 ` i915 " Yermandu Patapitafious
[not found] ` <BANLkTime7ZT2UEeG=T=JqZKZBYa77fi0_Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-05-27 9:31 ` Jean Delvare
[not found] ` <20110527113106.56c7d755-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2011-05-29 21:33 ` Yermandu Patapitafious
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=20110524093051.5682e769@endymion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=yermandu.dev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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;
as well as URLs for NNTP newsgroup(s).