blank screen

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

blank screen

lvdd-2

Hi,

is somebody messing with the graphics stack by any chance?

I installed today's snapshot (#116) and my system refuses to show me a
picture as soon as "inteldrm0" is initialized. Up to that point I can
see all messages on the console but after that the screen stays blank
because the monitor goes to sleep.
I have no console and no X and restarting xenodm or typing startx
blindly after login has no effect. Right now I can only connect
remotely. I had an older snapshot lying around (#111) and tried that
one with the same effect. I was working with OpenBSD 6.1-current
(GENERIC.MP) #91 until today and had no issues.
What is happening?

Thanks
Lars

here is my current dmesg:

OpenBSD 6.1-current (GENERIC.MP) #116: Sat Jun 10 22:34:37 MDT 2017
    [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8440090624 (8049MB)
avail mem = 8178507776 (7799MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xec2f0 (67 entries)
bios0: vendor American Megatrends Inc. version "0806" date 12/14/2015
bios0: ASUS All Series
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT LPIT SSDT SSDT MCFG HPET SSDT SSDT BGRT
acpi0: wakeup devices UAR1(S4) PXSX(S4) RP01(S4) PXSX(S4) PXSX(S4) RP03(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) GLAN(S4) EHC1(S4) EHC2(S4) XHC_(S4) HDEF(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i3-4360 CPU @ 3.70GHz, 3691.93 MHz
cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: TSC frequency 3691929440 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i3-4360 CPU @ 3.70GHz, 3691.46 MHz
cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i3-4360 CPU @ 3.70GHz, 3691.46 MHz
cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i3-4360 CPU @ 3.70GHz, 3691.46 MHz
cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 8 pa 0xfec00000, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xf8000000, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 2 (RP01)
acpiprt2 at acpi0: bus 3 (RP03)
acpiprt3 at acpi0: bus 1 (PEG0)
acpiprt4 at acpi0: bus -1 (PEG1)
acpiprt5 at acpi0: bus -1 (PEG2)
acpiec0 at acpi0: not present
acpicpu0 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS
acpipwrres0 at acpi0: FN00, resource for FAN0
acpipwrres1 at acpi0: FN01, resource for FAN1
acpipwrres2 at acpi0: FN02, resource for FAN2
acpipwrres3 at acpi0: FN03, resource for FAN3
acpipwrres4 at acpi0: FN04, resource for FAN4
acpitz0 at acpi0: critical temperature is 105 degC
acpitz1 at acpi0: critical temperature is 105 degC
"INT3F0D" at acpi0 not configured
"PNP0501" at acpi0 not configured
acpibtn0 at acpi0: PWRB
"PNP0C0B" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
"PNP0A0A" at acpi0 not configured
"PNP0C14" at acpi0 not configured
acpivideo0 at acpi0: GFX0
acpivout0 at acpivideo0: DD1F
cpu0: Enhanced SpeedStep 3691 MHz: speeds: 3700, 3500, 3300, 3100, 2900, 2700, 2500, 2300, 2200, 2000, 1800, 1600, 1400, 1200, 1000, 800 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Core 4G Host" rev 0x06
ppb0 at pci0 dev 1 function 0 "Intel Core 4G PCIE" rev 0x06: msi
pci1 at ppb0 bus 1
inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 4600" rev 0x06
drm0 at inteldrm0
inteldrm0: msi
inteldrm0: 1024x768, 32bpp
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
azalia0 at pci0 dev 3 function 0 "Intel Core 4G HD Audio" rev 0x06: msi
azalia0: No codecs found
"Intel 8 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured
ehci0 at pci0 dev 26 function 0 "Intel 8 Series USB" rev 0x05: apic 8 int 20
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
azalia1 at pci0 dev 27 function 0 "Intel 8 Series HD Audio" rev 0x05: msi
azalia1: codecs: Realtek/0x0887
audio0 at azalia1
ppb1 at pci0 dev 28 function 0 "Intel 8 Series PCIE" rev 0xd5: msi
pci2 at ppb1 bus 2
ppb2 at pci0 dev 28 function 2 "Intel 8 Series PCIE" rev 0xd5: msi
pci3 at ppb2 bus 3
re0 at pci3 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G (0x4c00), msi, address bc:ee:7b:9d:c4:05
rgephy0 at re0 phy 7: RTL8251 PHY, rev. 0
ehci1 at pci0 dev 29 function 0 "Intel 8 Series USB" rev 0x05: apic 8 int 23
usb1 at ehci1: USB revision 2.0
uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
pcib0 at pci0 dev 31 function 0 "Intel H81 LPC" rev 0x05
ahci0 at pci0 dev 31 function 2 "Intel 8 Series AHCI" rev 0x05: msi, AHCI 1.3
ahci0: port 0: 6.0Gb/s
scsibus1 at ahci0: 32 targets
sd0 at scsibus1 targ 0 lun 0: <ATA, Crucial_CT1050MX, M0C> SCSI3 0/direct fixed naa.500a075113f66ec6
sd0: 1001562MB, 512 bytes/sector, 2051200368 sectors, thin
ichiic0 at pci0 dev 31 function 3 "Intel 8 Series SMBus" rev 0x05: apic 8 int 18
iic0 at ichiic0
spdmem0 at iic0 addr 0x50: 4GB DDR3 SDRAM PC3-10600 SO-DIMM
spdmem1 at iic0 addr 0x52: 4GB DDR3 SDRAM PC3-10600 SO-DIMM
isa0 at pcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
vmm0 at mainbus0: VMX/EPT
uhub2 at uhub0 port 1 configuration 1 interface 0 "Intel Rate Matching Hub" rev 2.00/0.05 addr 2
uhub3 at uhub2 port 1 configuration 1 interface 0 "Genesys Logic USB2.0 Hub" rev 2.00/32.98 addr 3
uhidev0 at uhub3 port 3 configuration 1 interface 0 "Logitech G400s Optical Gaming Mouse" rev 2.00/83.00 addr 4
uhidev0: iclass 3/1
ums0 at uhidev0: 8 buttons, Z dir
wsmouse0 at ums0 mux 0
uhidev1 at uhub3 port 3 configuration 1 interface 1 "Logitech G400s Optical Gaming Mouse" rev 2.00/83.00 addr 4
uhidev1: iclass 3/0, 142 report ids
uhid0 at uhidev1 reportid 32: input=0, output=0, feature=1
uhid1 at uhidev1 reportid 128: input=1, output=0, feature=0
uhid2 at uhidev1 reportid 142: input=0, output=0, feature=1
uhidev2 at uhub3 port 4 configuration 1 interface 0 "Dell Dell USB Keyboard" rev 1.10/3.06 addr 5
uhidev2: iclass 3/1
ukbd0 at uhidev2: 8 variable keys, 6 key codes
wskbd1 at ukbd0 mux 1
wskbd1: connecting to wsdisplay0
uhub4 at uhub1 port 1 configuration 1 interface 0 "Intel Rate Matching Hub" rev 2.00/0.05 addr 2
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
sd1 at scsibus3 targ 1 lun 0: <OPENBSD, SR CRYPTO, 006> SCSI2 0/direct fixed
sd1: 988161MB, 512 bytes/sector, 2023755653 sectors
root on sd1a (b768bd81a6b9a7f1.a) swap on sd1b dump on sd1b

Reply | Threaded
Open this post in threaded view
|

Re: blank screen

Theo de Raadt-2
> is somebody messing with the graphics stack by any chance?

It is probably rude to call steps-being-taken-toward-progress "messing"


Reply | Threaded
Open this post in threaded view
|

Re: blank screen

lvdd-2
On Sun, 11 Jun 2017 09:42:15 -0600
"Theo de Raadt" <[hidden email]> wrote:

> > is somebody messing with the graphics stack by any chance?  
>
> It is probably rude to call steps-being-taken-toward-progress "messing"
>
>

I am sorry - this wasn't meant to be as insult to anyone. As far as I
know 'messing' is used in english as well for a more colloquial speech
of saying 'somebody is changing things' - But what do I know - it is
not my primary language.

So please let me rephrase it.

Is somebody currently doing changes to the graphics stack? I would like
to report a problem because those possible changes might have a
negative impact on my system.

Better? :-)

Thanks
Lars

Reply | Threaded
Open this post in threaded view
|

Re: blank screen

Theo de Raadt-2
> On Sun, 11 Jun 2017 09:42:15 -0600
> "Theo de Raadt" <[hidden email]> wrote:
>
> > > is somebody messing with the graphics stack by any chance?  
> >
> > It is probably rude to call steps-being-taken-toward-progress "messing"
> >
> >
>
> I am sorry - this wasn't meant to be as insult to anyone. As far as I
> know 'messing' is used in english as well for a more colloquial speech
> of saying 'somebody is changing things' - But what do I know - it is
> not my primary language.
>
> So please let me rephrase it.
>
> Is somebody currently doing changes to the graphics stack? I would like
> to report a problem because those possible changes might have a
> negative impact on my system.

For about a week, snapshots have contained a prototype of the new
inteldrm codebase.  Thereby allowing people to report issues.

But saying "messing" really isn't helping.  A detailed bug report
helps.  1 line of whining doesn't.

Noone said snapshots would always work for everyone all the time.

Reply | Threaded
Open this post in threaded view
|

Re: blank screen

lvdd-2
On Sun, 11 Jun 2017 09:56:07 -0600
"Theo de Raadt" <[hidden email]> wrote:

>
> For about a week, snapshots have contained a prototype of the new
> inteldrm codebase.  Thereby allowing people to report issues.

Thank you. That was the answer to my question. And it was exactly that
- just a question.

>
> But saying "messing" really isn't helping.  A detailed bug report
> helps.  1 line of whining doesn't.
>
> Noone said snapshots would always work for everyone all the time.
>

I won't answer to that. See above.

Thanks

Lars


Reply | Threaded
Open this post in threaded view
|

Re: blank screen

acampbell
In reply to this post by Theo de Raadt-2
On 11 Jun 2017, Theo de Raadt wrote:

> > On Sun, 11 Jun 2017 09:42:15 -0600
> > "Theo de Raadt" <[hidden email]> wrote:
> >
> > > > is somebody messing with the graphics stack by any chance?  
> > >
> > > It is probably rude to call steps-being-taken-toward-progress "messing"
> > >
> > >
> >
> > I am sorry - this wasn't meant to be as insult to anyone. As far as I
> > know 'messing' is used in english as well for a more colloquial speech
> > of saying 'somebody is changing things' - But what do I know - it is
> > not my primary language.
> >
> > So please let me rephrase it.
> >
> > Is somebody currently doing changes to the graphics stack? I would like
> > to report a problem because those possible changes might have a
> > negative impact on my system.
>
> For about a week, snapshots have contained a prototype of the new
> inteldrm codebase.  Thereby allowing people to report issues.
>
> But saying "messing" really isn't helping.  A detailed bug report
> helps.  1 line of whining doesn't.
>
> Noone said snapshots would always work for everyone all the time.

Thanks, usefl - probably explains the firefox lockups I reported earlier.
--
Anthony Campbell http://www.acampbell.uk

Reply | Threaded
Open this post in threaded view
|

Re: blank screen

Sebastien Marie-3
In reply to this post by lvdd-2
On Sun, Jun 11, 2017 at 06:08:11PM +0200, lvdd wrote:

> On Sun, 11 Jun 2017 09:56:07 -0600
> "Theo de Raadt" <[hidden email]> wrote:
>
> >
> > For about a week, snapshots have contained a prototype of the new
> > inteldrm codebase.  Thereby allowing people to report issues.
>
> Thank you. That was the answer to my question. And it was exactly that
> - just a question.
>
> >
> > But saying "messing" really isn't helping.  A detailed bug report
> > helps.  1 line of whining doesn't.
> >
> > Noone said snapshots would always work for everyone all the time.
> >
>
> I won't answer to that. See above.
>

Hi Lars,

I think you miss the point of using snapshots: helping the project and
permit progress for everybody.

Please at least post a dmesg: developers will at least know on which
hardware there is a problem. A detailed bug report would be welcome too.

Thanks.
--
Sebastien Marie

Reply | Threaded
Open this post in threaded view
|

Re: blank screen

Sebastien Marie-3
On Sun, Jun 11, 2017 at 06:48:07PM +0200, Sebastien Marie wrote:
>
> Please at least post a dmesg

sorry, I just saw you posted it in your first message.
--
Sebastien Marie

Reply | Threaded
Open this post in threaded view
|

Re: blank screen

tomr
In reply to this post by lvdd-2

On 06/11/17 11:53, lvdd wrote:

> On Sun, 11 Jun 2017 09:42:15 -0600
> "Theo de Raadt" <[hidden email]> wrote:
>
>>> is somebody messing with the graphics stack by any chance?  
>>
>> It is probably rude to call steps-being-taken-toward-progress "messing"
>>
>>
>
> I am sorry - this wasn't meant to be as insult to anyone.
<snip>

I took "messing" here to be a term of familiar endearment. Undoubtedly
it was written with as much affection as respect for the very
step-being-taken-towards-progress mentioned. The use of English was,
IMHO, sound... but perhaps familiarity has bred contempt. Chill-pill-time.

Long live the messing!

Reply | Threaded
Open this post in threaded view
|

Re: blank screen

Stuart Henderson
On 2017-06-11, tomr <[hidden email]> wrote:

>
> On 06/11/17 11:53, lvdd wrote:
>> On Sun, 11 Jun 2017 09:42:15 -0600
>> "Theo de Raadt" <[hidden email]> wrote:
>>
>>>> is somebody messing with the graphics stack by any chance?  
>>>
>>> It is probably rude to call steps-being-taken-toward-progress "messing"
>>>
>>>
>>
>> I am sorry - this wasn't meant to be as insult to anyone.
><snip>
>
> I took "messing" here to be a term of familiar endearment. Undoubtedly
> it was written with as much affection as respect for the very
> step-being-taken-towards-progress mentioned. The use of English was,
> IMHO, sound... but perhaps familiarity has bred contempt. Chill-pill-time.
>
> Long live the messing!
>
>

If it was just minor tweaks then "messing" might be appropriate.

But this is a ~157,000 line 5MB diff.


Reply | Threaded
Open this post in threaded view
|

Re: blank screen

Mihai Popescu-3
In reply to this post by lvdd-2
> is somebody messing with the graphics stack by any chance?

Too much linux mailing list reading will eventualy distort your language.