3.5-rc6 fb hw inteldrmfb

3.5-rc6 fb hw inteldrmfb

[werner]

On a computer of someone else, on which today I tried to 
install 3.5-rc6 (what on my computer and on an HP pavillon 
laptop runs without problem - on the laptop however needs 
ircpoll otherwhise don't find the harddisk), few seconds 
after start booting it sticks and don't continue longer 
(reboot not possible with Ctr-Alt-C but only pressing the 
reboot button), the last message is:   "conflicting fb hw 
usage inteldrmfb vs VESA VGA - removing generic driver" 
        then the cursor stops blinking, and the computer 
sticks.
With 3.4 the same computer runs since weeks without 
problems.  So, that's a regression.

Inspection of syslog, messages, debug don't show anything 
from this boot, it seems before the crash it hasn't nor 
time to log something.

Below is the lspci of that computer.


wl




00:00.0 Host bridge: Intel Corporation 82945G/GZ/P/PL 
Memory Controller Hub (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 
82945G/GZ Integrated Graphics Controller (rev 02)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 
Family) High Definition Audio Controller (rev 01)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) 
PCI Express Port 1 (rev 01)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) 
PCI Express Port 2 (rev 01)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) 
PCI Express Port 3 (rev 01)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) 
PCI Express Port 4 (rev 01)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 
Family) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 
Family) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 
Family) USB UHCI Controller #3 (rev 01)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 
Family) USB UHCI Controller #4 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 
Family) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge 
(rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 
Family) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 
Family) IDE Controller (rev 01)
00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH 
(ICH7 Family) SATA IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) 
SMBus Controller (rev 01)
05:00.0 Ethernet controller: Broadcom Corporation 
NetXtreme BCM5751 Gigabit Ethernet PCI Express (rev 01)

---
Professional hosting for everyone - http://www.host.ru

Re: 3.5-rc6 fb hw inteldrmfb

[Dave Airlie]

cc'ing Daniel,

On Sat, Jul 14, 2012 at 12:18 PM, werner <w.landgraf@ru.ru> wrote:
> On a computer of someone else, on which today I tried to install 3.5-rc6
> (what on my computer and on an HP pavillon laptop runs without problem - on
> the laptop however needs ircpoll otherwhise don't find the harddisk), few
> seconds after start booting it sticks and don't continue longer (reboot not
> possible with Ctr-Alt-C but only pressing the reboot button), the last
> message is:   "conflicting fb hw usage inteldrmfb vs VESA VGA - removing
> generic driver"        then the cursor stops blinking, and the computer
> sticks.

wierd, are you passing a vga= to the kernel? or is grub2 going graphical?

also the dmesg from 3.4 might be good.

Dave.

Re: 3.5-rc6 fb hw inteldrmfb

[Daniel Vetter]

On Sat, Jul 14, 2012 at 5:23 AM, Dave Airlie <airlied@gmail.com> wrote:
> On Sat, Jul 14, 2012 at 12:18 PM, werner <w.landgraf@ru.ru> wrote:
>> On a computer of someone else, on which today I tried to install 3.5-rc6
>> (what on my computer and on an HP pavillon laptop runs without problem - on
>> the laptop however needs ircpoll otherwhise don't find the harddisk), few
>> seconds after start booting it sticks and don't continue longer (reboot not
>> possible with Ctr-Alt-C but only pressing the reboot button), the last
>> message is:   "conflicting fb hw usage inteldrmfb vs VESA VGA - removing
>> generic driver"        then the cursor stops blinking, and the computer
>> sticks.
>
> wierd, are you passing a vga= to the kernel? or is grub2 going graphical?
>
> also the dmesg from 3.4 might be good.

Also if you could test 3.5-rc5 that'd be interesting, just to check
whether the "removing generic driver" which is new in -rc6 is the
cause of this or whether we have a bigger problem with the i915 driver
crashing in 3.5-rc.

Thanks, Daniel
-- 
Daniel Vetter
daniel.vetter@ffwll.ch - +41 (0) 79 365 57 48 - http://blog.ffwll.ch

Re: 3.5-rc6 fb hw inteldrmfb

[werner]

