search for: 0x2400

...e 0x04000000 pref] [ 0.357412] pci 0000:04:00.0: BAR 16: no space for [mem size 0x04000000] [ 0.357413] pci 0000:04:00.0: BAR 16: failed to assign [mem size 0x04000000] [ 0.357415] pci 0000:04:00.0: BAR 13: assigned [io 0x2000-0x20ff] [ 0.357416] pci 0000:04:00.0: BAR 14: assigned [io 0x2400-0x24ff] [ 0.357418] pci 0000:04:00.0: BAR 16: no space for [mem size 0x04000000] [ 0.357420] pci 0000:04:00.0: BAR 16: failed to assign [mem size 0x04000000] [ 0.357421] pci 0000:04:00.0: BAR 15: no space for [mem size 0x04000000 pref] [ 0.357422] pci 0000:04:00.0: BAR 15: failed to ass...

...Fermi with quite as much certainty as what I've checked on a GF108. (For the G92, the texture buffer object test fails in the same way it does on Fermi, but there could be other reasons for that.) To be clear, when I say "unbound" for Fermi / Tesla, I mean BIND_TSC(ACTIVE=0) (method 0x2400, bit 0 == 0). Kepler doesn't have that, so presumably you mean TLD will look at TSC ID == 0, irrespective of the TSC ID encoded into the texture handle. The sRGB thing is ... rather annoying. Especially since texelFetch has some kind of extra-specially-odd rule around sRGB conversion. I don...

...smb_reh=0 smb_err=0 smb_flg=136 smb_flg2=51201 smb_tid=0 smb_pid=36418 smb_uid=0 smb_mid=1 smt_wct=17 smb_vwv[ 0]= 7 (0x7) smb_vwv[ 1]=12803 (0x3203) smb_vwv[ 2]= 256 (0x100) smb_vwv[ 3]= 1024 (0x400) smb_vwv[ 4]= 65 (0x41) smb_vwv[ 5]= 0 (0x0) smb_vwv[ 6]= 256 (0x100) smb_vwv[ 7]= 9216 (0x2400) smb_vwv[ 8]= 108 (0x6C) smb_vwv[ 9]=64768 (0xFD00) smb_vwv[10]=33011 (0x80F3) smb_vwv[11]= 128 (0x80) smb_vwv[12]=49166 (0xC00E) smb_vwv[13]= 5095 (0x13E7) smb_vwv[14]=51223 (0xC817) smb_vwv[15]=11265 (0x2C01) smb_vwv[16]= 1 (0x1) smb_bcc=58 size=127 smb_com=0x72 smb_rcls=0 smb_reh=0 smb_err=...

...T MTU:1500 Metric:1 RX packets:77670 errors:0 dropped:0 overruns:0 frame:0 TX packets:97635 errors:0 dropped:0 overruns:0 carrier:0 collisions:523 txqueuelen:1000 RX bytes:22858238 (21.7 MiB) TX bytes:21513745 (20.5 MiB) Interrupt:11 Base address:0x2400 eth1 Link encap:Ethernet HWaddr 00:50:FC:AC:52:4B inet addr:192.168.0.254 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::250:fcff:feac:524b/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:26676 errors:0 d...

Hello, This question is in the context of Tesla / Fermi generations, which have explicit bindings for textures / samplers. It might also apply to Kepler+, not quite as sure due to the bindless nature. I've been trying to understand how the TLD operation works (which is used to implement texelFetch in GLSL). It does not appear to the op takes an explicit sampler id at all (unlike all the

...upport usb1: <OHCI (generic) USB controller> on ohci1 usb1: USB revision 1.0 uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered pci1: <display, VGA> at device 5.0 (no driver attached) atapci0: <SiI 3512 SATA150 controller> port 0x2400-0x240f,0x2410-0x2413,0x2418-0x241f,0x2414-0x2417,0x2420-0x2427 mem 0xfc103000-0xfc1031ff irq 17 at device 6.0 on pci1 ata2: channel #0 on atapci0 ata3: channel #1 on atapci0 isab0: <PCI-ISA bridge> at device 7.0 on pci0 isa0: <ISA bus> on isab0 atapci1: <AMD 8111 UDMA133 controller&g...

