Bug#570490: linux-image-2.6.32-2-amd64: cannot unload radeon with KMS enabled
Package: linux-2.6
Version: 2.6.32-8
Severity: normal
When kms is enabled the radeon module cannot be unloaded. rmmod
complains that the module is busy while the X server is not running.
This is different from my experience with intel KMS and quite annoying.
-- Package-specific info:
** Version:
Linux version 2.6.32-2-amd64 (Debian 2.6.32-8) (ben@decadent.org.uk) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Fri Feb 12 00:01:47 UTC 2010
** Kernel log:
[ 7.672185] i801_smbus 0000:00:1f.3: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[ 8.260908] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input4
[ 8.261058] ACPI: Power Button [PWRB]
[ 8.261200] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input5
[ 8.261316] ACPI: Power Button [PWRF]
[ 8.372173] processor LNXCPU:00: registered as cooling_device0
[ 11.090638] Adding 4883720k swap on /dev/sda6. Priority:-1 extents:1 across:4883720k
[ 11.108580] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
[ 11.108778] EXT3 FS on sda7, internal journal
[ 11.377985] loop: module loaded
[ 11.485276] vboxdrv: Trying to deactivate the NMI watchdog permanently...
[ 11.485280] vboxdrv: Warning: 2.6.31+ kernel detected. Most likely the hardware performance
[ 11.485282] vboxdrv: counter framework which can generate NMIs is active. You have to prevent
[ 11.485284] vboxdrv: the usage of hardware performance counters by
[ 11.485285] vboxdrv: echo 2 > /proc/sys/kernel/perf_counter_paranoid
[ 11.485416] vboxdrv: Found 1 processor cores.
[ 11.485764] VBoxDrv: dbg - g_abExecMemory=ffffffffa02ba1a0
[ 11.486230] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
[ 11.486233] vboxdrv: Successfully loaded version 3.1.2_OSE (interface 0x00100001).
[ 11.668092] [drm] Initialized drm 1.1.0 20060810
[ 11.739410] pci 0000:04:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 11.739417] pci 0000:04:00.0: setting latency timer to 64
[ 11.740024] [drm] Initialized radeon 1.31.0 20080528 for 0000:04:00.0 on minor 0
[ 11.807997] w83627ehf: Found W83627DHG chip at 0x290
[ 11.808289] ACPI: I/O resource w83627ehf [0x295-0x296] conflicts with ACPI region HWRE [0x290-0x299]
[ 11.808339] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 11.822083] coretemp coretemp.0: Using relative temperature scale!
[ 12.978620] fuse init (API version 7.13)
[ 13.463734] REISERFS (device sda5): found reiserfs format "3.6" with standard journal
[ 13.463760] REISERFS (device sda5): using ordered data mode
[ 13.469910] REISERFS (device sda5): journal params: device sda5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[ 13.471237] REISERFS (device sda5): checking transaction log (sda5)
[ 13.527600] REISERFS (device sda5): Using r5 hash to sort names
[ 13.568077] kjournald starting. Commit interval 5 seconds
[ 13.568228] EXT3 FS on sda8, internal journal
[ 13.568234] EXT3-fs: mounted filesystem with ordered data mode.
[ 13.614133] kjournald starting. Commit interval 5 seconds
[ 13.614312] EXT3 FS on sda3, internal journal
[ 13.614319] EXT3-fs: mounted filesystem with ordered data mode.
[ 13.652385] kjournald starting. Commit interval 5 seconds
[ 13.652544] EXT3 FS on sda9, internal journal
[ 13.652551] EXT3-fs: mounted filesystem with ordered data mode.
[ 14.804608] Bridge firewalling registered
[ 14.813630] device eth0 entered promiscuous mode
[ 14.818016] alloc irq_desc for 27 on node -1
[ 14.818025] alloc kstat_irqs on node -1
[ 14.818045] atl1 0000:02:00.0: irq 27 for MSI/MSI-X
[ 14.818148] atl1 0000:02:00.0: eth0 link is up 100 Mbps full duplex
[ 14.827723] tapbr: port 1(eth0) entering learning state
[ 24.864026] tapbr: no IPv6 routers present
[ 24.984027] eth0: no IPv6 routers present
[ 29.824031] tapbr: port 1(eth0) entering forwarding state
[ 33.801711] Loading iSCSI transport class v2.0-870.
[ 33.834733] iscsi: registered transport (tcp)
[ 33.929247] iscsi: registered transport (iser)
[ 44.948733] oss_hdaudio 0000:00:1b.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[ 45.118155] usbcore: registered new interface driver oss_usb
[ 50.352353] tun: Universal TUN/TAP device driver, 1.6
[ 50.352357] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 50.396836] device tap0 entered promiscuous mode
[ 50.396868] tapbr: port 2(tap0) entering learning state
[ 50.425908] device tap1 entered promiscuous mode
[ 50.425944] tapbr: port 3(tap1) entering learning state
[ 50.465363] device tap2 entered promiscuous mode
[ 50.465396] tapbr: port 4(tap2) entering learning state
[ 50.493220] device tap3 entered promiscuous mode
[ 50.493253] tapbr: port 5(tap3) entering learning state
[ 50.526413] device tap4 entered promiscuous mode
[ 50.526452] tapbr: port 6(tap4) entering learning state
[ 50.556874] device tap5 entered promiscuous mode
[ 50.556907] tapbr: port 7(tap5) entering learning state
[ 50.587206] device tap6 entered promiscuous mode
[ 50.587239] tapbr: port 8(tap6) entering learning state
[ 50.628841] device tap7 entered promiscuous mode
[ 50.628880] tapbr: port 9(tap7) entering learning state
[ 50.656954] device tap8 entered promiscuous mode
[ 50.656988] tapbr: port 10(tap8) entering learning state
[ 50.685765] device tap9 entered promiscuous mode
[ 50.685800] tapbr: port 11(tap9) entering learning state
[ 51.141645] warning: `jsvc' uses 32-bit capabilities (legacy support in use)
[ 60.628044] tap1: no IPv6 routers present
[ 60.668029] tap8: no IPv6 routers present
[ 60.752035] tap2: no IPv6 routers present
[ 60.792031] tap7: no IPv6 routers present
[ 60.848032] tap0: no IPv6 routers present
[ 60.896033] tap3: no IPv6 routers present
[ 60.896037] tap5: no IPv6 routers present
[ 61.000032] tap4: no IPv6 routers present
[ 61.444031] tap6: no IPv6 routers present
[ 61.676036] tap9: no IPv6 routers present
[ 65.396031] tapbr: port 2(tap0) entering forwarding state
[ 65.424042] tapbr: port 3(tap1) entering forwarding state
[ 65.464032] tapbr: port 4(tap2) entering forwarding state
[ 65.492042] tapbr: port 5(tap3) entering forwarding state
[ 65.524038] tapbr: port 6(tap4) entering forwarding state
[ 65.556035] tapbr: port 7(tap5) entering forwarding state
[ 65.584041] tapbr: port 8(tap6) entering forwarding state
[ 65.628028] tapbr: port 9(tap7) entering forwarding state
[ 65.656041] tapbr: port 10(tap8) entering forwarding state
[ 65.684042] tapbr: port 11(tap9) entering forwarding state
** Model information
sys_vendor: System manufacturer
product_name: System Product Name
product_version: System Version
chassis_vendor: Chassis Manufacture
chassis_version: Chassis Version
bios_vendor: American Megatrends Inc.
bios_version: 0802
board_vendor: ASUSTeK Computer INC.
board_name: P5L-VM 1394
board_version: Rev 1.xx
Kernel: Linux 2.6.32-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.32-2-amd64 depends on:
ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii initramfs-tools [linux-initra 0.92o tools for generating an initramfs
ii module-init-tools 3.4-1 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.32-2-amd64 recommends:
ii firmware-linux-free 2.6.32-5 Binary firmware for various driver
Versions of packages linux-image-2.6.32-2-amd64 suggests:
pn grub | lilo <none> (no description available)
pn linux-doc-2.6.32 <none> (no description available)
Versions of packages linux-image-2.6.32-2-amd64 is related to:
pn firmware-bnx2 <none> (no description available)
pn firmware-bnx2x <none> (no description available)
pn firmware-ipw2x00 <none> (no description available)
pn firmware-ivtv <none> (no description available)
pn firmware-iwlwifi <none> (no description available)
pn firmware-linux <none> (no description available)
ii firmware-linux-nonfree 0.22 Binary firmware for various driver
pn firmware-qlogic <none> (no description available)
pn firmware-ralink <none> (no description available)
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100219085653.2302.2909.reportbug@heretic.burning-in-hell">http://lists.debian.org/20100219085653.2302.2909.reportbug@heretic.burning-in-hell
02-19-2010, 12:43 PM
Ben Hutchings
Bug#570490: linux-image-2.6.32-2-amd64: cannot unload radeon with KMS enabled
On Fri, 2010-02-19 at 09:56 +0100, Michal Suchanek wrote:
> Package: linux-2.6
> Version: 2.6.32-8
> Severity: normal
>
>
> When kms is enabled the radeon module cannot be unloaded. rmmod
> complains that the module is busy while the X server is not running.
I think this is because the console now depends on the framebuffer
provided by the video driver. In theory the video driver could switch
back to a text mode on exit and the console driver could then be swapped
to vgacon (or whatever is appropriate) but there is no mechanism for
this currently.
> This is different from my experience with intel KMS and quite annoying.
Why is this a problem?
Ben.
--
Ben Hutchings
Life is like a sewer:
what you get out of it depends on what you put into it.
02-19-2010, 01:10 PM
Michal Suchanek
Bug#570490: linux-image-2.6.32-2-amd64: cannot unload radeon with KMS enabled
On 19 February 2010 14:43, Ben Hutchings <ben@decadent.org.uk> wrote:
> On Fri, 2010-02-19 at 09:56 +0100, Michal Suchanek wrote:
>> Package: linux-2.6
>> Version: 2.6.32-8
>> Severity: normal
>>
>>
>> When kms is enabled the radeon module cannot be unloaded. rmmod
>> complains that the module is busy while the X server is not running.
>
> I think this is because the console now depends on the framebuffer
> provided by the video driver. *In theory the video driver could switch
> back to a text mode on exit and the console driver could then be swapped
> to vgacon (or whatever is appropriate) but there is no mechanism for
> this currently.
>
>> This is different from my experience with intel KMS and quite annoying.
>
> Why is this a problem?
>
Because KMS does not seem to work well for me so a mechanism for
switching it off other than rebooting would come handy at times.
Of course, I can always edit my startup scripts to not enable it and
reboot. Not enabling it in startup scripts is not an option since X
fails in KMS mode unless the module is manually preloaded.
Thanks
Michal
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: a5d587fb1002190610u625b1120t288c58806bee42e4@mail. gmail.com">http://lists.debian.org/a5d587fb1002190610u625b1120t288c58806bee42e4@mail. gmail.com
02-20-2010, 11:54 AM
Julien Cristau
Bug#570490: linux-image-2.6.32-2-amd64: cannot unload radeon with KMS enabled
On Fri, Feb 19, 2010 at 09:56:53 +0100, Michal Suchanek wrote:
> When kms is enabled the radeon module cannot be unloaded. rmmod
> complains that the module is busy while the X server is not running.
>
> This is different from my experience with intel KMS and quite annoying.
>
err, it's exactly the same with i915. You can't unload it before
unbinding the console. Anyway, I think this bug can be closed with
2.6.32-9, which turns VT_HW_CONSOLE_BINDING on.
Cheers,
Julien
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100220125452.GA25752@radis.liafa.jussieu.fr">htt p://lists.debian.org/20100220125452.GA25752@radis.liafa.jussieu.fr
02-26-2010, 03:23 PM
Moritz Muehlenhoff
Bug#570490: linux-image-2.6.32-2-amd64: cannot unload radeon with KMS enabled
On Sat, Feb 20, 2010 at 01:54:52PM +0100, Julien Cristau wrote:
> On Fri, Feb 19, 2010 at 09:56:53 +0100, Michal Suchanek wrote:
>
> > When kms is enabled the radeon module cannot be unloaded. rmmod
> > complains that the module is busy while the X server is not running.
> >
> > This is different from my experience with intel KMS and quite annoying.
> >
> err, it's exactly the same with i915. You can't unload it before
> unbinding the console. Anyway, I think this bug can be closed with
> 2.6.32-9, which turns VT_HW_CONSOLE_BINDING on.
Michal, 2.6.32-9 is in unstable now. Can you please retest?
Cheers,
Moritz
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100226162347.GA32759@inutil.org">http://lists.debian.org/20100226162347.GA32759@inutil.org
03-01-2010, 07:31 AM
Michal Suchanek
Bug#570490: linux-image-2.6.32-2-amd64: cannot unload radeon with KMS enabled
On 26 February 2010 17:23, Moritz Muehlenhoff <jmm@inutil.org> wrote:
> On Sat, Feb 20, 2010 at 01:54:52PM +0100, Julien Cristau wrote:
>> On Fri, Feb 19, 2010 at 09:56:53 +0100, Michal Suchanek wrote:
>>
>> > When kms is enabled the radeon module cannot be unloaded. rmmod
>> > complains that the module is busy while the X server is not running.
>> >
>> > This is different from my experience with intel KMS and quite annoying.
>> >
>> err, it's exactly the same with i915. *You can't unload it before
>> unbinding the console. *Anyway, I think this bug can be closed with
>> 2.6.32-9, which turns VT_HW_CONSOLE_BINDING on.
>
> Michal, 2.6.32-9 is in unstable now. Can you please retest?
>
I don't see any difference. It doesn't just work. If I am supposed to
rebind the vgacon driver manually then I have no idea how.
Is this documented somewhere?
I tried to restore my setup with radeonfb but it no longer loads for
me automatically and I found there is no documentation whatsoever for
radeonfb :-S
Thanks
Michal
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: a5d587fb1003010031l3f1cdf0bue68f17b47b76cde@mail.g mail.com">http://lists.debian.org/a5d587fb1003010031l3f1cdf0bue68f17b47b76cde@mail.g mail.com
03-01-2010, 11:21 AM
Julien Cristau
Bug#570490: linux-image-2.6.32-2-amd64: cannot unload radeon with KMS enabled
On Mon, Mar 1, 2010 at 09:31:52 +0100, Michal Suchanek wrote:
> On 26 February 2010 17:23, Moritz Muehlenhoff <jmm@inutil.org> wrote:
> > On Sat, Feb 20, 2010 at 01:54:52PM +0100, Julien Cristau wrote:
> >> On Fri, Feb 19, 2010 at 09:56:53 +0100, Michal Suchanek wrote:
> >>
> >> > When kms is enabled the radeon module cannot be unloaded. rmmod
> >> > complains that the module is busy while the X server is not running.
> >> >
> >> > This is different from my experience with intel KMS and quite annoying.
> >> >
> >> err, it's exactly the same with i915. *You can't unload it before
> >> unbinding the console. *Anyway, I think this bug can be closed with
> >> 2.6.32-9, which turns VT_HW_CONSOLE_BINDING on.
> >
> > Michal, 2.6.32-9 is in unstable now. Can you please retest?
> >
>
> I don't see any difference. It doesn't just work. If I am supposed to
> rebind the vgacon driver manually then I have no idea how.
>
Yes, you need to unbind radeon manually to be able to unload it.
> Is this documented somewhere?
>
I don't know. Probably. I have no idea why anyone would want to do
that anyway.
> I tried to restore my setup with radeonfb but it no longer loads for
> me automatically and I found there is no documentation whatsoever for
> radeonfb :-S
>
You don't want to use radeonfb.