Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #53780 > unrolled thread

Re: Bug#822575: debian regression: no more console output after "switching to mgag200drmfb from simple"

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Bug#822575: debian regression: no more console output after  "switching to mgag200drmfb from simple" Mattia Rizzolo <mattia@debian.org> - 2016-04-26 10:40 +0200
    Processed: Re: Bug#822575: debian regression: no more console  output after "switching to mgag200drmfb from simple" owner@bugs.debian.org (Debian Bug Tracking System) - 2016-04-26 10:40 +0200
    Bug#822575: debian regression: no more console output after "switching to mgag200drmfb from simple" Ben Hutchings <ben@decadent.org.uk> - 2016-04-26 12:20 +0200
      Re: Bug#822575: debian regression: no more console output after  "switching to mgag200drmfb from simple" Harald Dunkel <harald.dunkel@aixigo.de> - 2016-04-26 14:00 +0200
      Bug#822575: debian regression: no more console output after "switching to mgag200drmfb from simple" Harald Dunkel <harald.dunkel@aixigo.de> - 2016-04-26 14:50 +0200
        Bug#822575: debian regression: no more console output after "switching to mgag200drmfb from simple" Ben Hutchings <ben@decadent.org.uk> - 2016-04-26 16:10 +0200
          Bug#822575: debian regression: no more console output after "switching to mgag200drmfb from simple" Harald Dunkel <harald.dunkel@aixigo.de> - 2016-04-27 09:10 +0200
            Bug#822575: debian regression: no more console output after "switching to mgag200drmfb from simple" Ben Hutchings <ben@decadent.org.uk> - 2016-04-27 11:50 +0200
    Bug#822575: debian regression: no more console output after "switching to mgag200drmfb from simple" Harald Dunkel <harald.dunkel@aixigo.de> - 2016-04-26 14:40 +0200

#53780 — Re: Bug#822575: debian regression: no more console output after "switching to mgag200drmfb from simple"

[Multipart message — attachments visible in raw view] — view raw

control: reassign -1 src:linux 4.4.6-1

On Mon, Apr 25, 2016 at 03:54:30PM +0200, Harald Dunkel wrote:
> Package: linux-image-4.4.0-1-amd64

This package doesn't exist anymore, so your bug report didn't actually
reach the linux maintainers.  reassigning so they'll see it.
(note: there is no reason whatsoever to keep me in CC after this
email...)

> Version: 4.4.6-1
> 
> Debian's kernel versions 4.4.6-1 and 4.5.1-1 give me

I kept your version, but if you have a problem with the current version,
whilst 4.4.6 is fine, probably you should have set the affected version
to 4.5.1-1, not 4.4.6-1...

