Re: linux-2.4.3-ac14 spinlock problem?

[Feng Xian]

David,

Actually it happened only once. then I upgrade my kernel to 2.4.5. problem
disappeared. I just hope this maybe a known problem.

Thanks.

Alex


On Wed, 30 May 2001, David Howells wrote:

>
> > I was running something on my Dell dual p3 box (optiplex gx300). my kernel
> > is linux-2.4.3-ac14. I got the following message:
>
> How often did this message occur?
>
> > __rwsem_do_wake(): wait_list unexpectedly empty
> > [4191] c5966f60 = { 0001 })
> > kenel BUG at rwsem.c:99!
> > invalid operand: 
> > CPU:1
> > EIP:0010:[]
> > EFLAGS: 00010282
> > kenel BUG at /usr/src/2.4.3-ac14/include/asm/spinlock.h:104!
> >
> >
> > I upgrade the kernel to 2.4.5, no such problem any more.
>
> I suspect something else corrupted the rw-semaphore structure, but that's very
> hard to prove unless you catch it in the act. If it happens again with any
> frequency, you might want to try turning on rwsem debugging.
>
> David
>

-- 
Feng Xian
   _o) .~.  (o_
   /\\ /V\  //\
  _\_V// \\ V_/_
 /(   )\
  ^^-^^
   ALEX

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: linux-2.4.3-ac14 spinlock problem?

[David Howells]

> I was running something on my Dell dual p3 box (optiplex gx300). my kernel
> is linux-2.4.3-ac14. I got the following message:

How often did this message occur?

> __rwsem_do_wake(): wait_list unexpectedly empty
> [4191] c5966f60 = { 0001 })
> kenel BUG at rwsem.c:99!
> invalid operand: 
> CPU:1
> EIP:0010:[]
> EFLAGS: 00010282
> kenel BUG at /usr/src/2.4.3-ac14/include/asm/spinlock.h:104!
> 
> 
> I upgrade the kernel to 2.4.5, no such problem any more.

I suspect something else corrupted the rw-semaphore structure, but that's very
hard to prove unless you catch it in the act. If it happens again with any
frequency, you might want to try turning on rwsem debugging.

David
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: linux-2.4.3-ac14 spinlock problem?

[David Howells]

 I was running something on my Dell dual p3 box (optiplex gx300). my kernel
 is linux-2.4.3-ac14. I got the following message:

How often did this message occur?

 __rwsem_do_wake(): wait_list unexpectedly empty
 [4191] c5966f60 = { 0001 })
 kenel BUG at rwsem.c:99!
 invalid operand: 
 CPU:1
 EIP:0010:[c0236b99]
 EFLAGS: 00010282
 kenel BUG at /usr/src/2.4.3-ac14/include/asm/spinlock.h:104!
 
 
 I upgrade the kernel to 2.4.5, no such problem any more.

I suspect something else corrupted the rw-semaphore structure, but that's very
hard to prove unless you catch it in the act. If it happens again with any
frequency, you might want to try turning on rwsem debugging.

David
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: linux-2.4.3-ac14 spinlock problem?

[Feng Xian]

David,

Actually it happened only once. then I upgrade my kernel to 2.4.5. problem
disappeared. I just hope this maybe a known problem.

Thanks.

Alex


On Wed, 30 May 2001, David Howells wrote:


  I was running something on my Dell dual p3 box (optiplex gx300). my kernel
  is linux-2.4.3-ac14. I got the following message:

 How often did this message occur?

  __rwsem_do_wake(): wait_list unexpectedly empty
  [4191] c5966f60 = { 0001 })
  kenel BUG at rwsem.c:99!
  invalid operand: 
  CPU:1
  EIP:0010:[c0236b99]
  EFLAGS: 00010282
  kenel BUG at /usr/src/2.4.3-ac14/include/asm/spinlock.h:104!
 
 
  I upgrade the kernel to 2.4.5, no such problem any more.

 I suspect something else corrupted the rw-semaphore structure, but that's very
 hard to prove unless you catch it in the act. If it happens again with any
 frequency, you might want to try turning on rwsem debugging.

 David


-- 
Feng Xian
   _o) .~.  (o_
   /\\ /V\  //\
  _\_V// \\ V_/_
 /(   )\
  ^^-^^
   ALEX

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

linux-2.4.3-ac14 spinlock problem?

[Feng Xian]

Hi,

I was running something on my Dell dual p3 box (optiplex gx300). my kernel
is linux-2.4.3-ac14. I got the following message:


__rwsem_do_wake(): wait_list unexpectedly empty
[4191] c5966f60 = { 0001 })
kenel BUG at rwsem.c:99!
invalid operand: 
CPU:1
EIP:0010:[]
EFLAGS: 00010282
kenel BUG at /usr/src/2.4.3-ac14/include/asm/spinlock.h:104!


I upgrade the kernel to 2.4.5, no such problem any more.

Any idea?

Alex


-- 
Feng Xian
   _o) .~.  (o_
   /\\ /V\  //\
  _\_V// \\ V_/_
 /(   )\
  ^^-^^
   ALEX

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

linux-2.4.3-ac14 spinlock problem?

[Feng Xian]

Hi,

I was running something on my Dell dual p3 box (optiplex gx300). my kernel
is linux-2.4.3-ac14. I got the following message:


__rwsem_do_wake(): wait_list unexpectedly empty
[4191] c5966f60 = { 0001 })
kenel BUG at rwsem.c:99!
invalid operand: 
CPU:1
EIP:0010:[c0236b99]
EFLAGS: 00010282
kenel BUG at /usr/src/2.4.3-ac14/include/asm/spinlock.h:104!


I upgrade the kernel to 2.4.5, no such problem any more.

Any idea?

Alex


-- 
Feng Xian
   _o) .~.  (o_
   /\\ /V\  //\
  _\_V// \\ V_/_
 /(   )\
  ^^-^^
   ALEX

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Oops during fsck.ext2, Linux 2.4.3

[Håvard Lygre]

I had my computer go down hard the other day, while it was sitting
idle (some time during the night).  This was while in X, so no
messages was visible on the screen, and nothing was recorded in the
logs.

When rebooting, Linux oopsed several times while running ext2.fsck,
requiring reboots every time, on different partitions attached to
different IDE-controllers.

I only recorded one of the oopses (by hand, so there may be mistakes
although I did proof-read it).

Since then the kernel has been rock-solid, and I have been running the
same 2.4.3-kernel since then.

I am running Debian unstable, current every day.


The system is a dual Pentium III 800EB on an MSI 6321 mainboard (MSI
694D Pro AI), only IDE drives:


Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: chipset revision 16
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt82c686a (rev 22) IDE UDMA66 controller on pci00:07.1
ide0: BM-DMA at 0x9000-0x9007, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x9008-0x900f, BIOS settings: hdc:pio, hdd:pio
PDC20267: IDE controller on PCI bus 00 dev 60
PDC20267: chipset revision 2
PDC20267: not 100% native mode: will probe irqs later
PDC20267: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
ide2: BM-DMA at 0xac00-0xac07, BIOS settings: hde:DMA, hdf:pio
ide3: BM-DMA at 0xac08-0xac0f, BIOS settings: hdg:pio, hdh:DMA
hda: IBM-DTLA-307030, ATA DISK drive
hde: WDC WD200BB-00AUA1, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide2 at 0x9c00-0x9c07,0xa002 on irq 18
hda: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=3737/255/63, UDMA(66)
hde: 39102336 sectors (20020 MB) w/2048KiB Cache, CHS=38792/16/63, UDMA(100)
Partition check:
 /dev/ide/host0/bus0/target0/lun0: p1 p2 p3 < p5 p6 >
 /dev/ide/host2/bus0/target0/lun0: [PTBL] [2434/255/63] p1


/dev/hde has since been repartitioned.


Any other information available upon request.  Config attached at
end of mail.


Unable to handle kernel NULL pointer dereference at virtual address 0020
c0131d80
*pde = 
Oops: 
CPU:1
EIP:0010:[]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010206
eax: 0306   ebx:    ecx: d6dd4800   edx: 0008
esi: 0004f141   edi:    ebp:    esp: d7b41f28
ds: 0018   es: 0018ss: 0018
Process fsck.ext2 (pid: 45, stackpage=d7b41000)
Stack: 0306 c64e4fa0 0306    03060306 c01382a0
   0306  d7c05e00 d7e89920 d7b4f860 d7d928e0  c0138352
   c64e4fa0  c0131231 d7b4f860 d7c05e00 d7c05e00 0805c658 
Call Trace: [] [] [] [] [] 
[]
Code: 8b 7b 20 0f b7 44 24 1a 66 39 43 0c 0f 85 9e 00 00 00 8b 43

>>EIP; c0131d80 <__invalidate_buffers+50/138>   <=
Trace; c01382a0 
Trace; c0138352 
Trace; c0131231 
Trace; c01301e2 
Trace; c0130247 
Trace; c0106f5b 
Code;  c0131d80 <__invalidate_buffers+50/138>
 <_EIP>:
Code;  c0131d80 <__invalidate_buffers+50/138>   <=
   0:   8b 7b 20  mov0x20(%ebx),%edi   <=
Code;  c0131d83 <__invalidate_buffers+53/138>
   3:   0f b7 44 24 1amovzwl 0x1a(%esp,1),%eax
Code;  c0131d88 <__invalidate_buffers+58/138>
   8:   66 39 43 0c   cmp%ax,0xc(%ebx)
Code;  c0131d8c <__invalidate_buffers+5c/138>
   c:   0f 85 9e 00 00 00 jneb0 <_EIP+0xb0> c0131e30 
<__invalidate_buffers+100/138>
Code;  c0131d92 <__invalidate_buffers+62/138>
  12:   8b 43 00  mov0x0(%ebx),%eax



 .config



-- 
Håvard Lygre, [EMAIL PROTECTED]
Bergen IT-Teknikk ANS, Conrad Mohrsvei 11, 5068 Bergen
Tlf: 55 360773  Fax: 55 360774

Oops during fsck.ext2, Linux 2.4.3

[Håvard Lygre]

I had my computer go down hard the other day, while it was sitting
idle (some time during the night).  This was while in X, so no
messages was visible on the screen, and nothing was recorded in the
logs.

When rebooting, Linux oopsed several times while running ext2.fsck,
requiring reboots every time, on different partitions attached to
different IDE-controllers.

I only recorded one of the oopses (by hand, so there may be mistakes
although I did proof-read it).

Since then the kernel has been rock-solid, and I have been running the
same 2.4.3-kernel since then.

I am running Debian unstable, current every day.


The system is a dual Pentium III 800EB on an MSI 6321 mainboard (MSI
694D Pro AI), only IDE drives:


Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: chipset revision 16
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt82c686a (rev 22) IDE UDMA66 controller on pci00:07.1
ide0: BM-DMA at 0x9000-0x9007, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x9008-0x900f, BIOS settings: hdc:pio, hdd:pio
PDC20267: IDE controller on PCI bus 00 dev 60
PDC20267: chipset revision 2
PDC20267: not 100% native mode: will probe irqs later
PDC20267: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
ide2: BM-DMA at 0xac00-0xac07, BIOS settings: hde:DMA, hdf:pio
ide3: BM-DMA at 0xac08-0xac0f, BIOS settings: hdg:pio, hdh:DMA
hda: IBM-DTLA-307030, ATA DISK drive
hde: WDC WD200BB-00AUA1, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide2 at 0x9c00-0x9c07,0xa002 on irq 18
hda: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=3737/255/63, UDMA(66)
hde: 39102336 sectors (20020 MB) w/2048KiB Cache, CHS=38792/16/63, UDMA(100)
Partition check:
 /dev/ide/host0/bus0/target0/lun0: p1 p2 p3  p5 p6 
 /dev/ide/host2/bus0/target0/lun0: [PTBL] [2434/255/63] p1


/dev/hde has since been repartitioned.


Any other information available upon request.  Config attached at
end of mail.


Unable to handle kernel NULL pointer dereference at virtual address 0020
c0131d80
*pde = 
Oops: 
CPU:1
EIP:0010:[c0131d80]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010206
eax: 0306   ebx:    ecx: d6dd4800   edx: 0008
esi: 0004f141   edi:    ebp:    esp: d7b41f28
ds: 0018   es: 0018ss: 0018
Process fsck.ext2 (pid: 45, stackpage=d7b41000)
Stack: 0306 c64e4fa0 0306    03060306 c01382a0
   0306  d7c05e00 d7e89920 d7b4f860 d7d928e0  c0138352
   c64e4fa0  c0131231 d7b4f860 d7c05e00 d7c05e00 0805c658 
Call Trace: [c01382a0] [c0138352] [c0131231] [c01301e2] [c0130247] 
[c0106f5b]
Code: 8b 7b 20 0f b7 44 24 1a 66 39 43 0c 0f 85 9e 00 00 00 8b 43

EIP; c0131d80 __invalidate_buffers+50/138   =
Trace; c01382a0 blkdev_put+74/114
Trace; c0138352 blkdev_close+12/18
Trace; c0131231 fput+39/e8
Trace; c01301e2 filp_close+b2/bc
Trace; c0130247 sys_close+5b/74
Trace; c0106f5b system_call+33/38
Code;  c0131d80 __invalidate_buffers+50/138
 _EIP:
Code;  c0131d80 __invalidate_buffers+50/138   =
   0:   8b 7b 20  mov0x20(%ebx),%edi   =
Code;  c0131d83 __invalidate_buffers+53/138
   3:   0f b7 44 24 1amovzwl 0x1a(%esp,1),%eax
Code;  c0131d88 __invalidate_buffers+58/138
   8:   66 39 43 0c   cmp%ax,0xc(%ebx)
Code;  c0131d8c __invalidate_buffers+5c/138
   c:   0f 85 9e 00 00 00 jneb0 _EIP+0xb0 c0131e30 
__invalidate_buffers+100/138
Code;  c0131d92 __invalidate_buffers+62/138
  12:   8b 43 00  mov0x0(%ebx),%eax



 .config



-- 
Håvard Lygre, [EMAIL PROTECTED]
Bergen IT-Teknikk ANS, Conrad Mohrsvei 11, 5068 Bergen
Tlf: 55 360773  Fax: 55 360774

Re: Linux 2.4.3-ac14

[Matthias Andree]

On Wed, 25 Apr 2001, Alan Cox wrote:

> 2.4.3-ac10
> o Fix reboot notifier unregister in aic7xxx   (Arjan van de Ven)

> 2.4.3-ac6
> o Merge aic7xxx driver 6.11   (Justin Gibbs)

I tried vanilla 2.4.3 yesterday, on a box which has one DPTA (IDE) drive
and two Seagate SCSI drives along with a CD-ROM attached to some 2940.
Linux 2.2.19 is fine on that box, but 2.4.3 tells something about an
abort that returned some value and fails to detect what Linux 2.2 calls
/dev/sda. Reset -> Inquiry delay in kernel is 10,000 ms.

Does any of the aforementioned merges remedy detection problems or
should I try a current 2.4.3-ac version and file a full report in case
the problem persists?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac14

[Matthias Andree]

On Wed, 25 Apr 2001, Alan Cox wrote:

 2.4.3-ac10
 o Fix reboot notifier unregister in aic7xxx   (Arjan van de Ven)

 2.4.3-ac6
 o Merge aic7xxx driver 6.11   (Justin Gibbs)

I tried vanilla 2.4.3 yesterday, on a box which has one DPTA (IDE) drive
and two Seagate SCSI drives along with a CD-ROM attached to some 2940.
Linux 2.2.19 is fine on that box, but 2.4.3 tells something about an
abort that returned some value and fails to detect what Linux 2.2 calls
/dev/sda. Reset - Inquiry delay in kernel is 10,000 ms.

Does any of the aforementioned merges remedy detection problems or
should I try a current 2.4.3-ac version and file a full report in case
the problem persists?
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Linux 2.4.3-ac14

[Alan Cox]

Oops forgot to update the text. This one is of course not just compile fixes

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Linux 2.4.3-ac14

[Alan Cox]

ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/

Intermediate diffs are available from

http://www.bzimage.org

This isnt a proper release as such, it should just deal with most of the 
compile failure/symbol failure problems.

2.4.3-ac14
o   Merge read-only veritas VxFS support(Christoph Hellwig)
o   Fix missing return in broken_apm_power  (Alex Riesen)
o   Remove bogus rwsem hacks from usbdevice_fs.h(Alex Riesen)
o   Fix umount/sync_inodes race (Al Viro)
o   Make new xircom driver report when promisc used (Arjan van de Ven)
o   Fix acenic PCI flag set up  (Phil Copeland)
o   Make nfs smart about passing max file sizes (Trond Myklebust)
o   Add initrd support to User Mode Linux   (Jeff Dike)
o   Fix timer irq race in User Mode Linux   (Jeff Dike)
o   Fix UML for semaphore changes   (Jeff Dike)
o   Update thw W9966 parallel port camera driver(Jakob Kemi)
o   Further dmfe SMP fixups (Tobias Ringstrom)
o   Kernel manual pages in man9 (Tim Waugh)
o   Work around BIOSes that implement E801 sizing
but don't implement the CX/DX values part   (Michael Miller)
o   Fix atp driver build(Arjan van de Ven)
o   Fix irda poll handling  (Dag Brattli)
o   Remove unused buggy pdc202xx code   (Arjan van de Ven)
o   Clean up iphase ATM (Arnaldo Carvalho
de Melo)
o   Setup slave PDC20265 controller on fasttrak (Arjan van de Ven)
as normal IDE
o   Add __init/__initdata to most net driver   (Andrzej Krzysztofowicz)
version info
o   SDDR09 config entry was missing (Phil Stracchino)
o   Configure.help NFS updates (Andrzej Krzysztofowicz)
o   Netfilter updates   (Rusty Russell and co)
o   Update 2.4 ipconfig to support dhcp (Eric Biederman)
o   es1371 setup updates/error check/pci bits   (Marcus Meissner)
o   Fix buzzing ymfpci  (Nick Brown)
o   Update nm256 audio driver   (Marcus Meissner)
o   Blacklist updates   (Arjan van de Ven)

2.4.3-ac13
o   Switch to NOVERS symbols for rwsem  (me)
| Called from asm blocks so they can't be versioned
o   Fix gcc 2.95 building on rwsem  (Niels Jensen)
o   Fix cmsfs build (Andrzej Krzysztofowicz)
o   Fix rio build/HZ setup  (Andrzej Krzysztofowicz)
o   Fix PPP filtering dependancy in config  (Andrzej Krzysztofowicz)

2.4.3-ac12
o   Rewrite the i2o post handling code to fix   (me)
DMA memory scribbles
o   Handle IOP constipation in the i2o_block layer  (me)
o   Fix bugs in the i2o table query causing reboots (me)
in i2o_proc on the DPT card
o   Add quirks for i2o cards that handle large I/O  (me)
queues badly [Promise supertrak100]
o   Add cache heuristics to the I2O block driver(me)
| We don't cache large writes (assume seq)
| We writeback small writes (random, metadata)
o   Disable use of writeback caching if there is(me)
no battery backup
o   Merge Linus 2.4.4pre6
o   Further semaphore fixes (David Howells)
o   Correct 'void main' to 'int main' in rtc doc(Jesper Juhl)
o   Hopefully fix bugtraq reported netfilter ftp
flaw
o   Fix unistd.h for ARM(Russell King)
o   Fix pre-emption of rt tasks (Nigel Gamble)
o   Fix revalidation bugs in cciss/cpqarray (Charles White)
when rereading partitions
o   Acenic updates  (Jes Sorensen)
o   Fix MAINTAINERS sort order  (David Woodhouse)
o   Restore DVDRAM fix with cdrom init fix too  (Jens Axboe)
o   Fix irda disconnect timeout bug (Dag Brattli)
o   Experimentally reap dead swap harder(Dave Miller)
o   Remove dead low mtu checks from drivers (Arnaldo Carvalho de
 Melo)
o   Add missing sk_chk_filter export(Byeong-ryeol Kim)
o   Quieten pci printks, send them to log   (Arjan van de Ven)
o   Hopefully fix fastrak oops  (me)

2.4.3-ac11
o   Merge Linus 2.4.4pre5
o   Back out problem dvdram changes
o   Make reiserfs use daemonize (Chris Mason)
o   Fix lvm map buglet  (Jens Axboe)
o   tms380 driver fixes 

Re: Linux 2.4.3-ac12

[Byeong-ryeol Kim]

On Mon, 23 Apr 2001, Byeong-ryeol Kim wrote:

> On Sun, 22 Apr 2001, Alan Cox wrote:
>
> > > > Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
> > > > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> > > > symbol rwsem_up_write_wake
> > > > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> > > > symbol rwsem_down_write_failed
> > >
> > > Same thing with tdfx.o...
> >
> > "Works for me" as ever. What configuration options are you using. This sounds
> > like some of the code is built with each kind of semaphore.
> 
>
> I use 2 PCs at home. One is unnamed desktop - AMD K6-II+, ASUS P/I-P55T2P4
> rev. 3.10, 128 MB EDO RAM, etc.), the other is IBM ThinkPad 600X(Pentium III
> 500, 192 MB PC100 RAM, etc.). But, the result of depmod under 2.4.3-ac12
> are the same.
> I use gcc-2.95.3 release + recommended patch about atexit from libc-alpha list
> which seemed to be applied in gcc-2.95.4 CVS tree).


