dri-devel February 2011

dri-devel@lists.freedesktop.org

84 participants
466 discussions

[Bug 34418] SuperTuxRacer 0.7/Warzone 2100 and r300g MemoryFault (64bit only)
by bugzilla-daemon＠freedesktop.org 20 Feb '11

20 Feb '11

https://bugs.freedesktop.org/show_bug.cgi?id=34418 Chistopher Krakowiak <krzysztof.krakowiak(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|SuperTuxRacer 0.7/Warzone |SuperTuxRacer 0.7/Warzone |2100 and r300g MemoryFault |2100 and r300g MemoryFault | |(64bit only) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

[Bug 29272] New: [BISECTED] Screen becomes corrupted when switching video mode with Radeon KMS
by bugzilla-daemon＠bugzilla.kernel.org 20 Feb '11

20 Feb '11

https://bugzilla.kernel.org/show_bug.cgi?id=29272 Summary: [BISECTED] Screen becomes corrupted when switching video mode with Radeon KMS Product: Drivers Version: 2.5 Kernel Version: 2.6.38-rc5 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: jlp.bugs(a)gmail.com CC: alexdeucher(a)gmail.com Regression: Yes After updating the kernel to 2.6.38-rc5 screen gets corrupted when video mode switches for KMS. This is on laptop eMachines E640G with integrated ATI Mobility Radeon HD 5470. It was working just fine with -rc4. I have bisected the commits and this one was pointed out as the culprit: 5b40ddf888398ce4cccbf3b9d0a18d90149ed7ff is the first bad commit commit 5b40ddf888398ce4cccbf3b9d0a18d90149ed7ff Author: Alex Deucher <alexdeucher(a)gmail.com> Date: Mon Feb 14 11:43:11 2011 -0500 drm/radeon/kms: hopefully fix pll issues for real (v3) The problematic boards have a recommended reference divider to be used when spread spectrum is enabled on the laptop panel. Enable the use of the recommended reference divider along with the new pll algo. v2: testing options v3: When using the fixed reference divider with LVDS, prefer min m to max p and use fractional feedback dividers. Fixes: https://bugzilla.kernel.org/show_bug.cgi?id=28852 https://bugzilla.kernel.org/show_bug.cgi?id=24462 https://bugzilla.kernel.org/show_bug.cgi?id=26552 MacbookPro issues reported by Justin Mattock <justinmattock(a)gmail.com> Signed-off-by: Alex Deucher <alexdeucher(a)gmail.com> Cc: stable(a)kernel.org Signed-off-by: Dave Airlie <airlied(a)redhat.com> :040000 040000 8736f993b97cc8370fd29048761a1e0da4969306 657bdb221e3f4da6efdfec02f8f348db5a537b29 M drivers -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 13

[Bug 28182] New: Radeon Cedar 5450 doesn't interlace
by bugzilla-daemon＠bugzilla.kernel.org 20 Feb '11

20 Feb '11

