Re: mmap dirty limits on 32 bit kernels (Was: [BUG] New Kernel Bugs)

2007-11-21 Thread Bron Gondwana
On Thu, Nov 22, 2007 at 10:51:15AM +1100, Bron Gondwana wrote: > On Thu, Nov 15, 2007 at 08:32:22AM -0800, Linus Torvalds wrote: > > If this patch makes a difference, please holler. I think it's the correct > > thing to do, but I'm not going to actually commit it without somebody > > saying that

Re: mmap dirty limits on 32 bit kernels (Was: [BUG] New Kernel Bugs)

2007-11-21 Thread Bron Gondwana
On Thu, Nov 15, 2007 at 08:32:22AM -0800, Linus Torvalds wrote: > On Thu, 15 Nov 2007, Bron Gondwana wrote: > > > > I guess we'll be doing the one-liner kernel mod and testing > > that then. > > The thing to look at is "get_dirty_limits()" in mm/page-writeback.c, and > in this particular case it

Re: mmap dirty limits on 32 bit kernels (Was: [BUG] New Kernel Bugs)

2007-11-21 Thread Jan Engelhardt
On Thu, 15 Nov 2007 13:47:54 -0800 (PST) Linus Torvalds wrote: > >But quite frankly, I refuse to even care about anything past that. If >you have 12G (or heaven forbid, even more) in your machine, and you >can't be bothered to just upgrade to a 64-bit CPU, then quite frankly, >*I* personally ca

Re: size of git repository (was Re: [BUG] New Kernel Bugs)

2007-11-18 Thread Willy Tarreau
On Sun, Nov 18, 2007 at 03:56:11PM +0100, Ingo Molnar wrote: > > * Pavel Machek <[EMAIL PROTECTED]> wrote: > > > On Tue 2007-11-13 12:50:08, Mark Lord wrote: > > > Ingo Molnar wrote: > > > > > > > >for example git-bisect was godsent. I remember that > > > >years ago bisection of a bug was a very

Re: mmap dirty limits on 32 bit kernels (Was: [BUG] New Kernel Bugs)

2007-11-18 Thread Bron Gondwana
On Thu, Nov 15, 2007 at 01:14:32PM -0800, Linus Torvalds wrote: Sorry about not replying to this earlier. I actually got a weekend away from the computer pretty much last weekend - took the kids swimming, helped a friend clear dead wood from around her house before the fire season. Shocking I k

Re: mmap dirty limits on 32 bit kernels (Was: [BUG] New Kernel Bugs)

2007-11-18 Thread Bron Gondwana
On Sun, Nov 18, 2007 at 04:13:18PM -0700, Daniel Phillips wrote: > On Thursday 15 November 2007 14:24, Rob Mueller wrote: > > > That's my personal opinion, and I realize that some of the > > > commercial vendors may care about their insane customers' > > > satisfaction, but I'm simply not intereste

Re: mmap dirty limits on 32 bit kernels (Was: [BUG] New Kernel Bugs)

2007-11-18 Thread Daniel Phillips
On Thursday 15 November 2007 14:24, Rob Mueller wrote: > > That's my personal opinion, and I realize that some of the > > commercial vendors may care about their insane customers' > > satisfaction, but I'm simply not interested in insane users. If > > they have that much RAM (and bought it a few ye

Re: [BUG] New Kernel Bugs

2007-11-18 Thread Theodore Tso
On Sat, Nov 17, 2007 at 01:20:10PM +0100, Adrian Bunk wrote: > > But a bisect takes around 7 compiles. > >... > > I don't understand that number. > > The common case are regressions in -rc1, and a bisection of > at about 7000 commits takes around 13 compiles. Worst case it would take 13. In pra

Re: size of git repository (was Re: [BUG] New Kernel Bugs)

2007-11-18 Thread Rene Herman
On 18-11-07 15:35, James Bottomley wrote: clean-cg? But failure to run "git repack -a -d" every once in a while? Actually, the best command is git gc which does a repack (into a single pack file rather than an incremenal), and then removes all the objects now in the pack. If, like me, you

Re: size of git repository (was Re: [BUG] New Kernel Bugs)

2007-11-18 Thread Ingo Molnar
* Pavel Machek <[EMAIL PROTECTED]> wrote: > On Tue 2007-11-13 12:50:08, Mark Lord wrote: > > Ingo Molnar wrote: > > > > > >for example git-bisect was godsent. I remember that > > >years ago bisection of a bug was a very laborous task > > >so that it was only used as a final, last-ditch > > >ap

Re: size of git repository (was Re: [BUG] New Kernel Bugs)

2007-11-18 Thread James Bottomley
On Sun, 2007-11-18 at 13:58 +0100, Rene Herman wrote: > On 18-11-07 13:44, Pavel Machek wrote: > > > On Tue 2007-11-13 12:50:08, Mark Lord wrote: > > >> It's a 540MByte download over a slow link for everyone > >> else. > > > > Hmmm, clean-cg is 7.7G on my machine, and yes I tried > > git-prune

Re: size of git repository (was Re: [BUG] New Kernel Bugs)