I retried to compile 2.4.3-ac12 with Red Hat's 2.96-81(that of 7.1) without
the patch previously applied.
This time, I noticed strange thing.(I guess, it would not be a compiler
problem).
While doing 'depmod -ae -F /boot/System.map-2.4.3-ac12 2.4.3-ac12'
there was no error as far as rwsem_* is concerned, but when doing simply
'depmod -ae', the result was the same as before.( the same kernel
configuration, modutils is original 2.4.5-1 fetched from kernel site).

1) 'depmod -ae -F /boot/system.map-2.4.3-ac12 2.4.3-ac12'

depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/net/aironet4500_card.o
depmod: __bad_udelay
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/cmsfs/cms.o
depmod: get_hardsect_size

2) 'depmod -ae'

depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/arch/i386/kernel/microcode.o
depmod: rwsem_up_write_wake
depmod: rwsem_up_read_wake
depmod: rwsem_down_write_failed
depmod: rwsem_down_read_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/gamma.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/i810.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/mga.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/r128.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/tdfx.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/net/aironet4500_card.o
depmod: __bad_udelay
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_base.o
depmod: rwsem_up_read_wake
depmod: rwsem_down_read_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_crtc2.o
depmod: rwsem_up_write_wake
depmod: rwsem_up_read_wake
depmod: rwsem_down_write_failed
depmod: rwsem_down_read_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_g450.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_maven.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/binfmt_aout.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/cmsfs/cms.o
depmod: get_hardsect_size


>
> #
> # Automatically generated make config: don't edit
> #
> CONFIG_X86=y
> CONFIG_ISA=y
> # CONFIG_SBUS is not set
> CONFIG_UID16=y
>
> #
> # Code maturity level options
> #
> CONFIG_EXPERIMENTAL=y
>
> #
> # Loadable module support
> #
> CONFIG_MODULES=y
> CONFIG_MODVERSIONS=y
> CONFIG_KMOD=y
>
> #
> # Processor type and features
> #
> # CONFIG_M386 is not set
> # CONFIG_M486 is not set
> # CONFIG_M586 is not set
> # CONFIG_M586TSC is not set
> # CONFIG_M586MMX is not set
> # CONFIG_M686 is not set
> # CONFIG_MPENTIUMIII is not set
> # CONFIG_MPENTIUM4 is not set
> CONFIG_MK6=y
> # CONFIG_MK7 is not set
> # CONFIG_MCRUSOE is not set
> # CONFIG_MWINCHIPC6 is not set
> # CONFIG_MWINCHIP2 is not set
> # CONFIG_MWINCHIP3D is not set
> # CONFIG_MCYRIXIII is not set
> CONFIG_X86_WP_WORKS_OK=y
> 

Re: Linux 2.4.3-ac12

[Byeong-ryeol Kim]

On Sun, 22 Apr 2001, Alan Cox wrote:

> > > Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
> > > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> > > symbol rwsem_up_write_wake
> > > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> > > symbol rwsem_down_write_failed
> >
> > Same thing with tdfx.o...
>
> "Works for me" as ever. What configuration options are you using. This sounds
> like some of the code is built with each kind of semaphore.


I use 2 PCs at home. One is unnamed desktop - AMD K6-II+, ASUS P/I-P55T2P4
rev. 3.10, 128 MB EDO RAM, etc.), the other is IBM ThinkPad 600X(Pentium III
500, 192 MB PC100 RAM, etc.). But, the result of depmod under 2.4.3-ac12
are the same.
I use gcc-2.95.3 release + recommended patch about atexit from libc-alpha list
which seemed to be applied in gcc-2.95.4 CVS tree).
BTW, I applied the follwing patch posted to this list:

--- 2.4.3-ac12/include/asm-i386/compiler.h  Sat Apr 21 22:56:03 2001
+++ 2.4.3-ac12/include/asm-i386/compiler.h  Sat Apr 21 22:56:43 2001
@@ -0,0 +1,13 @@
+#ifndef __I386_COMPILER_H
+#define __I386_COMPILER_H 1
+
+/* Somewhere in the middle of the GCC 2.96 development cycle, we implemented
+   a mechanism by which the user can annotate likely branch directions and
+   expect the blocks to be reordered appropriately.  Define __builtin_expect
+   to nothing for earlier compilers.  */
+
+#if __GNUC__ == 2 && __GNUC_MINOR__ < 96
+#define __builtin_expect(x, expected_value) (x)
+#endif
+
+#endif /* __I386_COMPILER_H */


--- 2.4.3-ac12/include/asm-i386/semaphore.h Sat Apr 21 22:55:38 2001
+++ 2.4.3-ac12/include/asm-i386/semaphore.h Sat Apr 21 22:55:57 2001
@@ -38,6 +38,7 @@

 #include 
 #include 
+#include 
 #include 
 #include 



depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/arch/i386/kernel/microcode.o
depmod: rwsem_up_write_wake
depmod: rwsem_up_read_wake
depmod: rwsem_down_write_failed
depmod: rwsem_down_read_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/gamma.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/i810.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/mga.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/r128.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/tdfx.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/net/aironet4500_card.o
depmod: __bad_udelay
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_base.o
depmod: rwsem_up_read_wake
depmod: rwsem_down_read_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_crtc2.o
depmod: rwsem_up_write_wake
depmod: rwsem_up_read_wake
depmod: rwsem_down_write_failed
depmod: rwsem_down_read_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_g450.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_maven.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/binfmt_aout.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/cmsfs/cms.o
depmod: get_hardsect_size


#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_ISA=y
# CONFIG_SBUS is not set
CONFIG_UID16=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y

#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUM4 is not set
CONFIG_MK6=y
# CONFIG_MK7 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_CMPXCHG=y

Re: Linux 2.4.3-ac12

[Geert Uytterhoeven]

On 22 Apr 2001, Jes Sorensen wrote:
> > "Alan" == Alan Cox <[EMAIL PROTECTED]> writes:
> Alan> The recommended compilers for non x86 are different too - eg you
> Alan> need 2.96 gcc for IA64, you need 2.95 not egcs for mips and so
> Alan> on.
> 
> In principle you just need 2.7.2.3 for m68k, but someone decided to
> raise the bar for all architectures by putting a check in a common
> header file.

Late 2.3.x proved to be very unstable for user applications (daily cron always
segfaulted somewhere), until I upgraded from 2.7.2.3 to 2.95.2 from Debian.

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[Geert Uytterhoeven]

On 22 Apr 2001, Jes Sorensen wrote:
  Alan == Alan Cox [EMAIL PROTECTED] writes:
 Alan The recommended compilers for non x86 are different too - eg you
 Alan need 2.96 gcc for IA64, you need 2.95 not egcs for mips and so
 Alan on.
 
 In principle you just need 2.7.2.3 for m68k, but someone decided to
 raise the bar for all architectures by putting a check in a common
 header file.

Late 2.3.x proved to be very unstable for user applications (daily cron always
segfaulted somewhere), until I upgraded from 2.7.2.3 to 2.95.2 from Debian.

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say programmer or something like that.
-- Linus Torvalds

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[Byeong-ryeol Kim]

On Sun, 22 Apr 2001, Alan Cox wrote:

   Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
   /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
   symbol rwsem_up_write_wake
   /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
   symbol rwsem_down_write_failed
 
  Same thing with tdfx.o...

 Works for me as ever. What configuration options are you using. This sounds
 like some of the code is built with each kind of semaphore.


I use 2 PCs at home. One is unnamed desktop - AMD K6-II+, ASUS P/I-P55T2P4
rev. 3.10, 128 MB EDO RAM, etc.), the other is IBM ThinkPad 600X(Pentium III
500, 192 MB PC100 RAM, etc.). But, the result of depmod under 2.4.3-ac12
are the same.
I use gcc-2.95.3 release + recommended patch about atexit from libc-alpha list
which seemed to be applied in gcc-2.95.4 CVS tree).
BTW, I applied the follwing patch posted to this list:

--- 2.4.3-ac12/include/asm-i386/compiler.h  Sat Apr 21 22:56:03 2001
+++ 2.4.3-ac12/include/asm-i386/compiler.h  Sat Apr 21 22:56:43 2001
@@ -0,0 +1,13 @@
+#ifndef __I386_COMPILER_H
+#define __I386_COMPILER_H 1
+
+/* Somewhere in the middle of the GCC 2.96 development cycle, we implemented
+   a mechanism by which the user can annotate likely branch directions and
+   expect the blocks to be reordered appropriately.  Define __builtin_expect
+   to nothing for earlier compilers.  */
+
+#if __GNUC__ == 2  __GNUC_MINOR__  96
+#define __builtin_expect(x, expected_value) (x)
+#endif
+
+#endif /* __I386_COMPILER_H */


--- 2.4.3-ac12/include/asm-i386/semaphore.h Sat Apr 21 22:55:38 2001
+++ 2.4.3-ac12/include/asm-i386/semaphore.h Sat Apr 21 22:55:57 2001
@@ -38,6 +38,7 @@

 #include asm/system.h
 #include asm/atomic.h
+#include asm/compiler.h
 #include linux/wait.h
 #include linux/rwsem.h



depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/arch/i386/kernel/microcode.o
depmod: rwsem_up_write_wake
depmod: rwsem_up_read_wake
depmod: rwsem_down_write_failed
depmod: rwsem_down_read_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/gamma.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/i810.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/mga.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/r128.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/tdfx.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/net/aironet4500_card.o
depmod: __bad_udelay
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_base.o
depmod: rwsem_up_read_wake
depmod: rwsem_down_read_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_crtc2.o
depmod: rwsem_up_write_wake
depmod: rwsem_up_read_wake
depmod: rwsem_down_write_failed
depmod: rwsem_down_read_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_g450.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_maven.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/binfmt_aout.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/cmsfs/cms.o
depmod: get_hardsect_size


#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_ISA=y
# CONFIG_SBUS is not set
CONFIG_UID16=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y

#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUM4 is not set
CONFIG_MK6=y
# CONFIG_MK7 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
CONFIG_X86_WP_WORKS_OK=y

Re: Linux 2.4.3-ac12

[Byeong-ryeol Kim]

On Mon, 23 Apr 2001, Byeong-ryeol Kim wrote:

 On Sun, 22 Apr 2001, Alan Cox wrote:

Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
symbol rwsem_up_write_wake
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
symbol rwsem_down_write_failed
  
   Same thing with tdfx.o...
 
  Works for me as ever. What configuration options are you using. This sounds
  like some of the code is built with each kind of semaphore.
 

 I use 2 PCs at home. One is unnamed desktop - AMD K6-II+, ASUS P/I-P55T2P4
 rev. 3.10, 128 MB EDO RAM, etc.), the other is IBM ThinkPad 600X(Pentium III
 500, 192 MB PC100 RAM, etc.). But, the result of depmod under 2.4.3-ac12
 are the same.
 I use gcc-2.95.3 release + recommended patch about atexit from libc-alpha list
 which seemed to be applied in gcc-2.95.4 CVS tree).


I retried to compile 2.4.3-ac12 with Red Hat's 2.96-81(that of 7.1) without
the patch previously applied.
This time, I noticed strange thing.(I guess, it would not be a compiler
problem).
While doing 'depmod -ae -F /boot/System.map-2.4.3-ac12 2.4.3-ac12'
there was no error as far as rwsem_* is concerned, but when doing simply
'depmod -ae', the result was the same as before.( the same kernel
configuration, modutils is original 2.4.5-1 fetched from kernel site).

1) 'depmod -ae -F /boot/system.map-2.4.3-ac12 2.4.3-ac12'

depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/net/aironet4500_card.o
depmod: __bad_udelay
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/cmsfs/cms.o
depmod: get_hardsect_size

2) 'depmod -ae'

depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/arch/i386/kernel/microcode.o
depmod: rwsem_up_write_wake
depmod: rwsem_up_read_wake
depmod: rwsem_down_write_failed
depmod: rwsem_down_read_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/gamma.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/i810.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/mga.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/r128.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/tdfx.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/net/aironet4500_card.o
depmod: __bad_udelay
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_base.o
depmod: rwsem_up_read_wake
depmod: rwsem_down_read_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_crtc2.o
depmod: rwsem_up_write_wake
depmod: rwsem_up_read_wake
depmod: rwsem_down_write_failed
depmod: rwsem_down_read_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_g450.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_maven.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/binfmt_aout.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/cmsfs/cms.o
depmod: get_hardsect_size



 #
 # Automatically generated make config: don't edit
 #
 CONFIG_X86=y
 CONFIG_ISA=y
 # CONFIG_SBUS is not set
 CONFIG_UID16=y

 #
 # Code maturity level options
 #
 CONFIG_EXPERIMENTAL=y

 #
 # Loadable module support
 #
 CONFIG_MODULES=y
 CONFIG_MODVERSIONS=y
 CONFIG_KMOD=y

 #
 # Processor type and features
 #
 # CONFIG_M386 is not set
 # CONFIG_M486 is not set
 # CONFIG_M586 is not set
 # CONFIG_M586TSC is not set
 # CONFIG_M586MMX is not set
 # CONFIG_M686 is not set
 # CONFIG_MPENTIUMIII is not set
 # CONFIG_MPENTIUM4 is not set
 CONFIG_MK6=y
 # CONFIG_MK7 is not set
 # CONFIG_MCRUSOE is not set
 # CONFIG_MWINCHIPC6 is not set
 # CONFIG_MWINCHIP2 is not set
 # CONFIG_MWINCHIP3D is not set
 # CONFIG_MCYRIXIII is not set
 CONFIG_X86_WP_WORKS_OK=y
 CONFIG_X86_INVLPG=y
 CONFIG_X86_CMPXCHG=y
 CONFIG_X86_XADD=y
 CONFIG_X86_BSWAP=y
 

Re: Linux 2.4.3-ac12

[John Cavan]

Alan Cox wrote:
> 
> > > Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
> > > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> > > symbol rwsem_up_write_wake
> > > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> > > symbol rwsem_down_write_failed
> >
> > Same thing with tdfx.o...
> 
> "Works for me" as ever. What configuration options are you using. This sounds
> like some of the code is built with each kind of semaphore.

