Created attachment 36275 [details]
apport output at working state
Using the HP 550, it is impossible to use the Xserver without starting the BIOS changing nothing and ignoring the changes. Maybe it is a BIOS or Video BIOS bug, but it is the same problem at any Linux. I'm using ubuntu lucid lynx and made 2 different apport files. One at a working state and one at the not working state.
In the not working file you see the following failure message starting at line 1677:
../../intel/intel_bufmgr_gem.c:983: Error setting domain 613: Input/output error
(WW) intel(0): i830_uxa_prepare_access: bo map failed
Fatal server error:
Failed to submit batchbuffer: Input/output error
Please consult the The X.Org Foundation support
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
another difference can be seen at my attachment picture
Created attachment 36276 [details]
apport output at not working state
Created attachment 36277 [details]
screenshot with kompare
If you need more information, a BIOS or VIDEO BIOS dump, just ask.
This bug is very bad, because it brings the notebook to a non-bootable state.
The inteltool from coreboot project cannot read any Nortbridge data, so I don't know how to read out the state of the graphics adapter registers.
I hope you can help me.
Thank you very much.
Ouch, so unless you enter BIOS setup it looks like either your VBT (video bios table) or your GPU isn't set up properly so X can't start.
Does the kernel set modes correctly? I.e. do you see the kernel boot log at startup time?
To get the current graphics registers, you can use intel_reg_dumper from the intel-gpu-tools package. Having that from a broken boot might be useful.
(In reply to comment #4)
> Ouch, so unless you enter BIOS setup it looks like either your VBT (video bios
> table) or your GPU isn't set up properly so X can't start.
> Does the kernel set modes correctly? I.e. do you see the kernel boot log at
> startup time?
I think so, I see everything even the ubuntu splashscreen and the blinking points.
Everything is fine, even the background of the desktop is coming. but if he starts to create windows... then he produces noisy signs and it crashes.
> To get the current graphics registers, you can use intel_reg_dumper from the
> intel-gpu-tools package. Having that from a broken boot might be useful.
I will try this as soon as possible.
Thank you very much for the quick answer.
Created attachment 36304 [details]
Created attachment 36305 [details]
I just added the stdout-output of intel_reg_dumper at the working and at the not working state. It seems to be different, but I don't know anything so special.
I saw that there is a intel_reg_read and a intel_reg_write in that package. May I read out a working state and write it into the gpu before starting the Xserver?
Maybe this could be a quick workaround.
I hope this bug can be closed as quick a possible. Because the new Intel driver ist soo fast and notebook so nice...
Thank you very much one more time.
Ok this sounds different than I was first thinking then. Can you capture a video or pictures of the failing case? If the desktop is coming up ok but then it starts failing once GNOME apps start up, it could be a problem related to the gnome display manager...
Also, since it sounds like you're using ubuntu, please try the xorg edgers repo packages, including the kernel. That should help us narrow down this problem.
(In reply to comment #9)
> Ok this sounds different than I was first thinking then. Can you capture a
> video or pictures of the failing case? If the desktop is coming up ok but then
> it starts failing once GNOME apps start up, it could be a problem related to
> the gnome display manager...
The same happens with KDE, so I think it is the Xserver.
I will take a video and upload it to youtube ok?
(In reply to comment #10)
> Also, since it sounds like you're using ubuntu, please try the xorg edgers repo
> packages, including the kernel. That should help us narrow down this problem.
Please explain more exactly, what I should install and which logs I should upload.
Thanks for the help. :)
Yeah a youtube upload is fine. For xorg edgers you'll have to look through the ubuntu websites, I think there's a launchpad project for it.
Oh also I don't know what format
Err nevermind that last comment.
(In reply to comment #12)
> (In reply to comment #10)
> > Also, since it sounds like you're using ubuntu, please try the xorg edgers repo
> > packages, including the kernel. That should help us narrow down this problem.
> Please explain more exactly, what I should install and which logs I should
To install the testing packages for Ubuntu,
To update the kernel, you'll have to specify that by hand. However, if it is booting fine and dies when using X, a good first step will be just updating the user space components (as above).
Created attachment 36710 [details]
the boot screen is working
Created attachment 36711 [details]
but the login screen is broken
Created attachment 36712 [details]
after 5 seconds it changes to this
Created attachment 36713 [details]
normally in a working state the login screen looks like this
Now I installed all the stuff from the ppa, but the problem is still the same.
This is the link to the video. The quality is bad, but you can see the problem anyway.
With your xorg-edgers packages installed, I cannot create an apport-bug-report with ubuntu-bug, because it is not an "ubuntu package". What log files do you need?
Does the kernel still detect a GPU hang? [Check dmesg.] If so, then the /sys/kernel/debug/dri/0/i915_error_state is the most interesting file, provided you have also installed a post-2.6.34 kernel.
That failure mode doesn't immediately ring any alarms bells. Though I think it might be partially rendered as a result of disabling acceleration following a GPU hang.
Hmm, the only other point of interest seems to be that FBC differs between the working and non-working configs.
There is an error_state file I will upload it. The dmesg file I will upload too.
Is this enough? Feel free to ask for more information you need the solve this bug. ;)
Created attachment 36751 [details]
the newest dmesg file
Created attachment 36752 [details]
the error_state file
Created attachment 36753 [details]
all files from the kernel debug folder and the dmesg file packed
In the dmesg file I found the following lines, maybe it gives an hint:
[ 1.488375] agpgart-intel 0000:00:00.0: Intel 965GME/GLE Chipset
[ 1.488817] agpgart-intel 0000:00:00.0: detected 7676K stolen memory
[ 1.493287] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000
[ 1.512236] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 1.512242] i915 0000:00:02.0: setting latency timer to 64
[ 1.528894] alloc irq_desc for 44 on node -1
[ 1.528898] alloc kstat_irqs on node -1
[ 1.528908] i915 0000:00:02.0: irq 44 for MSI/MSI-X
[ 1.528918] [drm] set up 7M of stolen space
[ 1.634568] [drm] initialized overlay support
What does "stolen memory" mean?
Maybe it is a memory initialization error?
(In reply to comment #28)
> What does "stolen memory" mean?
"Stolen memory" is region of memory reserved by the BIOS for the sole use of the GPU (i.e. it is not available for the rest of the system). GEM has little use for this (as the emphasis is on dynamic allocation of memory to the GPU, thus allowing the memory to be returned to the CPU depending upon system usage), but a few chipsets do require some stolen memory for pages that must be physically contiguous, the framebuffer compression being the major one.
The bug itself, I've stalled upon. I don't have enough information within the error dump to check the programs and samplers being executed. When I get some time I will work upon improving the debugging facilities for i965+. In the meantime, if you can think of anything that might differ on your system between the two conditions, or find another way to reproduce the same bug, that may grant enough insight in order to determine the cause.
Reassigning to Chris so he has another excuse to improve our debug infrastructure even more. ;)
Frank, does this issue still occur?
No, I sold the Notebook. So I don't have any problems at all. ;)