2007-11-18 Thread Rene Herman
On 18-11-07 13:44, Pavel Machek wrote: On Tue 2007-11-13 12:50:08, Mark Lord wrote: It's a 540MByte download over a slow link for everyone else. Hmmm, clean-cg is 7.7G on my machine, and yes I tried git-prune-packed. What am I doing wrong? clean-cg? But failure to run "git repack -a -d" e

size of git repository (was Re: [BUG] New Kernel Bugs)

2007-11-18 Thread Pavel Machek
On Tue 2007-11-13 12:50:08, Mark Lord wrote: > Ingo Molnar wrote: > > > >for example git-bisect was godsent. I remember that > >years ago bisection of a bug was a very laborous task > >so that it was only used as a final, last-ditch > >approach for really nasty bugs. Today we can > >autonomouly

Re: [BUG] New Kernel Bugs

2007-11-17 Thread Adrian Bunk
On Fri, Nov 16, 2007 at 02:46:18PM -0500, Theodore Tso wrote: > On Fri, Nov 16, 2007 at 01:20:16PM -0500, Daniel Barkalow wrote: > > Compared to getting useful suggestions from a mailing list, especially > > before you've gotten anybody's attention? Hours or overnight isn't > > particularly long,

Use *poof* for linux-omap (Was: [BUG] New Kernel Bugs)

2007-11-16 Thread Tony Lindgren
Hi Dave, * David Miller <[EMAIL PROTECTED]> [071114 02:09]: > > In fact, *poof*, there it is, [EMAIL PROTECTED] is there and > available for anyone who wants to use it. Can you please use your *poof* trick one more time to set up [EMAIL PROTECTED] We've (as in linux-omap community) would lik

Re: [BUG] New Kernel Bugs

2007-11-16 Thread Theodore Tso
On Fri, Nov 16, 2007 at 01:20:16PM -0500, Daniel Barkalow wrote: > Compared to getting useful suggestions from a mailing list, especially > before you've gotten anybody's attention? Hours or overnight isn't > particularly long, and doesn't take up much of your time if you've got a > working kern

Re: [BUG] New Kernel Bugs

2007-11-16 Thread Daniel Barkalow
On Fri, 16 Nov 2007, Romano Giannetti wrote: > > (Cc: trimmed a bit). > > On Thu, 2007-11-15 at 11:19 -0500, Daniel Barkalow wrote: > > On Thu, 15 Nov 2007, Theodore Tso wrote: > [...] > > > A full kernel build with everything selected can take good 30 minutes or > > > more, and that's on a fas

Re: [BUG] New Kernel Bugs

2007-11-16 Thread Romano Giannetti
(Cc: trimmed a bit). On Thu, 2007-11-15 at 11:19 -0500, Daniel Barkalow wrote: > On Thu, 15 Nov 2007, Theodore Tso wrote: [...] > > A full kernel build with everything selected can take good 30 minutes or > > more, and that's on a fast dual-core machine with 4gigs of memory and > > 7200rpm disk

Re: mmap dirty limits on 32 bit kernels (Was: [BUG] New Kernel Bugs)

2007-11-15 Thread Alan Cox
> So the _only_ explanation today for 12GB on a 32-bit machine is > (a) insanity > or > (b) being so lazy as to not bother to upgrade > and in either case, my personal reaction is "I'm *not* crazy, and yes, I'm > lazy too, and I can't give a rats *ss about those problems". 12GB-16GB worked wel

Re: [BUG] New Kernel Bugs

2007-11-15 Thread J. Bruce Fields
On Thu, Nov 15, 2007 at 01:50:43PM +1100, Neil Brown wrote: > Virtual Folders. > > I use VM mode in EMACS, but I believe some other mail readers have the > same functionality. > I have a virtual folder called "nfs" which shows me all mail in my > inbox which has the string 'nfs' or 'lockd' in a To

Re: mmap dirty limits on 32 bit kernels (Was: [BUG] New Kernel Bugs)

2007-11-15 Thread Rob Mueller
That's my personal opinion, and I realize that some of the commercial vendors may care about their insane customers' satisfaction, but I'm simply not interested in insane users. If they have that much RAM (and bought it a few years ago when a 64-bit CPU wasn't an option), they can't be poor. F

Re: mmap dirty limits on 32 bit kernels (Was: [BUG] New Kernel Bugs)

2007-11-15 Thread Linus Torvalds
On Thu, 15 Nov 2007, Chris Friesen wrote: > > We've got some 32-bit 8GB boxes for which both of these would hold true. Still not enough of a reason for me to care. Remember - I'm the guy who refused to merge RH's 4G:4G patches because I thought they were an unsupportable nightmare. I care a

Re: mmap dirty limits on 32 bit kernels (Was: [BUG] New Kernel Bugs)

2007-11-15 Thread Chris Friesen
Linus Torvalds wrote: So the _only_ explanation today for 12GB on a 32-bit machine is (a) insanity or (b) being so lazy as to not bother to upgrade and in either case, my personal reaction is "I'm *not* crazy, and yes, I'm lazy too, and I can't give a rats *ss about those problems". How ab