...-0xf60043ff,0xf6000000-0xf6001fff irq 24 at device 6.0 on pci3 sym0: Symbios NVRAM, ID 7, Fast-40, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: handling phase mismatch from SCRIPTS. sym0: [GIANT-LOCKED] sym1: <896> port 0x2400-0x24ff mem 0xf6004400-0xf60047ff,0xf6002000-0xf6003fff irq 25 at device 6.1 on pci3 sym1: Symbios NVRAM, ID 7, Fast-40, SE, parity checking sym1: open drain IRQ line driver, using on-chip SRAM sym1: using LOAD/STORE-based firmware. sym1: handling phase mismatch from SCRIPTS. sym1: [GIANT-LOCKED] at...

Konrad, et al, I am seeing visual corruption (almost like an interlacing problem) with i915 under Xen on some platforms using linux-3.8. See attached file for an example of the visual corruption. This particular platform is an HP Elitebook 2540p The same kernel and ramdisk, when booted as native linux does not show this corruption. dmesg is attached, as well (out.txt) - but I did not see

...'connection=1 Read .* offset=0x0 count=0x400 ' blocksize2.log +# Write should become read-modify-write +grep 'connection=1 Write .* count=0x\(1\|200\) ' blocksize1.log || + { echo "qemu-io can't pass 1-byte writes"; exit 77; } +grep 'connection=1 Read .* offset=0x2400 count=0x400 ' blocksize2.log +grep 'connection=1 Write .* offset=0x2400 count=0x400 ' blocksize2.log +# Zero should become read-modify-write +if grep 'connection=1 Zero' blocksize2.log; then + echo "filter should have converted short zero to write" + exit 1 +fi +...

This may not be the proper place to raise this question but I've had little luck elsewhere. After trying again, unsuccessfully this time, to install the proprietary NVIDIA driver, I've decided to focus my efforts on the open source Nouveau driver. I've seen video drivers blamed for varying degrees of "freeze on resume" but I'm not certain that's what I'm up

...anta TNT2 graphics accelerator> at 2.0 irq 5 pci0: <unknown card> (vendor=0x0e11, dev=0xa0f0) at 12.0 sym0: <875> port 0x2000-0x20ff mem 0xc4fd0000-0xc4fd0fff,0xc4fe0000-0xc4fe00ff irq 10 at device 13.0 on pci0 sym0: No NVRAM, ID 7, Fast-20, SE, parity checking sym1: <875> port 0x2400-0x24ff mem 0xc4fb0000-0xc4fb0fff,0xc4fc0000-0xc4fc00ff irq 15 at device 13.1 on pci0 sym1: No NVRAM, ID 7, Fast-20, SE, parity checking pci0: <ATI Mach64-GV graphics accelerator> at 14.0 isab0: <Intel 82371AB PCI to ISA bridge> at device 15.0 on pci0 isa0: <ISA bus> on isab0 atapc...

i trust i am still new in freebsd, after go through all mail and book, = now seem to be more close, i got 3 server and a notebook to play with, = install no problem. cvsup not problem.make buildworld not problem. make = build kernel become,every machine i got different error code 1,=20 1-one got system full=20 2-one showing this sometime=20 > anyone know the best way to be one time success,not

...ce pcib0: <Intel 82443BX host to PCI bridge (AGP disabled)> on motherboard pci0: <PCI bus> on pcib0 sym0: <875> port 0x2000-0x20ff mem 0xc6aff000-0xc6afffff,0xc6afaf00-0xc6afafff irq 10 at device 6.0 on pci0 sym0: No NVRAM, ID 7, Fast-20, SE, parity checking sym1: <875> port 0x2400-0x24ff mem 0xc6afe000-0xc6afefff,0xc6afae00-0xc6afaeff irq 11 at device 6.1 on pci0 sym1: No NVRAM, ID 7, Fast-20, SE, parity checking tl0: <Compaq Netelligent 10/100 Proliant> port 0x3040-0x304f mem 0xc6afacf0-0xc6afacff irq 15 at device 7.0 on pci0 tl0: Ethernet address: 00:50:8b:dc:8a:75 m...