> 	fb: switching to mgag200drmfb from simple
> 
> on amd64 at boot time. No further console output, esp. no
> login prompt. This is a regression of Debian's version 4.4.x;
> older kernels or a kernel built from upstream's sources
> doesn't show this problem. (I tried upstream's 4.4.8 and
> 4.5.2 on unstable.)
> 
> The log file says
> 
> :
> Apr 22 16:05:50 il06 kernel: [   10.552528] EDAC MC0: Giving out device to module i7core_edac.c controller i7 core #0: DEV 0000:ff:03.0 (POLLED)
> Apr 22 16:05:50 il06 kernel: [   10.552569] EDAC PCI0: Giving out device to module i7core_edac controller EDAC PCI controller: DEV 0000:ff:03.0 (POLLED)
> Apr 22 16:05:50 il06 kernel: [   10.552710] EDAC i7core: Driver loaded, 1 memory controller(s) found.
> Apr 22 16:05:50 il06 kernel: [   10.606660] checking generic (b0000000 280000) vs hw (b0000000 1000000)
> Apr 22 16:05:50 il06 kernel: [   10.606662] fb: switching to mgag200drmfb from simple
> Apr 22 16:05:50 il06 kernel: [   10.620080] Console: switching to colour dummy device 80x25
> Apr 22 16:05:50 il06 kernel: [   10.620135] iTCO_vendor_support: vendor-support=0
> Apr 22 16:05:50 il06 kernel: [   10.620343] [drm:mgag200_driver_load [mgag200]] *ERROR* can't reserve VRAM
> Apr 22 16:05:50 il06 kernel: [   10.620350] mgag200 0000:08:00.0: Fatal error during GPU init: -6
> Apr 22 16:05:50 il06 kernel: [   10.658776] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
> Apr 22 16:05:50 il06 kernel: [   10.658810] iTCO_wdt: unable to reset NO_REBOOT flag, device disabled by hardware/BIOS
> Apr 22 16:05:50 il06 kernel: [   10.767943] EXT4-fs (sda1): re-mounted. Opts: (null)
> :
> 
> Please note the "Console: switching to colour dummy device 80x25".
> I am using GRUB_GFXMODE=1280x1024.
> 
> # lspci
> 00:00.0 Host bridge: Intel Corporation Core Processor DMI (rev 11)
> 00:03.0 PCI bridge: Intel Corporation Core Processor PCI Express Root Port 1 (rev 11)
> 00:08.0 System peripheral: Intel Corporation Core Processor System Management Registers (rev 11)
> 00:08.1 System peripheral: Intel Corporation Core Processor Semaphore and Scratchpad Registers (rev 11)
> 00:08.2 System peripheral: Intel Corporation Core Processor System Control and Status Registers (rev 11)
> 00:08.3 System peripheral: Intel Corporation Core Processor Miscellaneous Registers (rev 11)
> 00:10.0 System peripheral: Intel Corporation Core Processor QPI Link (rev 11)
> 00:10.1 System peripheral: Intel Corporation Core Processor QPI Routing and Protocol Registers (rev 11)
> 00:19.0 Ethernet controller: Intel Corporation 82578DM Gigabit Network Connection (rev 05)
> 00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
> 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05)
> 00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5 (rev 05)
> 00:1c.6 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 7 (rev 05)
> 00:1c.7 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 8 (rev 05)
> 00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
> 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a5)
> 00:1f.0 ISA bridge: Intel Corporation 3400 Series Chipset LPC Interface Controller (rev 05)
> 00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller (rev 05)
> 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05)
> 01:00.0 PCI bridge: Integrated Device Technology, Inc. [IDT] HIO524G2 PCI Express Gen2 Switch (rev 02)
> 02:02.0 PCI bridge: Integrated Device Technology, Inc. [IDT] HIO524G2 PCI Express Gen2 Switch (rev 02)
> 02:03.0 PCI bridge: Integrated Device Technology, Inc. [IDT] HIO524G2 PCI Express Gen2 Switch (rev 02)
> 02:04.0 PCI bridge: Integrated Device Technology, Inc. [IDT] HIO524G2 PCI Express Gen2 Switch (rev 02)
> 07:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
> 08:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200e [Pilot] ServerEngines (SEP1) (rev 02)
> ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-Core Registers (rev 04)
> ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 04)
> ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 04)
> ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 04)
> ff:03.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller (rev 04)
> ff:03.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Target Address Decoder (rev 04)
> ff:03.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Test Registers (rev 04)
> ff:03.4 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Test Registers (rev 04)
> ff:04.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Control Registers (rev 04)
> ff:04.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Address Registers (rev 04)
> ff:04.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Rank Registers (rev 04)
> ff:04.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 0 Thermal Control Registers (rev 04)
> ff:05.0 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Control Registers (rev 04)
> ff:05.1 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Address Registers (rev 04)
> ff:05.2 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Rank Registers (rev 04)
> ff:05.3 Host bridge: Intel Corporation Core Processor Integrated Memory Controller Channel 1 Thermal Control Registers (rev 04)
> 
> 
> I got quiet a number of these intel boards, i.e. its a pretty
> painful problem. I wouldn't like to run all these hosts with
> 80x25.
> 
> 
> Regards
> Harri

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

[toc] | [next] | [standalone]

#53781 — Processed: Re: Bug#822575: debian regression: no more console output after "switching to mgag200drmfb from simple"

Processing control commands:

> reassign -1 src:linux 4.4.6-1
Bug #822575 [linux-image-4.4.0-1-amd64] debian regression: no more console output after "switching to mgag200drmfb from simple"
Warning: Unknown package 'linux-image-4.4.0-1-amd64'
Bug reassigned from package 'linux-image-4.4.0-1-amd64' to 'src:linux'.
No longer marked as found in versions linux/4.4.6-1.
Ignoring request to alter fixed versions of bug #822575 to the same values previously set
Bug #822575 [src:linux] debian regression: no more console output after "switching to mgag200drmfb from simple"
Marked as found in versions linux/4.4.6-1.

-- 
822575: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822575
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#53784 — Bug#822575: debian regression: no more console output after "switching to mgag200drmfb from simple"

[Multipart message — attachments visible in raw view] — view raw

Control: tag -1 moreinfo