Mine is attached. I always run "make menuconfig", reconfirm my
selections (which haven't changed in ages), save it, and then run "make
dep" before building. I should note that I'm using a version of the DRI
from CVS from early April, but it has been perfectly happy until now. I
also tried it with the code in the kernel tree, same problem.

John
 config

Re: Linux 2.4.3-ac12

[Mr. James W. Laferriere]

Hello Alan ,  To whom is this attributed ?  Tia ,  JimL

On Sun, 22 Apr 2001, Alan Cox wrote:
> o Hopefully fix bugtraq reported netfilter ftp
>   flaw
   ++
   | James   W.   Laferriere | System  Techniques | Give me VMS |
   | NetworkEngineer | 25416  22nd So |  Give me Linux  |
   | [EMAIL PROTECTED] | DesMoines WA 98198 |   only  on  AXP |
   ++

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[J . A . Magallon]

On 04.22 Dieter Nützel wrote:
> > My belief however is that several million people have gcc 2.96-69+, about 50
> > are likely to have random cvs snapshots and none of them are going to build
> > kernels with them anyway, as they wont work __builtin_expect or otherwise.
> >
> > Alan
> 
> I will not add fuel to the fire, but isn't 2.4.XX the "stable" version?
> And I think most people (here in Europe :-) are running 2.95.2 at the moment.
> But, yes the previously patches fixed it.
> 

That's going to change in a few weeks, I suspect. Dunno about SuSE, but just
released Mandrake 8.0 and RedHat 7.1 ship gcc-2.96.

-- 
J.A. Magallon  #  Let the source
mailto:[EMAIL PROTECTED]  #  be with you, Luke... 

Linux werewolf 2.4.3-ac12 #1 SMP Sun Apr 22 10:27:22 CEST 2001 i686

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12 unresolved symbol rwsem...

[J Sloan]

Alan Cox wrote:

> > > Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
> > > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> > > symbol rwsem_up_write_wake
> > > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> > > symbol rwsem_down_write_failed
> >
> > Same thing with tdfx.o...
>
> "Works for me" as ever. What configuration options are you using. This sounds
> like some of the code is built with each kind of semaphore.

I'm getting the same thing here - Red Hat 7.1, amd K6/2
450 with a voodoo 3 -

After successful build and booting of 2.4.3-ac12, I found
I had no 3D acceleration, and saw error msgs similar to
those above, concerning tdfx.o.

As always, building agp and tdfx as modules.

jjs

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[Manuel McLure]

On 2001.04.22 11:48 Alan Cox wrote:
> > > Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
> > > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> > > symbol rwsem_up_write_wake
> > > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> > > symbol rwsem_down_write_failed
> > 
> > Same thing with tdfx.o...
> 
> "Works for me" as ever. What configuration options are you using. This
> sounds
> like some of the code is built with each kind of semaphore.

.config attached - note that I build a lot more than I actually need. I
took a .config from the Red Hat 7 2.4 kernel RPM and have just been keeping
it up to date with "make oldconfig". I suppose some day I should go through
and select only the stuff I want...

-- 
Manuel A. McLure KE6TAW | ...for in Ulthar, according to an ancient
<[EMAIL PROTECTED]> | and significant law, no man may kill a cat.
 | -- H.P. Lovecraft
 .config

Re: Linux 2.4.3-ac12

[Alan Cox]

> > Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
> > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> > symbol rwsem_up_write_wake
> > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> > symbol rwsem_down_write_failed
> 
> Same thing with tdfx.o...

"Works for me" as ever. What configuration options are you using. This sounds
like some of the code is built with each kind of semaphore.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[Alan Cox]

> In principle you just need 2.7.2.3 for m68k, but someone decided to
> raise the bar for all architectures by putting a check in a common
> header file.

I suspect you would find that some of the problems with the initialisers
in structures were common to 2.7.2 across all platforms, but I may be wrong

> Maybe it's time to move that check to the arch include dir instead?

I have no problem there

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[Jes Sorensen]

> "Roman" == Roman Zippel <[EMAIL PROTECTED]> writes:

Roman> Hi, Jes Sorensen wrote:

>> In principle you just need 2.7.2.3 for m68k, but someone decided to
>> raise the bar for all architectures by putting a check in a common
>> header file.

Roman> IIRC 2.7.2.3 has problems with labeled initializers for
Roman> structures, which makes 2.7.2.3 unusable for all archs under
Roman> 2.4.

True, so our bar is egcs-1.1.2, but thats still a bit from 2.96+

Jes
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[Roman Zippel]

Hi,

Jes Sorensen wrote:

> In principle you just need 2.7.2.3 for m68k, but someone decided to
> raise the bar for all architectures by putting a check in a common
> header file.

IIRC 2.7.2.3 has problems with labeled initializers for structures,
which makes 2.7.2.3 unusable for all archs under 2.4.

bye, Roman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[Manuel McLure]

On 2001.04.22 09:25 John Cavan wrote:
> Alan Cox wrote:
> > 2.4.3-ac12
> > o   Further semaphore fixes (David Howells)
> 
> Getting unresolved symbols in some modules (notably, for me, microcode.o
> and radeon.o)...
> 
> Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
> /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> symbol rwsem_up_write_wake
> /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> symbol rwsem_down_write_failed

Same thing with tdfx.o...

-- 
Manuel A. McLure KE6TAW | ...for in Ulthar, according to an ancient
<[EMAIL PROTECTED]> | and significant law, no man may kill a cat.
 | -- H.P. Lovecraft

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[Dieter Nützel]

> My belief however is that several million people have gcc 2.96-69+, about 50
> are likely to have random cvs snapshots and none of them are going to build
> kernels with them anyway, as they wont work __builtin_expect or otherwise.
>
> Alan

I will not add fuel to the fire, but isn't 2.4.XX the "stable" version?
And I think most people (here in Europe :-) are running 2.95.2 at the moment.
But, yes the previously patches fixed it.

Thanks,
Dieter
-- 
Dieter Nützel
Graduate Student, Computer Science

University of Hamburg
Department of Computer Science
Cognitive Systems Group
Vogt-Kölln-Straße 30
D-22527 Hamburg, Germany

email: [EMAIL PROTECTED]
@home: [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[Mohammad A. Haque]

In case everyone missed my original patch =P

http://marc.theaimsgroup.com/?l=linux-kernel=98791931115515=2


Jes Sorensen wrote:
> 
> > "Alan" == Alan Cox <[EMAIL PROTECTED]> writes:
> 
> Alan> The recommended compilers for non x86 are different too - eg you
> Alan> need 2.96 gcc for IA64, you need 2.95 not egcs for mips and so
> Alan> on.
> 
> In principle you just need 2.7.2.3 for m68k, but someone decided to
> raise the bar for all architectures by putting a check in a common
> header file.
> 
> Maybe it's time to move that check to the arch include dir instead?
> 
> Jes
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 

=
Mohammad A. Haque  http://www.haque.net/ 
   [EMAIL PROTECTED]

  "Alcohol and calculus don't mix. Project Lead
   Don't drink and derive." --Unknown  http://wm.themes.org/
   [EMAIL PROTECTED]
=
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[John Cavan]

Alan Cox wrote:
> 2.4.3-ac12
> o   Further semaphore fixes (David Howells)

Getting unresolved symbols in some modules (notably, for me, microcode.o
and radeon.o)...

Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
symbol rwsem_up_write_wake
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
symbol rwsem_down_write_failed

John
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[Jes Sorensen]

> "Alan" == Alan Cox <[EMAIL PROTECTED]> writes:

Alan> The recommended compilers for non x86 are different too - eg you
Alan> need 2.96 gcc for IA64, you need 2.95 not egcs for mips and so
Alan> on.

In principle you just need 2.7.2.3 for m68k, but someone decided to
raise the bar for all architectures by putting a check in a common
header file.

Maybe it's time to move that check to the arch include dir instead?

Jes
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[Jesper Juhl]

f5ibh wrote:

> Alan,
> 
> 
>>> /usr/src/linux-2.4.3-ac12/lib/lib.a(rwsem.o): In function
>>> `rwsem_up_write_wake':rwsem.o(.text+0x3c6): undefined reference to
>>> `__builtin_expect'
>> 
>> Add a
>> 
>> #define __builtin_expect
> 
> 
> I had the same problem here, adding #define __builtin_expect in ../lib/rwsem.c
> solved the problem.
> 
> gcc is :
> 
> [jean-luc@debian-f5ibh] ~ # gcc -v
> Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.3/specs
> gcc version 2.95.3 20010315 (Debian release)
> 

Just a 'me too'. I had the same problem, and the #define fixed it nicely...

bash-2.03# gcc -v
Reading specs from /usr/lib/gcc-lib/i386-slackware-linux/2.95.3/specs
gcc version 2.95.3 20010315 (release)


-- Jesper Juhl - [EMAIL PROTECTED]

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[Alan Cox]

> Are you being deliberately obtuse?  2.97+ snapshots do all support 
> builtin_expect, which is what we were discussing.

I think we are having different conversations here.

The only valid inputs to the question are

Recommended
---
egcs-1.1.2  (miscompiles strstr  <2.4.4pre)
gcc 2.95.*  (miscompiles strstr  <2.4.4pre)

Recommended (for -ac at least)
--
rh-gcc 2.96-69+ (DAC960 fails due to gcc ABI change)
rh-gcc 2.96-78+

For the Brave
-
gcc 3.0 snapshots

There are no gcc 2.97 snapshots that compile the kernel correctly because
they have the broken bitfield packing ABI change. 

So if your belief is that we should insist on gcc 3.0 for __builtin_expect
then we should simply remove use of it completely. For 2.5.x it will be worth
making heavy use of once gcc 3.0 is out.

My belief however is that several million people have gcc 2.96-69+, about 50
are likely to have random cvs snapshots and none of them are going to build
kernels with them anyway, as they wont work __builtin_expect or otherwise.

Alan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[f5ibh]

Alan,

>> /usr/src/linux-2.4.3-ac12/lib/lib.a(rwsem.o): In function
>> `rwsem_up_write_wake':rwsem.o(.text+0x3c6): undefined reference to
>> `__builtin_expect'
>
>Add a
>
>#define __builtin_expect

I had the same problem here, adding #define __builtin_expect in ../lib/rwsem.c
solved the problem.

gcc is :

[jean-luc@debian-f5ibh] ~ # gcc -v
Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.3/specs
gcc version 2.95.3 20010315 (Debian release)

---
Regards

Jean-Luc
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[Philip Blundell]

>There are no gcc 2.97 snapshots that compile the kernel correctly because
>they have the broken bitfield packing ABI change. 

Oh right.  I didn't know about that particular nicety.

>My belief however is that several million people have gcc 2.96-69+, about 50
>are likely to have random cvs snapshots and none of them are going to build
>kernels with them anyway, as they wont work __builtin_expect or otherwise.

Fair enough.

p.



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[Philip Blundell]

There are no gcc 2.97 snapshots that compile the kernel correctly because
they have the broken bitfield packing ABI change. 

Oh right.  I didn't know about that particular nicety.

My belief however is that several million people have gcc 2.96-69+, about 50
are likely to have random cvs snapshots and none of them are going to build
kernels with them anyway, as they wont work __builtin_expect or otherwise.

Fair enough.

p.



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[f5ibh]

Alan,

 /usr/src/linux-2.4.3-ac12/lib/lib.a(rwsem.o): In function
 `rwsem_up_write_wake':rwsem.o(.text+0x3c6): undefined reference to
 `__builtin_expect'

Add a

#define __builtin_expect

I had the same problem here, adding #define __builtin_expect in ../lib/rwsem.c
solved the problem.

gcc is :

[jean-luc@debian-f5ibh] ~ # gcc -v
Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.3/specs
gcc version 2.95.3 20010315 (Debian release)

---
Regards

Jean-Luc
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[Jes Sorensen]

 "Alan" == Alan Cox [EMAIL PROTECTED] writes:

Alan The recommended compilers for non x86 are different too - eg you
Alan need 2.96 gcc for IA64, you need 2.95 not egcs for mips and so
Alan on.

In principle you just need 2.7.2.3 for m68k, but someone decided to
raise the bar for all architectures by putting a check in a common
header file.

Maybe it's time to move that check to the arch include dir instead?

Jes
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[John Cavan]

Alan Cox wrote:
 2.4.3-ac12
 o   Further semaphore fixes (David Howells)

Getting unresolved symbols in some modules (notably, for me, microcode.o
and radeon.o)...

Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
symbol rwsem_up_write_wake
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
symbol rwsem_down_write_failed

John
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[Mohammad A. Haque]

In case everyone missed my original patch =P

http://marc.theaimsgroup.com/?l=linux-kernelm=98791931115515w=2


Jes Sorensen wrote:
 
  "Alan" == Alan Cox [EMAIL PROTECTED] writes:
 
 Alan The recommended compilers for non x86 are different too - eg you
 Alan need 2.96 gcc for IA64, you need 2.95 not egcs for mips and so
 Alan on.
 
 In principle you just need 2.7.2.3 for m68k, but someone decided to
 raise the bar for all architectures by putting a check in a common
 header file.
 
 Maybe it's time to move that check to the arch include dir instead?
 
 Jes
 -
 To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
 the body of a message to [EMAIL PROTECTED]
 More majordomo info at  http://vger.kernel.org/majordomo-info.html
 Please read the FAQ at  http://www.tux.org/lkml/

-- 

=
Mohammad A. Haque  http://www.haque.net/ 
   [EMAIL PROTECTED]

  "Alcohol and calculus don't mix. Project Lead
   Don't drink and derive." --Unknown  http://wm.themes.org/
   [EMAIL PROTECTED]
=
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[Dieter Nützel]

 My belief however is that several million people have gcc 2.96-69+, about 50
 are likely to have random cvs snapshots and none of them are going to build
 kernels with them anyway, as they wont work __builtin_expect or otherwise.

 Alan

I will not add fuel to the fire, but isn't 2.4.XX the "stable" version?
And I think most people (here in Europe :-) are running 2.95.2 at the moment.
But, yes the previously patches fixed it.

Thanks,
Dieter
-- 
Dieter Ntzel
Graduate Student, Computer Science

University of Hamburg
Department of Computer Science
Cognitive Systems Group
Vogt-Klln-Strae 30
D-22527 Hamburg, Germany

email: [EMAIL PROTECTED]
@home: [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[Manuel McLure]

On 2001.04.22 09:25 John Cavan wrote:
 Alan Cox wrote:
  2.4.3-ac12
  o   Further semaphore fixes (David Howells)
 
 Getting unresolved symbols in some modules (notably, for me, microcode.o
 and radeon.o)...
 
 Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
 /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
 symbol rwsem_up_write_wake
 /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
 symbol rwsem_down_write_failed

Same thing with tdfx.o...

-- 
Manuel A. McLure KE6TAW | ...for in Ulthar, according to an ancient
[EMAIL PROTECTED] | and significant law, no man may kill a cat.
http://www.mclure.org | -- H.P. Lovecraft

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[Roman Zippel]

Hi,

Jes Sorensen wrote:

 In principle you just need 2.7.2.3 for m68k, but someone decided to
 raise the bar for all architectures by putting a check in a common
 header file.

IIRC 2.7.2.3 has problems with labeled initializers for structures,
which makes 2.7.2.3 unusable for all archs under 2.4.

bye, Roman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[Jes Sorensen]

 "Roman" == Roman Zippel [EMAIL PROTECTED] writes:

Roman Hi, Jes Sorensen wrote:

 In principle you just need 2.7.2.3 for m68k, but someone decided to
 raise the bar for all architectures by putting a check in a common
 header file.

Roman IIRC 2.7.2.3 has problems with labeled initializers for
Roman structures, which makes 2.7.2.3 unusable for all archs under
Roman 2.4.

True, so our bar is egcs-1.1.2, but thats still a bit from 2.96+

Jes
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[Alan Cox]

 In principle you just need 2.7.2.3 for m68k, but someone decided to
 raise the bar for all architectures by putting a check in a common
 header file.

I suspect you would find that some of the problems with the initialisers
in structures were common to 2.7.2 across all platforms, but I may be wrong

 Maybe it's time to move that check to the arch include dir instead?

I have no problem there

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[Alan Cox]

  Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
  /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
  symbol rwsem_up_write_wake
  /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
  symbol rwsem_down_write_failed
 
 Same thing with tdfx.o...

"Works for me" as ever. What configuration options are you using. This sounds
like some of the code is built with each kind of semaphore.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[Manuel McLure]

On 2001.04.22 11:48 Alan Cox wrote:
   Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
   /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
   symbol rwsem_up_write_wake
   /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
   symbol rwsem_down_write_failed
  
  Same thing with tdfx.o...
 
 "Works for me" as ever. What configuration options are you using. This
 sounds
 like some of the code is built with each kind of semaphore.

.config attached - note that I build a lot more than I actually need. I
took a .config from the Red Hat 7 2.4 kernel RPM and have just been keeping
it up to date with "make oldconfig". I suppose some day I should go through
and select only the stuff I want...

-- 
Manuel A. McLure KE6TAW | ...for in Ulthar, according to an ancient
[EMAIL PROTECTED] | and significant law, no man may kill a cat.
http://www.mclure.org | -- H.P. Lovecraft
 .config

Re: Linux 2.4.3-ac12 unresolved symbol rwsem...

[J Sloan]

Alan Cox wrote:

   Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
   /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
   symbol rwsem_up_write_wake
   /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
   symbol rwsem_down_write_failed
 
  Same thing with tdfx.o...

 "Works for me" as ever. What configuration options are you using. This sounds
 like some of the code is built with each kind of semaphore.

I'm getting the same thing here - Red Hat 7.1, amd K6/2
450 with a voodoo 3 -

After successful build and booting of 2.4.3-ac12, I found
I had no 3D acceleration, and saw error msgs similar to
those above, concerning tdfx.o.

As always, building agp and tdfx as modules.

jjs

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[J . A . Magallon]

On 04.22 Dieter Ntzel wrote:
  My belief however is that several million people have gcc 2.96-69+, about 50
  are likely to have random cvs snapshots and none of them are going to build
  kernels with them anyway, as they wont work __builtin_expect or otherwise.
 
  Alan
 
 I will not add fuel to the fire, but isn't 2.4.XX the "stable" version?
 And I think most people (here in Europe :-) are running 2.95.2 at the moment.
 But, yes the previously patches fixed it.
 

That's going to change in a few weeks, I suspect. Dunno about SuSE, but just
released Mandrake 8.0 and RedHat 7.1 ship gcc-2.96.

-- 
J.A. Magallon  #  Let the source
mailto:[EMAIL PROTECTED]  #  be with you, Luke... 

Linux werewolf 2.4.3-ac12 #1 SMP Sun Apr 22 10:27:22 CEST 2001 i686

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[Mr. James W. Laferriere]

Hello Alan ,  To whom is this attributed ?  Tia ,  JimL

On Sun, 22 Apr 2001, Alan Cox wrote:
 o Hopefully fix bugtraq reported netfilter ftp
   flaw
   ++
   | James   W.   Laferriere | System  Techniques | Give me VMS |
   | NetworkEngineer | 25416  22nd So |  Give me Linux  |
   | [EMAIL PROTECTED] | DesMoines WA 98198 |   only  on  AXP |
   ++

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

[John Cavan]

Alan Cox wrote:
 
   Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
   /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
   symbol rwsem_up_write_wake
   /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
   symbol rwsem_down_write_failed
 
  Same thing with tdfx.o...
 
 "Works for me" as ever. What configuration options are you using. This sounds
 like some of the code is built with each kind of semaphore.

Mine is attached. I always run "make menuconfig", reconfirm my
selections (which haven't changed in ages), save it, and then run "make
dep" before building. I should note that I'm using a version of the DRI
from CVS from early April, but it has been perfectly happy until now. I
also tried it with the code in the kernel tree, same problem.

John
 config

Re: Linux 2.4.3-ac11

[Alan Cox]

> On 04.21 Alan Cox wrote:
> > 
> > ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
> 
> gcc-2.96 spits warnings about possibly-used-before-initialized vars in
> mtrr.c, line 2004:

Its right actually... that could only bite what I believe to be never issued
chips but its right.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac11

[Alan Cox]

 On 04.21 Alan Cox wrote:
  
  ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
 
 gcc-2.96 spits warnings about possibly-used-before-initialized vars in
 mtrr.c, line 2004:

Its right actually... that could only bite what I believe to be never issued
chips but its right.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac11

[J . A . Magallon]

On 04.21 Alan Cox wrote:
> 
>   ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/

gcc-2.96 spits warnings about possibly-used-before-initialized vars in
mtrr.c, line 2004:

static void __init centaur_mcr_init(void)
{
int lo,hi;
..
if (anything)
set hi,lo

..
use lo, hi all around
}

Perhaps it never can happen, but...

-- 
J.A. Magallon  #  Let the source
mailto:[EMAIL PROTECTED]  #  be with you, Luke... 

Linux werewolf 2.4.3-ac9 #1 SMP Wed Apr 18 10:35:48 CEST 2001 i686

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Linux 2.4.3-ac11

[Alan Cox]

ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/

Intermediate diffs are available from

http://www.bzimage.org

You may well need to 'make clean' before building -ac8 as the GDT layout
has changed a little.

2.4.3-ac11
o   Merge Linus 2.4.4pre5
o   Back out problem dvdram changes
o   Make reiserfs use daemonize (Chris Mason)
o   Fix lvm map buglet  (Jens Axboe)
o   tms380 driver fixes (Adam Fritzler)
o   Fix up duplicate configs and other glitches (Steven Cole)
o   Fix pcnet32 printk format bug   (me)
o   ISDN driver further small update/fixes  (me)
o   Fix bounce buffer deadlock on bh allocs (Arjan van de Ven)
o   Fix fbmem merge glitch  (Geert Uytterhoeven)
o   Version string cleanups on net devices  (Jeff Garzik)
o   Update ext2 documentation   (Andreas Dilger)
o   Add MCE support for AMD Athlon/Duron(Dave Jones)
o   Further SDLA tidying(me)
o   Update Configure.help maintainers   (Steven Cole, Eric
 Raymond)
o   Tulip update(Jeff Garzik)
o   Fix sound config to use right symnames  (Eric Raymond)
o   Further dmfe fixes  (Tobias Ringstrom,
 Frank Davis
 Jeff Garzik)
o   Parport probe cleanups  (Tim Waugh)
o   Fix a few configure items   (Eric Raymond)
o   Fix cmsfs nonbuild  (me)


2.4.3-ac10
o   Merge Linus 2.4.4pre4
o   Apply the i960 quirk to the DPT I2O controllers (me)
o   Etrax100 updates(Bjorn Wesen)
o   Fix skge memory leak(Jes Sorensen)
o   Handle reiserfs log overflow error  (Chris Mason)
o   Merge JFFS2 (compressing log flash file system) (David Woodhouse)
o   Merge contributed help texts for options(Eric Raymond,
 Steven Cole)
o   Further screen blanking fixes   (Mikael Pettersson)
o   Further binfmt elf DLINFO fixes/alignment  (Benjamin Herrenschmidt)
o   Fix reboot notifier unregister in aic7xxx   (Arjan van de Ven)
o   Fix orinoco_cs build on powerpc (David Gibson)
o   Neomagic audio didn't call pci_enable_device(Marcus Meissner)
o   Remove superblock file size setting for 2Gb (Al Viro)
default size file systems
o   Merge UML gprof support (Jeff Dike)
o   Clean up UML slip code  (Jeff Dike)
o   Allow UML attach to already running debuggers   (Jeff Dike)
o   Reorder frame buffer probes (Geert Uytterhoeven)
o   Add __init calls to bluesmoke.c (Dave Jones)
o   Add missing pci_enable_device to toshoboe   (Marcus Meissner)
o   Updated AFFS file system(Roman Zippel)
o   DVD-RAM fixes   (Jens Axboe)
o   Further sundance driver fixes   (Jeff Garzik)
o   Fix qlogicfc warning(Dave Miller)
o   Fix sign handling error in scsi_ioctl   (me)
| Found by the Stanford validator
o   Fix sign handling error in af_decnet(me)
| Found by the Stanford validator
o   Fixed I2O posts to be uninterruptible   (me)
o   Stop IDE layer eating Supertrak slave PDC20265  (me)
o   Work around the DPT I2O controller exploding 
when asked to quiesce.  (me)


2.4.3-ac9
o   Fix ac8 pnpbios build bug   (me)
o   Fix ac8 sysrq build bug (me)
o   Fix uml for new semaphores  (Jeff Dike)
o   Attempt to flush low memory buffers when short
of bounce space on highmem machines (Marcelo Tosatti)
o   Kill old filesystem_setup function  (Al Viro)
o   Small pnp bios tidy up  (me)

2.4.3-ac8
o   Restore wan router features backed out by the   (me)
sangoma stuff Linus merged
o   Clean up #ifdefs in Sangoma code a bit  (me)
o   Fix missing kmalloc return checks in Sangoma(me)
o   Fix d_flags bit setting in knfsd(Mikael Pettersson)
o   Turn on winchip MCE (Dave Jones)
o   IRDA USB driver fixups  (Dag Brattli, 
Philipp Rumpf, Jean Tourrilhes)

Re: Kernel Panic Linux 2.4.3 RH7

[Tim Haynes]

<[EMAIL PROTECTED]> writes:

> Machine has been locking up between 0-3 times a day sporadically. Nothing
> predictable about it. Hadn't locked up for 3 days, and locked 3x today,
> the last 2 times within 20 minutes of each other. Had run stable with
> 2.2.18, and was running fairly stable on 2.4.3 up until about last week.
> (might be coincidence, or not, but seems to happen when I am on IRC --
> DOS?, nothing in log files or firewall logs however)
> 
> Machine info:
> 
> RedHat 7, Intel Celeron 450, 256Meg ECC PC100 DRAM, 1 15G IDE (/usr,
> /tmp, /home, /var, swap ), 1 2G SCSI (/, /boot, swap) HDD, 2 identical
> tulip chipset eth cards.
[snip]
> 
> Mismatch in TCPACCEPT IN=ETH0 OUT= MAC= 00:00:e8:24:53
[snip]
> (stack information skipped, if you need it let me know and I will write it
> all down the next time)
> 
> Process: swapper (pid0, stack page c02dl000)
[snip]

Take your pick from one or more of the following:
a) dodgy RAM - less likely if a different set of RAM has also had
   the problem;
b) a faulty network card - a tulip (Netgear FA310TX) reliably caused me
   a hang ~6 months ago, so there is a precedent;
c) overheating - see if, left to its own devices, the hangs become
   more frequent the longer the box is left on; also implement
   lm_sensors and keep an eye on the CPU temperature if possible;
d) RH7 alert: did you use kgcc to build the kernel?
e) Something totally else :8)

