* [ALSA - driver 0000002]: 1.0.2: intel8x0.c build problem
From: noreply @ 2004-01-27 19:48 UTC (permalink / raw)
To: alsa-devel
The following bug has been CLOSED
======================================================================
http://bugtrack.alsa-project.org/alsa-bug/bug_view_advanced_page.php?bug_id=0000002
======================================================================
Reporter: ZlatkO
Handler:
======================================================================
Project: ALSA - driver
Bug ID: 2
Category: PCI - intel8x0
Reproducibility: always
Severity: block
Priority: normal
Status: closed
Distribution: Slackware 8.1
Kernel Version: 2.4.24
======================================================================
Date Submitted: 01-27-2004 20:11 CET
Last Modified: 01-27-2004 20:48 CET
======================================================================
Summary: 1.0.2: intel8x0.c build problem
Description:
alsa-driver-1.0.2 doesn't build out of the box with gcc-2.95.3. The
attached patch fixes the problem.
======================================================================
----------------------------------------------------------------------
perex - 01-27-2004 20:47 CET
----------------------------------------------------------------------
I have regenerated the alsa-driver package with this fix.
It is dated:
Jan 27 14:15 alsa-driver-1.0.2.tar.bz2
----------------------------------------------------------------------
perex - 01-27-2004 20:48 CET
----------------------------------------------------------------------
The updated package is available at the ALSA FTP site.
Bug History
Date Modified Username Field Change
======================================================================
01-27-04 20:11 ZlatkO New Bug
01-27-04 20:11 ZlatkO File Added: alsa-driver-1.0.2.diff
01-27-04 20:47 perex Bugnote Added: 0000002
01-27-04 20:48 perex Bugnote Added: 0000003
01-27-04 20:48 perex Status new => closed
======================================================================
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
^ permalink raw reply
* Re: reiserfsprogs 3.6.11 compile failure. 3.6.12-pre3 compiles ok
From: Vitaly Fertman @ 2004-01-27 19:47 UTC (permalink / raw)
To: Philippe Gramoullé, reiserfs
In-Reply-To: <20040127151346.674f4843@philou.gramoulle.local>
On Tuesday 27 January 2004 17:13, Philippe Gramoullé wrote:
> Hi,
>
> While installing a box to start playing with reiser4 i got a compile error
> while trying to build reiserfsprogs 3.6.11. This the first time this
> happens as i had already compiled it successfully on other Debian Unstable
> boxes.
>
> I guess i may be because of a newly installed development package that
> breaks some macro.
>
> Reiserfsprogs 3.6.12-pre3 compiles fine.
> misc.c: In function `count_blocks':
> misc.c:431: error: parse error before '[' token
> make[1]: *** [misc.o] Error 1
> make[1]: Leaving directory `/usr/src/reiserfsprogs-3.6.11/lib'
> make: *** [all-recursive] Error 1
> boogie:/usr/src/reiserfsprogs-3.6.11#
I guess that you do not have BLKGETSIZE64 defined now and our
own definition had a bug, fixed in 3.6.12-pre1.
--
Thanks,
Vitaly Fertman
^ permalink raw reply
* [ALSA - driver 0000002]: 1.0.2: intel8x0.c build problem
From: noreply @ 2004-01-27 19:47 UTC (permalink / raw)
To: alsa-devel
A BUGNOTE has been added to this bug.
======================================================================
http://bugtrack.alsa-project.org/alsa-bug/bug_view_advanced_page.php?bug_id=0000002
======================================================================
Reporter: ZlatkO
Handler:
======================================================================
Project: ALSA - driver
Bug ID: 2
Category: PCI - intel8x0
Reproducibility: always
Severity: block
Priority: normal
Status: new
Distribution: Slackware 8.1
Kernel Version: 2.4.24
======================================================================
Date Submitted: 01-27-2004 20:11 CET
Last Modified: 01-27-2004 20:47 CET
======================================================================
Summary: 1.0.2: intel8x0.c build problem
Description:
alsa-driver-1.0.2 doesn't build out of the box with gcc-2.95.3. The
attached patch fixes the problem.
======================================================================
----------------------------------------------------------------------
perex - 01-27-2004 20:47 CET
----------------------------------------------------------------------
I have regenerated the alsa-driver package with this fix.
It is dated:
Jan 27 14:15 alsa-driver-1.0.2.tar.bz2
Bug History
Date Modified Username Field Change
======================================================================
01-27-04 20:11 ZlatkO New Bug
01-27-04 20:11 ZlatkO File Added: alsa-driver-1.0.2.diff
01-27-04 20:47 perex Bugnote Added: 0000002
======================================================================
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
^ permalink raw reply
* Re: [PATCH] volatile may be needed in rwsem
From: Joe Korty @ 2004-01-27 19:43 UTC (permalink / raw)
To: David Howells; +Cc: akpm, linux-kernel
In-Reply-To: <23376.1075231180@redhat.com>
On Tue, Jan 27, 2004 at 07:19:40PM +0000, David Howells wrote:
>> 'flags' should be declared volatile as rwsem_down_failed_common() spins
>> waiting for this to change. Untested.
>
> Is it though? Does this fix an error?
>
> The thing is, we make a function call inside of the loop:
>
> /* wait to be given the lock */
> for (;;) {
> if (!waiter->flags)
> break;
> schedule();
> set_task_state(tsk, TASK_UNINTERRUPTIBLE);
> }
>
> Which might preclude that need. I'm not entirely sure, though... it's one of
> those compiler black magic things.
>
> I suppose it can't hurt...
>
> David
Hi David,
I misspoke. The potentially failing spin is in __down_write and
__down_read in lib/rwsem-spinlock.c, not in rwsem_down_failed_common.
The problem is is that 'flags' is on the callee's stack and is thus
subject to be optimized out of the loop if the compiler is smart enough
to discover that it is on the stack. Apparently gcc is not yet smart
enough but that doesn't mean it won't be so soon.
Joe
^ permalink raw reply
* Re: linux-2.6.1 x86_64 : STACK_TOP and text/data
From: dada1 @ 2004-01-27 19:45 UTC (permalink / raw)
To: Andi Kleen; +Cc: linux-kernel
In-Reply-To: <20040127202930.6c29bbcf.ak@suse.de>
Andi Kleen wrote:
>
>You're right. Thanks for reporting this. This seems to be a 2.6
>specific bug, it didn't happen in 2.4.
>
>I will fix it. It should definitely use PAGE_OFFSET for 64bit
>processes and 4GB for !3GB 32bit processes.
>
>-Andi
>
>
>
>
Another thing I noticed in last glibc CVS (nptl)
Thread stacks are also allocated in the 1GB quadrant :
nptl/sysdeps/x86_64/pthreaddef.h
/* We prefer to have the stack allocated in the low 4GB since this
allows faster context switches. */
#define ARCH_MAP_FLAGS MAP_32BIT
Is this really true ?
Is memory allocated in the low 4GB is faster on x86_64 (64bit kernel,
64 bit user prog ?)
Thank you
Eric Dumazet
^ permalink raw reply
* Re: S1 could work
From: Dirk Meul @ 2004-01-27 19:45 UTC (permalink / raw)
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
In-Reply-To: <20040122102912.GA355-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
Am Do, den 22.01.2004 schrieb Pavel Machek um 11:29:
> Switching consoles doing S1 is not neccessary on working hardware. You
> might want to simply comment it out.
Can you give me a pointer where switching is done? I could not find it.
Trying to enter S1 when pdnsd is running aborts standby. But pdnsd is
killed by entering S1 or S3 (didn't know S4 because it didn't work for
me). Entering S3 with a running pdnsd works.
By entering S1 audio from my tv-card will not stopped.
Resuming from S3 will only work if i unload all sound modules. But i'm
not able to reload them successfully:
Starting ALSA (version 1.0.1):AC'97 0 does not respond - RESET
AC'97 0 access is not valid [0xffffffff], removing mixer.
EMU10K1_Audigy: probe of 0000:00:0d.0 failed with error -5
emu10k1 bt87x.
Restoring ALSA mixer settings ... done.
Without sound module unloading there is:
Kernel panic: Fatal exception in interrupt
Best regards,
--
/"\
Dirk Meul \ / ASCII Ribbon Campaign
dirk.meul-vA1bhqPz9FBZXbeN9DUtxg@public.gmane.org X Against HTML Mail
/ \
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
^ permalink raw reply
* RE: Marvell MV64340 documentation
From: Sergey Podstavin @ 2004-01-27 19:44 UTC (permalink / raw)
To: Matthew Dharm; +Cc: 'Pavel Kiryukhin', linux-mips@linux-mips.org
In-Reply-To: <000d01c3e50d$4a6e8b40$7200a8c0@internal.momenco.com>
It's OK, don't worry.
Sergey.
On Tue, 2004-01-27 at 22:39, Matthew Dharm wrote:
> I can't really answer something that specific without violating the NDA.
> Sorry.
>
> Matt
>
> --
> Matthew D. Dharm Senior Software Designer
> Momentum Computer Inc. 1815 Aston Ave. Suite 107
> (760) 431-8663 X-115 Carlsbad, CA 92008-7310
> Momentum Works For You www.momenco.com
>
>
> > -----Original Message-----
> > From: linux-mips-bounce@linux-mips.org
> > [mailto:linux-mips-bounce@linux-mips.org] On Behalf Of Sergey
> > Podstavin
> > Sent: Tuesday, January 27, 2004 10:45 AM
> > To: Matthew Dharm
> > Cc: Pavel Kiryukhin; linux-mips@linux-mips.org
> > Subject: Marvell MV64340 documentation
> >
> >
> > Hello Matthew!
> >
> > Could you write me what do bits mean in the interrupt cause
> > registers for MV64340 Ethernet? I need to handle them in the
> > interrupt handler for the Gigabit Ethernet in the driver.
> >
> > Best wishes,
> > Sergey Podstavin,
> > software engineer.
> >
> >
>
>
^ permalink raw reply
* Re: [PATCH] kgdb-x86_64-support.patch for 2.6.2-rc1-mm3
From: Andi Kleen @ 2004-01-27 19:43 UTC (permalink / raw)
To: jim.houston; +Cc: akpm, george, amitkale, linux-kernel
In-Reply-To: <1075232116.1020.326.camel@new.localdomain>
On 27 Jan 2004 14:35:17 -0500
Jim Houston <jim.houston@comcast.net> wrote:
> I was looking for a way to get the old behavior where the
> the effect was controlled by an OR of the two options.
Hmm, probably something like (untested):
config DEBUG_INFO
bool "Compile kernel with debug information"
default y if KGDB
help
bla bla bla
I have no strong preference to either way.
-Andi
^ permalink raw reply
* [PATCH] crypto/sha256.c crypto/sha512.c
From: Jean-Luc Cooke @ 2004-01-27 19:39 UTC (permalink / raw)
To: linux-kernel
Optimized the choice and majority fuctions a bit.
Patch:
http://jlcooke.ca/lkml/faster_sha2.patch
Test suite:
http://jlcooke.ca/lkml/faster_sha2.c
build with:
gcc -O3 -s faster_sha2.c -o faster_sha2
JLC
--
http://www.certainkey.com
Suite 4560 CTTC
1125 Colonel By Dr.
Ottawa ON, K1S 5B6
^ permalink raw reply
* Re: [parisc-linux] Using PAT_IO calls for PCI config space reads and writes.
From: Matthew Wilcox @ 2004-01-27 19:42 UTC (permalink / raw)
To: Grant Grundler; +Cc: Matthew Wilcox, parisc-linux, Naresh Kumar
In-Reply-To: <20040127192212.GC28476@colo.lackof.org>
On Tue, Jan 27, 2004 at 12:22:12PM -0700, Grant Grundler wrote:
> On Tue, Jan 27, 2004 at 06:43:45PM +0000, Matthew Wilcox wrote:
> > > 2. Can these changes be propagated to 2.6 also?
> >
> > You should be developing against 2.6 in the first place.
>
> Should - but they don't about 2.6. At least not yet.
> I'll deal with forward porting the changes once your comments are integrated.
> Naresh, can you take care of that and resubmit?
Their development would actually go a lot easier if they worked on 2.6.
Compare lba_pci.c between 2.4 and 2.6 -- the new one is a *lot* easier
to work on.
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
^ permalink raw reply
* Re: linux-2.4-benh compiling error
From: David Kimdon @ 2004-01-27 19:40 UTC (permalink / raw)
To: Christian Kujau; +Cc: linuxppc-dev
In-Reply-To: <4016760E.50009@g-house.de>
On Tue, Jan 27, 2004 at 03:30:38PM +0100, Christian Kujau wrote:
>
>
> hi,
>
> i was about to compile linux-2.4-benh (fresh tree fetched via rsync)
> when errors occured:
I don't know what your build system is, but I had the same error on
Debian unstable, the bug (and a patch) is here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=228852
-David
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply
* Re: [Jfs-discussion] md raid + jfs + jfs_fsck
From: Florian Huber @ 2004-01-27 19:39 UTC (permalink / raw)
To: JFS-Discussion; +Cc: Linux-Kernel, shaggy
In-Reply-To: <1075231718.21763.28.camel@shaggy.austin.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 673 bytes --]
On Tue, 2004-01-27 at 20:28, Dave Kleikamp wrote:
> I wonder if JFS is having trouble getting the partition size. Can you
> run jfs_fsck with the -v flag to see what part of the superblock it
> doesn't like?
The current device is: /dev/md2
Open(...READ/WRITE EXCLUSIVE...) returned rc = 0
Incorrect jlog length detected in the superblock (P).
Incorrect jlog length detected in the superblock (S).
Superblock is corrupt and cannot be repaired
since both primary and secondary copies are corrupt.
--
Florian Huber
Key ID: D9D50EA2
Fingerprint: 0241 C329 E355 9B94 8D34 F637 4EB9 1B1D D9D5 0EA2
BOFH Excuse #147:
Party-bug in the Aloha protocol.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply
* Re: [PATCH] kgdb-x86_64-support.patch for 2.6.2-rc1-mm3
From: Jim Houston @ 2004-01-27 19:35 UTC (permalink / raw)
To: Andi Kleen; +Cc: akpm, george, amitkale, linux-kernel
In-Reply-To: <20040127190251.4edb873d.ak@suse.de>
On Tue, 2004-01-27 at 13:02, Andi Kleen wrote:
> On 27 Jan 2004 12:43:20 -0500
> Jim Houston <jim.houston@comcast.net> wrote:
> > arch/x86_64/Kconfig
> > arch/x86_64/Kconfig.kgdb
> > We used a different approach to selecting DEBUG_INFO.
> > I was not really happy with the way select DEBUG_INFO worked.
>
> You reverted it back?
>
> What I did was to change all not really kgdb specific CONFIG_KGDB uses in
> the main kernel with CONFIG_DEBUG_INFO (mostly CFI support). I don't feel
> strongly about it, but this way there is no reference to an unknown
> config symbol in mainline. Also DEBUG_INFO including CFI makes sense I think.
Hi Andi,
I'm using CONFIG_DEBUG_INFO, but I used a different mechanism to
select it when KGDB is selected. I'm still learning to speak Kconfig.
My patch:
config KGDB
bool "Include kgdb kernel debugger"
depends on DEBUG_KERNEL
select DEBUG_INFO
help
If you say Y here, the system will be compiled with the debug
Your patch:
config DEBUG_INFO
bool "Compile kernel with debug information" if !KGDB
default y
Using "select DEBUG_INFO" selects the option and makes the input box
on xconfig disappear. The line describing the option remains, perhaps
leaving a user wondering why this line doesn't have an input box.
With your version, the DEBUG_INFO option disappears when KGDB forces
it on.
I was looking for a way to get the old behavior where the
the effect was controlled by an OR of the two options.
Jim Houston - Concurrent Computer Corp.
^ permalink raw reply
* RE: Marvell MV64340 documentation
From: Matthew Dharm @ 2004-01-27 19:39 UTC (permalink / raw)
To: podstavin; +Cc: 'Pavel Kiryukhin', linux-mips
In-Reply-To: <1075229071.4058.46.camel@podstavin.dev.rtsoft.ru>
I can't really answer something that specific without violating the NDA.
Sorry.
Matt
--
Matthew D. Dharm Senior Software Designer
Momentum Computer Inc. 1815 Aston Ave. Suite 107
(760) 431-8663 X-115 Carlsbad, CA 92008-7310
Momentum Works For You www.momenco.com
> -----Original Message-----
> From: linux-mips-bounce@linux-mips.org
> [mailto:linux-mips-bounce@linux-mips.org] On Behalf Of Sergey
> Podstavin
> Sent: Tuesday, January 27, 2004 10:45 AM
> To: Matthew Dharm
> Cc: Pavel Kiryukhin; linux-mips@linux-mips.org
> Subject: Marvell MV64340 documentation
>
>
> Hello Matthew!
>
> Could you write me what do bits mean in the interrupt cause
> registers for MV64340 Ethernet? I need to handle them in the
> interrupt handler for the Gigabit Ethernet in the driver.
>
> Best wishes,
> Sergey Podstavin,
> software engineer.
>
>
^ permalink raw reply
* RE: Marvell MV64340 documentation
From: Matthew Dharm @ 2004-01-27 19:39 UTC (permalink / raw)
To: podstavin; +Cc: 'Pavel Kiryukhin', linux-mips
In-Reply-To: <1075229071.4058.46.camel@podstavin.dev.rtsoft.ru>
I can't really answer something that specific without violating the NDA.
Sorry.
Matt
--
Matthew D. Dharm Senior Software Designer
Momentum Computer Inc. 1815 Aston Ave. Suite 107
(760) 431-8663 X-115 Carlsbad, CA 92008-7310
Momentum Works For You www.momenco.com
> -----Original Message-----
> From: linux-mips-bounce@linux-mips.org
> [mailto:linux-mips-bounce@linux-mips.org] On Behalf Of Sergey
> Podstavin
> Sent: Tuesday, January 27, 2004 10:45 AM
> To: Matthew Dharm
> Cc: Pavel Kiryukhin; linux-mips@linux-mips.org
> Subject: Marvell MV64340 documentation
>
>
> Hello Matthew!
>
> Could you write me what do bits mean in the interrupt cause
> registers for MV64340 Ethernet? I need to handle them in the
> interrupt handler for the Gigabit Ethernet in the driver.
>
> Best wishes,
> Sergey Podstavin,
> software engineer.
>
>
^ permalink raw reply
* [ALSA - lib 0000003]: alsa-lib-1.0.2: 'make check' fails
From: noreply @ 2004-01-27 19:39 UTC (permalink / raw)
To: alsa-devel
The following NEW bug has been ADDED.
======================================================================
http://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000003
======================================================================
Reporter: ZlatkO
Handler:
======================================================================
Project: ALSA - lib
Bug ID: 3
Category: general
Reproducibility: always
Severity: trivial
Priority: normal
Status: new
======================================================================
Date Submitted: 01-27-2004 20:39 CET
Last Modified: 01-27-2004 20:39 CET
======================================================================
Summary: alsa-lib-1.0.2: 'make check' fails
Description:
'make check' fails on a Slackware 8.1 system with gcc-2.95.3 due to three
minor problems (one missing #define/#include statement, two misplaced
variable delarations) in test/code.c and test/queue_timer.c. The attached
patch fixes these problems.
======================================================================
Bug History
Date Modified Username Field Change
======================================================================
01-27-04 20:39 ZlatkO New Bug
01-27-04 20:39 ZlatkO File Added: alsa-lib-1.0.2.diff
======================================================================
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
^ permalink raw reply
* InterScan NT Alert
From: postmaster-lX1WLSqV685oZSuCWFJQuMGzyFzmqZ/k @ 2004-01-27 19:38 UTC (permalink / raw)
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
Sender, InterScan has detected virus(es) in your e-mail attachment.
Date: Wed, 28 Jan 2004 01:08:44 +0530
Method: Mail
From: <acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
To: <jgarzik-7Aj/b8uzpy6AmYF/tR2SNQ@public.gmane.org>
File: file.zip
Action: clean failed - deleted
Virus: WORM_MIMAIL.R
begin 666 InterScan_Disclaimer.txt
M5&AE(&EN9F]R;6%T:6]N(&-O;G1A:6YE9"!I;B!T:&ES(&5L96-T<F]N:6,@
M;65S<V%G92!A;F0-0q2iP0p74hk@public.gmane.org(&%T=&%C:&UE;G1S('1O('1H:7,@;65S<V%G92!A
M<F4@#0II;G1E;F1E9"!F;W(@=&AE(&5X8VQU<VEV92!U<V4@;V8@=&AE(&%D
M9')E<W-E92AS*2!A;F0@;6%Y(&-O;G1A:6X-2ZHtrH1AIUU@public.gmane.org]N9FED96YT:6%L(&]R('!R
M:79I;&5G960@:6YF;W)M871I;VXN#0I)9B!Y;W4-4u3rHeVEGOc@public.gmane.org)E(&YO="!T:&4@:6YT
M96YD960@<F5C:7!I96YT+"!P;&5A<V4@;F]T:69Y('1H92!S96YD97(@870@
M4V%M<W5N9R!%;&5C=')O($UE8VAA;FEC<R!O<@T*861M:6Y <V5M<V]F=&EN
M9&EA+7-A;7-U;F<N8V]M(&EM;65D:6%T96QY(&%N9"!D97-T<F]Y(&%L;"!C
M;W!I97,@;V8@=&AI<R!M97-S86=E(&%N9"!A;GD-Yg1PUgpZdv8@public.gmane.org;65N=',N#0I!
M;GD@=6YA=71H;W)I>F5D(')E=FEE=RP@=7-E+"!D:7-C;&]S=7)E+"!D:7-S
M96UI;F%T:6]N+"!F;W)W87)D:6YG+"!P<FEN=&EN9R!O<B!C;W!Y:6YG(&]F
M('1H:7,@96UA:6P@;W(@86YY#0IA8W1I;VX@=&%K96X@:6X@<F5L:6%N8V4@
M;VX@=&AI<R!E+6UA:6P@:7,@<W1R:6-T;'D@<')O:&EB:71E9"!A;F0@;6%Y
5(&)E('5N;&%W9G5L+-wPuJ0ROkVbw@public.gmane.org*#0H-"@T*
end
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
^ permalink raw reply
* Re: RFC: Trailing blanks in source files
From: Paulo Marques @ 2004-01-27 19:31 UTC (permalink / raw)
To: David Weinehall; +Cc: Joseph D. Wagner, Andi Kleen, Rui Saraiva, linux-kernel
In-Reply-To: <20040127191358.GI20879@khan.acc.umu.se>
David Weinehall wrote:
> On Tue, Jan 27, 2004 at 12:51:34PM -0600, Joseph D. Wagner wrote:
>
>>>It seems that many files [1] in the Linux source have lines with
>>>trailing blank (space and tab) characters and some even have formfeed
>>>characters. Obviously these blank characters aren't necessary.
>>>
>>Actually, they are necessary.
>>
>>http://www.gnu.org/prep/standards_23.html
>>http://www.gnu.org/prep/standards_24.html
>>
>
> Let me quote CodingStyle:
>
> "First off, I'd suggest printing out a copy of the GNU coding standards,
> and NOT read it. Burn them, it's a great symbolic gesture."
>
> That's how much relevance GNU's coding standards have to the kernel.
>
And even if we did use GNU's coding standards (knock on wood :), where is the
part that requires *trailing* spaces?
Only in languages like "whitespace" ( http://compsoc.dur.ac.uk/whitespace/ ) the
trailing spaces have any meaning :)
--
Paulo Marques - www.grupopie.com
"In a world without walls and fences who needs windows and gates?"
^ permalink raw reply
* Re: Synaptics problems with kernel 2.6.x
From: Florian Huber @ 2004-01-27 19:31 UTC (permalink / raw)
To: linux-kernel; +Cc: Richard Kuryk
In-Reply-To: <1075171320.25088.46.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 535 bytes --]
On Tue, 2004-01-27 at 03:42, Richard Kuryk wrote:
> I have been reading prior messages so I know there are issues with power
> management and ACPI and I have tried them on/off it doesn't really
> help.
Do you have a tool that polls apm/acpi info very often? (like gkrellm
apci plugin). I switched this off and now my tp is workling correctly.
HTH
--
Florian Huber
Key ID: D9D50EA2
Fingerprint: 0241 C329 E355 9B94 8D34 F637 4EB9 1B1D D9D5 0EA2
BOFH Excuse #379:
We've picked COBOL as the language of choice.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply
* Re: [patch] Re: Kernels > 2.6.1-mm3 do not boot. - REALLY SOLVED
From: Eric @ 2004-01-27 19:31 UTC (permalink / raw)
To: Andi Kleen
Cc: Andrew Morton, stoffel, Valdis.Kletnieks, bunk, cova,
linux-kernel
In-Reply-To: <20040127181554.GA41917@colin2.muc.de>
On Tuesday 27 January 2004 12:15, Andi Kleen wrote:
> On Tue, Jan 27, 2004 at 12:37:43AM -0600, Eric wrote:
> > On Monday 26 January 2004 23:50, Andrew Morton wrote:
> > > Eric <eric@cisu.net> wrote:
> > > > YES. I finally have a working 2.6.2-rc1-mm3 booted kernel.
> > > > Lets review folks---
> > > > reverted -funit-at-a-time
> > > > patched test_wp_bit so exception tables are sorted sooner
> > > > reverted md-partition patch
> > >
> > > The latter two are understood, but the `-funit-at-a-time' problem is
> > > not.
> > >
> > > Can you plesae confirm that restoring only -funit-at-a-time again
> > > produces a crashy kernel? And that you are using a flavour of gcc-3.3?
> > > If so, I guess we'll need to only enable it for gcc-3.4 and later.
> >
> > Yes, confirmed. My version of gcc, I just sent you adding the
> > -funit-at-a-time hung after uncompressing the kernel. I booted a
> > secondary kernel, recompiled without it and all was fine again. Confirmed
> > non-boot for 2.6.2-rc1-mm3 but without a doubt for all kernels previous
> > where -funit-at-a-time is active in the makefile.
>
> Ok, found it. This patch should fix it. The top level asm in process.c
> assumed that the section was .text, but that is not guaranteed in a
> funit-at-a-time compiler. It ended up in the setup section and messed up
> the argument parsing. This bug could have hit with any compiler,
> it was just plain luck that it worked with newer gcc 3.3 and 3.4.
>
> Please test if it fixes your problem.
Yes. Confirmed. Lets review again.
-removed -funit from makefile
patched to fix exception table sorting
reverted md-partition-patch
BOOTS
add -funit again
FAILS
leave -funit active in makefile
patch with patch below
BOOTS
This patch is confirmed to fix the boot with -funit-at-a-time with
2.6.2-rc1-mm2 with gcc(below)
Thanks so much for everyones attention in the matter.
bot403@eric:~> gcc -v
Reading specs from /usr/lib/gcc-lib/i486-suse-linux/3.3/specs
Configured with: ../configure --enable-threads=posix --prefix=/usr
--with-local-prefix=/usr/local --infodir=/usr/share/info
--mandir=/usr/share/man --libdir=/usr/lib
--enable-languages=c,c++,f77,objc,java,ada --disable-checking --enable-libgcj
--with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib
--with-system-zlib --enable-shared --enable-__cxa_atexit i486-suse-linux
Thread model: posix
gcc version 3.3 20030226 (prerelease) (SuSE Linux)
> Andrew, please merge it if the bug is confirmed to be fixed.
>
> -Andi
>
> diff -u linux-2.6.2rc1mm3-test/arch/i386/kernel/process.c-o
> linux-2.6.2rc1mm3-test/arch/i386/kernel/process.c ---
> linux-2.6.2rc1mm3-test/arch/i386/kernel/process.c-o 2004-01-27
> 02:26:39.000000000 +0100 +++
> linux-2.6.2rc1mm3-test/arch/i386/kernel/process.c 2004-01-27
> 19:09:41.131460832 +0100 @@ -253,13 +253,15 @@
> * the "args".
> */
> extern void kernel_thread_helper(void);
> -__asm__(".align 4\n"
> +__asm__(".section .text\n"
> + ".align 4\n"
> "kernel_thread_helper:\n\t"
> "movl %edx,%eax\n\t"
> "pushl %edx\n\t"
> "call *%ebx\n\t"
> "pushl %eax\n\t"
> - "call do_exit");
> + "call do_exit\n"
> + ".previous");
>
> /*
> * Create a kernel thread
-------------------------
Eric Bambach
Eric at cisu dot net
-------------------------
^ permalink raw reply
* Re: PATCH: (as177) Add class_device_unregister_wait() and platform_device_unregister_wait() to the driver model core
From: Russell King @ 2004-01-27 19:32 UTC (permalink / raw)
To: Roman Zippel
Cc: Linus Torvalds, Alan Stern, Greg KH, Kernel development list,
Patrick Mochel
In-Reply-To: <Pine.LNX.4.58.0401261435160.7855@serv>
On Mon, Jan 26, 2004 at 05:22:41PM +0100, Roman Zippel wrote:
> For example pci drivers currently do something like:
>
> int init()
> {
> if (pci_register_driver(drv) < 0)
> pci_unregister_driver(drv);
> }
>
> void exit()
> {
> pci_unregister_driver(drv);
> }
I'd like to take this opportunity to mention that the above is buggy
as written. If pci_register_driver() fails, the device_driver structure
is not registered, and therefore pci_unregister_driver() may cause
Bad Things(tm) to happen.
(and yes, pci_module_init() is buggy as it currently stands, and I
believe GregKH has a patch in his queue from the stability freeze
from yours truely to fix it.)
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
^ permalink raw reply
* Re: linux-2.6.1 x86_64 : STACK_TOP and text/data
From: Andi Kleen @ 2004-01-27 19:29 UTC (permalink / raw)
To: dada1; +Cc: linux-kernel
In-Reply-To: <4016B493.9050404@cosmosbay.com>
On Tue, 27 Jan 2004 19:57:23 +0100
dada1 <dada1@cosmosbay.com> wrote:
> Andi Kleen wrote:
>
> > STACK_TOP is only for 32bit a.out executables running on x86-64
> >
> >ELF 32bit and 64bit programs use different defaults.
> >
> >-Andi
> >
> >
> >
> >
> Hi Andi
>
> I'm afraid not Andi
You're right. Thanks for reporting this. This seems to be a 2.6
specific bug, it didn't happen in 2.4.
I will fix it. It should definitely use PAGE_OFFSET for 64bit
processes and 4GB for !3GB 32bit processes.
-Andi
^ permalink raw reply
* Re: [Jfs-discussion] md raid + jfs + jfs_fsck
From: Dave Kleikamp @ 2004-01-27 19:28 UTC (permalink / raw)
To: Florian Huber; +Cc: linux-kernel, JFS Discussion
In-Reply-To: <1075230933.11207.84.camel@suprafluid>
On Tue, 2004-01-27 at 13:15, Florian Huber wrote:
> Hello MLs,
> today I switched from no-raid to linux kernel software raid 1 on a jfs
> and a ext3 partition. Both are working fine, but jfs_fsck reports an
> error on the jfs md device (md2 <-- hda3+hdc3):
>
> Superblock is corrupt and cannot be repaired
> since both primary and secondary copies are corrupt.
>
> Did I miss something? jfs_fsck runs without any error on hda3 and hdc3,
> but fails on md2.
I wonder if JFS is having trouble getting the partition size. Can you
run jfs_fsck with the -v flag to see what part of the superblock it
doesn't like?
> I'm using the 2.6.2-rc2 kernel with raid autodetection.
>
> TIA
> Florian
Thanks,
Shaggy
--
David Kleikamp
IBM Linux Technology Center
^ permalink raw reply
* Re: 2.6.2-rc1 / ACPI sleep / irqbalance / kirqd / pentium 4 HT problems on Uniwill N258SA0
From: Nigel Cunningham @ 2004-01-27 19:30 UTC (permalink / raw)
To: Bart Samwel
Cc: Pavel Machek, Huw Rogers, Linux Kernel Mailing List, linux-laptop
In-Reply-To: <401685F9.6000904@samwel.tk>
Hi.
I have SMP working under 2.4, and am not far away from having it for
2.6. There is just one file that needs changing, but I need to learn
some x86 assembly first. If someone already knows x86 assembly and wants
to get it going first, I'll happily apply the patch.
Regards,
Nigel
> > Well, no sleep developers have SMP or HT machines, AFAICT.
--
My work on Software Suspend is graciously brought to you by
LinuxFund.org.
^ permalink raw reply
* Re: [OFFTOPIC] "smack the penguin"
From: "Fernando O. Korndörfer" @ 2004-01-27 20:28 UTC (permalink / raw)
Cc: linux-kernel
In-Reply-To: <4012FA6D.6040101@netvis.co.uk>
Hail!
1216.2, but no screenshot :(
Neil Ferguson wrote:
> Nuno Alexandre wrote:
>
>> On Sat, 24 Jan 2004 21:41:19 +0000 (WET) Marcos D. Marado Torres wrote:
>>
>>
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>>
>>> 1213.6, as a matter of fact ;-)
>>> Well, I guess that with this URL you pro's will get really higher
>>> hi-scores...
>>>
>>
>>
>> hi.
>> thx for the url.
>>
>> 1214.9 here :)
>> http://ikaro.homepage.dk/pingu.jpg
>>
>>
>
> A student pushing the boundaries, with 1215.8 :-)
>
> http://www.netvis.co.uk/pingu3_swf.png
>
> Cheers,
>
> Neil
--
Fernando Korndorfer
fok@quatro.com.br
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.