Bug#655404: firmware-linux-nonfree Radeon R300-family problem

2012-01-10 Thread bugreport

Package: firmware-linux-nonfree
Version: 0.34
Severity: low

Hi there,

I recently tried to install a couple distributions on a Fujitsu Amilo M 
1420 laptop. Kubuntu 11.10, Fedora 16 and PCLinuxOS KDE 2011 all crashed 
either during install or when booting the installed system. Debian 
Squeeze installed fine. Until I installed the firmware-linux-nonfree 
package to get rid of the missing microcode error message from xorg. If 
firmware-linux-nonfree is installed under Wheezy the system won't boot 
properly. In Squeeze it is still possible to remove the 
firmware-linux-nonfree package and reboot, but you first have to stop 
the error messages spamming the console. X11 won't work at all. Trying 
to use it will lock the machine.


This problem could be related to the Xorg-Radeon driver as well as a 
hardware bug in either the ATI Mobility Radeon 9600 PRO (RV350) chip 
generally, of this particular laptop or even this very machine. 
Nonetheless, removing or not installing firmware-linux-nonfree is my 
current workaround. The graphics still work fine.


thx,

Malte



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f0cafda.6000...@2c2.de



Bug#651121: After xm restore dumU freezes

2011-12-05 Thread debian bugreport
Package: linux-image-2.6.32-5-xen-amd64
Version: 2.6.32-38

Steps to reproduce:
/usr/sbin/xm save TEST /xen/domains/TEST/checkpoint
/usr/sbin/xm restore /xen/domains/TEST/checkpoint
xm console # hangs, no input possible

Worked with older version about 2 months ago. Not working since update to 
2.6.32-38.
___
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1236542851.539564.1323124640899.JavaMail.fmail@mwmweb006



Bug#601823: Root on LVM on Raid1 won't boot custom kernel, stock kernel works fine

2010-10-29 Thread bugreport

Package: initramfs-tools
Version: 0.98.5
Severity: wishlist

Hi there,

this is most likely not a bug, but rather an error on my part, but I 
thought you might be interested in this. I installed a Squeeze system on 
an LVM sitting on a Linux softraid 1 array. I have a seperate boot 
partition that I finally put on a raid as well, but also tested the 
following when the boot partition was still on a normal partition on 
the first disk.
The stock kernel boots fine, but I wanted to build my own kernel. I 
build it using make-kpkg --uc --us --bzimage --initrd kernel_image. All 
necessary kernel options are set correctly (checked that four times) for 
both initramfs, dm and raid. But still the kernel doesn't boot into 
root. It drops right into busybox when it tries to access root. It even 
says it mounts the other raid (the one that boot is now sitting on).


Don't know if this is the right place, but in the past I have build a 
lot of kernels and installed lots of systems on softraid. Now on Squeeze 
it won't work in combination (softraid and my own kernel).


Maybe you will be able to reproduce this one easily. I use AMD64 
architecture btw.


I confirmed that initramfs is working, because it is loading a bunch of 
modules for the network and block devices.


Error message is:
mdadm: No devices listed in conf file were found.
Failure: failed to assemble all arrays

And it does load the raid1 modules right above that error message.

append=rootdelay=10 also didn't help.

Thx,

Malte



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ccb6ce9.6040...@2c2.de



Bug#576274: I finally have a meaningful log to report

2010-05-27 Thread bugreport
Hi there,

I am currently running linux-image-2.6.32-5-686 and I checked /var/log/kern.log 
instead of /var/log/Xorg.0.log for clues after another white screen (I am 
pretty tired of testing suspend, because the white screen always happens when I 
am right in the middle of work), and here it is. Finally some meaningful log 
output to back up the bug report:

May 27 09:15:29 voltaire kernel: [16440.384972] render error detected, EIR: 
0x0010
May 27 09:15:29 voltaire kernel: [16440.384979] page table error
May 27 09:15:29 voltaire kernel: [16440.384981]   PGTBL_ER: 0x0010
May 27 09:15:29 voltaire kernel: [16440.384986] [drm:i915_handle_error] *ERROR* 
EIR stuck: 0x0010, masking
May 27 09:15:29 voltaire kernel: [16440.384997] render error detected, EIR: 
0x0010
May 27 09:15:29 voltaire kernel: [16440.385000] page table error
May 27 09:15:29 voltaire kernel: [16440.385002]   PGTBL_ER: 0x0010

