Re: Random Hangs and Freezes
I'll try that, I just wasn't sure if 9.1-RC1 had a repo for pkgng. Tho, I'll upgrade now and let you know if it solves anything. On Fri, 31 Aug 2012 22:01:25 +0100 lokada...@gmx.de wrote: >On 08/31/12 22:09, a...@hush.com wrote: >> >> On Fri, 31 Aug 2012 20:31:13 +0100 lokada...@gmx.de wrote: >>> On 08/31/12 19:04, a...@hush.com wrote: Let me know what information you may need. >>> Which Version of FreeBSD you are running? >> I'm currently running FreeBSD 9.0, I don't recall having this >> issue on 8.2 when I used it. Rather it seems to be a new issue I >> have with >> >> ___ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers- >unsubscr...@freebsd.org" >> >Can you upgrade to 9.1-RC1? ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: [patch] libc: Do not export .cerror
On Sat, Sep 01, 2012 at 12:48:50AM +0200, Jilles Tjoelker wrote: > On Tue, Aug 28, 2012 at 02:03:22PM +0300, Konstantin Belousov wrote: > > On Sat, Aug 25, 2012 at 12:16:55AM +0200, Jilles Tjoelker wrote: > > > Not exporting .cerror causes it to be jumped to directly instead of via > > > the PLT. > > > > The below patch is for i386 only and also takes advantage of .cerror's > > > new status by not saving and loading %ebx before jumping to it. > > > (Therefore, .cerror now saves and loads %ebx itself.) Where there was a > > > conditional jump to a jump to .cerror, the conditional jump has been > > > changed to jump to .cerror directly (many modern CPUs don't do static > > > prediction and in any case it is not much of a benefit anyway). > > > Why do you need to save/restore the %ebx at all ? %ebx == > > &__GLOBAL_OFFSET_TABLE__ is only needed when you access GOT, but .cerror > > only works with PLT, which is addressed using the instruction capable of > > relative addressing. The old .cerror does not need it as well, but it is > > just engraved in the function ABI. > > On i386, a shared object's PLT entry needs %ebx set up to work properly. > This is because such a PLT entry needs to access the GOT to find the > address to jump to (the first instruction is jmp *d32(%ebx)). > > An executable's PLT entry accesses the GOT via absolute addressing and > therefore does not need %ebx. Doh, right. Still, this manipulations can be removed, we just need to resolve __error in some libc ctr. It is not very important after your patch, because ABI is not much more regular, but I think removing additional stack operations is still beneficial. > > > > The patch decreases the size of libc.so.7 by a few kilobytes. > > > > Similar changes could be made to other architectures, and there may be > > > more symbols that are exported but need not be. > > Sure, would you handle at least amd64 too ? > > The below patch handles amd64. > > I'm a bit annoyed that most of the syscall stubs are 17 bytes long now > and have the maximum 15 bytes of padding. This means that the patch > provides virtually no gain in code size. Stubs can be converted to do only load of the syscall number into %rax and unconditional jump to common code which would perform kernel call and do post-syscall bookkeeping to update errno. Otherwise, looks good. pgpYhjmDsmTnD.pgp Description: PGP signature
freebsd.org git repositories and svn ids
There seem to be git repositories available under freebsd.org and mirrors on github. I'm not terribly clear about how official they really are. I'm particularly asking about the freebsd repository, variously at git://git.freebsd.org/freebsd.git and git://github.com/freebsd/freebsd.git . How does one map between svn commit IDs and git IDs with this repository? Most git-svn repositories include a git-svn-id: header at the end of commit messages, but this repository doesn't. The freebsd-head repository at git://github.com/freebsd/freebsd-head.git does have these tags, but is limited in scope. It doesn't have enough history for my needs. As references to commits in mailing lists are most likely to speak of an svn ID, it's a big limitation. There are a couple of other applications where going back and forth between the ID spaces is useful. Suggestions welcome. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: freebsd.org git repositories and svn ids
Hi, On Sat, Sep 1, 2012 at 11:24 AM, Daniel Hagerty wrote: > How does one map between svn commit IDs and git IDs with this > repository? Most git-svn repositories include a git-svn-id: header at > the end of commit messages, but this repository doesn't. The > freebsd-head repository at git://github.com/freebsd/freebsd-head.git > does have these tags, but is limited in scope. It doesn't have enough > history for my needs. I use git://gitorious.org/freebsd/freebsd.git which has stable/releng/release branches and which does include git-svn-id --Artem ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Random Hangs and Freezes
Try grabbing the latest nvidia driver off the nvidia site. Its not really a matter of fixing deadlocks with nvidia, its a matter of finding which driver verion deadlocks on stuff you never use. Deadlocks with nvidia are nearly as bad on Windows too (I get about 2 a day) On Sep 1, 2012 7:54 AM, wrote: > I'll try that, I just wasn't sure if 9.1-RC1 had a repo for > pkgng. Tho, I'll upgrade now and let you know if it solves anything. > > > On Fri, 31 Aug 2012 22:01:25 +0100 lokada...@gmx.de wrote: > >On 08/31/12 22:09, a...@hush.com wrote: > >> > >> On Fri, 31 Aug 2012 20:31:13 +0100 lokada...@gmx.de wrote: > >>> On 08/31/12 19:04, a...@hush.com wrote: > Let me know what information you may need. > >>> Which Version of FreeBSD you are running? > >> I'm currently running FreeBSD 9.0, I don't recall having this > >> issue on 8.2 when I used it. Rather it seems to be a new issue I > >> have with > >> > >> ___ > >> freebsd-hackers@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > >> To unsubscribe, send any mail to "freebsd-hackers- > >unsubscr...@freebsd.org" > >> > >Can you upgrade to 9.1-RC1? > > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org" > ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: freebsd.org git repositories and svn ids
> I use git://gitorious.org/freebsd/freebsd.git which has > stable/releng/release branches and which does include git-svn-id This is what I'm using now, in fact. It lacks the 9.1 releng branch tho; I don't know if this is a bug or feature. More generally tho, I'm curious how one is supposed to use the seemingly more official repositories without this bit of data; I'd expect I must be missing some critical clue. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: freebsd.org git repositories and svn ids
On Sat, Sep 1, 2012 at 4:28 PM, Daniel Hagerty wrote: > > I use git://gitorious.org/freebsd/freebsd.git which has > > stable/releng/release branches and which does include git-svn-id > > This is what I'm using now, in fact. It lacks the 9.1 releng > branch tho; I don't know if this is a bug or feature. > > More generally tho, I'm curious how one is supposed to use the > seemingly more official repositories without this bit of data; I'd > expect I must be missing some critical clue. The last time I looked (which was a while ago), the gitorious (and github? don't remember) repos were seriously out of date. Is the git.freebsd.org repo more or less up-to-date, or is it out of synch? Thanks, -Garrett ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: freebsd.org git repositories and svn ids
On 9/1/2012 7:04 PM, Garrett Cooper wrote: > On Sat, Sep 1, 2012 at 4:28 PM, Daniel Hagerty wrote: >> > I use git://gitorious.org/freebsd/freebsd.git which has >> > stable/releng/release branches and which does include git-svn-id >> >> This is what I'm using now, in fact. It lacks the 9.1 releng >> branch tho; I don't know if this is a bug or feature. >> >> More generally tho, I'm curious how one is supposed to use the >> seemingly more official repositories without this bit of data; I'd >> expect I must be missing some critical clue. > > The last time I looked (which was a while ago), the gitorious (and > github? don't remember) repos were seriously out of date. Is the > git.freebsd.org repo more or less up-to-date, or is it out of synch? > Thanks, > -Garrett uqs@ maintains the git.freebsd.org and github mirrors. You should use those instead of gitorious as they are updated very quickly from SVN. http://wiki.freebsd.org/GitWorkflow >From that article: The official repository-mirrors are updated at least hourly, should they lag the svn repository by more than that, please contact (monitoring still needs to be put into place, help wanted btw). git://git.freebsd.org/freebsd.git git://git.freebsd.org/freebsd-doc.git git://git.freebsd.org/freebsd-ports.git (the canonical sources) git://github.com/freebsd/freebsd.git git://github.com/freebsd/freebsd-doc.git git://github.com/freebsd/freebsd-ports.git (the preferred sources) -- Regards, Bryan Drewery bdrewery@freenode/EFNet ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
start of text section in the ELF executable and in the Virtual Memory
Hi all, I've a generic question about how the program looks before and after it is loaded into the memory. I see that the TEXT_START_ADDR = 0x08048000 (found this in ~src/contrib/binutils/ld/emulparams/elf_i386.sh) when I do a procstat -v , I see some thing like this PIDSTARTEND PRT . PATH 2126 0x8048000 0x0804a000 r-x. /bin/cat I see that the VM address is same as that of the TEXT_START_ADDR. Does this mean that the actual begining of the program statement, `cat` in this case, has a VM address of 0x8048000. Looking at the Permission Flags (PRT = r-x) I assumed this is the text section. But when I do a objdump of /bin/cat (cmd: `objdump -D /bin/cat`), I see that there is a section named `.interp` starting at 0x8048134 and not 0x8048000. And the .text section starts from 0x8048b40 and there is no instruction at address 0x8048000. Can someone please tell me why is this so? and what exactly will be present in the memory from 0x8048000 and 0x8048134. Thanks. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: freebsd.org git repositories and svn ids
On Sat, Sep 1, 2012 at 5:50 PM, Bryan Drewery wrote: >>> More generally tho, I'm curious how one is supposed to use the >>> seemingly more official repositories without this bit of data; I'd >>> expect I must be missing some critical clue. I've just noticed that freebsd commits on github come with a git note. If you look past the diff of the commit, you will see a note that contains path and revision number. For example: https://github.com/freebsd/freebsd/commit/fa32f1f570be8b878b2965d95b7dbdc37a953938 has a note that says: svn path=/head/; revision=239998 So, information is there, it's just not part of the log message itself unless you add '--show-notes=*' While I'm sort of got used to git-svn-id being part of committed log messages, keeping conversion metadata separate from the content does make sense. --Artem ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: start of text section in the ELF executable and in the Virtual Memory
On Sat, Sep 1, 2012 at 7:44 PM, asp imho wrote: > Hi all, > > I've a generic question about how the program looks before and after it is > loaded into the memory. > > I see that the TEXT_START_ADDR = 0x08048000 (found this in > ~src/contrib/binutils/ld/emulparams/elf_i386.sh) > > when I do a procstat -v , I see some thing like this > > PIDSTARTEND PRT . > PATH > 2126 0x8048000 0x0804a000 r-x. > /bin/cat > > > I see that the VM address is same as that of the TEXT_START_ADDR. Does this > mean that the actual begining of the program statement, `cat` in this case, > has a VM address of 0x8048000. > > Looking at the Permission Flags (PRT = r-x) I assumed this is the text > section. this section be loaded from the file into memory at 0x8048000. .text section is probably part of that, but it's not necessarily the only thing. readelf command is quite handy when you need to see details of an ELF file. > > But when I do a objdump of /bin/cat (cmd: `objdump -D /bin/cat`), I see > that there is a section named `.interp` starting at 0x8048134 and not > 0x8048000. And the .text section starts from 0x8048b40 and there is no > instruction at address 0x8048000. Can someone please tell me why is this > so? and what exactly will be present in the memory from 0x8048000 and > 0x8048134. .interp section tells kernel what it needs to run in order to launch the executable. In case of dynamic executable this section contains path to dynamic linker. In this case kernel loads and runs the *runtime linker*. It's the linke which then looks at the ELF file, parses dynamic headers in the ELF file, finds and loads required shared objects and then jumps to the entry point specified in the ELF header of the original executable. --Artem ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: freebsd.org git repositories and svn ids
On Sat, Sep 1, 2012 at 9:29 PM, Artem Belevich wrote: > I've just noticed that freebsd commits on github come with a git note. > If you look past the diff of the commit, you will see a note that > contains path and revision number. > > For example: > https://github.com/freebsd/freebsd/commit/fa32f1f570be8b878b2965d95b7dbdc37a953938 > > has a note that says: > svn path=/head/; revision=239998 > > So, information is there, it's just not part of the log message itself > unless you add '--show-notes=*' > > While I'm sort of got used to git-svn-id being part of committed log > messages, keeping conversion metadata separate from the content does > make sense. Hmm. I've just cloned github.com/freebsd/freebsd and I don't see the notes that are shown on the web site. It appears that notes are not cloned by default. This page suggests adding "fetch = +refs/notes/*:refs/notes/*" to .git/config http://alblue.bandlem.com/2011/11/git-tip-of-week-git-notes.html Alas, that didn't help me much. It did seem to fetch notes for new commits, but preceeding commits are still note-less. I guess one would have to start with an empty git repository, then manually add remote and required 'fetch' magic and only then fetch commits from that remote. Does anyone know an easier way? --Artem ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
