Re: 2.6.13-rc3 test: finding compile errors with make randconfig

2005-07-24 Thread Grant Coady
On Sun, 24 Jul 2005 23:27:22 +0200, Adrian Bunk <[EMAIL PROTECTED]> wrote: >Looking at the .config, the problem is actually: > CONFIG_BROKEN=y > >You should edit init/Kconfig to disallow CONFIG_CLEAN_COMPILE=n, since >any errors you see with CONFIG_BROKEN=y aren't interesting. Very good point.

Re: 2.6.13-rc3 test: finding compile errors with make randconfig

2005-07-24 Thread Grant Coady
On Sun, 24 Jul 2005 22:39:32 +0200, Adrian Bunk <[EMAIL PROTECTED]> wrote: >On Mon, Jul 25, 2005 at 05:42:58AM +1000, Grant Coady wrote: >> On Sun, 24 Jul 2005 11:13:27 +0200, Adrian Bunk <[EMAIL PROTECTED]> wrote: >> > >> >it's generally useful, but the

Re: xor as a lazy comparison

2005-07-24 Thread Grant Coady
On Sun, 24 Jul 2005 18:40:25 +0200 (MEST), Jan Engelhardt <[EMAIL PROTECTED]> wrote: > >I have seen this in kernel/signal.c:check_kill_permission() > >&& (current->euid ^ t->suid) && (current->euid ^ t->uid) > >If current->euid and t->suid are the same, the xor returns 0, so these

Re: 2.6.13-rc3 test: finding compile errors with make randconfig

2005-07-24 Thread Grant Coady
On Sun, 24 Jul 2005 11:13:27 +0200, Adrian Bunk <[EMAIL PROTECTED]> wrote: > >it's generally useful, but the target kernel should be the latest -mm >kernel. 097-error:drivers/char/drm/drm_memory.h:163: error: redefinition of `drm_ioremap_nocache' 097-error:drivers/char/drm/drm_memory.h:163:

Re: 2.6.13-rc3 test: finding compile errors with make randconfig

2005-07-24 Thread Grant Coady
On Sun, 24 Jul 2005 15:01:22 +0200, Jesper Juhl <[EMAIL PROTECTED]> wrote: >> context. Deliberately simplistic for traceability at the moment, truncated >> error length for this post. >> >If you could put the data online somewhere I'd be interrested in >taking a look at it. 7.4MB raw data -->

2.6.13-rc3 test: finding compile errors with make randconfig