HTH,

~Tim
-- 
   10:32pm  up 3 days, 46 min, 10 users,  load average: 0.18, 0.10, 0.08
[EMAIL PROTECTED] |Clouds cross the black moonlight,
http://piglet.is.dreaming.org |Rushing on down to the sound 
  |of a turning world   
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Kernel Panic Linux 2.4.3 RH7

[lkern]

Machine has been locking up between 0-3 times a day
sporadically.  Nothing predictable about it. Hadn't locked up for 3
days, and locked 3x today, the last 2 times within 20 minutes of each 
other. Had run stable with 2.2.18, and was running fairly stable on 2.4.3
up until about last week.  (might be coincidence, or not, but seems to
happen when I am on IRC -- DOS?, nothing in log files or firewall logs
however)

Machine info:

RedHat 7, Intel Celeron 450, 256Meg ECC PC100 DRAM, 1 15G IDE (/usr, /tmp,
/home,
/var, swap ), 1 2G SCSI (/, /boot, swap) HDD, 2 identical tulip chipset
eth cards.

I just swapped the RAM out this last crash, seeing if that makes any
differences.

Kernel is configured as advanced router with packet filtering, ip
firewalling, NAT, IPTABLES and others enabled running a fairly
comprehensive iptables ruleset, nothing superhuge though.


Machine was recently upgraded to 2.4.3 kernel, from 2.2.18.
Dump message is partially as follows:

Mismatch in TCPACCEPT IN=ETH0 OUT= MAC= 00:00:e8:24:53

(some other stuff below this, but the machine then rolled to the below and
I couldn't finish copying down the above, remainder is as follows:

Kernel Panic:  Attempted to Kill init!
Unable to handle kernel paging request at virtual address e030a40c

printing eip:
c01194ae
*pid=
Oops: 
CPU: 0
Eip: 0010 []
EFLAGS: 0010087

(stack information skipped, if you need it let me know and I will write it
all down the next time)

Process: swapper (pid0, stack page c02dl000)

stack 

Code 8b1186108b 590c85d274 088b410489 42048910

Kernel Panic: Aiee, killing interrupt handler
In interrupt handler - not syncing

Any ideas?

-buddy ellis


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3 Compile Errors - Power Mac

[tom_gall]

Jeff Galloway wrote:
> 
> Sorry, Tom about the word doc faux pas.  I've set out my problem in plain
> text below.  I got my source from ftp.kernel.org.

Hi Jeff,

  Well that's problem #1. Source from kernel.org for 2.4 tends to not work on
PPC as it has been lagging on important patches and such. We're hoping to get
kernel.org caught up ASAP.

  Visit here to get the up to date and sometime bleeding edge source for PPC.

  http://www.fsmlabs.com/linuxppcbk.html

> Here's my problem:
> 
> Problem in compiling linux 2.4.3
> 
> Compile error message:
> 
> After the compiler message:
> 
> gcc ­D__KERNEL__ -I/home/jeff/kernel/linux/include ­Wall
> ­Wstrict-prototypes ­O2 ­fomit-frame-pointer ­fno-strict-aliasing
> ­D__powerpc__ -fsigned-char ­msoft-float ­pipe ­ffixed-r2 ­Wno-uninitialized
> ­mmultiple ­mstring-c ­o fork.o fork.c
> 
> Compiler error message:
> 
> fork.c: In function ?copy_mm¹:
> fork.c:353: fixed or forbidden register 68 (0) was spilled for class
> CR0_REGS.
> This may be due to a compiler bug or to impossible asm statements or
> clauses.

Which version of gcc do you have? You want either 2.95.2 or 2.95.3



> cpp: output pipe has been closed
> make[2]: *** [fork.o] Error 1
> make[2]: Leaving directory ?/home/jeff/kernel/linux/kernel¹
> make[1]: *** [first_rule] Error 2
> make[1]: Leaving directory ?/home/jeff/kernel/linux/kernel¹
> make: *** [_dir_kernel] Error 2
> 
> Compiling on Power Mac 7600, with dual processor (604e/180) installed,
> running kernel 2.2.18 compiled by Jeff Galloway, but otherwise a Yellow Dog
> distribution.

Ah YDL ... good stuff. Hope you are on 1.2 at least. 8-)

Regards,

Tom

-- 
Tom Gall - PowerPC Linux Team"Where's the ka-boom? There was
Linux Technology Center   supposed to be an earth
(w) [EMAIL PROTECTED] shattering ka-boom!"
(w) 507-253-4558 -- Marvin Martian
(h) [EMAIL PROTECTED]
http://oss.software.ibm.com/developerworks/opensource/linux
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3 Compile Errors - Power Mac

[Jeff Galloway]

Thanks.  I'll try your suggestions and check on the version of my compiler
and binutils.

on 4/20/01 3:57 AM, David Woodhouse at [EMAIL PROTECTED] wrote:

> 
> 
> [EMAIL PROTECTED] said:
>>   However, I don't think that wishing the world would avoid these
>> dominant (and very useful) formats is a realistic expectation.  It is
>> certainly not "common sense" to assume as such.
> 
> Of course it's not a realistic expectation. There are times when it's a pain
> to have to be safe - people will always break the rules when they're in a
> hurry and the document to be sent is already in an unsafe format. But taking
> plain text with absolutely no formatting, in fact text which is
> _degenerated_ by word wrapping , and gratuitously putting it in a Word
> document is just _so_ unnecessary that I assumed it had to be a troll.
> 
> 
>> fork.c: In function ?copy_mm:
> 
> Given what this output's been through - I'll assume it's corrupted in
> transit, shall I?
> 
> The kind of error you're seeing is often caused by a mismatch between
> compiler and kernel. As Alan suggests, you should make sure you're using a
> PPC-specific tree because it's not up to date in the stock 2.4.3. And make
> sure you're using the recommended versions of compiler and binutils. Other
> than that, I'm afraid I don't know.
> 
> --
> dwmw2
> 


Jeff Galloway
New York
[EMAIL PROTECTED]


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3 Compile Errors - Power Mac

[Paul Mackerras]

Jeff Galloway writes:

> Compiler error message:
> 
> fork.c: In function Œcopy_mm¹:
> fork.c:353: fixed or forbidden register 68 (0) was spilled for class
> CR0_REGS.
> This may be due to a compiler bug or to impossible asm statements or
> clauses.

You need a newer gcc, I suspect you have egcs installed, and you need
to upgrade to gcc-2.95.2 or later.

Paul.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac10

[Geert Uytterhoeven]

On Thu, 19 Apr 2001, Alan Cox wrote:
> 2.4.3-ac10
> o Merge Linus 2.4.4pre4
> o Reorder frame buffer probes (Geert Uytterhoeven)

These got somewhat mixed. Remove the duplicates:

--- linux-2.4.3-ac10/drivers/video/fbmem.c.orig Fri Apr 20 09:58:50 2001
+++ linux-2.4.3-ac10/drivers/video/fbmem.c  Fri Apr 20 11:33:28 2001
@@ -205,9 +205,6 @@
 #if defined(CONFIG_FB_SIS) && (defined(CONFIG_FB_SIS_300) || 
defined(CONFIG_FB_SIS_315))
{ "sisfb", sisfb_init, sisfb_setup },
 #endif
-#ifdef CONFIG_FB_E1355
-   { "e1355fb", e1355fb_init, e1355fb_setup },
-#endif
 
