udl: Unrecognized vendor firmware descriptor (all zeroes)
I got a Lenovo USB port replicator (model no: K33415) with DisplayLink VGA. When I plug it into my Lenovo laptop (with no display attached to the dock yet), USB hub and audio devices from the dock are found but the DisplayLink device initialization gets an error. All bytes in vendor firmware descriptor and EDID seem to be zero. Is it something wrong with the device, Linux USB stack or UDL driver? [379953.534772] usb 1-3.4: new high-speed USB device number 23 using xhci_hcd [379953.630502] usb 1-3.4: New USB device found, idVendor=17e9, idProduct=01e0, bcdDevice= 0.03 [379953.635493] usb 1-3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [379953.640411] usb 1-3.4: Product: Lenovo Enhanced USB Port Replicator [379953.645573] usb 1-3.4: Manufacturer: DisplayLink [379953.650430] usb 1-3.4: SerialNumber: 01>0-128530 [379953.662128] [drm] vendor descriptor length:e0 data:00 00 00 00 00 00 00 00 00 00 00 [379953.667129] [drm:udl_init.cold [udl]] *ERROR* Unrecognized vendor firmware descriptor [379953.673031] [drm] Initialized udl 0.0.1 20120220 for 1-3.4:1.0 on minor 1 [379953.677693] [drm] Initialized udl on minor 1 [379953.733025] udl 1-3.4:1.0: [drm] DVI-I-1: EDID is invalid: [379953.735019] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [379953.737014] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [379953.739061] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [379953.741086] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [379953.743170] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [379953.745163] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [379953.747176] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [379953.749093] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [379953.751015] udl 1-3.4:1.0: [drm] Cannot find any crtc or sizes [379953.753565] [drm] vendor descriptor length:e0 data:00 00 00 00 00 00 00 00 00 00 00 [379953.755501] [drm:udl_init.cold [udl]] *ERROR* Unrecognized vendor firmware descriptor [379953.758261] [drm] Initialized udl 0.0.1 20120220 for 1-3.4:1.1 on minor 3 [379953.760405] [drm] Initialized udl on minor 3 [379953.827661] udl 1-3.4:1.1: [drm] DVI-I-3: EDID is invalid: [379953.832758] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [379953.838083] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [379953.843553] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [379953.848803] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [379953.853151] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [379953.856164] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [379953.858381] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [379953.860334] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [379953.862199] udl 1-3.4:1.1: [drm] Cannot find any crtc or sizes [379964.084865] udl 1-3.4:1.0: [drm] Cannot find any crtc or sizes [379964.089921] udl 1-3.4:1.1: [drm] Cannot find any crtc or sizes -- Meelis Roos ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: radeon UBSAN warning from user syscall
Looks like the shift and mask are reversed. Does this patch fix it? Yes, the warning is gone and it still works. Thank you! Tested-by: Meelis Roos ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
radeon UBSAN warning from user syscall
I tried latest (5.4) custom kernel (with UBSAN) on my Dell D600 laptop and found that it exhibits a UBSAN warning triggered by userspace ioctl. Here is dmesg with anything radeon-related + the warning, and config: [ 17.659534] [drm] radeon kernel modesetting enabled. [ 17.659607] radeon :01:00.0: remove_conflicting_pci_framebuffers: bar 0: 0xe800 -> 0xefff [ 17.659609] radeon :01:00.0: remove_conflicting_pci_framebuffers: bar 2: 0xfcff -> 0xfcff [ 17.659613] radeon :01:00.0: vgaarb: deactivate vga console [ 17.661629] Console: switching to colour dummy device 80x25 [ 17.667764] [drm] initializing kernel modesetting (RV250 0x1002:0x4C66 0x1028:0x011D 0x01). [ 17.667822] resource sanity check: requesting [mem 0x000c-0x000d], which spans more than PCI Bus :00 [mem 0x000d-0x000d window] [ 17.667832] caller pci_map_rom+0x6d/0x19a mapping multiple BARs [ 17.668236] agpgart-intel :00:00.0: AGP 2.0 bridge [ 17.668246] agpgart-intel :00:00.0: putting AGP V2 device into 4x mode [ 17.668269] radeon :01:00.0: putting AGP V2 device into 4x mode [ 17.668291] radeon :01:00.0: GTT: 128M 0xE000 - 0xE7FF [ 17.668299] radeon :01:00.0: VRAM: 128M 0xE800 - 0xEFFF (32M used) [ 17.668336] [drm] Detected VRAM RAM=128M, BAR=128M [ 17.668337] [drm] RAM width 64bits DDR [ 17.681858] [TTM] Zone kernel: Available graphics memory: 412324 KiB [ 17.681861] [TTM] Initializing pool allocator [ 17.681868] [TTM] Initializing DMA pool allocator [ 17.681905] [drm] radeon: 32M of VRAM memory ready [ 17.681907] [drm] radeon: 128M of GTT memory ready. [ 17.681918] [drm] radeon: power management initialized [ 17.685726] radeon :01:00.0: WB disabled [ 17.685735] radeon :01:00.0: fence driver on ring 0 use gpu addr 0xe000 and cpu addr 0x116c2780 [ 17.685738] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 17.685739] [drm] Driver supports precise vblank timestamp query. [ 17.685755] [drm] radeon: irq initialized. [ 17.685758] [drm] Loading R200 Microcode [ 17.788181] [drm] radeon: ring at 0xE0001000 [ 17.788207] [drm] ring test succeeded in 1 usecs [ 17.788379] [drm] ib test succeeded in 0 usecs [ 17.788845] [drm] Panel ID String: 2K077141X13 [ 17.788846] [drm] Panel Size 1024x768 [ 17.70] [drm] No TV DAC info found in BIOS [ 17.788912] [drm] Radeon Display Connectors [ 17.788913] [drm] Connector 0: [ 17.788914] [drm] VGA-1 [ 17.788916] [drm] DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60 [ 17.788917] [drm] Encoders: [ 17.788918] [drm] CRT1: INTERNAL_DAC1 [ 17.788920] [drm] Connector 1: [ 17.788920] [drm] DVI-D-1 [ 17.788921] [drm] HPD1 [ 17.788923] [drm] DDC: 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 [ 17.788923] [drm] Encoders: [ 17.788924] [drm] DFP1: INTERNAL_TMDS1 [ 17.788925] [drm] Connector 2: [ 17.788925] [drm] LVDS-1 [ 17.788926] [drm] Encoders: [ 17.788927] [drm] LCD1: INTERNAL_LVDS [ 17.788927] [drm] Connector 3: [ 17.788928] [drm] SVIDEO-1 [ 17.788929] [drm] Encoders: [ 17.788929] [drm] TV1: INTERNAL_DAC2 [ 17.957500] [drm] fb mappable at 0xE804 [ 17.957503] [drm] vram apper at 0xE800 [ 17.957504] [drm] size 1572864 [ 17.957505] [drm] fb depth is 16 [ 17.957505] [drm]pitch is 2048 [ 18.013861] fbcon: radeondrmfb (fb0) is primary device [ 18.566984] Console: switching to colour frame buffer device 128x48 [ 18.576250] radeon :01:00.0: fb0: radeondrmfb frame buffer device [ 18.577844] [drm] Initialized radeon 2.50.0 20080528 for :01:00.0 on minor 0 [ 64.194226] [ 64.194238] UBSAN: Undefined behaviour in drivers/gpu/drm/radeon/r200.c:480:34 [ 64.194244] shift exponent 4096 is too large for 32-bit type 'int' [ 64.194248] CPU: 0 PID: 447 Comm: Xorg Not tainted 5.4.0 #16 [ 64.194249] Hardware name: Dell Computer Corporation Latitude D600 /0X2034, BIOS A16 06/29/2005 [ 64.194251] Call Trace: [ 64.194266] dump_stack+0x16/0x19 [ 64.194272] ubsan_epilogue+0xb/0x29 [ 64.194274] __ubsan_handle_shift_out_of_bounds.cold+0x26/0x78 [ 64.194368] ? radeon_cs_packet_next_reloc+0x3c/0x170 [radeon] [ 64.194403] ? r100_reloc_pitch_offset+0x27/0x140 [radeon] [ 64.194433] r200_packet0_check.cold+0x5e/0x63 [radeon] [ 64.194473] ? r200_copy_dma+0x430/0x430 [radeon] [ 64.194508] r100_cs_parse_packet0+0x53/0xe0 [radeon] [ 64.194543] r100_cs_parse+0x2de/0x4b0 [radeon] [ 64.194583] ? r200_copy_dma+0x430/0x430 [radeon] [ 64.194617] radeon_cs_ioctl+0x305/0x890 [radeon] [ 64.194626] ? ttm_bo_init_reserved+0x2f0/0x390 [ttm] [ 64.194662] ? radeon_cs_parser_init+0x550/0x550 [radeon] [ 64.194689] drm_ioctl_kernel+0x8b/0xd0 [drm] [ 64.194724] ?
Re: Radeon HD 7450 brightness oversaturated
Kernels are 5.0 and 5.1-rc1. Is it just kernels 5.0 and 5.1? There haven't really been any display related changes to radeon in ages. Possibly a duplicate of: https://bugzilla.kernel.org/show_bug.cgi?id=198123 No, I just put the card in and tested with only the current kernels I had. I can get some older kernel and test with that if that is of any help. Just tested Debianis 4.19.0-4 package (4.19.28) and it exhibits the same symptoms. Slight additional detail: chenaging between fbcon vt-s does not fix it, only changing between fbcon and X fixes it. -- Meelis Roos ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: Radeon HD 7450 brightness oversaturated
I decided to put a discrete graphics card into a PC and found a fitting Radeon HD 7450. It works, but there is strange whiteness like the brightness is oversaturated and light places turn into other colors: * on fbcon, right after radeondrmfb initializes * in X after powersave The colors return to normal after a VT switch or two. Screenshot of one such washed view is at http://kodu.ut.ee/~mroos/radeon_washed.jpg Kernels are 5.0 and 5.1-rc1. Is it just kernels 5.0 and 5.1? There haven't really been any display related changes to radeon in ages. Possibly a duplicate of: https://bugzilla.kernel.org/show_bug.cgi?id=198123 No, I just put the card in and tested with only the current kernels I had. I can get some older kernel and test with that if that is of any help. -- Meelis Roos ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: Radeon init fail and resulting cascade of UBSAN errors
.938576] Code: 00 55 89 e5 57 56 89 d6 53 83 ec 14 8b 7d 0c 8b 55 08 89 7d e8 c1 ff 10 81 f9 ff 0f 00 00 89 55 ec 89 7d f0 76 53 85 ff 74 60 <0f> b6 19 31 d2 8d 79 01 84 db 74 23 b9 01 00 00 00 eb 0e 8d 74 26 [ 7.938576] EAX: df7a0bcd EBX: f5471a48 ECX: 00f80c53 EDX: 0704 [ 7.938577] ESI: df7a0fa0 EDI: EBP: f5471940 ESP: df79439c [ 7.938578] DS: 007b ES: 007b FS: GS: 00e0 SS: 0068 EFLAGS: 00210086 [ 7.938579] CR0: 80050033 CR2: 00f80c53 CR3: 354cf000 CR4: 06d0 [ 8.201765] Adding 2096124k swap on /dev/sda5. Priority:-2 extents:1 across:2096124k -- Meelis Roos ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
5.1-rc1: radeon WARNING: CPU: 1 PID: 160 at drivers/gpu/drm/drm_fourcc.c:278 drm_format_info+0x74/0xe0 [drm]
858194] ? 0xc0791000 [4.858200] do_one_initcall+0x7e/0x19b [4.858207] do_init_module+0x59/0x1e0 [4.858211] load_module+0x2030/0x2820 [4.858216] ? __do_sys_finit_module+0xba/0xe0 [4.858220] __do_sys_finit_module+0xba/0xe0 [4.858224] do_syscall_64+0x4a/0xf0 [4.858231] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [4.858236] RIP: 0033:0x7fb1a603d2a9 [4.858240] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b7 6b 0c 00 f7 d8 64 89 01 48 [4.858246] RSP: 002b:7ffd46f1bbd8 EFLAGS: 0246 ORIG_RAX: 0139 [4.858251] RAX: ffda RBX: 559eddfec720 RCX: 7fb1a603d2a9 [4.858254] RDX: RSI: 7fb1a5f41cad RDI: 0017 [4.858258] RBP: 7fb1a5f41cad R08: R09: [4.858262] R10: 0017 R11: 0246 R12: [4.858265] R13: 559eddfe7060 R14: 0002 R15: 559eddfec720 [4.858271] ---[ end trace 4ae78d4354eb ]--- [4.858281] [TTM] Illegal buffer object size [4.858287] [TTM] Illegal buffer object size [4.858336] [drm:radeon_gem_object_create [radeon]] *ERROR* Failed to allocate GEM object (0, 6, 4096, -22) [4.858340] failed to allocate framebuffer (0) [4.858385] [drm:radeonfb_create [radeon]] *ERROR* failed to create fbcon object -12 [4.858416] [drm] Initialized radeon 2.50.0 20080528 for :01:01.0 on minor 0 -- Meelis Roos ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Radeon init fail and resulting cascade of UBSAN errors
EAX: df7a0bcd EBX: f5471a48 ECX: 00f80c53 EDX: 0704 [7.938577] ESI: df7a0fa0 EDI: EBP: f5471940 ESP: df79439c [7.938578] DS: 007b ES: 007b FS: GS: 00e0 SS: 0068 EFLAGS: 00210086 [7.938579] CR0: 80050033 CR2: 00f80c53 CR3: 354cf000 CR4: 06d0 [8.201765] Adding 2096124k swap on /dev/sda5. Priority:-2 extents:1 across:2096124k -- Meelis Roos ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Undefined behaviour in drivers/gpu/drm/radeon/r200.c:480:34 - shift exponent 4096 is too large
Got UBSAN warning from Dell D600 running 5.0.0-rc4-00218-g12491ed354d2. The warning did not happen on bootup but during xfce session start or console switch. [ 15.323113] radeon :01:00.0: putting AGP V2 device into 4x mode [ 15.323134] radeon :01:00.0: GTT: 128M 0xE000 - 0xE7FF [ 15.323142] radeon :01:00.0: VRAM: 128M 0xE800 - 0xEFFF (32M used) [ 15.323459] [drm] Detected VRAM RAM=128M, BAR=128M [ 15.323463] [drm] RAM width 64bits DDR [ 15.323566] [TTM] Zone kernel: Available graphics memory: 412446 kiB [ 15.323567] [TTM] Initializing pool allocator [ 15.323580] [TTM] Initializing DMA pool allocator [ 15.323609] [drm] radeon: 32M of VRAM memory ready [ 15.323611] [drm] radeon: 128M of GTT memory ready. [ 15.323621] [drm] radeon: power management initialized [ 15.331289] radeon :01:00.0: WB disabled [ 15.331296] radeon :01:00.0: fence driver on ring 0 use gpu addr 0xe000 and cpu addr 0x712386dd [ 15.331299] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 15.331300] [drm] Driver supports precise vblank timestamp query. [ 15.331315] [drm] radeon: irq initialized. [ 15.331317] [drm] Loading R200 Microcode [...] [ 15.795041] [drm] radeon: ring at 0xE0001000 [ 15.795073] [drm] ring test succeeded in 1 usecs [ 15.795316] [drm] ib test succeeded in 0 usecs [ 15.801857] [drm] Panel ID String: 2K077141X13 [ 15.801861] [drm] Panel Size 1024x768 [ 15.801938] [drm] No TV DAC info found in BIOS [ 15.802012] [drm] Radeon Display Connectors [ 15.802015] [drm] Connector 0: [ 15.802017] [drm] VGA-1 [ 15.802023] [drm] DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60 [ 15.802024] [drm] Encoders: [ 15.802027] [drm] CRT1: INTERNAL_DAC1 [ 15.802030] [drm] Connector 1: [ 15.802031] [drm] DVI-D-1 [ 15.802033] [drm] HPD1 [ 15.802038] [drm] DDC: 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 [ 15.802040] [drm] Encoders: [ 15.802042] [drm] DFP1: INTERNAL_TMDS1 [ 15.802044] [drm] Connector 2: [ 15.802046] [drm] LVDS-1 [ 15.802047] [drm] Encoders: [ 15.802049] [drm] LCD1: INTERNAL_LVDS [ 15.802051] [drm] Connector 3: [ 15.802053] [drm] SVIDEO-1 [ 15.802054] [drm] Encoders: [ 15.802056] [drm] TV1: INTERNAL_DAC2 [ 15.845987] [drm] fb mappable at 0xE804 [ 15.845988] [drm] vram apper at 0xE800 [ 15.845989] [drm] size 1572864 [ 15.845990] [drm] fb depth is 16 [ 15.845990] [drm]pitch is 2048 [ 15.848183] fbcon: radeondrmfb (fb0) is primary device [ 15.892233] Console: switching to colour frame buffer device 128x48 [ 15.901408] radeon :01:00.0: fb0: radeondrmfb frame buffer device [ 15.905786] [drm] Initialized radeon 2.50.0 20080528 for :01:00.0 on minor 0 [...] [ 447.146334] [ 447.146347] UBSAN: Undefined behaviour in drivers/gpu/drm/radeon/r200.c:480:34 [ 447.146351] shift exponent 4096 is too large for 32-bit type 'int' [ 447.146357] CPU: 0 PID: 386 Comm: Xorg Not tainted 5.0.0-rc4-00218-g12491ed354d2 #7 [ 447.146358] Hardware name: Dell Computer Corporation Latitude D600 /0X2034, BIOS A16 06/29/2005 [ 447.146359] Call Trace: [ 447.146375] dump_stack+0x16/0x19 [ 447.146379] ubsan_epilogue+0xb/0x29 [ 447.146381] __ubsan_handle_shift_out_of_bounds.cold.14+0x26/0x80 [ 447.146486] ? radeon_cs_packet_next_reloc+0x3c/0x150 [radeon] [ 447.146521] ? r100_reloc_pitch_offset+0x27/0x150 [radeon] [ 447.146551] r200_packet0_check.cold.0+0xf/0x45 [radeon] [ 447.146592] ? r200_copy_dma+0x430/0x430 [radeon] [ 447.146626] r100_cs_parse_packet0+0x53/0xe0 [radeon] [ 447.146661] r100_cs_parse+0x12e/0x440 [radeon] [ 447.146700] ? r200_copy_dma+0x430/0x430 [radeon] [ 447.146734] radeon_cs_ioctl+0x256/0x890 [radeon] [ 447.146743] ? ttm_bo_init_reserved+0x338/0x390 [ttm] [ 447.146779] ? radeon_cs_parser_init+0x550/0x550 [radeon] [ 447.146804] drm_ioctl_kernel+0x96/0xe0 [drm] [ 447.146816] drm_ioctl+0x25f/0x530 [drm] [ 447.146850] ? radeon_cs_parser_init+0x550/0x550 [radeon] [ 447.146855] ? ktime_get_mono_fast_ns+0xb6/0x1f0 [ 447.146880] radeon_drm_ioctl+0x40/0x80 [radeon] [ 447.146905] ? radeon_pci_shutdown+0x30/0x30 [radeon] [ 447.146909] do_vfs_ioctl+0x90/0x6c0 [ 447.146913] ? handle_mm_fault+0xa48/0xfe0 [ 447.146918] ? vm_mmap_pgoff+0x88/0xd0 [ 447.146923] ? ktime_get_ts64+0x5f/0x1e0 [ 447.146925] ksys_ioctl+0x39/0x70 [ 447.146927] sys_ioctl+0x11/0x13 [ 447.146930] do_fast_syscall_32+0x95/0x1d0 [ 447.146934] entry_SYSENTER_32+0x6b/0xbd [ 447.146936] EIP: 0xb7f937cd [ 447.146939] Code: 54 cd ff ff 85 d2 8b 98 58 cd ff ff 89 c8 74 02 89 0a 5b 5d c3 8b 04 24 c3 8b 14 24 c3 8b 3c 24 c3 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d 76 00 58 b8 77 00 00 00 cd 80 90 8d 76 [ 447.146941] EAX: ffda EBX: 000e ECX: c0206466 EDX: 02311c40 [
UBSAN warning in nouveau_bios.c:1528:8
This is the first time I have tried UBSAN on this specific machine (onboard nforce 420 with HP BIOS on Nance mainboard). nouveau seems to be working fine but gives this UBSAN warning: [7.953957] nouveau :00:0d.0: NVIDIA C61 (04c000a2) [7.965101] nouveau :00:0d.0: bios: version 05.61.32.25.02 [7.966141] nouveau :00:0d.0: fb: 128 MiB of unknown memory type [8.015336] [TTM] Zone kernel: Available graphics memory: 952564 kiB [8.015339] [TTM] Initializing pool allocator [8.015344] [TTM] Initializing DMA pool allocator [8.015370] nouveau :00:0d.0: DRM: VRAM: 125 MiB [8.015372] nouveau :00:0d.0: DRM: GART: 512 MiB [8.015377] nouveau :00:0d.0: DRM: TMDS table version 1.1 [8.015379] nouveau :00:0d.0: DRM: DCB version 3.0 [8.015382] nouveau :00:0d.0: DRM: DCB outp 00: 01000310 0023 [8.015385] nouveau :00:0d.0: DRM: DCB outp 01: 00110204 98830003 [8.015386] [8.015423] UBSAN: Undefined behaviour in drivers/gpu/drm/nouveau/nouveau_bios.c:1528:8 [8.015455] shift exponent -1 is negative [8.015482] CPU: 1 PID: 148 Comm: systemd-udevd Not tainted 4.16.0-rc3-00167-g97ace515f014 #1 [8.015483] Hardware name: HP-Pavilion RT589AA-ABU t3709.uk/Nance, BIOS 5.02 11/26/2006 [8.015485] Call Trace: [8.015496] dump_stack+0x5a/0x99 [8.015500] ubsan_epilogue+0x9/0x40 [8.015503] __ubsan_handle_shift_out_of_bounds+0x124/0x160 [8.015506] ? _dev_info+0x67/0x90 [8.015509] ? dev_printk_emit+0x49/0x70 [8.015632] parse_dcb_entry+0x91e/0xd90 [nouveau] [8.015712] ? parse_bit_M_tbl_entry+0x150/0x150 [nouveau] [8.015791] olddcb_outp_foreach+0x66/0xa0 [nouveau] [8.015870] nouveau_bios_init+0x23a/0x2250 [nouveau] [8.015950] ? nouveau_ttm_init+0x3a4/0x710 [nouveau] [8.016029] nouveau_drm_load+0x229/0xf10 [nouveau] [8.016033] ? sysfs_do_create_link_sd+0xa6/0x170 [8.016067] drm_dev_register+0x1b7/0x330 [drm] [8.016070] ? pci_enable_device_flags+0x160/0x1f0 [8.016091] drm_get_pci_dev+0xee/0x2e0 [drm] [8.016172] nouveau_drm_probe+0x1dd/0x270 [nouveau] [8.016175] pci_device_probe+0x113/0x1d0 [8.016178] driver_probe_device+0x375/0x720 [8.016180] __driver_attach+0xeb/0x150 [8.016181] ? driver_probe_device+0x720/0x720 [8.016183] bus_for_each_dev+0x84/0xe0 [8.016186] bus_add_driver+0x19f/0x340 [8.016188] driver_register+0x67/0x110 [8.016190] ? 0xc0cfb000 [8.016193] do_one_initcall+0x66/0x210 [8.016197] do_init_module+0xa7/0x2a9 [8.016199] load_module+0x2548/0x3d30 [8.016202] ? __symbol_put+0x60/0x60 [8.016205] ? kernel_read_file+0x21b/0x390 [8.016208] ? kernel_read_file_from_fd+0x52/0x90 [8.016210] SYSC_finit_module+0x124/0x150 [8.016212] do_syscall_64+0x7a/0x1f0 [8.016214] ? page_fault+0x2f/0x50 [8.016217] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [8.016219] RIP: 0033:0x7f2e47b82e19 [8.016220] RSP: 002b:7ffdcdc157b8 EFLAGS: 0246 ORIG_RAX: 0139 [8.016223] RAX: ffda RBX: 5638b23c7250 RCX: 7f2e47b82e19 [8.016224] RDX: RSI: 7f2e4788d0ed RDI: 0019 [8.016225] RBP: 7f2e4788d0ed R08: R09: [8.016226] R10: 0019 R11: 0246 R12: [8.016227] R13: 5638b23c2ce0 R14: 0002 R15: 5638b23c7250 [8.016228] [8.016299] nouveau :00:0d.0: DRM: DCB conn 00: [8.016301] nouveau :00:0d.0: DRM: DCB conn 01: 1131 [8.016302] nouveau :00:0d.0: DRM: DCB conn 02: 0110 [8.016304] nouveau :00:0d.0: DRM: DCB conn 03: 0111 [8.016305] nouveau :00:0d.0: DRM: DCB conn 04: 0113 [8.016626] nouveau :00:0d.0: DRM: Saving VGA fonts [8.052781] nouveau :00:0d.0: DRM: DCB type 4 not known [8.052784] nouveau :00:0d.0: DRM: Unknown-1 has no encoders, removing [8.053728] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [8.053729] [drm] Driver supports precise vblank timestamp query. [8.055836] nouveau :00:0d.0: DRM: MM: using M2MF for buffer copies [8.084488] nouveau :00:0d.0: DRM: allocated 1280x1024 fb: 0x9000, bo 50f4b5d0 [8.084678] fbcon: nouveaufb (fb0) is primary device [8.193959] Console: switching to colour frame buffer device 160x64 [8.195378] nouveau :00:0d.0: fb0: nouveaufb frame buffer device [8.212083] [drm] Initialized nouveau 1.3.1 20120801 for :00:0d.0 on minor 0 -- Meelis Roos (mr...@linux.ee) ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [Nouveau] 4.16-rc1: UBSAN warning in nouveau/nvkm/subdev/therm/base.c + oops in nvkm_therm_clkgate_fini
> Actually this was brought up to me already, there's a fix on the mailing list > for this I reviewed a little while ago from nvidia that we should pull in: > > https://patchwork.freedesktop.org/patch/203205/ > > Would you guys mind confirming that this patch fixes your issues? It works on my amd64, P4 is still compiling. [1.124987] nouveau :04:05.0: NVIDIA NV05 (20154000) [1.161464] nouveau :04:05.0: bios: version 03.05.00.10.00 [1.161475] nouveau :04:05.0: bios: DCB table not found [1.161535] nouveau :04:05.0: bios: DCB table not found [1.161577] nouveau :04:05.0: bios: DCB table not found [1.161586] nouveau :04:05.0: bios: DCB table not found [1.344008] tsc: Refined TSC clocksource calibration: 2200.078 MHz [1.344024] clocksource: tsc: mask: 0x max_cycles: 0x1fb67c69f81, max_idle_ns: 440795210317 ns [1.344037] clocksource: Switched to clocksource tsc [1.408102] nouveau :04:05.0: tmr: unknown input clock freq [1.409471] nouveau :04:05.0: fb: 32 MiB SDRAM [1.414459] nouveau :04:05.0: DRM: VRAM: 31 MiB [1.414467] nouveau :04:05.0: DRM: GART: 128 MiB [1.414476] nouveau :04:05.0: DRM: BMP version 5.17 [1.414484] nouveau :04:05.0: DRM: No DCB data found in VBIOS [1.415629] nouveau :04:05.0: DRM: Adaptor not initialised, running VBIOS init tables. [1.415829] nouveau :04:05.0: bios: DCB table not found [1.416125] nouveau :04:05.0: DRM: Saving VGA fonts [1.477526] nouveau :04:05.0: DRM: No DCB data found in VBIOS [1.478428] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [1.478438] [drm] Driver supports precise vblank timestamp query. [1.479618] nouveau :04:05.0: DRM: MM: using M2MF for buffer copies [1.517930] nouveau :04:05.0: DRM: allocated 1024x768 fb: 0x4000, bo a09f4d1f [1.519294] nouveau :04:05.0: fb1: nouveaufb frame buffer device [1.519313] [drm] Initialized nouveau 1.3.1 20120801 for :04:05.0 on minor 1 -- Meelis Roos (mr...@linux.ee) ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: 4.16-rc1: UBSAN warning in nouveau/nvkm/subdev/therm/base.c + oops in nvkm_therm_clkgate_fini
> This is 4.16-rc1+todays git on a lowly P4 with NV5, worked fine in 4.15: NV5 in another PC (secondary card in x86-64) made the systrem crash on boot, in nvkm_therm_clkgate_fini. -- Meelis Roos (mr...@linux.ee) ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
4.16-rc1: UBSAN warning in nouveau/nvkm/subdev/therm/base.c + oops in nvkm_therm_clkgate_fini
snd_ac97_codec button rng_core ac97_bus snd_pcm snd_timer snd soundcore eeprom adm1031 adm1025 hwmon_vid i2c_core ip_tables x_tables ipv6 autofs4 [7.410357] CPU: 0 PID: 125 Comm: systemd-udevd Not tainted 4.16.0-rc1-00010-g178e834c47b0 #65 [7.410499] Hardware name: /D850GB , BIOS GB85010A.86A.0078.P18.0110081719 10/08/2001 [7.410824] EIP: nvkm_therm_clkgate_fini+0x15/0x174 [nouveau] [7.410921] EFLAGS: 00010286 CPU: 0 [7.411014] EAX: f6b3b800 EBX: ECX: 0006 EDX: 0007 [7.411109] ESI: EDI: EBP: f6155858 ESP: f6155834 [7.411205] DS: 007b ES: 007b FS: GS: 00e0 SS: 0068 [7.411299] CR0: 80050033 CR2: CR3: 3614b000 CR4: 06d0 [7.411395] Call Trace: [7.411662] ? nvkm_device_subdev+0x1b9/0x1fa [nouveau] [7.411926] nvkm_device_fini+0x113/0x3e9 [nouveau] [7.412030] ? ktime_get+0x4b/0x135 [7.412274] ? nvkm_devinit_post+0x35/0xbf [nouveau] [7.412536] nvkm_device_init+0x228/0x5b0 [nouveau] [7.412640] ? kmem_cache_alloc+0xbd/0x12a [7.412906] nvkm_udevice_init+0x51/0xa9 [nouveau] [7.413146] nvkm_object_init+0xc8/0x442 [nouveau] [7.413248] ? check_preempt_wakeup+0xc2/0x1c1 [7.413602] ? nvkm_client_child_new+0x1d/0x38 [nouveau] [7.413956] nvkm_ioctl_new+0x152/0x3d9 [nouveau] [7.414055] ? default_wake_function+0x1a/0x35 [7.414409] ? nvif_vmm_init+0x2ce/0x2ce [nouveau] [7.414788] ? nvkm_udevice_rd08+0x5b/0x5b [nouveau] [7.415150] nvkm_ioctl+0x1c6/0x48d [nouveau] [7.416466] ? nvif_client_init+0xc3/0x114 [nouveau] [7.416832] ? nvkm_client_map+0xf/0xf [nouveau] [7.417201] nvkm_client_ioctl+0x1c/0x22 [nouveau] [7.417554] nvif_object_ioctl+0x6f/0xff [nouveau] [7.417909] nvif_object_init+0xd4/0x1de [nouveau] [7.418271] nvif_device_init+0x21/0x5c [nouveau] [7.418536] nouveau_cli_init+0x21f/0xe1f [nouveau] [7.418799] ? nouveau_drm_load+0x1d/0xe11 [nouveau] [7.419058] nouveau_drm_load+0x54/0xe11 [nouveau] [7.419158] ? kernfs_new_node+0x2b/0x8e [7.419255] ? kernfs_create_link+0x55/0xcd [7.419369] ? drm_dev_register+0x12f/0x2e0 [drm] [7.419496] drm_dev_register+0x168/0x2e0 [drm] [7.419596] ? pci_enable_device_flags+0xeb/0x15e [7.419724] drm_get_pci_dev+0xbf/0x230 [drm] [7.420102] nouveau_drm_probe+0x183/0x1ea [nouveau] [7.420207] pci_device_probe+0xaa/0x163 [7.420305] driver_probe_device+0x1db/0x383 [7.420402] __driver_attach+0x86/0xb8 [7.420497] ? driver_probe_device+0x383/0x383 [7.420597] bus_for_each_dev+0x4e/0x83 [7.420694] driver_attach+0x1d/0x33 [7.420790] ? driver_probe_device+0x383/0x383 [7.420886] bus_add_driver+0x184/0x273 [7.420983] driver_register+0x66/0x107 [7.421215] ? nouveau_drm_init+0x66/0x1000 [nouveau] [7.421322] __pci_register_driver+0x47/0x71 [7.421555] nouveau_drm_init+0x18a/0x1000 [nouveau] [7.421654] ? 0xf831a000 [7.421751] do_one_initcall+0x4f/0x1e2 [7.421850] ? free_unref_page_commit.isra.88+0xd5/0x176 [7.421947] ? kvfree+0x3c/0x3e [7.422041] ? __vunmap+0x89/0xef [7.422136] ? do_init_module+0x1a/0x23f [7.422232] do_init_module+0x82/0x23f [7.422329] load_module+0x243c/0x36ae [7.422428] ? kernel_read+0x4c/0xa1 [7.422524] SyS_finit_module+0x78/0x8d [7.422624] do_fast_syscall_32+0xc1/0x31b [7.422722] entry_SYSENTER_32+0x4e/0x7c [7.422817] EIP: 0xb7ee9ad5 [7.422907] EFLAGS: 0296 CPU: 0 [7.423001] EAX: ffda EBX: 0019 ECX: b7ce0bdd EDX: [7.423098] ESI: 00eb6670 EDI: 00ebe610 EBP: ESP: bff8704c [7.423195] DS: 007b ES: 007b FS: GS: 0033 SS: 007b [7.423291] Code: e9 30 ff ff ff 31 d2 b8 78 cf b0 f8 e8 ba 07 a2 c8 e9 0f ff ff ff 55 89 e5 57 56 53 83 ec 18 89 c3 89 d6 85 c0 0f 84 2c 01 00 00 <8b> 3b 85 ff 0f 84 11 01 00 00 8b 47 30 85 c0 0f 84 a1 00 00 00 [7.423757] EIP: nvkm_therm_clkgate_fini+0x15/0x174 [nouveau] SS:ESP: 0068:f6155834 [7.423899] CR2: [7.424033] ---[ end trace cad535783d11d7b9 ]--- -- Meelis Roos (mr...@linux.ee) ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: Radeon rv250 GPU acceleration broken in 4.15-rc6
> Beacuse of PTI, I decided to test 4.15-rc6 on most of my test machines. > And I happened to notice a radeon problem on RV250 era card with no > monitor attached. 4.15-rc1 and earlier kernels did not show these > errors, not kernels between rc1 and rc6 have been tested yet. Sorry, I can not reproduce it, so it looks like random noise from an old computer. About 10 reboots later, I have not managed to reproduce this problem. -- Meelis Roos (mr...@linux.ee) ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Radeon rv250 GPU acceleration broken in 4.15-rc6
] Initialized radeon 2.50.0 20080528 for :01:05.0 on minor 0 [6.290422] [drm] Cannot find any crtc or sizes -- Meelis Roos (mr...@linux.ee) ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
i915 WARNING: Missing switch case (16) in gen6_check_mailbox_status
> Meelis, what does 'lspci -nns 2' say for you? 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) > > BR, > Jani. > > On Tue, 06 Sep 2016, Jani Nikula wrote: > > Lyude, this is due to > > > > commit 87660502f1a4d51fb043e89a45d30c9917787c22 > > Author: Lyude > > Date: Wed Aug 17 15:55:53 2016 -0400 > > > > drm/i915/gen6+: Interpret mailbox error flags > > > > and on its way to stable. > > > > BR, > > Jani. > > > > > > On Mon, 29 Aug 2016, Meelis Roos wrote: > >> Tried 4.8-rc4 on my i5-2400 PC, got this warning: > >> > >> [ 14.579557] i915 :00:02.0: fb0: inteldrmfb frame buffer device > >> [ 15.847321] [ cut here ] > >> [ 15.847346] WARNING: CPU: 0 PID: 208 at > >> drivers/gpu/drm/i915/intel_pm.c:7866 sandybridge_pcode_write+0x109/0x1f0 > >> [i915] > >> [ 15.847348] Missing switch case (16) in gen6_check_mailbox_status > >> [ 15.847349] Modules linked in: cpufreq_powersave cpufreq_userspace > >> cpufreq_conservative joydev hid_generic usbhid hid x86_pkg_temp_thermal > >> kvm_intel kvm irqbypass crc32c_intel aesni_intel snd_hda_codec_realtek > >> snd_hda_codec_generic iTCO_wdt i915 aes_x86_64 iTCO_vendor_support > >> glue_helper lrw ablk_helper cryptd video i2c_algo_bit drm_kms_helper > >> psmouse pcspkr syscopyarea sysfillrect sysimgblt fb_sys_fops ehci_pci > >> ehci_hcd snd_hda_intel xhci_pci xhci_hcd e1000e snd_hda_codec snd_hwdep > >> usbcore drm snd_hda_core usb_common i2c_i801 ptp pps_core i2c_smbus > >> snd_pcm_oss snd_mixer_oss snd_pcm snd_timer evdev snd tpm_tis lpc_ich > >> parport_pc tpm_tis_core mfd_core parport nuvoton_cir rc_core tpm soundcore > >> floppy w83627ehf hwmon_vid coretemp hwmon eeprom i2c_core loop ip_tables > >> x_tables autofs4 > >> [ 15.847395] CPU: 0 PID: 208 Comm: kworker/0:2 Not tainted 4.8.0-rc4 #213 > >> [ 15.847396] Hardware name: /DQ67OW, BIOS > >> SWQ6710H.86A.0066.2012.1105.1504 11/05/2012 > >> [ 15.847412] Workqueue: events intel_gen6_powersave_work [i915] > >> [ 15.847414] 812d8198 88023191fd70 > >> > >> [ 15.847417] 81056d1e 88022ea4 88023191fdc0 > >> > >> [ 15.847419] 88022ea4a3c8 88022ea487c0 088023e21ba0 > >> 81056d8f > >> [ 15.847422] Call Trace: > >> [ 15.847427] [] ? dump_stack+0x46/0x5e > >> [ 15.847429] [] ? __warn+0xbe/0xe0 > >> [ 15.847431] [] ? warn_slowpath_fmt+0x4f/0x60 > >> [ 15.847446] [] ? sandybridge_pcode_write+0x109/0x1f0 > >> [i915] > >> [ 15.847459] [] ? > >> intel_gen6_powersave_work+0x2a8/0x1400 [i915] > >> [ 15.847462] [] ? process_one_work+0x1eb/0x480 > >> [ 15.847465] [] ? worker_thread+0x47/0x4c0 > >> [ 15.847467] [] ? __schedule+0x1d7/0x660 > >> [ 15.847469] [] ? process_one_work+0x480/0x480 > >> [ 15.847472] [] ? kthread+0xbd/0xe0 > >> [ 15.847475] [] ? ret_from_fork+0x1f/0x40 > >> [ 15.847478] [] ? kthread_worker_fn+0x160/0x160 > >> [ 15.847487] ---[ end trace ad9e991297d99be1 ]--- > > -- Meelis Roos (mroos at linux.ee)
i915 WARNING: Missing switch case (16) in gen6_check_mailbox_status
Tried 4.8-rc4 on my i5-2400 PC, got this warning: [ 14.579557] i915 :00:02.0: fb0: inteldrmfb frame buffer device [ 15.847321] [ cut here ] [ 15.847346] WARNING: CPU: 0 PID: 208 at drivers/gpu/drm/i915/intel_pm.c:7866 sandybridge_pcode_write+0x109/0x1f0 [i915] [ 15.847348] Missing switch case (16) in gen6_check_mailbox_status [ 15.847349] Modules linked in: cpufreq_powersave cpufreq_userspace cpufreq_conservative joydev hid_generic usbhid hid x86_pkg_temp_thermal kvm_intel kvm irqbypass crc32c_intel aesni_intel snd_hda_codec_realtek snd_hda_codec_generic iTCO_wdt i915 aes_x86_64 iTCO_vendor_support glue_helper lrw ablk_helper cryptd video i2c_algo_bit drm_kms_helper psmouse pcspkr syscopyarea sysfillrect sysimgblt fb_sys_fops ehci_pci ehci_hcd snd_hda_intel xhci_pci xhci_hcd e1000e snd_hda_codec snd_hwdep usbcore drm snd_hda_core usb_common i2c_i801 ptp pps_core i2c_smbus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer evdev snd tpm_tis lpc_ich parport_pc tpm_tis_core mfd_core parport nuvoton_cir rc_core tpm soundcore floppy w83627ehf hwmon_vid coretemp hwmon eeprom i2c_core loop ip_tables x_tables autofs4 [ 15.847395] CPU: 0 PID: 208 Comm: kworker/0:2 Not tainted 4.8.0-rc4 #213 [ 15.847396] Hardware name: /DQ67OW, BIOS SWQ6710H.86A.0066.2012.1105.1504 11/05/2012 [ 15.847412] Workqueue: events intel_gen6_powersave_work [i915] [ 15.847414] 812d8198 88023191fd70 [ 15.847417] 81056d1e 88022ea4 88023191fdc0 [ 15.847419] 88022ea4a3c8 88022ea487c0 088023e21ba0 81056d8f [ 15.847422] Call Trace: [ 15.847427] [] ? dump_stack+0x46/0x5e [ 15.847429] [] ? __warn+0xbe/0xe0 [ 15.847431] [] ? warn_slowpath_fmt+0x4f/0x60 [ 15.847446] [] ? sandybridge_pcode_write+0x109/0x1f0 [i915] [ 15.847459] [] ? intel_gen6_powersave_work+0x2a8/0x1400 [i915] [ 15.847462] [] ? process_one_work+0x1eb/0x480 [ 15.847465] [] ? worker_thread+0x47/0x4c0 [ 15.847467] [] ? __schedule+0x1d7/0x660 [ 15.847469] [] ? process_one_work+0x480/0x480 [ 15.847472] [] ? kthread+0xbd/0xe0 [ 15.847475] [] ? ret_from_fork+0x1f/0x40 [ 15.847478] [] ? kthread_worker_fn+0x160/0x160 [ 15.847487] ---[ end trace ad9e991297d99be1 ]--- -- Meelis Roos (mroos at linux.ee)
i865, drm_modeset_lock_all: BUG: unable to handle kernel NULL pointer dereference at 00000104
> > > Looks like an incorrect call to drm_encoder_cleanup() from the error > > > path. If we hit the error path we have never called drm_encoder_init. > > > Please try: > > > > > > diff --git a/drivers/gpu/drm/i915/intel_dvo.c > > > b/drivers/gpu/drm/i915/intel_dvo.c > > > index 47bdf9dad0d3..b9e5a63a7c9e 100644 > > > --- a/drivers/gpu/drm/i915/intel_dvo.c > > > +++ b/drivers/gpu/drm/i915/intel_dvo.c > > > @@ -554,7 +554,6 @@ void intel_dvo_init(struct drm_device *dev) > > > return; > > > } > > > > > > - drm_encoder_cleanup(_encoder->base); > > > kfree(intel_dvo); > > > kfree(intel_connector); > > > } > > > > It works - the BUG is gone. > > > > Now I get just > > [drm:__intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* pipe A underrun > > Other than the annoying underrun, is everything else as expected? i.e. > no connected outputs? Have we lost dvo detection? Yes, as expected - there is no monitor connected. -- Meelis Roos (mroos at linux.ee)
i865, drm_modeset_lock_all: BUG: unable to handle kernel NULL pointer dereference at 00000104
> Looks like an incorrect call to drm_encoder_cleanup() from the error > path. If we hit the error path we have never called drm_encoder_init. > Please try: > > diff --git a/drivers/gpu/drm/i915/intel_dvo.c > b/drivers/gpu/drm/i915/intel_dvo.c > index 47bdf9dad0d3..b9e5a63a7c9e 100644 > --- a/drivers/gpu/drm/i915/intel_dvo.c > +++ b/drivers/gpu/drm/i915/intel_dvo.c > @@ -554,7 +554,6 @@ void intel_dvo_init(struct drm_device *dev) > return; > } > > - drm_encoder_cleanup(_encoder->base); > kfree(intel_dvo); > kfree(intel_connector); > } It works - the BUG is gone. Now I get just [drm:__intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* pipe A underrun [ 10.499523] agpgart-intel :00:00.0: Intel 865 Chipset [ 10.499623] agpgart-intel :00:00.0: detected gtt size: 131072K total, 131072K mappable [ 10.499928] agpgart-intel :00:00.0: detected 16384K stolen memory [ 10.500939] [drm] Memory usable by graphics device = 128M [ 10.501029] [drm] Replacing VGA console driver [ 10.502804] Console: switching to colour dummy device 80x25 [ 10.504746] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 10.504760] [drm] Driver supports precise vblank timestamp query. [ 11.210224] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 11.237197] [drm] RC6 disabled, disabling runtime PM support [ 11.237407] [drm] initialized overlay support [ 11.362560] [drm:__intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* pipe A underrun [ 11.418776] i915 :00:02.0: No connectors reported connected with modes [ 11.418792] [drm] Cannot find any crtc or sizes - going 1024x768 [ 11.421148] fbcon: inteldrmfb (fb0) is primary device [ 11.448292] Console: switching to colour frame buffer device 128x48 [ 11.458643] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device -- Meelis Roos (mroos at linux.ee)
i865, drm_modeset_lock_all: BUG: unable to handle kernel NULL pointer dereference at 00000104
3 e8 75 ec ff ff 89 d8 08 79 05 e8 fa 0a 00 00 5b c3 53 89 c3 85 c0 74 1b 8b 03 83 [ 10.067180] EIP: [] mutex_lock+0xa/0x15 SS:ESP 0068:f5971b58 [ 10.067190] CR2: 0104 [ 10.067222] ---[ end trace 049f1f09da45a856 ]--- [ 283.840252] random: crng init done -- Meelis Roos (mroos at linux.ee)
Radeon R100 UBSAN warning
I am seeing the following UBSAN warning on three of my computers (4.6.0 with UBSAN turned on). I am reporting this because some of the UBSAN reports have been correct (some have been false positives though). [9.372287] [9.372423] UBSAN: Undefined behaviour in drivers/gpu/drm/radeon/r100.c:595:15 [9.372559] shift exponent 255 is too large for 32-bit type 'int' [9.372696] CPU: 0 PID: 222 Comm: systemd-udevd Not tainted 4.6.0 #129 [9.372831] Hardware name: MicroLink /D850MV , BIOS MV85010A.86A.0067.P24.0304081124 04/08/2003 [9.373058] c12244c8 f8df9704 c1224aa4 f8df96d4 0001 0202 00353532 [9.373516] 0236 0246 0246 0006 00010246 001c 0006 [9.373972] c17f6842 0031 c1074ab1 0246 0002 f4a06800 [9.374427] Call Trace: [9.374567] [] ? ubsan_epilogue+0x8/0x23 [9.374704] [] ? __ubsan_handle_shift_out_of_bounds+0xd5/0xdd [9.374843] [] ? vprintk_emit+0x37a/0x390 [9.375156] [] ? r100_hpd_init+0x72/0xb7 [radeon] [9.375437] [] ? radeon_modeset_init+0x753/0xe7b [radeon] [9.375719] [] ? radeon_driver_load_kms+0xd8/0x196 [radeon] [9.375884] [] ? drm_dev_register+0x75/0xad [drm] [9.376041] [] ? drm_get_pci_dev+0x11d/0x23e [drm] [9.376135] [] ? pci_device_probe+0x9f/0xee [9.376135] [] ? driver_probe_device+0x149/0x271 [9.376135] [] ? __driver_attach+0x86/0xa1 [9.376135] [] ? bus_for_each_dev+0x47/0x5a [9.376135] [] ? driver_attach+0x24/0x27 [9.376135] [] ? driver_probe_device+0x271/0x271 [9.376135] [] ? bus_add_driver+0xed/0x1db [9.376135] [] ? 0xf8e58000 [9.376135] [] ? driver_register+0x9a/0xcb [9.376135] [] ? do_one_initcall+0x159/0x1d9 [9.376135] [] ? __free_one_page+0x1a1/0x369 [9.376135] [] ? kernel_poison_pages+0x10/0xc4 [9.376135] [] ? free_pages_prepare+0x1f7/0x21c [9.376135] [] ? kmem_cache_alloc+0xa2/0xd6 [9.376135] [] ? do_init_module+0x17/0x21a [9.376135] [] ? do_init_module+0x76/0x21a [9.376135] [] ? load_module+0x1b28/0x206a [9.376135] [] ? SyS_finit_module+0x71/0x79 [9.376135] [] ? do_fast_syscall_32+0xd9/0x111 [9.376135] [] ? sysenter_past_esp+0x40/0x6a [9.376135] -- Meelis Roos (mroos at linux.ee)
UBSAN warning in r100: shift exponent 255 is too large for 32-bit type 'int'
is 1024 [8.979895] fbcon: radeondrmfb (fb0) is primary device [8.988343] Console: switching to colour frame buffer device 128x48 [8.998095] radeon :01:00.0: fb0: radeondrmfb frame buffer device [8.998181] [drm] Initialized radeon 2.43.0 20080528 for :01:00.0 on minor 0 -- Meelis Roos (mroos at linux.ee)
[PATCH] drm/i915: Init power domains early in driver load
> commit ac9b8236551d1177fd07b56aef9b565d1864420d
> Author: Ville Syrjälä
> Date: Fri Nov 27 18:55:26 2015 +0200
>
> drm/i915: Introduce a gmbus power domain
>
> gmbus also needs the power domain infrastructure right from the start,
> since as soon as we register the i2c controllers someone can use them.
>
> v2: Adjust cleanup paths too (Chris).
>
> v3: Rebase onto -nightly (totally bogus tree I had lying around) and
> also move dpio init head (Ville).
>
> v4: Ville instead suggested to move gmbus setup later in the sequence,
> since it's only needed by the modeset code.
>
> v5: Move even close to the actual user, right next to the comment that
> states where we really need gmbus (and interrupts!).
>
> Cc: Ville Syrjälä
> Cc: Patrik Jakobsson
> Cc: Imre Deak
> Cc: Jani Nikula
> Cc: Meelis Roos
> Cc: Chris Wilson
> Fixes: ac9b8236551d ("drm/i915: Introduce a gmbus power domain")
> Cc: stable at vger.kernel.org
> References: http://www.spinics.net/lists/intel-gfx/msg83075.html
> Signed-off-by: Daniel Vetter
> ---
>
> Meelis, can you pls retest this one?
I also confirmed that my 865G chipset computer was suffering from the
same problem and the patch also helps on D865GLC mainboard with my
userspace that autoloads eeprom driver.
--
Meelis Roos (mroos at linux.ee)
[PATCH] drm/i915: Init power domains early in driver load
> commit ac9b8236551d1177fd07b56aef9b565d1864420d
> Author: Ville Syrjälä
> Date: Fri Nov 27 18:55:26 2015 +0200
>
> drm/i915: Introduce a gmbus power domain
>
> gmbus also needs the power domain infrastructure right from the start,
> since as soon as we register the i2c controllers someone can use them.
>
> v2: Adjust cleanup paths too (Chris).
>
> v3: Rebase onto -nightly (totally bogus tree I had lying around) and
> also move dpio init head (Ville).
>
> v4: Ville instead suggested to move gmbus setup later in the sequence,
> since it's only needed by the modeset code.
>
> v5: Move even close to the actual user, right next to the comment that
> states where we really need gmbus (and interrupts!).
>
> Cc: Ville Syrjälä
> Cc: Patrik Jakobsson
> Cc: Imre Deak
> Cc: Jani Nikula
> Cc: Meelis Roos
> Cc: Chris Wilson
> Fixes: ac9b8236551d ("drm/i915: Introduce a gmbus power domain")
> Cc: stable at vger.kernel.org
> References: http://www.spinics.net/lists/intel-gfx/msg83075.html
> Signed-off-by: Daniel Vetter
> ---
>
> Meelis, can you pls retest this one?
Tested successfully on SNB computer.
>
> Thanks, Daniel
> ---
> drivers/gpu/drm/i915/i915_dma.c | 6 +++---
> drivers/gpu/drm/i915/intel_display.c | 2 ++
> 2 files changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_dma.c b/drivers/gpu/drm/i915/i915_dma.c
> index 988a3806512a..d70d96fe553b 100644
> --- a/drivers/gpu/drm/i915/i915_dma.c
> +++ b/drivers/gpu/drm/i915/i915_dma.c
> @@ -406,6 +406,8 @@ static int i915_load_modeset_init(struct drm_device *dev)
> if (ret)
> goto cleanup_gem_stolen;
>
> + intel_setup_gmbus(dev);
> +
> /* Important: The output setup functions called by modeset_init need
>* working irqs for e.g. gmbus and dp aux transfers. */
> intel_modeset_init(dev);
> @@ -455,6 +457,7 @@ cleanup_gem:
> cleanup_irq:
> intel_guc_ucode_fini(dev);
> drm_irq_uninstall(dev);
> + intel_teardown_gmbus(dev);
> cleanup_gem_stolen:
> i915_gem_cleanup_stolen(dev);
> cleanup_vga_switcheroo:
> @@ -1028,7 +1031,6 @@ int i915_driver_load(struct drm_device *dev, unsigned
> long flags)
>
> /* Try to make sure MCHBAR is enabled before poking at it */
> intel_setup_mchbar(dev);
> - intel_setup_gmbus(dev);
> intel_opregion_setup(dev);
>
> i915_gem_load(dev);
> @@ -1101,7 +1103,6 @@ out_gem_unload:
> if (dev->pdev->msi_enabled)
> pci_disable_msi(dev->pdev);
>
> - intel_teardown_gmbus(dev);
> intel_teardown_mchbar(dev);
> pm_qos_remove_request(_priv->pm_qos);
> destroy_workqueue(dev_priv->gpu_error.hangcheck_wq);
> @@ -1203,7 +1204,6 @@ int i915_driver_unload(struct drm_device *dev)
>
> intel_csr_ucode_fini(dev_priv);
>
> - intel_teardown_gmbus(dev);
> intel_teardown_mchbar(dev);
>
> destroy_workqueue(dev_priv->hotplug.dp_wq);
> diff --git a/drivers/gpu/drm/i915/intel_display.c
> b/drivers/gpu/drm/i915/intel_display.c
> index 37945ddb4dad..ac0038bf4fbf 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -15971,6 +15971,8 @@ void intel_modeset_cleanup(struct drm_device *dev)
> mutex_lock(>struct_mutex);
> intel_cleanup_gt_powersave(dev);
> mutex_unlock(>struct_mutex);
> +
> + intel_teardown_gmbus(dev);
> }
>
> /*
>
--
Meelis Roos (mroos at ut.ee) http://www.cs.ut.ee/~mroos/
bisected: i915 modeset broken in ac9b8236551d1177fd07b56aef9b565d1864420d
> > intel_setup_gmbus registers the i2c adapters, which does transfers on > > the i2c bus on probe, and this happens before intel_power_domains_init > > which initializes the power domain lock. > > > > The bisect and backtrace make sense and are not mysterious at all. > > > > Not sure of the fix though, are we better off changing the init order, > > or making sure the probes don't happen or don't screw us up. > > So I started wondering why we are not seeing this. To reproduce, looks > like you'll need to have an i2c driver with class I2C_CLASS_DDC for the > i2c detect (and the bug) to happen. In tree, the only ones seem to be > > drivers/misc/eeprom/eeprom.c Yes, I have that for DIMM SPD information access. > drivers/staging/olpc_dcon/olpc_dcon.c > > I presume you have one or the other. > > No matter what, userspace can access the adapter right away when we > register it, so this needs to be fixed along the lines of [1]. > > BR, > Jani. > > > [1] > http://patchwork.freedesktop.org/patch/msgid/1452157856-27360-1-git-send-email-daniel.vetter > at ffwll.ch -- Meelis Roos (mroos at linux.ee)
[PATCH] drm/i915: Init power domains early in driver load
> commit ac9b8236551d1177fd07b56aef9b565d1864420d
> Author: Ville Syrjälä
> Date: Fri Nov 27 18:55:26 2015 +0200
>
> drm/i915: Introduce a gmbus power domain
>
> gmbus also needs the power domain infrastructure right from the start,
> since as soon as we register the i2c controllers someone can use them.
>
> Cc: Ville Syrjälä
> Cc: Patrik Jakobsson
> Cc: Imre Deak
> Cc: Jani Nikula
> Cc: Meelis Roos
> Fixes: ac9b8236551d ("drm/i915: Introduce a gmbus power domain")
> Cc: stable at vger.kernel.org
> References: http://www.spinics.net/lists/intel-gfx/msg83075.html
> Signed-off-by: Daniel Vetter
Tested-by: Meelis Roos
Worked fine on my SNB computer.
> ---
> drivers/gpu/drm/i915/i915_dma.c | 6 ++
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_dma.c b/drivers/gpu/drm/i915/i915_dma.c
> index b4741d121a74..405aba2ca736 100644
> --- a/drivers/gpu/drm/i915/i915_dma.c
> +++ b/drivers/gpu/drm/i915/i915_dma.c
> @@ -396,8 +396,6 @@ static int i915_load_modeset_init(struct drm_device *dev)
> if (ret)
> goto cleanup_vga_switcheroo;
>
> - intel_power_domains_init_hw(dev_priv);
> -
> ret = intel_irq_install(dev_priv);
> if (ret)
> goto cleanup_gem_stolen;
> @@ -1025,6 +1023,8 @@ int i915_driver_load(struct drm_device *dev, unsigned
> long flags)
>
> intel_irq_init(dev_priv);
> intel_uncore_sanitize(dev);
> + intel_power_domains_init(dev_priv);
> + intel_power_domains_init_hw(dev_priv);
>
> /* Try to make sure MCHBAR is enabled before poking at it */
> intel_setup_mchbar(dev);
> @@ -1057,8 +1057,6 @@ int i915_driver_load(struct drm_device *dev, unsigned
> long flags)
> goto out_gem_unload;
> }
>
> - intel_power_domains_init(dev_priv);
> -
> ret = i915_load_modeset_init(dev);
> if (ret < 0) {
> DRM_ERROR("failed to init modeset\n");
>
--
Meelis Roos (mroos at ut.ee) http://www.cs.ut.ee/~mroos/
bisected: i915 modeset broken in ac9b8236551d1177fd07b56aef9b565d1864420d
> On Mon, Dec 14, 2015 at 03:31:09PM +0200, Meelis Roos wrote: > > Between 4.4-rc3 and 4.4-rc4, i915 modesetting broke on my i5-2400 PC. > > That would seem to be SNB. Yes. > > Instead of seeing the new dense graphics mode, I see the last VGA text > > lines and no X appears either. > > That's a bit weird. SNB has no power power wells, so only runtime PM > could be a factor, but it should not kick in that fast during boot even > if you enable it before loading the driver since we set the delay to 10 > seconds. > > And in any case the commit you list shouldn't really change anything > for SNB. We used to grab a rpm reference for gmbus via > intel_aux_display_runtime_get() and now we get it via the GMBUS power > domain instead. I captured dmesg from failing boot, from system logs. gmbus has something to do with it: [drm:i915_dump_device_info] i915 device info: gen=6, pciid=0x0102 rev=0x09 flags=need_gfx_hws,has_fbc,has_hotplug,has_llc, [drm:intel_detect_pch] Found CougarPoint PCH [drm] Memory usable by graphics device = 2048M [drm:i915_gem_gtt_init] GMADR size = 256M [drm:i915_gem_gtt_init] GTT stolen size = 32M [drm:i915_gem_gtt_init] ppgtt mode: 1 [drm] Replacing VGA console driver Console: switching to colour dummy device 80x25 BUG: unable to handle kernel NULL pointer dereference at (null) IP: [] __mutex_lock_slowpath+0x74/0x100 PGD 0 Oops: 0002 [#1] SMP Modules linked in: i915(+) x86_pkg_temp_thermal kvm_intel kvm irqbypass video crc32c_intel i2c_algo_bit aesni_intel aes_x86_64 glue_helper lrw drm_kms_helper syscopyarea sysfillrect ablk_helper cryptd iTCO_wdt sysimgblt iTCO_vendor_support fb_sys_fops snd_hda_codec_realtek drm psmouse snd_hda_codec_generic e1000e xhci_pci xhci_hcd snd_hda_intel pcspkr snd_hda_codec snd_hwdep snd_hda_core snd_pcm_oss snd_mixer_oss i2c_i801 snd_pcm ehci_pci ehci_hcd nuvoton_cir usbcore snd_timer parport_pc ptp pps_core evdev rc_core parport snd usb_common soundcore tpm_tis tpm floppy lpc_ich mfd_core md_mod w83627ehf hwmon_vid coretemp hwmon eeprom i2c_core loop autofs4 CPU: 0 PID: 390 Comm: systemd-udevd Not tainted 4.4.0-rc2-6-gac9b823 #185 Hardware name: /DQ67OW, BIOS SWQ6710H.86A.0066.2012.1105.1504 11/05/2012 task: 8800b7e48c40 ti: 88023342 task.ti: 88023342 RIP: 0010:[] [] __mutex_lock_slowpath+0x74/0x100 RSP: 0018:880233423620 EFLAGS: 00010282 RAX: RBX: 8800b6a594f8 RCX: 8800b7e48c40 RDX: 0001 RSI: 8800b7e48c40 RDI: 8800b6a594fc RBP: 880233423670 R08: R09: 0001 R10: 8800b6a507e8 R11: 0013 R12: 8800b7e48c40 R13: 8800b6a594fc R14: R15: 8800b6a59500 FS: 7f58846428c0() GS:88023e20() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: CR3: 000233424000 CR4: 000406f0 Stack: 8800b6a59500 8802353b7148 0206 8800b6a5 8800b6a594f8 001d 8800b6a594f8 8800b6a5 8800b6a5 fffeea06 81519d1b Call Trace: [] ? mutex_lock+0x1b/0x30 [] ? intel_display_power_get+0x29/0xe0 [i915] [] ? gmbus_xfer+0x38/0x680 [i915] [] ? try_to_wake_up+0x43/0x320 [] ? __i2c_transfer+0x106/0x380 [i2c_core] [] ? i2c_transfer+0x6d/0xa0 [i2c_core] [] ? i2c_smbus_xfer_emulated+0x105/0x4c0 [i2c_core] [] ? __wake_up_common+0x4e/0x90 [] ? idr_get_empty_slot+0x18b/0x390 [] ? i2c_smbus_xfer+0x118/0x2e0 [i2c_core] [] ? i2c_default_probe+0xc5/0x110 [i2c_core] [] ? i2c_check_addr_busy+0x39/0x60 [i2c_core] [] ? i2c_do_add_adapter+0x159/0x260 [i2c_core] [] ? i2c_do_add_adapter+0x260/0x260 [i2c_core] [] ? bus_for_each_drv+0x55/0x90 [] ? i2c_register_adapter+0x1c6/0x320 [i2c_core] [] ? intel_setup_gmbus+0x220/0x310 [i915] [] ? i915_driver_load+0x4eb/0x15e0 [i915] [] ? drm_dev_register+0x9c/0xb0 [drm] [] ? drm_get_pci_dev+0x89/0x1d0 [drm] [] ? pci_device_probe+0x81/0xe0 [] ? driver_probe_device+0x147/0x310 [] ? __driver_attach+0x7b/0x80 [] ? driver_probe_device+0x310/0x310 [] ? bus_for_each_dev+0x5a/0x90 [] ? bus_add_driver+0x1a4/0x220 [] ? 0xa033c000 [] ? driver_register+0x57/0xc0 [] ? do_one_initcall+0x81/0x1b0 [] ? kmem_cache_alloc_trace+0x31/0x120 [] ? do_init_module+0x5b/0x1dc [] ? load_module+0x1e52/0x2220 [] ? __symbol_put+0x50/0x50 [] ? SyS_finit_module+0x85/0x90 [] ? entry_SYSCALL_64_fastpath+0x16/0x6a Code: e8 c2 1a 00 00 8b 03 83 f8 01 0f 84 92 00 00 00 48 8b 43 10 4c 8d 7b 08 48 89 63 10 41 be ff ff ff ff 4c 89 3c 24 48 89 44 24 08 <48> 89 20 4c 89 64 24 10 eb 19 49 c7 04 24 02 00 00 00 c6 43 04 RIP [] __mutex_lock_slowpath+0x74/0x100 RSP CR2: ---[ end trace 5e2e7e41ffefe21d ]--- > So this bisect result is somewhat mysterious. A full dmesg with > drm.debug=0xe with and without the offending patch reverted wo
bisected: i915 modeset broken in ac9b8236551d1177fd07b56aef9b565d1864420d
Between 4.4-rc3 and 4.4-rc4, i915 modesetting broke on my i5-2400 PC. Instead of seeing the new dense graphics mode, I see the last VGA text lines and no X appears either. I saw something similar on I865G but have not had time to check if it is the same issue. ac9b8236551d1177fd07b56aef9b565d1864420d is the first bad commit commit ac9b8236551d1177fd07b56aef9b565d1864420d Author: Ville Syrjälä Date: Fri Nov 27 18:55:26 2015 +0200 drm/i915: Introduce a gmbus power domain Currently the gmbus code uses intel_aux_display_runtime_get/put in an effort to make sure the hardware is powered up sufficiently for gmbus. That function only takes the runtime PM reference which on VLV/CHV/BXT is not enough. We need the disp2d/pipe-a well on VLV/CHV and power well 2 on BXT. So add a new power domnain for gmbus and kill off the now unused intel_aux_display_runtime_get/put. And change intel_hdmi_set_edid() to use the gmbus power domain too since that's all we need there. Also toss in a BUILD_BUG_ON() to catch problems if we run out of bits for power domains. We're already really close to the limit... [Patrik: Add gmbus string to debugfs output] Signed-off-by: Ville Syrjälä Reviewed-by: Patrik Jakobsson [Cherry-picked from drm-intel-next-queued f0ab43e6 (Imre)] Signed-off-by: Imre Deak Link: http://patchwork.freedesktop.org/patch/msgid/1448643329-18675-3-git-send-email-imre.deak at intel.com Signed-off-by: Jani Nikula :04 04 39379146d7e6dda8a4d5f8781ee3d307cce8c47e f4f09fae0485ad6263d31d425296fa9cd7de343b M drivers -- Meelis Roos (mroos at linux.ee)
4.3 nouveau regression: nv04_fbcon_imageblit(?) deadlock
> > 4.2.0 (both packaged and self-compiled) worked fine, 4.3.0 and 4.4-rc2 > > exhibit a problem: after the system has started up, I start getting > > messages like INFO: task kworker/0:2:652 blocked for more than 120 > > seconds. where nv04_fbcon_imageblit and nouveau_pmops_runtime_suspend > > show up in trace. The trace keeps reappearing, also breaking lspci and > > clean reboot (they hang). > > > > dmesg from 4.4-rc2, drm-debug=0xe > > http://kodu.ut.ee/~mroos/download/dm-nouveau-4.4-rc2 > > > > dmesg from 4.2.0, drm.debug=0xe > > http://kodu.ut.ee/~mroos/download/dm-nouveau-4.2 > > > > lspci -vvv > > http://kodu.ut.ee/~mroos/download/lspci.nouveau > > > > config: > > http://kodu.ut.ee/~mroos/download/nouveau-config > > > > Is there anything else I can provide? > > Runtime pm shouldn't be a thing for these GPUs... can you see if > booting with nouveau.runpm=0 fixes it? Sounds like we reintroduced > some problem for GPUs that don't have optimus-style acpi power off > hooks. Yes, nouveau.runpm=0 makes the hang go away, and reboot and lspci also started working without hangs. -- Meelis Roos (mroos at linux.ee)
4.3 nouveau regression: nv04_fbcon_imageblit(?) deadlock
Hello, this is a report about a PC with 3 nvidia cards - PCI-E NV44, AGP NV34 and PCI NV05. Only NV44 has monitor attached currently. 4.2.0 (both packaged and self-compiled) worked fine, 4.3.0 and 4.4-rc2 exhibit a problem: after the system has started up, I start getting messages like INFO: task kworker/0:2:652 blocked for more than 120 seconds. where nv04_fbcon_imageblit and nouveau_pmops_runtime_suspend show up in trace. The trace keeps reappearing, also breaking lspci and clean reboot (they hang). dmesg from 4.4-rc2, drm-debug=0xe http://kodu.ut.ee/~mroos/download/dm-nouveau-4.4-rc2 dmesg from 4.2.0, drm.debug=0xe http://kodu.ut.ee/~mroos/download/dm-nouveau-4.2 lspci -vvv http://kodu.ut.ee/~mroos/download/lspci.nouveau config: http://kodu.ut.ee/~mroos/download/nouveau-config Is there anything else I can provide? -- Meelis Roos (mroos at linux.ee)
4.2-rc7: mutex-related crash on boot (radeon?)
> > Hi, I tried 4.2-rc7 and todays 4.2-rc7+git on a P4 PC with Intel 850 > > chipset and old Radeon graphics. The machine crashes during boot and > > starts spamming dmesg as fast as it scrolls. Netconsole caught the > > dmesg. 4.1.0 worked fine. > > > > The first crash seems to be related to radeon_hotplug_work_func during > > radeon initialization. > > Looks like a race at startup, I've sent a fix to dri-devel that should work. It works. Applied on top of 4.2.0-rc7-00071-g0bad909 and everything seems to work fine, no crash. -- Meelis Roos (mroos at linux.ee)
4.2-rc7: mutex-related crash on boot (radeon?)
> On 19 August 2015 at 00:28, Meelis Roos wrote: > > Hi, I tried 4.2-rc7 and todays 4.2-rc7+git on a P4 PC with Intel 850 > > chipset and old Radeon graphics. The machine crashes during boot and > > starts spamming dmesg as fast as it scrolls. Netconsole caught the > > dmesg. 4.1.0 worked fine. > > > > The first crash seems to be related to radeon_hotplug_work_func during > > radeon initialization. > > Looks like a race at startup, I've sent a fix to dri-devel that should work. Thank you - found it. Will test tomorrow. -- Meelis Roos (mroos at linux.ee)
4.2-rc7: mutex-related crash on boot (radeon?)
Hi, I tried 4.2-rc7 and todays 4.2-rc7+git on a P4 PC with Intel 850 chipset and old Radeon graphics. The machine crashes during boot and starts spamming dmesg as fast as it scrolls. Netconsole caught the dmesg. 4.1.0 worked fine. The first crash seems to be related to radeon_hotplug_work_func during radeon initialization. Bisecting is possible but slow because of lack of remote power switch. .config is also below. Linux version 4.2.0-rc7-00015-gbf67402 (mroos at d850) (gcc version 4.9.2 (Debian 4.9.2-21) ) #111 Tue Aug 18 16:45:54 EEST 2015 x86/fpu: Legacy x87 FPU detected. x86/fpu: Using 'lazy' FPU context switches. e820: BIOS-provided physical RAM map: BIOS-e820: [mem 0x-0x0009bbff] usable BIOS-e820: [mem 0x0009bc00-0x0009bfff] reserved BIOS-e820: [mem 0x000e-0x000f] reserved BIOS-e820: [mem 0x0010-0x5ffb] usable BIOS-e820: [mem 0x5ffc-0x5fff7fff] ACPI data BIOS-e820: [mem 0x5fff8000-0x5fff] ACPI NVS BIOS-e820: [mem 0xfec0-0xfec00fff] reserved BIOS-e820: [mem 0xfee0-0xfee00fff] reserved BIOS-e820: [mem 0xffb8-0xffbf] reserved BIOS-e820: [mem 0xfff0-0x] reserved Notice: NX (Execute Disable) protection missing in CPU! Legacy DMI 2.3 present. e820: last_pfn = 0x5ffc0 max_arch_pfn = 0x10 x86/PAT: Configuration [0-7]: WB WC UC- UC WB WC UC- UC Warning only 895MB will be used. Use a HIGHMEM enabled kernel. found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [c00ff780] init_memory_mapping: [mem 0x-0x000f] init_memory_mapping: [mem 0x3780-0x37bf] init_memory_mapping: [mem 0x0010-0x377f] init_memory_mapping: [mem 0x37c0-0x37fa0fff] ACPI: Early table checksum verification disabled ACPI: RSDP 0x000FF980 14 (v00 AMI ) ACPI: RSDT 0x5FFF 2C (v01 D850MV MV85010A 20030408 MSFT 1011) ACPI: FACP 0x5FFF1000 74 (v01 D850MV MV85010A 20030408 MSFT 1011) ACPI: DSDT 0x5FFE 003954 (v01 D850MV MV85010A 0010 MSFT 010B) ACPI: FACS 0x5FFF8000 40 ACPI: APIC 0x5FFE3954 68 (v01 D850MV MV85010A 20030408 MSFT 1011) 895MB LOWMEM available. mapped low ram: 0 - 37fa1000 low ram: 0 - 37fa1000 Zone ranges: DMA [mem 0x1000-0x00ff] Normal [mem 0x0100-0x37fa0fff] Movable zone start for each node Early memory node ranges node 0: [mem 0x1000-0x0009afff] node 0: [mem 0x0010-0x5ffb] Initmem setup node 0 [mem 0x1000-0x5ffb] Using APIC driver default ACPI: PM-Timer IO Port: 0x408 ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1]) IOAPIC[0]: apic_id 2, version 32, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) Using ACPI (MADT) for SMP configuration information PM: Registered nosave memory: [mem 0x-0x0fff] PM: Registered nosave memory: [mem 0x0009b000-0x0009bfff] PM: Registered nosave memory: [mem 0x0009c000-0x000d] PM: Registered nosave memory: [mem 0x000e-0x000f] e820: [mem 0x6000-0xfebf] available for PCI devices clocksource: refined-jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 7645519600211568 ns Built 1 zonelists in Zone order, mobility grouping on. Total pages: 227387 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-rc7-00015-gbf67402 root=/dev/sda1 ro netconsole=1980 at 192.168.78.23/eth0,1975 at 192.168.78.14/00:03:47:a4:64:d5 PID hash table entries: 4096 (order: 2, 16384 bytes) Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Initializing CPU#0 Memory: 899028K/916716K available (2438K kernel code, 302K rwdata, 1080K rodata, 320K init, 288K bss, 17688K reserved, 0K cma-reserved) virtual kernel memory layout: fixmap : 0xfffa3000 - 0xf000 ( 368 kB) vmalloc : 0xf87a1000 - 0xfffa1000 ( 120 MB) lowmem : 0xc000 - 0xf7fa1000 ( 895 MB) .init : 0xc13be000 - 0xc140e000 ( 320 kB) .data : 0xc1261bce - 0xc13bca00 (1387 kB) .text : 0xc100 - 0xc1261bce (2438 kB) Checking if this processor honours the WP bit even in supervisor mode...Ok. SLUB: HWalign=128, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 NR_IRQS:2304 nr_irqs:256 16 Console: colour VGA+ 80x25 console [tty0] enabled tsc: Fast TSC calibration failed tsc: PIT calibration matches PMTIMER. 1 loops tsc: Detected 1993.982 MHz processor Calibrating delay loop (skipped), value calculated using timer frequency.. 3987.96 BogoMIPS (lpj=7975928) pid_max: default: 32768 minimum: 301 ACPI: Core revision 20150619 ACPI: All ACPI Tables successfully acquired Mount-cache hash
PCI Radeon RV100 detection hang on sparc64
> >>>> The instrumented dmesg had a couple of my local test changes and was > >>>> bad now that I had ROM. Reverted them exept my readb changes (instead > >>>> of direct dereferences of iomapped space) and redid > >>>> logging to be more precise. > >>>> > >>>>> [drm] radeon kernel modesetting enabled. > >>>>> PCI: Enabling device: (:02:02.0), cmd 82 > >>>>> [drm] initializing kernel modesetting (RV100 0x1002:0x5159 > >>>>> 0x1002:0x0908). > >>>>> [drm] register mmio base: 0x1000 > >>>>> [drm] register mmio size: 32768 > >>>>> [drm:radeon_device_init] *ERROR* Unable to find PCI I/O BAR > >>>> > >>>> > >>>> This was still the unchanged kernel hanging. > >>>> > >>>> Below is a new debug log to pinpoint the hang. It seems to hang in > >>>> r100_gfx_get_rptr but not on first try. > >>> > >>> > >>> It's most likely hanging in readl() in r100_mm_rreg() then. > >> > >> Yes, it is doing direct readl() there. But what does this hang mean? > > > > I'm not sure if the read can hang because of the GPU, or if indicates a more > > fundamental PCI issue. Dave? [...] > Just a short question regarding the test setup. > Is the video card a Sun XVR-100 or is it a vanilla ATI RV100 ? > (If it is a vanilla RV100 there might be some kind of initialization issue > as the video ROM is not executed during boot?) It,s SUNW,XVR-100 with F-code ROM. -- Meelis Roos (mroos at linux.ee)
PCI Radeon RV100 detection hang on sparc64
> > > r100 init hangs in a different place. Original dmesg first, then my > > > instrumented dmesg (seems to get further): > > > > The instrumented dmesg had a couple of my local test changes and was > > bad now that I had ROM. Reverted them exept my readb changes (instead > > of direct dereferences of iomapped space) and redid > > logging to be more precise. > > > > > [drm] radeon kernel modesetting enabled. > > > PCI: Enabling device: (:02:02.0), cmd 82 > > > [drm] initializing kernel modesetting (RV100 0x1002:0x5159 0x1002:0x0908). > > > [drm] register mmio base: 0x1000 > > > [drm] register mmio size: 32768 > > > [drm:radeon_device_init] *ERROR* Unable to find PCI I/O BAR > > > > This was still the unchanged kernel hanging. > > > > Below is a new debug log to pinpoint the hang. It seems to hang in > > r100_gfx_get_rptr but not on first try. > > It's most likely hanging in readl() in r100_mm_rreg() then. Yes, it is doing direct readl() there. But what does this hang mean? By the way, I get these warnings from r100. Seem to be unrelated but still worth reporting IMHO: CC [M] drivers/gpu/drm/radeon/r100.o drivers/gpu/drm/radeon/r100.c: In function ?r100_bandwidth_update?: include/drm/drm_fixed.h:64:13: warning: ?crit_point_ff.full? may be used uninitialized in this function [-Wuninitialized] drivers/gpu/drm/radeon/r100.c:3149:63: note: ?crit_point_ff.full? was declared here drivers/gpu/drm/radeon/r100.c:3573:42: warning: ?disp_drain_rate.full? may be used uninitialized in this function [-Wuninitialized] -- Meelis Roos (mroos at linux.ee)
PCI Radeon RV100 detection hang on sparc64
unlocking [drm] r100_ring_test start [drm] r100_ring_test: after radeon_scratch_get, r=d [drm] r100_ring_test before radeon_ring_lock [drm] radeon_ring_lock start [drm] radeon_ring_lock got mutex [drm] radeon_ring_alloc start [drm] radeon_ring_alloc before radeon_ring_free_size [drm] radeon_ring_free_size before radeon_ring_get_rptr [drm] r100_gfx_get_rptr start [drm] r100_gfx_get_rptr case 2 -- Meelis Roos (mroos at linux.ee)
PCI Radeon RV100 detection hang on sparc64
ce-tree clock info radeon :02:02.0: VRAM: 64M 0x01FF0800 - 0x01FF0BFF (64M used) radeon :02:02.0: GTT: 512M 0x01FF0C00 - 0x01FF2BFF [drm] Detected VRAM RAM=64M, BAR=64M [drm] RAM width 64bits DDR [TTM] Zone kernel: Available graphics memory: 512796 kiB [TTM] Initializing pool allocator [drm] radeon: 64M of VRAM memory ready [drm] radeon: 512M of GTT memory ready. [drm] GART: num cpu pages 65536, num gpu pages 131072 [drm] PCI GART of 512M enabled (table at 0xC1236000). radeon :02:02.0: WB disabled radeon :02:02.0: fence driver on ring 0 use gpu addr 0x01ff0c00 and cpu addr 0xff003c90c000 [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [drm] Driver supports precise vblank timestamp query. [drm] radeon: irq initialized. [drm] Loading R100 Microcode [drm] radeon: ring at 0x01FF0C002000 [drm] r100_ring_test: 1 [drm] r100_ring_test: 2, r=15e4d [drm] r100_ring_test: 3 -- Meelis Roos (mroos at linux.ee)
[PATCH] only try to find radeon IGP ROM on X86
To prevent hangs on non-PC machines (e.g. sparc64), probe Radeon ROM from ATI IGP only on X86. Fixes hang in this place and allows PCI radeon detection to move on to next problem. Signed-off-by: Meelis Roos mr...@linux.ee diff --git a/drivers/gpu/drm/radeon/radeon_bios.c b/drivers/gpu/drm/radeon/radeon_bios.c index 061b227..48ef97c 100644 --- a/drivers/gpu/drm/radeon/radeon_bios.c +++ b/drivers/gpu/drm/radeon/radeon_bios.c @@ -49,6 +49,11 @@ static bool igp_read_bios_from_vram(struct radeon_device *rdev) resource_size_t vram_base; resource_size_t size = 256 * 1024; /* ??? */ +#ifndef CONFIG_X86 + /* IGP only exists on X86 (32- and 64-bit) */ + return false; +#endif + if (!(rdev-flags RADEON_IS_IGP)) if (!radeon_card_posted(rdev)) return false; -- Meelis Roos (mr...@linux.ee) ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH] only try to find radeon IGP ROM on X86
On Thu, Oct 10, 2013 at 7:51 AM, Meelis Roos mr...@linux.ee wrote: To prevent hangs on non-PC machines (e.g. sparc64), probe Radeon ROM from ATI IGP only on X86. Fixes hang in this place and allows PCI radeon detection to move on to next problem. NACK. All this function does it attempt to read the rom from the framebuffer PCI BAR. If you get hangs reading the BAR, then you have larger problems on your platform. Also, there are non-x86 platforms that IGP chips which this may break. OK. But the code seems to just dereference addresses returned from ioremap, but to the best of my knowledge, these are not universally (like on each arch) safe to read without readb/readw/readl. Should I convert these to readb for test? Signed-off-by: Meelis Roos mr...@linux.ee diff --git a/drivers/gpu/drm/radeon/radeon_bios.c b/drivers/gpu/drm/radeon/radeon_bios.c index 061b227..48ef97c 100644 --- a/drivers/gpu/drm/radeon/radeon_bios.c +++ b/drivers/gpu/drm/radeon/radeon_bios.c @@ -49,6 +49,11 @@ static bool igp_read_bios_from_vram(struct radeon_device *rdev) resource_size_t vram_base; resource_size_t size = 256 * 1024; /* ??? */ +#ifndef CONFIG_X86 + /* IGP only exists on X86 (32- and 64-bit) */ + return false; +#endif + if (!(rdev-flags RADEON_IS_IGP)) if (!radeon_card_posted(rdev)) return false; -- Meelis Roos (mr...@linux.ee) -- Meelis Roos (mr...@linux.ee) ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: PCI Radeon RV100 detection hang on sparc64
The pci_assign_resource() path must have some bug that causes the resource values to be set incorrectly or similar. Meelis, what is the value of pci_resource_start(pdev, PCI_ROM_RESOURCE) before the pci_map_rom() call? [drm] radeon_read_bios: pci_resource_start(ROM)=01FF1002 I am a little confused here. ROM addressis OK but after pci_map_rom it results in address that corresponds to another device? That's certainly a bug. So after pci_map_rom() pci_resource_start(ROM)=01FF, right? I double checked it - yes: before pci_map_rom: [drm] radeon_read_bios: pci_resource_start(ROM)=01FF1002 radeon :02:02.0: BAR 6: assigned [mem 0x1ff-0x1ff0001] after pci_map_rom: [drm] radeon_read_bios, bios=01ff, pci_resource_start(ROM)=01FF, size=46592 This is first range in pci bus :02 that is tried, and it matches: pci_bus :02: pci_bus_alloc_resource trying [mem 0x1ff-0x1ff00bf] I instrumented bootup with pci_bus_add_resource_offset and pci_bus_add_resource logs if this of any help: /pci@1f,0: PCI IO[1fe0200] MEM[1ff] /pci@1f,0: SABRE PCI Bus Module ver[0:0] PCI: Scanning PBM /pci@1f,0 pci_bus_add_resource_offset adding [io 0x1fe0200-0x1fe02ff] pci_bus_add_resource_offset adding [mem 0x1ff-0x1ff] pci_bus_add_resource_offset adding [bus 00-02] sabre f005f9c0: PCI host bridge to bus :00 pci_bus :00: pci_bus_add_resource adding [io 0x1fe0200-0x1fe02ff] with flags 0 pci_bus :00: root bus resource [io 0x1fe0200-0x1fe02ff] (bus address [0x-0xff]) pci_bus :00: pci_bus_add_resource adding [mem 0x1ff-0x1ff] with flags 0 pci_bus :00: root bus resource [mem 0x1ff-0x1ff] (bus address [0x-0x]) pci_bus :00: root bus resource [bus 00-02] To me it looks like we get the PCI bus ranges and store them and nobody uses them until now, and then we insert PCI devices with allocations from OF and do not update PCI bus available windows? -- Meelis Roos (mr...@linux.ee) ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: PCI Radeon RV100 detection hang on sparc64
That looks quite strange. I guess the kernel should map the ROM at the address OpenBoot/OF assigned to it. ( 1002 ). The address you see is a raw physical I/O address, which is a concatenation of the I/O window physical address for that PCI controller and the PCI bus assigned address. This is what we store in the resource values. The pci_assign_resource() path must have some bug that causes the resource values to be set incorrectly or similar. Meelis, what is the value of pci_resource_start(pdev, PCI_ROM_RESOURCE) before the pci_map_rom() call? [drm] radeon_read_bios: pci_resource_start(ROM)=01FF1002 I am a little confused here. ROM addressis OK but after pci_map_rom it results in address that corresponds to another device? That's certainly a bug. So after pci_map_rom() pci_resource_start(ROM)=01FF, right? I double checked it - yes: before pci_map_rom: [drm] radeon_read_bios: pci_resource_start(ROM)=01FF1002 radeon :02:02.0: BAR 6: assigned [mem 0x1ff-0x1ff0001] after pci_map_rom: [drm] radeon_read_bios, bios=01ff, pci_resource_start(ROM)=01FF, size=46592 [drm] radeon_read_bios: found ROM signature at 01ff [drm] radeon_read_bios: bios=01ff, size=46592 -- Meelis Roos (mr...@linux.ee) ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: PCI Radeon RV100 detection hang on sparc64
: Fujitsu Limited. Device 11a2 (rev 02) Subsystem: Fujitsu Limited. Device 11a2 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Interrupt: pin A routed to IRQ 18 Region 0: Memory at 1204 (64-bit, non-prefetchable) [disabled] [size=64K] Region 2: [virtual] Memory at fe01 (32-bit, non-prefetchable) [size=1] Region 3: [virtual] Memory at fe01 (32-bit, non-prefetchable) [size=1] Region 4: [virtual] Memory at fe01 (32-bit, non-prefetchable) [size=1] Region 5: [virtual] Memory at fe01 (32-bit, non-prefetchable) [size=1] Expansion ROM at fe01 [disabled] [size=1] Capabilities: [40] PCI-X non-bridge device Command: DPERE- ERO+ RBC=512 OST=1 Status: Dev=ff:1f.1 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=2048 DMOST=1 DMCRS=16 RSCEM- 266MHz- 533MHz- Capabilities: [48] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME- Capabilities: [50] Vital Product Data Unknown small resource type 00, will not decode more. Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+ Address: 082024c310601050 Data: 1080 -- Meelis Roos (mr...@linux.ee) ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
i915 pipe A assertion failure (expected on, current off)
> >> Tried 3.11-rc7 on Thinkpad X30 (first 3-11-rc tried on this hw). Works > >> but i915 gives strange assertion failure with WARNING stack trace. This > >> is new since 3.10. > > > > It is still there with 3.12-rc1 but now I git around to bisecting it. > > This is the commit that introduces the warning. > > > > commit 9f11a9e4e50006b615ba94722dfc33ced89664cf > > Author: Daniel Vetter > > Date: Thu Jun 13 00:54:58 2013 +0200 > > > > drm/i915: set up PIPECONF explicitly for i9xx/vlv platforms > > My apologies for not responding to your first report, fell through the > cracks somehow. Can you please boot with drm.debug=0xe, reproduce the > WARN and grab the full dmesg (please make sure everything from boot-up > is in there). That's usually enough to figure out what's going wrong > here. [0.00] Linux version 3.12.0-rc1-00273-g2457aaf (mroos at x30) (gcc version 4.8.1 (Debian 4.8.1-10) ) #31 Sat Sep 21 20:40:43 EEST 2013 [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009efff] usable [0.00] BIOS-e820: [mem 0x0009f000-0x0009] reserved [0.00] BIOS-e820: [mem 0x000dc000-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x1f76] usable [0.00] BIOS-e820: [mem 0x1f77-0x1f77dfff] ACPI data [0.00] BIOS-e820: [mem 0x1f77e000-0x1f77] ACPI NVS [0.00] BIOS-e820: [mem 0x1f78-0x1fff] reserved [0.00] BIOS-e820: [mem 0xff80-0x] reserved [0.00] Notice: NX (Execute Disable) protection missing in CPU! [0.00] SMBIOS 2.3 present. [0.00] DMI: IBM 26724XG/26724XG, BIOS 1KET48WW (1.09 ) 06/16/2006 [0.00] e820: update [mem 0x-0x0fff] usable ==> reserved [0.00] e820: remove [mem 0x000a-0x000f] usable [0.00] e820: last_pfn = 0x1f770 max_arch_pfn = 0x10 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-B uncachable [0.00] C-C write-protect [0.00] D-DBFFF uncachable [0.00] DC000-D write-back [0.00] E-F write-protect [0.00] MTRR variable ranges enabled: [0.00] 0 base 0 mask FE000 write-back [0.00] 1 base 01FF8 mask 8 uncachable [0.00] 2 disabled [0.00] 3 disabled [0.00] 4 disabled [0.00] 5 disabled [0.00] 6 disabled [0.00] 7 disabled [0.00] PAT not supported by CPU. [0.00] original variable MTRRs [0.00] reg 0, base: 0GB, range: 512MB, type WB [0.00] reg 1, base: 523776KB, range: 512KB, type UC [0.00] total RAM covered: 511M [0.00] Found optimal setting for mtrr clean up [0.00] gran_size: 64K chunk_size: 1M num_reg: 2 lose cover RAM: 0G [0.00] New variable MTRRs [0.00] reg 0, base: 0GB, range: 512MB, type WB [0.00] reg 1, base: 523776KB, range: 512KB, type UC [0.00] initial memory mapped: [mem 0x-0x017f] [0.00] Base memory trampoline at [c009b000] 9b000 size 16384 [0.00] init_memory_mapping: [mem 0x-0x000f] [0.00] [mem 0x-0x000f] page 4k [0.00] init_memory_mapping: [mem 0x1f00-0x1f3f] [0.00] [mem 0x1f00-0x1f3f] page 2M [0.00] init_memory_mapping: [mem 0x1800-0x1eff] [0.00] [mem 0x1800-0x1eff] page 2M [0.00] init_memory_mapping: [mem 0x0010-0x17ff] [0.00] [mem 0x0010-0x003f] page 4k [0.00] [mem 0x0040-0x17ff] page 2M [0.00] init_memory_mapping: [mem 0x1f40-0x1f76] [0.00] [mem 0x1f40-0x1f76] page 4k [0.00] BRK [0x014ed000, 0x014edfff] PGTABLE [0.00] ACPI: RSDP 000f7090 00024 (v02 IBM ) [0.00] ACPI: XSDT 1f772a76 0004C (v01 IBMTP-1K1090 LTP ) [0.00] ACPI: FACP 1f772b00 00081 (v01 IBMTP-1K1090 IBM 0001) [0.00] ACPI: DSDT 1f772be7 0B22C (v01 IBMTP-1K1090 MSFT 010D) [0.00] ACPI: FACS 1f77f000 00040 [0.00] ACPI: SSDT 1f772bb4 00033 (v01 IBMTP-1K1090 MSFT 010D) [0.00] ACPI: ECDT 1f77de13 00052 (v01 IBMTP-1K1090 IBM 0001) [0.00] ACPI: TCPA 1f77de65 00032 (v01 IBMTP-1K1090 PTL 0001) [0.00] ACPI: BOOT 1f77dfd8 00028 (v01 IBMTP-1K1090 LTP 0001) [0.00] 503MB LOWMEM available. [0.00] mapped low ram: 0 - 1f77 [0.00] low ram: 0 - 1f77 [0.00] Zone ranges: [0.00] DMA [mem 0x1000-0x00ff] [0.00] Normal [mem 0x0100-0x1f76] [
i915 pipe A assertion failure (expected on, current off)
> Tried 3.11-rc7 on Thinkpad X30 (first 3-11-rc tried on this hw). Works > but i915 gives strange assertion failure with WARNING stack trace. This > is new since 3.10. It is still there with 3.12-rc1 but now I git around to bisecting it. This is the commit that introduces the warning. commit 9f11a9e4e50006b615ba94722dfc33ced89664cf Author: Daniel Vetter Date: Thu Jun 13 00:54:58 2013 +0200 drm/i915: set up PIPECONF explicitly for i9xx/vlv platforms Same reasons as for the previous patch, just no bug report about anything going wrong yet: We only support exactly the mode we program, so don't leave any stale BIOS state behind. Again this will be fun to properly track for fastboot. Reviewed-by: Chris Wilson Reviewed-by: Ville Syrj?l? Signed-off-by: Daniel Vetter > > The only monitor is internal LCD. lspci -vvvnn is also below. > > [0.00] Linux version 3.11.0-rc7 (mroos at x30) (gcc version 4.8.1 > (Debian 4.8.1-5) ) #4 Mon Aug 26 11:42:19 EEST 2013 > [0.00] e820: BIOS-provided physical RAM map: > [0.00] BIOS-e820: [mem 0x-0x0009efff] usable > [0.00] BIOS-e820: [mem 0x0009f000-0x0009] reserved > [0.00] BIOS-e820: [mem 0x000dc000-0x000f] reserved > [0.00] BIOS-e820: [mem 0x0010-0x1f76] usable > [0.00] BIOS-e820: [mem 0x1f77-0x1f77dfff] ACPI > data > [0.00] BIOS-e820: [mem 0x1f77e000-0x1f77] ACPI NVS > [0.00] BIOS-e820: [mem 0x1f78-0x1fff] reserved > [0.00] BIOS-e820: [mem 0xff80-0x] reserved > [0.00] Notice: NX (Execute Disable) protection missing in CPU! > [0.00] SMBIOS 2.3 present. > [0.00] DMI: IBM 26724XG/26724XG, BIOS 1KET48WW (1.09 ) 06/16/2006 > [0.00] e820: update [mem 0x-0x0fff] usable ==> reserved > [0.00] e820: remove [mem 0x000a-0x000f] usable > [0.00] e820: last_pfn = 0x1f770 max_arch_pfn = 0x10 > [0.00] MTRR default type: uncachable > [0.00] MTRR fixed ranges enabled: > [0.00] 0-9 write-back > [0.00] A-B uncachable > [0.00] C-C write-protect > [0.00] D-DBFFF uncachable > [0.00] DC000-D write-back > [0.00] E-F write-protect > [0.00] MTRR variable ranges enabled: > [0.00] 0 base 0 mask FE000 write-back > [0.00] 1 base 01FF8 mask 8 uncachable > [0.00] 2 disabled > [0.00] 3 disabled > [0.00] 4 disabled > [0.00] 5 disabled > [0.00] 6 disabled > [0.00] 7 disabled > [0.00] PAT not supported by CPU. > [0.00] original variable MTRRs > [0.00] reg 0, base: 0GB, range: 512MB, type WB > [0.00] reg 1, base: 523776KB, range: 512KB, type UC > [0.00] total RAM covered: 511M > [0.00] Found optimal setting for mtrr clean up > [0.00] gran_size: 64Kchunk_size: 1M num_reg: 2 lose > cover RAM: 0G > [0.00] New variable MTRRs > [0.00] reg 0, base: 0GB, range: 512MB, type WB > [0.00] reg 1, base: 523776KB, range: 512KB, type UC > [0.00] initial memory mapped: [mem 0x-0x017f] > [0.00] Base memory trampoline at [c009b000] 9b000 size 16384 > [0.00] init_memory_mapping: [mem 0x-0x000f] > [0.00] [mem 0x-0x000f] page 4k > [0.00] init_memory_mapping: [mem 0x1f00-0x1f3f] > [0.00] [mem 0x1f00-0x1f3f] page 2M > [0.00] init_memory_mapping: [mem 0x1800-0x1eff] > [0.00] [mem 0x1800-0x1eff] page 2M > [0.00] init_memory_mapping: [mem 0x0010-0x17ff] > [0.00] [mem 0x0010-0x003f] page 4k > [0.00] [mem 0x0040-0x17ff] page 2M > [0.00] init_memory_mapping: [mem 0x1f40-0x1f76] > [0.00] [mem 0x1f40-0x1f76] page 4k > [0.00] BRK [0x014da000, 0x014dafff] PGTABLE > [0.00] ACPI: RSDP 000f7090 00024 (v02 IBM ) > [0.00] ACPI: XSDT 1f772a76 0004C (v01 IBMTP-1K1090 LTP > ) > [0.00] ACPI: FACP 1f772b00 00081 (v01 IBMTP-1K1090 IBM > 0001) > [0.00] ACPI: DSDT 1f772be7 0B22C (v01 IBMTP-1K1090 MSFT > 010D) > [0.00] ACPI: FACS 1f77f000 00040 > [0.00] ACPI: SSDT 1f772bb4 00033 (v01 IBMTP-1K1090 MSFT > 010D) > [0.00] ACPI: ECDT 1f77de13 00052 (v01 IBMTP-1K1090 IBM > 0001) > [0.00] ACPI: TCPA 1f77de65 00032 (v01 IBMTP-1K1090 PTL > 0001) > [0.00] ACPI: BOOT 1f77dfd8 00028 (v01 IBMTP-1K1090 LTP > 0001) > [0.00] 503MB LOWMEM available. > [
[PATCH] radeon kms: fix uninitialised hotplug work usage in r100_irq_process()
> Reported-by: Meelis Roos
> Signed-off-by: Sergey Senozhatsky
It works, thank you for quick response!
Tested-by: Meelis Roos
> drivers/gpu/drm/radeon/radeon_irq_kms.c | 10 ++
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/radeon/radeon_irq_kms.c
> b/drivers/gpu/drm/radeon/radeon_irq_kms.c
> index 081886b..cc9e848 100644
> --- a/drivers/gpu/drm/radeon/radeon_irq_kms.c
> +++ b/drivers/gpu/drm/radeon/radeon_irq_kms.c
> @@ -275,17 +275,19 @@ int radeon_irq_kms_init(struct radeon_device *rdev)
> dev_info(rdev->dev, "radeon: using MSI.\n");
> }
> }
> +
> + INIT_WORK(>hotplug_work, radeon_hotplug_work_func);
> + INIT_WORK(>audio_work, r600_audio_update_hdmi);
> + INIT_WORK(>reset_work, radeon_irq_reset_work_func);
> +
> rdev->irq.installed = true;
> r = drm_irq_install(rdev->ddev);
> if (r) {
> rdev->irq.installed = false;
> + flush_work(>hotplug_work);
> return r;
> }
>
> - INIT_WORK(>hotplug_work, radeon_hotplug_work_func);
> - INIT_WORK(>audio_work, r600_audio_update_hdmi);
> - INIT_WORK(>reset_work, radeon_irq_reset_work_func);
> -
> DRM_INFO("radeon: irq initialized.\n");
> return 0;
> }
>
--
Meelis Roos (mroos at linux.ee)
3.11-rc3: radeon WARNING at kernel/workqueue.c:1378 __queue_work+0x132/0x16d()
> > Just got this WARNING while loading radeon driver on a test PC that was > > running 3.10 fine (full dmesg below). The machine is a Intel 850 chipst > > PC with AGP Radeon 7000 and no monitor attached. lspci and config are > > also below. > > Still there with 3.11-rc6 and fully reproducible. Finally found time to bisect it. CC-ing Greg since it was CC: stable. This is the commit that introduces the WARNING: a01c34f72e7cd2624570818f579b5ab464f93de2 is the first bad commit commit a01c34f72e7cd2624570818f579b5ab464f93de2 Author: Sergey Senozhatsky Date: Sun Jul 14 14:03:27 2013 +0300 radeon kms: do not flush uninitialized hotplug work Fix a warning from lockdep caused by calling flush_work() for uninitialized hotplug work. Initialize hotplug_work, audio_work and reset_work upon successful radeon_irq_kms_init() completion and thus perform hotplug flush_work only when rdev->irq.installed is true. > > > Linux version 3.11.0-rc3 (mroos at d850) (gcc version 4.8.1 (Debian > > 4.8.1-3) ) #48 Mon Jul 29 12:54:00 EEST 2013 > > e820: BIOS-provided physical RAM map: > > BIOS-e820: [mem 0x-0x0009bbff] usable > > BIOS-e820: [mem 0x0009bc00-0x0009bfff] reserved > > BIOS-e820: [mem 0x000e-0x000f] reserved > > BIOS-e820: [mem 0x0010-0x3ffb] usable > > BIOS-e820: [mem 0x3ffc-0x3fff7fff] ACPI data > > BIOS-e820: [mem 0x3fff8000-0x3fff] ACPI NVS > > BIOS-e820: [mem 0xfec0-0xfec00fff] reserved > > BIOS-e820: [mem 0xfee0-0xfee00fff] reserved > > BIOS-e820: [mem 0xffb8-0xffbf] reserved > > BIOS-e820: [mem 0xfff0-0x] reserved > > Notice: NX (Execute Disable) protection missing in CPU! > > Legacy DMI 2.3 present. > > DMI: MicroLink /D850MV > > , BIOS MV85010A.86A.0067.P24.0304081124 04/08/2003 > > e820: update [mem 0x-0x0fff] usable ==> reserved > > e820: remove [mem 0x000a-0x000f] usable > > e820: last_pfn = 0x3ffc0 max_arch_pfn = 0x10 > > MTRR default type: uncachable > > MTRR fixed ranges enabled: > > 0-9 write-back > > A-B uncachable > > C-C write-protect > > D-D uncachable > > E-F write-protect > > MTRR variable ranges enabled: > > 0 base 0 mask FC000 write-back > > 1 disabled > > 2 disabled > > 3 disabled > > 4 disabled > > 5 disabled > > 6 disabled > > 7 disabled > > x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 > > Warning only 895MB will be used. > > Use a HIGHMEM enabled kernel. > > found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [c00ff780] > > initial memory mapped: [mem 0x-0x017f] > > Base memory trampoline at [c0097000] 97000 size 16384 > > init_memory_mapping: [mem 0x-0x000f] > > [mem 0x-0x000f] page 4k > > init_memory_mapping: [mem 0x3780-0x37bf] > > [mem 0x3780-0x37bf] page 2M > > init_memory_mapping: [mem 0x3000-0x377f] > > [mem 0x3000-0x377f] page 2M > > init_memory_mapping: [mem 0x0010-0x2fff] > > [mem 0x0010-0x003f] page 4k > > [mem 0x0040-0x2fff] page 2M > > init_memory_mapping: [mem 0x37c0-0x37f9] > > [mem 0x37c0-0x37f9] page 4k > > BRK [0x013f2000, 0x013f2fff] PGTABLE > > ACPI: RSDP 000ff980 00014 (v00 AMI ) > > ACPI: RSDT 3fff 0002C (v01 D850MV MV85010A 20030408 MSFT 1011) > > ACPI: FACP 3fff1000 00074 (v01 D850MV MV85010A 20030408 MSFT 1011) > > ACPI: DSDT 3ffe 03954 (v01 D850MV MV85010A 0010 MSFT 010B) > > ACPI: FACS 3fff8000 00040 > > ACPI: APIC 3ffe3954 00068 (v01 D850MV MV85010A 20030408 MSFT 1011) > > ACPI: Local APIC address 0xfee0 > > 895MB LOWMEM available. > > mapped low ram: 0 - 37fa > > low ram: 0 - 37fa > > Zone ranges: > > DMA [mem 0x1000-0x00ff] > > Normal [mem 0x0100-0x37f9] > > Movable zone start for each node > > Early memory node ranges > > node 0: [mem 0x1000-0x0009afff] > > node 0: [mem 0x0010-0x3ffb] > > On node 0 totalpages: 229178 > > DMA zone: 32 pages used for memmap > > DMA zone: 0 pages reserved > > DMA zone: 3994 pages, LIFO batch:0 > > Normal zone: 1760 pages used for memmap > > Normal zone: 225184 pages, LIFO batch:31 > > Using APIC driver default > > ACPI: PM-Timer IO Port: 0x408 > > ACPI: Local APIC address 0xfee0 > > ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) > > ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] disabled) > > ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1]) > > ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1]) > > ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) > > IOAPIC[0]: apic_id 2, version 32, address 0xfec0, GSI 0-23 > > ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high
Re: [PATCH] radeon kms: fix uninitialised hotplug work usage in r100_irq_process()
Reported-by: Meelis Roos mr...@linux.ee
Signed-off-by: Sergey Senozhatsky sergey.senozhat...@gmail.com
It works, thank you for quick response!
Tested-by: Meelis Roos mr...@linux.ee
drivers/gpu/drm/radeon/radeon_irq_kms.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/radeon/radeon_irq_kms.c
b/drivers/gpu/drm/radeon/radeon_irq_kms.c
index 081886b..cc9e848 100644
--- a/drivers/gpu/drm/radeon/radeon_irq_kms.c
+++ b/drivers/gpu/drm/radeon/radeon_irq_kms.c
@@ -275,17 +275,19 @@ int radeon_irq_kms_init(struct radeon_device *rdev)
dev_info(rdev-dev, radeon: using MSI.\n);
}
}
+
+ INIT_WORK(rdev-hotplug_work, radeon_hotplug_work_func);
+ INIT_WORK(rdev-audio_work, r600_audio_update_hdmi);
+ INIT_WORK(rdev-reset_work, radeon_irq_reset_work_func);
+
rdev-irq.installed = true;
r = drm_irq_install(rdev-ddev);
if (r) {
rdev-irq.installed = false;
+ flush_work(rdev-hotplug_work);
return r;
}
- INIT_WORK(rdev-hotplug_work, radeon_hotplug_work_func);
- INIT_WORK(rdev-audio_work, r600_audio_update_hdmi);
- INIT_WORK(rdev-reset_work, radeon_irq_reset_work_func);
-
DRM_INFO(radeon: irq initialized.\n);
return 0;
}
--
Meelis Roos (mr...@linux.ee)
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
i915 pipe A assertion failure (expected on, current off)
s: Kernel driver in use: agpgart-intel 00:02.0 VGA compatible controller [0300]: Intel Corporation 82830M/MG Integrated Graphics Controller [8086:3577] (rev 04) (prog-if 00 [VGA controller]) Subsystem: IBM ThinkPad A/T/X Series [1014:0513] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: Kernel driver in use: i915 00:02.1 Display controller [0380]: Intel Corporation 82830M/MG Integrated Graphics Controller [8086:3577] Subsystem: IBM ThinkPad A/T/X Series [1014:0513] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:1d.0 USB controller [0c03]: Intel Corporation 82801CA/CAM USB Controller #1 [8086:2482] (rev 02) (prog-if 00 [UHCI]) Subsystem: IBM ThinkPad A/T/X Series [1014:0220] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 00:1f.0 ISA bridge [0601]: Intel Corporation 82801CAM ISA Bridge (LPC) [8086:248c] (rev 02) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Reset- 16bInt+ PostWrite+ 16-bit legacy interface ports at 0001 Kernel driver in use: yenta_cardbus 01:00.1 CardBus bridge [0607]: Ricoh Co Ltd RL5c476 II [1180:0476] (rev a8) Subsystem: IBM ThinkPad A/T/X Series [1014:0185] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Reset- 16bInt+ PostWrite+ 16-bit legacy interface ports at 0001 Kernel driver in use: yenta_cardbus 01:00.2 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C552 IEEE 1394 Controller [1180:0552] (prog-if 10 [OHCI]) Subsystem: IBM ThinkPad A/T/X Series [1014:0511] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: firewire_ohci 01:02.0 Network controller [0280]: Cisco Aironet Wireless Communications Cisco Aironet Wireless 802.11b [14b9:a504] Subsystem: Cisco Aironet Wireless Communications Device [14b9:5000] Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: airo 01:08.0 Ethernet controller [0200]: Intel Corporation 82801CAM (ICH3) PRO/100 VE (LOM) Ethernet Controller [8086:1031] (rev 42) Subsystem: IBM ThinkPad A/T/X Series [1014:0209] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: e100 -- Meelis Roos (mroos at ut.ee) http://www.cs.ut.ee/~mroos/
i915 pipe A assertion failure (expected on, current off)
Tried 3.11-rc7 on Thinkpad X30 (first 3-11-rc tried on this hw). Works but i915 gives strange assertion failure with WARNING stack trace. This is new since 3.10. The only monitor is internal LCD. lspci -vvvnn is also below. [0.00] Linux version 3.11.0-rc7 (mroos@x30) (gcc version 4.8.1 (Debian 4.8.1-5) ) #4 Mon Aug 26 11:42:19 EEST 2013 [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009efff] usable [0.00] BIOS-e820: [mem 0x0009f000-0x0009] reserved [0.00] BIOS-e820: [mem 0x000dc000-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x1f76] usable [0.00] BIOS-e820: [mem 0x1f77-0x1f77dfff] ACPI data [0.00] BIOS-e820: [mem 0x1f77e000-0x1f77] ACPI NVS [0.00] BIOS-e820: [mem 0x1f78-0x1fff] reserved [0.00] BIOS-e820: [mem 0xff80-0x] reserved [0.00] Notice: NX (Execute Disable) protection missing in CPU! [0.00] SMBIOS 2.3 present. [0.00] DMI: IBM 26724XG/26724XG, BIOS 1KET48WW (1.09 ) 06/16/2006 [0.00] e820: update [mem 0x-0x0fff] usable == reserved [0.00] e820: remove [mem 0x000a-0x000f] usable [0.00] e820: last_pfn = 0x1f770 max_arch_pfn = 0x10 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-B uncachable [0.00] C-C write-protect [0.00] D-DBFFF uncachable [0.00] DC000-D write-back [0.00] E-F write-protect [0.00] MTRR variable ranges enabled: [0.00] 0 base 0 mask FE000 write-back [0.00] 1 base 01FF8 mask 8 uncachable [0.00] 2 disabled [0.00] 3 disabled [0.00] 4 disabled [0.00] 5 disabled [0.00] 6 disabled [0.00] 7 disabled [0.00] PAT not supported by CPU. [0.00] original variable MTRRs [0.00] reg 0, base: 0GB, range: 512MB, type WB [0.00] reg 1, base: 523776KB, range: 512KB, type UC [0.00] total RAM covered: 511M [0.00] Found optimal setting for mtrr clean up [0.00] gran_size: 64K chunk_size: 1M num_reg: 2 lose cover RAM: 0G [0.00] New variable MTRRs [0.00] reg 0, base: 0GB, range: 512MB, type WB [0.00] reg 1, base: 523776KB, range: 512KB, type UC [0.00] initial memory mapped: [mem 0x-0x017f] [0.00] Base memory trampoline at [c009b000] 9b000 size 16384 [0.00] init_memory_mapping: [mem 0x-0x000f] [0.00] [mem 0x-0x000f] page 4k [0.00] init_memory_mapping: [mem 0x1f00-0x1f3f] [0.00] [mem 0x1f00-0x1f3f] page 2M [0.00] init_memory_mapping: [mem 0x1800-0x1eff] [0.00] [mem 0x1800-0x1eff] page 2M [0.00] init_memory_mapping: [mem 0x0010-0x17ff] [0.00] [mem 0x0010-0x003f] page 4k [0.00] [mem 0x0040-0x17ff] page 2M [0.00] init_memory_mapping: [mem 0x1f40-0x1f76] [0.00] [mem 0x1f40-0x1f76] page 4k [0.00] BRK [0x014da000, 0x014dafff] PGTABLE [0.00] ACPI: RSDP 000f7090 00024 (v02 IBM ) [0.00] ACPI: XSDT 1f772a76 0004C (v01 IBMTP-1K1090 LTP ) [0.00] ACPI: FACP 1f772b00 00081 (v01 IBMTP-1K1090 IBM 0001) [0.00] ACPI: DSDT 1f772be7 0B22C (v01 IBMTP-1K1090 MSFT 010D) [0.00] ACPI: FACS 1f77f000 00040 [0.00] ACPI: SSDT 1f772bb4 00033 (v01 IBMTP-1K1090 MSFT 010D) [0.00] ACPI: ECDT 1f77de13 00052 (v01 IBMTP-1K1090 IBM 0001) [0.00] ACPI: TCPA 1f77de65 00032 (v01 IBMTP-1K1090 PTL 0001) [0.00] ACPI: BOOT 1f77dfd8 00028 (v01 IBMTP-1K1090 LTP 0001) [0.00] 503MB LOWMEM available. [0.00] mapped low ram: 0 - 1f77 [0.00] low ram: 0 - 1f77 [0.00] Zone ranges: [0.00] DMA [mem 0x1000-0x00ff] [0.00] Normal [mem 0x0100-0x1f76] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x1000-0x0009efff] [0.00] node 0: [mem 0x0010-0x1f76] [0.00] On node 0 totalpages: 128782 [0.00] DMA zone: 32 pages used for memmap [0.00] DMA zone: 0 pages reserved [0.00] DMA zone: 3998 pages, LIFO batch:0 [0.00] Normal zone: 975 pages used for memmap [0.00] Normal zone: 124784 pages, LIFO batch:31 [0.00] Using APIC driver default [0.00] ACPI: PM-Timer IO Port: 0x1008 [0.00] Local
3.11-rc3: radeon WARNING at kernel/workqueue.c:1378 __queue_work+0x132/0x16d()
> Just got this WARNING while loading radeon driver on a test PC that was > running 3.10 fine (full dmesg below). The machine is a Intel 850 chipst > PC with AGP Radeon 7000 and no monitor attached. lspci and config are > also below. Still there with 3.11-rc6 and fully reproducible. > Linux version 3.11.0-rc3 (mroos at d850) (gcc version 4.8.1 (Debian 4.8.1-3) > ) #48 Mon Jul 29 12:54:00 EEST 2013 > e820: BIOS-provided physical RAM map: > BIOS-e820: [mem 0x-0x0009bbff] usable > BIOS-e820: [mem 0x0009bc00-0x0009bfff] reserved > BIOS-e820: [mem 0x000e-0x000f] reserved > BIOS-e820: [mem 0x0010-0x3ffb] usable > BIOS-e820: [mem 0x3ffc-0x3fff7fff] ACPI data > BIOS-e820: [mem 0x3fff8000-0x3fff] ACPI NVS > BIOS-e820: [mem 0xfec0-0xfec00fff] reserved > BIOS-e820: [mem 0xfee0-0xfee00fff] reserved > BIOS-e820: [mem 0xffb8-0xffbf] reserved > BIOS-e820: [mem 0xfff0-0x] reserved > Notice: NX (Execute Disable) protection missing in CPU! > Legacy DMI 2.3 present. > DMI: MicroLink /D850MV > , BIOS MV85010A.86A.0067.P24.0304081124 04/08/2003 > e820: update [mem 0x-0x0fff] usable ==> reserved > e820: remove [mem 0x000a-0x000f] usable > e820: last_pfn = 0x3ffc0 max_arch_pfn = 0x10 > MTRR default type: uncachable > MTRR fixed ranges enabled: > 0-9 write-back > A-B uncachable > C-C write-protect > D-D uncachable > E-F write-protect > MTRR variable ranges enabled: > 0 base 0 mask FC000 write-back > 1 disabled > 2 disabled > 3 disabled > 4 disabled > 5 disabled > 6 disabled > 7 disabled > x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 > Warning only 895MB will be used. > Use a HIGHMEM enabled kernel. > found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [c00ff780] > initial memory mapped: [mem 0x-0x017f] > Base memory trampoline at [c0097000] 97000 size 16384 > init_memory_mapping: [mem 0x-0x000f] > [mem 0x-0x000f] page 4k > init_memory_mapping: [mem 0x3780-0x37bf] > [mem 0x3780-0x37bf] page 2M > init_memory_mapping: [mem 0x3000-0x377f] > [mem 0x3000-0x377f] page 2M > init_memory_mapping: [mem 0x0010-0x2fff] > [mem 0x0010-0x003f] page 4k > [mem 0x0040-0x2fff] page 2M > init_memory_mapping: [mem 0x37c0-0x37f9] > [mem 0x37c0-0x37f9] page 4k > BRK [0x013f2000, 0x013f2fff] PGTABLE > ACPI: RSDP 000ff980 00014 (v00 AMI ) > ACPI: RSDT 3fff 0002C (v01 D850MV MV85010A 20030408 MSFT 1011) > ACPI: FACP 3fff1000 00074 (v01 D850MV MV85010A 20030408 MSFT 1011) > ACPI: DSDT 3ffe 03954 (v01 D850MV MV85010A 0010 MSFT 010B) > ACPI: FACS 3fff8000 00040 > ACPI: APIC 3ffe3954 00068 (v01 D850MV MV85010A 20030408 MSFT 1011) > ACPI: Local APIC address 0xfee0 > 895MB LOWMEM available. > mapped low ram: 0 - 37fa > low ram: 0 - 37fa > Zone ranges: > DMA [mem 0x1000-0x00ff] > Normal [mem 0x0100-0x37f9] > Movable zone start for each node > Early memory node ranges > node 0: [mem 0x1000-0x0009afff] > node 0: [mem 0x0010-0x3ffb] > On node 0 totalpages: 229178 > DMA zone: 32 pages used for memmap > DMA zone: 0 pages reserved > DMA zone: 3994 pages, LIFO batch:0 > Normal zone: 1760 pages used for memmap > Normal zone: 225184 pages, LIFO batch:31 > Using APIC driver default > ACPI: PM-Timer IO Port: 0x408 > ACPI: Local APIC address 0xfee0 > ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) > ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] disabled) > ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1]) > ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1]) > ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) > IOAPIC[0]: apic_id 2, version 32, address 0xfec0, GSI 0-23 > ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) > ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > ACPI: IRQ0 used by override. > ACPI: IRQ2 used by override. > ACPI: IRQ9 used by override. > Using ACPI (MADT) for SMP configuration information > nr_irqs_gsi: 40 > PM: Registered nosave memory: [mem 0x0009b000-0x0009bfff] > PM: Registered nosave memory: [mem 0x0009c000-0x000d] > PM: Registered nosave memory: [mem 0x000e-0x000f] > e820: [mem 0x4000-0xfebf] available for PCI devices > pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 > pcpu-alloc: [0] 0 > Built 1 zonelists in Zone order, mobility grouping on. Total pages: 227386 > Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.11.0-rc3 root=/dev/sda1 ro > PID hash table entries: 4096 (order: 2, 16384 bytes) > Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) > Inode-cache hash
3.11-rc3+git: __divdi3 undefined on powerpc (from radeon)
While trying to compile v3.11-rc3-288-gabe0308 on powerpc 32-bit, it failed with the following linking error: ERROR: "__divdi3" [drivers/gpu/drm/radeon/radeon.ko] undefined! Some new 64-bit division in radeon that is not implemented on 32-bit powerpc? This is new - 3.11-rc3 worked fine. -- Meelis Roos (mroos at linux.ee)
3.11-rc3+git: __divdi3 undefined on powerpc (from radeon)
While trying to compile v3.11-rc3-288-gabe0308 on powerpc 32-bit, it failed with the following linking error: ERROR: __divdi3 [drivers/gpu/drm/radeon/radeon.ko] undefined! Some new 64-bit division in radeon that is not implemented on 32-bit powerpc? This is new - 3.11-rc3 worked fine. -- Meelis Roos (mr...@linux.ee) ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
3.11-rc3: radeon WARNING at kernel/workqueue.c:1378 __queue_work+0x132/0x16d()
Just got this WARNING while loading radeon driver on a test PC that was running 3.10 fine (full dmesg below). The machine is a Intel 850 chipst PC with AGP Radeon 7000 and no monitor attached. lspci and config are also below. Linux version 3.11.0-rc3 (mroos at d850) (gcc version 4.8.1 (Debian 4.8.1-3) ) #48 Mon Jul 29 12:54:00 EEST 2013 e820: BIOS-provided physical RAM map: BIOS-e820: [mem 0x-0x0009bbff] usable BIOS-e820: [mem 0x0009bc00-0x0009bfff] reserved BIOS-e820: [mem 0x000e-0x000f] reserved BIOS-e820: [mem 0x0010-0x3ffb] usable BIOS-e820: [mem 0x3ffc-0x3fff7fff] ACPI data BIOS-e820: [mem 0x3fff8000-0x3fff] ACPI NVS BIOS-e820: [mem 0xfec0-0xfec00fff] reserved BIOS-e820: [mem 0xfee0-0xfee00fff] reserved BIOS-e820: [mem 0xffb8-0xffbf] reserved BIOS-e820: [mem 0xfff0-0x] reserved Notice: NX (Execute Disable) protection missing in CPU! Legacy DMI 2.3 present. DMI: MicroLink /D850MV , BIOS MV85010A.86A.0067.P24.0304081124 04/08/2003 e820: update [mem 0x-0x0fff] usable ==> reserved e820: remove [mem 0x000a-0x000f] usable e820: last_pfn = 0x3ffc0 max_arch_pfn = 0x10 MTRR default type: uncachable MTRR fixed ranges enabled: 0-9 write-back A-B uncachable C-C write-protect D-D uncachable E-F write-protect MTRR variable ranges enabled: 0 base 0 mask FC000 write-back 1 disabled 2 disabled 3 disabled 4 disabled 5 disabled 6 disabled 7 disabled x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 Warning only 895MB will be used. Use a HIGHMEM enabled kernel. found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [c00ff780] initial memory mapped: [mem 0x-0x017f] Base memory trampoline at [c0097000] 97000 size 16384 init_memory_mapping: [mem 0x-0x000f] [mem 0x-0x000f] page 4k init_memory_mapping: [mem 0x3780-0x37bf] [mem 0x3780-0x37bf] page 2M init_memory_mapping: [mem 0x3000-0x377f] [mem 0x3000-0x377f] page 2M init_memory_mapping: [mem 0x0010-0x2fff] [mem 0x0010-0x003f] page 4k [mem 0x0040-0x2fff] page 2M init_memory_mapping: [mem 0x37c0-0x37f9] [mem 0x37c0-0x37f9] page 4k BRK [0x013f2000, 0x013f2fff] PGTABLE ACPI: RSDP 000ff980 00014 (v00 AMI ) ACPI: RSDT 3fff 0002C (v01 D850MV MV85010A 20030408 MSFT 1011) ACPI: FACP 3fff1000 00074 (v01 D850MV MV85010A 20030408 MSFT 1011) ACPI: DSDT 3ffe 03954 (v01 D850MV MV85010A 0010 MSFT 010B) ACPI: FACS 3fff8000 00040 ACPI: APIC 3ffe3954 00068 (v01 D850MV MV85010A 20030408 MSFT 1011) ACPI: Local APIC address 0xfee0 895MB LOWMEM available. mapped low ram: 0 - 37fa low ram: 0 - 37fa Zone ranges: DMA [mem 0x1000-0x00ff] Normal [mem 0x0100-0x37f9] Movable zone start for each node Early memory node ranges node 0: [mem 0x1000-0x0009afff] node 0: [mem 0x0010-0x3ffb] On node 0 totalpages: 229178 DMA zone: 32 pages used for memmap DMA zone: 0 pages reserved DMA zone: 3994 pages, LIFO batch:0 Normal zone: 1760 pages used for memmap Normal zone: 225184 pages, LIFO batch:31 Using APIC driver default ACPI: PM-Timer IO Port: 0x408 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] disabled) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 2, version 32, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Using ACPI (MADT) for SMP configuration information nr_irqs_gsi: 40 PM: Registered nosave memory: [mem 0x0009b000-0x0009bfff] PM: Registered nosave memory: [mem 0x0009c000-0x000d] PM: Registered nosave memory: [mem 0x000e-0x000f] e820: [mem 0x4000-0xfebf] available for PCI devices pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 pcpu-alloc: [0] 0 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 227386 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.11.0-rc3 root=/dev/sda1 ro PID hash table entries: 4096 (order: 2, 16384 bytes) Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Initializing CPU#0 Memory: 903552K/916712K available (2259K kernel code, 249K rwdata, 936K rodata, 296K init, 260K bss, 13160K reserved) virtual kernel memory layout: fixmap : 0xfffa2000 - 0xf000 ( 372 kB)
Radeon RV100 init fails with specific card+mobo - IRQ problem
> >> > Adding some printks reveals it calls > >> > r100_init() -> radeon_irq_kms_init() -> drm_irq_install() -> > >> > drm_dev_to_irq() and that fails. So no IRQ, no KMS. > >> > > >> > lspci does not show Interrupt like on some other PCI devices. > >> > /proc/interrupts obviously does not contain the irq since we do not > >> > register any yet. > >> > > >> > There is no BIOS option of "Enable IRQ for VGA" or similar (BIOS is > >> > latest). Could this be the problem? > >> > > >> > What can I do to get KMS working on this computer? > >> > > >> > -- > >> > Meelis Roos (mroos at linux.ee) > >> > >> Try booting with radeon.agp_mode=-1 > > > > radeon: `-1' invalid for parameter `agp_mode' > > radeon.agpmode=-1 > > However, I think there are a number of places where we require > interrupts that would need to be worked around (fences, display > hotplug, pageflipping) if not interrupt is available. I did dome more testing with different cards an got a surprise. The machine works fine with other AGP cards - one MX440 with nouvea, another RV100 QY and a R200. They do have interrupt in lspci -vvv output. Why does this specific card not have its IRQ routed - card ROM problem? -- Meelis Roos (mroos at linux.ee)
Re: Radeon RV100 init fails with specific card+mobo - IRQ problem
Adding some printks reveals it calls r100_init() - radeon_irq_kms_init() - drm_irq_install() - drm_dev_to_irq() and that fails. So no IRQ, no KMS. lspci does not show Interrupt like on some other PCI devices. /proc/interrupts obviously does not contain the irq since we do not register any yet. There is no BIOS option of Enable IRQ for VGA or similar (BIOS is latest). Could this be the problem? What can I do to get KMS working on this computer? -- Meelis Roos (mr...@linux.ee) Try booting with radeon.agp_mode=-1 radeon: `-1' invalid for parameter `agp_mode' radeon.agpmode=-1 However, I think there are a number of places where we require interrupts that would need to be worked around (fences, display hotplug, pageflipping) if not interrupt is available. I did dome more testing with different cards an got a surprise. The machine works fine with other AGP cards - one MX440 with nouvea, another RV100 QY and a R200. They do have interrupt in lspci -vvv output. Why does this specific card not have its IRQ routed - card ROM problem? -- Meelis Roos (mr...@linux.ee) ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Radeon RV100 init fails with specific card+mobo - IRQ problem
> >> > Adding some printks reveals it calls > >> > r100_init() -> radeon_irq_kms_init() -> drm_irq_install() -> > >> > drm_dev_to_irq() and that fails. So no IRQ, no KMS. > >> > > >> > lspci does not show Interrupt like on some other PCI devices. > >> > /proc/interrupts obviously does not contain the irq since we do not > >> > register any yet. > >> > > >> > There is no BIOS option of "Enable IRQ for VGA" or similar (BIOS is > >> > latest). Could this be the problem? > >> > > >> > What can I do to get KMS working on this computer? > >> > > >> > -- > >> > Meelis Roos (mroos at linux.ee) > >> > >> Try booting with radeon.agp_mode=-1 > > > > radeon: `-1' invalid for parameter `agp_mode' > > radeon.agpmode=-1 Still fails in the same place as in the beginning - finding IRQ. > However, I think there are a number of places where we require > interrupts that would need to be worked around (fences, display > hotplug, pageflipping) if not interrupt is available. OK. -- Meelis Roos (mroos at linux.ee)
Radeon RV100 init fails with specific card+mobo - IRQ problem
> > Adding some printks reveals it calls > > r100_init() -> radeon_irq_kms_init() -> drm_irq_install() -> > > drm_dev_to_irq() and that fails. So no IRQ, no KMS. > > > > lspci does not show Interrupt like on some other PCI devices. > > /proc/interrupts obviously does not contain the irq since we do not > > register any yet. > > > > There is no BIOS option of "Enable IRQ for VGA" or similar (BIOS is > > latest). Could this be the problem? > > > > What can I do to get KMS working on this computer? > > > > -- > > Meelis Roos (mroos at linux.ee) > > Try booting with radeon.agp_mode=-1 radeon: `-1' invalid for parameter `agp_mode' -- Meelis Roos (mroos at linux.ee)
Radeon RV100 init fails with specific card+mobo - IRQ problem
I have a test PC with AMD 760MPX chipset (Tyan S2466 Tiger MPX board) and Radeon RV100-based AGP card where radeon KMS modesetting does not work (does not work with any kernel tried so far (2.6.32, 3.2, 3.7, 3.8-rc6). >From dmesg with drm.debug=0xc [3.209617] agpgart-amdk7 :00:00.0: AMD 760MP chipset [3.325408] agpgart-amdk7 :00:00.0: AGP aperture is 512M @ 0xc000 [...] [3.529106] [drm] Initialized drm 1.1.0 20060810 [3.797715] [drm] radeon defaulting to kernel modesetting. [3.797817] [drm] radeon kernel modesetting enabled. [3.799108] [drm] initializing kernel modesetting (RV100 0x1002:0x5159 0x1787:0x0F02). [3.799277] [drm] register mmio base: 0xB200 [3.799354] [drm] register mmio size: 65536 [3.799629] agpgart-amdk7 :00:00.0: AGP 2.0 bridge [3.799718] agpgart-amdk7 :00:00.0: putting AGP V2 device into 4x mode [3.799811] radeon :01:05.0: putting AGP V2 device into 4x mode [3.799900] radeon :01:05.0: GTT: 512M 0xC000 - 0xDFFF [3.799985] radeon :01:05.0: VRAM: 128M 0xE000 - 0xE7FF (64M used) [3.800187] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [3.800268] [drm] Driver supports precise vblank timestamp query. [3.800350] radeon :01:05.0: Fatal error during GPU init [3.800432] [drm] radeon: finishing device. [3.800509] [TTM] Memory type 2 has not been initialized [3.800590] [drm] radeon: cp finalized [3.800756] radeon: probe of :01:05.0 failed with error -22 01:05.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI RV100 QY [Radeon 7000/VE] [1002:5159] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device [1787:0f02] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B+ DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- radeon_irq_kms_init() -> drm_irq_install() -> drm_dev_to_irq() and that fails. So no IRQ, no KMS. lspci does not show Interrupt like on some other PCI devices. /proc/interrupts obviously does not contain the irq since we do not register any yet. There is no BIOS option of "Enable IRQ for VGA" or similar (BIOS is latest). Could this be the problem? What can I do to get KMS working on this computer? -- Meelis Roos (mroos at linux.ee)
Radeon RV100 init fails with specific card+mobo - IRQ problem
I have a test PC with AMD 760MPX chipset (Tyan S2466 Tiger MPX board) and Radeon RV100-based AGP card where radeon KMS modesetting does not work (does not work with any kernel tried so far (2.6.32, 3.2, 3.7, 3.8-rc6). From dmesg with drm.debug=0xc [3.209617] agpgart-amdk7 :00:00.0: AMD 760MP chipset [3.325408] agpgart-amdk7 :00:00.0: AGP aperture is 512M @ 0xc000 [...] [3.529106] [drm] Initialized drm 1.1.0 20060810 [3.797715] [drm] radeon defaulting to kernel modesetting. [3.797817] [drm] radeon kernel modesetting enabled. [3.799108] [drm] initializing kernel modesetting (RV100 0x1002:0x5159 0x1787:0x0F02). [3.799277] [drm] register mmio base: 0xB200 [3.799354] [drm] register mmio size: 65536 [3.799629] agpgart-amdk7 :00:00.0: AGP 2.0 bridge [3.799718] agpgart-amdk7 :00:00.0: putting AGP V2 device into 4x mode [3.799811] radeon :01:05.0: putting AGP V2 device into 4x mode [3.799900] radeon :01:05.0: GTT: 512M 0xC000 - 0xDFFF [3.799985] radeon :01:05.0: VRAM: 128M 0xE000 - 0xE7FF (64M used) [3.800187] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [3.800268] [drm] Driver supports precise vblank timestamp query. [3.800350] radeon :01:05.0: Fatal error during GPU init [3.800432] [drm] radeon: finishing device. [3.800509] [TTM] Memory type 2 has not been initialized [3.800590] [drm] radeon: cp finalized [3.800756] radeon: probe of :01:05.0 failed with error -22 01:05.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI RV100 QY [Radeon 7000/VE] [1002:5159] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device [1787:0f02] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B+ DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Region 0: Memory at e000 (32-bit, prefetchable) [size=128M] Region 1: I/O ports at 2000 [size=256] Region 2: Memory at b200 (32-bit, non-prefetchable) [size=64K] [virtual] Expansion ROM at b202 [disabled] [size=128K] Capabilities: [58] AGP version 2.0 Status: RQ=48 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4 Command: RQ=16 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x4 Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Adding some printks reveals it calls r100_init() - radeon_irq_kms_init() - drm_irq_install() - drm_dev_to_irq() and that fails. So no IRQ, no KMS. lspci does not show Interrupt like on some other PCI devices. /proc/interrupts obviously does not contain the irq since we do not register any yet. There is no BIOS option of Enable IRQ for VGA or similar (BIOS is latest). Could this be the problem? What can I do to get KMS working on this computer? -- Meelis Roos (mr...@linux.ee) ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: Radeon RV100 init fails with specific card+mobo - IRQ problem
Adding some printks reveals it calls r100_init() - radeon_irq_kms_init() - drm_irq_install() - drm_dev_to_irq() and that fails. So no IRQ, no KMS. lspci does not show Interrupt like on some other PCI devices. /proc/interrupts obviously does not contain the irq since we do not register any yet. There is no BIOS option of Enable IRQ for VGA or similar (BIOS is latest). Could this be the problem? What can I do to get KMS working on this computer? -- Meelis Roos (mr...@linux.ee) Try booting with radeon.agp_mode=-1 radeon: `-1' invalid for parameter `agp_mode' -- Meelis Roos (mr...@linux.ee) ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: Radeon RV100 init fails with specific card+mobo - IRQ problem
Adding some printks reveals it calls r100_init() - radeon_irq_kms_init() - drm_irq_install() - drm_dev_to_irq() and that fails. So no IRQ, no KMS. lspci does not show Interrupt like on some other PCI devices. /proc/interrupts obviously does not contain the irq since we do not register any yet. There is no BIOS option of Enable IRQ for VGA or similar (BIOS is latest). Could this be the problem? What can I do to get KMS working on this computer? -- Meelis Roos (mr...@linux.ee) Try booting with radeon.agp_mode=-1 radeon: `-1' invalid for parameter `agp_mode' radeon.agpmode=-1 Still fails in the same place as in the beginning - finding IRQ. However, I think there are a number of places where we require interrupts that would need to be worked around (fences, display hotplug, pageflipping) if not interrupt is available. OK. -- Meelis Roos (mr...@linux.ee) ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
New i915 warning from intel_dp_aux_ch
While testing out 3.8.0-rc4-00071-g9a92841 on a PC where I have ironlake_crtc_disable warning (https://bugzilla.kernel.org/show_bug.cgi?id=52061), I saw a new warning today that was not there with 3.8.0-rc3-00074. The previous warning is also still there. EDID is occasionally wrong on this PC, probably some timing issue in trying to read it out. It is not 100% reproducible - happened 3 out of 6 reboots. It happens together with the EDID warning - probably related. But since it is not always there, I do now knwo exactly since when it might be present. I managed to capture drm.debug=0xe output, full dmesg with debug is below is the main one. [0.270838] i915 :00:02.0: setting latency timer to 64 [0.283426] i915 :00:02.0: irq 40 for MSI/MSI-X [0.283431] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [0.283470] [drm] Driver supports precise vblank timestamp query. [0.283532] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [0.366758] [drm:intel_dp_aux_ch] *ERROR* dp_aux_ch not done status 0x0015003f [0.375148] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 142 [0.375210] Raw EDID: [0.375239] 00 ff ff ff ff ff ff 00 22 f0 49 29 00 00 00 00 [0.375275] 15 15 01 04 a5 33 1d 78 26 01 f5 a2 57 52 9f 27 [0.375312] 0a 50 54 a1 08 00 81 c0 81 80 95 00 b3 00 d1 c0 [0.375348] 01 01 01 01 01 01 02 3a 80 18 71 38 2d 40 58 2c [0.375385] 45 00 fe 1f 11 00 00 1e 00 00 00 fd 00 32 4c 18 [0.375421] 5e 11 00 0a 0a 0a 0a 0a 20 20 20 20 20 00 00 00 [0.375458] fc 00 48 50 20 4c 41 32 33 30 36 0a 20 20 20 00 [0.375495] 00 00 ff 00 43 4e 43 31 32 31 31 32 50 42 0a 20 [0.389465] [ cut here ] [0.389502] WARNING: at drivers/gpu/drm/i915/intel_dp.c:410 intel_dp_aux_ch+0x131/0x4e0() [0.389563] Hardware name: HP Compaq 8100 Elite SFF PC [0.389598] dp_aux_ch not started status 0x8025003f [0.389632] Modules linked in: [0.389671] Pid: 6, comm: kworker/u:0 Not tainted 3.8.0-rc4-00071-g9a92841 #80 [0.389729] Call Trace: [0.389762] [] ? warn_slowpath_common+0x79/0xc0 [0.389801] [] ? warn_slowpath_fmt+0x45/0x50 [0.389838] [] ? intel_dp_aux_ch+0x131/0x4e0 [0.389877] [] ? intel_dp_aux_native_write+0xa2/0xe0 [0.389916] [] ? intel_dp_aux_ch+0x3f1/0x4e0 [0.389953] [] ? intel_dp_set_link_train+0xbc/0x300 [0.389993] [] ? intel_dp_aux_native_write+0xa2/0xe0 [0.390032] [] ? intel_dp_start_link_train+0xf2/0x2f0 [0.390072] [] ? intel_dp_check_link_status+0x91/0x180 [0.390113] [] ? i915_hotplug_work_func+0x6e/0xa0 [0.390153] [] ? process_one_work+0x120/0x430 [0.390686] [] ? i915_error_work_func+0x100/0x100 [0.390725] [] ? worker_thread+0x15d/0x450 [0.390762] [] ? schedule_delayed_work+0x20/0x20 [0.390801] [] ? kthread+0xb3/0xc0 [0.390837] [] ? kthread_create_on_node+0x110/0x110 [0.390878] [] ? ret_from_fork+0x7c/0xb0 [0.390917] [] ? kthread_create_on_node+0x110/0x110 [0.390958] ---[ end trace 0f2d76d213a31275 ]--- [0.00] Linux version 3.8.0-rc4-00071-g9a92841 (mroos at prometheus) (gcc version 4.7.2 (Debian 4.7.2-5) ) #80 SMP Mon Jan 21 09:52:32 EET 2013 [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.8.0-rc4-00071-g9a92841 root=/dev/sda1 ro drm.debug=0xe [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009f7ff] usable [0.00] BIOS-e820: [mem 0x0009f800-0x0009] reserved [0.00] BIOS-e820: [mem 0x000e8000-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0xdb7ac43f] usable [0.00] BIOS-e820: [mem 0xdb7ac440-0xdb7ae49f] ACPI NVS [0.00] BIOS-e820: [mem 0xdb7ae4a0-0xdfff] reserved [0.00] BIOS-e820: [mem 0xf400-0xf7ff] reserved [0.00] BIOS-e820: [mem 0xfe00-0xfed3] reserved [0.00] BIOS-e820: [mem 0xfed45000-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x000117ff] usable [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.6 present. [0.00] DMI: Hewlett-Packard HP Compaq 8100 Elite SFF PC/304Ah, BIOS 786H1 v01.13 07/14/2011 [0.00] e820: update [mem 0x-0x] usable ==> reserved [0.00] e820: remove [mem 0x000a-0x000f] usable [0.00] No AGP bridge found [0.00] e820: last_pfn = 0x118000 max_arch_pfn = 0x4 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-B uncachable [0.00] C-E3FFF write-protect [0.00] E4000-E write-back [
WARNING: at drivers/gpu/drm/i915/intel_display.c:1009 ironlake_crtc_disable+0xaf/0x8e0
> >> I tried 3.7-rc5 on an ironlale PC and got the warning in subject. The > >> computer last ran 3.6.0 without any warnings. Second reboot showed the > >> same warning plus a couple of EDID warnings (also below). > > > > Still there with 3.7.0-rc7-00113-gcc19528 and 100% reproducible: > > Hm, can you please boot with drm.debug=0xe added to your kernel > cmdline and the attach the complete dmesg? Here you are. This time the EDID warning is there too, seems to depend on timing. [0.00] Linux version 3.7.0-rc7-00113-gcc19528 (mroos at prometheus) (gcc version 4.7.2 (Debian 4.7.2-4) ) #75 SMP Fri Nov 30 22:40:48 EET 2012 [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.7.0-rc7-00113-gcc19528 root=/dev/sda1 ro drm.debug=0xe [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009f7ff] usable [0.00] BIOS-e820: [mem 0x0009f800-0x0009] reserved [0.00] BIOS-e820: [mem 0x000e8000-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0xdb7ac43f] usable [0.00] BIOS-e820: [mem 0xdb7ac440-0xdb7ae49f] ACPI NVS [0.00] BIOS-e820: [mem 0xdb7ae4a0-0xdfff] reserved [0.00] BIOS-e820: [mem 0xf400-0xf7ff] reserved [0.00] BIOS-e820: [mem 0xfe00-0xfed3] reserved [0.00] BIOS-e820: [mem 0xfed45000-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x000117ff] usable [0.00] NX (Execute Disable) protection: active [0.00] DMI 2.6 present. [0.00] DMI: Hewlett-Packard HP Compaq 8100 Elite SFF PC/304Ah, BIOS 786H1 v01.13 07/14/2011 [0.00] e820: update [mem 0x-0x] usable ==> reserved [0.00] e820: remove [mem 0x000a-0x000f] usable [0.00] No AGP bridge found [0.00] e820: last_pfn = 0x118000 max_arch_pfn = 0x4 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-B uncachable [0.00] C-E3FFF write-protect [0.00] E4000-E write-back [0.00] F-F write-protect [0.00] MTRR variable ranges enabled: [0.00] 0 base 0 mask E write-back [0.00] 1 base 0DB80 mask FFF80 uncachable [0.00] 2 base 0DC00 mask FFC00 uncachable [0.00] 3 base 0E000 mask FE000 uncachable [0.00] 4 disabled [0.00] 5 disabled [0.00] 6 disabled [0.00] 7 disabled [0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 [0.00] e820: update [mem 0xdb80-0x] usable ==> reserved [0.00] e820: last_pfn = 0xdb7ac max_arch_pfn = 0x4 [0.00] found SMP MP-table at [mem 0x000f9bf0-0x000f9bff] mapped at [880f9bf0] [0.00] initial memory mapped: [mem 0x-0x1fff] [0.00] Base memory trampoline at [88099000] 99000 size 24576 [0.00] init_memory_mapping: [mem 0x-0xdb7abfff] [0.00] [mem 0x-0xdb5f] page 2M [0.00] [mem 0xdb60-0xdb7abfff] page 4k [0.00] kernel direct mapping tables up to 0xdb7abfff @ [mem 0x1fffa000-0x1fff] [0.00] init_memory_mapping: [mem 0x1-0x117ff] [0.00] [mem 0x1-0x117ff] page 2M [0.00] kernel direct mapping tables up to 0x117ff @ [mem 0xdb7aa000-0xdb7abfff] [0.00] ACPI: RSDP 000e5210 00014 (v00 COMPAQ) [0.00] ACPI: RSDT db7d0540 00040 (v01 HPQOEM SLIC-BPC 20110714 ) [0.00] ACPI: FACP db7d05e8 00074 (v01 COMPAQ IBEXPEAK 0001 ) [0.00] ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0050/0x0 (20120913/tbfadt-598) [0.00] ACPI BIOS Bug: Warning: Invalid length for FADT/Pm2ControlBlock: 0, using default 8 (20120913/tbfadt-648) [0.00] ACPI: DSDT db7d0a4f 0A69E (v01 COMPAQ DSDT_PRJ 0001 MSFT 010E) [0.00] ACPI: FACS db7d0500 00040 [0.00] ACPI: APIC db7d065c 000BC (v01 COMPAQ IBEXPEAK 0001 ) [0.00] ACPI: ASF! db7d0718 00063 (v32 COMPAQ IBEXPEAK 0001 ) [0.00] ACPI: MCFG db7d077b 0003C (v01 COMPAQ IBEXPEAK 0001 ) [0.00] ACPI: TCPA db7d07b7 00032 (v01 COMPAQ IBEXPEAK 0001 ) [0.00] ACPI: SLIC db7d07e9 00176 (v01 HPQOEM SLIC-BPC 0001 ) [0.00] ACPI: HPET db7d095f 00038 (v01 COMPAQ IBEXPEAK 0001 ) [0.00] ACPI: Local APIC address 0xfee0 [0.00] [ea00-ea00045f] PMD ->
WARNING: at drivers/gpu/drm/i915/intel_display.c:1009 ironlake_crtc_disable+0xaf/0x8e0
> I tried 3.7-rc5 on an ironlale PC and got the warning in subject. The > computer last ran 3.6.0 without any warnings. Second reboot showed the > same warning plus a couple of EDID warnings (also below). Still there with 3.7.0-rc7-00113-gcc19528 and 100% reproducible: [0.646574] WARNING: at drivers/gpu/drm/i915/intel_display.c:1009 ironlake_crtc_disable+0xaf/0x8e0() [0.646575] Hardware name: HP Compaq 8100 Elite SFF PC [0.646575] pipe_off wait timed out [0.646576] Modules linked in: [0.646578] Pid: 1, comm: swapper/0 Not tainted 3.7.0-rc7-00113-gcc19528 #75 [0.646578] Call Trace: [0.646583] [] ? warn_slowpath_common+0x79/0xc0 [0.646584] [] ? warn_slowpath_fmt+0x45/0x50 [0.646585] [] ? intel_wait_for_pipe_off+0x5b/0x170 [0.646586] [] ? ironlake_crtc_disable+0xaf/0x8e0 [0.646588] [] ? intel_dp_mode_fixup+0x249/0x270 [0.646590] [] ? intel_set_mode+0x306/0x920 [0.646592] [] ? intel_crtc_set_config+0x6f1/0x950 [0.646595] [] ? drm_fb_helper_set_par+0x6f/0xe0 [0.646598] [] ? fbcon_init+0x55f/0x5f0 [0.646600] [] ? visual_init+0xac/0x110 [0.646601] [] ? bind_con_driver+0x16c/0x340 [0.646602] [] ? take_over_console+0x60/0x70 [0.646604] [] ? fbcon_takeover+0x5b/0xc0 [0.646607] [] ? notifier_call_chain+0x45/0x60 [0.646608] [] ? __blocking_notifier_call_chain+0x55/0x80 [0.646609] [] ? register_framebuffer+0x1af/0x2e0 [0.646611] [] ? drm_fb_helper_single_fb_probe+0x1f4/0x320 [0.646612] [] ? drm_fb_helper_initial_config+0x1a9/0x220 [0.646615] [] ? __kmalloc+0xed/0x130 [0.646618] [] ? intel_fbdev_init+0x7d/0xb0 [0.646619] [] ? i915_driver_load+0xd95/0xf00 [0.646622] [] ? drm_get_pci_dev+0x185/0x2c0 [0.646624] [] ? pci_device_probe+0xd1/0x170 [0.646625] [] ? driver_probe_device+0x68/0x220 [0.646626] [] ? __driver_attach+0x93/0xa0 [0.646627] [] ? driver_probe_device+0x220/0x220 [0.646629] [] ? bus_for_each_dev+0x4d/0x80 [0.646630] [] ? bus_add_driver+0x178/0x260 [0.646631] [] ? driver_register+0x84/0x180 [0.646634] [] ? drm_core_init+0x12f/0x12f [0.646636] [] ? do_one_initcall+0x122/0x170 [0.646638] [] ? kernel_init+0x11c/0x2a0 [0.646641] [] ? do_early_param+0x83/0x83 [0.646643] [] ? schedule_tail+0x21/0xb0 [0.646644] [] ? rest_init+0x70/0x70 [0.646645] [] ? ret_from_fork+0x7c/0xb0 [0.646646] [] ? rest_init+0x70/0x70 [0.646650] ---[ end trace ed6fe7a7042b42d8 ]--- [0.702400] [drm:intel_disable_transcoder] *ERROR* failed to disable transcoder 0 -- Meelis Roos (mroos at ut.ee) http://www.cs.ut.ee/~mroos/
Re: WARNING: at drivers/gpu/drm/i915/intel_display.c:1009 ironlake_crtc_disable+0xaf/0x8e0
I tried 3.7-rc5 on an ironlale PC and got the warning in subject. The computer last ran 3.6.0 without any warnings. Second reboot showed the same warning plus a couple of EDID warnings (also below). Still there with 3.7.0-rc7-00113-gcc19528 and 100% reproducible: [0.646574] WARNING: at drivers/gpu/drm/i915/intel_display.c:1009 ironlake_crtc_disable+0xaf/0x8e0() [0.646575] Hardware name: HP Compaq 8100 Elite SFF PC [0.646575] pipe_off wait timed out [0.646576] Modules linked in: [0.646578] Pid: 1, comm: swapper/0 Not tainted 3.7.0-rc7-00113-gcc19528 #75 [0.646578] Call Trace: [0.646583] [81036899] ? warn_slowpath_common+0x79/0xc0 [0.646584] [81036995] ? warn_slowpath_fmt+0x45/0x50 [0.646585] [812b5ceb] ? intel_wait_for_pipe_off+0x5b/0x170 [0.646586] [812b669f] ? ironlake_crtc_disable+0xaf/0x8e0 [0.646588] [812c5ac9] ? intel_dp_mode_fixup+0x249/0x270 [0.646590] [812bd4c6] ? intel_set_mode+0x306/0x920 [0.646592] [812be1d1] ? intel_crtc_set_config+0x6f1/0x950 [0.646595] [8127545f] ? drm_fb_helper_set_par+0x6f/0xe0 [0.646598] [8120c7bf] ? fbcon_init+0x55f/0x5f0 [0.646600] [8125af8c] ? visual_init+0xac/0x110 [0.646601] [8125c7ec] ? bind_con_driver+0x16c/0x340 [0.646602] [8125ca20] ? take_over_console+0x60/0x70 [0.646604] [8120ab6b] ? fbcon_takeover+0x5b/0xc0 [0.646607] [81059375] ? notifier_call_chain+0x45/0x60 [0.646608] [81059555] ? __blocking_notifier_call_chain+0x55/0x80 [0.646609] [8120415f] ? register_framebuffer+0x1af/0x2e0 [0.646611] [812756c4] ? drm_fb_helper_single_fb_probe+0x1f4/0x320 [0.646612] [81275999] ? drm_fb_helper_initial_config+0x1a9/0x220 [0.646615] [810dd13d] ? __kmalloc+0xed/0x130 [0.646618] [812d6ead] ? intel_fbdev_init+0x7d/0xb0 [0.646619] [81298e55] ? i915_driver_load+0xd95/0xf00 [0.646622] [81283fa5] ? drm_get_pci_dev+0x185/0x2c0 [0.646624] [811f3d41] ? pci_device_probe+0xd1/0x170 [0.646625] [812e9ed8] ? driver_probe_device+0x68/0x220 [0.646626] [812ea123] ? __driver_attach+0x93/0xa0 [0.646627] [812ea090] ? driver_probe_device+0x220/0x220 [0.646629] [812e836d] ? bus_for_each_dev+0x4d/0x80 [0.646630] [812e9648] ? bus_add_driver+0x178/0x260 [0.646631] [812ea724] ? driver_register+0x84/0x180 [0.646634] [8188c7c4] ? drm_core_init+0x12f/0x12f [0.646636] [810002e2] ? do_one_initcall+0x122/0x170 [0.646638] [8142c6bc] ? kernel_init+0x11c/0x2a0 [0.646641] [8186c54a] ? do_early_param+0x83/0x83 [0.646643] [8105e761] ? schedule_tail+0x21/0xb0 [0.646644] [8142c5a0] ? rest_init+0x70/0x70 [0.646645] [814455ac] ? ret_from_fork+0x7c/0xb0 [0.646646] [8142c5a0] ? rest_init+0x70/0x70 [0.646650] ---[ end trace ed6fe7a7042b42d8 ]--- [0.702400] [drm:intel_disable_transcoder] *ERROR* failed to disable transcoder 0 -- Meelis Roos (mr...@ut.ee) http://www.cs.ut.ee/~mroos/ ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: at drivers/gpu/drm/i915/intel_display.c:1009 ironlake_crtc_disable+0xaf/0x8e0
I tried 3.7-rc5 on an ironlale PC and got the warning in subject. The computer last ran 3.6.0 without any warnings. Second reboot showed the same warning plus a couple of EDID warnings (also below). [0.00] Linux version 3.7.0-rc5 (mroos at prometheus) (gcc version 4.7.2 (Debian 4.7.2-4) ) #70 SMP Mon Nov 12 18:20:25 EET 2012 [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.7.0-rc5 root=/dev/sda1 ro [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009f7ff] usable [0.00] BIOS-e820: [mem 0x0009f800-0x0009] reserved [0.00] BIOS-e820: [mem 0x000e8000-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0xdb7ac43f] usable [0.00] BIOS-e820: [mem 0xdb7ac440-0xdb7ae49f] ACPI NVS [0.00] BIOS-e820: [mem 0xdb7ae4a0-0xdfff] reserved [0.00] BIOS-e820: [mem 0xf400-0xf7ff] reserved [0.00] BIOS-e820: [mem 0xfe00-0xfed3] reserved [0.00] BIOS-e820: [mem 0xfed45000-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x000117ff] usable [0.00] NX (Execute Disable) protection: active [0.00] DMI 2.6 present. [0.00] DMI: Hewlett-Packard HP Compaq 8100 Elite SFF PC/304Ah, BIOS 786H1 v01.13 07/14/2011 [0.00] e820: update [mem 0x-0x] usable ==> reserved [0.00] e820: remove [mem 0x000a-0x000f] usable [0.00] No AGP bridge found [0.00] e820: last_pfn = 0x118000 max_arch_pfn = 0x4 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-B uncachable [0.00] C-E3FFF write-protect [0.00] E4000-E write-back [0.00] F-F write-protect [0.00] MTRR variable ranges enabled: [0.00] 0 base 0 mask E write-back [0.00] 1 base 0DB80 mask FFF80 uncachable [0.00] 2 base 0DC00 mask FFC00 uncachable [0.00] 3 base 0E000 mask FE000 uncachable [0.00] 4 disabled [0.00] 5 disabled [0.00] 6 disabled [0.00] 7 disabled [0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 [0.00] e820: update [mem 0xdb80-0x] usable ==> reserved [0.00] e820: last_pfn = 0xdb7ac max_arch_pfn = 0x4 [0.00] found SMP MP-table at [mem 0x000f9bf0-0x000f9bff] mapped at [880f9bf0] [0.00] initial memory mapped: [mem 0x-0x1fff] [0.00] Base memory trampoline at [88099000] 99000 size 24576 [0.00] init_memory_mapping: [mem 0x-0xdb7abfff] [0.00] [mem 0x-0xdb5f] page 2M [0.00] [mem 0xdb60-0xdb7abfff] page 4k [0.00] kernel direct mapping tables up to 0xdb7abfff @ [mem 0x1fffa000-0x1fff] [0.00] init_memory_mapping: [mem 0x1-0x117ff] [0.00] [mem 0x1-0x117ff] page 2M [0.00] kernel direct mapping tables up to 0x117ff @ [mem 0xdb7aa000-0xdb7abfff] [0.00] ACPI: RSDP 000e5210 00014 (v00 COMPAQ) [0.00] ACPI: RSDT db7d0540 00040 (v01 HPQOEM SLIC-BPC 20110714 ) [0.00] ACPI: FACP db7d05e8 00074 (v01 COMPAQ IBEXPEAK 0001 ) [0.00] ACPI BIOS Bug: Warning: Optional FADT field Pm2ControlBlock has zero address or length: 0x0050/0x0 (20120913/tbfadt-598) [0.00] ACPI BIOS Bug: Warning: Invalid length for FADT/Pm2ControlBlock: 0, using default 8 (20120913/tbfadt-648) [0.00] ACPI: DSDT db7d0a4f 0A69E (v01 COMPAQ DSDT_PRJ 0001 MSFT 010E) [0.00] ACPI: FACS db7d0500 00040 [0.00] ACPI: APIC db7d065c 000BC (v01 COMPAQ IBEXPEAK 0001 ) [0.00] ACPI: ASF! db7d0718 00063 (v32 COMPAQ IBEXPEAK 0001 ) [0.00] ACPI: MCFG db7d077b 0003C (v01 COMPAQ IBEXPEAK 0001 ) [0.00] ACPI: TCPA db7d07b7 00032 (v01 COMPAQ IBEXPEAK 0001 ) [0.00] ACPI: SLIC db7d07e9 00176 (v01 HPQOEM SLIC-BPC 0001 ) [0.00] ACPI: HPET db7d095f 00038 (v01 COMPAQ IBEXPEAK 0001 ) [0.00] ACPI: Local APIC address 0xfee0 [0.00] [ea00-ea00045f] PMD -> [88011380-8801175f] on node 0 [0.00] Zone ranges: [0.00] DMA [mem 0x0001-0x00ff] [0.00] DMA32[mem 0x0100-0x] [0.00] Normal [mem 0x1-0x117ff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [
PCI Radeon RV100 detection hang on sparc64
This is with initialyy unmodified 3.6.0-rc4-00101-g0809095 kernel in Ultra 10 (clean, without my "Video RAM" hack that I talked in other sparclinux posts). When I saw that Sun XVR-100 was detected fine by the kernel, I compiled radeon drm driver with modesetting enabled and tried it: [drm] radeon defaulting to kernel modesetting. [drm] radeon kernel modesetting enabled. PCI: Enabling device: (:02:02.0), cmd 82 [drm] initializing kernel modesetting (RV100 0x1002:0x5159 0x1002:0x0908). [drm] register mmio base: 0x1000 [drm] register mmio size: 32768 [drm:radeon_device_init] *ERROR* Unable to find PCI I/O BAR And here the machine hangs. Debugging printk-s reveal that it does not find any active I/O port resources and then continues into initializing the card. Down in igp_read_bios_from_vram() it successfully ioremaps memory region 0 (vram_base=1ff0800 and size=4) and tries to read 2 bytes from there and hangs on reading bios[0]. With radeon.modeset=0, it boots and I collected the following info: 02:02.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV100 QY [Radeon 7000/VE] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices [AMD] nee ATI XVR-100 (supplied by Sun) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR-
3.5-rc5: radeon acceleration regression on Transmeta system
> > It's actually more complicated than that. Old kernel images started > > misbehaving from around 2.6.35-rc5 and any kernel older than that was > > OK. When I recompiled the older kernels with squeeze gcc (migh have been > > lenny gcc before, or different answers to make oldconfig), anything from > > current git down to 2.6.33 is broken with radeon.modeset=1 and works (I > > What releases of GCC were those? I'm chasing an issue where compiling > with 4.7.[01] breaks but 4.6.2 is OK, wondering if we're chasing the same > thing. I do not remember when I upgraded from lenny to squeeze. It the previous gcc was lenny's, it was gcc version 4.3.2 (Debian 4.3.2-1.1). The gcc in current stable (squeeze) is gcc version 4.4.5 (Debian 4.4.5-8). Since the old laptop is somewhat slow for following unstable, I have not tried any newer gcc version on that machine, and it has been compiling its own kernels for stress-testing purposes. So it's probably not related to gcc 4.6->4.7 changes. -- Meelis Roos (mroos at linux.ee)
3.5-rc5: radeon acceleration regression on Transmeta system
> > > In 3.4, radeon worked with a glitch - window titles were see-throug (not > > > drawn). In 3.5-rc5, radeon driver seems to be more careful and disables > > > acceleration on this system at all. Full dmesg below. > > > > Does it always do it the same? got the dmesg from 3.4 and/or 2.6.32? > > That was a good question. I did some more tries, and it was not > repeatable. Sometimes it worked like 3.4 did - rv100 initialized fine, > no borders except when maximized, otherwise worked. Re-tested 3.4.0-rc7 that I had availble from 3.4 times, it worked 4 out of 4 times. > Initial windows border problem seems to have been introduced between > 2.6.37 and 2.6.38, bisect is slow. It's actually more complicated than that. Old kernel images started misbehaving from around 2.6.35-rc5 and any kernel older than that was OK. When I recompiled the older kernels with squeeze gcc (migh have been lenny gcc before, or different answers to make oldconfig), anything from current git down to 2.6.33 is broken with radeon.modeset=1 and works (I get window titles) with radeon.modeset=0. 2.6.32 works and has kernel modesetting enabled from dmesg but I think I did not notice screen going fbcon during boot... maybe it only used the modesetting when X started. So there are 2 different problems (maybe related), the new one above and the old one of not seeing some window borders when modesetting and acceleration are in use. Maximized windows do have borders. -- Meelis Roos (mroos at linux.ee)
Re: 3.5-rc5: radeon acceleration regression on Transmeta system
In 3.4, radeon worked with a glitch - window titles were see-throug (not drawn). In 3.5-rc5, radeon driver seems to be more careful and disables acceleration on this system at all. Full dmesg below. Does it always do it the same? got the dmesg from 3.4 and/or 2.6.32? That was a good question. I did some more tries, and it was not repeatable. Sometimes it worked like 3.4 did - rv100 initialized fine, no borders except when maximized, otherwise worked. Re-tested 3.4.0-rc7 that I had availble from 3.4 times, it worked 4 out of 4 times. Initial windows border problem seems to have been introduced between 2.6.37 and 2.6.38, bisect is slow. It's actually more complicated than that. Old kernel images started misbehaving from around 2.6.35-rc5 and any kernel older than that was OK. When I recompiled the older kernels with squeeze gcc (migh have been lenny gcc before, or different answers to make oldconfig), anything from current git down to 2.6.33 is broken with radeon.modeset=1 and works (I get window titles) with radeon.modeset=0. 2.6.32 works and has kernel modesetting enabled from dmesg but I think I did not notice screen going fbcon during boot... maybe it only used the modesetting when X started. So there are 2 different problems (maybe related), the new one above and the old one of not seeing some window borders when modesetting and acceleration are in use. Maximized windows do have borders. -- Meelis Roos (mr...@linux.ee) ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
3.5-rc5: radeon acceleration regression on Transmeta system
ilters: protocol multicast [ 45.945918] NET: Registered protocol family 10 [ 46.384565] Bridge firewalling registered [ 55.289903] sshd (1379): /proc/1379/oom_adj is deprecated, please use /proc/1379/oom_score_adj instead. -- Meelis Roos (mroos at linux.ee)
3.5-rc5: radeon acceleration regression on Transmeta system
cated, please use /proc/1391/oom_score_adj instead. -- Meelis Roos (mroos at linux.ee)
3.5-rc5: radeon acceleration regression on Transmeta system
[ 59.527042] sshd (1391): /proc/1391/oom_adj is deprecated, please use /proc/1391/oom_score_adj instead. -- Meelis Roos (mr...@linux.ee) ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: 3.5-rc5: radeon acceleration regression on Transmeta system
] Bluetooth: BNEP filters: protocol multicast [ 45.945918] NET: Registered protocol family 10 [ 46.384565] Bridge firewalling registered [ 55.289903] sshd (1379): /proc/1379/oom_adj is deprecated, please use /proc/1379/oom_score_adj instead. -- Meelis Roos (mr...@linux.ee) ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Bisected regression: hang on i915 between 3.1.0-rc9 and 3.1.0
> > > 3.0 worked fine, 3.1-rc9 worked fine, I think -rc10 too. 3.1 release > > > hangs in random places while using X. > > Do you have VT-d enabled in the BIOS? Disabled VT-d in BIOS and 3.2-rc3 has been running stable since then. SO it seems to be the same problem. -- Meelis Roos (mroos at linux.ee)
Re: Bisected regression: hang on i915 between 3.1.0-rc9 and 3.1.0
3.0 worked fine, 3.1-rc9 worked fine, I think -rc10 too. 3.1 release hangs in random places while using X. Do you have VT-d enabled in the BIOS? Disabled VT-d in BIOS and 3.2-rc3 has been running stable since then. SO it seems to be the same problem. -- Meelis Roos (mr...@linux.ee) ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Bisected regression: hang on i915 between 3.1.0-rc9 and 3.1.0
> > Yes, VT-x and VT-d are both enabled from BIOS setup. > > Any reason for that? We've found all kinds of problems with DMAR enabled > on these machines that is only resolved by completely turning it > off. You might try with intel_iommu=off and make sure that's stable. Well, there is reason for VT-x but actually none for VT-d because I am not giving out any PCI devices to virtual machines. Will also test witout it. -- Meelis Roos (mroos at linux.ee)
Bisected regression: hang on i915 between 3.1.0-rc9 and 3.1.0
9.751924] microcode: CPU1 sig=0x20655, pf=0x2, revision=0x2 [9.755430] microcode: CPU2 sig=0x20655, pf=0x2, revision=0x2 [9.758865] microcode: CPU3 sig=0x20655, pf=0x2, revision=0x2 [9.761764] microcode: Microcode Update Driver: v2.00 , Peter Oruba [ 10.582948] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None [ 10.584633] e1000e :00:19.0: eth0: 10/100 speed: disabling TSO [ 10.586628] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 17.331458] lp0: using parport0 (interrupt-driven). [ 39.431271] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,commit=0 [ 293.184449] tun: Universal TUN/TAP device driver, 1.6 [ 293.184452] tun: (C) 1999-2004 Max Krasnyansky -- Meelis Roos (mroos at linux.ee)
Re: Bisected regression: hang on i915 between 3.1.0-rc9 and 3.1.0
Yes, VT-x and VT-d are both enabled from BIOS setup. Any reason for that? We've found all kinds of problems with DMAR enabled on these machines that is only resolved by completely turning it off. You might try with intel_iommu=off and make sure that's stable. Well, there is reason for VT-x but actually none for VT-d because I am not giving out any PCI devices to virtual machines. Will also test witout it. -- Meelis Roos (mr...@linux.ee) ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Bisected regression: hang on i915 between 3.1.0-rc9 and 3.1.0
> 3.0 worked fine, 3.1-rc9 worked fine, I think -rc10 too. 3.1 release > hangs in random places while using X. Just tested 3.2.0-rc2-00369-gbbbc479 after finishing bisecting, and it also freezes. .config below: # # Automatically generated file; DO NOT EDIT. # Linux/x86_64 3.2.0-rc2 Kernel Configuration # CONFIG_64BIT=y # CONFIG_X86_32 is not set CONFIG_X86_64=y CONFIG_X86=y CONFIG_INSTRUCTION_DECODER=y CONFIG_OUTPUT_FORMAT="elf64-x86-64" CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig" CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_ARCH_CLOCKSOURCE_DATA=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_NEED_DMA_MAP_STATE=y CONFIG_NEED_SG_DMA_LENGTH=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_GPIO=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y # CONFIG_RWSEM_GENERIC_SPINLOCK is not set CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_DEFAULT_IDLE=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y CONFIG_ZONE_DMA32=y CONFIG_ARCH_POPULATES_NODE_MAP=y CONFIG_AUDIT_ARCH=y CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y CONFIG_HAVE_INTEL_TXT=y CONFIG_X86_64_SMP=y CONFIG_X86_HT=y CONFIG_ARCH_HWEIGHT_CFLAGS="-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 -fcall-saved-r11" # CONFIG_KTIME_SCALAR is not set CONFIG_ARCH_CPU_PROBE_RELEASE=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" CONFIG_HAVE_IRQ_WORK=y CONFIG_IRQ_WORK=y # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_CROSS_COMPILE="" CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_HAVE_KERNEL_GZIP=y CONFIG_HAVE_KERNEL_BZIP2=y CONFIG_HAVE_KERNEL_LZMA=y CONFIG_HAVE_KERNEL_XZ=y CONFIG_HAVE_KERNEL_LZO=y # CONFIG_KERNEL_GZIP is not set # CONFIG_KERNEL_BZIP2 is not set CONFIG_KERNEL_LZMA=y # CONFIG_KERNEL_XZ is not set # CONFIG_KERNEL_LZO is not set CONFIG_DEFAULT_HOSTNAME="(none)" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_POSIX_MQUEUE_SYSCTL=y # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_FHANDLE=y CONFIG_TASKSTATS=y CONFIG_TASK_DELAY_ACCT=y CONFIG_TASK_XACCT=y CONFIG_TASK_IO_ACCOUNTING=y # CONFIG_AUDIT is not set CONFIG_HAVE_GENERIC_HARDIRQS=y # # IRQ subsystem # CONFIG_GENERIC_HARDIRQS=y CONFIG_HAVE_SPARSE_IRQ=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_GENERIC_IRQ_SHOW=y CONFIG_GENERIC_PENDING_IRQ=y CONFIG_IRQ_FORCED_THREADING=y CONFIG_SPARSE_IRQ=y # # RCU Subsystem # CONFIG_TREE_RCU=y # CONFIG_PREEMPT_RCU is not set # CONFIG_RCU_TRACE is not set CONFIG_RCU_FANOUT=64 # CONFIG_RCU_FANOUT_EXACT is not set CONFIG_RCU_FAST_NO_HZ=y # CONFIG_TREE_RCU_TRACE is not set # CONFIG_IKCONFIG is not set CONFIG_LOG_BUF_SHIFT=17 CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y CONFIG_CGROUPS=y # CONFIG_CGROUP_DEBUG is not set CONFIG_CGROUP_FREEZER=y CONFIG_CGROUP_DEVICE=y CONFIG_CPUSETS=y CONFIG_PROC_PID_CPUSET=y CONFIG_CGROUP_CPUACCT=y CONFIG_RESOURCE_COUNTERS=y CONFIG_CGROUP_MEM_RES_CTLR=y CONFIG_CGROUP_MEM_RES_CTLR_SWAP=y CONFIG_CGROUP_MEM_RES_CTLR_SWAP_ENABLED=y # CONFIG_CGROUP_PERF is not set CONFIG_CGROUP_SCHED=y CONFIG_FAIR_GROUP_SCHED=y CONFIG_CFS_BANDWIDTH=y CONFIG_RT_GROUP_SCHED=y CONFIG_BLK_CGROUP=y # CONFIG_DEBUG_BLK_CGROUP is not set CONFIG_NAMESPACES=y CONFIG_UTS_NS=y CONFIG_IPC_NS=y CONFIG_USER_NS=y CONFIG_PID_NS=y CONFIG_NET_NS=y # CONFIG_SCHED_AUTOGROUP is not set CONFIG_MM_OWNER=y # CONFIG_SYSFS_DEPRECATED is not set # CONFIG_RELAY is not set # CONFIG_BLK_DEV_INITRD is not set CONFIG_CC_OPTIMIZE_FOR_SIZE=y CONFIG_SYSCTL=y CONFIG_ANON_INODES=y # CONFIG_EXPERT is not set CONFIG_UID16=y # CONFIG_SYSCTL_SYSCALL is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_PCSPKR_PLATFORM=y CONFIG_HAVE_PCSPKR_PLATFORM=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_AIO=y # CONFIG_EMBEDDED is not set CONFIG_HAVE_PERF_EVENTS=y # # Kernel Performance Events And Counters # CONFIG_PERF_EVENTS=y # CONFIG_PERF_COUNTERS is not set # CONFIG_DEBUG_PERF_USE_VMALLOC is not set CONFIG_VM_EVENT_COUNTERS=y CONFIG_PCI_QUIRKS=y CONFIG_SLUB_DEBUG=y # CONFIG_COMPAT_BRK is not set # CONFIG_SLAB is not set CONFIG_SLUB=y # CONFIG_PROFILING is not set CONFIG_HAVE_OPROFILE=y # CONFIG_KPROBES is not set CONFIG_JUMP_LABEL=y CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y CONFIG_USER_RETURN_NOTIFIER=y CONFIG_HAVE_IOREMAP_PROT=y
Bisected regression: hang on i915 between 3.1.0-rc9 and 3.1.0
3.0 worked fine, 3.1-rc9 worked fine, I think -rc10 too. 3.1 release hangs in random places while using X. Core i5 660, lspci below. Running 64-bit Debian unstable. lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation Core Processor DRAM Controller [8086:0040] (rev 02) 00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 02) 00:16.0 Communication controller [0780]: Intel Corporation 5 Series/3400 Series Chipset HECI Controller [8086:3b64] (rev 06) 00:16.3 Serial controller [0700]: Intel Corporation 5 Series/3400 Series Chipset KT Controller [8086:3b67] (rev 06) 00:19.0 Ethernet controller [0200]: Intel Corporation 82578DM Gigabit Network Connection [8086:10ef] (rev 05) 00:1a.0 USB Controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b3c] (rev 05) 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b56] (rev 05) 00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 [8086:3b42] (rev 05) 00:1c.4 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5 [8086:3b4a] (rev 05) 00:1c.6 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 7 [8086:3b4e] (rev 05) 00:1d.0 USB Controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b34] (rev 05) 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev a5) 00:1f.0 ISA bridge [0601]: Intel Corporation 5 Series Chipset LPC Interface Controller [8086:3b0a] (rev 05) 00:1f.2 SATA controller [0106]: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller [8086:3b22] (rev 05) 3f:00.0 Host bridge [0600]: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers [8086:2c61] (rev 05) 3f:00.1 Host bridge [0600]: Intel Corporation Core Processor QuickPath Architecture System Address Decoder [8086:2d01] (rev 05) 3f:02.0 Host bridge [0600]: Intel Corporation Core Processor QPI Link 0 [8086:2d10] (rev 05) 3f:02.1 Host bridge [0600]: Intel Corporation Core Processor QPI Physical 0 [8086:2d11] (rev 05) 3f:02.2 Host bridge [0600]: Intel Corporation Core Processor Reserved [8086:2d12] (rev 05) 3f:02.3 Host bridge [0600]: Intel Corporation Core Processor Reserved [8086:2d13] (rev 05) Bisected it to the following commit. Bisection may not be 100% correct because the issue happens at random, and most of the "good" revisions got some usage without problems. The "bad" bisects are the ones that hang. 6fbcfb3e467adb414e235eeefaeaf51ad12f2461 is the first bad commit commit 6fbcfb3e467adb414e235eeefaeaf51ad12f2461 Author: David Woodhouse Date: Sun Sep 25 19:11:14 2011 -0700 intel-iommu: Workaround IOTLB hang on Ironlake GPU To work around a hardware issue, we have to submit IOTLB flushes while the graphics engine is idle. The graphics driver will (we hope) go to great lengths to ensure that it gets that right on the affected chipset(s)... so let's not screw it over by deferring the unmap and doing it later. That wouldn't be very helpful. Signed-off-by: David Woodhouse :04 04 3d2943d67945d8321d7aa8faac7497a8e8f1412a afaa155acfd1a7111ee607a971013ed615582ac8 M drivers git bisect log: git bisect start # good: [899e3ee404961a90b828ad527573c39f0ab1] Linux 3.1-rc10 git bisect good 899e3ee404961a90b828ad527573c39f0ab1 # bad: [c3b92c8787367a8bb53d57d9789b558f1295cc96] Linux 3.1 git bisect bad c3b92c8787367a8bb53d57d9789b558f1295cc96 # good: [505f48b53478d3816d1f3b001815703cfd7afa09] Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net git bisect good 505f48b53478d3816d1f3b001815703cfd7afa09 # good: [5117cc25fd43add94c04c9d2ace713c69a21bdb1] Merge branch 'hwmon-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging git bisect good 5117cc25fd43add94c04c9d2ace713c69a21bdb1 # bad: [4399c8bf2b9093696fa8160d79712e7346989c46] intel-iommu: fix superpage support in pfn_to_dma_pte() git bisect bad 4399c8bf2b9093696fa8160d79712e7346989c46 # bad: [c0771df8d5297bfb9c4fbe8ada085a49cb22ec4f] intel-iommu: Export a flag indicating that the IOMMU is used for iGFX. git bisect bad c0771df8d5297bfb9c4fbe8ada085a49cb22ec4f # bad: [6fbcfb3e467adb414e235eeefaeaf51ad12f2461] intel-iommu: Workaround IOTLB hang on Ironlake GPUgit bisect bad 6fbcfb3e467adb414e235eeefaeaf51ad12f2461 # good: [3e7abe2556b583e87dabda3e0e6178a67b20d06f] intel-iommu: Fix AB-BA lockdep report git bisect good 3e7abe2556b583e87dabda3e0e6178a67b20d06f -- Meelis Roos (mroos at linux.ee)
Bisected regression: hang on i915 between 3.1.0-rc9 and 3.1.0
3.0 worked fine, 3.1-rc9 worked fine, I think -rc10 too. 3.1 release hangs in random places while using X. Core i5 660, lspci below. Running 64-bit Debian unstable. lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation Core Processor DRAM Controller [8086:0040] (rev 02) 00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 02) 00:16.0 Communication controller [0780]: Intel Corporation 5 Series/3400 Series Chipset HECI Controller [8086:3b64] (rev 06) 00:16.3 Serial controller [0700]: Intel Corporation 5 Series/3400 Series Chipset KT Controller [8086:3b67] (rev 06) 00:19.0 Ethernet controller [0200]: Intel Corporation 82578DM Gigabit Network Connection [8086:10ef] (rev 05) 00:1a.0 USB Controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b3c] (rev 05) 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b56] (rev 05) 00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 [8086:3b42] (rev 05) 00:1c.4 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5 [8086:3b4a] (rev 05) 00:1c.6 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 7 [8086:3b4e] (rev 05) 00:1d.0 USB Controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b34] (rev 05) 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev a5) 00:1f.0 ISA bridge [0601]: Intel Corporation 5 Series Chipset LPC Interface Controller [8086:3b0a] (rev 05) 00:1f.2 SATA controller [0106]: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller [8086:3b22] (rev 05) 3f:00.0 Host bridge [0600]: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers [8086:2c61] (rev 05) 3f:00.1 Host bridge [0600]: Intel Corporation Core Processor QuickPath Architecture System Address Decoder [8086:2d01] (rev 05) 3f:02.0 Host bridge [0600]: Intel Corporation Core Processor QPI Link 0 [8086:2d10] (rev 05) 3f:02.1 Host bridge [0600]: Intel Corporation Core Processor QPI Physical 0 [8086:2d11] (rev 05) 3f:02.2 Host bridge [0600]: Intel Corporation Core Processor Reserved [8086:2d12] (rev 05) 3f:02.3 Host bridge [0600]: Intel Corporation Core Processor Reserved [8086:2d13] (rev 05) Bisected it to the following commit. Bisection may not be 100% correct because the issue happens at random, and most of the good revisions got some usage without problems. The bad bisects are the ones that hang. 6fbcfb3e467adb414e235eeefaeaf51ad12f2461 is the first bad commit commit 6fbcfb3e467adb414e235eeefaeaf51ad12f2461 Author: David Woodhouse dw...@infradead.org Date: Sun Sep 25 19:11:14 2011 -0700 intel-iommu: Workaround IOTLB hang on Ironlake GPU To work around a hardware issue, we have to submit IOTLB flushes while the graphics engine is idle. The graphics driver will (we hope) go to great lengths to ensure that it gets that right on the affected chipset(s)... so let's not screw it over by deferring the unmap and doing it later. That wouldn't be very helpful. Signed-off-by: David Woodhouse david.woodho...@intel.com :04 04 3d2943d67945d8321d7aa8faac7497a8e8f1412a afaa155acfd1a7111ee607a971013ed615582ac8 M drivers git bisect log: git bisect start # good: [899e3ee404961a90b828ad527573c39f0ab1] Linux 3.1-rc10 git bisect good 899e3ee404961a90b828ad527573c39f0ab1 # bad: [c3b92c8787367a8bb53d57d9789b558f1295cc96] Linux 3.1 git bisect bad c3b92c8787367a8bb53d57d9789b558f1295cc96 # good: [505f48b53478d3816d1f3b001815703cfd7afa09] Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net git bisect good 505f48b53478d3816d1f3b001815703cfd7afa09 # good: [5117cc25fd43add94c04c9d2ace713c69a21bdb1] Merge branch 'hwmon-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging git bisect good 5117cc25fd43add94c04c9d2ace713c69a21bdb1 # bad: [4399c8bf2b9093696fa8160d79712e7346989c46] intel-iommu: fix superpage support in pfn_to_dma_pte() git bisect bad 4399c8bf2b9093696fa8160d79712e7346989c46 # bad: [c0771df8d5297bfb9c4fbe8ada085a49cb22ec4f] intel-iommu: Export a flag indicating that the IOMMU is used for iGFX. git bisect bad c0771df8d5297bfb9c4fbe8ada085a49cb22ec4f # bad: [6fbcfb3e467adb414e235eeefaeaf51ad12f2461] intel-iommu: Workaround IOTLB hang on Ironlake GPUgit bisect bad 6fbcfb3e467adb414e235eeefaeaf51ad12f2461 # good: [3e7abe2556b583e87dabda3e0e6178a67b20d06f] intel-iommu: Fix AB-BA lockdep report git bisect good 3e7abe2556b583e87dabda3e0e6178a67b20d06f -- Meelis Roos (mr...@linux.ee) ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: Bisected regression: hang on i915 between 3.1.0-rc9 and 3.1.0
=0x2, revision=0x2 [9.761764] microcode: Microcode Update Driver: v2.00 tig...@aivazian.fsnet.co.uk, Peter Oruba [ 10.582948] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None [ 10.584633] e1000e :00:19.0: eth0: 10/100 speed: disabling TSO [ 10.586628] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 17.331458] lp0: using parport0 (interrupt-driven). [ 39.431271] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,commit=0 [ 293.184449] tun: Universal TUN/TAP device driver, 1.6 [ 293.184452] tun: (C) 1999-2004 Max Krasnyansky m...@qualcomm.com -- Meelis Roos (mr...@linux.ee) ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Radeon drm: Hang with posting GPU when PCI card is primary
> [ 10.169900] [drm] radeon kernel modesetting enabled. > [ 10.170270] radeon :02:00.0: enabling device (0080 -> 0083) > [ 10.170816] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 > [ 10.171044] radeon :02:00.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, > low) -> IRQ 11 > [ 10.172664] [drm] initializing kernel modesetting (RV100 0x1002:0x5159). > [ 10.172897] [drm] register mmio base: 0xFEAF > [ 10.173098] [drm] register mmio size: 65536 > [ 10.273609] [drm] GPU not posted. posting now... Hmm. Added some printk-s (POSTing combios for example) and now it did not hang any more but failed gracefully which is much better. [5.769826] [drm] radeon kernel modesetting enabled. [5.770181] radeon :02:00.0: enabling device (0080 -> 0083) [5.770677] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 [5.770903] radeon :02:00.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11 [5.772142] [drm] initializing kernel modesetting (RV100 0x1002:0x5159). [5.772363] [drm] register mmio base: 0xFEAF [5.772529] [drm] register mmio size: 65536 [5.914902] [drm] GPU not posted. posting now... [5.915086] [drm] POSTing combios [5.938458] agpgart-intel :00:00.0: AGP 2.0 bridge [5.938697] agpgart: Couldn't find an AGP VGA controller. [5.938914] radeon :02:00.0: GTT: 64M 0xF800 - 0xFBFF [5.939133] [drm] Generation 1 PCI interface in multifunction mode [5.939352] [drm] Limiting VRAM to one aperture [5.939569] radeon :02:00.0: limiting VRAM to PCI aperture size [5.939792] radeon :02:00.0: VRAM: 128M 0xE800 - 0xEFFF (128M used) [5.940212] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [5.940425] [drm] Driver supports precise vblank timestamp query. [5.940666] [drm] radeon: irq initialized. [5.941035] [drm] Detected VRAM RAM=128M, BAR=128M [5.941263] [drm] RAM width 64bits SDR [5.941607] [TTM] Zone kernel: Available graphics memory: 257508 kiB. [5.941825] [TTM] Initializing pool allocator. [5.942111] radeon :02:00.0: df650c00 pin failed [5.942351] radeon :02:00.0: Fatal error during GPU init [5.942567] [drm] radeon: finishing device. [5.942783] [drm] radeon: cp finalized [5.943014] [TTM] Trying to take down uninitialized memory manager type 1 [5.943243] [TTM] Finalizing pool allocator. [5.943523] [TTM] Zone kernel: Used memory at exit: 0 kiB. [5.943693] [drm] radeon: ttm finalized [5.944380] radeon :02:00.0: PCI INT A disabled [5.944564] radeon: probe of 0000:02:00.0 failed with error -22 -- Meelis Roos (mroos at ut.ee) http://www.cs.ut.ee/~mroos/
Modeline problem with Radeon KMS
> > So it decides this modeline is usable for the console while it is not. > > Ah, ok. yeah, that mode has a much higher clock than those chips can > handle. Where is that mode even coming from? I don't see it in the > EDID. The attached patch should filter out that mode. It works, thank you! Now the console is switching 256x96 charactest and I can see the console. fbset tells mode "2048x1536" geometry 2048 1536 2048 1536 8 timings 0 0 0 0 0 0 0 accel true rgba 8/0,8/0,8/0,0/0 endmode -- Meelis Roos (mroos at linux.ee)
Re: Modeline problem with Radeon KMS
So it decides this modeline is usable for the console while it is not. Ah, ok. yeah, that mode has a much higher clock than those chips can handle. Where is that mode even coming from? I don't see it in the EDID. The attached patch should filter out that mode. It works, thank you! Now the console is switching 256x96 charactest and I can see the console. fbset tells mode 2048x1536 geometry 2048 1536 2048 1536 8 timings 0 0 0 0 0 0 0 accel true rgba 8/0,8/0,8/0,0/0 endmode -- Meelis Roos (mr...@linux.ee) ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: Radeon drm: Hang with posting GPU when PCI card is primary
[ 10.169900] [drm] radeon kernel modesetting enabled. [ 10.170270] radeon :02:00.0: enabling device (0080 - 0083) [ 10.170816] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 [ 10.171044] radeon :02:00.0: PCI INT A - Link[LNKA] - GSI 11 (level, low) - IRQ 11 [ 10.172664] [drm] initializing kernel modesetting (RV100 0x1002:0x5159). [ 10.172897] [drm] register mmio base: 0xFEAF [ 10.173098] [drm] register mmio size: 65536 [ 10.273609] [drm] GPU not posted. posting now... Hmm. Added some printk-s (POSTing combios for example) and now it did not hang any more but failed gracefully which is much better. [5.769826] [drm] radeon kernel modesetting enabled. [5.770181] radeon :02:00.0: enabling device (0080 - 0083) [5.770677] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 [5.770903] radeon :02:00.0: PCI INT A - Link[LNKA] - GSI 11 (level, low) - IRQ 11 [5.772142] [drm] initializing kernel modesetting (RV100 0x1002:0x5159). [5.772363] [drm] register mmio base: 0xFEAF [5.772529] [drm] register mmio size: 65536 [5.914902] [drm] GPU not posted. posting now... [5.915086] [drm] POSTing combios [5.938458] agpgart-intel :00:00.0: AGP 2.0 bridge [5.938697] agpgart: Couldn't find an AGP VGA controller. [5.938914] radeon :02:00.0: GTT: 64M 0xF800 - 0xFBFF [5.939133] [drm] Generation 1 PCI interface in multifunction mode [5.939352] [drm] Limiting VRAM to one aperture [5.939569] radeon :02:00.0: limiting VRAM to PCI aperture size [5.939792] radeon :02:00.0: VRAM: 128M 0xE800 - 0xEFFF (128M used) [5.940212] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [5.940425] [drm] Driver supports precise vblank timestamp query. [5.940666] [drm] radeon: irq initialized. [5.941035] [drm] Detected VRAM RAM=128M, BAR=128M [5.941263] [drm] RAM width 64bits SDR [5.941607] [TTM] Zone kernel: Available graphics memory: 257508 kiB. [5.941825] [TTM] Initializing pool allocator. [5.942111] radeon :02:00.0: df650c00 pin failed [5.942351] radeon :02:00.0: Fatal error during GPU init [5.942567] [drm] radeon: finishing device. [5.942783] [drm] radeon: cp finalized [5.943014] [TTM] Trying to take down uninitialized memory manager type 1 [5.943243] [TTM] Finalizing pool allocator. [5.943523] [TTM] Zone kernel: Used memory at exit: 0 kiB. [5.943693] [drm] radeon: ttm finalized [5.944380] radeon :02:00.0: PCI INT A disabled [5.944564] radeon: probe of :02:00.0 failed with error -22 -- Meelis Roos (mr...@ut.ee) http://www.cs.ut.ee/~mroos/ ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Modeline problem with Radeon KMS
> > I have LG Flatron F900P CRT monitor. X drivers work fine, nouveau KMS > > works fine but Radeon KMS selects a videomode that is out of spec for > > monitor. This is not a regression - this hardware combination has never > > worked for me yet with radeon KMS. The result is same for Radeon 7000 > > (RV100, currently installed) and Radeon 9200 series card. Umm, I guess I forgot one important aspect. When X comes up, it finds a good video mode and gets a picture. It's just the text consoles that have no picture. In the console, it tells it's using 352x132 console. This translates with 8x16 font to 2816x2112 and 9x16 font to 3168x2112 if I calculated the right thing. Running fbset remotely verifies this: # fbset -s Is it just 2048x1536 that's causing problems? Do any other modes > work? 1600x1200 for example? X uses 2048x1536 successfully. 1600x1200, 1920x1440, 1280x1024 all work fine, just tested with xrandr. > > [ ? ?36.111] (II) RADEON(0): Output VGA-0 using monitor section CM771 > > I notice you have a monitor section defined in your xorg.conf. Does > that monitor section perhaps have any old modelines from an old > monitor that may be causing problems? X without configuration also gets a working 2048x1536. X conf seems to be quite irrelevant - scree-related things here, and my list of resolutions is ignored anyway for some reason not important righh now. Section "Device" Identifier "AGP kaart" Driver "ati" Option "AGPMode" "2" EndSection Section "Monitor" Identifier "CM771" Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "AGP kaart" Monitor "CM771" DefaultDepth24 SubSection "Display" Depth 1 Modes "1280x960" "1024x768" "832x624" "800x600" "720x400" "640x480" EndSubSection SubSection "Display" Depth 4 Modes "1280x960" "1024x768" "832x624" "800x600" "720x400" "640x480" EndSubSection SubSection "Display" Depth 8 Modes "1280x960" "1024x768" "832x624" "800x600" "720x400" "640x480" EndSubSection SubSection "Display" Depth 15 Modes "1280x960" "1024x768" "832x624" "800x600" "720x400" "640x480" EndSubSection SubSection "Display" Depth 16 Modes "1280x960" "1024x768" "832x624" "800x600" "720x400" "640x480" EndSubSection SubSection "Display" Depth 24 Modes "1280x960" "1024x768" "832x624" "800x600" "720x400" "640x480" EndSubSection EndSection -- Meelis Roos (mroos at linux.ee)
Modeline problem with Radeon KMS
Mouse (/dev/input/event1) [41.257] (**) ImExPS/2 Logitech Explorer Mouse: Applying InputClass "evdev pointer catchall" [41.257] (II) Using input driver 'evdev' for 'ImExPS/2 Logitech Explorer Mouse' [41.257] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so [41.257] (**) ImExPS/2 Logitech Explorer Mouse: always reports core events [41.257] (**) ImExPS/2 Logitech Explorer Mouse: Device: "/dev/input/event1" [41.257] (--) ImExPS/2 Logitech Explorer Mouse: Found 9 mouse buttons [41.257] (--) ImExPS/2 Logitech Explorer Mouse: Found scroll wheel(s) [41.257] (--) ImExPS/2 Logitech Explorer Mouse: Found relative axes [41.257] (--) ImExPS/2 Logitech Explorer Mouse: Found x and y relative axes [41.257] (II) ImExPS/2 Logitech Explorer Mouse: Configuring as mouse [41.257] (II) ImExPS/2 Logitech Explorer Mouse: Adding scrollwheel support [41.258] (**) ImExPS/2 Logitech Explorer Mouse: YAxisMapping: buttons 4 and 5 [41.258] (**) ImExPS/2 Logitech Explorer Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 [41.258] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input1/event1" [41.258] (II) XINPUT: Adding extended input device "ImExPS/2 Logitech Explorer Mouse" (type: MOUSE) [41.258] (II) ImExPS/2 Logitech Explorer Mouse: initialized for relative axes. [41.258] (**) ImExPS/2 Logitech Explorer Mouse: (accel) keeping acceleration scheme 1 [41.258] (**) ImExPS/2 Logitech Explorer Mouse: (accel) acceleration profile 0 [41.258] (**) ImExPS/2 Logitech Explorer Mouse: (accel) acceleration factor: 2.000 [41.258] (**) ImExPS/2 Logitech Explorer Mouse: (accel) acceleration threshold: 4 [41.259] (II) config/udev: Adding input device ImExPS/2 Logitech Explorer Mouse (/dev/input/mouse0) [41.259] (II) No input driver/identifier specified (ignoring) [41.271] (II) config/udev: Adding input device ACPI Virtual Keyboard Device (/dev/input/event4) [41.271] (**) ACPI Virtual Keyboard Device: Applying InputClass "evdev keyboard catchall" [41.271] (II) Using input driver 'evdev' for 'ACPI Virtual Keyboard Device' [41.271] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so [41.271] (**) ACPI Virtual Keyboard Device: always reports core events [41.276] (**) ACPI Virtual Keyboard Device: Device: "/dev/input/event4" [41.276] (--) ACPI Virtual Keyboard Device: Found keys [41.276] (II) ACPI Virtual Keyboard Device: Configuring as keyboard [41.276] (**) Option "config_info" "udev:/sys/devices/virtual/input/input4/event4" [41.276] (II) XINPUT: Adding extended input device "ACPI Virtual Keyboard Device" (type: KEYBOARD) [41.276] (**) Option "xkb_rules" "evdev" [41.276] (**) Option "xkb_model" "pc105" [41.276] (**) Option "xkb_layout" "ee" [41.276] (**) Option "xkb_options" "lv3:ralt_switch" -- Meelis Roos (mroos at linux.ee) -- next part -- A non-text attachment was scrubbed... Name: edid Type: application/octet-stream Size: 128 bytes Desc: URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20110608/fde7ed52/attachment-0001.obj>
Radeon drm: Hang with posting GPU when PCI card is primary
B hub found [9.839163] hub 1-0:1.0: 2 ports detected [9.839801] ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 10 [9.840111] PCI: setting IRQ 10 as level-triggered [9.840352] uhci_hcd :00:1f.4: PCI INT C -> Link[LNKH] -> GSI 10 (level, low) -> IRQ 10 [9.840795] uhci_hcd :00:1f.4: setting latency timer to 64 [9.841019] uhci_hcd :00:1f.4: UHCI Host Controller [9.841257] uhci_hcd :00:1f.4: new USB bus registered, assigned bus number 2 [9.841694] uhci_hcd :00:1f.4: irq 10, io base 0xef80 [9.842009] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 [9.842200] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [9.842525] usb usb2: Product: UHCI Host Controller [9.842709] usb usb2: Manufacturer: Linux 3.0.0-rc2-00108-gcb0a02e uhci_hcd [9.842896] usb usb2: SerialNumber: :00:1f.4 [9.850372] hub 2-0:1.0: USB hub found [9.850624] hub 2-0:1.0: 2 ports detected [ 10.169900] [drm] radeon kernel modesetting enabled. [ 10.170270] radeon :02:00.0: enabling device (0080 -> 0083) [ 10.170816] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 [ 10.171044] radeon :02:00.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11 [ 10.172664] [drm] initializing kernel modesetting (RV100 0x1002:0x5159). [ 10.172897] [drm] register mmio base: 0xFEAF [ 10.173098] [drm] register mmio size: 65536 [ 10.273609] [drm] GPU not posted. posting now... -- Meelis Roos (mroos at linux.ee)
Radeon drm: Hang with posting GPU when PCI card is primary
Link [LNKH] enabled at IRQ 10 [9.840111] PCI: setting IRQ 10 as level-triggered [9.840352] uhci_hcd :00:1f.4: PCI INT C - Link[LNKH] - GSI 10 (level, low) - IRQ 10 [9.840795] uhci_hcd :00:1f.4: setting latency timer to 64 [9.841019] uhci_hcd :00:1f.4: UHCI Host Controller [9.841257] uhci_hcd :00:1f.4: new USB bus registered, assigned bus number 2 [9.841694] uhci_hcd :00:1f.4: irq 10, io base 0xef80 [9.842009] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 [9.842200] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [9.842525] usb usb2: Product: UHCI Host Controller [9.842709] usb usb2: Manufacturer: Linux 3.0.0-rc2-00108-gcb0a02e uhci_hcd [9.842896] usb usb2: SerialNumber: :00:1f.4 [9.850372] hub 2-0:1.0: USB hub found [9.850624] hub 2-0:1.0: 2 ports detected [ 10.169900] [drm] radeon kernel modesetting enabled. [ 10.170270] radeon :02:00.0: enabling device (0080 - 0083) [ 10.170816] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 [ 10.171044] radeon :02:00.0: PCI INT A - Link[LNKA] - GSI 11 (level, low) - IRQ 11 [ 10.172664] [drm] initializing kernel modesetting (RV100 0x1002:0x5159). [ 10.172897] [drm] register mmio base: 0xFEAF [ 10.173098] [drm] register mmio size: 65536 [ 10.273609] [drm] GPU not posted. posting now... -- Meelis Roos (mr...@linux.ee) ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Modeline problem with Radeon KMS
) No input driver/identifier specified (ignoring) [41.271] (II) config/udev: Adding input device ACPI Virtual Keyboard Device (/dev/input/event4) [41.271] (**) ACPI Virtual Keyboard Device: Applying InputClass evdev keyboard catchall [41.271] (II) Using input driver 'evdev' for 'ACPI Virtual Keyboard Device' [41.271] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so [41.271] (**) ACPI Virtual Keyboard Device: always reports core events [41.276] (**) ACPI Virtual Keyboard Device: Device: /dev/input/event4 [41.276] (--) ACPI Virtual Keyboard Device: Found keys [41.276] (II) ACPI Virtual Keyboard Device: Configuring as keyboard [41.276] (**) Option config_info udev:/sys/devices/virtual/input/input4/event4 [41.276] (II) XINPUT: Adding extended input device ACPI Virtual Keyboard Device (type: KEYBOARD) [41.276] (**) Option xkb_rules evdev [41.276] (**) Option xkb_model pc105 [41.276] (**) Option xkb_layout ee [41.276] (**) Option xkb_options lv3:ralt_switch -- Meelis Roos (mr...@linux.ee) edid Description: Binary data ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: Modeline problem with Radeon KMS
I have LG Flatron F900P CRT monitor. X drivers work fine, nouveau KMS works fine but Radeon KMS selects a videomode that is out of spec for monitor. This is not a regression - this hardware combination has never worked for me yet with radeon KMS. The result is same for Radeon 7000 (RV100, currently installed) and Radeon 9200 series card. Umm, I guess I forgot one important aspect. When X comes up, it finds a good video mode and gets a picture. It's just the text consoles that have no picture. In the console, it tells it's using 352x132 console. This translates with 8x16 font to 2816x2112 and 9x16 font to 3168x2112 if I calculated the right thing. Running fbset remotely verifies this: # fbset -s /dev/tty1 mode 2816x2114 geometry 2816 2114 2816 2114 8 timings 0 0 0 0 0 0 0 accel true rgba 8/0,8/0,8/0,0/0 endmode So it decides this modeline is usable for the console while it is not. Is it just 2048x1536 that's causing problems? Do any other modes work? 1600x1200 for example? X uses 2048x1536 successfully. 1600x1200, 1920x1440, 1280x1024 all work fine, just tested with xrandr. [ 36.111] (II) RADEON(0): Output VGA-0 using monitor section CM771 I notice you have a monitor section defined in your xorg.conf. Does that monitor section perhaps have any old modelines from an old monitor that may be causing problems? X without configuration also gets a working 2048x1536. X conf seems to be quite irrelevant - scree-related things here, and my list of resolutions is ignored anyway for some reason not important righh now. Section Device Identifier AGP kaart Driver ati Option AGPMode 2 EndSection Section Monitor Identifier CM771 Option DPMS EndSection Section Screen Identifier Default Screen Device AGP kaart Monitor CM771 DefaultDepth24 SubSection Display Depth 1 Modes 1280x960 1024x768 832x624 800x600 720x400 640x480 EndSubSection SubSection Display Depth 4 Modes 1280x960 1024x768 832x624 800x600 720x400 640x480 EndSubSection SubSection Display Depth 8 Modes 1280x960 1024x768 832x624 800x600 720x400 640x480 EndSubSection SubSection Display Depth 15 Modes 1280x960 1024x768 832x624 800x600 720x400 640x480 EndSubSection SubSection Display Depth 16 Modes 1280x960 1024x768 832x624 800x600 720x400 640x480 EndSubSection SubSection Display Depth 24 Modes 1280x960 1024x768 832x624 800x600 720x400 640x480 EndSubSection EndSection -- Meelis Roos (mr...@linux.ee) ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[PATCH] fix i915 compile in 2.6.36-rc2
Commit 6ef3d4278034982c13df87c4a51e0445f762d316 introduces seq_file usage in intel_overlay.c but does not include the header and now compilation fails on i386. Fix it by including the necessary header. Signed-off-by: Meelis Roos diff --git a/drivers/gpu/drm/i915/intel_overlay.c b/drivers/gpu/drm/i915/intel_overlay.c index 4f00390..7e4b378 100644 --- a/drivers/gpu/drm/i915/intel_overlay.c +++ b/drivers/gpu/drm/i915/intel_overlay.c @@ -25,6 +25,7 @@ * * Derived from Xorg ddx, xf86-video-intel, src/i830_video.c */ +#include #include "drmP.h" #include "drm.h" #include "i915_drm.h" -- Meelis Roos (mroos at linux.ee)