Re: mmap dirty limits on 32 bit kernels (Was: [BUG] New Kernel Bugs)

2007-11-15 Thread Linus Torvalds
On Thu, 15 Nov 2007, Peter Zijlstra wrote: > > But this problem is already an issue, Anton recently had a case where a > 12GB highmem box locked up due to NTFS running out of lowmem - or > something like that. Yeah. I always considered HIGHMEM to just be unusable. It's ok for extending to 2-4G

Re: mmap dirty limits on 32 bit kernels (Was: [BUG] New Kernel Bugs)

2007-11-15 Thread Peter Zijlstra
On Thu, 2007-11-15 at 13:14 -0800, Linus Torvalds wrote: > > On Thu, 15 Nov 2007, Linus Torvalds wrote: > > > > Unacceptable. We used to do exactly what your patch does, and it got fixed > > once. We're not introducing that fundamentally broken concept again. > > Examples of non-broken solutio

Re: mmap dirty limits on 32 bit kernels (Was: [BUG] New Kernel Bugs)

2007-11-15 Thread Linus Torvalds
On Thu, 15 Nov 2007, Linus Torvalds wrote: > > The problem with HIGHMEM is that it causes various metadata (dentries, > inodes, page struct tables etc) to eat up memory "prime real estate" under > the same kind of conditions that also dirty a lot of memory. So the reason > we disallow HIGHMEM

Re: [BUG] New Kernel Bugs

2007-11-15 Thread Ben Dooks
On Tue, Nov 13, 2007 at 10:34:37PM +, Russell King wrote: > On Tue, Nov 13, 2007 at 06:25:16PM +, Alan Cox wrote: > > > Given the wide range of ARM platforms today, it is utterly idiotic to > > > expect a single person to be able to provide responses for all ARM bugs. > > > I for one wish I

Re: mmap dirty limits on 32 bit kernels (Was: [BUG] New Kernel Bugs)

2007-11-15 Thread Peter Zijlstra
On Thu, 2007-11-15 at 21:59 +0100, Peter Zijlstra wrote: > On Thu, 2007-11-15 at 12:56 -0800, Linus Torvalds wrote: > > > > On Thu, 15 Nov 2007, Peter Zijlstra wrote: > > > > > > Something like this ought to do I guess. Although my > > > mapping_is_buffercache() is the ugliest thing. I'm sure th

Re: mmap dirty limits on 32 bit kernels (Was: [BUG] New Kernel Bugs)

2007-11-15 Thread Linus Torvalds
On Thu, 15 Nov 2007, Linus Torvalds wrote: > > Unacceptable. We used to do exactly what your patch does, and it got fixed > once. We're not introducing that fundamentally broken concept again. Examples of non-broken solutions: (a) always use lowmem sizes (what we do now) (b) always use total

Re: mmap dirty limits on 32 bit kernels (Was: [BUG] New Kernel Bugs)

2007-11-15 Thread Peter Zijlstra
On Thu, 2007-11-15 at 12:56 -0800, Linus Torvalds wrote: > > On Thu, 15 Nov 2007, Peter Zijlstra wrote: > > > > Something like this ought to do I guess. Although my > > mapping_is_buffercache() is the ugliest thing. I'm sure that can be done > > better. > > No, this absolutely sucks. Agreed, I

Re: mmap dirty limits on 32 bit kernels (Was: [BUG] New Kernel Bugs)

2007-11-15 Thread Linus Torvalds
On Thu, 15 Nov 2007, Peter Zijlstra wrote: > > Something like this ought to do I guess. Although my > mapping_is_buffercache() is the ugliest thing. I'm sure that can be done > better. No, this absolutely sucks. Why? It's totally unacceptable to have per-mapping notions of how much memory we

Re: mmap dirty limits on 32 bit kernels (Was: [BUG] New Kernel Bugs)

2007-11-15 Thread Peter Zijlstra
On Thu, 2007-11-15 at 20:40 +0100, Peter Zijlstra wrote: > As for the highmem part, that was due to buffer cache, and unfortunately > that is still true. Although maybe we can do something smart with the > per-bdi stuff. Something like this ought to do I guess. Although my mapping_is_buffercache

Re: mmap dirty limits on 32 bit kernels (Was: [BUG] New Kernel Bugs)

2007-11-15 Thread Peter Zijlstra
On Thu, 2007-11-15 at 08:32 -0800, Linus Torvalds wrote: > > On Thu, 15 Nov 2007, Bron Gondwana wrote: > > > > I guess we'll be doing the one-liner kernel mod and testing > > that then. > > The thing to look at is "get_dirty_limits()" in mm/page-writeback.c, and > in this particular case it's

Re: [BUG] New Kernel Bugs

2007-11-15 Thread Daniel Barkalow
On Thu, 15 Nov 2007, Theodore Tso wrote: > On Wed, Nov 14, 2007 at 06:23:34PM -0500, Daniel Barkalow wrote: > > I don't see any reason that we couldn't have a tool accessible to Ubuntu > > users that does a real "git bisect". Git is really good at being scripted > > by fancy GUIs. It should be e