/*
 * Generic drivers that are used as fallbacks
@@ -275,9 +272,6 @@
 #endif
 #ifdef CONFIG_FB_E1355
{ "e1355fb", e1355fb_init, e1355fb_setup },
-#endif
-#ifdef CONFIG_FB_DC
-   { "dcfb", dcfb_init, NULL },
 #endif
 #ifdef CONFIG_FB_DC
{ "dcfb", dcfb_init, NULL },

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3 Compile Errors - Power Mac

[David Woodhouse]

[EMAIL PROTECTED] said:
>   However, I don't think that wishing the world would avoid these
> dominant (and very useful) formats is a realistic expectation.  It is
> certainly not "common sense" to assume as such.

Of course it's not a realistic expectation. There are times when it's a pain
to have to be safe - people will always break the rules when they're in a
hurry and the document to be sent is already in an unsafe format. But taking
plain text with absolutely no formatting, in fact text which is
_degenerated_ by word wrapping , and gratuitously putting it in a Word
document is just _so_ unnecessary that I assumed it had to be a troll.


> fork.c: In function Œcopy_mm¹:

Given what this output's been through - I'll assume it's corrupted in 
transit, shall I? 

The kind of error you're seeing is often caused by a mismatch between 
compiler and kernel. As Alan suggests, you should make sure you're using a 
PPC-specific tree because it's not up to date in the stock 2.4.3. And make 
sure you're using the recommended versions of compiler and binutils. Other 
than that, I'm afraid I don't know.

--
dwmw2


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: FW: Linux 2.4.3 Compile Errors - Power Mac

[Paul Mackerras]

Jeff Galloway writes:

> I sent this report to the people indicated below, whose names I got from the
> MAINTAINERS file in the 2.4.3 distribution, but the email address for Mr.
> MacKerras is no longer good and Mr. Chastain wrote me back that he is not
> following 2.4 issues.

I have left Linuxcare and [EMAIL PROTECTED] no longer works.
Please use [EMAIL PROTECTED]

> The compiler error message along with the menuconfig-generated configuration
> file are set out in the attached MS Word document.  I've had similar
> problems with other versions of 2.4.

Hmmm, I have to go to a lot of trouble to read Word documents, so I
don't like receiving them.

Paul.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3 Compile Errors - Power Mac

[Jeff Galloway]

Sorry, Tom about the word doc faux pas.  I've set out my problem in plain
text below.  I got my source from ftp.kernel.org.

Here's my problem:



Problem in compiling linux 2.4.3

Compile error message:

After the compiler message:

gcc ­D__KERNEL__ -I/home/jeff/kernel/linux/include ­Wall
­Wstrict-prototypes ­O2 ­fomit-frame-pointer ­fno-strict-aliasing
­D__powerpc__ -fsigned-char ­msoft-float ­pipe ­ffixed-r2 ­Wno-uninitialized
­mmultiple ­mstring-c ­o fork.o fork.c

Compiler error message:

fork.c: In function Œcopy_mm¹:
fork.c:353: fixed or forbidden register 68 (0) was spilled for class
CR0_REGS.
This may be due to a compiler bug or to impossible asm statements or
clauses.
cpp: output pipe has been closed
make[2]: *** [fork.o] Error 1
make[2]: Leaving directory Œ/home/jeff/kernel/linux/kernel¹
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory Œ/home/jeff/kernel/linux/kernel¹
make: *** [_dir_kernel] Error 2

Compiling on Power Mac 7600, with dual processor (604e/180) installed,
running kernel 2.2.18 compiled by Jeff Galloway, but otherwise a Yellow Dog
distribution.

/proc/cpuinfo:

processor: 0
cpu: 604e
clock: 180MHz
revision: 2.2
bogomips: 360.12
zero pages: total 0 (0Kb) current: 0 (0Kb) hits: 0/1457 (0%)
machine: Power Macintosh
motherboard: AAPL,7500 MacRISC
L2 cache: 256K unified
memory: 200MB
pmac-generation: OldWorld


Configuration file:

#
# Automatically generated by make menuconfig: don't edit
#
# CONFIG_UID16 is not set

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y

#
# Platform support
#
CONFIG_PPC=y
CONFIG_6xx=y
# CONFIG_4xx is not set
# CONFIG_POWER3 is not set
# CONFIG_POWER4 is not set
# CONFIG_8xx is not set
# CONFIG_8260 is not set
CONFIG_ALL_PPC=y
# CONFIG_APUS is not set
CONFIG_PPC601_SYNC_FIX=y
CONFIG_SMP=y
CONFIG_IRQ_ALL_CPUS=y
CONFIG_ALTIVEC=y

#
# General setup
#
# CONFIG_HIGHMEM is not set
CONFIG_MOL=y
# CONFIG_ISA is not set
# CONFIG_EISA is not set
# CONFIG_SBUS is not set
# CONFIG_MCA is not set
CONFIG_PCI=y
CONFIG_NET=y
CONFIG_SYSCTL=y
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_KCORE_ELF=y
CONFIG_BINFMT_ELF=y
CONFIG_KERNEL_ELF=y
CONFIG_BINFMT_MISC=m
CONFIG_PCI_NAMES=y
CONFIG_HOTPLUG=y

#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set
CONFIG_PPC_RTC=y
CONFIG_PROC_DEVICETREE=y
CONFIG_PPC_RTAS=y
CONFIG_BOOTX_TEXT=y
CONFIG_PREP_RESIDUAL=y
# CONFIG_CMDLINE_BOOL is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Plug and Play configuration
#
# CONFIG_PNP is not set
# CONFIG_ISAPNP is not set

#
# Block devices
#
CONFIG_BLK_DEV_FD=m
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_NBD is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
# CONFIG_BLK_DEV_MD is not set
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID5 is not set
# CONFIG_BLK_DEV_LVM is not set

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_NETLINK=y
# CONFIG_RTNETLINK is not set
# CONFIG_NETLINK_DEV is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
# CONFIG_FILTER is not set
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_INET_ECN is not set
CONFIG_SYN_COOKIES=y

#
#   IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
CONFIG_IP_NF_FTP=m
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_MAC=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
# CONFIG_IP_NF_MATCH_TCPMSS is not set
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_UNCLEAN=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_MIRROR=m
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_IP_NF_NAT_FTP=m
# CONFIG_IP_NF_MANGLE is not set
# CONFIG_IP_NF_TARGET_LOG is not set
# CONFIG_IP_NF_TARGET_TCPMSS is not set
CONFIG_IP_NF_COMPAT_IPCHAINS=m
CONFIG_IP_NF_NAT_NEEDED=y
# CONFIG_IP_NF_COMPAT_IPFWADM is not set
# CONFIG_IPV6 is not set
# CONFIG_KHTTPD is not set
# CONFIG_ATM is not set
# CONFIG_IPX is not set
CONFIG_ATALK=y
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_LLC is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set

Re: Linux 2.4.3 Compile Errors - Power Mac

[Jeff Galloway]

Jeez David.  Although it was insensitive of me to seek succor from the Linux
folks while speaking Microsoft, you needn't be so touchy about it.  I
promise I won't commit that sin again, however, at least not in these
circles.  (If it makes you feel any better, I'm using a Mac and not a
Wintel.)

For the record, I disagree with the content of your page at
http://www.infradead.org/fileexchange.html.  Viruses can indeed be hidden in
your list of (almost exclusively Microsoft) file formats.  Companies will
certainly enhance their security by following your "common sense" advice.
They can even be more secure by not accepting any email at all.  However, I
don't think that wishing the world would avoid these dominant (and very
useful) formats is a realistic expectation.  It is certainly not "common
sense" to assume as such.

Anyway, in case you may want to help, here's my problem in (virus free)
plain text:

Problem in compiling linux 2.4.3

Compile error message:

After the compiler message:

gcc ­D__KERNEL__ -I/home/jeff/kernel/linux/include ­Wall
­Wstrict-prototypes ­O2 ­fomit-frame-pointer ­fno-strict-aliasing
­D__powerpc__ -fsigned-char ­msoft-float ­pipe ­ffixed-r2 ­Wno-uninitialized
­mmultiple ­mstring-c ­o fork.o fork.c

Compiler error message:

fork.c: In function Œcopy_mm¹:
fork.c:353: fixed or forbidden register 68 (0) was spilled for class
CR0_REGS.
This may be due to a compiler bug or to impossible asm statements or
clauses.
cpp: output pipe has been closed
make[2]: *** [fork.o] Error 1
make[2]: Leaving directory Œ/home/jeff/kernel/linux/kernel¹
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory Œ/home/jeff/kernel/linux/kernel¹
make: *** [_dir_kernel] Error 2

Compiling on Power Mac 7600, with dual processor (604e/180) installed,
running kernel 2.2.18 compiled by Jeff Galloway, but otherwise a Yellow Dog
distribution.

/proc/cpuinfo:

processor: 0
cpu: 604e
clock: 180MHz
revision: 2.2
bogomips: 360.12
zero pages: total 0 (0Kb) current: 0 (0Kb) hits: 0/1457 (0%)
machine: Power Macintosh
motherboard: AAPL,7500 MacRISC
L2 cache: 256K unified
memory: 200MB
pmac-generation: OldWorld


Configuration file:

#
# Automatically generated by make menuconfig: don't edit
#
# CONFIG_UID16 is not set

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y

#
# Platform support
#
CONFIG_PPC=y
CONFIG_6xx=y
# CONFIG_4xx is not set
# CONFIG_POWER3 is not set
# CONFIG_POWER4 is not set
# CONFIG_8xx is not set
# CONFIG_8260 is not set
CONFIG_ALL_PPC=y
# CONFIG_APUS is not set
CONFIG_PPC601_SYNC_FIX=y
CONFIG_SMP=y
CONFIG_IRQ_ALL_CPUS=y
CONFIG_ALTIVEC=y

#
# General setup
#
# CONFIG_HIGHMEM is not set
CONFIG_MOL=y
# CONFIG_ISA is not set
# CONFIG_EISA is not set
# CONFIG_SBUS is not set
# CONFIG_MCA is not set
CONFIG_PCI=y
CONFIG_NET=y
CONFIG_SYSCTL=y
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_KCORE_ELF=y
CONFIG_BINFMT_ELF=y
CONFIG_KERNEL_ELF=y
CONFIG_BINFMT_MISC=m
CONFIG_PCI_NAMES=y
CONFIG_HOTPLUG=y

#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set
CONFIG_PPC_RTC=y
CONFIG_PROC_DEVICETREE=y
CONFIG_PPC_RTAS=y
CONFIG_BOOTX_TEXT=y
CONFIG_PREP_RESIDUAL=y
# CONFIG_CMDLINE_BOOL is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Plug and Play configuration
#
# CONFIG_PNP is not set
# CONFIG_ISAPNP is not set

#
# Block devices
#
CONFIG_BLK_DEV_FD=m
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_NBD is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
# CONFIG_BLK_DEV_MD is not set
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID5 is not set
# CONFIG_BLK_DEV_LVM is not set

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_NETLINK=y
# CONFIG_RTNETLINK is not set
# CONFIG_NETLINK_DEV is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
# CONFIG_FILTER is not set
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_INET_ECN is not set
CONFIG_SYN_COOKIES=y

#
#   IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
CONFIG_IP_NF_FTP=m
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_MAC=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
# CONFIG_IP_NF_MATCH_TCPMSS is not set
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_UNCLEAN=m
CONFIG_IP_NF_MATCH_OWNER=m
C

Re: Linux 2.4.3 Compile Errors - Power Mac

[Jeff Galloway]

Jeez David.  Although it was insensitive of me to seek succor from the Linux
folks while speaking Microsoft, you needn't be so touchy about it.  I
promise I won't commit that sin again, however, at least not in these
circles.  (If it makes you feel any better, I'm using a Mac and not a
Wintel.)

For the record, I disagree with the content of your page at
http://www.infradead.org/fileexchange.html.  Viruses can indeed be hidden in
your list of (almost exclusively Microsoft) file formats.  Companies will
certainly enhance their security by following your "common sense" advice.
They can even be more secure by not accepting any email at all.  However, I
don't think that wishing the world would avoid these dominant (and very
useful) formats is a realistic expectation.  It is certainly not "common
sense" to assume as such.

Anyway, in case you may want to help, here's my problem in (virus free)
plain text:

Problem in compiling linux 2.4.3

Compile error message:

After the compiler message:

gcc D__KERNEL__ -I/home/jeff/kernel/linux/include Wall
Wstrict-prototypes O2 fomit-frame-pointer fno-strict-aliasing
D__powerpc__ -fsigned-char msoft-float pipe ffixed-r2 Wno-uninitialized
mmultiple mstring-c o fork.o fork.c

Compiler error message:

fork.c: In function Œcopy_mm:
fork.c:353: fixed or forbidden register 68 (0) was spilled for class
CR0_REGS.
This may be due to a compiler bug or to impossible asm statements or
clauses.
cpp: output pipe has been closed
make[2]: *** [fork.o] Error 1
make[2]: Leaving directory Œ/home/jeff/kernel/linux/kernel
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory Œ/home/jeff/kernel/linux/kernel
make: *** [_dir_kernel] Error 2

Compiling on Power Mac 7600, with dual processor (604e/180) installed,
running kernel 2.2.18 compiled by Jeff Galloway, but otherwise a Yellow Dog
distribution.

/proc/cpuinfo:

processor: 0
cpu: 604e
clock: 180MHz
revision: 2.2
bogomips: 360.12
zero pages: total 0 (0Kb) current: 0 (0Kb) hits: 0/1457 (0%)
machine: Power Macintosh
motherboard: AAPL,7500 MacRISC
L2 cache: 256K unified
memory: 200MB
pmac-generation: OldWorld


Configuration file:

#
# Automatically generated by make menuconfig: don't edit
#
# CONFIG_UID16 is not set

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y

#
# Platform support
#
CONFIG_PPC=y
CONFIG_6xx=y
# CONFIG_4xx is not set
# CONFIG_POWER3 is not set
# CONFIG_POWER4 is not set
# CONFIG_8xx is not set
# CONFIG_8260 is not set
CONFIG_ALL_PPC=y
# CONFIG_APUS is not set
CONFIG_PPC601_SYNC_FIX=y
CONFIG_SMP=y
CONFIG_IRQ_ALL_CPUS=y
CONFIG_ALTIVEC=y

#
# General setup
#
# CONFIG_HIGHMEM is not set
CONFIG_MOL=y
# CONFIG_ISA is not set
# CONFIG_EISA is not set
# CONFIG_SBUS is not set
# CONFIG_MCA is not set
CONFIG_PCI=y
CONFIG_NET=y
CONFIG_SYSCTL=y
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_KCORE_ELF=y
CONFIG_BINFMT_ELF=y
CONFIG_KERNEL_ELF=y
CONFIG_BINFMT_MISC=m
CONFIG_PCI_NAMES=y
CONFIG_HOTPLUG=y

#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set
CONFIG_PPC_RTC=y
CONFIG_PROC_DEVICETREE=y
CONFIG_PPC_RTAS=y
CONFIG_BOOTX_TEXT=y
CONFIG_PREP_RESIDUAL=y
# CONFIG_CMDLINE_BOOL is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Plug and Play configuration
#
# CONFIG_PNP is not set
# CONFIG_ISAPNP is not set

#
# Block devices
#
CONFIG_BLK_DEV_FD=m
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_NBD is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
# CONFIG_BLK_DEV_MD is not set
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID5 is not set
# CONFIG_BLK_DEV_LVM is not set

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_NETLINK=y
# CONFIG_RTNETLINK is not set
# CONFIG_NETLINK_DEV is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
# CONFIG_FILTER is not set
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_INET_ECN is not set
CONFIG_SYN_COOKIES=y

#
#   IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
CONFIG_IP_NF_FTP=m
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_MAC=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
# CONFIG_IP_NF_MATCH_TCPMSS is not set
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_UNCLEAN=m
CONFIG_IP_NF_MATCH_OWNER=m
C

Re: Linux 2.4.3 Compile Errors - Power Mac

[Jeff Galloway]

Sorry, Tom about the word doc faux pas.  I've set out my problem in plain
text below.  I got my source from ftp.kernel.org.

Here's my problem:



Problem in compiling linux 2.4.3

Compile error message:

After the compiler message:

gcc D__KERNEL__ -I/home/jeff/kernel/linux/include Wall
Wstrict-prototypes O2 fomit-frame-pointer fno-strict-aliasing
D__powerpc__ -fsigned-char msoft-float pipe ffixed-r2 Wno-uninitialized
mmultiple mstring-c o fork.o fork.c

Compiler error message:

fork.c: In function Œcopy_mm:
fork.c:353: fixed or forbidden register 68 (0) was spilled for class
CR0_REGS.
This may be due to a compiler bug or to impossible asm statements or
clauses.
cpp: output pipe has been closed
make[2]: *** [fork.o] Error 1
make[2]: Leaving directory Œ/home/jeff/kernel/linux/kernel
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory Œ/home/jeff/kernel/linux/kernel
make: *** [_dir_kernel] Error 2

Compiling on Power Mac 7600, with dual processor (604e/180) installed,
running kernel 2.2.18 compiled by Jeff Galloway, but otherwise a Yellow Dog
distribution.

/proc/cpuinfo:

processor: 0
cpu: 604e
clock: 180MHz
revision: 2.2
bogomips: 360.12
zero pages: total 0 (0Kb) current: 0 (0Kb) hits: 0/1457 (0%)
machine: Power Macintosh
motherboard: AAPL,7500 MacRISC
L2 cache: 256K unified
memory: 200MB
pmac-generation: OldWorld


Configuration file:

#
# Automatically generated by make menuconfig: don't edit
#
# CONFIG_UID16 is not set

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y

#
# Platform support
#
CONFIG_PPC=y
CONFIG_6xx=y
# CONFIG_4xx is not set
# CONFIG_POWER3 is not set
# CONFIG_POWER4 is not set
# CONFIG_8xx is not set
# CONFIG_8260 is not set
CONFIG_ALL_PPC=y
# CONFIG_APUS is not set
CONFIG_PPC601_SYNC_FIX=y
CONFIG_SMP=y
CONFIG_IRQ_ALL_CPUS=y
CONFIG_ALTIVEC=y

#
# General setup
#
# CONFIG_HIGHMEM is not set
CONFIG_MOL=y
# CONFIG_ISA is not set
# CONFIG_EISA is not set
# CONFIG_SBUS is not set
# CONFIG_MCA is not set
CONFIG_PCI=y
CONFIG_NET=y
CONFIG_SYSCTL=y
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_KCORE_ELF=y
CONFIG_BINFMT_ELF=y
CONFIG_KERNEL_ELF=y
CONFIG_BINFMT_MISC=m
CONFIG_PCI_NAMES=y
CONFIG_HOTPLUG=y

#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set
CONFIG_PPC_RTC=y
CONFIG_PROC_DEVICETREE=y
CONFIG_PPC_RTAS=y
CONFIG_BOOTX_TEXT=y
CONFIG_PREP_RESIDUAL=y
# CONFIG_CMDLINE_BOOL is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Plug and Play configuration
#
# CONFIG_PNP is not set
# CONFIG_ISAPNP is not set

#
# Block devices
#
CONFIG_BLK_DEV_FD=m
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_NBD is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
# CONFIG_BLK_DEV_MD is not set
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID5 is not set
# CONFIG_BLK_DEV_LVM is not set

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_NETLINK=y
# CONFIG_RTNETLINK is not set
# CONFIG_NETLINK_DEV is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
# CONFIG_FILTER is not set
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_INET_ECN is not set
CONFIG_SYN_COOKIES=y

#
#   IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
CONFIG_IP_NF_FTP=m
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_MAC=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
# CONFIG_IP_NF_MATCH_TCPMSS is not set
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_UNCLEAN=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_MIRROR=m
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_IP_NF_NAT_FTP=m
# CONFIG_IP_NF_MANGLE is not set
# CONFIG_IP_NF_TARGET_LOG is not set
# CONFIG_IP_NF_TARGET_TCPMSS is not set
CONFIG_IP_NF_COMPAT_IPCHAINS=m
CONFIG_IP_NF_NAT_NEEDED=y
# CONFIG_IP_NF_COMPAT_IPFWADM is not set
# CONFIG_IPV6 is not set
# CONFIG_KHTTPD is not set
# CONFIG_ATM is not set
# CONFIG_IPX is not set
CONFIG_ATALK=y
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_LLC is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set

Re: FW: Linux 2.4.3 Compile Errors - Power Mac

[Paul Mackerras]

Jeff Galloway writes:

 I sent this report to the people indicated below, whose names I got from the
 MAINTAINERS file in the 2.4.3 distribution, but the email address for Mr.
 MacKerras is no longer good and Mr. Chastain wrote me back that he is not
 following 2.4 issues.

I have left Linuxcare and [EMAIL PROTECTED] no longer works.
Please use [EMAIL PROTECTED]

 The compiler error message along with the menuconfig-generated configuration
 file are set out in the attached MS Word document.  I've had similar
 problems with other versions of 2.4.

Hmmm, I have to go to a lot of trouble to read Word documents, so I
don't like receiving them.

Paul.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3 Compile Errors - Power Mac

[David Woodhouse]

[EMAIL PROTECTED] said:
   However, I don't think that wishing the world would avoid these
 dominant (and very useful) formats is a realistic expectation.  It is
 certainly not "common sense" to assume as such.

Of course it's not a realistic expectation. There are times when it's a pain
to have to be safe - people will always break the rules when they're in a
hurry and the document to be sent is already in an unsafe format. But taking
plain text with absolutely no formatting, in fact text which is
_degenerated_ by word wrapping c, and gratuitously putting it in a Word
document is just _so_ unnecessary that I assumed it had to be a troll.


 fork.c: In function Œcopy_mm¹:

Given what this output's been through - I'll assume it's corrupted in 
transit, shall I? 

The kind of error you're seeing is often caused by a mismatch between 
compiler and kernel. As Alan suggests, you should make sure you're using a 
PPC-specific tree because it's not up to date in the stock 2.4.3. And make 
sure you're using the recommended versions of compiler and binutils. Other 
than that, I'm afraid I don't know.

--
dwmw2


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac10

[Geert Uytterhoeven]

On Thu, 19 Apr 2001, Alan Cox wrote:
 2.4.3-ac10
 o Merge Linus 2.4.4pre4
 o Reorder frame buffer probes (Geert Uytterhoeven)

These got somewhat mixed. Remove the duplicates:

--- linux-2.4.3-ac10/drivers/video/fbmem.c.orig Fri Apr 20 09:58:50 2001
+++ linux-2.4.3-ac10/drivers/video/fbmem.c  Fri Apr 20 11:33:28 2001
@@ -205,9 +205,6 @@
 #if defined(CONFIG_FB_SIS)  (defined(CONFIG_FB_SIS_300) || 
defined(CONFIG_FB_SIS_315))
{ "sisfb", sisfb_init, sisfb_setup },
 #endif
-#ifdef CONFIG_FB_E1355
-   { "e1355fb", e1355fb_init, e1355fb_setup },
-#endif
 
/*
 * Generic drivers that are used as fallbacks
@@ -275,9 +272,6 @@
 #endif
 #ifdef CONFIG_FB_E1355
{ "e1355fb", e1355fb_init, e1355fb_setup },
-#endif
-#ifdef CONFIG_FB_DC
-   { "dcfb", dcfb_init, NULL },
 #endif
 #ifdef CONFIG_FB_DC
{ "dcfb", dcfb_init, NULL },

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3 Compile Errors - Power Mac

[Paul Mackerras]

Jeff Galloway writes:

 Compiler error message:
 
 fork.c: In function Œcopy_mm:
 fork.c:353: fixed or forbidden register 68 (0) was spilled for class
 CR0_REGS.
 This may be due to a compiler bug or to impossible asm statements or
 clauses.

You need a newer gcc, I suspect you have egcs installed, and you need
to upgrade to gcc-2.95.2 or later.

Paul.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3 Compile Errors - Power Mac

[Jeff Galloway]

Thanks.  I'll try your suggestions and check on the version of my compiler
and binutils.

on 4/20/01 3:57 AM, David Woodhouse at [EMAIL PROTECTED] wrote:

 
 
 [EMAIL PROTECTED] said:
   However, I don't think that wishing the world would avoid these
 dominant (and very useful) formats is a realistic expectation.  It is
 certainly not "common sense" to assume as such.
 
 Of course it's not a realistic expectation. There are times when it's a pain
 to have to be safe - people will always break the rules when they're in a
 hurry and the document to be sent is already in an unsafe format. But taking
 plain text with absolutely no formatting, in fact text which is
 _degenerated_ by word wrapping c, and gratuitously putting it in a Word
 document is just _so_ unnecessary that I assumed it had to be a troll.
 
 
 fork.c: In function ?copy_mm:
 
 Given what this output's been through - I'll assume it's corrupted in
 transit, shall I?
 
 The kind of error you're seeing is often caused by a mismatch between
 compiler and kernel. As Alan suggests, you should make sure you're using a
 PPC-specific tree because it's not up to date in the stock 2.4.3. And make
 sure you're using the recommended versions of compiler and binutils. Other
 than that, I'm afraid I don't know.
 
 --
 dwmw2
 


Jeff Galloway
New York
[EMAIL PROTECTED]


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3 Compile Errors - Power Mac

[tom_gall]

Jeff Galloway wrote:
 
 Sorry, Tom about the word doc faux pas.  I've set out my problem in plain
 text below.  I got my source from ftp.kernel.org.

Hi Jeff,

  Well that's problem #1. Source from kernel.org for 2.4 tends to not work on
PPC as it has been lagging on important patches and such. We're hoping to get
kernel.org caught up ASAP.

  Visit here to get the up to date and sometime bleeding edge source for PPC.

  http://www.fsmlabs.com/linuxppcbk.html

 Here's my problem:
 
 Problem in compiling linux 2.4.3
 
 Compile error message:
 
 After the compiler message:
 
 gcc D__KERNEL__ -I/home/jeff/kernel/linux/include Wall
 Wstrict-prototypes O2 fomit-frame-pointer fno-strict-aliasing
 D__powerpc__ -fsigned-char msoft-float pipe ffixed-r2 Wno-uninitialized
 mmultiple mstring-c o fork.o fork.c
 
 Compiler error message:
 
 fork.c: In function ?copy_mm:
 fork.c:353: fixed or forbidden register 68 (0) was spilled for class
 CR0_REGS.
 This may be due to a compiler bug or to impossible asm statements or
 clauses.

Which version of gcc do you have? You want either 2.95.2 or 2.95.3



 cpp: output pipe has been closed
 make[2]: *** [fork.o] Error 1
 make[2]: Leaving directory ?/home/jeff/kernel/linux/kernel
 make[1]: *** [first_rule] Error 2
 make[1]: Leaving directory ?/home/jeff/kernel/linux/kernel
 make: *** [_dir_kernel] Error 2
 
 Compiling on Power Mac 7600, with dual processor (604e/180) installed,
 running kernel 2.2.18 compiled by Jeff Galloway, but otherwise a Yellow Dog
 distribution.

Ah YDL ... good stuff. Hope you are on 1.2 at least. 8-)

Regards,

Tom

-- 
Tom Gall - PowerPC Linux Team"Where's the ka-boom? There was
Linux Technology Center   supposed to be an earth
(w) [EMAIL PROTECTED] shattering ka-boom!"
(w) 507-253-4558 -- Marvin Martian
(h) [EMAIL PROTECTED]
http://oss.software.ibm.com/developerworks/opensource/linux
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Kernel Panic Linux 2.4.3 RH7

[lkern]

Machine has been locking up between 0-3 times a day
sporadically.  Nothing predictable about it. Hadn't locked up for 3
days, and locked 3x today, the last 2 times within 20 minutes of each 
other. Had run stable with 2.2.18, and was running fairly stable on 2.4.3
up until about last week.  (might be coincidence, or not, but seems to
happen when I am on IRC -- DOS?, nothing in log files or firewall logs
however)

Machine info:

RedHat 7, Intel Celeron 450, 256Meg ECC PC100 DRAM, 1 15G IDE (/usr, /tmp,
/home,
/var, swap ), 1 2G SCSI (/, /boot, swap) HDD, 2 identical tulip chipset
eth cards.

I just swapped the RAM out this last crash, seeing if that makes any
differences.

Kernel is configured as advanced router with packet filtering, ip
firewalling, NAT, IPTABLES and others enabled running a fairly
comprehensive iptables ruleset, nothing superhuge though.


Machine was recently upgraded to 2.4.3 kernel, from 2.2.18.
Dump message is partially as follows:

Mismatch in TCPACCEPT IN=ETH0 OUT= MAC= 00:00:e8:24:53

(some other stuff below this, but the machine then rolled to the below and
I couldn't finish copying down the above, remainder is as follows:

Kernel Panic:  Attempted to Kill init!
Unable to handle kernel paging request at virtual address e030a40c

printing eip:
c01194ae
*pid=
Oops: 
CPU: 0
Eip: 0010 [c01194ae7]
EFLAGS: 0010087

(stack information skipped, if you need it let me know and I will write it
all down the next time)

Process: swapper (pid0, stack page c02dl000)

stack 

Code 8b1186108b 590c85d274 088b410489 42048910

Kernel Panic: Aiee, killing interrupt handler
In interrupt handler - not syncing

Any ideas?

-buddy ellis


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Kernel Panic Linux 2.4.3 RH7

[Tim Haynes]

[EMAIL PROTECTED] writes:

 Machine has been locking up between 0-3 times a day sporadically. Nothing
 predictable about it. Hadn't locked up for 3 days, and locked 3x today,
 the last 2 times within 20 minutes of each other. Had run stable with
 2.2.18, and was running fairly stable on 2.4.3 up until about last week.
 (might be coincidence, or not, but seems to happen when I am on IRC --
 DOS?, nothing in log files or firewall logs however)
 
 Machine info:
 
 RedHat 7, Intel Celeron 450, 256Meg ECC PC100 DRAM, 1 15G IDE (/usr,
 /tmp, /home, /var, swap ), 1 2G SCSI (/, /boot, swap) HDD, 2 identical
 tulip chipset eth cards.
[snip]
 
 Mismatch in TCPACCEPT IN=ETH0 OUT= MAC= 00:00:e8:24:53
[snip]
 (stack information skipped, if you need it let me know and I will write it
 all down the next time)
 
 Process: swapper (pid0, stack page c02dl000)
[snip]

Take your pick from one or more of the following:
a) dodgy RAM - less likely if a different set of RAM has also had
   the problem;
b) a faulty network card - a tulip (Netgear FA310TX) reliably caused me
   a hang ~6 months ago, so there is a precedent;
c) overheating - see if, left to its own devices, the hangs become
   more frequent the longer the box is left on; also implement
   lm_sensors and keep an eye on the CPU temperature if possible;
d) RH7 alert: did you use kgcc to build the kernel?
e) Something totally else :8)

HTH,

~Tim
-- 
   10:32pm  up 3 days, 46 min, 10 users,  load average: 0.18, 0.10, 0.08
[EMAIL PROTECTED] |Clouds cross the black moonlight,
http://piglet.is.dreaming.org |Rushing on down to the sound 
  |of a turning world   
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Linux 2.4.3-ac11

[Alan Cox]

ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/

Intermediate diffs are available from

http://www.bzimage.org

You may well need to 'make clean' before building -ac8 as the GDT layout
has changed a little.

2.4.3-ac11
o   Merge Linus 2.4.4pre5
o   Back out problem dvdram changes
o   Make reiserfs use daemonize (Chris Mason)
o   Fix lvm map buglet  (Jens Axboe)
o   tms380 driver fixes (Adam Fritzler)
o   Fix up duplicate configs and other glitches (Steven Cole)
o   Fix pcnet32 printk format bug   (me)
o   ISDN driver further small update/fixes  (me)
o   Fix bounce buffer deadlock on bh allocs (Arjan van de Ven)
o   Fix fbmem merge glitch  (Geert Uytterhoeven)
o   Version string cleanups on net devices  (Jeff Garzik)
o   Update ext2 documentation   (Andreas Dilger)
o   Add MCE support for AMD Athlon/Duron(Dave Jones)
o   Further SDLA tidying(me)
o   Update Configure.help maintainers   (Steven Cole, Eric
 Raymond)
o   Tulip update(Jeff Garzik)
o   Fix sound config to use right symnames  (Eric Raymond)
o   Further dmfe fixes  (Tobias Ringstrom,
 Frank Davis
 Jeff Garzik)
o   Parport probe cleanups  (Tim Waugh)
o   Fix a few configure items   (Eric Raymond)
o   Fix cmsfs nonbuild  (me)


2.4.3-ac10
o   Merge Linus 2.4.4pre4
o   Apply the i960 quirk to the DPT I2O controllers (me)
o   Etrax100 updates(Bjorn Wesen)
o   Fix skge memory leak(Jes Sorensen)
o   Handle reiserfs log overflow error  (Chris Mason)
o   Merge JFFS2 (compressing log flash file system) (David Woodhouse)
o   Merge contributed help texts for options(Eric Raymond,
 Steven Cole)
o   Further screen blanking fixes   (Mikael Pettersson)
o   Further binfmt elf DLINFO fixes/alignment  (Benjamin Herrenschmidt)
o   Fix reboot notifier unregister in aic7xxx   (Arjan van de Ven)
o   Fix orinoco_cs build on powerpc (David Gibson)
o   Neomagic audio didn't call pci_enable_device(Marcus Meissner)
o   Remove superblock file size setting for 2Gb (Al Viro)
default size file systems
o   Merge UML gprof support (Jeff Dike)
o   Clean up UML slip code  (Jeff Dike)
o   Allow UML attach to already running debuggers   (Jeff Dike)
o   Reorder frame buffer probes (Geert Uytterhoeven)
o   Add __init calls to bluesmoke.c (Dave Jones)
o   Add missing pci_enable_device to toshoboe   (Marcus Meissner)
o   Updated AFFS file system(Roman Zippel)
o   DVD-RAM fixes   (Jens Axboe)
o   Further sundance driver fixes   (Jeff Garzik)
o   Fix qlogicfc warning(Dave Miller)
o   Fix sign handling error in scsi_ioctl   (me)
| Found by the Stanford validator
o   Fix sign handling error in af_decnet(me)
| Found by the Stanford validator
o   Fixed I2O posts to be uninterruptible   (me)
o   Stop IDE layer eating Supertrak slave PDC20265  (me)
o   Work around the DPT I2O controller exploding 
when asked to quiesce.  (me)


2.4.3-ac9
o   Fix ac8 pnpbios build bug   (me)
o   Fix ac8 sysrq build bug (me)
o   Fix uml for new semaphores  (Jeff Dike)
o   Attempt to flush low memory buffers when short
of bounce space on highmem machines (Marcelo Tosatti)
o   Kill old filesystem_setup function  (Al Viro)
o   Small pnp bios tidy up  (me)

2.4.3-ac8
o   Restore wan router features backed out by the   (me)
sangoma stuff Linus merged
o   Clean up #ifdefs in Sangoma code a bit  (me)
o   Fix missing kmalloc return checks in Sangoma(me)
o   Fix d_flags bit setting in knfsd(Mikael Pettersson)
o   Turn on winchip MCE (Dave Jones)
o   IRDA USB driver fixups  (Dag Brattli, 
Philipp Rumpf, Jean Tourrilhes)

Re: Linux 2.4.3-ac11

[J . A . Magallon]

On 04.21 Alan Cox wrote:
 
   ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/

gcc-2.96 spits warnings about possibly-used-before-initialized vars in
mtrr.c, line 2004:

static void __init centaur_mcr_init(void)
{
int lo,hi;
..
if (anything)
set hi,lo
else ??? unset
..
use lo, hi all around
}

Perhaps it never can happen, but...

-- 
J.A. Magallon  #  Let the source
mailto:[EMAIL PROTECTED]  #  be with you, Luke... 

Linux werewolf 2.4.3-ac9 #1 SMP Wed Apr 18 10:35:48 CEST 2001 i686

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac10

[Ion Badulescu]

On Thu, 19 Apr 2001, Jeff Garzik wrote:

> I should have gotten off my butt and mentioned this...  I would prefer a
> patch without the 2.2.x compat stuff.  So instead of all that compat
> code, have
>   #include "starfire-2.2.h"
> or similar...
> 
> And then starfire-2.2.h would only exist on 2.2.x.

Hard to please, aren't we. :-)

All right, is this version more pleasant to the eye? It's identical to the 
previous one, but with all the 2.2 ifdef'ed code replaced with an #include 
"starfire-kcomp22.h".

[Now of course starfire-kcomp22.h doesn't exist on 2.4, which -- if you 
stick to your own principles from 2 months ago -- will naturally lead to 
the question, what is this doing in the tree, it's referencing code that 
doesn't exist in the tree, etc, etc. And round and round we go again. :-{

Or maybe not. Hopefully...]

Thanks,
Ion

-- 
  It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.
---
--- /mnt/3/linux-2.4-ac/drivers/net/starfire.c  Thu Apr 19 15:58:57 2001
+++ linux-2.4/drivers/net/starfire.cThu Apr 19 21:39:24 2001
@@ -20,7 +20,7 @@
---
 
Linux kernel-specific changes:
-   
+
LK1.1.1 (jgarzik):
- Use PCI driver interface
- Fix MOD_xxx races
@@ -31,9 +31,45 @@
 
LK1.1.3 (Andrew Morton)
- Timer cleanups
-   
+
LK1.1.4 (jgarzik):
- Merge Becker version 1.03
+
+   LK1.2.1 (Ion Badulescu <[EMAIL PROTECTED]>)
+   - Support hardware Rx/Tx checksumming
+   - Use the GFP firmware taken from Adaptec's Netware driver
+
+   LK1.2.2 (Ion Badulescu)
+   - Backported to 2.2.x
+
+   LK1.2.3 (Ion Badulescu)
+   - Fix the flaky mdio interface
+   - More compat clean-ups
+
+   LK1.2.4 (Ion Badulescu)
+   - More 2.2.x initialization fixes
+
+   LK1.2.5 (Ion Badulescu)
+   - Several fixes from Manfred Spraul
+
+   LK1.2.6 (Ion Badulescu)
+   - Fixed ifup/ifdown/ifup problem in 2.4.x
+
+   LK1.2.7 (Ion Badulescu)
+   - Removed unused code
+   - Made more functions static and __init
+
+   LK1.2.8 (Ion Badulescu)
+   - Quell bogus error messages, inform about the Tx threshold
+   - Removed #ifdef CONFIG_PCI, this driver is PCI only
+
+   LK1.2.9 (Ion Badulescu)
+   - Merged Jeff Garzik's changes from 2.4.4-pre5
+   - Added 2.2.x compatibility stuff required by the above changes
+
+TODO:
+   - implement tx_timeout() properly
+   - support ethtool
 */
 
 /* These identify the driver base version and may not be removed. */