On Mon, Apr 25, 2016 at 03:54:30PM +0200, Harald Dunkel wrote:
[...]
>	fb: switching to mgag200drmfb from simple
> 
> on amd64 at boot time. No further console output, esp. no
> login prompt. This is a regression of Debian's version 4.4.x;
> older kernels or a kernel built from upstream's sources
> doesn't show this problem. (I tried upstream's 4.4.8 and
> 4.5.2 on unstable.)
[...]
> Please note the "Console: switching to colour dummy device 80x25".
> I am using GRUB_GFXMODE=1280x1024.

And have you tried removing that?

[...]
>  I got quiet a number of these intel boards, i.e. its a pretty
>  painful problem. I wouldn't like to run all these hosts with
>  80x25.

That might be an effect of the driver being confused by GRUB's
modesetting.  I don't know.

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
                                                            - Robert Coveyou

[toc] | [prev] | [next] | [standalone]

#53786

Without GRUB_GFXMODE and GRUB_GFXPAYLOAD_LINUX I get

Apr 26 13:07:57 usbpc kernel: [   18.245417] AES CTR mode by8 optimization enabled
Apr 26 13:07:57 usbpc kernel: [   18.256518] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
Apr 26 13:07:57 usbpc kernel: [   18.271819] fbcon: mgadrmfb (fb0) is primary device
Apr 26 13:07:57 usbpc kernel: [   18.340257] ipmi_si IPI0001:00: Found new BMC (man_id: 0x000157, prod_id: 0x0048, dev_id: 0x21)
Apr 26 13:07:57 usbpc kernel: [   18.340261] ipmi_si IPI0001:00: IPMI kcs interface initialized
Apr 26 13:07:57 usbpc kernel: [   18.539515] Console: switching to colour frame buffer device 160x64
Apr 26 13:07:57 usbpc kernel: [   18.577386] mgag200 0000:03:00.0: fb0: mgadrmfb frame buffer device
Apr 26 13:07:57 usbpc kernel: [   18.585608] [drm] Initialized mgag200 1.0.0 20110418 for 0000:03:00.0 on minor 0
Apr 26 13:07:57 usbpc kernel: [   18.588803] intel_rapl: Found RAPL domain package
Apr 26 13:07:57 usbpc kernel: [   18.588817] intel_rapl: Found RAPL domain core

The console output doesn't get stuck, either.

> That might be an effect of the driver being confused by GRUB's
> modesetting.  I don't know.

Maybe. OTOH, upstream's kernel (built on unstable) just works,
using the same grub configuration, installed on the same bootable
USB stick and booted on the same hardware.

Do you think there could be a side effect of the recent patch
cleanup for mgag200 & cirrus done for 4.4~rc5-1~exp1?


Regards
Harri

[toc] | [prev] | [next] | [standalone]

#53788 — Bug#822575: debian regression: no more console output after "switching to mgag200drmfb from simple"

Without GRUB_GFXMODE and GRUB_GFXPAYLOAD_LINUX I get

Apr 26 13:07:57 usbpc kernel: [   18.245417] AES CTR mode by8 optimization enabled
Apr 26 13:07:57 usbpc kernel: [   18.256518] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
Apr 26 13:07:57 usbpc kernel: [   18.271819] fbcon: mgadrmfb (fb0) is primary device
Apr 26 13:07:57 usbpc kernel: [   18.340257] ipmi_si IPI0001:00: Found new BMC (man_id: 0x000157, prod_id: 0x0048, dev_id: 0x21)
Apr 26 13:07:57 usbpc kernel: [   18.340261] ipmi_si IPI0001:00: IPMI kcs interface initialized
Apr 26 13:07:57 usbpc kernel: [   18.539515] Console: switching to colour frame buffer device 160x64
Apr 26 13:07:57 usbpc kernel: [   18.577386] mgag200 0000:03:00.0: fb0: mgadrmfb frame buffer device
Apr 26 13:07:57 usbpc kernel: [   18.585608] [drm] Initialized mgag200 1.0.0 20110418 for 0000:03:00.0 on minor 0
Apr 26 13:07:57 usbpc kernel: [   18.588803] intel_rapl: Found RAPL domain package
Apr 26 13:07:57 usbpc kernel: [   18.588817] intel_rapl: Found RAPL domain core

The console output doesn't get stuck, either.

> That might be an effect of the driver being confused by GRUB's
> modesetting.  I don't know.

Maybe. OTOH, upstream's kernel (built on unstable) just works,
using the same grub configuration, installed on the same bootable
USB stick and booted on the same hardware.