...aseTX-FDX, auto tlphy0: <ThunderLAN 10baseT media interface> on miibus0 tlphy0: 10base2/BNC, 10base5/AUI sym0: <875> port 0x2000-0x20ff mem 0xc6eff000-0xc6efffff,0xc6efcf00-0xc6efcfff i rq 9 at device 9.0 on pci1 sym0: No NVRAM, ID 7, Fast-20, SE, parity checking sym1: <875> port 0x2400-0x24ff mem 0xc6efe000-0xc6efefff,0xc6efce00-0xc6efceff i rq 10 at device 9.1 on pci1 sym1: No NVRAM, ID 7, Fast-20, SE, parity checking pci1: <unknown card> (vendor=0x10b8, dev=0x0005) at 10.0 irq 15 pci0: <unknown card> (vendor=0x0e11, dev=0xa0f0) at 14.0 pcib2: <IBM 82351 PCI-PCI b...

...lt;unknown card> (vendor=0x0e11, dev=0xa0f0) at 12.0 > > sym0: <875> port 0x2000-0x20ff mem > > 0xc4fd0000-0xc4fd0fff,0xc4fe0000-0xc4fe00ff irq 10 at > device > > 13.0 on pci0 > > sym0: No NVRAM, ID 7, Fast-20, SE, parity checking > > sym1: <875> port 0x2400-0x24ff mem > > 0xc4fb0000-0xc4fb0fff,0xc4fc0000-0xc4fc00ff irq 15 at > device > > 13.1 on pci0 > > sym1: No NVRAM, ID 7, Fast-20, SE, parity checking > > pci0: <ATI Mach64-GV graphics accelerator> at 14.0 > > isab0: <Intel 82371AB PCI to ISA bridge> at d...

...U> on acpi0 acpi_cpu1: <CPU> on acpi0 acpi_cpu2: <CPU> on acpi0 acpi_cpu3: <CPU> on acpi0 acpi_tz0: <thermal zone> on acpi0 pcib0: <ACPI Host-PCI bridge> on acpi0 pci0: <ACPI PCI bus> on pcib0 ahc0: <Adaptec (Compaq OEM) 3960D Ultra160 SCSI adapter> port 0x2400-0x24ff mem 0xf7df0000-0xf7df0fff irq 3 at device 2.0 on pci0 aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs ahc1: <Adaptec (Compaq OEM) 3960D Ultra160 SCSI adapter> port 0x2800-0x28ff mem 0xf7de0000-0xf7de0fff irq 3 at device 2.1 on pci0 aic7899: Ultra160 Wide Channel B, SCSI Id=7,...

...peripheral> at device 1.0 (no driver attached) pcib1: <ACPI PCI-PCI bridge> irq 16 at device 2.0 on pci0 pci1: <ACPI PCI bus> on pcib1 pcib2: <ACPI PCI-PCI bridge> at device 0.0 on pci1 pci2: <ACPI PCI bus> on pcib2 ahd0: <Adaptec AIC7902 Ultra320 SCSI adapter> port 0x2400-0x24ff,0x2000-0x20ff mem 0xdd200000-0xdd201fff irq 32 at device 2.0 on pci2 aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 101-133MHz, 512 SCBs ahd1: <Adaptec AIC7902 Ultra320 SCSI adapter> port 0x2c00-0x2cff,0x2800-0x28ff mem 0xdd202000-0xdd203fff irq 33 at device 2.1 on pci2 aic7902: Ul...

Hi! I'm currently hunting a strange problem and looking for help! I have a samba3 fileserver (currently samba-3.0.20b, but problem can be reproduced with samba-3.0.7, but _not_ with samba2 like 2.2.8a), and I see performance problems when writing files with MS word 2002 SP3 from a NT4.0 (SP6a) workstation. Saving even the smallest file takes more than 10 seconds! Copying files with Windows

Hi. The patch I send before was too large so that it was dropped from the maling list. I'm sending again with smaller size. This patch set is the xen paravirtualization of hand written assenbly code. And I expect that much clean up is necessary before merge. We really need the feed back before starting actual clean up as Eddie already said before. Eddie discussed how to clean up and suggested

Hi. The patch I send before was too large so that it was dropped from the maling list. I'm sending again with smaller size. This patch set is the xen paravirtualization of hand written assenbly code. And I expect that much clean up is necessary before merge. We really need the feed back before starting actual clean up as Eddie already said before. Eddie discussed how to clean up and suggested