@@ -43,24 +79,60 @@
 " Updates and info at http://www.scyld.com/network/starfire.html\n";
 
 static const char version3[] =
-" (unofficial 2.4.x kernel port, version 1.1.4, August 10, 2000)\n";
+" (unofficial 2.4.x kernel port, version 1.2.9, April 19, 2001)\n";
+
+/*
+ * Adaptec's license for their Novell drivers (which is where I got the
+ * firmware files) does not allow one to redistribute them. Thus, we can't
+ * include the firmware with this driver.
+ *
+ * However, an end-user is allowed to download and use it, after
+ * converting it to C header files using starfire_firmware.pl.
+ * Once that's done, the #undef must be changed into a #define
+ * for this driver to really use the firmware. Note that Rx/Tx
+ * hardware TCP checksumming is not possible without the firmware.
+ *
+ * I'm currently [Feb 2001] talking to Adaptec about this redistribution
+ * issue. Stay tuned...
+ */
+#undef HAS_FIRMWARE
+/*
+ * The current frame processor firmware fails to checksum a fragment
+ * of length 1. If and when this is fixed, the #define below can be removed.
+ */
+#define HAS_BROKEN_FIRMWARE
 
 /* The user-configurable values.
These may be modified when a driver module is loaded.*/
 
 /* Used for tuning interrupt latency vs. overhead. */
-static int interrupt_mitigation = 0x0;
+static int interrupt_mitigation;
 
 static int debug = 1;  /* 1 normal messages, 0 quiet .. 7 verbose. */
 static int max_interrupt_work = 20;
-static int mtu = 0;
+static int mtu;
 /* Maximum number of multicast addresses to filter (vs. rx-all-multicast).
-   The Starfire has a 512 element hash table based on the Ethernet CRC.  */
-static int multicast_filter_limit = 32;
+   The Starfire has a 512 element hash table based on the Ethernet CRC. */
+static int multicast_filter_limit = 512;
 