2005-07-24 Thread Grant Coady
Greetings, Few days ago I compiled 241 random configurations of 2.6.13-rc3, today I finally got around to parsing the results, top 40, sorted by name. Percentage is error_builds / total_builds. build script similar to: count=0 while [ $((++count)) -le $limit ]; do trial=$(printf %003d

2.6.13-rc3 test: finding compile errors with make randconfig

2005-07-24 Thread Grant Coady
Greetings, Few days ago I compiled 241 random configurations of 2.6.13-rc3, today I finally got around to parsing the results, top 40, sorted by name. Percentage is error_builds / total_builds. build script similar to: count=0 while [ $((++count)) -le $limit ]; do trial=$(printf %003d

Re: 2.6.13-rc3 test: finding compile errors with make randconfig

2005-07-24 Thread Grant Coady
On Sun, 24 Jul 2005 15:01:22 +0200, Jesper Juhl [EMAIL PROTECTED] wrote: context. Deliberately simplistic for traceability at the moment, truncated error length for this post. If you could put the data online somewhere I'd be interrested in taking a look at it. 7.4MB raw data -- low info

Re: 2.6.13-rc3 test: finding compile errors with make randconfig

2005-07-24 Thread Grant Coady
On Sun, 24 Jul 2005 11:13:27 +0200, Adrian Bunk [EMAIL PROTECTED] wrote: it's generally useful, but the target kernel should be the latest -mm kernel. 097-error:drivers/char/drm/drm_memory.h:163: error: redefinition of `drm_ioremap_nocache' 097-error:drivers/char/drm/drm_memory.h:163: error:

Re: xor as a lazy comparison

2005-07-24 Thread Grant Coady
On Sun, 24 Jul 2005 18:40:25 +0200 (MEST), Jan Engelhardt [EMAIL PROTECTED] wrote: I have seen this in kernel/signal.c:check_kill_permission() (current-euid ^ t-suid) (current-euid ^ t-uid) If current-euid and t-suid are the same, the xor returns 0, so these statements are

Re: 2.6.13-rc3 test: finding compile errors with make randconfig

2005-07-24 Thread Grant Coady
On Sun, 24 Jul 2005 22:39:32 +0200, Adrian Bunk [EMAIL PROTECTED] wrote: On Mon, Jul 25, 2005 at 05:42:58AM +1000, Grant Coady wrote: On Sun, 24 Jul 2005 11:13:27 +0200, Adrian Bunk [EMAIL PROTECTED] wrote: it's generally useful, but the target kernel should be the latest -mm kernel. 097

Re: 2.6.13-rc3 test: finding compile errors with make randconfig

2005-07-24 Thread Grant Coady
On Sun, 24 Jul 2005 23:27:22 +0200, Adrian Bunk [EMAIL PROTECTED] wrote: Looking at the .config, the problem is actually: CONFIG_BROKEN=y You should edit init/Kconfig to disallow CONFIG_CLEAN_COMPILE=n, since any errors you see with CONFIG_BROKEN=y aren't interesting. Very good point. $ grep

Re: PROBLEM: IDE Zip drive doesn't work under 2.6.12

2005-07-22 Thread Grant Coady
On Thu, 21 Jul 2005 11:21:05 -0400 (EDT), Jim Faulkner <[EMAIL PROTECTED]> wrote: > >Recently I upgraded from 2.6.11.11 to 2.6.12.3. This morning I tried >using my Zip drive... unfortunately it doesn't work under 2.6.12.3. To >verify that this was a kernel problem, I rebooted to 2.6.11.11.

Re: PROBLEM: IDE Zip drive doesn't work under 2.6.12

2005-07-22 Thread Grant Coady
On Thu, 21 Jul 2005 11:21:05 -0400 (EDT), Jim Faulkner [EMAIL PROTECTED] wrote: Recently I upgraded from 2.6.11.11 to 2.6.12.3. This morning I tried using my Zip drive... unfortunately it doesn't work under 2.6.12.3. To verify that this was a kernel problem, I rebooted to 2.6.11.11. Here's

Re: 2.6.12 vs. /sbin/cardmgr

2005-07-16 Thread Grant Coady
On Sat, 16 Jul 2005 11:36:45 -0500 (CDT), [EMAIL PROTECTED] (Bob Tracy) wrote: >rct wrote: >> Dominik Brodowski wrote: >> > On Sun, Jul 10, 2005 at 03:37:22PM -0500, Bob Tracy wrote: >> > > Dominik Brodowski wrote: >> > > > On Sat, Jul 09, 2005 at 12:12:17AM -0500, Bob Tracy wrote: >> > > > >

Re: 2.6.12 vs. /sbin/cardmgr

2005-07-16 Thread Grant Coady
On Sat, 16 Jul 2005 11:36:45 -0500 (CDT), [EMAIL PROTECTED] (Bob Tracy) wrote: rct wrote: Dominik Brodowski wrote: On Sun, Jul 10, 2005 at 03:37:22PM -0500, Bob Tracy wrote: Dominik Brodowski wrote: On Sat, Jul 09, 2005 at 12:12:17AM -0500, Bob Tracy wrote: (/sbin/cardmgr chewing

Re: 2.6.13-rc3-mm1

2005-07-15 Thread Grant Coady
On Fri, 15 Jul 2005 01:36:53 -0700, Andrew Morton <[EMAIL PROTECTED]> wrote: > >ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc3/2.6.13-rc3-mm1/ Did _not_ break Yenta + CardBus on Toshiba ToPIC100: http://scatter.mine.nu/test/linux-2.6/tosh/dmesg-2.6.13-rc3-mm1a.gz

Re: 2.6.13-rc3-mm1

2005-07-15 Thread Grant Coady
On Fri, 15 Jul 2005 01:36:53 -0700, Andrew Morton [EMAIL PROTECTED] wrote: ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc3/2.6.13-rc3-mm1/ Did _not_ break Yenta + CardBus on Toshiba ToPIC100: http://scatter.mine.nu/test/linux-2.6/tosh/dmesg-2.6.13-rc3-mm1a.gz

Re: eepro100/e100 broken in 2.6.13-rc3

2005-07-14 Thread Grant Coady
On Wed, 13 Jul 2005 23:28:15 -0700, Jesse Brandeburg <[EMAIL PROTECTED]> wrote: >On 7/13/05, Mikhail Kshevetskiy <[EMAIL PROTECTED]> wrote: >> symptom >> === >> modprobe e100 >> ifconfig eth0 netmask >> >> result: >> === >> SIOCADDRT: Network is unreachable >> >> There were no such

Re: eepro100/e100 broken in 2.6.13-rc3

2005-07-14 Thread Grant Coady
On Wed, 13 Jul 2005 23:28:15 -0700, Jesse Brandeburg [EMAIL PROTECTED] wrote: On 7/13/05, Mikhail Kshevetskiy [EMAIL PROTECTED] wrote: symptom === modprobe e100 ifconfig eth0 ip netmask netmask result: === SIOCADDRT: Network is unreachable There were no such error in

linux-2.6.13-rc2-mm2: kconfig: warning: defaults for choice values not supported

2005-07-12 Thread Grant Coady
Hi there, Lately in 2.6.13-rc* I've noticed a warning pop up: [EMAIL PROTECTED]:/usr/src/linux-2.6.13-rc2-mm2a$ make menuconfig ... scripts/kconfig/mconf arch/i386/Kconfig net/ipv4/Kconfig:92:warning: defaults for choice values not supported <<== ?? # # using defaults found in .config # Linux

linux-2.6.13-rc2-mm2: kconfig: warning: defaults for choice values not supported

2005-07-12 Thread Grant Coady
Hi there, Lately in 2.6.13-rc* I've noticed a warning pop up: [EMAIL PROTECTED]:/usr/src/linux-2.6.13-rc2-mm2a$ make menuconfig ... scripts/kconfig/mconf arch/i386/Kconfig net/ipv4/Kconfig:92:warning: defaults for choice values not supported == ?? # # using defaults found in .config # Linux

Re: [git patches] IDE update

2005-07-07 Thread Grant Coady
On Thu, 07 Jul 2005 18:32:52 -0400, Mark Lord <[EMAIL PROTECTED]> wrote: > >hdparm can also use O_DIRECT for the -t timing test. I've not been able to get dual channel I/O speed faster than single interface speed, either as 'md' RAID0 or simultaneous reading or writing done the other day: Time

Re: [git patches] IDE update

2005-07-07 Thread Grant Coady
On Thu, 07 Jul 2005 18:32:52 -0400, Mark Lord [EMAIL PROTECTED] wrote: hdparm can also use O_DIRECT for the -t timing test. I've not been able to get dual channel I/O speed faster than single interface speed, either as 'md' RAID0 or simultaneous reading or writing done the other day: Time to

Re: [git patches] IDE update

2005-07-06 Thread Grant Coady
On Tue, 5 Jul 2005 17:51:50 -0700 (PDT), Linus Torvalds <[EMAIL PROTECTED]> wrote: > >Btw, can you try this same thing (or at least a subset) with a large file >on a filesystem? Does that show the same pattern, or is it always just the >raw device? > Sure, take a while longer to vary by block

Re: [git patches] IDE update

2005-07-06 Thread Grant Coady
On Tue, 5 Jul 2005 17:51:50 -0700 (PDT), Linus Torvalds [EMAIL PROTECTED] wrote: Btw, can you try this same thing (or at least a subset) with a large file on a filesystem? Does that show the same pattern, or is it always just the raw device? Sure, take a while longer to vary by block size.

Re: [git patches] IDE update

2005-07-05 Thread Grant Coady
On Tue, 5 Jul 2005 16:21:26 +0200, Jens Axboe <[EMAIL PROTECTED]> wrote: ># gcc -Wall -O2 -o oread oread.c ># time ./oread /dev/hda Executive Summary `` Comparing 'oread' with hdparm -tT on latest 2.4 vs 2.6 stable on various x86 boxen. Performance drops for 2.6, sometimes:

Re: [git patches] IDE update

2005-07-05 Thread Grant Coady
On Tue, 5 Jul 2005 16:21:26 +0200, Jens Axboe [EMAIL PROTECTED] wrote: # gcc -Wall -O2 -o oread oread.c # time ./oread /dev/hda Executive Summary `` Comparing 'oread' with hdparm -tT on latest 2.4 vs 2.6 stable on various x86 boxen. Performance drops for 2.6, sometimes:

Re: [PATCH 2.4] PCI 2/2 update pci.ids (0/2)

2005-04-04 Thread Grant Coady
On Tue, 05 Apr 2005 08:24:20 +1000, Grant Coady <[EMAIL PROTECTED]> wrote: >Hi Marcelo, > >This patch updates pci.ids to latest snapshot, requires patch 1/2 >to compile. gzip'd due to size. Compile and run tested. > >Sign-off-by: Grant Coady <[EMAIL PROTECTE

[PATCH 2.4] PCI 2/2 update pci.ids (0/2)

2005-04-04 Thread Grant Coady
Hi Marcelo, This patch updates pci.ids to latest snapshot, requires patch 1/2 to compile. gzip'd due to size. Compile and run tested. Sign-off-by: Grant Coady <[EMAIL PROTECTED]> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a m

[PATCH 2.4] PCI 1/2 update pci.ids

2005-04-04 Thread Grant Coady
Hi Marcelo, Found the size of pci.ids strings (MAX_NAME_SIZE) needed increasing to accommodate latest pci.ids snapshot, compile failed at 140, succeeded at 150, so I went 160. This patch is required for the update to latest pci.ids snapshot patch 2/2. Signed-off-by: Grant Coady <[EM

[PATCH 2.4] PCI 1/2 update pci.ids

2005-04-04 Thread Grant Coady
Hi Marcelo, Found the size of pci.ids strings (MAX_NAME_SIZE) needed increasing to accommodate latest pci.ids snapshot, compile failed at 140, succeeded at 150, so I went 160. This patch is required for the update to latest pci.ids snapshot patch 2/2. Signed-off-by: Grant Coady [EMAIL

[PATCH 2.4] PCI 2/2 update pci.ids (0/2)

2005-04-04 Thread Grant Coady
Hi Marcelo, This patch updates pci.ids to latest snapshot, requires patch 1/2 to compile. gzip'd due to size. Compile and run tested. Sign-off-by: Grant Coady [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL

Re: [PATCH 2.4] PCI 2/2 update pci.ids (0/2)

2005-04-04 Thread Grant Coady
On Tue, 05 Apr 2005 08:24:20 +1000, Grant Coady [EMAIL PROTECTED] wrote: Hi Marcelo, This patch updates pci.ids to latest snapshot, requires patch 1/2 to compile. gzip'd due to size. Compile and run tested. Sign-off-by: Grant Coady [EMAIL PROTECTED] Sorry about the borked attachment, grab

Re: dmesg verbosity [was Re: AGP bogosities]

2005-03-22 Thread Grant Coady
On Wed, 23 Mar 2005 01:37:29 +0100, Diego Calleja <[EMAIL PROTECTED]> wrote: >El Mon, 14 Mar 2005 14:07:53 -0500, >Lee Revell <[EMAIL PROTECTED]> escribió: > >> I'm really not trolling, but I suspect if we made the boot process less >> verbose, people would start to wonder more about why Linux

Re: Linux 2.4.30-rc1

2005-03-22 Thread Grant Coady
Hi Marcelo, On Fri, 18 Mar 2005 18:55:13 -0300, Marcelo Tosatti <[EMAIL PROTECTED]> wrote: > > >Here goes the first release candidate for v2.4.30. drivers/pci/pci.ids is lagging http://pciids.sourceforge.net/pci.ids by a fair amount, >6300 lines diff I don't know policy on this reference,

Re: Linux 2.4.30-rc1

2005-03-22 Thread Grant Coady
Hi Marcelo, On Fri, 18 Mar 2005 18:55:13 -0300, Marcelo Tosatti [EMAIL PROTECTED] wrote: Here goes the first release candidate for v2.4.30. drivers/pci/pci.ids is lagging http://pciids.sourceforge.net/pci.ids by a fair amount, 6300 lines diff I don't know policy on this reference, just

Re: dmesg verbosity [was Re: AGP bogosities]

2005-03-22 Thread Grant Coady
On Wed, 23 Mar 2005 01:37:29 +0100, Diego Calleja [EMAIL PROTECTED] wrote: El Mon, 14 Mar 2005 14:07:53 -0500, Lee Revell [EMAIL PROTECTED] escribió: I'm really not trolling, but I suspect if we made the boot process less verbose, people would start to wonder more about why Linux takes so much

Re: forkbombing Linux distributions

2005-03-20 Thread Grant Coady
On Mon, 21 Mar 2005 14:27:55 +1100, Peter Chubb <[EMAIL PROTECTED]> wrote: >> "William" == William Beebe <[EMAIL PROTECTED]> writes: > >William> Sure enough, I created the following script and ran it as a >William> non-root user: > >William> #!/bin/bash $0 & $0 & > >There are two approaches

Re: forkbombing Linux distributions

2005-03-20 Thread Grant Coady
On Mon, 21 Mar 2005 14:27:55 +1100, Peter Chubb [EMAIL PROTECTED] wrote: William == William Beebe [EMAIL PROTECTED] writes: William Sure enough, I created the following script and ran it as a William non-root user: William #!/bin/bash $0 $0 There are two approaches to fixing this. 1.

<    1   2