Do you think there could be a side effect of the recent patch
cleanup for mgag200 & cirrus done for 4.4~rc5-1~exp1?


Regards
Harri

[toc] | [prev] | [next] | [standalone]

#53789 — Bug#822575: debian regression: no more console output after "switching to mgag200drmfb from simple"

[Multipart message — attachments visible in raw view] — view raw

On Tue, 2016-04-26 at 14:43 +0200, Harald Dunkel wrote:
> Without GRUB_GFXMODE and GRUB_GFXPAYLOAD_LINUX I get
> 
> Apr 26 13:07:57 usbpc kernel: [   18.245417] AES CTR mode by8 optimization enabled
> Apr 26 13:07:57 usbpc kernel: [   18.256518] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
> Apr 26 13:07:57 usbpc kernel: [   18.271819] fbcon: mgadrmfb (fb0) is primary device
> Apr 26 13:07:57 usbpc kernel: [   18.340257] ipmi_si IPI0001:00: Found new BMC (man_id: 0x000157, prod_id: 0x0048, dev_id: 0x21)
> Apr 26 13:07:57 usbpc kernel: [   18.340261] ipmi_si IPI0001:00: IPMI kcs interface initialized
> Apr 26 13:07:57 usbpc kernel: [   18.539515] Console: switching to colour frame buffer device 160x64
> Apr 26 13:07:57 usbpc kernel: [   18.577386] mgag200 0000:03:00.0: fb0: mgadrmfb frame buffer device
> Apr 26 13:07:57 usbpc kernel: [   18.585608] [drm] Initialized mgag200 1.0.0 20110418 for 0000:03:00.0 on minor 0
> Apr 26 13:07:57 usbpc kernel: [   18.588803] intel_rapl: Found RAPL domain package
> Apr 26 13:07:57 usbpc kernel: [   18.588817] intel_rapl: Found RAPL domain core
> 
> The console output doesn't get stuck, either.
> 
> > 
> > That might be an effect of the driver being confused by GRUB's
> > modesetting.  I don't know.
> Maybe. OTOH, upstream's kernel (built on unstable) just works,
> using the same grub configuration, installed on the same bootable
> USB stick and booted on the same hardware.

I'm guessing that you didn't built the mgag200 driver (CONFIG_DRM_MGA),
right?

> Do you think there could be a side effect of the recent patch
> cleanup for mgag200 & cirrus done for 4.4~rc5-1~exp1?

Yes, very likely.

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
                                                            - Robert Coveyou

[toc] | [prev] | [next] | [standalone]

#53793 — Bug#822575: debian regression: no more console output after "switching to mgag200drmfb from simple"

[Multipart message — attachments visible in raw view] — view raw

On 04/26/2016 04:05 PM, Ben Hutchings wrote:
> 
> I'm guessing that you didn't built the mgag200 driver (CONFIG_DRM_MGA),
> right?
> 

Of course its in, as for the official kernel.

	% grep -i mga /boot/config-4.5.2
	CONFIG_DRM_MGA=m
	CONFIG_DRM_MGAG200=m

Would you suggest to blacklist this module?

Regards
Harri

[toc] | [prev] | [next] | [standalone]

#53795 — Bug#822575: debian regression: no more console output after "switching to mgag200drmfb from simple"

[Multipart message — attachments visible in raw view] — view raw

Control: tag -1 - moreinfo

On Wed, 2016-04-27 at 09:01 +0200, Harald Dunkel wrote:
> On 04/26/2016 04:05 PM, Ben Hutchings wrote:
> > 
> > 
> > I'm guessing that you didn't built the mgag200 driver
> > (CONFIG_DRM_MGA),
> > right?
> > 
> Of course its in, as for the official kernel.
> 
> 	% grep -i mga /boot/config-4.5.2
> 	CONFIG_DRM_MGA=m
> 	CONFIG_DRM_MGAG200=m

Oh of course, mga and mgag200 are two different drivers.  Thanks for
working out what I meant.

> Would you suggest to blacklist this module?

Not in general, but that should work around the bug.  That is
effectively what we were doing before version 4.4~rc5-1~exp1 to avoid
conflicts with older X drivers (while xserver-xorg-video-modesetting
would override that blacklisting).  Since we don't patch mgag200 any
more, I don't understand why you are seeing a bug with the official
kernel package and yet not with a custom kernel.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

[toc] | [prev] | [next] | [standalone]

#53787 — Bug#822575: debian regression: no more console output after "switching to mgag200drmfb from simple"

We can focus on 4.5.1-1, even though the regression
came up with 4.4.x.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web