-/* Set the copy breakpoint for the copy-only-tiny-frames scheme.
-   Setting to > 1518 effectively disables this feature. */
+#define PKT_BUF_SZ 1536/* Size of each temporary Rx buffer.*/
+/*
+ * Set the copy breakpoint for the copy-only-tiny-frames scheme.
+ * Setting to > 1518 effectively disables this feature.
+ *
+ * NOTE:
+ * The ia64 doesn't allow for unaligned loads even of integers being
+ * misaligned on a 2 byte boundary. Thus always force copying of
+ * packets as the starfire 

Re: Linux 2.4.3-ac10

[Jeff Garzik]

Ion wrote:
> On Thu, 19 Apr 2001 21:14:32 +0100 (BST), Alan Cox <[EMAIL PROTECTED]> wrote:
> 
> > 2.4.3-ac10
> > o   Merge Linus 2.4.4pre4
> 
> Well, it seems you have backed out my starfire changes when you merged
> Jeff Garzik's changes from 2.4.4pre4. So here's a new version, diff'ed
> against 2.4.3-ac10, which includes all of Jeff's changes from 2.4.3pre[45].
> 
> BTW Jeff, do you want me to send these updates to you instead of Alan,
> diff'ed against 2.4.x-pre_latest? Right now we're just wasting each
> other's time by making conflicting changes to different trees.

I should have gotten off my butt and mentioned this...  I would prefer a
patch without the 2.2.x compat stuff.  So instead of all that compat
code, have
#include "starfire-2.2.h"
or similar...

And then starfire-2.2.h would only exist on 2.2.x.

-- 
Jeff Garzik   | "The universe is like a safe to which there is a
Building 1024 |  combination -- but the combination is locked up
MandrakeSoft  |  in the safe."-- Peter DeVries
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac10

[Ion Badulescu]

On Thu, 19 Apr 2001 21:14:32 +0100 (BST), Alan Cox <[EMAIL PROTECTED]> wrote:

> 2.4.3-ac10
> o   Merge Linus 2.4.4pre4

Well, it seems you have backed out my starfire changes when you merged
Jeff Garzik's changes from 2.4.4pre4. So here's a new version, diff'ed
against 2.4.3-ac10, which includes all of Jeff's changes from 2.4.3pre[45].

BTW Jeff, do you want me to send these updates to you instead of Alan,
diff'ed against 2.4.x-pre_latest? Right now we're just wasting each
other's time by making conflicting changes to different trees.

Thanks,
Ion

-- 
  It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.
--
--- /mnt/3/linux-2.4-ac/drivers/net/starfire.c  Thu Apr 19 15:58:57 2001
+++ linux-2.4/drivers/net/starfire.cThu Apr 19 17:41:01 2001
@@ -20,7 +20,7 @@
---
 
Linux kernel-specific changes:
-   
+
LK1.1.1 (jgarzik):
- Use PCI driver interface
- Fix MOD_xxx races
@@ -31,9 +31,45 @@
 
LK1.1.3 (Andrew Morton)
- Timer cleanups
-   
+
LK1.1.4 (jgarzik):
- Merge Becker version 1.03
+
+   LK1.2.1 (Ion Badulescu <[EMAIL PROTECTED]>)
+   - Support hardware Rx/Tx checksumming
+   - Use the GFP firmware taken from Adaptec's Netware driver
+
+   LK1.2.2 (Ion Badulescu)
+   - Backported to 2.2.x
+
+   LK1.2.3 (Ion Badulescu)
+   - Fix the flaky mdio interface
+   - More compat clean-ups
+
+   LK1.2.4 (Ion Badulescu)
+   - More 2.2.x initialization fixes
+
+   LK1.2.5 (Ion Badulescu)
+   - Several fixes from Manfred Spraul
+
+   LK1.2.6 (Ion Badulescu)
+   - Fixed ifup/ifdown/ifup problem in 2.4.x
+
+   LK1.2.7 (Ion Badulescu)
+   - Removed unused code
+   - Made more functions static and __init
+
+   LK1.2.8 (Ion Badulescu)
+   - Quell bogus error messages, inform about the Tx threshold
+   - Removed #ifdef CONFIG_PCI, this driver is PCI only
+
+   LK1.2.9 (Ion Badulescu)
+   - Merged Jeff Garzik's changes from 2.4.4-pre5
+   - Added 2.2.x compatibility stuff required by the above changes
+
+TODO:
+   - implement tx_timeout() properly
+   - support ethtool
 */
 
 /* These identify the driver base version and may not be removed. */
@@ -43,24 +79,60 @@
 " Updates and info at http://www.scyld.com/network/starfire.html\n";
 
 static const char version3[] =
-" (unofficial 2.4.x kernel port, version 1.1.4, August 10, 2000)\n";
+" (unofficial 2.4.x kernel port, version 1.2.9, April 19, 2001)\n";
+
+/*
+ * Adaptec's license for their Novell drivers (which is where I got the
+ * firmware files) does not allow one to redistribute them. Thus, we can't
+ * include the firmware with this driver.
+ *
+ * However, an end-user is allowed to download and use it, after
+ * converting it to C header files using starfire_firmware.pl.
+ * Once that's done, the #undef must be changed into a #define
+ * for this driver to really use the firmware. Note that Rx/Tx
+ * hardware TCP checksumming is not possible without the firmware.
+ *
+ * I'm currently [Feb 2001] talking to Adaptec about this redistribution
+ * issue. Stay tuned...
+ */
+#undef HAS_FIRMWARE
+/*
+ * The current frame processor firmware fails to checksum a fragment
+ * of length 1. If and when this is fixed, the #define below can be removed.
+ */
+#define HAS_BROKEN_FIRMWARE
 
 /* The user-configurable values.
These may be modified when a driver module is loaded.*/
 
 /* Used for tuning interrupt latency vs. overhead. */
-static int interrupt_mitigation = 0x0;
+static int interrupt_mitigation;
 
 static int debug = 1;  /* 1 normal messages, 0 quiet .. 7 verbose. */
 static int max_interrupt_work = 20;
-static int mtu = 0;
+static int mtu;
 /* Maximum number of multicast addresses to filter (vs. rx-all-multicast).
-   The Starfire has a 512 element hash table based on the Ethernet CRC.  */
-static int multicast_filter_limit = 32;
+   The Starfire has a 512 element hash table based on the Ethernet CRC. */
+static int multicast_filter_limit = 512;
 
-/* Set the copy breakpoint for the copy-only-tiny-frames scheme.
-   Setting to > 1518 effectively disables this feature. */
+#define PKT_BUF_SZ 1536/* Size of each temporary Rx buffer.*/
+/*
+ * Set the copy breakpoint for the copy-only-tiny-frames scheme.
+ * Setting to > 1518 effectively disables this feature.
+ *
+ * NOTE:
+ * The ia64 doesn't allow for unaligned loads even of integers being
+ * misaligned on a 2 byte boundary. Thus always force copying of
+ * packets as the starfire doesn't allow for misaligned DMAs ;-(
+ * 23/10/2000 - Jes
+ *
+ * The Alpha and the Sparc don't allow unaligned loads, either. -Ion
+ */
+#if defined(__ia64__) || defined(__alpha__) || defined(__sparc__)
+static int rx_copybreak = PKT_BUF_SZ;
+#else
 static int rx_copybreak = 0;
+#endif
 
 

Re: FW: Linux 2.4.3 Compile Errors - Power Mac

[Alan Cox]

> I sent this report to the people indicated below, whose names I got from the
> MAINTAINERS file in the 2.4.3 distribution, but the email address for Mr.
> MacKerras is no longer good and Mr. Chastain wrote me back that he is not
> following 2.4 issues.

Well Keith is on holiday I believe and Paul is moving from Linuxcare.

> Any suggestions on the solution to my problem?

Build PPC from the linuxppc trees not the base one - it isnt yet all nicely
merged in 2.4
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: FW: Linux 2.4.3 Compile Errors - Power Mac

[David Woodhouse]

[EMAIL PROTECTED] said:
>  I have not yet heard from Mr. Owens.

This does not surprise me, given the content of your email.

> The compiler error message along with the menuconfig-generated
> configuration file are set out in the attached MS Word document.

I have to assume that you're just winding us up here, rather than genuinely
in need of assistance. Word documents are not an appropriate form in which
to exchange such information across security domains; especially in public
fora - and I won't insult your intelligence by assuming that you believe
otherwise.

cf. http://www.infradead.org/fileexchange.html

--
dwmw2


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: FW: Linux 2.4.3 Compile Errors - Power Mac

[tom_gall]

Jeff Galloway wrote:
> 
> I sent this report to the people indicated below, whose names I got from the
> MAINTAINERS file in the 2.4.3 distribution, but the email address for Mr.
> MacKerras is no longer good and Mr. Chastain wrote me back that he is not
> following 2.4 issues.

Hi Jeff,

  Hmm Paul is around his email just changed and the pmac maintainer is now
Ben, but that issue aside where did you get your 2.4.3 sources from that you are
trying to build?

  http://www.fsmlabs.com/linuxppcbk.html is the location you want to pull stuff
from.

> I have not yet heard from Mr. Owens.
> 
> Any suggestions on the solution to my problem?

  Well suggestion one is DON'T GIVE US A WORD DOCUMENT! Plain text please, then
we can actually read what's wrong.

  Best to post to [EMAIL PROTECTED] That's one of the lists that
the PPC Linux watches.
 
Regards,

Tom

-- 
Tom Gall - PowerPC Linux Team"Where's the ka-boom? There was
Linux Technology Center   supposed to be an earth
(w) [EMAIL PROTECTED] shattering ka-boom!"
(w) 507-253-4558 -- Marvin Martian
(h) [EMAIL PROTECTED]
http://oss.software.ibm.com/developerworks/opensource/linux
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

FW: Linux 2.4.3 Compile Errors - Power Mac

[Jeff Galloway]

I sent this report to the people indicated below, whose names I got from the
MAINTAINERS file in the 2.4.3 distribution, but the email address for Mr.
MacKerras is no longer good and Mr. Chastain wrote me back that he is not
following 2.4 issues.

I have not yet heard from Mr. Owens.

Any suggestions on the solution to my problem?


Jeff Galloway
New York
[EMAIL PROTECTED]


-- Forwarded Message
From: Jeff Galloway <[EMAIL PROTECTED]>
Date: Thu, 19 Apr 2001 00:38:46 -0400
To: Michael Elizabeth Chastain <[EMAIL PROTECTED]>, Keith Owens
<[EMAIL PROTECTED]>, Paul Mackerras <[EMAIL PROTECTED]>
Subject: Linux 2.4.3 Compile Errors - Power Mac

I have been unable to compile the 2.4 kernel on my Power Mac 7600 (with a
dual 604e/180 processor installed, running kernel 2.2.18 in single processor
mode (which I compiled), but otherwise with the Yellow Dog (Red Hat)
distribution files, including gcc compiler).

The compiler error message along with the menuconfig-generated configuration
file are set out in the attached MS Word document.  I've had similar
problems with other versions of 2.4.

Any suggestions?



Jeff Galloway
New York
[EMAIL PROTECTED]


-- End of Forwarded Message


 Problem in compiling linu.doc

Linux 2.4.3-ac10

[Alan Cox]

ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/

Intermediate diffs are available from

http://www.bzimage.org

You may well need to 'make clean' before building -ac8 as the GDT layout
has changed a little.

2.4.3-ac10
o   Merge Linus 2.4.4pre4
o   Apply the i960 quirk to the DPT I2O controllers (me)
o   Etrax100 updates(Bjorn Wesen)
o   Fix skge memory leak(Jes Sorensen)
o   Handle reiserfs log overflow error  (Chris Mason)
o   Merge JFFS2 (compressing log flash file system) (David Woodhouse)
o   Merge contributed help texts for options(Eric Raymond,
 Steven Cole)
o   Further screen blanking fixes   (Mikael Pettersson)
o   Further binfmt elf DLINFO fixes/alignment  (Benjamin Herrenschmidt)
o   Fix reboot notifier unregister in aic7xxx   (Arjan van de Ven)
o   Fix orinoco_cs build on powerpc (David Gibson)
o   Neomagic audio didn't call pci_enable_device(Marcus Meissner)
o   Remove superblock file size setting for 2Gb (Al Viro)
default size file systems
o   Merge UML gprof support (Jeff Dike)
o   Clean up UML slip code  (Jeff Dike)
o   Allow UML attach to already running debuggers   (Jeff Dike)
o   Reorder frame buffer probes (Geert Uytterhoeven)
o   Add __init calls to bluesmoke.c (Dave Jones)
o   Add missing pci_enable_device to toshoboe   (Marcus Meissner)
o   Updated AFFS file system(Roman Zippel)
o   DVD-RAM fixes   (Jens Axboe)
o   Further sundance driver fixes   (Jeff Garzik)
o   Fix qlogicfc warning(Dave Miller)
o   Fix sign handling error in scsi_ioctl   (me)
| Found by the Stanford validator
o   Fix sign handling error in af_decnet(me)
| Found by the Stanford validator
o   Fixed i2o posts to be uninterruptible   (me)
o   Stop I2O layer eating Supertrak slave PDC20265  (me)
o   Work around the DPT I2O controller exploding 
when asked to quiesce.  (me)


2.4.3-ac9
o   Fix ac8 pnpbios build bug   (me)
o   Fix ac8 sysrq build bug (me)
o   Fix uml for new semaphores  (Jeff Dike)
o   Attempt to flush low memory buffers when short
of bounce space on highmem machines (Marcelo Tosatti)
o   Kill old filesystem_setup function  (Al Viro)
o   Small pnp bios tidy up  (me)

2.4.3-ac8
o   Restore wan router features backed out by the   (me)
sangoma stuff Linus merged
o   Clean up #ifdefs in Sangoma code a bit  (me)
o   Fix missing kmalloc return checks in Sangoma(me)
o   Fix d_flags bit setting in knfsd(Mikael Pettersson)
o   Turn on winchip MCE (Dave Jones)
o   IRDA USB driver fixups  (Dag Brattli, 
Philipp Rumpf, Jean Tourrilhes)
o   Tidy up cpu capability mask reporting   (Rogier Wolff)
o   Refix icmp gcc warnings (Andrzej M. Krzysztofowicz)
o   Remove 2.0 ioremap hacks from ISDN layer(Kai Germaschewski)
o   Fix request_region ranges on hisax/bkm_a8   (Roland Klabunde)
o   Add rx fifo overlfow handling to pci hisax  (Werner Cornelius)
o   Hysdn driver updates(Ulrich Albrecht)
o   Rewrite cisco hdlc keepalive code   (Bjoern Zeeb,
 Kai Germaschewski)
o   Document CONFIG_TMSISA  (Jochen Friedrich)
o   Fix emu10k memory leak  (Hugh Dickins)
o   Fix i810 audio SMP lockups  (Doug Ledford)
o   Merge binfmt_elf changes for PPC(Benjamin Herrenschmidt)
o   Make sysrq keybindings a clean API  (Crutcher Dunvant)
| I think I caught all the sysrq updates from after
| the patch was written and got them right - please check
o   Merge PnP bios enumeration and PnP BIOS (Christian Schmidt,
parport support (Tom Lees, David Hinds, Gunther Mayer)
o   Bit more experimental work on fixing bounce (Marcelo Tosatti, me)
buffers

2.4.3-ac7
o   Updated VIA quirk handling for the chipset  (Andre Hedrick,
flawsGeorge Breese)
| Experimental version removed
| VIA users should check this kernel -carefully-
o   Remove KT7 

Re: [linux-power]Re: Linux 2.4.3-ac7

[Akos Maroy]

Martin Hamilton wrote:

> FWIW, I didn't have any luck with the 2.4.3 swsusp-v8pre3 patch - my
> C1VE suspended to disk, but on re-reading the memory image from swap
> space the machine reset and we were back to the LILO prompt & fsck.

I can confirm Martin's experience, I got the same results.

Akos

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac7

[Martin Hamilton]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Content-Type: text/plain; charset=us-ascii

(cc'd to the acpi list, where people have also been talking about 
this recently...)

Ookhoi writes:

| I tried swsusp on my vaio (also a c1ve :-) and it didn't work because it
| (said it) couldn't stop [kreiserfsd]. :-(  It didn't do any harm also
| afaics. 

FWIW, I didn't have any luck with the 2.4.3 swsusp-v8pre3 patch - my
C1VE suspended to disk, but on re-reading the memory image from swap
space the machine reset and we were back to the LILO prompt & fsck.

I tried turning everything off at build time that I didn't need to
actually boot the machine, and with 'CONFIG_HWSTATE_RESTORE' both on
and off - to no avail.  Will do a bit more digging to see if I can
figure out the problem, since I was enjoying running the bleeding edge
kernels on this box...

On the other hand the swsusp-v7c patch worked against 2.2.19 with only
minor tweakings, and presumably out-of-the-box against 2.2.18, which
is what it was actually indended for.  Yay!

Just so you don't get your hopes up too high, with this patch (only
tried with CONFIG_HWSTATE_RESTORE off so far) I still had to restart
networking and X after powering up again.  Compared with a full reboot
(of RedHat 7.1!) that's a small price to pay ;-)

But as Alan Cox says, expected the unexpected if you use this in
conjunction with ext3 or ReiserFS at the minute... !

Cheers,

Martin



-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999 + martin

iD8DBQE63r9gVw+hz3xBJfQRAnVLAKCaKjSbR7wbRMGQIEFYMRXNDDM8tgCffGTO
MAC6PG1MyHCcaD7vsCvpdh4=
=7nBk
-END PGP SIGNATURE-

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac7

[Martin Hamilton]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Content-Type: text/plain; charset=us-ascii

"Grover, Andrew" writes:

| I don't think I understand that first sentence. (Let me respond anyways ;-)

Doh!  Sorry, what I meant was that (if I'm understanding this right!)
the AML interpreter being embedded in the kernel in 2.4.x is Intel's
platform-independent solution to the problem of providing support for
ACPI under Unix, so that you don't have to code up ACPI stuff
independently for the vagaries of each Unix variant's kernel.

So, it's good for you, but not necessarily optimal for any particular 
Unix variant, right ?  e.g. this could perhaps be simplified 
somewhat..

  [root@porcupine acpi]# pwd
  /usr/src/linux-2.4.3-ac9-swsusp-jogutils/drivers/acpi
  [root@porcupine acpi]# wc -l `find . -type f` | grep total
59435 total

My gripe is taken care of now, though - swsusp is working :-)

Cheers,

Martin




-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999 + martin

iD8DBQE63ryhVw+hz3xBJfQRAkzDAJ9eVSJUK7mPZqUyqpvl/yOJSkiAsQCeJjtN
153+/FDFzNKht/7iTKYSI0k=
=0C2p
-END PGP SIGNATURE-

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac7

[Ookhoi]

> > > I was wondering whether the swsusp work might form a useful basis
> > > for the eventual ACPI implementation of the to-disk hibernation
> > > stuff:
> > 
> > I (and others) have looked at it. It's a pretty cool patch, but it
> > really isn't the right way to do things.
> 
> swsusp is most definitely the right way to do things. It works on my
> laptop which has non suspend to disk APM, it even works on my MVP3
> board where ACPI bombs totally (BIOS bug).
> 
> It might not be the right thing to do if ACPI suspend is present
> though.
> 
> Actually swsusp has one minor problem. Because of implementation bugs
> in some of the journalled file systems like ext3 using swsusp with
> those file systems can corrupt your disks (they write to disk even
> when told to mount read only rather than replaying the log to disk
> when the mount goes r/w - which is really antisocial, breaks if you
> are trying to recover from a failed disk and wants fixing.)