For almost an hour nothing is in there before that time and nothing happens 
after that until I shut the machine down. 

Thx,

Malte

Problem remains the same, computer is fine after normal boot, but the screen 
goes white after pm-suspend, wake up, and then some time after that.

Here is some log output from the wakeup about an hour earlier:

May 27 08:23:03 voltaire kernel: [13290.179679] i915 :00:02.0: PCI INT A 
disabled
May 27 08:23:03 voltaire kernel: [13290.192162] i915 :00:02.0: power state 
changed by ACPI to D3
May 27 08:23:03 voltaire kernel: [13290.336063] ehci_hcd :00:1d.7: power 
state changed by ACPI to D3
May 27 08:23:03 voltaire kernel: [13290.360073] uhci_hcd :00:1d.1: power 
state changed by ACPI to D3
May 27 08:23:03 voltaire kernel: [13290.384073] uhci_hcd :00:1d.0: power 
state changed by ACPI to D3
May 27 08:23:03 voltaire kernel: [13290.424066] ACPI: Preparing to enter system 
sleep state S3
May 27 08:23:03 voltaire kernel: [13290.596383] Disabling non-boot CPUs ...
May 27 08:23:03 voltaire kernel: [13290.596500] Extended CMOS year: 2000
May 27 08:23:03 voltaire kernel: [13290.596500] Back to C!
May 27 08:23:03 voltaire kernel: [13290.596500] CPU0: Thermal monitoring 
enabled (TM2)
May 27 08:23:03 voltaire kernel: [13290.596500] Extended CMOS year: 2000
May 27 08:23:03 voltaire kernel: [13290.596500] Force enabled HPET at resume
May 27 08:23:03 voltaire kernel: [13290.596500] ACPI: Waking up from system 
sleep state S3
May 27 08:23:03 voltaire kernel: [13291.088143] agpgart-intel :00:00.0: 
restoring config space at offset 0x1 (was 0x900106, writing 0x20900106)
May 27 08:23:03 voltaire kernel: [13291.088167] i915 :00:02.0: restoring 
config space at offset 0x1 (was 0x93, writing 0x97)
May 27 08:23:03 voltaire kernel: [13291.088186] pci :00:02.1: restoring 
config space at offset 0x4 (was 0x0, writing 0x8020)
May 27 08:23:03 voltaire kernel: [13291.088219] pcieport :00:1c.0: 
restoring config space at offset 0x9 (was 0x1fff1, writing 0x80118001)
May 27 08:23:03 voltaire kernel: [13291.088227] pcieport :00:1c.0: 
restoring config space at offset 0x7 (was 0xf0, writing 0x7070)
May 27 08:23:03 voltaire kernel: [13291.088241] pcieport :00:1c.0: 
restoring config space at offset 0x1 (was 0x100107, writing 0x100507)

and then another couple of lines concerning the i915:

May 27 08:23:03 voltaire kernel: [13291.255521] i915 :00:02.0: power state 
changed by ACPI to D0
May 27 08:23:03 voltaire kernel: [13291.255573] i915 :00:02.0: power state 
changed by ACPI to D0
May 27 08:23:03 voltaire kernel: [13291.255583] i915 :00:02.0: PCI INT A - 
GSI 16 (level, low) - IRQ 16
May 27 08:23:03 voltaire kernel: [13291.255589] i915 :00:02.0: setting 
latency timer to 64



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100527073332.132...@gmx.net



Bug#576274: bug still present in current kernel from Sid

2010-04-21 Thread bugreport
Hi,

I tested the current linux-image-2.6.32-4-686 in Sid and the problem is indeed 
still there. Current workaround: Don't use suspend.

I use the laptop while testing and I always lose a little of the stuff I work 
on when the screen goes dark (the stuff not saved yet). So I really recommend 
the workaround for now.

Cheers,

Malte
-- 
Feel free - 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/2010042612.156...@gmx.net



Bug#576274: This time crash with log output

2010-04-08 Thread bugreport
I finally got a crash with a log output. The strange thing is that this time it 
was an X sever crash instead of just the blank screen.

I had about three to four pm-suspend (without --auto-quirks). This time the 
keyboard also did not work any more and the screen went black with hyphen bar 
in the upper right corner. Font size looked like the one when not running X.
-- 
Feel free - 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail


Xorg.0.log
Description: Binary data


Bug#576274: additional info

2010-04-06 Thread bugreport
I will continue to test new kernels as they come. This has been a long standing 
issue. In early 2.6.32 kernels I had an error message right after Grub. This 
went away with later versions. At the same time my own compiled kernels (from 
recent linux-source-2.6.32) had a blank screen right after Grub (instead of the 
error message I got with the precompiled kernels), but otherwise booted fine. I 
just couldn't get them to display anything. 
I think they put a lot of work into the Intel graphics driver in the kernel 
recently. That is why the error message dissapeared. 

I think the screen blanking only comes after a pm-suspend. Usually when 
browsing the web. I tried both pm-suspend with and without --auto-quirks. 

I don't think it has anything to do with Xorg.conf, since I both tried with and 
without one. 

So it comes back down to the basic kernel. And I don't think I configured 
anything there at all, which leads me to think that it might be a real bug 
after all.

I did check for a bit if other people did report this already, but didn't find 
anything matching my problem very good. Could you keep the bug open for recent 
kernels please? Maybe someone else will come forward with the same problem.

I will see about 2.6.33 from experimental. My internet connection is currently 
a little slow, so I might only do this in a week or two.

Thank you so far for bearing with me.

Malte

 Original-Nachricht 
 Datum: Tue, 6 Apr 2010 04:36:52 +0200
 Von: maximilian attems m...@stro.at
 An: bugrep...@public-files.de
 CC: 576...@bugs.debian.org
 Betreff: Re: Bug#576274: additional info

 On Mon, 05 Apr 2010, bugrep...@public-files.de wrote:
 
  I don't have hotkey-setup installed 
 
 good.
  
  output of lscpi -vvv attached
  
  Thanks for caring so much. I am still not entirely convinced that this
  is a genuine bug (which is why I waited so long reporting it), because
  the graphics chip in use (and the rest of the hardware) is so
  widespread, that I can't be the only Debian user experiencing this.
  
  Malte
 
 hmmm,
 could you check against 2.6.32-11 should land next days in unstable?
 
 also there is 2.6.33 in experimental, don't think it should make
 a difference but better check.
 
 thanks

-- 
Feel free - 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100406154357.299...@gmx.net



Bug#576274: additional info

2010-04-04 Thread bugreport
Hi there,

with some help from one of the maintainers I found the latest package from sid 
and installed it:
http://packages.debian.org/sid/linux-image-2.6.32-4-686

But the problem remains unchanged. And I still don't have any meaningful log 
reports. I wanted to add that in former kenel versions (pre 2.6.31) the problem 
was less frequent, but more severe (e.g. crash also took down x input) . So it 
might be a different problem.

Also when the screen goes blank it sometimes takes on different shades of grey. 
From almost white to grey to black. Backlight is on. And when rebooted the 
screen stays that way until the screen powers all the way down.

With the new kernel version I had an uptime of about 3 hours and only two 
pm-suspends until the problem occured.

Thanks,

Malte
-- 
GMX.at - Österreichs FreeMail-Dienst mit über 2 Mio Mitgliedern
E-Mail, SMS  mehr! Kostenlos: http://portal.gmx.net/de/go/atfreemail



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100404102300.77...@gmx.net



Bug#576274: infrequent, but persistent blank screens with Intel GMA900

2010-04-02 Thread bugreport
Package: linux-image-2.6.32-3-686
Version: 2.6.32-9

This bug also applies to linux-source and linux-image packages going back to at 
least 2.6.30

I have not reported this, because I have no useful log file entries. And I 
thought because the chipset is so common that someone else will report it more 
properly (with more information).

I have tried different linux-source packages as well as linux-image packages.

The problem usually occurs after some time and one or two software suspends 
(pm-suspend  --auto-quirks). Shortly before it the screen will usually jump 
horizontally. The jumping will not stop if not changing virtual screens in X. 
Then, after some time it will get really bad. Then the screen suddenly blanks 
(backlight will stay on). It only effects the screen. Everything else will 
still work, confirmed by remote login via ssh.

Hardware:
http://www.thinkwiki.org/wiki/Category:X41
http://www.thinkwiki.org/wiki/Intel_915GM

Thanks,

Malte
-- 
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100402131521.314...@gmx.net