Re: mmap dirty limits on 32 bit kernels (Was: [BUG] New Kernel Bugs)

2007-11-15 Thread Linus Torvalds
On Thu, 15 Nov 2007, Bron Gondwana wrote: > > I guess we'll be doing the one-liner kernel mod and testing > that then. The thing to look at is "get_dirty_limits()" in mm/page-writeback.c, and in this particular case it's the unsigned long available_memory = determine_dirtyable_memory(

Re: [BUG] New Kernel Bugs

2007-11-15 Thread Theodore Tso
On Wed, Nov 14, 2007 at 06:23:34PM -0500, Daniel Barkalow wrote: > I don't see any reason that we couldn't have a tool accessible to Ubuntu > users that does a real "git bisect". Git is really good at being scripted > by fancy GUIs. It should be easy enough to have a drop down with all of > the

Re: [alsa-devel] [BUG] New Kernel Bugs

2007-11-15 Thread Rene Herman
On 15-11-07 14:00, Jörn Engel wrote: And even without mails being held hostage for weeks, every single moderation mail is annoying. Like the one I'm sure to receive after sending this out. Certainly. Upto this thread I wasn't actually aware the list was doing that. While it might be informa

Re: [alsa-devel] [BUG] New Kernel Bugs

2007-11-15 Thread Takashi Iwai
At Thu, 15 Nov 2007 14:17:27 +0100, Olivier Galibert wrote: > > On Thu, Nov 15, 2007 at 06:59:34AM +0100, Rene Herman wrote: > > Totally unrelated indeed so why are spouting crap? If the kohab list has a > > problem take it up with them but keep ALSA out of it. alsa-devel has only > > ever moder

Re: [alsa-devel] [BUG] New Kernel Bugs

2007-11-15 Thread Olivier Galibert
On Thu, Nov 15, 2007 at 06:59:34AM +0100, Rene Herman wrote: > Totally unrelated indeed so why are spouting crap? If the kohab list has a > problem take it up with them but keep ALSA out of it. alsa-devel has only > ever moderated out spam -- nothing else. That is incorrect. Hopefully it is the

Re: [alsa-devel] [BUG] New Kernel Bugs

2007-11-15 Thread Jörn Engel
On Thu, 15 November 2007 13:26:51 +0100, Rene Herman wrote: > > Can you please just shelve this crap? You have a way of knowing that "ALSA > will accept you" and that is knowing or assuming that the ALSA project > doesn't consist of drooling retards. Well, my experience with moderation has been

Re: [alsa-devel] [BUG] New Kernel Bugs

2007-11-15 Thread Rene Herman
On 15-11-07 13:02, Bron Gondwana wrote: I get the same information from both project websites: "moderated for non-members, public archives" - no way of knowing that ALSA will accept me informing them of something they would be interested without committing to reading or bit-bucketing their list.

Re: [alsa-devel] [BUG] New Kernel Bugs

2007-11-15 Thread Bron Gondwana
On Thu, Nov 15, 2007 at 06:59:34AM +0100, Rene Herman wrote: > On 15-11-07 05:16, Bron Gondwana wrote: > >> Totally unrelated - I sent something to the kolab mailing list a couple > > [ ... ] > >> I'm sure if I had something that I considered worth informing the ALSA >> project of, I'd be wary of

mmap dirty limits on 32 bit kernels (Was: [BUG] New Kernel Bugs)

2007-11-15 Thread Bron Gondwana
On Wed, Nov 14, 2007 at 09:53:38PM -0800, Linus Torvalds wrote: > > > On Wed, 14 Nov 2007, Linus Torvalds wrote: > > > > So even at 100% dirty limits, it won't let you dirty more than 1GB on the > > default 32-bit setup. > > Side note: all of these are obviously still just heuristics. If you r

Re: [alsa-devel] [BUG] New Kernel Bugs

2007-11-14 Thread Rene Herman
On 15-11-07 05:16, Bron Gondwana wrote: Totally unrelated - I sent something to the kolab mailing list a couple [ ... ] I'm sure if I had something that I considered worth informing the ALSA project of, I'd be wary of spending the same effort writing a good post knowing it may be dropped in

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Linus Torvalds
On Wed, 14 Nov 2007, Linus Torvalds wrote: > > So even at 100% dirty limits, it won't let you dirty more than 1GB on the > default 32-bit setup. Side note: all of these are obviously still just heuristics. If you really *do* run on a 32-bit kernel, and you want to have the pain, I'm sure you

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Linus Torvalds
On Thu, 15 Nov 2007, Bron Gondwana wrote: > > So we've already been running those settings for a while. They didn't > help. Ok, so something else is up. If the mmap file is 2G, and you have 6G of RAM, you shouldn't be hitting the dirty limits with those setups. Of course, it may still be tha

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Bron Gondwana
On Wed, Nov 14, 2007 at 08:24:53PM -0800, Linus Torvalds wrote: > > > On Thu, 15 Nov 2007, Bron Gondwana wrote: > > > > And congratulations to him for that. We almost entirely dropped 2.6.16, > > but there's a regression some time since then that makes large MMAPed > > files a major pain (speci

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Bron Gondwana
On Tue, Nov 13, 2007 at 10:56:01PM +0100, Christian Kujau wrote: > On Tue, 13 Nov 2007, Andrew Morton wrote: >> There are a number of process things we _could_ do. Like >> - have bugfix-only kernel releases > > Adrian Bunk does (did?) this with 2.6.16.x, although it always seemed to me > like an

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Linus Torvalds
On Thu, 15 Nov 2007, Bron Gondwana wrote: > > And congratulations to him for that. We almost entirely dropped 2.6.16, > but there's a regression some time since then that makes large MMAPed > files a major pain (specifically the dcc database clean takes about 5 > minutes on 2.6.16 and about 12

Re: [alsa-devel] [BUG] New Kernel Bugs

2007-11-14 Thread Bron Gondwana
On Wed, Nov 14, 2007 at 12:46:24PM +0100, Rene Herman wrote: > On 14-11-07 11:07, David Miller wrote: > > Added Jaroslav and Takashi to the already extensive CC > >> From: Russell King <[EMAIL PROTECTED]> > >>> So, when are you creating a replacement alsa-devel mailing list on >>> vger? That's

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Neil Brown
On Tuesday November 13, [EMAIL PROTECTED] wrote: > On Tuesday 13 November 2007 07:08, Mark Lord wrote: > > Ingo Molnar wrote: > > .. > > > > > This is all QA-101 that _cannot be argued against on a rational basis_, > > > it's just that these sorts of things have been largely ignored for > > > years

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Neil Brown
On Wednesday November 14, [EMAIL PROTECTED] wrote: > On Wed, Nov 14, 2007 at 09:38:20AM -0800, Randy Dunlap wrote: > > On Wed, 14 Nov 2007 15:08:47 +0100 Ingo Molnar wrote: > > > so please stop this "too busy and too noisy" nonsense already. It was > > > nonsense 10 years ago and it's nonsense tod

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Daniel Barkalow
On Tue, 13 Nov 2007, Theodore Tso wrote: > There are two parts to this. One is a Ubuntu development kernel which > we can give to large numbers of people to expand our testing pool. > But if we don't do a better job of responding to bug reports that > would be generated by expanded testing this w

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Linus Torvalds
On Thu, 15 Nov 2007, Heikki Orsila wrote: > > See > http://bugzilla.kernel.org/show_bug.cgi?id=9321 > > for more information. That's a pretty unhelpful thing. It doesn't describe the breakage at all, so there is hardly much "more info". You've also apparently made all the attachements

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Heikki Orsila
On Wed, Nov 14, 2007 at 11:54:16AM -0800, Linus Torvalds wrote: > Actually, I'm pretty happy reverting patches that cause regressions even > if it *can* be "fixed for release". If there isn't a fix available within > a day or two, it should get reverted. > ... > Also, please notice the latter par

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Gabriel C
Denys Vlasenko wrote: > hi Matthew, > > On Wednesday 14 November 2007 06:35, Hannes Reinecke wrote: >> Matthew Wilcox wrote: >>> On Wed, Nov 14, 2007 at 12:46:20AM -0700, Denys Vlasenko wrote: Finally they replied and asked to rediff it against their git tree. I did that and sent patches

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Denys Vlasenko
hi Matthew, On Wednesday 14 November 2007 06:35, Hannes Reinecke wrote: > Matthew Wilcox wrote: > > On Wed, Nov 14, 2007 at 12:46:20AM -0700, Denys Vlasenko wrote: > >> Finally they replied and asked to rediff it against their > >> git tree. I did that and sent patches back. No reply since then. >

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Randy Dunlap
On Wed, 14 Nov 2007 21:37:37 +0100 Ingo Molnar wrote: > ok, then you conceded it by not replying to it? good ;-) No, I don't intend to carry on this discussion, but I appreciate the smiley. --- ~Randy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a mess