I tried swsusp on my vaio (also a c1ve :-) and it didn't work because it
(said it) couldn't stop [kreiserfsd]. :-(  It didn't do any harm also
afaics. 
I have zero experience with apm and acpi, but the thing I liked about
swsusp is that it works with a sysrq key combo. 

Ookhoi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac7

[Ookhoi]

   I was wondering whether the swsusp work might form a useful basis
   for the eventual ACPI implementation of the to-disk hibernation
   stuff:
  
  I (and others) have looked at it. It's a pretty cool patch, but it
  really isn't the right way to do things.
 
 swsusp is most definitely the right way to do things. It works on my
 laptop which has non suspend to disk APM, it even works on my MVP3
 board where ACPI bombs totally (BIOS bug).
 
 It might not be the right thing to do if ACPI suspend is present
 though.
 
 Actually swsusp has one minor problem. Because of implementation bugs
 in some of the journalled file systems like ext3 using swsusp with
 those file systems can corrupt your disks (they write to disk even
 when told to mount read only rather than replaying the log to disk
 when the mount goes r/w - which is really antisocial, breaks if you
 are trying to recover from a failed disk and wants fixing.)

I tried swsusp on my vaio (also a c1ve :-) and it didn't work because it
(said it) couldn't stop [kreiserfsd]. :-(  It didn't do any harm also
afaics. 
I have zero experience with apm and acpi, but the thing I liked about
swsusp is that it works with a sysrq key combo. 

Ookhoi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac7

[Martin Hamilton]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Content-Type: text/plain; charset=us-ascii

"Grover, Andrew" writes:

| I don't think I understand that first sentence. (Let me respond anyways ;-)

Doh!  Sorry, what I meant was that (if I'm understanding this right!)
the AML interpreter being embedded in the kernel in 2.4.x is Intel's
platform-independent solution to the problem of providing support for
ACPI under Unix, so that you don't have to code up ACPI stuff
independently for the vagaries of each Unix variant's kernel.

So, it's good for you, but not necessarily optimal for any particular 
Unix variant, right ?  e.g. this could perhaps be simplified 
somewhat..

  [root@porcupine acpi]# pwd
  /usr/src/linux-2.4.3-ac9-swsusp-jogutils/drivers/acpi
  [root@porcupine acpi]# wc -l `find . -type f` | grep total
59435 total

My gripe is taken care of now, though - swsusp is working :-)

Cheers,

Martin




-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999 + martin

iD8DBQE63ryhVw+hz3xBJfQRAkzDAJ9eVSJUK7mPZqUyqpvl/yOJSkiAsQCeJjtN
153+/FDFzNKht/7iTKYSI0k=
=0C2p
-END PGP SIGNATURE-

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac7

[Martin Hamilton]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Content-Type: text/plain; charset=us-ascii

(cc'd to the acpi list, where people have also been talking about 
this recently...)

Ookhoi writes:

| I tried swsusp on my vaio (also a c1ve :-) and it didn't work because it
| (said it) couldn't stop [kreiserfsd]. :-(  It didn't do any harm also
| afaics. 

FWIW, I didn't have any luck with the 2.4.3 swsusp-v8pre3 patch - my
C1VE suspended to disk, but on re-reading the memory image from swap
space the machine reset and we were back to the LILO prompt  fsck.

I tried turning everything off at build time that I didn't need to
actually boot the machine, and with 'CONFIG_HWSTATE_RESTORE' both on
and off - to no avail.  Will do a bit more digging to see if I can
figure out the problem, since I was enjoying running the bleeding edge
kernels on this box...

On the other hand the swsusp-v7c patch worked against 2.2.19 with only
minor tweakings, and presumably out-of-the-box against 2.2.18, which
is what it was actually indended for.  Yay!

Just so you don't get your hopes up too high, with this patch (only
tried with CONFIG_HWSTATE_RESTORE off so far) I still had to restart
networking and X after powering up again.  Compared with a full reboot
(of RedHat 7.1!) that's a small price to pay ;-)

But as Alan Cox says, expected the unexpected if you use this in
conjunction with ext3 or ReiserFS at the minute... !

Cheers,

Martin



-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999 + martin

iD8DBQE63r9gVw+hz3xBJfQRAnVLAKCaKjSbR7wbRMGQIEFYMRXNDDM8tgCffGTO
MAC6PG1MyHCcaD7vsCvpdh4=
=7nBk
-END PGP SIGNATURE-

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [linux-power]Re: Linux 2.4.3-ac7

[Akos Maroy]

Martin Hamilton wrote:

 FWIW, I didn't have any luck with the 2.4.3 swsusp-v8pre3 patch - my
 C1VE suspended to disk, but on re-reading the memory image from swap
 space the machine reset and we were back to the LILO prompt  fsck.

I can confirm Martin's experience, I got the same results.

Akos

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Linux 2.4.3-ac10

[Alan Cox]

ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/

Intermediate diffs are available from

http://www.bzimage.org

You may well need to 'make clean' before building -ac8 as the GDT layout
has changed a little.

2.4.3-ac10
o   Merge Linus 2.4.4pre4
o   Apply the i960 quirk to the DPT I2O controllers (me)
o   Etrax100 updates(Bjorn Wesen)
o   Fix skge memory leak(Jes Sorensen)
o   Handle reiserfs log overflow error  (Chris Mason)
o   Merge JFFS2 (compressing log flash file system) (David Woodhouse)
o   Merge contributed help texts for options(Eric Raymond,
 Steven Cole)
o   Further screen blanking fixes   (Mikael Pettersson)
o   Further binfmt elf DLINFO fixes/alignment  (Benjamin Herrenschmidt)
o   Fix reboot notifier unregister in aic7xxx   (Arjan van de Ven)
o   Fix orinoco_cs build on powerpc (David Gibson)
o   Neomagic audio didn't call pci_enable_device(Marcus Meissner)
o   Remove superblock file size setting for 2Gb (Al Viro)
default size file systems
o   Merge UML gprof support (Jeff Dike)
o   Clean up UML slip code  (Jeff Dike)
o   Allow UML attach to already running debuggers   (Jeff Dike)
o   Reorder frame buffer probes (Geert Uytterhoeven)
o   Add __init calls to bluesmoke.c (Dave Jones)
o   Add missing pci_enable_device to toshoboe   (Marcus Meissner)
o   Updated AFFS file system(Roman Zippel)
o   DVD-RAM fixes   (Jens Axboe)
o   Further sundance driver fixes   (Jeff Garzik)
o   Fix qlogicfc warning(Dave Miller)
o   Fix sign handling error in scsi_ioctl   (me)
| Found by the Stanford validator
o   Fix sign handling error in af_decnet(me)
| Found by the Stanford validator
o   Fixed i2o posts to be uninterruptible   (me)
o   Stop I2O layer eating Supertrak slave PDC20265  (me)
o   Work around the DPT I2O controller exploding 
when asked to quiesce.  (me)


2.4.3-ac9
o   Fix ac8 pnpbios build bug   (me)
o   Fix ac8 sysrq build bug (me)
o   Fix uml for new semaphores  (Jeff Dike)
o   Attempt to flush low memory buffers when short
of bounce space on highmem machines (Marcelo Tosatti)
o   Kill old filesystem_setup function  (Al Viro)
o   Small pnp bios tidy up  (me)

2.4.3-ac8
o   Restore wan router features backed out by the   (me)
sangoma stuff Linus merged
o   Clean up #ifdefs in Sangoma code a bit  (me)
o   Fix missing kmalloc return checks in Sangoma(me)
o   Fix d_flags bit setting in knfsd(Mikael Pettersson)
o   Turn on winchip MCE (Dave Jones)
o   IRDA USB driver fixups  (Dag Brattli, 
Philipp Rumpf, Jean Tourrilhes)
o   Tidy up cpu capability mask reporting   (Rogier Wolff)
o   Refix icmp gcc warnings (Andrzej M. Krzysztofowicz)
o   Remove 2.0 ioremap hacks from ISDN layer(Kai Germaschewski)
o   Fix request_region ranges on hisax/bkm_a8   (Roland Klabunde)
o   Add rx fifo overlfow handling to pci hisax  (Werner Cornelius)
o   Hysdn driver updates(Ulrich Albrecht)
o   Rewrite cisco hdlc keepalive code   (Bjoern Zeeb,
 Kai Germaschewski)
o   Document CONFIG_TMSISA  (Jochen Friedrich)
o   Fix emu10k memory leak  (Hugh Dickins)
o   Fix i810 audio SMP lockups  (Doug Ledford)
o   Merge binfmt_elf changes for PPC(Benjamin Herrenschmidt)
o   Make sysrq keybindings a clean API  (Crutcher Dunvant)
| I think I caught all the sysrq updates from after
| the patch was written and got them right - please check
o   Merge PnP bios enumeration and PnP BIOS (Christian Schmidt,
parport support (Tom Lees, David Hinds, Gunther Mayer)
o   Bit more experimental work on fixing bounce (Marcelo Tosatti, me)
buffers

2.4.3-ac7
o   Updated VIA quirk handling for the chipset  (Andre Hedrick,
flawsGeorge Breese)
| Experimental version removed
| VIA users should check this kernel -carefully-
o   Remove KT7 

FW: Linux 2.4.3 Compile Errors - Power Mac

[Jeff Galloway]

I sent this report to the people indicated below, whose names I got from the
MAINTAINERS file in the 2.4.3 distribution, but the email address for Mr.
MacKerras is no longer good and Mr. Chastain wrote me back that he is not
following 2.4 issues.

I have not yet heard from Mr. Owens.

Any suggestions on the solution to my problem?


Jeff Galloway
New York
[EMAIL PROTECTED]


-- Forwarded Message
From: Jeff Galloway [EMAIL PROTECTED]
Date: Thu, 19 Apr 2001 00:38:46 -0400
To: Michael Elizabeth Chastain [EMAIL PROTECTED], Keith Owens
[EMAIL PROTECTED], Paul Mackerras [EMAIL PROTECTED]
Subject: Linux 2.4.3 Compile Errors - Power Mac

I have been unable to compile the 2.4 kernel on my Power Mac 7600 (with a
dual 604e/180 processor installed, running kernel 2.2.18 in single processor
mode (which I compiled), but otherwise with the Yellow Dog (Red Hat)
distribution files, including gcc compiler).

The compiler error message along with the menuconfig-generated configuration
file are set out in the attached MS Word document.  I've had similar
problems with other versions of 2.4.

Any suggestions?



Jeff Galloway
New York
[EMAIL PROTECTED]


-- End of Forwarded Message


 Problem in compiling linu.doc

Re: FW: Linux 2.4.3 Compile Errors - Power Mac

[tom_gall]

Jeff Galloway wrote:
 
 I sent this report to the people indicated below, whose names I got from the
 MAINTAINERS file in the 2.4.3 distribution, but the email address for Mr.
 MacKerras is no longer good and Mr. Chastain wrote me back that he is not
 following 2.4 issues.

Hi Jeff,

  Hmm Paul is around his email just changed and the pmac maintainer is now
Ben, but that issue aside where did you get your 2.4.3 sources from that you are
trying to build?

  http://www.fsmlabs.com/linuxppcbk.html is the location you want to pull stuff
from.

 I have not yet heard from Mr. Owens.
 
 Any suggestions on the solution to my problem?

  Well suggestion one is DON'T GIVE US A WORD DOCUMENT! Plain text please, then
we can actually read what's wrong.

  Best to post to [EMAIL PROTECTED] That's one of the lists that
the PPC Linux watches.
 
Regards,

Tom

-- 
Tom Gall - PowerPC Linux Team"Where's the ka-boom? There was
Linux Technology Center   supposed to be an earth
(w) [EMAIL PROTECTED] shattering ka-boom!"
(w) 507-253-4558 -- Marvin Martian
(h) [EMAIL PROTECTED]
http://oss.software.ibm.com/developerworks/opensource/linux
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: FW: Linux 2.4.3 Compile Errors - Power Mac

[David Woodhouse]

[EMAIL PROTECTED] said:
  I have not yet heard from Mr. Owens.

This does not surprise me, given the content of your email.

 The compiler error message along with the menuconfig-generated
 configuration file are set out in the attached MS Word document.

I have to assume that you're just winding us up here, rather than genuinely
in need of assistance. Word documents are not an appropriate form in which
to exchange such information across security domains; especially in public
fora - and I won't insult your intelligence by assuming that you believe
otherwise.

cf. http://www.infradead.org/fileexchange.html

--
dwmw2


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: FW: Linux 2.4.3 Compile Errors - Power Mac

[Alan Cox]

 I sent this report to the people indicated below, whose names I got from the
 MAINTAINERS file in the 2.4.3 distribution, but the email address for Mr.
 MacKerras is no longer good and Mr. Chastain wrote me back that he is not
 following 2.4 issues.

Well Keith is on holiday I believe and Paul is moving from Linuxcare.

 Any suggestions on the solution to my problem?

Build PPC from the linuxppc trees not the base one - it isnt yet all nicely
merged in 2.4
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac10

[Ion Badulescu]

On Thu, 19 Apr 2001 21:14:32 +0100 (BST), Alan Cox [EMAIL PROTECTED] wrote:

 2.4.3-ac10
 o   Merge Linus 2.4.4pre4

Well, it seems you have backed out my starfire changes when you merged
Jeff Garzik's changes from 2.4.4pre4. So here's a new version, diff'ed
against 2.4.3-ac10, which includes all of Jeff's changes from 2.4.3pre[45].

BTW Jeff, do you want me to send these updates to you instead of Alan,
diff'ed against 2.4.x-pre_latest? Right now we're just wasting each
other's time by making conflicting changes to different trees.

Thanks,
Ion

-- 
  It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.
--
--- /mnt/3/linux-2.4-ac/drivers/net/starfire.c  Thu Apr 19 15:58:57 2001
+++ linux-2.4/drivers/net/starfire.cThu Apr 19 17:41:01 2001
@@ -20,7 +20,7 @@
---
 
Linux kernel-specific changes:
-   
+
LK1.1.1 (jgarzik):
- Use PCI driver interface
- Fix MOD_xxx races
@@ -31,9 +31,45 @@
 
LK1.1.3 (Andrew Morton)
- Timer cleanups
-   
+
LK1.1.4 (jgarzik):
- Merge Becker version 1.03
+
+   LK1.2.1 (Ion Badulescu [EMAIL PROTECTED])
+   - Support hardware Rx/Tx checksumming
+   - Use the GFP firmware taken from Adaptec's Netware driver
+
+   LK1.2.2 (Ion Badulescu)
+   - Backported to 2.2.x
+
+   LK1.2.3 (Ion Badulescu)
+   - Fix the flaky mdio interface
+   - More compat clean-ups
+
+   LK1.2.4 (Ion Badulescu)
+   - More 2.2.x initialization fixes
+
+   LK1.2.5 (Ion Badulescu)
+   - Several fixes from Manfred Spraul
+
+   LK1.2.6 (Ion Badulescu)
+   - Fixed ifup/ifdown/ifup problem in 2.4.x
+
+   LK1.2.7 (Ion Badulescu)
+   - Removed unused code
+   - Made more functions static and __init
+
+   LK1.2.8 (Ion Badulescu)
+   - Quell bogus error messages, inform about the Tx threshold
+   - Removed #ifdef CONFIG_PCI, this driver is PCI only
+
+   LK1.2.9 (Ion Badulescu)
+   - Merged Jeff Garzik's changes from 2.4.4-pre5
+   - Added 2.2.x compatibility stuff required by the above changes
+
+TODO:
+   - implement tx_timeout() properly
+   - support ethtool
 */
 
 /* These identify the driver base version and may not be removed. */
@@ -43,24 +79,60 @@
 " Updates and info at http://www.scyld.com/network/starfire.html\n";
 
 static const char version3[] =
-" (unofficial 2.4.x kernel port, version 1.1.4, August 10, 2000)\n";
+" (unofficial 2.4.x kernel port, version 1.2.9, April 19, 2001)\n";
+
+/*
+ * Adaptec's license for their Novell drivers (which is where I got the
+ * firmware files) does not allow one to redistribute them. Thus, we can't
+ * include the firmware with this driver.
+ *
+ * However, an end-user is allowed to download and use it, after
+ * converting it to C header files using starfire_firmware.pl.
+ * Once that's done, the #undef must be changed into a #define
+ * for this driver to really use the firmware. Note that Rx/Tx
+ * hardware TCP checksumming is not possible without the firmware.
+ *
+ * I'm currently [Feb 2001] talking to Adaptec about this redistribution
+ * issue. Stay tuned...
+ */
+#undef HAS_FIRMWARE
+/*
+ * The current frame processor firmware fails to checksum a fragment
+ * of length 1. If and when this is fixed, the #define below can be removed.
+ */
+#define HAS_BROKEN_FIRMWARE
 
 /* The user-configurable values.
These may be modified when a driver module is loaded.*/
 
 /* Used for tuning interrupt latency vs. overhead. */
-static int interrupt_mitigation = 0x0;
+static int interrupt_mitigation;
 
 static int debug = 1;  /* 1 normal messages, 0 quiet .. 7 verbose. */
 static int max_interrupt_work = 20;
-static int mtu = 0;
+static int mtu;
 /* Maximum number of multicast addresses to filter (vs. rx-all-multicast).
-   The Starfire has a 512 element hash table based on the Ethernet CRC.  */
-static int multicast_filter_limit = 32;
+   The Starfire has a 512 element hash table based on the Ethernet CRC. */
+static int multicast_filter_limit = 512;
 
-/* Set the copy breakpoint for the copy-only-tiny-frames scheme.
-   Setting to  1518 effectively disables this feature. */
+#define PKT_BUF_SZ 1536/* Size of each temporary Rx buffer.*/
+/*
+ * Set the copy breakpoint for the copy-only-tiny-frames scheme.
+ * Setting to  1518 effectively disables this feature.
+ *
+ * NOTE:
+ * The ia64 doesn't allow for unaligned loads even of integers being
+ * misaligned on a 2 byte boundary. Thus always force copying of
+ * packets as the starfire doesn't allow for misaligned DMAs ;-(
+ * 23/10/2000 - Jes
+ *
+ * The Alpha and the Sparc don't allow unaligned loads, either. -Ion
+ */
+#if defined(__ia64__) || defined(__alpha__) || defined(__sparc__)
+static int rx_copybreak = PKT_BUF_SZ;
+#else
 static int rx_copybreak = 0;
+#endif
 
 /* Used