https://bugzilla.kernel.org/show_bug.cgi?id=28182 Summary: Radeon Cedar 5450 doesn't interlace Product: Drivers Version: 2.5 Kernel Version: 2.6.38-rc3 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: bitbytebit(a)gmail.com Regression: No When using the 5450 card and trying a 640x480 interlaced console frame buffer I get half the screen shown (top half) and bottom is out of the screen display. It's a progressive picture too, not interlaced. If I use 320x240 progressive it all fits, so seems to be that the interlacing isn't working for this chip. Not sure if it's known and just not been implemented yet or if it's a bug. Thanks, Chris 40:00.0 VGA compatible controller: ATI Technologies Inc Device 68f9 (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited Device e157 Flags: bus master, fast devsel, latency 0, IRQ 88 Memory at d0000000 (64-bit, prefetchable) [size=256M] Memory at f2500000 (64-bit, non-prefetchable) [size=128K] I/O ports at 3000 [size=256] [virtual] Expansion ROM at f2540000 [disabled] [size=128K] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information <?> Capabilities: [150] Advanced Error Reporting Kernel driver in use: radeon 40:00.1 Audio device: ATI Technologies Inc Device aa68 Subsystem: PC Partner Limited Device aa68 Physical Slot: 2 Flags: bus master, fast devsel, latency 0, IRQ 5 Memory at f2520000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information <?> Capabilities: [150] Advanced Error Reporting Kernel modules: snd-hda-intel [ 0.801038] [drm] Initialized drm 1.1.0 20060810 [ 0.801109] [drm] radeon defaulting to kernel modesetting. [ 0.801154] [drm] radeon kernel modesetting enabled. [ 0.801253] radeon 0000:40:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 0.801304] radeon 0000:40:00.0: setting latency timer to 64 [ 0.804194] [drm] initializing kernel modesetting (CEDAR 0x1002:0x68F9). [ 0.804282] [drm] register mmio base: 0xF2500000 [ 0.804327] [drm] register mmio size: 131072 [ 0.804566] ATOM BIOS: CEDAR [ 0.804700] radeon 0000:40:00.0: VRAM: 512M 0x0000000000000000 - 0x000000001FFFFFFF (512M used) [ 0.804755] radeon 0000:40:00.0: GTT: 512M 0x0000000020000000 - 0x000000003FFFFFFF [ 0.805277] [drm] Detected VRAM RAM=512M, BAR=256M [ 0.805329] [drm] RAM width 64bits DDR [ 0.805461] [TTM] Zone kernel: Available graphics memory: 1541250 kiB. [ 0.805508] [TTM] Initializing pool allocator. [ 0.805576] [drm] radeon: 512M of VRAM memory ready [ 0.805621] [drm] radeon: 512M of GTT memory ready. [ 0.805686] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 0.805732] [drm] Driver supports precise vblank timestamp query. [ 0.805830] radeon 0000:40:00.0: irq 88 for MSI/MSI-X [ 0.805837] radeon 0000:40:00.0: radeon: using MSI. [ 0.805917] [drm] radeon: irq initialized. [ 0.805963] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 0.807259] [drm] Loading CEDAR Microcode [ 0.809692] radeon 0000:40:00.0: WB enabled [ 0.826164] [drm] ring test succeeded in 1 usecs [ 0.826364] [drm] radeon: ib pool ready. [ 0.826569] [drm] ib test succeeded in 0 usecs [ 0.827043] [drm] Radeon Display Connectors [ 0.827087] [drm] Connector 0: [ 0.827129] [drm] HDMI-A [ 0.827171] [drm] HPD1 [ 0.827214] [drm] DDC: 0x6460 0x6460 0x6464 0x6464 0x6468 0x6468 0x646c 0x646c [ 0.827265] [drm] Encoders: [ 0.827307] [drm] DFP1: INTERNAL_UNIPHY1 [ 0.827350] [drm] Connector 1: [ 0.827392] [drm] DVI-I [ 0.827434] [drm] HPD4 [ 0.827476] [drm] DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448 0x644c 0x644c [ 0.827527] [drm] Encoders: [ 0.827569] [drm] DFP2: INTERNAL_UNIPHY [ 0.827612] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [ 0.827655] [drm] Connector 2: [ 0.827697] [drm] VGA [ 0.827739] [drm] DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 0x643c [ 0.827790] [drm] Encoders: [ 0.827832] [drm] CRT2: INTERNAL_KLDSCP_DAC2 [ 0.934929] [drm] Internal thermal controller with fan control [ 0.935028] [drm] radeon: power management initialized [ 1.066145] [drm] fb mappable at 0xD0141000 [ 1.066189] [drm] vram apper at 0xD0000000 [ 1.066233] [drm] size 9216000 [ 1.066275] [drm] fb depth is 24 [ 1.066317] [drm] pitch is 7680 [ 1.500225] [drm] force priority to high [ 1.500231] [drm] force priority to high [ 1.514974] Console: switching to colour frame buffer device 240x67 [ 1.520982] fb0: radeondrmfb frame buffer device [ 1.520985] drm: registered panic notifier [ 1.521048] [drm] Initialized radeon 2.8.0 20080528 for 0000:40:00.0 on minor 0 -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 4

