On Mon, 22 Dec 2014 12:43:10 -0800, you wrote:
>On Sat, 20 Dec 2014 23:11:39 -0800 "Nicholas A. Bellinger"
> wrote:
>
>> Just hit the following build failure with CONFIG_AUDIT=y:
>>
>> arch/x86/ia32/audit.c: In function ‘ia32_classify_syscall’:
>> arch/x86/ia32/audit.c:38:7: error:
On Mon, 22 Dec 2014 12:43:10 -0800, you wrote:
On Sat, 20 Dec 2014 23:11:39 -0800 Nicholas A. Bellinger
n...@linux-iscsi.org wrote:
Just hit the following build failure with CONFIG_AUDIT=y:
arch/x86/ia32/audit.c: In function ‘ia32_classify_syscall’:
arch/x86/ia32/audit.c:38:7: error:
Hi there,
I was running machine overnight on 12V battery test, with this simple
kernel compile loop:
grant@itxmini:~/linux/linux-3.7.5a$ while :; do make clean; make -j5; done
Today it was time to shutdown the box ('halt' command) and recharge the battery.
Snapshot of screen:
Hi there,
I was running machine overnight on 12V battery test, with this simple
kernel compile loop:
grant@itxmini:~/linux/linux-3.7.5a$ while :; do make clean; make -j5; done
Today it was time to shutdown the box ('halt' command) and recharge the battery.
Snapshot of screen:
On Fri, 27 Jul 2012 14:45:18 -0700, you wrote:
>On 07/27/2012 12:08 PM, Bill Davidsen wrote:
>> Have you set the io scheduler to deadline on all members of the array?
>> That's kind of "job one" on older kernels.
>>
>
>I have not, thanks for the tip, I'll look into that now.
Plus I disable the
On Fri, 27 Jul 2012 14:45:18 -0700, you wrote:
On 07/27/2012 12:08 PM, Bill Davidsen wrote:
Have you set the io scheduler to deadline on all members of the array?
That's kind of job one on older kernels.
I have not, thanks for the tip, I'll look into that now.
Plus I disable the on-drive
On Sat, 31 Mar 2007 00:31:38 +0200, Oliver Joa <[EMAIL PROTECTED]> wrote:
>Hi,
>
>does anyone have a running Intel DP965LT Mainboard? I can not get this
>Board running. You can see the Problems in the Thread "Corrupt
>XFS-Filesystems on new Hardware and Kernel". Please can you give me a
On Sat, 31 Mar 2007 00:31:38 +0200, Oliver Joa [EMAIL PROTECTED] wrote:
Hi,
does anyone have a running Intel DP965LT Mainboard? I can not get this
Board running. You can see the Problems in the Thread Corrupt
XFS-Filesystems on new Hardware and Kernel. Please can you give me a
running
ecommended for
>users of smbfs with unix extension, since a security fix in 2.4.34
>broke symlinks. Special thanks to Dann Frazier, Santiago Garcia
>and Grant Coady who did the boring work of tracking and fixing the
>problem.
>
>The files are located at the usual places. Pl
with unix extension, since a security fix in 2.4.34
broke symlinks. Special thanks to Dann Frazier, Santiago Garcia
and Grant Coady who did the boring work of tracking and fixing the
problem.
The files are located at the usual places. Please give it some time
to sync between the servers
: *** [kernel] Error 2
Signed-off-by: Grant Coady <[EMAIL PROTECTED]>
---
params.c |4
1 files changed, 4 insertions(+)
--- linux-2.6.20-rc6-mm3/kernel/params.c2007-01-30 16:25:34.0
+1100
+++ linux-2.6.20-rc6-mm3c/kernel/params.c 2007-02-01 07:25:09.0
: *** [kernel] Error 2
Signed-off-by: Grant Coady [EMAIL PROTECTED]
---
params.c |4
1 files changed, 4 insertions(+)
--- linux-2.6.20-rc6-mm3/kernel/params.c2007-01-30 16:25:34.0
+1100
+++ linux-2.6.20-rc6-mm3c/kernel/params.c 2007-02-01 07:25:09.0
+1100
Hi there,
Random .config: 20-rc6-mm3a/002 found the following boo-boo...
From: Grant Coady <[EMAIL PROTECTED]>
Defining protos twice caused:
In file included from kernel/sched.c:39:
include/linux/blkdev.h:928: error: redefinition of 'blk_replug_current_nested'
include/linux/blkdev
Hi there,
Random .config: 20-rc6-mm3a/002 found the following boo-boo...
From: Grant Coady [EMAIL PROTECTED]
Defining protos twice caused:
In file included from kernel/sched.c:39:
include/linux/blkdev.h:928: error: redefinition of 'blk_replug_current_nested'
include/linux/blkdev.h:907: error
Hi there,
Dunno who does IPC so hoping you do ;) (ref.config: 20-rc6-mm2b/048)
Cheers,
Grant.
From: Grant Coady <[EMAIL PROTECTED]>
Fix typos causing compile failure when CONFIG_PROC_FS not set in
ipc/ipc_sysctl.c, compile tested.
ipc/ipc_sysctl.c:107: error: `proc_ipc_doulongvec_
Hi there,
Dunno who does IPC so hoping you do ;) (ref.config: 20-rc6-mm2b/048)
Cheers,
Grant.
From: Grant Coady [EMAIL PROTECTED]
Fix typos causing compile failure when CONFIG_PROC_FS not set in
ipc/ipc_sysctl.c, compile tested.
ipc/ipc_sysctl.c:107: error: `proc_ipc_doulongvec_minmax
On Wed, 17 Jan 2007 22:55:19 +0100, Willy Tarreau <[EMAIL PROTECTED]> wrote:
>Hello Santiago,
>
>On Wed, Jan 17, 2007 at 11:00:30AM +0100, Santiago Garcia Mantinan wrote:
>> Hi!
>>
>> I have discovered a problem with the changes applied to smbfs in 2.4.34 and
>> in the security backports like
On Wed, 17 Jan 2007 22:55:19 +0100, Willy Tarreau [EMAIL PROTECTED] wrote:
Hello Santiago,
On Wed, Jan 17, 2007 at 11:00:30AM +0100, Santiago Garcia Mantinan wrote:
Hi!
I have discovered a problem with the changes applied to smbfs in 2.4.34 and
in the security backports like last Debian's
Hi there,
This is odd:
Index of /pub/linux/kernel/v2.6/snapshots
NameLast modified Size
Parent Directory -
incr/ 13-Dec-2006 22:45-
old/26-Sep-2006 07:41-
Hi there,
This is odd:
Index of /pub/linux/kernel/v2.6/snapshots
NameLast modified Size
Parent Directory -
incr/ 13-Dec-2006 22:45-
old/26-Sep-2006 07:41-
On Tue, 23 Jan 2007 14:12:57 -0700, dann frazier <[EMAIL PROTECTED]> wrote:
>Users have reported a symlink issue with my recent smbfs backport.
>Turns out my backport overlooked a second 2.6 patch w/ the fix:
> http://linux.bkbits.net:8080/linux-2.6/?PAGE=cset=419e7b76CdrmRG_NZ8LKj9DUUBGu1w
>
On Tue, 23 Jan 2007 13:19:37 -0700, dann frazier <[EMAIL PROTECTED]> wrote:
>On Mon, Jan 22, 2007 at 12:03:21AM +0100, Willy Tarreau wrote:
>> Hi Grant !
>>
>> On Mon, Jan 22, 2007 at 09:52:44AM +1100, Grant Coady wrote:
>> > On Fri, 19 Jan 2007 18:05:44 -
On Tue, 23 Jan 2007 13:19:37 -0700, dann frazier [EMAIL PROTECTED] wrote:
On Mon, Jan 22, 2007 at 12:03:21AM +0100, Willy Tarreau wrote:
Hi Grant !
On Mon, Jan 22, 2007 at 09:52:44AM +1100, Grant Coady wrote:
On Fri, 19 Jan 2007 18:05:44 -0700, dann frazier [EMAIL PROTECTED] wrote
On Tue, 23 Jan 2007 14:12:57 -0700, dann frazier [EMAIL PROTECTED] wrote:
Users have reported a symlink issue with my recent smbfs backport.
Turns out my backport overlooked a second 2.6 patch w/ the fix:
http://linux.bkbits.net:8080/linux-2.6/?PAGE=csetREV=419e7b76CdrmRG_NZ8LKj9DUUBGu1w
This
On Mon, 22 Jan 2007 10:36:30 +0100, Santiago Garcia Mantinan <[EMAIL
PROTECTED]> wrote:
>> > As you can see I now can see the symbolic links perfectly and they work as
>> > expected.
>> >
>> > In fact, this patch is working so well that it poses a security risk, as
>> > now
>> > the devices on
On Mon, 22 Jan 2007 10:18:16 +0100, Willy Tarreau <[EMAIL PROTECTED]> wrote:
>Grant, just to be sure, are you really certain that you tried the fixed kernel
>?
>It is possible that you booted a wrong kernel during one of your tests. I'm
>intrigued by the fact that it changed nothing for you and
On Mon, 22 Jan 2007 10:18:16 +0100, Willy Tarreau [EMAIL PROTECTED] wrote:
Grant, just to be sure, are you really certain that you tried the fixed kernel
?
It is possible that you booted a wrong kernel during one of your tests. I'm
intrigued by the fact that it changed nothing for you and that
On Mon, 22 Jan 2007 10:36:30 +0100, Santiago Garcia Mantinan [EMAIL
PROTECTED] wrote:
As you can see I now can see the symbolic links perfectly and they work as
expected.
In fact, this patch is working so well that it poses a security risk, as
now
the devices on my /mnt/dev
On Fri, 19 Jan 2007 18:05:44 -0700, dann frazier <[EMAIL PROTECTED]> wrote:
>On Thu, Jan 18, 2007 at 06:00:40PM -0700, dann frazier wrote:
>Ah, think I see the problem now:
>
>--- kernel-source-2.4.27.orig/fs/smbfs/proc.c 2007-01-19 17:53:57.247695476
>-0700
>+++
On Mon, 22 Jan 2007 00:03:21 +0100, Willy Tarreau <[EMAIL PROTECTED]> wrote:
>Hi Grant !
>
>On Mon, Jan 22, 2007 at 09:52:44AM +1100, Grant Coady wrote:
>> On Fri, 19 Jan 2007 18:05:44 -0700, dann frazier <[EMAIL PROTECTED]> wrote:
>>
>> >On Thu, Jan
On Thu, 18 Jan 2007 05:21:16 +0100, Willy Tarreau <[EMAIL PROTECTED]> wrote:
>Hi Grant !
>
>On Thu, Jan 18, 2007 at 11:09:57AM +1100, Grant Coady wrote:
>(...)
>> >} else {
>> >- mnt->file_mode = mnt-
On Mon, 22 Jan 2007 00:03:21 +0100, Willy Tarreau [EMAIL PROTECTED] wrote:
Hi Grant !
On Mon, Jan 22, 2007 at 09:52:44AM +1100, Grant Coady wrote:
On Fri, 19 Jan 2007 18:05:44 -0700, dann frazier [EMAIL PROTECTED] wrote:
On Thu, Jan 18, 2007 at 06:00:40PM -0700, dann frazier wrote:
Ah
On Thu, 18 Jan 2007 05:21:16 +0100, Willy Tarreau [EMAIL PROTECTED] wrote:
Hi Grant !
On Thu, Jan 18, 2007 at 11:09:57AM +1100, Grant Coady wrote:
(...)
} else {
- mnt-file_mode = mnt-dir_mode = S_IRWXU | S_IRGRP | S_IXGRP |
- S_IROTH
On Fri, 19 Jan 2007 18:05:44 -0700, dann frazier [EMAIL PROTECTED] wrote:
On Thu, Jan 18, 2007 at 06:00:40PM -0700, dann frazier wrote:
Ah, think I see the problem now:
--- kernel-source-2.4.27.orig/fs/smbfs/proc.c 2007-01-19 17:53:57.247695476
-0700
+++ kernel-source-2.4.27/fs/smbfs/proc.c
Hi Jeff,
This patch changes pocket and parallel adaptors to depend on PARPORT
instead of ISA in order to get the option in newer SuperIO based systems.
Tested on x86 (AMD K7). Also applies to 2.6.13-git8 cleanly.
Signed-off-by: Grant Coady <[EMAIL PROTECTED]>
---
Kconfig |8 -
Hi Andrew, Marko,
On Fri, 9 Sep 2005 02:43:36 -0700, Andrew Morton <[EMAIL PROTECTED]> wrote:
>Grant Coady <[EMAIL PROTECTED]> wrote:
>>
>> On Thu, 8 Sep 2005 05:30:42 -0700, Andrew Morton <[EMAIL PROTECTED]> wrote:
>>
>> >
>> >ftp://ftp.k
Hi Andrew, Marko,
On Fri, 9 Sep 2005 02:43:36 -0700, Andrew Morton [EMAIL PROTECTED] wrote:
Grant Coady [EMAIL PROTECTED] wrote:
On Thu, 8 Sep 2005 05:30:42 -0700, Andrew Morton [EMAIL PROTECTED] wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13/2.6.13-mm2/
Hi
Hi Jeff,
This patch changes pocket and parallel adaptors to depend on PARPORT
instead of ISA in order to get the option in newer SuperIO based systems.
Tested on x86 (AMD K7). Also applies to 2.6.13-git8 cleanly.
Signed-off-by: Grant Coady [EMAIL PROTECTED]
---
Kconfig |8
1
On Thu, 8 Sep 2005 05:30:42 -0700, Andrew Morton <[EMAIL PROTECTED]> wrote:
>
>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13/2.6.13-mm2/
Hi Andrew,
After this error:
CC drivers/parport/parport_pc.o
drivers/parport/parport_pc.c:2511: error: via_686a_data causes a
On Thu, 8 Sep 2005 05:30:42 -0700, Andrew Morton [EMAIL PROTECTED] wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13/2.6.13-mm2/
Hi Andrew,
After this error:
CC drivers/parport/parport_pc.o
drivers/parport/parport_pc.c:2511: error: via_686a_data causes a
On Sun, 4 Sep 2005 14:04:46 -0700, Matthew Dharm <[EMAIL PROTECTED]> wrote:
>On Sat, Sep 03, 2005 at 09:53:19PM -0400, Alan Stern wrote:
>> On Sat, 3 Sep 2005, Jan De Luyck wrote:
>>
>> > I've posted in the past about problems with these enclosures - increasing
>> > the
>> > delay seems to fix
On Sun, 4 Sep 2005 14:04:46 -0700, Matthew Dharm [EMAIL PROTECTED] wrote:
On Sat, Sep 03, 2005 at 09:53:19PM -0400, Alan Stern wrote:
On Sat, 3 Sep 2005, Jan De Luyck wrote:
I've posted in the past about problems with these enclosures - increasing
the
delay seems to fix it, albeit
On Thu, 1 Sep 2005 09:03:38 +0200, Jean Delvare <[EMAIL PROTECTED]> wrote:
Hi Jean,
>Hi Grant,
>
>> adm9240 i2c still broken, spamming debug with:
>> (...)
>> Aug 23 18:48:40 peetoo kernel: [ 1591.151834] i2c_adapter i2c-0: Transaction
>> (pre): CNT=08, CMD=2c, ADD=5a, DAT0=00, DAT1=00
>> Aug
On Thu, 1 Sep 2005 09:03:38 +0200, Jean Delvare [EMAIL PROTECTED] wrote:
Hi Jean,
Hi Grant,
adm9240 i2c still broken, spamming debug with:
(...)
Aug 23 18:48:40 peetoo kernel: [ 1591.151834] i2c_adapter i2c-0: Transaction
(pre): CNT=08, CMD=2c, ADD=5a, DAT0=00, DAT1=00
Aug 23 18:48:40
On Mon, 22 Aug 2005 21:30:21 -0700, Andrew Morton <[EMAIL PROTECTED]> wrote:
>
>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc6/2.6.13-rc6-mm2/
>
>- Various updates. Nothing terribly noteworthy.
adm9240 i2c still broken, spamming debug with:
Aug 23 18:48:40 peetoo
On Mon, 22 Aug 2005 21:30:21 -0700, Andrew Morton [EMAIL PROTECTED] wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc6/2.6.13-rc6-mm2/
- Various updates. Nothing terribly noteworthy.
adm9240 i2c still broken, spamming debug with:
Aug 23 18:48:40 peetoo kernel: [
Greetings,
Some more info on removable media oddness. I use both vfat and ext2
format zip disk. Two mountpoints:
/dev/hdc4 /mnt/zipvfatnoauto,user 0 0
/dev/hdc1 /mnt/zip2 ext2noauto,user 0 0
Odd behaviour:
$ mount
Greetings,
Some more info on removable media oddness. I use both vfat and ext2
format zip disk. Two mountpoints:
/dev/hdc4 /mnt/zipvfatnoauto,user 0 0
/dev/hdc1 /mnt/zip2 ext2noauto,user 0 0
Odd behaviour:
$ mount
On Sun, 14 Aug 2005 22:12:55 +1000, Roger Luethi <[EMAIL PROTECTED]> wrote:
@@ -31,7 +31,7 @@
#define APC_BPORT_REG 0x30
#define APC_REGMASK0x01
-define APC_BPMASK 0x03
+#define APC_BPMASK 0x03
Color me skeptical. I've seen some weird bit flips and
On Fri, 12 Aug 2005 09:43:31 +1000, Grant Coady <[EMAIL PROTECTED]> wrote:
Hi there,
Problem was dataloss on extracting kernel source, sometimes only
one character changed. Details on
http://bugsplatter.mine.nu/test/boxen/sempro/
Not the NIC, not reiserfs, not the kernel config, no
On Fri, 12 Aug 2005 09:43:31 +1000, Grant Coady [EMAIL PROTECTED] wrote:
Hi there,
Problem was dataloss on extracting kernel source, sometimes only
one character changed. Details on
http://bugsplatter.mine.nu/test/boxen/sempro/
Not the NIC, not reiserfs, not the kernel config, not even
On Sun, 14 Aug 2005 22:12:55 +1000, Roger Luethi [EMAIL PROTECTED] wrote:
@@ -31,7 +31,7 @@
#define APC_BPORT_REG 0x30
#define APC_REGMASK0x01
-define APC_BPMASK 0x03
+#define APC_BPMASK 0x03
Color me skeptical. I've seen some weird bit flips and data
On Sat, 13 Aug 2005 12:41:33 -0400, Jeff Garzik <[EMAIL PROTECTED]> wrote:
>Grant Coady wrote:
>> I'm tracking a dataloss on box with this chip, finding it difficult
>> to nail a configuration that reliably produces dataloss, sometimes
>> only one bit (e.g. 'c' -
On Sat, 13 Aug 2005 17:10:38 +0200, Karsten Wiese <[EMAIL PROTECTED]> wrote:
>Hi,
>
>this fixes the 'doubled ioapic level interrupt rate' issue I've been
>seeing on a K8T800/AMD64 mainboard.
>It also switches off quirk_via_irq() for the VT8237 southbridge.
I'm tracking a dataloss on box with
On Sat, 13 Aug 2005 17:10:38 +0200, Karsten Wiese [EMAIL PROTECTED] wrote:
Hi,
this fixes the 'doubled ioapic level interrupt rate' issue I've been
seeing on a K8T800/AMD64 mainboard.
It also switches off quirk_via_irq() for the VT8237 southbridge.
I'm tracking a dataloss on box with this chip,
On Sat, 13 Aug 2005 12:41:33 -0400, Jeff Garzik [EMAIL PROTECTED] wrote:
Grant Coady wrote:
I'm tracking a dataloss on box with this chip, finding it difficult
to nail a configuration that reliably produces dataloss, sometimes
only one bit (e.g. 'c' -- 'C') of unpacking kernel source tree
On Sat, 13 Aug 2005 00:21:30 +1000, Masoud Sharbiani <[EMAIL PROTECTED]> wrote:
Can you turn on UDP checksums and try again? That would isolate the
fault between the network or SATA.
It is the second tarball extraction from cache that suffers data
corruption, not a network error. I am in
On Fri, 12 Aug 2005 14:43:42 +0400, "Vladimir V. Saveliev" <[EMAIL PROTECTED]>
wrote:
>> How to test and isolate this error is in NIC driver, SATA driver or
>> filesystem?
>>
>
>Could it be that tarbal on NFS server changed?
>It is not very likely that error in kernel drivers fixed typos in
On Fri, 12 Aug 2005 14:43:42 +0400, Vladimir V. Saveliev [EMAIL PROTECTED]
wrote:
How to test and isolate this error is in NIC driver, SATA driver or
filesystem?
Could it be that tarbal on NFS server changed?
It is not very likely that error in kernel drivers fixed typos in source code.
On Sat, 13 Aug 2005 00:21:30 +1000, Masoud Sharbiani [EMAIL PROTECTED] wrote:
Can you turn on UDP checksums and try again? That would isolate the
fault between the network or SATA.
It is the second tarball extraction from cache that suffers data
corruption, not a network error. I am in
Greetings,
Situation is dataloss with no errors logged.
Test: unpack 2.6.12 tarball from NFS mount source, diff against
previous attempt:
$ diff -Nrup linux-2.6.12.old linux-2.6.12
Binary files linux-2.6.12.old/include/asm-sparc/a.out.h and
linux-2.6.12/include/asm-sparc/a.out.h differ
diff
Greetings,
Situation is dataloss with no errors logged.
Test: unpack 2.6.12 tarball from NFS mount source, diff against
previous attempt:
$ diff -Nrup linux-2.6.12.old linux-2.6.12
Binary files linux-2.6.12.old/include/asm-sparc/a.out.h and
linux-2.6.12/include/asm-sparc/a.out.h differ
diff
Hi Jesper,
On Wed, 3 Aug 2005 23:28:06 +0200, Jesper Juhl <[EMAIL PROTECTED]> wrote:
I like it, just a little concerned about confusing new user with too
many alternative patching methods up front...
>+ This (as usual with Linux and other UNIX like operating systems) can be
>+done in several
Hi Adrian,
On Wed, 3 Aug 2005 13:20:50 +0200, Adrian Bunk <[EMAIL PROTECTED]> wrote:
>>
>> After 300 random builds, add one more error:
>> drivers/acpi/osl.c:261: error: `AmlCode' undeclared (first use in this
>> function)
>> drivers/acpi/osl.c:61:10: empty file name in #include
>
>Please
On Tue, 02 Aug 2005 22:58:59 +1000, Grant Coady <[EMAIL PROTECTED]> wrote:
>Greetings,
>
>Preliminary results, better sample (some hundreds) in a day or so.
After 300 random builds, add one more error:
drivers/acpi/osl.c:261: error: `AmlCode' undeclared (first use in this functio
On Tue, 02 Aug 2005 22:58:59 +1000, Grant Coady [EMAIL PROTECTED] wrote:
Greetings,
Preliminary results, better sample (some hundreds) in a day or so.
After 300 random builds, add one more error:
drivers/acpi/osl.c:261: error: `AmlCode' undeclared (first use in this function)
drivers/acpi/osl.c
Hi Adrian,
On Wed, 3 Aug 2005 13:20:50 +0200, Adrian Bunk [EMAIL PROTECTED] wrote:
After 300 random builds, add one more error:
drivers/acpi/osl.c:261: error: `AmlCode' undeclared (first use in this
function)
drivers/acpi/osl.c:61:10: empty file name in #include
Please exclude builds with
Hi Jesper,
On Wed, 3 Aug 2005 23:28:06 +0200, Jesper Juhl [EMAIL PROTECTED] wrote:
I like it, just a little concerned about confusing new user with too
many alternative patching methods up front...
+ This (as usual with Linux and other UNIX like operating systems) can be
+done in several
Greetings,
Preliminary results, better sample (some hundreds) in a day or so.
2.6.13-rc5
~~
Done processing 70 random builds, from which:
### 6 .configs produced errors
### 4 .configs produced undefs
### 29 .configs produced warnings
# zcat result-report-error-abbrev.gz|cut -d:
Greetings,
Preliminary results, better sample (some hundreds) in a day or so.
2.6.13-rc5
~~
Done processing 70 random builds, from which:
### 6 .configs produced errors
### 4 .configs produced undefs
### 29 .configs produced warnings
# zcat result-report-error-abbrev.gz|cut -d:
Greetings,
Automating random config kernel build testing, for 2.6.13-rc4-mm1:
Done processing 752 random builds, from which:
### 8 .configs produced errors
### 11 .configs produced undefs
### 52 .configs produced warnings
Abbreviated errors (first 2 lines/error):
[EMAIL
Greetings,
Automating random config kernel build testing, for 2.6.13-rc4-mm1:
Done processing 752 random builds, from which:
### 8 .configs produced errors
### 11 .configs produced undefs
### 52 .configs produced warnings
Abbreviated errors (first 2 lines/error):
[EMAIL
On Sun, 31 Jul 2005 09:37:43 -0400, Yani Ioannou <[EMAIL PROTECTED]> wrote:
>On 7/31/05, Pete Zaitcev <[EMAIL PROTECTED]> wrote:
>> Evidently, Yani Ioannou's display is wider than mine.
>
>[EMAIL PROTECTED]" (Thinkpad) ;-). The changes were done by a script I
>wrote which wasn't checking if the
On Sun, 31 Jul 2005 09:37:43 -0400, Yani Ioannou [EMAIL PROTECTED] wrote:
On 7/31/05, Pete Zaitcev [EMAIL PROTECTED] wrote:
Evidently, Yani Ioannou's display is wider than mine.
[EMAIL PROTECTED] (Thinkpad) ;-). The changes were done by a script I
wrote which wasn't checking if the 80 chars
Greetings,
Patch to fix PCI_DEVIEC_ID_APPLE_UNI_N_ATA spelling.
Signed-off-by: Grant Coady <[EMAIL PROTECTED]>
---
drivers/ide/ppc/pmac.c |2 +-
include/linux/pci_ids.h |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff -X dontdiff -Nrup linux-2.6.13-rc4-git2/drive
On Sat, 30 Jul 2005 22:36:28 +0100, Russell King <[EMAIL PROTECTED]> wrote:
>
>Let me qualify that, because it's not 100% fine due to the changes in
>PCMCIA land.
>
>Since PCMCIA cards are detected and drivers bound at boot time, we no
Without an unbind/eject option? Implies reboot to remove a
On Fri, 29 Jul 2005 18:21:05 -0400, Jeff Garzik <[EMAIL PROTECTED]> wrote:
>
>[speaking to the audience] I wouldn't mind if someone did a pass
>through pci_ids.h and removed all the constants that are not being used.
> If constants are not being used, it's IMHO more appropriate to store
>that
On Fri, 29 Jul 2005 18:21:05 -0400, Jeff Garzik [EMAIL PROTECTED] wrote:
[speaking to the audience] I wouldn't mind if someone did a pass
through pci_ids.h and removed all the constants that are not being used.
If constants are not being used, it's IMHO more appropriate to store
that info
On Sat, 30 Jul 2005 22:36:28 +0100, Russell King [EMAIL PROTECTED] wrote:
Let me qualify that, because it's not 100% fine due to the changes in
PCMCIA land.
Since PCMCIA cards are detected and drivers bound at boot time, we no
Without an unbind/eject option? Implies reboot to remove a
Greetings,
Patch to fix PCI_DEVIEC_ID_APPLE_UNI_N_ATA spelling.
Signed-off-by: Grant Coady [EMAIL PROTECTED]
---
drivers/ide/ppc/pmac.c |2 +-
include/linux/pci_ids.h |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff -X dontdiff -Nrup linux-2.6.13-rc4-git2/drivers/ide
On Fri, 29 Jul 2005 23:52:39 -0400, Jeff Garzik <[EMAIL PROTECTED]> wrote:
>
>However you did your search, you did it wrong. The very first two
>entries I tried had zero uses:
>
>[EMAIL PROTECTED] linux-2.6]$ grepsrc ICH7_22
>./include/linux/pci_ids.h:#define PCI_DEVICE_ID_INTEL_ICH7_22 0x27e0
On Fri, 29 Jul 2005 18:21:05 -0400, Jeff Garzik <[EMAIL PROTECTED]> wrote:
>
>[speaking to the audience] I wouldn't mind if someone did a pass
>through pci_ids.h and removed all the constants that are not being used.
Only these seem not referenced by source:
PCI_CLASS_SYSTEM_PCI_HOTPLUG
On Fri, 29 Jul 2005 18:40:46 -0300, Mauro Carvalho Chehab <[EMAIL PROTECTED]>
wrote:
drivers/media/video/zr36120.c
drivers/media/video/zr36120_i2c.c
drivers/media/video/zr36120_mem.c
>>
>>
>> Being discussed on the V4L list
> It seems that nobody are interested on maintaining
On Fri, 29 Jul 2005 18:40:46 -0300, Mauro Carvalho Chehab [EMAIL PROTECTED]
wrote:
drivers/media/video/zr36120.c
drivers/media/video/zr36120_i2c.c
drivers/media/video/zr36120_mem.c
Being discussed on the V4L list
It seems that nobody are interested on maintaining it. No answer from
On Fri, 29 Jul 2005 18:21:05 -0400, Jeff Garzik [EMAIL PROTECTED] wrote:
[speaking to the audience] I wouldn't mind if someone did a pass
through pci_ids.h and removed all the constants that are not being used.
Only these seem not referenced by source:
PCI_CLASS_SYSTEM_PCI_HOTPLUG
On Fri, 29 Jul 2005 23:52:39 -0400, Jeff Garzik [EMAIL PROTECTED] wrote:
However you did your search, you did it wrong. The very first two
entries I tried had zero uses:
[EMAIL PROTECTED] linux-2.6]$ grepsrc ICH7_22
./include/linux/pci_ids.h:#define PCI_DEVICE_ID_INTEL_ICH7_22 0x27e0
[EMAIL
On Thu, 28 Jul 2005 07:22:25 -0300, Marcelo Tosatti <[EMAIL PROTECTED]> wrote:
>>
>> Breaks Toshiba laptop: hard lockup --> what is on screen is same as
>> working dmesg up to point: "host/uhci.c: detected 2 port"
>>
>> Same .config as for 2.4.31-hf3 or 2.4.32-pre1
>>
Hi there,
More info on Toshiba laptop lockup with 2.4.32-pre2:
/var/log/syslog:
Jul 28 22:59:33 tosh kernel: Linux version 2.4.32-pre2 ([EMAIL PROTECTED]) (gcc
version 3.3.5) #4 Thu Jul 28 22:57:05 EST 2005
Jul 28 22:59:33 tosh kernel: BIOS-e820: - 0009fc00
(usable)
On Wed, 27 Jul 2005 05:05:12 -0300, Marcelo Tosatti <[EMAIL PROTECTED]> wrote:
>
>Here goes another -pre, after a long period.
Breaks Toshiba laptop: hard lockup --> what is on screen is same as
working dmesg up to point: "host/uhci.c: detected 2 port"
Same .config as for 2.4.31-hf3 or
On Wed, 27 Jul 2005 05:05:12 -0300, Marcelo Tosatti [EMAIL PROTECTED] wrote:
Here goes another -pre, after a long period.
Breaks Toshiba laptop: hard lockup -- what is on screen is same as
working dmesg up to point: host/uhci.c: detected 2 port
Same .config as for 2.4.31-hf3 or 2.4.32-pre1
Hi there,
More info on Toshiba laptop lockup with 2.4.32-pre2:
/var/log/syslog:
Jul 28 22:59:33 tosh kernel: Linux version 2.4.32-pre2 ([EMAIL PROTECTED]) (gcc
version 3.3.5) #4 Thu Jul 28 22:57:05 EST 2005
Jul 28 22:59:33 tosh kernel: BIOS-e820: - 0009fc00
(usable)
On Thu, 28 Jul 2005 07:22:25 -0300, Marcelo Tosatti [EMAIL PROTECTED] wrote:
Breaks Toshiba laptop: hard lockup -- what is on screen is same as
working dmesg up to point: host/uhci.c: detected 2 port
Same .config as for 2.4.31-hf3 or 2.4.32-pre1
http://scatter.mine.nu/test/linux-2.4/tosh/
On Wed, 27 Jul 2005 15:58:48 -0400, "linux-os \(Dick Johnson\)" <[EMAIL
PROTECTED]> wrote:
>
>I think the XOR thread was started by somebody as a ruse or
>a joke. XOR will always destroy the value of an operand.
You missed the part where somebody checked assembler output and
found compiler
On Wed, 27 Jul 2005 15:58:48 -0400, linux-os \(Dick Johnson\) [EMAIL
PROTECTED] wrote:
I think the XOR thread was started by somebody as a ruse or
a joke. XOR will always destroy the value of an operand.
You missed the part where somebody checked assembler output and
found compiler optimised
On Tue, 26 Jul 2005 20:34:10 -0600, Robert Hancock <[EMAIL PROTECTED]> wrote:
>Karim Yaghmour wrote:
>> That being said, shouldn't there be a way for the kernel to refuse to
>> use this hd if it's not getting enough power. I don't know enough about
>> USB to say, but isn't there something more
On Tue, 26 Jul 2005 21:39:26 +0200, Michel Bouissou <[EMAIL PROTECTED]> wrote:
>
>Yes, but it doesn't tell us why kernels 2.4x felt perfectly happy with the old
>BIOS...
You turned off 4k stacks? I have a Via KM400 chipset box locked
up a few times, once under 2.4.31-hf2 after 4.5 hours
On Tue, 26 Jul 2005 21:39:26 +0200, Michel Bouissou [EMAIL PROTECTED] wrote:
Yes, but it doesn't tell us why kernels 2.4x felt perfectly happy with the old
BIOS...
You turned off 4k stacks? I have a Via KM400 chipset box locked
up a few times, once under 2.4.31-hf2 after 4.5 hours compiling
On Tue, 26 Jul 2005 20:34:10 -0600, Robert Hancock [EMAIL PROTECTED] wrote:
Karim Yaghmour wrote:
That being said, shouldn't there be a way for the kernel to refuse to
use this hd if it's not getting enough power. I don't know enough about
USB to say, but isn't there something more elegant
On Sun, 24 Jul 2005 23:27:22 +0200, Adrian Bunk <[EMAIL PROTECTED]> wrote:
>
>You should edit init/Kconfig to disallow CONFIG_CLEAN_COMPILE=n, since
>any errors you see with CONFIG_BROKEN=y aren't interesting.
Straight over the top of my head yesterday :) Is the following
what you had in mind?
On Sun, 24 Jul 2005 23:27:22 +0200, Adrian Bunk [EMAIL PROTECTED] wrote:
You should edit init/Kconfig to disallow CONFIG_CLEAN_COMPILE=n, since
any errors you see with CONFIG_BROKEN=y aren't interesting.
Straight over the top of my head yesterday :) Is the following
what you had in mind?
1 - 100 of 140 matches
Mail list logo
