search for: _that_

...at has to deal with many more files showed the leak, and the crash. (BTW, I am still waiting - after more than 3 years - and hoping for that useful c32 module to be part of official Syslinux.) Additionally, the amount of available resources (including memory, among others) in some cases is not _that_ high, and we frequently forget they exist. Cases such as the DOS-based installer comes to mind, and the length of the file names for library modules (e.g. "libutil_com.c32") is another one. It was _that_ easy to forget that FAT and ISO9660 do not support such file names (thus, a libra...

...-requests). > > I suspect that moving to a system where people are watching the repository instead of subscribing to the mailing-list is likely unavoidable at some point. Then again, watching the repository will ultimately be like subscribing to llvm-commits, won't it? How many people do _that_ and actually track what happens? I personally can't imagine doing that without some serious automatic filtering... Cheers, Nicolai > > -- > Mehdi > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > https://...

...orruption.jpg > > Does that just happen in 3.6.11 or even in 3.13? If the latter, that. > points to some key lack of understanding of... something. With > noaccel, we're not using pgraph or anything fancy -- it's just a > framebuffer, basically. So if we can't even render _that_ right... > > Hopefully someone else will pipe up re your other issues -- my > knowledge base on this is exhausted :( Interestingly, it turns out that the screen corruption occurs on every boot (booting with nouveau.noaccel=1 for now), and I can consistently work around it by one suspend-r...

...entioned wiki page, I would not > had interpreted the text the same way you wrote it here. > > Anyway, have you actually tried the first suggested method to clone the > repo: > > git clone --recursive git://repo.or.cz/syslinux.git a-new-directory > > using git, not http? Is _that_ working correctly? Ady, no need. Smells like he's behind a firewall that blocks tcp/9418 but allows tcp/80. Robert, I just updated the directions and it should help your issue. -- -Gene

> > If rpm is configured for _that_ location of log files, I would remove the > repository this rpm comes from from configuration and will remember to > never-never ever use that repository for anything. > > Just my $0.02 > Yeah I completely get where you're coming from there. However it's not an RPM from a re...

...hese... anything made before 1999 or so, and probably a bunch since then too. There _has_ to be a way to do this generically. Is the PCI spec version anywhere in the root hub? Perhaps we can check if every bridge on the way to the CPU has the MSI capability (including the root hub)? (And naturally _that_ won't work... on my sandybridge laptop, the host bridge doesn't have the MSI cap but the system most definitely supports MSI.) Adding Bjorn... perhaps you know? Some of the info has been stripped out by now, you can see the full lspci -vvvxxx at http://marc.info/?l=linux-pci&m=14044344...

...we're currently nested within, and update the offsets with every expansion of arguments. That's a bit more complex than just an integer count of number of files seen so far, but it should be implementable completely within the ExpandResponseFiles function, and I don't think it'd be _that_ tricky. On Mon, Apr 29, 2019 at 3:26 AM Hans Wennborg via llvm-dev < llvm-dev at lists.llvm.org> wrote: > It seems reasonable to have an expansion limit, but maybe 20 is too low. > > Chris: You say you're relying heavily on nested response files. Do you > have a feel for wh...

So, I _finally_ got the time to upgrade from 0.99.14 ... which I told myself I'd upgrade from once 1.0 was released... (yep, I've been _that_ busy :) So I read the Wiki page on 0.99->1.0 transition, and went through the config file - for all of about 5 or 10 minutes. I logged in at 11pm when nobody else should be using it, restarted dovecot with the new version, and logged in. Snap snap snap went my folders opening.. wow, so fas...

On 5 September 2016 at 22:12, Renato Golin <renato.golin at linaro.org> wrote: > Should we revert this? This is pretty serious? Can we fix this quickly > on the bots? Just FYI, I'm moving the "llvm" directory away and making it as a symlink to "llvm.src", at least until we sort out this problem. Since this has been going on from Sep 1st, I believe we'll

...erver. The fact that 3 PRIs are error free and that the problem moves with the circuit tells me that there is still a problem on the circuit. The telco believes that there is nothing more that they can do (provision a complete new circuit?). I don't get HDLC aborts, so the problem may not be _that_ serious. Does anyone have any comments? Would a newer (unstable) version of Zaptel drivers help? Would line-build-out parameter in zaptel.conf make any difference?