[Bug 26562] New: [bisected] blank screen with radeon.modeset=1
by bugzilla-daemon＠bugzilla.kernel.org 19 Feb '11

19 Feb '11

https://bugzilla.kernel.org/show_bug.cgi?id=26562 Summary: [bisected] blank screen with radeon.modeset=1 Product: Drivers Version: 2.5 Kernel Version: 2.6.37 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: sliedes(a)cc.hut.fi CC: airlied(a)linux.ie, alexdeucher(a)gmail.com Regression: Yes Hi, On 2.6.37, I get blank screen with my RV630 desktop radeon with KMS on (kernel parameter radeon.modeset=1). 2.6.36 works fine. The computer does not crash, the only symptom I can find is no signal to the screen. I have bisected the problem down to this commit: ------------------------------------------------------------ 48dfaaeb6637240af3089bf9b7a00a6cf24e0182 is the first bad commit commit 48dfaaeb6637240af3089bf9b7a00a6cf24e0182 Author: Alex Deucher <alexdeucher(a)gmail.com> Date: Wed Sep 29 11:37:41 2010 -0400 drm/radeon/kms: remove new pll algo The recent changes to the old algo (prefer high post div) coupled with the range and precision limitations of using fixed point with the new algo make the new algo less useful. So drop the new algo. This should work as well or better than the old new/old combinations and simplifies the code a lot. Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=30218 among others. Signed-off-by: Alex Deucher <alexdeucher(a)gmail.com> Signed-off-by: Dave Airlie <airlied(a)redhat.com> ------------------------------------------------------------ lspci -v: ------------------------------------------------------------ 01:00.0 VGA compatible controller: ATI Technologies Inc RV630 [Radeon HD 2600 Series] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited Device e410 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at d0000000 (64-bit, prefetchable) [size=256M] Memory at fe620000 (64-bit, non-prefetchable) [size=64K] I/O ports at e000 [size=256] Expansion ROM at fe600000 [disabled] [size=128K] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> 01:00.1 Audio device: ATI Technologies Inc RV630/M76 audio device [Radeon HD 2600 Series] Subsystem: PC Partner Limited Device aa08 Flags: bus master, fast devsel, latency 0, IRQ 67 Memory at fe630000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Kernel driver in use: HDA Intel ------------------------------------------------------------ I tried to diagnose this further with `radeontool regs', but there is no difference in the output between the last good commit (f28488c2) with screen in the working state and the first bad commit (48dfaaeb) with the screen blanked. Here's its output with a text console on the screen (no X): ------------------------------------------------------------ RADEON_DAC_CNTL 00000000 RADEON_DAC_EXT_CNTL 00000000 RADEON_DAC_MACRO_CNTL 00000000 RADEON_DAC_CNTL2 00000000 RADEON_TV_DAC_CNTL 00000000 RADEON_DISP_OUTPUT_CNTL 00000000 RADEON_CONFIG_MEMSIZE 00000000 RADEON_AUX_SC_CNTL 2ba7a25e RADEON_CRTC_EXT_CNTL 00000000 RADEON_CRTC_GEN_CNTL 00000000 RADEON_CRTC2_GEN_CNTL 00000000 RADEON_DEVICE_ID 00000000 RADEON_DISP_MISC_CNTL 00000000 RADEON_GPIO_MONID 00000000 RADEON_GPIO_MONIDB 00000000 RADEON_GPIO_CRT2_DDC 00000000 RADEON_GPIO_DVI_DDC 00000000 RADEON_GPIO_VGA_DDC 00000000 RADEON_LVDS_GEN_CNTL 00000000 RADEON_LVDS_PLL_CNTL 00000000 RADEON_FP_GEN_CNTL 00000000 RADEON_FP2_GEN_CNTL 00000000 RADEON_PPLL_CNTL 00000000 RADEON_PPLL_REF_DIV 00000000 RADEON_PPLL_DIV_3 00000000 RADEON_PIXCLKS_CNTL 00000000 RADEON_P2PLL_CNTL 00000000 RADEON_P2PLL_REF_DIV 00000000 RADEON_P2PLL_DIV_0 00000000 RADEON_VCLK_ECP_CNTL 00000000 RADEON_MEM_TIMING_CNTL 00000000 RADEON_TMDS_PLL_CNTL 00000000 RADEON_TMDS_TRANSMITTER_CNTL 00000000 RADEON_CRTC_MORE_CNTL 00000000 RADEON_FP_H_SYNC_STRT_WID 00000000 RADEON_FP_V_SYNC_STRT_WID 00000000 RADEON_FP_CRTC_H_TOTAL_DISP 00000000 RADEON_FP_CRTC_V_TOTAL_DISP 00000000 RADEON_FP_HORZ_STRETCH 00000000 RADEON_FP_VERT_STRETCH 00000000 RADEON_FP_HORZ_VERT_ACTIVE 00000000 RADEON_CRTC_H_TOTAL_DISP 00000000 RADEON_CRTC_H_SYNC_STRT_WID 00000000 RADEON_CRTC_V_TOTAL_DISP 00000000 RADEON_CRTC_V_SYNC_STRT_WID 00000000 RADEON_CRTC2_H_TOTAL_DISP 0200000f RADEON_CRTC2_H_SYNC_STRT_WID 00000000 RADEON_CRTC2_V_TOTAL_DISP 00000100 RADEON_CRTC2_V_SYNC_STRT_WID 00000002 ------------------------------------------------------------ If there's anything further you need me to do to diagnose this, I'll be happy to help. --- Comment #1 from Sami Liedes <sliedes(a)cc.hut.fi> 2011-01-12 13:30:45 --- Did the mail for this bug go anywhere?? Bugzilla timed out and I certainly did not get any mail about this (I should per my bugzilla preferences), but the bug has been created. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 11

