Bug 1733

Can you capture the oops ?

either from the logs, or with a camera picture of the screen

CC: (none) => tmb
Assignee: bugsquad => tmb

Here is the /var/log/kernel/error (I cleaned up the file before unplugging the power cord):

It seems somthing is wrong with the rt61pci.. 

Jun 10 13:32:49 kharas kernel: BUG: unable to handle kernel NULL pointer dereference at   (null)
Jun 10 13:32:49 kharas kernel: IP: [<f4d93e29>] rt61pci_config+0x19/0x280 [rt61pci]
Jun 10 13:32:49 kharas kernel: Oops: 0000 [#1] SMP 
Jun 10 13:32:49 kharas kernel: last sysfs file: /sys/devices/LNXSYSTM:00/device:00/PNP0A03:00/device:14/PNP0C09:00/PNP0C0A:00/power_supply/BAT1/present
Jun 10 13:32:49 kharas kernel: Process irq/22-0000:05: (pid: 2433, ti=f00f2000 task=efa06480 task.ti=f00f2000)
Jun 10 13:32:49 kharas kernel: Stack:
Jun 10 13:32:49 kharas kernel: Call Trace:
Jun 10 13:32:49 kharas kernel: Code: 6d fe ff ff e8 89 6c 3b cb 89 f6 8d bc 27 00 00 00 00 55 89 e5 57 56 53 83 ec 1c 3e 8d 74 26 00 89 c3 8b 02 89 cf 89 d6 8b 40 18 <8b> 08 85 c9 75 59 8b 93 74 03 00 00 8b 83 38 02 00 00 0f b6 92 
Jun 10 13:32:49 kharas kernel: EIP: [<f4d93e29>] rt61pci_config+0x19/0x280 [rt61pci] SS:ESP 0068:f00f3ef4
Jun 10 13:32:49 kharas kernel: CR2: 0000000000000000
Jun 10 13:32:49 kharas kernel: exiting task "irq/22-0000:05:" (2433) is an active IRQ thread (irq 22)
Jun 10 13:33:02 kharas kernel: phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 0.
Jun 10 13:33:02 kharas kernel: Please file bug report to http://rt2x00.serialmonkey.com.
Jun 10 13:33:03 kharas kernel: phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 0.
Jun 10 13:33:03 kharas kernel: Please file bug report to http://rt2x00.serialmonkey.com.
Jun 10 13:33:08 kharas kernel: phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 0.
Jun 10 13:33:08 kharas kernel: Please file bug report to http://rt2x00.serialmonkey.com.
Jun 10 13:33:08 kharas kernel: phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 0.
Jun 10 13:33:08 kharas kernel: Please file bug report to http://rt2x00.serialmonkey.com.
Jun 10 13:33:09 kharas kernel: phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 0.
Jun 10 13:33:09 kharas kernel: Please file bug report to http://rt2x00.serialmonkey.com.
Jun 10 13:39:05 kharas kernel: fb: conflicting fb hw usage radeondrmfb vs VESA VGA - removing generic driver
Jun 10 13:39:05 kharas kernel: mmc0: Unknown controller version (16). You may experience problems.

I think something's wrong with rt61pci when activating power savings if msi_laptop is not loaded... 

Now I briefly saw a battery discharged,need to suspend -like message before the oops... 

And now? Go without battery information (non blacklisting msi_laptop) or risking oopses while removing power supply (blacklisting the module)? Amletic situation. :)

tmb: is there anything you can do for this bug ?

CC: (none) => stormi

If you need something, the laptop is currently in low use, so I can try and install anything from cauldron or testing... I think it could be something in the configurations, since in mandriva 2010 it worked fine (did not try 2011).

pinging. because nothing happened to this report since more than 3 months ago, and it still has the status NEW or REOPENED


@ Thomas
Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.

CC: (none) => marja11

I was researching possible solutions (key-words in your bug), and looking at your bug and thought some of these possibilities might help...

...got some questions....

Did you update BIOS or replace the battery? If yes, you may need to reset some levels. With an Acer I have use of, you would need to remove power and battery, and then press power and reset for X amount of time to reset the battery power levels (proper reset method on Acer website). Your MSI probably has a similar cmos reset procedure to make sure you have the correct battery levels for full and empty.

If a battery is close to dead (not holding a charge), you may also get some similar problem. When it oops, does the computer shutdown? or simply dies?
Try powering up, go into BIOS mode (not into linux yet), and simply wait, next unplug the power, if the laptop dies fairly quickly, then I'd look at the battery as the suspect, time to get another battery.

You mention blacklisted module... it could be that it's blacklisted because it is incomplete or there is a problem with BIOS itself.
http://linux.slashdot.org/story/08/07/25/1150218/mobo-manufacturer-foxconn-refuses-to-support-linux
Are you running the latest BIOS, just to make sure any possible problems may be fixed already?

CC: (none) => digital

Hi there.
Simple answers first :)

The battery is fine, if I boot from battery when it's fully charged, I get more that 1 hour of with no particular power saving mode (that is cpu frequency get scaled, but no standby whatsoever). I did not do the bios-only test because I can really get the desktop experience right in this hour.

Concerning BIOS. I did a full upgrade a while ago (the motherboard is MSI, as the laptop) and found the wireless driver had issues, so I looked for all availlable bioses and rolled back. You can find the history of the msi support in this forum (I'm Palin there)

http://forum-en.msi.com/index.php?topic=134530.0

So, I could try to upgrade the bios to the latest version, now I know the version to roll back to if the wireless dies again.

Should I try that?

I updated the bios to the latest version from MSI.

Mageia 1 behave the same.

I installed Mageia 2 beta, which was released yesterday. I had to blacklist msi_laptop for the battery meter to work, but now everything seems to work fine. I downloaded from the non_free repository the rt61_firmware to make the wireless work.

I think Mageia 2 has done a nice job... 

now for another matter entirely I have to know how to make the... nice Gnome 3 to work in non-fallback mode. I stick to KDE4 right now. :) But this is another issue I'll try to resolve by myself.

(In reply to comment #9)

> 
> now for another matter entirely I have to know how to make the... nice Gnome 3
> to work in non-fallback mode. I stick to KDE4 right now. :) But this is another
> issue I'll try to resolve by myself.

another user said that when you log out of Gnome/fallback, that it is possible to login to Gnome 3 then. HTH

@Marja
Thank you but "deep" debugging told me that someone in both the free radeon driver and in fglrx removed 3d support for my video card in recent xorg versions. 

In Mageia 1.0 worked fine. I did not notice it because apparently the composer (eg. compiz) works. 

I like when a perfectly working and not so obsolete piece of hardware get obsoleted, I mean it's a notebook that went out with Vista, and many people still use pc that came with xp preinstalaled :)

So, no Gnome3, I'll stick to XFCE.

To try a decent version of Gnome3, I'll go out of my way and try to install it on my macbook pro.

For maintainers: the original bug I think it could be closed now. It's fixed in the Beta (maybe on MSI s271 msi_laptop should be blackisted by default)

After a massive upgrade today, Gnome3 started to work all by itself! :)

(In reply to comment #11)
> For maintainers: the original bug I think it could be closed now. It's fixed in
> the Beta (maybe on MSI s271 msi_laptop should be blackisted by default)
ok


(In reply to comment #12)
> After a massive upgrade today, Gnome3 started to work all by itself! :)

great

Status: NEW => RESOLVED
Resolution: (none) => FIXED