Re: xorg hangs after last commits
On Wed, 2010-04-28 at 10:27 +0400, Alex Keda wrote: > 27.04.2010 18:13, Robert Noland пишет: > > > > > > Alex Keda wrote: > >> 27.04.2010 17:55, Robert Noland пишет: > >>> > >>> > >>> Alex Keda wrote: > >>>> Following recent changes in dri, xorg server freezes after 20-30 > >>>> seconds of work. mouse works, but the image does not change. > >>>> process xorg get 100% cpu > >>>> if I delete/rename drm.ko - all OK (but, very slow) > >>>> > >>>> > >>>> vgap...@pci0:1:5:0: class=0x03 card=0x12ff103c > >>>> chip=0x791e1002 rev=0x00 hdr=0x00 > >>>> vendor = 'ATI Technologies Inc. / Advanced Micro Devices, > >>>> Inc.' > >>>> device = 'ATI RADEON X1200 Series (RS690)' > >>>> class = display > >>>> subclass = VGA > >>>> bar [10] = type Prefetchable Memory, range 64, base > >>>> 0xd000, size 134217728, enabled > >>>> bar [18] = type Memory, range 64, base 0xd850, size > >>>> 65536, enabled > >>>> bar [20] = type I/O Port, range 32, base 0x1100, size 256, > >>>> enabled > >>>> bar [24] = type Memory, range 32, base 0xd840, size > >>>> 1048576, enabled > >>>> cap 01[50] = powerspec 2 supports D0 D1 D2 D3 current D0 > >>>> cap 05[80] = MSI supports 1 message, 64 bit > >>> > >>> Ok, does this patch help? > >> yes. I work without freeze more than 3 minutes =)) > > > > How about this one? > I reverse previous and apply it patch > working time more than without it (without ~1 minutes, with last patch > ~2-3 minutes), but - one final - Xorg get 100% CPU and freeze Ok, the IGP chips are strange... Just go with the first patch for now and let it keep snooping... Performance impact shouldn't be substantial. robert. > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" -- Robert Noland FreeBSD ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: xorg hangs after last commits
Alex Keda wrote: 27.04.2010 18:13, Robert Noland пишет: Alex Keda wrote: 27.04.2010 17:55, Robert Noland пишет: Alex Keda wrote: Following recent changes in dri, xorg server freezes after 20-30 seconds of work. mouse works, but the image does not change. process xorg get 100% cpu if I delete/rename drm.ko - all OK (but, very slow) vgap...@pci0:1:5:0: class=0x03 card=0x12ff103c chip=0x791e1002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'ATI RADEON X1200 Series (RS690)' class = display subclass = VGA bar [10] = type Prefetchable Memory, range 64, base 0xd000, size 134217728, enabled bar [18] = type Memory, range 64, base 0xd850, size 65536, enabled bar [20] = type I/O Port, range 32, base 0x1100, size 256, enabled bar [24] = type Memory, range 32, base 0xd840, size 1048576, enabled cap 01[50] = powerspec 2 supports D0 D1 D2 D3 current D0 cap 05[80] = MSI supports 1 message, 64 bit Ok, does this patch help? yes. I work without freeze more than 3 minutes =)) How about this one? it use with previous patch, or without it? Try this one by itself. robert. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: xorg hangs after last commits
Alex Keda wrote: 27.04.2010 17:55, Robert Noland пишет: Alex Keda wrote: Following recent changes in dri, xorg server freezes after 20-30 seconds of work. mouse works, but the image does not change. process xorg get 100% cpu if I delete/rename drm.ko - all OK (but, very slow) vgap...@pci0:1:5:0: class=0x03 card=0x12ff103c chip=0x791e1002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'ATI RADEON X1200 Series (RS690)' class = display subclass = VGA bar [10] = type Prefetchable Memory, range 64, base 0xd000, size 134217728, enabled bar [18] = type Memory, range 64, base 0xd850, size 65536, enabled bar [20] = type I/O Port, range 32, base 0x1100, size 256, enabled bar [24] = type Memory, range 32, base 0xd840, size 1048576, enabled cap 01[50] = powerspec 2 supports D0 D1 D2 D3 current D0 cap 05[80] = MSI supports 1 message, 64 bit Ok, does this patch help? yes. I work without freeze more than 3 minutes =)) How about this one? robert. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" Index: ati_pcigart.c === --- ati_pcigart.c (revision 207069) +++ ati_pcigart.c (working copy) @@ -220,6 +220,8 @@ ret = 1; done: + if (gart_info->gart_reg_if == DRM_ATI_GART_IGP) + DRM_MEMORYBARRIER(); gart_info->addr = address; gart_info->bus_addr = bus_address; return ret; ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: xorg hangs after last commits
Alex Keda wrote: Following recent changes in dri, xorg server freezes after 20-30 seconds of work. mouse works, but the image does not change. process xorg get 100% cpu if I delete/rename drm.ko - all OK (but, very slow) vgap...@pci0:1:5:0: class=0x03 card=0x12ff103c chip=0x791e1002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'ATI RADEON X1200 Series (RS690)' class = display subclass = VGA bar [10] = type Prefetchable Memory, range 64, base 0xd000, size 134217728, enabled bar [18] = type Memory, range 64, base 0xd850, size 65536, enabled bar [20] = type I/O Port, range 32, base 0x1100, size 256, enabled bar [24] = type Memory, range 32, base 0xd840, size 1048576, enabled cap 01[50] = powerspec 2 supports D0 D1 D2 D3 current D0 cap 05[80] = MSI supports 1 message, 64 bit Ok, does this patch help? robert. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" Index: ati_pcigart.c === --- ati_pcigart.c (revision 207069) +++ ati_pcigart.c (working copy) @@ -198,7 +198,7 @@ page_base |= (upper_32_bits(entry_addr) & 0xff) << 4; page_base |= ATI_GART_READ | ATI_GART_WRITE; -page_base |= ATI_GART_NOSNOOP; +//page_base |= ATI_GART_NOSNOOP; break; case DRM_ATI_GART_PCIE: page_base >>= 8; ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ports and PBIs
On Sat, 2010-04-10 at 15:18 +0100, Bruce Simpson wrote: > On 04/10/10 02:31, Julian Elischer wrote: > > > > Alfred Perlstein , Matt at ix systems Kris (Mr PBI), some > > others and I, felt that these ideas seemed to make some sense > > and so I put them here for comment. > > Please do. Someone has to do something about deployment. > > For what it's worth, I've tripped over the garden rake on the ground, > that is 'unsatisfied dependency' one too many times in commercial work. > > If PBIs can address this, even for FreeBSD's embedded and server use > cases, they will likely be well recieved. If I understood the PBI construct correctly... How is this really that different than just producing static binaries? I mean, as I understood it, your bundling the binary and all of it's required libraries into a private directory tree and then playing linker games. robert. > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" -- Robert Noland FreeBSD ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: gpart failing with no such geom after gpt corruption
Robert Noland wrote: Olivier Smedts wrote: 2010/4/1 Bartosz Stec : Hello ZFS and GPT hackers :) I'm sending this message to both freebsd-current and freebsd-fs because it doesn't seems to be a CURRENT-specific issue. Yesterday I tried to migrate my mixed UFS/RAIDZ config to clean RAIDZ with GPT boot. I've following mostly this guide: http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ1 I'm using CURRENT on 3x40GB HDDs (ad0-ad3) and additional 250GB HDD has been used for data migration (ad4). Data was copied form RAIDZ to 250GB HDD, GPT sheme was created on 40GB HDDs, then new zpool on them, and finally data went back to RAIDZ. Booting from RAIDZ was succesful, so far so good. After a while I've noticed some SMART errors on ad1, so I've booted machine with seatools for dos and made long test. One bad sector was found and reallocated, nothing to worry about. As I was in seatools already, I've decided to adjust LBA size on that disk (seatools can do that), because it was about 30MB larger than the other two, and because of that I had to adjust size of freebsd-zfs partition on that disk to match exact size of others (otherwise 'zpool create' will complain). So LBA was adjusted and system rebooted. I don't understand why you adjusted LBA. You're using GPT partitions, so, couldn't you just make the zfs partition the same size on all disks by adjusting it to the smallest disk, and let free space at the end of the bigger ones ? For that matter, my understanding is that ZFS just doesn't care. If you have disks of different sized in a raidz, the pool size will be limited by the size of the smallest device. If those devices are replaced with larger ones, then the pool just grows to take advantage of the additional available space. balrog% gpart show => 34 2097085 md0 GPT (1.0G) 34 1281 freebsd-boot (64K) 162 20969572 freebsd-zfs (1.0G) => 34 2097085 md1 GPT (1.0G) 34 1281 freebsd-boot (64K) 162 20969572 freebsd-zfs (1.0G) => 34 4194237 md2 GPT (2.0G) 34 1281 freebsd-boot (64K) 162 41941092 freebsd-zfs (2.0G) balrog% zpool status pool: test state: ONLINE scrub: none requested config: NAMESTATE READ WRITE CKSUM testONLINE 0 0 0 raidz1ONLINE 0 0 0 md0p2 ONLINE 0 0 0 md1p2 ONLINE 0 0 0 md2p2 ONLINE 0 0 0 errors: No known data errors balrog% zpool list NAME SIZE USED AVAILCAP HEALTH ALTROOT test 2.98G 141K 2.98G 0% ONLINE - robert. robert. Cheers, Olivier Yes, I was aware that changing disk size probably end with corrupted GPT and data loss, but it doesn't seem to be a big deal for me as far as 2/3 of zpool is alive, because I can always recreate gpt and resilver ad1. Unfortunately it wasn't so easy. First of all system booted, and as I expected kernel message shows GPT error on ad1. Zpool was degraded but alive and kicking. However, when I tried to execute any gpart command on ad1, it return: ad1: no such geom ad1 was present under /dev, and it could be accessed by sysinstall/fdisk, but no with gpart. I've created bsd slice with sysinstall on ad1 and rebooted, with hope that after reboot I could acces ad1 with gpart and recreate GPT scheme. Another surprise - system didn't boot at all, rebooting after couple of seconds in loader (changing boot device didn't make a difference). Only way I could boot system at this moment was connecting 250GB HDD which fortunately still had data from zpool migration and boot from it. Another surprise - kernel was still complaining about GPT corruption on ad1. I had no other ideas so I ran dd if=/dev/zero of=/dev/ad1 bs=512 count=512 to clear beginning of the hdd. After that disk was still unaccesible fromt gpart, so I tried sysinstall/fdisk againt to create standard BSD partitioning scheme and rebooted system. After that finally gpart started to talk with ad1 and GPT scheme and zpool has been recreated and work as it supposed to. Still, how can we clear broken GPT data after it got corrupted? Why gpart has been showing "ad1: no such geom", and how can we deal with this problem? Finally, why gptzfsboot failed with GPT corrupted on other disk after trying to fix it, while it booted at first place? Or maybe changing LBA size of already partitioned HDD is extreme case, and the only way these problems could be triggered ;)? Cheers! -- Bartosz Stec ___ freebsd...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-fs To unsubscribe, send any mail to "freebsd-fs-unsubscr...@freebsd.org" __
Re: gpart failing with no such geom after gpt corruption
Olivier Smedts wrote: 2010/4/1 Bartosz Stec : Hello ZFS and GPT hackers :) I'm sending this message to both freebsd-current and freebsd-fs because it doesn't seems to be a CURRENT-specific issue. Yesterday I tried to migrate my mixed UFS/RAIDZ config to clean RAIDZ with GPT boot. I've following mostly this guide: http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ1 I'm using CURRENT on 3x40GB HDDs (ad0-ad3) and additional 250GB HDD has been used for data migration (ad4). Data was copied form RAIDZ to 250GB HDD, GPT sheme was created on 40GB HDDs, then new zpool on them, and finally data went back to RAIDZ. Booting from RAIDZ was succesful, so far so good. After a while I've noticed some SMART errors on ad1, so I've booted machine with seatools for dos and made long test. One bad sector was found and reallocated, nothing to worry about. As I was in seatools already, I've decided to adjust LBA size on that disk (seatools can do that), because it was about 30MB larger than the other two, and because of that I had to adjust size of freebsd-zfs partition on that disk to match exact size of others (otherwise 'zpool create' will complain). So LBA was adjusted and system rebooted. I don't understand why you adjusted LBA. You're using GPT partitions, so, couldn't you just make the zfs partition the same size on all disks by adjusting it to the smallest disk, and let free space at the end of the bigger ones ? For that matter, my understanding is that ZFS just doesn't care. If you have disks of different sized in a raidz, the pool size will be limited by the size of the smallest device. If those devices are replaced with larger ones, then the pool just grows to take advantage of the additional available space. robert. Cheers, Olivier Yes, I was aware that changing disk size probably end with corrupted GPT and data loss, but it doesn't seem to be a big deal for me as far as 2/3 of zpool is alive, because I can always recreate gpt and resilver ad1. Unfortunately it wasn't so easy. First of all system booted, and as I expected kernel message shows GPT error on ad1. Zpool was degraded but alive and kicking. However, when I tried to execute any gpart command on ad1, it return: ad1: no such geom ad1 was present under /dev, and it could be accessed by sysinstall/fdisk, but no with gpart. I've created bsd slice with sysinstall on ad1 and rebooted, with hope that after reboot I could acces ad1 with gpart and recreate GPT scheme. Another surprise - system didn't boot at all, rebooting after couple of seconds in loader (changing boot device didn't make a difference). Only way I could boot system at this moment was connecting 250GB HDD which fortunately still had data from zpool migration and boot from it. Another surprise - kernel was still complaining about GPT corruption on ad1. I had no other ideas so I ran dd if=/dev/zero of=/dev/ad1 bs=512 count=512 to clear beginning of the hdd. After that disk was still unaccesible fromt gpart, so I tried sysinstall/fdisk againt to create standard BSD partitioning scheme and rebooted system. After that finally gpart started to talk with ad1 and GPT scheme and zpool has been recreated and work as it supposed to. Still, how can we clear broken GPT data after it got corrupted? Why gpart has been showing "ad1: no such geom", and how can we deal with this problem? Finally, why gptzfsboot failed with GPT corrupted on other disk after trying to fix it, while it booted at first place? Or maybe changing LBA size of already partitioned HDD is extreme case, and the only way these problems could be triggered ;)? Cheers! -- Bartosz Stec ___ freebsd...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-fs To unsubscribe, send any mail to "freebsd-fs-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: buildkernel broken
On Sat, 2010-03-13 at 19:35 +0200, Sergey V. Dyatko wrote: > Hi, > I'm trying to build kernel (update from 204272 to 205122) and > got following error: > > ===> drm/i915 (all) > cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE > -nostdinc -DHAVE_KERNEL_OPTION_HEADERS > -include /usr/obj/usr/src/sys/b450/opt_global.h -I. -I@ > -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 > --param large-function-growth=1000 -fno-common -g > -fno-omit-frame-pointer -I/usr/obj/usr/src/sys/b450 -mcmodel=kernel > -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx > -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding > -fstack-protector -std=iso9899:1999 -fstack-protector -Wall > -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef > -Wno-pointer-sign -fformat-extensions > -c /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_dma.c > /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_dma.c: > In function > 'i915_dma_cleanup': > /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_dma.c:159: > error: 'DEV' undeclared (first use in this Typo, pointyhat to me... Fixed in rev 205126. robert. > function) /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_dma.c:159: > error: (Each undeclared identifier is reported only > once /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_dma.c:159: > error: for each function it appears > in.) /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_dma.c: In > function > 'i915_set_status_page': > /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_dma.c:807: > error: 'DEV' undeclared (first use in this > function) /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_dma.c: In > function > 'i915_driver_load': > /usr/src/sys/modules/drm/i915/../../../dev/drm/i915_dma.c:847: > error: 'DEV' undeclared (first use in this function) *** Error code 1 > > Stop in /usr/src/sys/modules/drm/i915. > *** Error code 1 > > Stop in /usr/src/sys/modules/drm. > *** Error code 1 > > Stop in /usr/src/sys/modules. > *** Error code 1 > > Stop in /usr/obj/usr/src/sys/b450. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > > -- > wbr, tiger > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" -- Robert Noland FreeBSD ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