[Bug 34418] SuperTuxRacer 0.7/Warzone 2100 and r300g MemoryFault
by bugzilla-daemon＠freedesktop.org 19 Feb '11

19 Feb '11

https://bugs.freedesktop.org/show_bug.cgi?id=34418 --- Comment #7 from Chistopher Krakowiak <krzysztof.krakowiak(a)gmail.com> 2011-02-19 11:04:33 PST --- (In reply to comment #6) > I wonder whether the reason is that my system is 32-bit and yours is 64-bit. I have multilib system, so it wasnt problem to rebuild it on builders and transfer 32bit binary..and..IT WORKS :) And to clarify, I got nearly symetrical envs(multilib) on thinkpad, and similary(chroots) on PLD builders. And now I am sure that ut2k4/doom3 problems arent related to this bug, because doom3 is only 32bit, and both ut2k4 binaries hangs in menu or segfaults on start(depending on vars) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

[PATCH] radeon: (re)initialize the CP lockup tracking info at resume
by Paul Bolle 19 Feb '11

19 Feb '11

A laptop with an "ATI Radeon Mobility 9000 (M9) Lf (AGP)" chipset tends to show the following WARNING if: - run with agpmode=-1 (which apparently means "PCI mode"); - suspended and resumed a few times: [33181.505650] radeon 0000:01:00.0: GPU lockup CP stall for more than 5496706msec [33181.505655] ------------[ cut here ]------------ [33181.505718] WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:248 radeon_fence_wait+0x248/0x2bb [radeon]() [33181.505722] Hardware name: [33181.505724] GPU lockup (waiting for 0x00014AB4 last fence id 0x00014AB2) [33181.505727] Modules linked in: snd_intel8x0m tcp_lp sco bnep l2cap bluetooth fuse cpufreq_ondemand acpi_cpufreq mperf ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_netbios_ns ip6table_filter ip6_tables arc4 ath5k snd_intel8x0 ath snd_ac97_codec mac80211 ac97_bus snd_seq snd_seq_device snd_pcm snd_timer iTCO_wdt ppdev thinkpad_acpi cfg80211 rfkill snd microcode parport_pc e1000 iTCO_vendor_support snd_page_alloc joydev parport i2c_i801 soundcore uinput ipv6 yenta_socket radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded: snd_intel8x0m] [33181.505779] Pid: 1061, comm: Xorg Not tainted 2.6.38-0.rc4.git0.2.local3.fc15.i686 #1 [33181.505783] Call Trace: [33181.505794] [<c043aab5>] ? warn_slowpath_common+0x7c/0x91 [33181.505828] [<f79cf14b>] ? radeon_fence_wait+0x248/0x2bb [radeon] [33181.505867] [<f79cf14b>] ? radeon_fence_wait+0x248/0x2bb [radeon] [33181.505872] [<c043ab55>] ? warn_slowpath_fmt+0x33/0x35 [33181.505911] [<f79cf14b>] ? radeon_fence_wait+0x248/0x2bb [radeon] [33181.505924] [<c0451493>] ? autoremove_wake_function+0x0/0x37 [33181.505958] [<f79cf734>] ? radeon_sync_obj_wait+0x11/0x13 [radeon] [33181.505976] [<f78df3ec>] ? ttm_bo_wait+0xae/0x151 [ttm] [33181.506013] [<f79de6de>] ? radeon_bo_wait+0x6e/0x8d [radeon] [33181.506080] [<f79dec16>] ? radeon_gem_wait_idle_ioctl+0x2f/0x59 [radeon] [33181.506111] [<f788340b>] ? drm_ioctl+0x2a4/0x38a [drm] [33181.506150] [<f79debe7>] ? radeon_gem_wait_idle_ioctl+0x0/0x59 [radeon] [33181.506164] [<c0593524>] ? file_has_perm+0x9a/0xb3 [33181.506180] [<f7883167>] ? drm_ioctl+0x0/0x38a [drm] [33181.506186] [<c04f0737>] ? do_vfs_ioctl+0x451/0x482 [33181.506192] [<c0593795>] ? selinux_file_ioctl+0x39/0x3c [33181.506196] [<c04f07af>] ? sys_ioctl+0x47/0x60 [33181.506203] [<c07d78dc>] ? syscall_call+0x7/0xb [33181.506207] ---[ end trace eecc6a32d93293db ]--- [33181.611857] radeon 0000:01:00.0: GPU reset succeed [33181.637228] radeon 0000:01:00.0: WB enabled After that the screen is black and the keyboard non-functioning. I then need to log in over eg. ssh and reboot or kill X to get the laptop in a usable state again. After adding a number of printks and running numerous sessions it seems something like the following is going on: - at each resume the GPU lockup detection code is run; - if a previous session was quiet for the GPU the "RPTR" register will not have changed from its starting value (apparently 0x80) so at the next resume the current RPTR will equal the RPTR value saved in the CP lockup tracking information; - if the GPU lockup detection code runs at resume and more than 10 seconds have passed since the previous GPU lockup detection r100_gpu_cp_is_lockup() will decide a lockup has occurred; - the GPU lockup detection code will then reset the GPU. The easiest solution I could think of was to update the CP lockup tracking information at the end of r100_startup(). This will mean that this information is up to date after (each boot and after) each resume and (apparently) before the GPU lockup detection code is run. I have not been able to generate this WARNING with that (one line) change added. Note that this patch (further) invalidates the comment above r100_gpu_cp_is_lockup(). But I'm not sure how that comment should read anyhow as it already is at odds with the current code. Signed-off-by: Paul Bolle <pebolle(a)tiscali.nl> --- drivers/gpu/drm/radeon/r100.c | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/drivers/gpu/drm/radeon/r100.c b/drivers/gpu/drm/radeon/r100.c index 56deae5..0107cb1 100644 --- a/drivers/gpu/drm/radeon/r100.c +++ b/drivers/gpu/drm/radeon/r100.c @@ -3831,6 +3831,10 @@ static int r100_startup(struct radeon_device *rdev) dev_err(rdev->dev, "failled initializing IB (%d).\n", r); return r; } + + /* (re)initialize the CP lockup tracking information */ + r100_gpu_lockup_update(&rdev->config.r100.lockup, &rdev->cp); + return 0; } -- 1.7.4.1