Re: [BUG] New Kernel Bugs

2007-11-14 Thread david
On Wed, 14 Nov 2007, Ingo Molnar wrote: Dumping even more crap on lkml is not the answer. that "crap" that i'd like to see dumped upon lkml would be netdev traffic mainly - most of the other kernel development lists (and i'm subscribed to many of them) are low-traffic. netdev is the main reaso

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Ingo Molnar
* James Bottomley <[EMAIL PROTECTED]> wrote: > On Wed, 2007-11-14 at 11:56 -0800, David Miller wrote: > > From: Ingo Molnar <[EMAIL PROTECTED]> > > Date: Wed, 14 Nov 2007 15:08:47 +0100 > > > > > In fact this thread is the very example: David points out that on netdev > > > some of those bugs w

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Ingo Molnar
* David Miller <[EMAIL PROTECTED]> wrote: > From: Ingo Molnar <[EMAIL PROTECTED]> > Date: Wed, 14 Nov 2007 15:08:47 +0100 > > > In fact this thread is the very example: David points out that on netdev > > some of those bugs were already discussed and resolved. Had it been all > > on lkml we'd

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Ingo Molnar
* Randy Dunlap <[EMAIL PROTECTED]> wrote: > On Wed, 14 Nov 2007 21:16:39 +0100 Ingo Molnar wrote: > > > countered by the underlined sentences above, just in case you missed > > it. > > I didn't miss your claim. ok, then you conceded it by not replying to it? good ;-) Ingo - To unsubs

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Randy Dunlap
On Wed, 14 Nov 2007 21:16:39 +0100 Ingo Molnar wrote: > countered by the underlined sentences above, just in case you missed it. I didn't miss your claim. --- ~Randy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More maj

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Ingo Molnar
* Randy Dunlap <[EMAIL PROTECTED]> wrote: > On Wed, 14 Nov 2007 15:08:47 +0100 Ingo Molnar wrote: > > > > > * Randy Dunlap <[EMAIL PROTECTED]> wrote: > > > > > > (and this is in no way directed at the networking folks - it holds > > > > for all of us. I have one main complaint about networkin

Re: [BUG] New Kernel Bugs

2007-11-14 Thread James Bottomley
On Wed, 2007-11-14 at 11:56 -0800, David Miller wrote: > From: Ingo Molnar <[EMAIL PROTECTED]> > Date: Wed, 14 Nov 2007 15:08:47 +0100 > > > In fact this thread is the very example: David points out that on netdev > > some of those bugs were already discussed and resolved. Had it been all > > on

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Russell King
On Wed, Nov 14, 2007 at 01:24:48PM +, Pavel Machek wrote: > Hi! > > > > Suspend to RAM resume hangs on a tickless (NO_HZ) kernel > > > http://bugzilla.kernel.org/show_bug.cgi?id=9275 > > > Kernel: 2.6.23 > > > This is HP notebook nc6320 T2400 945GM > > > > No response from developers > > May

Re: [BUG] New Kernel Bugs

2007-11-14 Thread David Miller
From: Ingo Molnar <[EMAIL PROTECTED]> Date: Wed, 14 Nov 2007 15:08:47 +0100 > In fact this thread is the very example: David points out that on netdev > some of those bugs were already discussed and resolved. Had it been all > on lkml we'd all be aware of it. That's a rediculious argument. One

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Linus Torvalds
On Wed, 14 Nov 2007, Nick Piggin wrote: > > Not if you said their regression causing patches will get reverted unless it > can be fixed for release. Actually, I'm pretty happy reverting patches that cause regressions even if it *can* be "fixed for release". If there isn't a fix available withi

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Russell King
On Wed, Nov 14, 2007 at 02:07:06AM -0800, David Miller wrote: > From: Russell King <[EMAIL PROTECTED]> > Date: Wed, 14 Nov 2007 09:55:07 + > > > On Tue, Nov 13, 2007 at 05:55:51PM -0800, David Miller wrote: > > > I've created [EMAIL PROTECTED] > > > > By doing so you've just said (implicitly)

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Kok, Auke
Denys Vlasenko wrote: > On Wednesday 14 November 2007 00:27, Adrian Bunk wrote: >> You missed the following in my email: >> "we slowly scare them away due to the many bug reports without any >> reaction." >> >> The problem is that bug reports take time. If you go away from easy >> things like comp

Re: [BUG] New Kernel Bugs

2007-11-14 Thread J. Bruce Fields
On Wed, Nov 14, 2007 at 09:38:20AM -0800, Randy Dunlap wrote: > On Wed, 14 Nov 2007 15:08:47 +0100 Ingo Molnar wrote: > > so please stop this "too busy and too noisy" nonsense already. It was > > nonsense 10 years ago and it's nonsense today. In 10 years the kernel > > grew from a 1 million lines

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Randy Dunlap
On Wed, 14 Nov 2007 15:08:47 +0100 Ingo Molnar wrote: > > * Randy Dunlap <[EMAIL PROTECTED]> wrote: > > > > (and this is in no way directed at the networking folks - it holds > > > for all of us. I have one main complaint about networking: the > > > separate netdev list is a bad idea - network

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Jan Evert van Grootheest
Adrian Bunk wrote: On Tue, Nov 13, 2007 at 12:13:56PM -0500, Theodore Tso wrote: On Tue, Nov 13, 2007 at 04:52:32PM +0100, Benoit Boissinot wrote: Btw, I used to test every -mm kernel. But since I've switched distros (gentoo->ubuntu) and I have less time, I feel it's harder to test -rc

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Larry Finger
Ingo Molnar wrote: > * Mark Lord <[EMAIL PROTECTED]> wrote: > >>> You're assuming that everything in linux-2.6 was downloaded; that's >>> not true. Everything in linux-2.6/.git was downloaded; but then you >>> do a checkout which happens to approximately double the size of the >>> linux-2.6 di

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Ingo Molnar
* Mark Lord <[EMAIL PROTECTED]> wrote: >> You're assuming that everything in linux-2.6 was downloaded; that's >> not true. Everything in linux-2.6/.git was downloaded; but then you >> do a checkout which happens to approximately double the size of the >> linux-2.6 directory. > .. > > Ah, I wo

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Fabio Comolli
FWIW, I see the same problem with another HP notebook, DV4378EA with radeon X700 video card. It does not happen frequently but I can say that since I disabled the tickless feature I can't reproduce the problem anymore. On Nov 14, 2007 2:24 PM, Pavel Machek <[EMAIL PROTECTED]> wrote: > Hi! > > > >

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Ingo Molnar
* Randy Dunlap <[EMAIL PROTECTED]> wrote: > > (and this is in no way directed at the networking folks - it holds > > for all of us. I have one main complaint about networking: the > > separate netdev list is a bad idea - networking regressions should > > be discussed and fixed on lkml, like mo

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Pavel Machek
Hi! > > Suspend to RAM resume hangs on a tickless (NO_HZ) kernel > > http://bugzilla.kernel.org/show_bug.cgi?id=9275 > > Kernel: 2.6.23 > > This is HP notebook nc6320 T2400 945GM > > No response from developers Maybe I'm optimistic, but I expected Ingo/Thomas to look after nohz problems. nohz=of

Re: Moderated list (Was: Re: [BUG] New Kernel Bugs)

2007-11-14 Thread Takashi Iwai
At Wed, 14 Nov 2007 13:21:30 +0100, Rene Herman wrote: > > On 14-11-07 09:25, Takashi Iwai wrote: > > > At Wed, 14 Nov 2007 04:01:31 -0800 (PST), > > David Miller wrote: > >> From: David Miller <[EMAIL PROTECTED]> > >> Date: Wed, 14 Nov 2007 03:56:57 -0800 (PST) > >> > >>> The fact that it farts

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Hannes Reinecke
Matthew Wilcox wrote: > On Wed, Nov 14, 2007 at 12:46:20AM -0700, Denys Vlasenko wrote: >> Finally they replied and asked to rediff it against their >> git tree. I did that and sent patches back. No reply since then. >> >> And mind you, the patch is not trying to do anything >> complex, it mostly m

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Matthew Wilcox
On Wed, Nov 14, 2007 at 12:46:20AM -0700, Denys Vlasenko wrote: > Finally they replied and asked to rediff it against their > git tree. I did that and sent patches back. No reply since then. > > And mind you, the patch is not trying to do anything > complex, it mostly moves code around, removes 'i

Re: [alsa-devel] [BUG] New Kernel Bugs

2007-11-14 Thread Rene Herman
On 14-11-07 13:01, David Miller wrote: From: David Miller <[EMAIL PROTECTED]> Date: Wed, 14 Nov 2007 03:56:57 -0800 (PST) The fact that it farts at me every time I post to this thread. See? I got another one and I have received at least 10 of the following over the past 2 days. Nah, in th

Re: [alsa-devel] [BUG] New Kernel Bugs

2007-11-14 Thread Rene Herman
On 14-11-07 12:56, David Miller wrote: From: Rene Herman <[EMAIL PROTECTED]> Date: Wed, 14 Nov 2007 12:46:24 +0100 [EMAIL PROTECTED] is not subscriber-only. Same as that arm list, it's _moderated_ for non-subscribers and given that I and other moderators have been doing our best to moderate q

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Jiri Kosina
On Tue, 13 Nov 2007, Andrew Morton wrote: > > HID > > > > Kernel NULL pointer dereference at :usbhid:hiddev_ioctl+0x2f/0xabc > > http://bugzilla.kernel.org/show_bug.cgi?id=9216 > > Kernel: 2.6.23.1 > > Looks like this is a regres

Re: Moderated list (Was: Re: [BUG] New Kernel Bugs)

2007-11-14 Thread Rene Herman
On 14-11-07 09:25, Takashi Iwai wrote: At Wed, 14 Nov 2007 04:01:31 -0800 (PST), David Miller wrote: From: David Miller <[EMAIL PROTECTED]> Date: Wed, 14 Nov 2007 03:56:57 -0800 (PST) The fact that it farts at me every time I post to this thread. See? I got another one and I have received a

Moderated list (Was: Re: [BUG] New Kernel Bugs)

2007-11-14 Thread Takashi Iwai
At Wed, 14 Nov 2007 04:01:31 -0800 (PST), David Miller wrote: > > From: David Miller <[EMAIL PROTECTED]> > Date: Wed, 14 Nov 2007 03:56:57 -0800 (PST) > > > The fact that it farts at me every time I post to this thread. > > See? I got another one and I have received at least 10 of the > followi

Re: [alsa-devel] [BUG] New Kernel Bugs

2007-11-14 Thread David Miller
MAIL PROTECTED] Date: Wed, 14 Nov 2007 12:57:06 +0100 Sender: [EMAIL PROTECTED] Your mail to 'Alsa-devel' with the subject Re: [alsa-devel] [BUG] New Kernel Bugs Is being held until the list moderator can review it for approval. The reason it is being held: Too many recipient

Re: [alsa-devel] [BUG] New Kernel Bugs

2007-11-14 Thread David Miller
From: Rene Herman <[EMAIL PROTECTED]> Date: Wed, 14 Nov 2007 12:46:24 +0100 > [EMAIL PROTECTED] is not subscriber-only. Same as that arm list, > it's _moderated_ for non-subscribers and given that I and other moderators > have been doing our best to moderate quickly (I tend to stay logged in to

Re: [alsa-devel] [BUG] New Kernel Bugs

2007-11-14 Thread Rene Herman
On 14-11-07 11:07, David Miller wrote: Added Jaroslav and Takashi to the already extensive CC From: Russell King <[EMAIL PROTECTED]> So, when are you creating a replacement alsa-devel mailing list on vger? That's also subscribers-only. The operative term is "alternative" rather than "

Re: [BUG] New Kernel Bugs

2007-11-14 Thread David Miller
From: Russell King <[EMAIL PROTECTED]> Date: Wed, 14 Nov 2007 09:55:07 + > On Tue, Nov 13, 2007 at 05:55:51PM -0800, David Miller wrote: > > I've created [EMAIL PROTECTED] > > By doing so you've just said (implicitly) that you can not tolerate > someone having a different opinion from your ow

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Russell King
On Tue, Nov 13, 2007 at 05:55:51PM -0800, David Miller wrote: > From: Andrew Morton <[EMAIL PROTECTED]> > Date: Tue, 13 Nov 2007 14:32:01 -0800 > > > On Tue, 13 Nov 2007 22:18:01 + Russell King <[EMAIL PROTECTED]> wrote: > > > > > Find some other mailing list; I'm not hosting *nor* am I willi

Re: [BUG] New Kernel Bugs

2007-11-14 Thread Russell King
On Tue, Nov 13, 2007 at 06:27:00PM -0800, Andrew Morton wrote: > On Tue, 13 Nov 2007 17:55:51 -0800 (PST) David Miller <[EMAIL PROTECTED]> > wrote: > > > I've created [EMAIL PROTECTED] > > Let me just say - I'm astonished at how little spam gets though the vger > lists. Considering how many tim

Re: [BUG] New Kernel Bugs

2007-11-13 Thread Denys Vlasenko
On Wednesday 14 November 2007 00:27, Adrian Bunk wrote: > You missed the following in my email: > "we slowly scare them away due to the many bug reports without any > reaction." > > The problem is that bug reports take time. If you go away from easy > things like compile errors then even things li

Re: [BUG] New Kernel Bugs

2007-11-13 Thread Adrian Bunk
On Tue, Nov 13, 2007 at 05:39:45PM -0700, Denys Vlasenko wrote: > On Tuesday 13 November 2007 10:56, Adrian Bunk wrote: > > On Tue, Nov 13, 2007 at 12:13:56PM -0500, Theodore Tso wrote: > > > On Tue, Nov 13, 2007 at 04:52:32PM +0100, Benoit Boissinot wrote: > > > > Btw, I used to test every -mm ker

Re: [BUG] New Kernel Bugs

2007-11-13 Thread David Miller
From: Sam Ravnborg <[EMAIL PROTECTED]> Date: Wed, 14 Nov 2007 06:56:06 +0100 > > > > > If so, MANITAINERS claims that it is subscribers-only. That would cause > > > some bug reporters to give up and go away. > > > > Find some other mailing list; I'm not hosting *nor* am I willing to run a > > n

Re: [BUG] New Kernel Bugs

2007-11-13 Thread Sam Ravnborg
On Wed, Nov 14, 2007 at 06:56:06AM +0100, Sam Ravnborg wrote: > > > > > If so, MANITAINERS claims that it is subscribers-only. That would cause > > > some bug reporters to give up and go away. > > > > Find some other mailing list; I'm not hosting *nor* am I willing to run a > > non-subscribers o

Re: [BUG] New Kernel Bugs

2007-11-13 Thread Sam Ravnborg
> > > If so, MANITAINERS claims that it is subscribers-only. That would cause > > some bug reporters to give up and go away. > > Find some other mailing list; I'm not hosting *nor* am I willing to run a > non-subscribers only mailing list. Period. Not negotiable, so don't even > try to change

Re: [BUG] New Kernel Bugs

2007-11-13 Thread David Miller
From: "Martin Bligh" <[EMAIL PROTECTED]> Date: Tue, 13 Nov 2007 09:46:08 -0800 > This is a technical issue with vger.kernel.org mailing lists that I've tried > addressing before - maybe davem can help fix it? I think the problem is that certain mail headers show up multiple times and this makes i

Re: [BUG] New Kernel Bugs

2007-11-13 Thread Nick Piggin
rant on :) ... These aren't directed specifically at Andrew, but everyone who merges patches or is involved in the release process. On Wednesday 14 November 2007 08:04, Andrew Morton wrote: > On Tue, 13 Nov 2007 21:00:30 +0100 (CET) Christian Kujau <[EMAIL PROTECTED]> wrote: > > On Tue, 13 Nov 20

Re: [BUG] New Kernel Bugs

2007-11-13 Thread David Miller
From: Andrew Morton <[EMAIL PROTECTED]> Date: Tue, 13 Nov 2007 18:27:00 -0800 > Let me just say - I'm astonished at how little spam gets though the vger > lists. Considering how many times those email addresses must have been > added to spam databases. > > It must be a lot of work, and whoever i

  1   2   3   >