[-- Attachment #1: Type: text/plain, Size: 2567 bytes --]

Enclosed syslog, debug and the last messages copied from /var/log .   (i send that from my own homecomputer mail service, as ru.ru has no space for anex files)

I can try out 3.5-rc1 what I have compiled too 


Pls observe that the runs with 3.5-rc6 are before the last run (under which these copies were made), I see no trace of them in the logs, the computer crashed within a few seconds after booting start, appearently before it could write something into the log files or before it's synced.    With 3.4 and 2.6.26.2 the computer works normal.  

The command line is the same as on my own computer, see below;  kmemleak=off and irqpoll were tried out also at that computer but without success i.e. it sticked/crashed too  .  On my own computer 3.5-rc6 works almost normally, but it has a nvidia grafic card,  also a laptop for another friend where I installed it yesterday don't give problem but it has ati grafic card.


wl
============

  boot =  /dev/sda   
  root=/dev/sda1
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
#
# SYS_Linux: Zeilen mit root = werden bei der Installierung gel�scht,
# daher diese Option als separate Zeile schreiben, nicht in append = ...
append="splash=silent devfs=nomount noapic nolapic acpi=ht"
message = /boot/boot_message.txt
prompt
menu-scheme=Wb 
timeout = 50
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# End LILO global section
# pci=off  rootfstype=ext4dev  rw  acpi=ht

image = /boot/vmlinuz-3.5-rc6-i486-1sys
  root = /dev/sda1
  label = "35rc6"
  read-only
  vga=791   # 785 fuer kleine laptops
  append="4 root=/dev/sda1 devfs=nomount kmemleak=on   nomodeset noapic nolapic acpi=ht rootwait percpu_alloc=page"


#
image = /boot/vmlinuz-3.5-rc1-i486-1sys
  root = /dev/sda1
  label = "35rc1"       
  read-only
  vga=791
  append="4 root=/dev/sda1 devfs=nomount kmemleak=on nomodeset noapic nolapic acpi=ht rootwait percpu_alloc=page"
#

#
#
image = /boot/vmlinuz-2.6.26.2-i486-1sys
  root = /dev/sda1
  label = "26262"
  read-only
  vga=791
  append="4 root=/dev/sda1 devfs=nomount noapic nolapic acpi=ht "
    
#
other = /dev/sda4
label = MINIX
#
# master-boot
# loader = os2_d
#
#
#

[-- Attachment #2: syslog.bz2 --]
[-- Type: application/octet-stream, Size: 132087 bytes --]

[-- Attachment #3: lastmessages.bz2 --]
[-- Type: application/octet-stream, Size: 76666 bytes --]

[-- Attachment #4: debug.bz2 --]
[-- Type: application/octet-stream, Size: 154477 bytes --]

Re: 3.5-rc6 fb hw inteldrmfb

[werner]

[-- Attachment #1: Type: text/plain, Size: 1985 bytes --]


As said, with 3.5-rc6 with vga=791 , on someone else's computer with intel grafics  ,  it sticks/crashs within 5 (or even 3) seconds after start booting, long time before trying to switch into grafic mode.   That happened today again, like yesterday. In the logfiles yesterday I found nothing.

Now I tried also the same, 3.5-rc6 but with vga=0 .    Then the booting process goes forward, but later, at the time it tries to switch into the grafic mode, it sticks in the same way.  Reboot with CTRL+ALT+C is not possible, one have to press the reboot button.

With 3.5-rc1 and vga=791 (what on my own computer with nv grafic card runs normally), on that said computer with intel grafic card,  it don't stop in early stage, but continues, but at the time of switching in grafic mode, the screen stays black.    However, now it's possible to reboot wich CTRL+ALT+C , so I suppose that different to 3.5-rc6 the computer didn't really stick/crash (but the grafic stays just invisible) 

With 3.4-rc5 that computer runs normal.


I forget to mention, that on my own computer, what works almost normally with 3.5-rc6 ,  rsync don't return (i.e. after type rsync in text mode, it continues eternally, neither can be stopped with CTRL-C).   That didn't happen with a next laptop of someone else where I installed 3.5-rc6 yesterday (which has ati grafics).   However, I suppose that has nothing to do with the current problem, but with some other hardware.



Enclosed are the new logfiles, of today, of the trying out 's explained above, of that computer which sticks/crashs with 3.5-rc6.  I send you that quickly but I don't have tiome now to inspect them; I suppose there is again nothing from the 3.5-rc6 vga=791 run which crashs in early stage of booting, but perhaps there is something from 3.5-rc6 vga=0 which crashs only later (at the time switching to grafics) as explained above.   Added is also, for comparison, dmesg of the run with 3.4-rc5 what's without that grafic problem.


wl

[-- Attachment #2: syslog.bz2 --]
[-- Type: application/octet-stream, Size: 9102 bytes --]

[-- Attachment #3: lastmessages.bz2 --]
[-- Type: application/octet-stream, Size: 56528 bytes --]

[-- Attachment #4: debug.bz2 --]
[-- Type: application/octet-stream, Size: 5997 bytes --]

[-- Attachment #5: dmesg.bz2 --]
[-- Type: application/octet-stream, Size: 8291 bytes --]

Re: 3.5-rc6 fb hw inteldrmfb

[Daniel Vetter]

On Sat, Jul 14, 2012 at 2:33 PM,  <werner@guyane.yi.org> wrote:
> With 3.4-rc5 that computer runs normal.

I've looked a bit at the logfiles and dmesg contains tons of stuff
that I didn't expect to be there and the other's contain tons of
unrelated stuff (e.g. they contain a few days worth of data). So I
couldn't figure out anything with that.
The difference betwen rc5 and rc6 is simply due to the firmware
kicking, but since rc5 dies in a similar fashion (but simply later) I
think the bug has been introduced earlier.

I guess we're down to a bisect, since 3.4-rc5 seems to work for you.
Can you please to that?

Thanks, Daniel
-- 
Daniel Vetter
daniel.vetter@ffwll.ch - +41 (0) 79 365 57 48 - http://blog.ffwll.ch