1 0

[Bug 34418] SuperTuxRacer 0.7/Warzone 2100 and r300g MemoryFault
by bugzilla-daemon＠freedesktop.org 19 Feb '11

19 Feb '11

https://bugs.freedesktop.org/show_bug.cgi?id=34418 --- Comment #6 from Marek Olšák <maraeo(a)gmail.com> 2011-02-19 07:59:30 PST --- I wonder whether the reason is that my system is 32-bit and yours is 64-bit. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

[Bug 13170] Macbook 5,2 only boots with acpi=off, or nosmp, or maxcpus=1
by bugzilla-daemon＠bugzilla.kernel.org 19 Feb '11

19 Feb '11

https://bugzilla.kernel.org/show_bug.cgi?id=13170 Gregory Bellier <dest(a)gatekeeper.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dest(a)gatekeeper.fr --- Comment #60 from Gregory Bellier <dest(a)gatekeeper.fr> 2011-02-19 15:58:42 --- I also have a MacBook 5,2 (early 2009) and I experience the same errors than you do. This has been tested on Ubuntu 10.10 I managed to build a grub2 1.99rc1 x86_64-efi. I had to do some tweaks to make some progress. I'm hacking directly in grub.cfg but from now, I don't care, I just want to test. So here is my entry : menuentry 'Ubuntu, with Linux 2.6.35-25-generic' --class ubuntu --class gnu-linux --class gnu --class os { insmod part_gpt insmod ext2 set debug=video insmod efi_gop set root='(hd0,gpt3)' search --no-floppy --fs-uuid --set=root d5175c18-7da2-49a9-a3af-844bad27c91d linux /boot/vmlinuz-2.6.35-25-generic root=UUID=d5175c18-7da2-49a9-a3af-844bad27c91d ro initrd /boot/initrd.img-2.6.35-25-generic } The options are pretty much the same than the ones from my working grub (with maxcpus=1). At my first boot, I got "error: no argument specified". From what I've seen on the internet, it's because the syntax is different between Grub 1.98 and 1.99rc1. In 1.98 it's --set d5175c18... while --set=root is needed for 1.99rc1. However, this error wasn't a real problem because we're asked to press a key and then the boot continues. It continues until the second error: "error: no suitable mode found". I've resolved this error by putting "set debug=video" and "insmod efi_gop" in my grub entry. >From this point, I can see that the kernel starts booting until the error I now have which I haven't solved yet : "fb: conflicting fb hw usage nouveaufb vs EFI VGA - removing generic driver". I hope this post will help some of you to make some progress until the point I've reached. I also tried what comment #58 detailed but I have the very same error : conflicting fb... -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 0

