The right log with 2.6.37-rc3+:
Dec 15 16:13:03 teawater-workpc kernel: [ 14.569871] [drm] Initialized
drm 1.1.0 20060810
Dec 15 16:13:03 teawater-workpc kernel: [ 14.882768] i915
0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Dec 15 16:13:03 teawater-workpc kernel: [ 14.882775] i915
0000:00:02.0: setting latency timer to 64
Dec 15 16:13:03 teawater-workpc kernel: [ 14.894778] mtrr: type
mismatch for d0000000,10000000 old: write-back new: write-combining
Dec 15 16:13:03 teawater-workpc kernel: [ 14.894781] [drm] MTRR
allocation failed. Graphics performance may suffer.
Dec 15 16:13:03 teawater-workpc kernel: [ 14.895367] i915
0000:00:02.0: irq 43 for MSI/MSI-X
Dec 15 16:13:03 teawater-workpc kernel: [ 14.895610] vgaarb: device
changed decodes:
PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
Dec 15 16:13:03 teawater-workpc kernel: [ 14.895927] [drm] initialized
overlay support
Dec 15 16:13:03 teawater-workpc kernel: [ 14.981492] Console:
switching to colour frame buffer device 210x65
Dec 15 16:13:03 teawater-workpc kernel: [ 14.986676] fb0: inteldrmfb
frame buffer device
Dec 15 16:13:03 teawater-workpc kernel: [ 14.986678] drm: registered
panic notifier
Dec 15 16:13:03 teawater-workpc kernel: [ 14.986761] [drm] Initialized
i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
The black log with 2.6.37-rc5+:
Dec 15 16:10:51 teawater-workpc kernel: [ 12.418419] [drm] Initialized
drm 1.1.0 20060810
Dec 15 16:10:51 teawater-workpc kernel: [ 12.945240] i915
0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Dec 15 16:10:51 teawater-workpc kernel: [ 12.945246] i915
0000:00:02.0: setting latency timer to 64
Dec 15 16:10:51 teawater-workpc kernel: [ 12.957555] mtrr: type
mismatch for d0000000,10000000 old: write-back new: write-combining
Dec 15 16:10:51 teawater-workpc kernel: [ 12.957559] [drm] MTRR
allocation failed. Graphics performance may suffer.
Dec 15 16:10:51 teawater-workpc kernel: [ 12.958502] i915
0000:00:02.0: irq 42 for MSI/MSI-X
Dec 15 16:10:51 teawater-workpc kernel: [ 12.958806] vgaarb: device
changed decodes:
PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
Dec 15 16:10:51 teawater-workpc kernel: [ 12.959124] [drm] initialized
overlay support
Dec 15 16:10:51 teawater-workpc kernel: [ 13.980020] No connectors
reported connected with modes
Dec 15 16:10:51 teawater-workpc kernel: [ 13.980025] [drm] Cannot find
any crtc or sizes - going 1024x768
Dec 15 16:10:51 teawater-workpc kernel: [ 13.986063] Console:
switching to colour frame buffer device 128x48
Dec 15 16:10:51 teawater-workpc kernel: [ 13.988296] fb0: inteldrmfb
frame buffer device
Dec 15 16:10:51 teawater-workpc kernel: [ 13.988298] drm: registered
panic notifier
Dec 15 16:10:51 teawater-workpc kernel: [ 13.988425] [drm] Initialized
i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
Thanks,
Hui
Which chipset and what connectors? Judging by the offending commits, my
guess is an Arrandale with eDP, in which case
https://bugs.freedesktop.org/show_bug.cgi?id=31988 will be of interest.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
On Wed, Dec 15, 2010 at 17:23, Chris Wilson <[email protected]> wrote:
> Which chipset and what connectors? Judging by the offending commits, my
> guess is an Arrandale with eDP, in which case
> https://bugs.freedesktop.org/show_bug.cgi?id=31988 will be of interest.
> -Chris
>
> --
> Chris Wilson, Intel Open Source Technology Centre
>
lspci | grep Display
00:02.1 Display controller: Intel Corporation 82Q35 Express Integrated
Graphics Controller (rev 02)
Thanks,
Hui
On Wed, 15 Dec 2010 17:28:45 +0800, Hui Zhu <[email protected]> wrote:
> lspci | grep Display
> 00:02.1 Display controller: Intel Corporation 82Q35 Express Integrated
> Graphics Controller (rev 02)
Q35. I wasn't expecting that. Can you please add drm.debug=0xe to your
boot line and attach the dmesg from rc3 and rc5? Thanks.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
On Wed, Dec 15, 2010 at 18:20, Chris Wilson <[email protected]> wrote:
> On Wed, 15 Dec 2010 17:28:45 +0800, Hui Zhu <[email protected]> wrote:
>> lspci | grep Display
>> 00:02.1 Display controller: Intel Corporation 82Q35 Express Integrated
>> Graphics Controller (rev 02)
>
> Q35. I wasn't expecting that. Can you please add drm.debug=0xe to your
> boot line and attach the dmesg from rc3 and rc5? Thanks.
> -Chris
>
> --
> Chris Wilson, Intel Open Source Technology Centre
>
Thanks Chris.
I post the logs of rc3+, rc4+ and rc5+ in attchement. Wish they can
be more helpful.
Best,
Hui
On Thu, 16 Dec 2010 10:20:57 +0800, Hui Zhu <[email protected]> wrote:
> On Wed, Dec 15, 2010 at 18:20, Chris Wilson <[email protected]> wrote:
> > On Wed, 15 Dec 2010 17:28:45 +0800, Hui Zhu <[email protected]> wrote:
> >> lspci | grep Display
> >> 00:02.1 Display controller: Intel Corporation 82Q35 Express Integrated
> >> Graphics Controller (rev 02)
> >
> > Q35. I wasn't expecting that. Can you please add drm.debug=0xe to your
> > boot line and attach the dmesg from rc3 and rc5? Thanks.
> > -Chris
> >
> > --
> > Chris Wilson, Intel Open Source Technology Centre
> >
>
> Thanks Chris.
>
> I post the logs of rc3+, rc4+ and rc5+ in attchement. Wish they can
> be more helpful.
The hotplug probe was failing. The only change along that path I could see
was to setting some hotplug flags in the analag adapter register. Can you
try this patch to see if it fixes things for you? Meanwhile I'll check the
docs for the validity of those flags for the various gen.
diff --git a/drivers/gpu/drm/i915/intel_crt.c
b/drivers/gpu/drm/i915/intel_crt.c
index 8df5743..14c276e 100644
--- a/drivers/gpu/drm/i915/intel_crt.c
+++ b/drivers/gpu/drm/i915/intel_crt.c
@@ -148,7 +148,9 @@ static void intel_crt_mode_set(struct drm_encoder *encoder,
dpll_md & ~DPLL_MD_UDI_MULTIPLIER_MASK);
}
- adpa = ADPA_HOTPLUG_BITS;
+ adpa = 0;
+ if (INTEL_INFO(dev)->gen >= 4)
+ adpa |= ADPA_HOTPLUG_BITS;
if (adjusted_mode->flags & DRM_MODE_FLAG_PHSYNC)
adpa |= ADPA_HSYNC_ACTIVE_HIGH;
if (adjusted_mode->flags & DRM_MODE_FLAG_PVSYNC)
--
Chris Wilson, Intel Open Source Technology Centre
Still black screen.
Cannot get the log from /var/log and cannot connect the pc through
net. So I didn't get the log. Sorry for that.
Thanks,
Hui
On Thu, Dec 16, 2010 at 18:10, Chris Wilson <[email protected]> wrote:
> On Thu, 16 Dec 2010 10:20:57 +0800, Hui Zhu <[email protected]> wrote:
>> On Wed, Dec 15, 2010 at 18:20, Chris Wilson <[email protected]> wrote:
>> > On Wed, 15 Dec 2010 17:28:45 +0800, Hui Zhu <[email protected]> wrote:
>> >> lspci | grep Display
>> >> 00:02.1 Display controller: Intel Corporation 82Q35 Express Integrated
>> >> Graphics Controller (rev 02)
>> >
>> > Q35. I wasn't expecting that. Can you please add drm.debug=0xe to your
>> > boot line and attach the dmesg from rc3 and rc5? Thanks.
>> > -Chris
>> >
>> > --
>> > Chris Wilson, Intel Open Source Technology Centre
>> >
>>
>> Thanks Chris.
>>
>> I post the logs of rc3+, rc4+ and rc5+ in attchement. ?Wish they can
>> be more helpful.
>
> The hotplug probe was failing. The only change along that path I could see
> was to setting some hotplug flags in the analag adapter register. Can you
> try this patch to see if it fixes things for you? Meanwhile I'll check the
> docs for the validity of those flags for the various gen.
>
> diff --git a/drivers/gpu/drm/i915/intel_crt.c
> b/drivers/gpu/drm/i915/intel_crt.c
> index 8df5743..14c276e 100644
> --- a/drivers/gpu/drm/i915/intel_crt.c
> +++ b/drivers/gpu/drm/i915/intel_crt.c
> @@ -148,7 +148,9 @@ static void intel_crt_mode_set(struct drm_encoder *encoder,
> ? ? ? ? ? ? ? ? ? ? ? ? ? dpll_md & ~DPLL_MD_UDI_MULTIPLIER_MASK);
> ? ? ? ?}
>
> - ? ? ? adpa = ADPA_HOTPLUG_BITS;
> + ? ? ? adpa = 0;
> + ? ? ? if (INTEL_INFO(dev)->gen >= 4)
> + ? ? ? ? ? ? ? adpa |= ADPA_HOTPLUG_BITS;
> ? ? ? ?if (adjusted_mode->flags & DRM_MODE_FLAG_PHSYNC)
> ? ? ? ? ? ? ? ?adpa |= ADPA_HSYNC_ACTIVE_HIGH;
> ? ? ? ?if (adjusted_mode->flags & DRM_MODE_FLAG_PVSYNC)
>
> --
> Chris Wilson, Intel Open Source Technology Centre
>
Chris Wilson wrote:
> Which chipset and what connectors? Judging by the offending commits, my
> guess is an Arrandale with eDP, in which case
> https://bugs.freedesktop.org/show_bug.cgi?id=31988 will be of interest.
> -Chris
>
>
Chris, after seeing this message I have tested -rc6 on G33 as well and
can confirm that it is broken.
I can see only "unpacking" message - very very brief - and then
absolutely black screen.
I have prepared a custom initrd to ddump the dmesg to a hard disk and
here are results - "No connectors reported connected with modes".
I attach a run with -rc5 (good) and -rc6 (bad) dmesg dump...
Would it give you enough to work on?
Thanks, Woody
I created a Bugzilla entry at
https://bugzilla.kernel.org/show_bug.cgi?id=25242
for your bug report, please add your address to the CC list in there, thanks!
On środa, 15 grudnia 2010 o 09:33:29 Hui Zhu wrote:
> The right log with 2.6.37-rc3+:
> Dec 15 16:13:03 teawater-workpc kernel: [ 14.569871] [drm] Initialized
> drm 1.1.0 20060810
> Dec 15 16:13:03 teawater-workpc kernel: [ 14.882768] i915
> 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> Dec 15 16:13:03 teawater-workpc kernel: [ 14.882775] i915
> 0000:00:02.0: setting latency timer to 64
> Dec 15 16:13:03 teawater-workpc kernel: [ 14.894778] mtrr: type
> mismatch for d0000000,10000000 old: write-back new: write-combining
> Dec 15 16:13:03 teawater-workpc kernel: [ 14.894781] [drm] MTRR
> allocation failed. Graphics performance may suffer.
> Dec 15 16:13:03 teawater-workpc kernel: [ 14.895367] i915
> 0000:00:02.0: irq 43 for MSI/MSI-X
> Dec 15 16:13:03 teawater-workpc kernel: [ 14.895610] vgaarb: device
> changed decodes:
> PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
> Dec 15 16:13:03 teawater-workpc kernel: [ 14.895927] [drm] initialized
> overlay support
> Dec 15 16:13:03 teawater-workpc kernel: [ 14.981492] Console:
> switching to colour frame buffer device 210x65
> Dec 15 16:13:03 teawater-workpc kernel: [ 14.986676] fb0: inteldrmfb
> frame buffer device
> Dec 15 16:13:03 teawater-workpc kernel: [ 14.986678] drm: registered
> panic notifier
> Dec 15 16:13:03 teawater-workpc kernel: [ 14.986761] [drm] Initialized
> i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
>
> The black log with 2.6.37-rc5+:
> Dec 15 16:10:51 teawater-workpc kernel: [ 12.418419] [drm] Initialized
> drm 1.1.0 20060810
> Dec 15 16:10:51 teawater-workpc kernel: [ 12.945240] i915
> 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> Dec 15 16:10:51 teawater-workpc kernel: [ 12.945246] i915
> 0000:00:02.0: setting latency timer to 64
> Dec 15 16:10:51 teawater-workpc kernel: [ 12.957555] mtrr: type
> mismatch for d0000000,10000000 old: write-back new: write-combining
> Dec 15 16:10:51 teawater-workpc kernel: [ 12.957559] [drm] MTRR
> allocation failed. Graphics performance may suffer.
> Dec 15 16:10:51 teawater-workpc kernel: [ 12.958502] i915
> 0000:00:02.0: irq 42 for MSI/MSI-X
> Dec 15 16:10:51 teawater-workpc kernel: [ 12.958806] vgaarb: device
> changed decodes:
> PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
> Dec 15 16:10:51 teawater-workpc kernel: [ 12.959124] [drm] initialized
> overlay support
> Dec 15 16:10:51 teawater-workpc kernel: [ 13.980020] No connectors
> reported connected with modes
> Dec 15 16:10:51 teawater-workpc kernel: [ 13.980025] [drm] Cannot find
> any crtc or sizes - going 1024x768
> Dec 15 16:10:51 teawater-workpc kernel: [ 13.986063] Console:
> switching to colour frame buffer device 128x48
> Dec 15 16:10:51 teawater-workpc kernel: [ 13.988296] fb0: inteldrmfb
> frame buffer device
> Dec 15 16:10:51 teawater-workpc kernel: [ 13.988298] drm: registered
> panic notifier
> Dec 15 16:10:51 teawater-workpc kernel: [ 13.988425] [drm] Initialized
> i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
>
> Thanks,
> Hui
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Maciej Rutecki
http://www.maciek.unixy.pl
Maciej Rutecki wrote:
> I created a Bugzilla entry at
> https://bugzilla.kernel.org/show_bug.cgi?id=25242
> for your bug report, please add your address to the CC list in there, thanks!
>
>
Reverting the commit 541cc966915b6756e54c20eebe60ae957afdb537 fixes the
problem on my G33 system
Woody