...t; + * Got the lock, can clear the waiting bit now > + */ > + smp_u8_store_release(&qlock->wait, 0); So we just did an atomic op, and now you're trying to optimize this write. Why do you need a whole byte for that? Surely a cmpxchg loop with the right atomic op can't be _that_ much slower? Its far more readable and likely avoids that steal fail below as well. > + return 1; > + } else if (old == _QSPINLOCK_LOCKED) { > +try_again: > + /* > + * Wait until the lock byte is cleared to get the lock > + */ > + do { > + cpu_relax(); > + } wh...

...t; + * Got the lock, can clear the waiting bit now > + */ > + smp_u8_store_release(&qlock->wait, 0); So we just did an atomic op, and now you're trying to optimize this write. Why do you need a whole byte for that? Surely a cmpxchg loop with the right atomic op can't be _that_ much slower? Its far more readable and likely avoids that steal fail below as well. > + return 1; > + } else if (old == _QSPINLOCK_LOCKED) { > +try_again: > + /* > + * Wait until the lock byte is cleared to get the lock > + */ > + do { > + cpu_relax(); > + } wh...

...files > showed the leak, and the crash. > > (BTW, I am still waiting - after more than 3 years - and hoping for > that useful c32 module to be part of official Syslinux.) > > Additionally, the amount of available resources (including memory, > among others) in some cases is not _that_ high, and we frequently > forget they exist. Cases such as the DOS-based installer comes to mind, > and the length of the file names for library modules (e.g. > "libutil_com.c32") is another one. It was _that_ easy to forget that > FAT and ISO9660 do not support such file name...

...it?ll work for you ? klibc on sh4, for example, was broken and nobody noticed it until I ssh?d to a porterbox (there seem to not exist any for hppa and powerpcspe) to fix an FTBFS, wanted to test the result and saw SIGILL (then downloaded the last version that had built, ran it and saw a SIGILL, so _that_ was no regression). A klibc 2.0 release is imminent, so please have a look. I?d also be interested in the general status of these two ports. bye, //mirabilos PS: It?s possible to get d-p.o access as non-DD. It?s possible to become DD relatively quickly too though. -- [...] if maybe ext3fs w...

Three tables: users: id clients: id admin_contacts: user_id, client_id class Client has_many :admin_contacts has_many :contacts, :through => :admin_contacts, :foreign_key => :user_id, :class_name => ''User'' end I added the :contacts for ease of use of grabbing the user objects associated with the admin_contact. This all works great, I can grab the Users that

...is becoming corporate and all. I have > absolute faith that this "anti-pirating technique" will be broken quite > quickly and everything will return to business as usual. It'll be circumvented eventually, but that doesn't mean labels won't keep trying. I'd consider _that_ to be business as usual from now on. > If it hasn't been > already. Lucky for me, none of the music i listen to comes from any major > record labels and something tells me the indie labels will be slow if at all > to come on board with this crap. Yeah, especially compared with the...

I''m having performance issues with one of my actions, and think I''ve narrowed it down to too many sql queries. I have a form with ~60 lines, which takes ~6 sec to save, 60%+ of that is db io. There''s 650+ lines of log data, most of which are AR/queries. The app is a simple dual entry book keeping thingy, and the form in question contains a journal entry along with a

...d quite full, and another storage chassis was added. Now, space problem gone, fine, but what about speed? Three of the VDEVs are quite full, as indicated below. VDEV #3 (the one with the spare active) just spent some 72 hours resilvering a 2TB drive. Now, those green drives suck quite hard, but not _that_ hard. I''m guessing the reason for this slowdown is the fill of those three first VDEVs. Now, is there a way, manually or automatically, to somehow balance the data across these LVOLs? My first guess is that doing this _automatically_ will require block pointer rewrite, but then, is there...

...ot flag to disable MSI, > you can refer to this in ACPI 5.2.9.3 chapter "Fixed ACPI Description Table Boot Architecture Flags" > > >> >> Perhaps we can check if every bridge on the way to the CPU has the MSI >> capability (including the root hub)? (And naturally _that_ won't >> work... on my sandybridge laptop, the host bridge doesn't have the MSI >> cap but the system most definitely supports MSI.) >> >> Adding Bjorn... perhaps you know? Some of the info has been stripped >> out by now, you can see the full lspci -vvvxxx at...

Hi, I have downloaded the newest source code ocfs2-1.2.3.tar.gz from oss.oracle.com. After do the configuration I find a strange thing. Although my kernel is "2.6.9-11.19AX"(Asianux2.0 on a vmware server with a single processor configured), the configuration find that it is 2.6.9-11.19AX-smp. So after I make and install, those *.ko went to the wrong place. The reason is: 1.