[Bug 34418] SuperTuxRacer 0.7/Warzone 2100 and r300g MemoryFault
by bugzilla-daemon＠freedesktop.org 19 Feb '11

19 Feb '11

https://bugs.freedesktop.org/show_bug.cgi?id=34418 --- Comment #5 from Marek Olšák <maraeo(a)gmail.com> 2011-02-19 07:56:55 PST --- noimmd disables the "immediate mode" style of rendering, which means vertices are written directly to the command stream for the GPU instead of being stored in vertex buffers. There is something fishy here because I can't reproduce it for whatever reason, so there is something wrong either with my machine or yours. Bug 34336 is likely a duplicate of this one. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

[Bug 34418] SuperTuxRacer 0.7/Warzone 2100 and r300g MemoryFault
by bugzilla-daemon＠freedesktop.org 19 Feb '11

19 Feb '11

https://bugs.freedesktop.org/show_bug.cgi?id=34418 --- Comment #4 from Chistopher Krakowiak <krzysztof.krakowiak(a)gmail.com> 2011-02-19 07:15:03 PST --- (In reply to comment #3) > I can't reproduce this. airlied also on nearly identical hardware to mine :/ > Please try: > > git clean -fdx Didnt helped > > and rebuild Mesa. I know that ;) > Alternatively, you may try and set either of these environment variables and > see if it helps: > > RADEON_THREAD=0 This doesnt change anything for this two games > RADEON_DEBUG=noimmd This fixes SuperTuxKart 0.7 and Warzone2100 doom3/ut2k4 still are broken in the same time(commits), but both differently, so I will probably open new bug reports. And what noimmd does? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

← Newer
1
...
27
28
29
30
31
32
33
...
47
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel February 2011