Re: problems with em(4) since update to driver 7.2.2
Hello, 2011/4/27 Jack Vogel jfvo...@gmail.com: If you get cannot setup receive structures you cannot go on and try to use the thing :) It means you have inadequate mbuf clusters to setup your receive side, you simply have to increase it and reload the driver. I tried increasing kern.ipc.nmbjumbo* (is it what you suggested ?). Values doubled : kern.ipc.nmbjumbo16: 6400 kern.ipc.nmbjumbo9: 12800 kern.ipc.nmbjumbop: 25600 And unloaded / reloaded the kernel module. Still no luck, same problem, on latest 9-CURRENT (r221363). %sysctl -a | grep mbuf dev.em.0.mbuf_alloc_fail: 0 What can I do ? Do you want a dump of sysctl dev.em with old and new if_em module ? Thanks Here is what gives me netstat -m with my new 9-CURRENT kernel but with old (working, after some time of computer use) if_em.ko : 1027/3458/4485 mbufs in use (current/cache/total) 1024/2066/3090/25600 mbuf clusters in use (current/cache/total/max) 1024/1792 mbuf+clusters out of packet secondary zone in use (current/cache) 0/367/367/12800 4k (page size) jumbo clusters in use (current/cache/total/max) 0/0/0/6400 9k jumbo clusters in use (current/cache/total/max) 0/0/0/3200 16k jumbo clusters in use (current/cache/total/max) 2304K/6464K/8769K bytes allocated to network (current/cache/total) 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters denied (4k/9k/16k) 0/0/0 sfbufs in use (current/peak/max) 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 0 calls to protocol drain routines And here is the output with the new (non-working) if_em.ko : 1029/3456/4485 mbufs in use (current/cache/total) 1023/2067/3090/25600 mbuf clusters in use (current/cache/total/max) 1023/1793 mbuf+clusters out of packet secondary zone in use (current/cache) 0/367/367/12800 4k (page size) jumbo clusters in use (current/cache/total/max) 0/0/0/6400 9k jumbo clusters in use (current/cache/total/max) 0/0/0/3200 16k jumbo clusters in use (current/cache/total/max) 2303K/6466K/8769K bytes allocated to network (current/cache/total) 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters denied (4k/9k/16k) 0/0/0 sfbufs in use (current/peak/max) 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 0 calls to protocol drain routines I've got the em0: Could not setup receive structures messages with the new if_em.ko even in single user mode. No network connectivity. I tried removing all other network-related modules (vboxnet, ipfw...) and still have this problem (again, even when booting in single-user mode). My network card is em0@pci0:0:25:0: class=0x02 card=0x304b103c chip=0x10ef8086 rev=0x05 hdr=0x00. I'm using a stripped-down GENERIC amd64 kernel (no network, no scsi, no raid...), a nearly empty sysctl.conf and loader.conf (except module loading). I saw at the time of the commit that an MFC to 8-STABLE was planned, but I don't think it should happen so soon. Given that my network adapter was previously working well before the em driver update, can't this be considerd a serious regression ? Thanks, Olivier -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org - against HTML email vCards X www: http://www.gid0.org - against proprietary attachments / \ Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas. ___ 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
I am very confused and would appreciate some help on device renameing or on renumbering on current fstab.
I have two disks on this old machine that I have keep current sin FreeBSD 6 IIRC as preparation for all the new goodies but this really bit me in the morning with a generic kernel and had a heck of a time getting it up. I have a new kernel with the new options. optionsATA_CAM device ahci device mvs device siis This morning was such a shock that I am tempted to go back to the old kernel config that I understand still works but gonna try to bite the bullit. My fstab that I assume is still needed, is as before, although I had changed ad4xx to ada4xx (etc) that I found was incorrect the HARD way after trying to reboot; /dev/ad4s1bnoneswapsw 0 0 /dev/ad4s1a/ ufs rw 1 1 /dev/ad4s2g/backup ufs rw 2 2 /dev/ad4s1g/home ufs rw 2 2 /dev/ad4s2f/releaseufs rw 2 2 /dev/ad4s2d/tmpufs rw 2 2 /dev/ad4s1e/usrufs rw 2 2 /dev/ad4s1h/usr/local ufs rw 2 2 /dev/ad4s1f/varufs rw 2 2 /dev/ad4s2e/var/tmpufs rw 2 2 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /dev/acd1 /cdrom1 cd9660 ro,noauto 0 0 /dev/cd0 /cdrom cd9660 ro,noauto 0 0 /dev/cd1 /cdrom cd9660 ro,noauto 0 0 # /dev/ad0s1a /newufs rw 1 1 /dev/ad0s1g /new/home ufs rw 2 2 /dev/ad0s1d/new/tmpufs rw 2 2 /dev/ad0s1e/new/usrufs rw 2 2 /dev/ad0s1h /new/usr/local ufs rw 2 2 /dev/ad0s1f/new/varufs rw 2 2 I am totally confused on how these should now be. Any and all help appreciated. ed ___ 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: I am very confused and would appreciate some help on device renameing or on renumbering on current fstab.
On Tuesday, May 03, 2011 7:16:34 am Edwin L. Culp W. wrote: I have two disks on this old machine that I have keep current sin FreeBSD 6 IIRC as preparation for all the new goodies but this really bit me in the morning with a generic kernel and had a heck of a time getting it up. I have a new kernel with the new options. optionsATA_CAM device ahci device mvs device siis This morning was such a shock that I am tempted to go back to the old kernel config that I understand still works but gonna try to bite the bullit. My fstab that I assume is still needed, is as before, although I had changed ad4xx to ada4xx (etc) that I found was incorrect the HARD way after trying to reboot; /dev/ad4s1bnoneswapsw 0 0 /dev/ad4s1a/ ufs rw 1 1 /dev/ad4s2g/backup ufs rw 2 2 /dev/ad4s1g/home ufs rw 2 2 /dev/ad4s2f/releaseufs rw 2 2 /dev/ad4s2d/tmpufs rw 2 2 /dev/ad4s1e/usrufs rw 2 2 /dev/ad4s1h/usr/local ufs rw 2 2 /dev/ad4s1f/varufs rw 2 2 /dev/ad4s2e/var/tmpufs rw 2 2 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /dev/acd1 /cdrom1 cd9660 ro,noauto 0 0 /dev/cd0 /cdrom cd9660 ro,noauto 0 0 /dev/cd1 /cdrom cd9660 ro,noauto 0 0 # /dev/ad0s1a /newufs rw 1 1 /dev/ad0s1g /new/home ufs rw 2 2 /dev/ad0s1d/new/tmpufs rw 2 2 /dev/ad0s1e/new/usrufs rw 2 2 /dev/ad0s1h /new/usr/local ufs rw 2 2 /dev/ad0s1f/new/varufs rw 2 2 I am totally confused on how these should now be. Any and all help appreciated. It will be ada0 rather than ad4. With adaX the weird ATA_STATIC_ID stuff is gone and ATA disks are now numbered starting from 0 just like SCSI disks use da0, da1, ... etc. -- John Baldwin ___ 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: cardbus memory allocation problem
On Monday, May 02, 2011 10:29:56 pm Michael Butler wrote: I've stared at this for a (long) while but haven't come to any reasonable conclusion as to why it does what it does or how to fix it :-( Specifically, the BIOS in this machine doesn't set up a memory window for the cardbus controller nor does it properly configure the PCI bridge to route to the correct buses. BSD tries but allocates memory from the wrong space. My question is - how to get PCI-cardbus bridge to allocate memory inside the window of the parent PCI-PCI bridge? .. the bus tree looks like .. imb@toshi:/home/imb sudo lspci -t -[:00]-+-00.0 +-02.0 +-02.1 +-1b.0 +-1c.0-[02]-- +-1c.1-[03-04]-- +-1c.2-[05-06]00.0 +-1d.0 +-1d.1 +-1d.2 +-1d.3 +-1d.7 +-1e.0-[07]--+-06.0 |+-06.1 |+-06.2 |+-06.3 |\-08.0 +-1f.0 +-1f.2 \-1f.3 I've annotated the verbose dmesg below to highlight the issues .. pcib4: ACPI PCI-PCI bridge at device 30.0 on pci0 pcib4: domain0 pcib4: secondary bus 7 pcib4: subordinate bus 7 *** subordinate bus needs to be '9' so as to include both '8' '9' *** for the PCI-cardbus bridge I have WIP patches to fix this but they aren't ready yet. pcib4: I/O decode0x4000-0x4fff pcib4: memory decode 0xf090-0xf09f *** this memory widow is what I expected all children to allocate from pcib4: no prefetched decode pcib4: Subtractively decoded bridge. It's a subtractive bridge, so the resources do not have to be allocated from the window. That said, I'm committing the last of my patches to HEAD today to rework how PCI-PCI bridges handle I/O windows to support growing windows, etc. and the new PCI-PCI bridge driver will attempt to grow the memory window to allocate a new range before falling back to depending on the subtractive decode. cbb0: PCI-CardBus Bridge at device 6.0 on pci7 pcib4: cbb0 requested memory range 0x0-0x: good *** what appears to be a wildcard alloc request cbb0: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0xbf67 *** but which isn't constrained to be within the parent bridge's space Yes, it is a subtractive bridge, so that should be fine. The problem may be that the bf67 address may not be decoded by the parent Host-PCI bridge. There are some tunable hacks you can try to force this address higher, but I am also working on other patches (before the bus numbering ones) to query ACPI for the list of valid decoded ranges of PCI addresses for Host-PCI bridges and to restrict PCI allocations to coming from those ranges. You can try increasing hw.acpi.host_mem_start or hw.cbb.memory_start loader tunables. (There should be sysctl's with the current values I think.) -- John Baldwin ___ 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: A replacement for GEOM_LABEL's gpt/gptid
on 29/04/2011 19:55 Andrey V. Elsukov said the following: On 27.04.2011 11:37, Andrey V. Elsukov wrote: I wrote a small extension for the GEOM_PART class. It adds an ability to GEOM_PART class to create partition labels for schemes which are support them. Hi All, i got several successful reports from users, but now i decided to make this functional available for another consumers. New patch: http://people.freebsd.org/~ae/geom_alias.diff I really like your approach. One question - is it somehow possible to make the alias geom even more transparent? I mean completely eliminating g_alias_start() or making it more noop-ish. Thank you! What it contains: * gpt/gptid support removed from GEOM_LABEL class; * new GEOM_ALIAS class added. This class has two public functions: void g_alias_create(struct g_provider *pp, const char *name); void g_alias_spoil(struct g_provider *pp); * first two consumers of GEOM_ALIAS class are GEOM_PART and GEOM_DISK: GEOM_DISK uses g_alias_create() to create aliases for disks, disk's serial number is used for alias name. GEOM_PART uses g_alias_create() to create aliases for labeled partitions (gpt/gptid, apm and pc98). How it looks like: http://paste.org.ru/?5exeve -- Andriy Gapon ___ 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: I am very confused and would appreciate some help on device renameing or on renumbering on current fstab.
On Tue, May 3, 2011 at 6:59 AM, John Baldwin j...@freebsd.org wrote: On Tuesday, May 03, 2011 7:16:34 am Edwin L. Culp W. wrote: I have two disks on this old machine that I have keep current sin FreeBSD 6 IIRC as preparation for all the new goodies but this really bit me in the morning with a generic kernel and had a heck of a time getting it up. I have a new kernel with the new options. options ATA_CAM device ahci device mvs device siis This morning was such a shock that I am tempted to go back to the old kernel config that I understand still works but gonna try to bite the bullit. My fstab that I assume is still needed, is as before, although I had changed ad4xx to ada4xx (etc) that I found was incorrect the HARD way after trying to reboot; /dev/ad4s1b none swap sw 0 0 /dev/ad4s1a / ufs rw 1 1 /dev/ad4s2g /backup ufs rw 2 2 /dev/ad4s1g /home ufs rw 2 2 /dev/ad4s2f /release ufs rw 2 2 /dev/ad4s2d /tmp ufs rw 2 2 /dev/ad4s1e /usr ufs rw 2 2 /dev/ad4s1h /usr/local ufs rw 2 2 /dev/ad4s1f /var ufs rw 2 2 /dev/ad4s2e /var/tmp ufs rw 2 2 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /dev/acd1 /cdrom1 cd9660 ro,noauto 0 0 /dev/cd0 /cdrom cd9660 ro,noauto 0 0 /dev/cd1 /cdrom cd9660 ro,noauto 0 0 # /dev/ad0s1a /new ufs rw 1 1 /dev/ad0s1g /new/home ufs rw 2 2 /dev/ad0s1d /new/tmp ufs rw 2 2 /dev/ad0s1e /new/usr ufs rw 2 2 /dev/ad0s1h /new/usr/local ufs rw 2 2 /dev/ad0s1f /new/var ufs rw 2 2 I am totally confused on how these should now be. Any and all help appreciated. It will be ada0 rather than ad4. With adaX the weird ATA_STATIC_ID stuff is gone and ATA disks are now numbered starting from 0 just like SCSI disks use da0, da1, ... etc. -- John Baldwin Thanks, John. I was afraid that was the answer. Now, II'm really confused. I'm guessing that the partitions will notl need to be shown in fstab (ada0s1a). What little mind I have left is a blank, /dev/ad4s1g will be automatically be detected. Is that correct? What will I do with my second disk /dev/ad0s1a that is already zero? I apologize but I have really confused myself. I've filled my glass with too much water and I'm drowning. Thanks for everyone's patience. ed P.S. If I am not the only idiot, maybe a couple of lines as an example could go into UPDATING. ___ 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
Totally confused with the /usrsrc/UPDATING for 20110424 CAM-based ATA stack
With this confusion I need someone to give me an idea on renumbering. I have two disks on this old machine that I have keep current sin FreeBSD 6 IIRC as preparation for all the new goodies but this really bit me in the morning with a generic kernel and had a heck of a time getting it up. I have a new kernel with the new options. optionsATA_CAM device ahci device mvs device siis This morning was such a shock that I am tempted to go back to the old kernel config that I understand still works but gonna try to bite the bullit. My fstab that I assume is still necessary is: /dev/ad4s1bnoneswapsw 0 0 /dev/ad4s1a/ ufs rw 1 1 /dev/ad4s2g/backup ufs rw 2 2 /dev/ad4s1g/home ufs rw 2 2 /dev/ad4s2f/releaseufs rw 2 2 /dev/ad4s2d/tmpufs rw 2 2 /dev/ad4s1e/usrufs rw 2 2 /dev/ad4s1h/usr/local ufs rw 2 2 /dev/ad4s1f/varufs rw 2 2 /dev/ad4s2e/var/tmpufs rw 2 2 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /dev/acd1 /cdrom1 cd9660 ro,noauto 0 0 /dev/cd0 /cdrom cd9660 ro,noauto 0 0 /dev/cd1 /cdrom cd9660 ro,noauto 0 0 # /dev/ad0s1a /newufs rw 1 1 /dev/ad0s1g /new/home ufs rw 2 2 /dev/ad0s1d/new/tmpufs rw 2 2 /dev/ad0s1e/new/usrufs rw 2 2 /dev/ada01h /new/usr/local ufs rw 2 2 /dev/ada01f/new/varufs rw 2 2 I am totally confused on how these should now be. Any help appreciated. ed ___ 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: I am very confused and would appreciate some help on device renameing or on renumbering on current fstab.
On Tue, 3 May 2011, Edwin L. Culp W. wrote: It will be ada0 rather than ad4. With adaX the weird ATA_STATIC_ID stuff is gone and ATA disks are now numbered starting from 0 just like SCSI disks use da0, da1, ... etc. -- John Baldwin Thanks, John. I was afraid that was the answer. Now, II'm really confused. I'm guessing that the partitions will notl need to be shown in fstab (ada0s1a). What little mind I have left is a blank, /dev/ad4s1g will be automatically be detected. Is that correct? What will I do with my second disk /dev/ad0s1a that is already zero? The device names change from ad to ada. Slice and partition identifiers don't change. Device numbering is dynamic with ahci. Using labels is an easy way to not have to worry about a device's name or number. Moving A FreeBSD System To AHCI http://www.wonkity.com/~wblock/docs/html/ahci.html FreeBSD Labeled Filesystems http://www.wonkity.com/~wblock/docs/html/labels.html___ 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: I am very confused and would appreciate some help on device renameing or on renumbering on current fstab.
On Tuesday, May 03, 2011 8:51:02 am Edwin L. Culp W. wrote: On Tue, May 3, 2011 at 6:59 AM, John Baldwin j...@freebsd.org wrote: On Tuesday, May 03, 2011 7:16:34 am Edwin L. Culp W. wrote: I have two disks on this old machine that I have keep current sin FreeBSD 6 IIRC as preparation for all the new goodies but this really bit me in the morning with a generic kernel and had a heck of a time getting it up. I have a new kernel with the new options. optionsATA_CAM device ahci device mvs device siis This morning was such a shock that I am tempted to go back to the old kernel config that I understand still works but gonna try to bite the bullit. My fstab that I assume is still needed, is as before, although I had changed ad4xx to ada4xx (etc) that I found was incorrect the HARD way after trying to reboot; /dev/ad4s1bnoneswapsw 0 0 /dev/ad4s1a/ ufs rw 1 1 /dev/ad4s2g/backup ufs rw 2 2 /dev/ad4s1g/home ufs rw 2 2 /dev/ad4s2f/releaseufs rw 2 2 /dev/ad4s2d/tmpufs rw 2 2 /dev/ad4s1e/usrufs rw 2 2 /dev/ad4s1h/usr/local ufs rw 2 2 /dev/ad4s1f/varufs rw 2 2 /dev/ad4s2e/var/tmpufs rw 2 2 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /dev/acd1 /cdrom1 cd9660 ro,noauto 0 0 /dev/cd0 /cdrom cd9660 ro,noauto 0 0 /dev/cd1 /cdrom cd9660 ro,noauto 0 0 # /dev/ad0s1a /newufs rw 1 1 /dev/ad0s1g /new/home ufs rw 2 2 /dev/ad0s1d/new/tmpufs rw 2 2 /dev/ad0s1e/new/usrufs rw 2 2 /dev/ad0s1h /new/usr/local ufs rw 2 2 /dev/ad0s1f/new/varufs rw 2 2 I am totally confused on how these should now be. Any and all help appreciated. It will be ada0 rather than ad4. With adaX the weird ATA_STATIC_ID stuff is gone and ATA disks are now numbered starting from 0 just like SCSI disks use da0, da1, ... etc. -- John Baldwin Thanks, John. I was afraid that was the answer. Now, II'm really confused. I'm guessing that the partitions will notl need to be shown in fstab (ada0s1a). What little mind I have left is a blank, /dev/ad4s1g will be automatically be detected. Is that correct? What will I do with my second disk /dev/ad0s1a that is already zero? I apologize but I have really confused myself. I've filled my glass with too much water and I'm drowning. Thanks for everyone's patience. ed P.S. If I am not the only idiot, maybe a couple of lines as an example could go into UPDATING. Oh, I missed that you had an ad0. Most likely ad0 will become ada0, and ad4 will become ada1. All the partitions will still exist, so ad0s1a will become ada0s1a and ad4s1a will become ada1s1a. There is a chance that ad0 will become ada1 and ad4 will become ada1 instead. That depends on how your PCI devices are laid out on the PCI bus. I can't answer that without seeing a dmesg though. Do you have mav's latest changes? They should provide aliases for the old names along with printfs to let you know what the new names are for each old disk I think. -- John Baldwin ___ 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: I am very confused and would appreciate some help on device renameing or on renumbering on current fstab.
Thanks, John. I was afraid that was the answer. Now, II'm really confused. I'm guessing that the partitions will notl need to be shown in fstab (ada0s1a). What little mind I have left is a blank, /dev/ad4s1g will be automatically be detected. Is that correct? What will I do with my second disk /dev/ad0s1a that is already zero? I apologize but I have really confused myself. I've filled my glass with too much water and I'm drowning. Thanks for everyone's patience. ed P.S. If I am not the only idiot, maybe a couple of lines as an example could go into UPDATING. If I have understood ada correct, the first disk (lowest current number) is ada0, the next ada1, and so on. If you have ad0 and ad4, they will be ad0=ada0, and ad4=ada1 . It doesn't affect anything _except_ the disk names, so ad4s1f = ada1s1f and so on. You'll have to change most of your fstab, basically s/ad0/ada0/g and s/ad4/ada1/g . That said, my one ad to ada transition was on a ZFS-only system, which took the fstab editing out of it. I might be horribly wrong in some or all of the above. -- Daniel Nebdal ___ 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
a process waits forever
Hi, I've got a problem which I harly can explain. Latest CURRENT built with gcc and clang suffers. Both hosts with CURRENT I have an access to has this problem. The most clean way to reproduce the error (for me) is to reload (sometimes once or twice, sometimes more, but not more than a dozen) current and latest builds at my local tinderbox. Firefox (I use FF4) reloads the page (it's seen since time counter is updated) shows X with red foreground instead of a reload sign at the very end of an URL window. The next symptom is using gsasl within emacs (gnus). Sometimes communication between gnus and an imap server stops. The only way to resume operations is to do killall gsasl. BTW, a gsasl process is at a select state. Sometimes gnus displays something like garbage received, enter RET to continue. I never managed to reproduce the bug by a script (i.e. fetching the problem URL 100 times succeeds). And I'm not sure how to diagnose the case further. Any suggestions? Thanks! -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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
firefox4+html5
Hi, list! I do not know in what part of forum to write, so I decide write in General. I'm trying to use html5 on youtube.com. I getting the video stream, but audio stutters on most of video files . I tried to use the chrome-browser and he is works fine. Also, I tried boot from usb flash drive with installed ubuntu and firefox 4 and this works. So, I believe what trouble is in my FreeBSD. [QUOTE] uname -a FreeBSD laptop 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r221296M: Sun May 1 20:13:15 EEST 2011 larin@laptop:/usr/obj/usr/src/sys/GENERIC amd64 [/QUOTE] My box is: Laptop asus UL30A, 3 GB ram, Intel CPU U2300 1.2Mhz. Thanks in advance. ___ 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: firefox4+html5
Dear Vitaly, I'm usually not using FreeBSD for accessing youtube, but as you're using FreeBSD 9.0-current, please note that this presumably has Witness enabled (because FreeBSD 9.0-current is still development branch), which will reduce performance and hence might give the problems you described. from http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-options.html options WITNESS: this option enables run-time lock order tracking and verification, and is an invaluable tool for deadlock diagnosis. WITNESS maintains a graph of acquired lock orders by lock type, and checks the graph at each acquire for cycles (implicit or explicit). If a cycle is detected, a warning and stack trace are generated to the console, indicating that a potential deadlock might have occurred. WITNESS is required in order to use the show locks, show witness and show alllocks DDB commands. This debug option has significant performance overhead, which may be somewhat mitigated through the use of options WITNESS_SKIPSPIN. Detailed documentation may be found in witness(4). = http://www.freebsd.org/cgi/man.cgi?query=witnesssektion=4 Best regards, Holger From: owner-freebsd-curr...@freebsd.org [owner-freebsd-curr...@freebsd.org] on behalf of Vitaly Liaschuk [lari...@gmail.com] Sent: 03 May 2011 16:49 To: FreeBSD current mailing list Subject: firefox4+html5 Hi, list! I do not know in what part of forum to write, so I decide write in General. I'm trying to use html5 on youtube.com. I getting the video stream, but audio stutters on most of video files . I tried to use the chrome-browser and he is works fine. Also, I tried boot from usb flash drive with installed ubuntu and firefox 4 and this works. So, I believe what trouble is in my FreeBSD. [QUOTE] uname -a FreeBSD laptop 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r221296M: Sun May 1 20:13:15 EEST 2011 larin@laptop:/usr/obj/usr/src/sys/GENERIC amd64 [/QUOTE] My box is: Laptop asus UL30A, 3 GB ram, Intel CPU U2300 1.2Mhz. Thanks in advance. ___ 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 -- Holger Kipp Diplom-Mathematiker Senior Consultant Tel. : +49 30 436 58 114 Fax. : +49 30 436 58 214 Mobil: +49 178 36 58 114 Email: holger.k...@alogis.com alogis AG Alt-Moabit 90b D-10559 Berlin web : http://www.alogis.com -- alogis AG Sitz/Registergericht: Berlin/AG Charlottenburg, HRB 71484 Vorstand: Arne Friedrichs, Joern Samuelson Aufsichtsratsvorsitzender: Reinhard Mielke ___ 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: firefox4+html5
Hi all, I'm currently running FreeBSD 8.1 (latest update) and I'm experiencing a similar issue. HTML5 videos are very laggy (both image and sound) with Firefox 4. I ended up installing the flash player to watch youtube streaming. I didn't spot any particular warning/error messages so I don't know where to start... Thanks! 2011/5/3 Vitaly Liaschuk lari...@gmail.com Hi, list! I do not know in what part of forum to write, so I decide write in General. I'm trying to use html5 on youtube.com. I getting the video stream, but audio stutters on most of video files . I tried to use the chrome-browser and he is works fine. Also, I tried boot from usb flash drive with installed ubuntu and firefox 4 and this works. So, I believe what trouble is in my FreeBSD. [QUOTE] uname -a FreeBSD laptop 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r221296M: Sun May 1 20:13:15 EEST 2011 larin@laptop:/usr/obj/usr/src/sys/GENERIC amd64 [/QUOTE] My box is: Laptop asus UL30A, 3 GB ram, Intel CPU U2300 1.2Mhz. Thanks in advance. ___ 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: Totally confused with the /usrsrc/UPDATING for 20110424 CAM-based ATA stack
Hi, On Mon, May 2, 2011 at 8:28 PM, eculp ec...@encontacto.net wrote: With this confusion I need someone to give me an idea on renumbering. I have two disks on this old machine that I have keep current sin FreeBSD 6 IIRC as preparation for all the new goodies but this really bit me in the morning with a generic kernel and had a heck of a time getting it up. I have a new kernel with the new options. options ATA_CAM device ahci device mvs device siis I've got the following in my stripped down GENERIC: # ATA controllers device ahci# AHCI-compatible SATA controllers device ata # Legacy ATA/SATA controllers options ATA_CAM # Handle legacy controllers with CAM # ATA/SCSI peripherals device scbus # SCSI bus (required for ATA/SCSI) device da # Direct Access (disks) device pass# Passthrough device (direct ATA/SCSI access) I'm able to boot from CF on a couple of different machine. It would seem that without: device ata # Legacy ATA/SATA controllers the disk is not detected. With, the disk shows up as: ada0 at ata3 bus 0 scbus1 target 0 lun 0 ada0: 20070709 ATA-0 device ada0: 16.700MB/s transfers (WDMA2, PIO 512bytes) ada0: 967MB (1981728 512 byte sectors: 16H 63S/T 1966C) ada0: Previously was known as ad0 and I did not need any /etc/fstab modification. my .2 credits, - Arnaud This morning was such a shock that I am tempted to go back to the old kernel config that I understand still works but gonna try to bite the bullit. My fstab that I assume is still necessary is: /dev/ad4s1b none swap sw 0 0 /dev/ad4s1a / ufs rw 1 1 /dev/ad4s2g /backup ufs rw 2 2 /dev/ad4s1g /home ufs rw 2 2 /dev/ad4s2f /release ufs rw 2 2 /dev/ad4s2d /tmp ufs rw 2 2 /dev/ad4s1e /usr ufs rw 2 2 /dev/ad4s1h /usr/local ufs rw 2 2 /dev/ad4s1f /var ufs rw 2 2 /dev/ad4s2e /var/tmp ufs rw 2 2 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /dev/acd1 /cdrom1 cd9660 ro,noauto 0 0 /dev/cd0 /cdrom cd9660 ro,noauto 0 0 /dev/cd1 /cdrom cd9660 ro,noauto 0 0 # /dev/ad0s1a /new ufs rw 1 1 /dev/ad0s1g /new/home ufs rw 2 2 /dev/ad0s1d /new/tmp ufs rw 2 2 /dev/ad0s1e /new/usr ufs rw 2 2 /dev/ada01h /new/usr/local ufs rw 2 2 /dev/ada01f /new/var ufs rw 2 2 I am totally confused on how these should now be. Any help appreciated. ed ___ 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: A replacement for GEOM_LABEL's gpt/gptid
Hi Andrey, just want to say you don't have to wait for me anymore. Just can't find the time to analyze your aproach. Thanks for your work on this. 2011/5/3 Andriy Gapon a...@freebsd.org: on 29/04/2011 19:55 Andrey V. Elsukov said the following: On 27.04.2011 11:37, Andrey V. Elsukov wrote: I wrote a small extension for the GEOM_PART class. It adds an ability to GEOM_PART class to create partition labels for schemes which are support them. Hi All, i got several successful reports from users, but now i decided to make this functional available for another consumers. New patch: http://people.freebsd.org/~ae/geom_alias.diff I really like your approach. One question - is it somehow possible to make the alias geom even more transparent? I mean completely eliminating g_alias_start() or making it more noop-ish. Thank you! What it contains: * gpt/gptid support removed from GEOM_LABEL class; * new GEOM_ALIAS class added. This class has two public functions: void g_alias_create(struct g_provider *pp, const char *name); void g_alias_spoil(struct g_provider *pp); * first two consumers of GEOM_ALIAS class are GEOM_PART and GEOM_DISK: GEOM_DISK uses g_alias_create() to create aliases for disks, disk's serial number is used for alias name. GEOM_PART uses g_alias_create() to create aliases for labeled partitions (gpt/gptid, apm and pc98). How it looks like: http://paste.org.ru/?5exeve -- Andriy Gapon ___ freebsd-g...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-geom To unsubscribe, send any mail to freebsd-geom-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: I am very confused and would appreciate some help on device renameing or on renumbering on current fstab.
On Tue, May 3, 2011 at 8:54 AM, Daniel Nebdal dneb...@gmail.com wrote: Thanks, John. I was afraid that was the answer. Now, II'm really confused. I'm guessing that the partitions will notl need to be shown in fstab (ada0s1a). What little mind I have left is a blank, /dev/ad4s1g will be automatically be detected. Is that correct? What will I do with my second disk /dev/ad0s1a that is already zero? I apologize but I have really confused myself. I've filled my glass with too much water and I'm drowning. Thanks for everyone's patience. ed P.S. If I am not the only idiot, maybe a couple of lines as an example could go into UPDATING. If I have understood ada correct, the first disk (lowest current number) is ada0, the next ada1, and so on. If you have ad0 and ad4, they will be ad0=ada0, and ad4=ada1 . It doesn't affect anything _except_ the disk names, so ad4s1f = ada1s1f and so on. You'll have to change most of your fstab, basically s/ad0/ada0/g and s/ad4/ada1/g . That said, my one ad to ada transition was on a ZFS-only system, which took the fstab editing out of it. I might be horribly wrong in some or all of the above. Thanks, Daniel. Your explanation makes sense to me and to eleminate problems with ad0, it is an old disk, that I will bring up later and just change ad4 to ada0 and ad4s1g to ada0s1g, etc. and reboot it again early tomorrow morning about 5 am CDT and will post a working fstab, if I manage to get it to work. Thanks again, ed -- Daniel Nebdal ___ 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: firefox4+html5
On 05/03/11 19:19, Francois Gerodez wrote: Hi all, I'm currently running FreeBSD 8.1 (latest update) and I'm experiencing a similar issue. HTML5 videos are very laggy (both image and sound) with Firefox 4. I ended up installing the flash player to watch youtube streaming. I didn't spot any particular warning/error messages so I don't know where to start... I have these symptoms too, but usually if I pause the video, send it back to the start with the slider and finally start playing it goes smoothly usually. This is quite strange, I know. Perhaps someone else should check if this is the same for everyone or just something that is happening to me. -- Guido Falsi m...@madpilot.net ___ 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: I am very confused and would appreciate some help on device renameing or on renumbering on current fstab.
On Tue, May 3, 2011 at 9:02 AM, John Baldwin j...@freebsd.org wrote: On Tuesday, May 03, 2011 8:51:02 am Edwin L. Culp W. wrote: On Tue, May 3, 2011 at 6:59 AM, John Baldwin j...@freebsd.org wrote: On Tuesday, May 03, 2011 7:16:34 am Edwin L. Culp W. wrote: I have two disks on this old machine that I have keep current sin FreeBSD 6 IIRC as preparation for all the new goodies but this really bit me in the morning with a generic kernel and had a heck of a time getting it up. I have a new kernel with the new options. options ATA_CAM device ahci device mvs device siis This morning was such a shock that I am tempted to go back to the old kernel config that I understand still works but gonna try to bite the bullit. My fstab that I assume is still needed, is as before, although I had changed ad4xx to ada4xx (etc) that I found was incorrect the HARD way after trying to reboot; /dev/ad4s1b none swap sw 0 0 /dev/ad4s1a / ufs rw 1 1 /dev/ad4s2g /backup ufs rw 2 2 /dev/ad4s1g /home ufs rw 2 2 /dev/ad4s2f /release ufs rw 2 2 /dev/ad4s2d /tmp ufs rw 2 2 /dev/ad4s1e /usr ufs rw 2 2 /dev/ad4s1h /usr/local ufs rw 2 2 /dev/ad4s1f /var ufs rw 2 2 /dev/ad4s2e /var/tmp ufs rw 2 2 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /dev/acd1 /cdrom1 cd9660 ro,noauto 0 0 /dev/cd0 /cdrom cd9660 ro,noauto 0 0 /dev/cd1 /cdrom cd9660 ro,noauto 0 0 # /dev/ad0s1a /new ufs rw 1 1 /dev/ad0s1g /new/home ufs rw 2 2 /dev/ad0s1d /new/tmp ufs rw 2 2 /dev/ad0s1e /new/usr ufs rw 2 2 /dev/ad0s1h /new/usr/local ufs rw 2 2 /dev/ad0s1f /new/var ufs rw 2 2 I am totally confused on how these should now be. Any and all help appreciated. It will be ada0 rather than ad4. With adaX the weird ATA_STATIC_ID stuff is gone and ATA disks are now numbered starting from 0 just like SCSI disks use da0, da1, ... etc. -- John Baldwin Thanks, John. I was afraid that was the answer. Now, II'm really confused. I'm guessing that the partitions will notl need to be shown in fstab (ada0s1a). What little mind I have left is a blank, /dev/ad4s1g will be automatically be detected. Is that correct? What will I do with my second disk /dev/ad0s1a that is already zero? I apologize but I have really confused myself. I've filled my glass with too much water and I'm drowning. Thanks for everyone's patience. ed P.S. If I am not the only idiot, maybe a couple of lines as an example could go into UPDATING. Oh, I missed that you had an ad0. Most likely ad0 will become ada0, and ad4 will become ada1. All the partitions will still exist, so ad0s1a will become ada0s1a and ad4s1a will become ada1s1a. There is a chance that ad0 will become ada1 and ad4 will become ada1 instead. That depends on how your PCI devices are laid out on the PCI bus. I can't answer that without seeing a dmesg though. Do you have mav's latest changes? They should provide aliases for the old names along with printfs to let you know what the new names are for each old disk I think. -- John Baldwin Thanks, John. I apologize for being so thick on this but since I screwed it up the first time, but It took a few extra minutes to get it up and make me a bit nervous. Need it for dns and a few other things, . I cvsup current, build and install a new world and kernel every morning so I assume that I should have mav's latest changes. I'll try it again in the morning with the new build, correct kernel config and fstab entry.. I'll report the results on this thread then. Thanks for you help. ed ___ 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: I am very confused and would appreciate some help on device renameing or on renumbering on current fstab.
Hi, On Tue, May 3, 2011 at 7:16 AM, Edwin L. Culp W. edwinlc...@gmail.com wrote: ... thanks a lot to have posted the same message, twice, under different subject... - Arnaud ___ 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: Totally confused with the /usrsrc/UPDATING for 20110424 CAM-based ATA stack
On Tue, May 3, 2011 at 12:56 PM, Arnaud Lacombe lacom...@gmail.com wrote: Hi, On Mon, May 2, 2011 at 8:28 PM, eculp ec...@encontacto.net wrote: With this confusion I need someone to give me an idea on renumbering. I have two disks on this old machine that I have keep current sin FreeBSD 6 IIRC as preparation for all the new goodies but this really bit me in the morning with a generic kernel and had a heck of a time getting it up. I have a new kernel with the new options. options ATA_CAM device ahci device mvs device siis I've got the following in my stripped down GENERIC: # ATA controllers device ahci # AHCI-compatible SATA controllers device ata # Legacy ATA/SATA controllers options ATA_CAM # Handle legacy controllers with CAM # ATA/SCSI peripherals device scbus # SCSI bus (required for ATA/SCSI) device da # Direct Access (disks) device pass # Passthrough device (direct ATA/SCSI access) I'm able to boot from CF on a couple of different machine. It would seem that without: device ata # Legacy ATA/SATA controllers the disk is not detected. With, the disk shows up as: ada0 at ata3 bus 0 scbus1 target 0 lun 0 ada0: 20070709 ATA-0 device ada0: 16.700MB/s transfers (WDMA2, PIO 512bytes) ada0: 967MB (1981728 512 byte sectors: 16H 63S/T 1966C) ada0: Previously was known as ad0 and I did not need any /etc/fstab modification. my .2 credits, - Arnaud Thanks Arnaud, Again I apologize of having posted this problem twice but as I mentioned on the previous thread the machine in question is dns and my screwing with it to get it up and runing having a bad fstab. I wrote this email before checking and I thought it was lost. Tomorrow morning I'll get to the bottom of my misunderstanding and hopefully be able to help make this a bit more clear for others who haven't taken the jump yet. ed This morning was such a shock that I am tempted to go back to the old kernel config that I understand still works but gonna try to bite the bullit. My fstab that I assume is still necessary is: /dev/ad4s1b none swap sw 0 0 /dev/ad4s1a / ufs rw 1 1 /dev/ad4s2g /backup ufs rw 2 2 /dev/ad4s1g /home ufs rw 2 2 /dev/ad4s2f /release ufs rw 2 2 /dev/ad4s2d /tmp ufs rw 2 2 /dev/ad4s1e /usr ufs rw 2 2 /dev/ad4s1h /usr/local ufs rw 2 2 /dev/ad4s1f /var ufs rw 2 2 /dev/ad4s2e /var/tmp ufs rw 2 2 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /dev/acd1 /cdrom1 cd9660 ro,noauto 0 0 /dev/cd0 /cdrom cd9660 ro,noauto 0 0 /dev/cd1 /cdrom cd9660 ro,noauto 0 0 # /dev/ad0s1a /new ufs rw 1 1 /dev/ad0s1g /new/home ufs rw 2 2 /dev/ad0s1d /new/tmp ufs rw 2 2 /dev/ad0s1e /new/usr ufs rw 2 2 /dev/ada01h /new/usr/local ufs rw 2 2 /dev/ada01f /new/var ufs rw 2 2 I am totally confused on how these should now be. Any help appreciated. ed ___ 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 ___ 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: Building FreeBSD 9.0-CUR/amd64 with CLANG fails
2011/5/3 O. Hartmann ohart...@mail.zedat.fu-berlin.de:
On 05/02/11 14:19, Olivier Smedts wrote:
2011/5/1 O. Hartmannohart...@mail.zedat.fu-berlin.de:
Well,
I tried the first time building FreeBSD 9.0-CURRENT/amd64 (sources from
today's latest svn) and it failed (taken the /etc/make.conf addition from
the wiki), giving the below showed error.
Did you follow the instructions on the wiki ? Do you have the
following lines in your /etc/make.conf ?
NO_WERROR=
WERROR=
Is this a well known issue and FreeBSD isn't building correctly at the
moment or did I miss something (not mentioned on the wiki's page)?
Today, I tried again, after CLANG/LLVM has been updated to version 3.0.
Same error.
This is the addendum I made to the /etc/make.conf:
##
## CLANG
##
.if defined(USE_CLANG)
Why do you have the previous line ? Can you try without it and the last endif ?
.if !defined(CC) || ${CC} == cc
CC=clang
.endif
.if !defined(CXX) || ${CXX} == c++
CXX=clang++
.endif
# Don't die on warnings
NO_WERROR=
WERROR=
# Don't forget this when using Jails!
NO_FSCHG=
.endif
I think I should file a PR ...
oliver
--
Olivier Smedts _
ASCII ribbon campaign ( )
e-mail: oliv...@gid0.org - against HTML email vCards X
www: http://www.gid0.org - against proprietary attachments / \
Il y a seulement 10 sortes de gens dans le monde :
ceux qui comprennent le binaire,
et ceux qui ne le comprennent pas.
___
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: Building FreeBSD 9.0-CUR/amd64 with CLANG fails
On 05/02/11 14:19, Olivier Smedts wrote: 2011/5/1 O. Hartmannohart...@mail.zedat.fu-berlin.de: Well, I tried the first time building FreeBSD 9.0-CURRENT/amd64 (sources from today's latest svn) and it failed (taken the /etc/make.conf addition from the wiki), giving the below showed error. Did you follow the instructions on the wiki ? Do you have the following lines in your /etc/make.conf ? NO_WERROR= WERROR= Is this a well known issue and FreeBSD isn't building correctly at the moment or did I miss something (not mentioned on the wiki's page)? clang: warning: argument unused during compilation: '-finhibit-size-directive' clang: warning: argument unused during compilation: '-fno-toplevel-reorder' sh /usr/src/tools/install.sh -o root -g wheel -m 444 �crtbegin.o /usr/obj/usr/src/lib32/usr/lib32/crtbegin.o sh /usr/src/tools/install.sh -o root -g wheel -m 444 �crtend.o /usr/obj/usr/src/lib32/usr/lib32/crtend.o sh /usr/src/tools/install.sh -o root -g wheel -m 444 �crtbeginT.o /usr/obj/usr/src/lib32/usr/lib32/crtbeginT.o sh /usr/src/tools/install.sh -o root -g wheel -m 444 �crtbegin.So /usr/obj/usr/src/lib32/usr/lib32/crtbeginS.o sh /usr/src/tools/install.sh -o root -g wheel -m 444 �crtend.So /usr/obj/usr/src/lib32/usr/lib32/crtendS.o === lib/csu/i386-elf (obj,depend,all,install) rm -f .depend CC='clang' mkdep -f .depend -a � �-I/usr/src/lib/csu/i386-elf/../common -I/usr/src/lib/csu/i386-elf/../../libc/include /usr/src/lib/csu/i386-elf/crti.S /usr/src/lib/csu/i386-elf/crtn.S clang -O2 -pipe -I/usr/src/lib/csu/i386-elf/../common -I/usr/src/lib/csu/i386-elf/../../libc/include -std=gnu99 -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign �-c /usr/src/lib/csu/i386-elf/crti.S clang -O2 -pipe -I/usr/src/lib/csu/i386-elf/../common -I/usr/src/lib/csu/i386-elf/../../libc/include -std=gnu99 -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign �-c /usr/src/lib/csu/i386-elf/crtn.S clang -O2 -pipe -I/usr/src/lib/csu/i386-elf/../common -I/usr/src/lib/csu/i386-elf/../../libc/include -std=gnu99 -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -DGCRT -S -o gcrt1_c.s /usr/src/lib/csu/i386-elf/crt1_c.c sed -i -e '/\.note\.ABI-tag/s/progbits/note/' gcrt1_c.s clang -O2 -pipe -I/usr/src/lib/csu/i386-elf/../common -I/usr/src/lib/csu/i386-elf/../../libc/include -std=gnu99 -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -c -o gcrt1_c.o gcrt1_c.s clang: warning: argument unused during compilation: '-I /usr/src/lib/csu/i386-elf/../common' clang: warning: argument unused during compilation: '-I /usr/src/lib/csu/i386-elf/../../libc/include' clang: warning: argument unused during compilation: '-std=gnu99' clang: warning: argument unused during compilation: '-Wsystem-headers' clang: warning: argument unused during compilation: '-Wall' clang: warning: argument unused during compilation: '-Wno-format-y2k' clang: warning: argument unused during compilation: '-W' clang: warning: argument unused during compilation: '-Wno-unused-parameter' clang: warning: argument unused during compilation: '-Wstrict-prototypes' clang: warning: argument unused during compilation: '-Wmissing-prototypes' clang: warning: argument unused during compilation: '-Wpointer-arith' clang: warning: argument unused during compilation: '-Wreturn-type' clang: warning: argument unused during compilation: '-Wcast-qual' clang: warning: argument unused during compilation: '-Wwrite-strings' clang: warning: argument unused during compilation: '-Wswitch' clang: warning: argument unused during compilation: '-Wshadow' clang: warning: argument unused during compilation: '-Wunused-parameter' clang: warning: argument unused during compilation: '-Wcast-align' clang: warning: argument unused during compilation: '-Wchar-subscripts' clang: warning: argument unused during compilation: '-Winline' clang: warning: argument unused during compilation: '-Wnested-externs' clang: warning: argument unused during compilation: '-Wredundant-decls' clang:
Re: Building FreeBSD 9.0-CUR/amd64 with CLANG fails
On 05/03/11 21:13, Olivier Smedts wrote:
2011/5/3 O. Hartmannohart...@mail.zedat.fu-berlin.de:
On 05/02/11 14:19, Olivier Smedts wrote:
2011/5/1 O. Hartmannohart...@mail.zedat.fu-berlin.de:
Well,
I tried the first time building FreeBSD 9.0-CURRENT/amd64 (sources from
today's latest svn) and it failed (taken the /etc/make.conf addition from
the wiki), giving the below showed error.
Did you follow the instructions on the wiki ? Do you have the
following lines in your /etc/make.conf ?
NO_WERROR=
WERROR=
Is this a well known issue and FreeBSD isn't building correctly at the
moment or did I miss something (not mentioned on the wiki's page)?
Today, I tried again, after CLANG/LLVM has been updated to version 3.0.
Same error.
This is the addendum I made to the /etc/make.conf:
##
## � � �CLANG
##
.if defined(USE_CLANG)
Why do you have the previous line ? Can you try without it and the last endif ?
Setting USE_CLANG=yes at the beginning of /etc/make.conf avoids
commenting out or uncommenting the CLANG-stuff.
I'll try.
.if !defined(CC) || ${CC} == cc
CC=clang
.endif
.if !defined(CXX) || ${CXX} == c++
CXX=clang++
.endif
# Don't die on warnings
NO_WERROR=
WERROR=
# Don't forget this when using Jails!
NO_FSCHG=
.endif
I think I should file a PR ...
oliver
___
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: problems with em(4) since update to driver 7.2.2
If you get the setup receive structures fail, then increase the nmbclusters. If you use standard MTU then what you need are mbufs, and standard size clusters (2K). Only when you use jumbo frames will you need larger. You must configure enough, its that simple. Jack On Tue, May 3, 2011 at 2:13 PM, Michael Schmiedgen schmied...@gmx.netwrote: Hi, I have the very same problem. - GENERIC 9.0-CURRENT (April 28) - em0 PRO/1000 7.2.3 - em0: Could not setup receive structures On 03.05.2011 10:58, Olivier Smedts wrote: I tried increasing kern.ipc.nmbjumbo* (is it what you suggested ?). Values doubled : kern.ipc.nmbjumbo16: 6400 kern.ipc.nmbjumbo9: 12800 kern.ipc.nmbjumbop: 25600 And unloaded / reloaded the kernel module. Still no luck, same problem, on latest 9-CURRENT (r221363). Same here. If I should provide some more configuration settings, please let me know. Michael ___ 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
firewire debugging
does anyone know if there is a limitation on firewire debugging on a
machine with 4GB or memory?
I have 1394 {a,b} cards. does it make a difference?
also, the firewire card on one machine stops it from booting..
is there a way to disable it during boot other than recompiling the
kernel without firewire?
___
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: problems with em(4) since update to driver 7.2.2
Hi, I have the very same problem. - GENERIC 9.0-CURRENT (April 28) - em0 PRO/1000 7.2.3 - em0: Could not setup receive structures On 03.05.2011 10:58, Olivier Smedts wrote: I tried increasing kern.ipc.nmbjumbo* (is it what you suggested ?). Values doubled : kern.ipc.nmbjumbo16: 6400 kern.ipc.nmbjumbo9: 12800 kern.ipc.nmbjumbop: 25600 And unloaded / reloaded the kernel module. Still no luck, same problem, on latest 9-CURRENT (r221363). Same here. If I should provide some more configuration settings, please let me know. Michael ___ 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: problems with em(4) since update to driver 7.2.2
On 03.05.2011 23:24, Jack Vogel wrote: If you get the setup receive structures fail, then increase the nmbclusters. If you use standard MTU then what you need are mbufs, and standard size clusters (2K). Only when you use jumbo frames will you need larger. You must configure enough, its that simple. I doubled the nmbclusters as well. But nothing happened. I have no load on this machine and nothing special configured. Thanks, Michael ___ 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: problems with em(4) since update to driver 7.2.2
It has nothing to do with load, it has to do with the prerequisites to init your interfaces. The amount you need is fixed, it doesn't vary with load. Every RX descriptor needs one, so its simple math, number-of-interfaces X number-of-queues X size of the ring. If you have other network interfaces beside Intel they also consume mbufs remember. Jack On Tue, May 3, 2011 at 2:50 PM, Michael Schmiedgen schmied...@gmx.netwrote: On 03.05.2011 23:24, Jack Vogel wrote: If you get the setup receive structures fail, then increase the nmbclusters. If you use standard MTU then what you need are mbufs, and standard size clusters (2K). Only when you use jumbo frames will you need larger. You must configure enough, its that simple. I doubled the nmbclusters as well. But nothing happened. I have no load on this machine and nothing special configured. Thanks, Michael ___ 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: problems with em(4) since update to driver 7.2.2
2011/5/4 Arnaud Lacombe lacom...@gmail.com: A more rude version might be Why the frak my network adapter stopped working with the default setting ? :) ...on a -STABLE branch -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org - against HTML email vCards X www: http://www.gid0.org - against proprietary attachments / \ Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas. ___ 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: problems with em(4) since update to driver 7.2.2
Hi Jack, On Tue, May 3, 2011 at 6:00 PM, Jack Vogel jfvo...@gmail.com wrote: It has nothing to do with load, it has to do with the prerequisites to init your interfaces. The amount you need is fixed, it doesn't vary with load. Every RX descriptor needs one, so its simple math, number-of-interfaces X number-of-queues X size of the ring. I guess the question is more: why would I need N*M (M 1) nmbclusters with driver version X when driver version X-1 worked perfectly fine, from my daily-average-user point of view, with N nmbclusters ? A more rude version might be Why the frak my network adapter stopped working with the default setting ? :) - Arnaud If you have other network interfaces beside Intel they also consume mbufs remember. Jack On Tue, May 3, 2011 at 2:50 PM, Michael Schmiedgen schmied...@gmx.netwrote: On 03.05.2011 23:24, Jack Vogel wrote: If you get the setup receive structures fail, then increase the nmbclusters. If you use standard MTU then what you need are mbufs, and standard size clusters (2K). Only when you use jumbo frames will you need larger. You must configure enough, its that simple. I doubled the nmbclusters as well. But nothing happened. I have no load on this machine and nothing special configured. Thanks, Michael ___ 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: cardbus memory allocation problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have WIP patches to fix this but they aren't ready yet. pcib4: I/O decode0x4000-0x4fff pcib4: memory decode 0xf090-0xf09f *** this memory widow is what I expected all children to allocate from pcib4: no prefetched decode pcib4: Subtractively decoded bridge. It's a subtractive bridge, so the resources do not have to be allocated from the window. That said, I'm committing the last of my patches to HEAD today to rework how PCI-PCI bridges handle I/O windows to support growing windows, etc. and the new PCI-PCI bridge driver will attempt to grow the memory window to allocate a new range before falling back to depending on the subtractive decode. You might be pleased to hear that, without any special arrangements in loader.conf, the new PCI-PCI code does The Right Thing with memory allocation :-) Parent bridge: I fixed the subordinate bus using setpci -s 07:06.2 4c.b=02 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2) (prog-if 01 [Subtractive decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=07, subordinate=09, sec-latency=64 I/O behind bridge: 4000-4fff Memory behind bridge: f090-f09f Cardbus bridge: 07:06.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller Subsystem: Toshiba America Info Systems Device ff10 Flags: bus master, medium devsel, latency 64, IRQ 18 Memory at f0907000 (32-bit, non-prefetchable) Bus: primary=07, secondary=08, subordinate=09, sec-latency=32 16-bit legacy interface ports at 0001 [ .. snip .. ] Cardbus inserted .. 08:00.0 Ethernet controller: Atheros Communications Inc. Atheros AR5001X+ Wireless Network Adapter (rev 01) Subsystem: Netgear WG511T 108 Mbps Wireless PC Card (rev.A/B) Flags: medium devsel, IRQ 18 Memory at f091 (32-bit, non-prefetchable) Capabilities: [44] Power Management version 2 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk3AlIkACgkQQv9rrgRC1JKC1ACcDVsXXN/4NrR9y707OkCMaBAm NmEAoKJfwjaP0+92LKDYI9FRDULy8gPx =m/J6 -END PGP SIGNATURE- ___ 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: cardbus memory allocation problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/03/11 19:49, I wrote: Parent bridge: I fixed the subordinate bus using setpci -s 07:06.2 4c.b=02 Correction: this should be pciconf -wb pci0:0:30:0 0x1a 9 imb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk3ApU4ACgkQQv9rrgRC1JKDTwCgyv7JAXZgsI459vCaFOCsYlwe 8x4AnAyeMAS2c23xglr29BdYQNXftlyW =NB2b -END PGP SIGNATURE- ___ 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
Clang error make buildworld
I get this error when trying to buildworld on current i386. It's been this way for awhile Any Ideas ? === boot/i386/boot0 (all) clang -O2 -pipe -DVOLUME_SERIAL -DPXE -DFLAGS=0x8f -DTICKS=0xb6 -DCOMSPEED=7 5 + 3 -ffreestanding -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -std=gnu99-c /usr/src/sys/boot/i386/boot0/boot0.S clang: warning: argument unused during compilation: '-mpreferred-stack-boundary=2' /tmp/cc-4SXZt8.s:42:11: error: .code16 not supported yet .code16 # This runs in real mode ^ /tmp/cc-4SXZt8.s:313:3: error: unknown use of instruction mnemonic without a size suffix jmp *%bx # Invoke bootstrap ^ /tmp/cc-4SXZt8.s:346:3: error: invalid operand for instruction retw # To caller ^ /tmp/cc-4SXZt8.s:372:3: error: invalid operand for instruction retw # To caller ^ *** Error code 1 Stop in /usr/src/sys/boot/i386/boot0. *** Error code 1 Stop in /usr/src/sys/boot/i386. *** Error code 1 Stop in /usr/src/sys/boot. *** Error code 1 Stop in /usr/src/sys. Thanks Manfred || n...@pozo.com || || Ph. (415) 681-6235 || -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ 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
Fwd: svn commit: r221418 - head/sys/net80211
This has the potential to subtly break things, so I'd appreciate it if
users of wireless devices would please test this out and let me know
if it breaks anything.
Thanks,
Adrian
-- Forwarded message --
From: Adrian Chadd adr...@freebsd.org
Date: 4 May 2011 10:23
Subject: svn commit: r221418 - head/sys/net80211
To: src-committ...@freebsd.org, svn-src-...@freebsd.org,
svn-src-h...@freebsd.org
Author: adrian
Date: Wed May 4 02:23:59 2011
New Revision: 221418
URL: http://svn.freebsd.org/changeset/base/221418
Log:
Fix some corner cases in the net80211 sequence number retransmission
handling.
The current sequence number code does a few things incorrectly:
* It didn't try eliminating duplications from HT nodes. I guess it's assumed
that out of order / retransmission handling would be handled by the AMPDU RX
routines. If a HT node isn't doing AMPDU RX, then retransmissions need to
be eliminated. Since most of my debugging is based on this (as AMPDU TX
software packet aggregation isn't yet handled), handle this corner case.
* When a sequence number of 4095 was received, any subsequent sequence number
is going to be (by definition) less than 4095. So if the following sequence
number (0) doesn't initially occur and the retransmit is received, it's
incorrectly eliminated by the IEEE80211_FC1_RETRY SEQ_LEQ() check.
Try to handle this better.
This almost completely eliminates out of order TCP statistics showing up during
iperf testing for the 11a, 11g and non-aggregate 11n AMPDU RX case. The only
other packet loss conditions leading to this are due to baseband resets or
heavy interference.
Modified:
head/sys/net80211/ieee80211_adhoc.c
head/sys/net80211/ieee80211_hostap.c
head/sys/net80211/ieee80211_input.h
head/sys/net80211/ieee80211_mesh.c
head/sys/net80211/ieee80211_sta.c
head/sys/net80211/ieee80211_wds.c
Modified: head/sys/net80211/ieee80211_adhoc.c
==
--- head/sys/net80211/ieee80211_adhoc.c Wed May 4 01:39:44 2011
(r221417)
+++ head/sys/net80211/ieee80211_adhoc.c Wed May 4 02:23:59 2011
(r221418)
@@ -285,7 +285,6 @@ doprint(struct ieee80211vap *vap, int su
static int
adhoc_input(struct ieee80211_node *ni, struct mbuf *m, int rssi, int nf)
{
-#define SEQ_LEQ(a,b) ((int)((a)-(b)) = 0)
#define HAS_SEQ(type) ((type 0x4) == 0)
struct ieee80211vap *vap = ni-ni_vap;
struct ieee80211com *ic = ni-ni_ic;
@@ -412,9 +411,7 @@ adhoc_input(struct ieee80211_node *ni, s
TID_TO_WME_AC(tid) = WME_AC_VI)
ic-ic_wme.wme_hipri_traffic++;
rxseq = le16toh(*(uint16_t *)wh-i_seq);
- if ((ni-ni_flags IEEE80211_NODE_HT) == 0
- (wh-i_fc[1] IEEE80211_FC1_RETRY)
- SEQ_LEQ(rxseq, ni-ni_rxseqs[tid])) {
+ if (! ieee80211_check_rxseq(ni, wh)) {
/* duplicate, discard */
IEEE80211_DISCARD_MAC(vap, IEEE80211_MSG_INPUT,
bssid, duplicate,
@@ -660,7 +657,6 @@ out:
m_freem(m);
}
return type;
-#undef SEQ_LEQ
}
static int
Modified: head/sys/net80211/ieee80211_hostap.c
==
--- head/sys/net80211/ieee80211_hostap.c Wed May 4 01:39:44
2011 (r221417)
+++ head/sys/net80211/ieee80211_hostap.c Wed May 4 02:23:59
2011 (r221418)
@@ -472,7 +472,6 @@ doprint(struct ieee80211vap *vap, int su
static int
hostap_input(struct ieee80211_node *ni, struct mbuf *m, int rssi, int nf)
{
-#define SEQ_LEQ(a,b) ((int)((a)-(b)) = 0)
#define HAS_SEQ(type) ((type 0x4) == 0)
struct ieee80211vap *vap = ni-ni_vap;
struct ieee80211com *ic = ni-ni_ic;
@@ -572,9 +571,7 @@ hostap_input(struct ieee80211_node *ni,
TID_TO_WME_AC(tid) = WME_AC_VI)
ic-ic_wme.wme_hipri_traffic++;
rxseq = le16toh(*(uint16_t *)wh-i_seq);
- if ((ni-ni_flags IEEE80211_NODE_HT) == 0
- (wh-i_fc[1] IEEE80211_FC1_RETRY)
- SEQ_LEQ(rxseq, ni-ni_rxseqs[tid])) {
+ if (! ieee80211_check_rxseq(ni, wh)) {
/* duplicate, discard */
IEEE80211_DISCARD_MAC(vap, IEEE80211_MSG_INPUT,
bssid, duplicate,
@@ -914,7 +911,6 @@ out:
m_freem(m);
}
return type;
-#undef SEQ_LEQ
}
static void
Modified: head/sys/net80211/ieee80211_input.h
==
--- head/sys/net80211/ieee80211_input.h Wed May 4 01:39:44 2011
(r221417)
+++
Re: I am very confused and would appreciate some help on device renameing or on renumbering on current fstab.
Edwin, /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /dev/acd1 /cdrom1 cd9660 ro,noauto 0 0 As a side note. These are also now useless can be sent to /dev/null for extra padding ;) Shouldn't cause no harm being there but just for reference. -- Regards, (jhell) Jason Hellenthal pgpB0GwwepyZI.pgp Description: PGP signature
Nasty non-recursive lockmgr panic on softdep only enabled UFS partition when filesystem full
Hi Jeff and Dr. McKusick, Ran into this panic when /usr ran out of space doing a make universe on amd64/r221219 (it took ~15 minutes for the panic to occur after the filesystem ran out of space -- wasn't quite sure what it was doing at the time): pid 24486 (ld), uid 0 inumber 9993 on /usr: filesystem full pid 24511 (config), uid 0 inumber 361082 on /usr: filesystem full pid 24494 (make), uid 0 inumber 1886295 on /usr: filesystem full panic: __lockmgr_args: recursing on non recursive lockmgr bufwait @ /usr/src/sys/ufs/ffs/ffs_softdep.c:11025 (kgdb) #0 doadump () at pcpu.h:224 #1 0x802af22c in db_fncall (dummy1=Variable dummy1 is not available. ) at /usr/src/sys/ddb/db_command.c:548 #2 0x802af561 in db_command (last_cmdp=0x808f93c0, cmd_table=Variable cmd_table is not available. ) at /usr/src/sys/ddb/db_command.c:445 #3 0x802af7a9 in db_command_loop () at /usr/src/sys/ddb/db_command.c:498 #4 0x802b1737 in db_trap (type=Variable type is not available. ) at /usr/src/sys/ddb/db_main.c:229 #5 0x803f7d48 in kdb_trap (type=3, code=0, tf=0xff834e4c8ef0) at /usr/src/sys/kern/subr_kdb.c:533 #6 0x80599da5 in trap (frame=0xff834e4c8ef0) at /usr/src/sys/amd64/amd64/trap.c:590 #7 0x80584ef3 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:228 #8 0x803f7baf in kdb_enter (why=0x806178cf panic, msg=0xa Address 0xa out of bounds) at cpufunc.h:63 #9 0x803c4b6f in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:584 #10 0x803af3ac in __lockmgr_args (lk=0x100, flags=0, ilk=0xfe00b95766c0, wmesg=Variable wmesg is not available. ) at /usr/src/sys/kern/kern_lock.c:720 #11 0x8054240b in softdep_sync_metadata (vp=0xfe017fe5d000) at lockmgr.h:97 #12 0x80548e90 in ffs_syncvnode (vp=0xfe017fe5d000, waitfor=Variable waitfor is not available. ) at /usr/src/sys/ufs/ffs/ffs_vnops.c:331 #13 0x8053be23 in softdep_request_cleanup (fs=0xfe00086ef000, vp=0xfe00b95765a0, cred=Variable cred is not available. ) at /usr/src/sys/ufs/ffs/ffs_softdep.c:11392 #14 0x80523895 in ffs_realloccg (ip=0xfe00b9285bd0, lbprev=0, bprev=10092847, bpref=10723304, osize=2048, nsize=4096, flags=65536, cred=0xfe026e905a00, bpp=0xff834e4c95f0) at /usr/src/sys/ufs/ffs/ffs_alloc.c:423 #15 0x805266de in ffs_balloc_ufs2 (vp=0xfe00b95765a0, startoffset=Variable startoffset is not available. ) at /usr/src/sys/ufs/ffs/ffs_balloc.c:699 #16 0x8054fbfb in ufs_direnter (dvp=0xfe00b95765a0, tvp=0xfe00701c4000, dirp=0xff834e4c97b0, cnp=Variable cnp is not available. ) at /usr/src/sys/ufs/ufs/ufs_lookup.c:910 #17 0x80557af8 in ufs_mkdir (ap=0xff834e4c9a90) at /usr/src/sys/ufs/ufs/ufs_vnops.c:1961 #18 0x805d666b in VOP_MKDIR_APV (vop=0x808c2a40, a=0xff834e4c9a90) at vnode_if.c:1534 #19 0x80457eb8 in kern_mkdirat (td=0xfe0149df4000, fd=-100, path=0x6096e0 Address 0x6096e0 out of bounds, segflg=Variable segflg is not available. ) at vnode_if.h:665 #20 0x80404cd1 in syscallenter (td=0xfe0149df4000, sa=0xff834e4c9bb0) at /usr/src/sys/kern/subr_trap.c:344 #21 0x8059996e in syscall (frame=0xff834e4c9c50) at /usr/src/sys/amd64/amd64/trap.c:910 #22 0x805851bd in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:384 #23 0x000800b3798c in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) $ sudo tunefs -p /usr tunefs: POSIX.1e ACLs: (-a)disabled tunefs: NFSv4 ACLs: (-N) disabled tunefs: MAC multilabel: (-l) disabled tunefs: soft updates: (-n) enabled tunefs: soft update journaling: (-j) disabled tunefs: gjournal: (-J) disabled tunefs: trim: (-t) disabled tunefs: maximum blocks per file in a cylinder group: (-e) 2048 tunefs: average file size: (-f)16384 tunefs: average number of files in a directory: (-s) 64 tunefs: minimum percentage of free space: (-m) 8% tunefs: optimization preference: (-o) time tunefs: volume label: (-L) Let me know what other commands you would like for me to run in kgdb. Thanks, -Garrett ___ 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
