Re: [ANNOUNCE] Generalised Kernel Hooks Interface (GKHI)

[Larry McVoy]

On Thu, Nov 09, 2000 at 08:44:11AM +0100, Christoph Rohland wrote:
> Hi Michael,
> 
> On Wed, 08 Nov 2000, Michael Rothwell wrote:
> > Sounds great; unfortunately, the core group has spoken out against a
> > modular kernel.
> > 
> > Perhaps IBM should get together with SGI, HP and other interested
> > parties and start an Advanced Linux Kernel Project. Then they can
> > run off and make their scalable, modular, enterprise kernel and the
> > Linus Version can always merge back in features from it.
> 
> *Are you crazy?* =:-0 
> 
> Proposing proprietary kernel extensions to establish an enterprise
> kernel? No thanks!

Actually, I think this idea is a good one.  I'm a big opponent of all the
big iron feature bloat getting into the kernel, and if SGI et al want to
go off and do their own thing, that's fine with me.  As long as Linus 
continues in his current role, I doubt much of anything that the big iron
boys do will really make it back into the generic kernel.  Linus is really
smart about that stuff, are least it seems so to me; he seems to be well
aware that 99.% of the hardware in the world isn't big iron and never
will be, so something approximating 99% of the effort should be going towards
the common platforms, not the uncommon ones.
-- 
---
Larry McVoy  lm at bitmover.com   http://www.bitmover.com/lm 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: [ANNOUNCE] Generalised Kernel Hooks Interface (GKHI)

[Christoph Rohland]

Hi Michael,

On Wed, 08 Nov 2000, Michael Rothwell wrote:
> Sounds great; unfortunately, the core group has spoken out against a
> modular kernel.
> 
> Perhaps IBM should get together with SGI, HP and other interested
> parties and start an Advanced Linux Kernel Project. Then they can
> run off and make their scalable, modular, enterprise kernel and the
> Linus Version can always merge back in features from it.

*Are you crazy?* =:-0 

Proposing proprietary kernel extensions to establish an enterprise
kernel? No thanks!

Greetings
Christoph

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

Re: [bug] usb-uhci locks up on boot half the time

[David Ford]

Sigh.  That's not the real hang position.  I needed to step slower.

kdb> ss
0xc01100f8 pci_conf1_write_config_word+0x40:   outw   %ax,(%dx)
SS trap at 0xc01100fa (pci_conf1_write_config_word+0x42)
0xc01100fa pci_conf1_write_config_word+0x42:   popl   %ebx
kdb> ss
0xc01100fa pci_conf1_write_config_word+0x42:   popl   %ebx
SS trap at 0xc01100fb (pci_conf1_write_config_word+0x43)
0xc01100fb pci_conf1_write_config_word+0x43:   xorl   %eax,%eax
kdb> ss
0xc01100fb pci_conf1_write_config_word+0x43:   xorl   %eax,%eax
SS trap at 0xc01100fd (pci_conf1_write_config_word+0x45)
0xc01100fd pci_conf1_write_config_word+0x45:   popl   %esi
kdb> ss
0xc01100fd pci_conf1_write_config_word+0x45:   popl   %esi
SS trap at 0xc01100fe (pci_conf1_write_config_word+0x46)
0xc01100fe pci_conf1_write_config_word+0x46:   movl   %ebp,%esp
kdb> ss
0xc01100fe pci_conf1_write_config_word+0x46:   movl   %ebp,%esp
SS trap at 0xc0110100 (pci_conf1_write_config_word+0x48)
0xc0110100 pci_conf1_write_config_word+0x48:   popl   %ebp
kdb> ss
0xc0110100 pci_conf1_write_config_word+0x48:   popl   %ebp
SS trap at 0xc0110101 (pci_conf1_write_config_word+0x49)
0xc0110101 pci_conf1_write_config_word+0x49:   ret
kdb> ss
0xc0110101 pci_conf1_write_config_word+0x49:   ret
SS trap at 0xc020c7af (pci_write_config_word+0x2b)
0xc020c7af pci_write_config_word+0x2b:   pushl  %ebx
kdb> ss
0xc020c7af pci_write_config_word+0x2b:   pushl  %ebx
SS trap at 0xc020c7b0 (pci_write_config_word+0x2c)
0xc020c7b0 pci_write_config_word+0x2c:   popf
kdb> ss
0xc020c7b0 pci_write_config_word+0x2c:   popf

Here is where it hung this time.  Register dump below.

usb-uhci.c: $Revision: 1.242 $ time 20:13:32 Nov  8 2000
usb-uhci.c: High bandwidth mode enabled
Instruction(i) breakpoint #0 at 0xc03f5a8c (adjusted)
0xc03f5a8c start_uhci:   pushl  %ebp

Entering kdb (current=0xcfff4000, pid 1) due to Breakpoint @ 0xc03f5a8c
kdb> bp pci_write_config_word+0x2c
Instruction(i) BP #1 at 0xc020c7b0 (pci_write_config_word+0x2c)
is enabled globally adjust 1
kdb> g
Instruction(i) breakpoint #1 at 0xc020c7b0 (adjusted)
0xc020c7b0 pci_write_config_word+0x2c:   popf

Entering kdb (current=0xcfff4000, pid 1) due to Breakpoint @ 0xc020c7b0
kdb> rd
eax = 0x ebx = 0x0256 ecx = 0x00c0 edx = 0x0cfc
esi = 0x00c0 edi = 0xc144c800 esp = 0xcfff5f74 eip = 0xc020c7b0
ebp = 0xcfff5f90 xss = 0x0018 xcs = 0x0010 eflags = 0x0046
xds = 0xc1440018 xes = 0x0018 origeax = 0x ®s = 0xcfff5f40



0xc020c7aa pci_write_config_word+0x26:   movl   0x10(%edx),%eax
0xc020c7ad pci_write_config_word+0x29:   call   *%eax
0xc020c7af pci_write_config_word+0x2b:   pushl  %ebx
0xc020c7b0 pci_write_config_word+0x2c:   popf
0xc020c7b1 pci_write_config_word+0x2d:   jmp0xc020c7bc
pci_write_config_word+0x38
0xc020c7b3 pci_write_config_word+0x2f:   nop
0xc020c7b4 pci_write_config_word+0x30:   movl   $0x87,%eax
0xc020c7b9 pci_write_config_word+0x35:   leal   0x0(%esi),%esi
0xc020c7bc pci_write_config_word+0x38:   leal   0xfff4(%ebp),%esp

I'm going to have to drop this debug shortly and return to my regular work :(

-d


--
"The difference between 'involvement' and 'commitment' is like an
eggs-and-ham breakfast: the chicken was 'involved' - the pig was
'committed'."




begin:vcard 
n:Ford;David
x-mozilla-html:TRUE
adr:;;
version:2.1
email;internet:[EMAIL PROTECTED]
title:Blue Labs Developer
x-mozilla-cpt:;14688
fn:David Ford
end:vcard

Re: Stange NFS messages - 2.2.18pre19

[Sasi Peter]

On Wed, 8 Nov 2000, Scott McDermott wrote:

> Sasi Peter on Tue  7/11 23:28 +0100:
> > I'm getting this under moderate NFS load:
> > Nov  6 17:39:56 iq kernel: svc: server socket destroy delayed (sk_inuse: 1)
> > Nov  6 17:40:08 iq kernel: svc: unknown program 100227 (me 13)
> > Nov  6 19:06:11 iq kernel: svc: server socket destroy delayed (sk_inuse: 1)
> > Nov  6 19:38:48 iq kernel: svc: server socket destroy delayed (sk_inuse: 1)
> > What do these means? Is this a kernel bug?
> Your Suns are using TCP mounts, this got introduced into 2.2.18
> somewhere and is a bit broken, do a patch -R with
> ftp://oss.sgi.com/www.projects/nfs3/download/nfs_tcp-2.2.17.dif and
> these go away.  Suns try TCP mounts first.  Be careful to unmount them
> first or they will hang waiting for the TCP server to come back up.

Broken link:
[root@iq patches]# wget
ftp://oss.sgi.com/www.projects/nfs3/download/nfs_tcp-2.2.17.dif
--08:31:28--
ftp://oss.sgi.com:21/www.projects/nfs3/download/nfs_tcp-2.2.17.dif
   => `nfs_tcp-2.2.17.dif'
Connecting to oss.sgi.com:21... connected!
Logging in as anonymous ... Logged in!
==> TYPE I ... done.  ==> CWD www.projects/nfs3/download ...
No such directory `www.projects/nfs3/download'.

--  SaPE

Peter, Sasi <[EMAIL PROTECTED]>

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

kernel: eepro100: wait_for_cmd_done timeout!

[Ulrich Windl]

Hello,

I'm seeing the message periodically:

Nov  8 09:52:59 kgate last message repeated 5 times
Nov  8 11:26:54 kgate kernel: eepro100: wait_for_cmd_done timeout!
Nov  8 11:56:12 kgate kernel: eepro100: wait_for_cmd_done timeout!
Nov  8 14:38:45 kgate kernel: eepro100: wait_for_cmd_done timeout!
Nov  8 14:38:47 kgate last message repeated 3 times
Nov  8 14:56:11 kgate kernel: eepro100: wait_for_cmd_done timeout!
Nov  8 14:57:01 kgate last message repeated 10 times
Nov  8 21:32:15 kgate kernel: eepro100: wait_for_cmd_done timeout!
Nov  8 22:57:46 kgate kernel: eepro100: wait_for_cmd_done timeout!

The source contains:

/* How to wait for the command unit to accept a command.
   Typically this takes 0 ticks. */
static inline void wait_for_cmd_done(long cmd_ioaddr)
{
int wait = 1000;
do   ;
while(inb(cmd_ioaddr) && --wait >= 0);
#ifndef final_version
if (wait < 0)
printk(KERN_ALERT "eepro100: wait_for_cmd_done 
timeout!\n");
#endif
}

My machine is a HP Netserver LD Pro with a 200MHz Pentium Pro. I guess 
a fast machine will only allow a very short time for the above loop. 
Shouldn't it be fixed?

The hardware is this:
01:02.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] 
(rev 02)
Subsystem: Hewlett-Packard Company Ethernet Pro 10/100TX
Flags: bus master, medium devsel, latency 66, IRQ 9
Memory at fe8fe000 (32-bit, prefetchable)
I/O ports at ece0
Memory at fea0 (32-bit, non-prefetchable)


kgate kernel: eepro100.c:v1.09j-t 9/29/99 Donald Becker 
http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
kgate kernel: eepro100.c: $Revision: 1.20.2.10 $ 2000/05/31 Modified by 
Andrey V. Savochkin <[EMAIL PROTECTED]> and others
kgate kernel: eth0: OEM i82557/i82558 10/100 Ethernet, 00:60:B0:6D:F1:AE, 
IRQ 9.
kgate kernel:   Board assembly 673610-001, Physical connectors present: 
RJ45
kgate kernel:   Primary interface chip i82555 PHY #1.
kgate kernel:   General self-test: passed.
kgate kernel:   Serial sub-system self-test: passed.
kgate kernel:   Internal registers self-test: passed.
kgate kernel:   ROM checksum self-test: passed (0x49caa8d6).
kgate kernel:   Receiver lock-up workaround activated.

The software is Linux-2.2.16 (SuSE 7.0).

Regards,
Ulrich

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

Re: [bug] usb-uhci locks up on boot half the time

[David Ford]

More data:

kdb> bp pci_conf1_write_config_word+0x3a
Instruction(i) BP #1 at 0xc01100f2 (pci_conf1_write_config_word+0x3a)
is enabled globally adjust 1
kdb> go
Instruction(i) breakpoint #1 at 0xc01100f2 (adjusted)
0xc01100f2 pci_conf1_write_config_word+0x3a:   orl$0xcfc,%edx

Entering kdb (current=0xcfff4000, pid 1) due to Breakpoint @ 0xc01100f2
kdb> ss
0xc01100f2 pci_conf1_write_config_word+0x3a:   orl$0xcfc,%edx
SS trap at 0xc01100f8 (pci_conf1_write_config_word+0x40)
0xc01100f8 pci_conf1_write_config_word+0x40:   outw   %ax,(%dx)
kdb> rd
eax = 0x2000 ebx = 0x800022c0 ecx = 0x00c0 edx = 0x0cfc
esi = 0x2000 edi = 0xc144c800 esp = 0xcfff5f68 eip = 0xc01100f8
ebp = 0xcfff5f70 xss = 0x0018 xcs = 0x0010 eflags = 0x0006
xds = 0xcfff0018 xes = 0x0018 origeax = 0x ®s = 0xcfff5f34

-d

--
"The difference between 'involvement' and 'commitment' is like an
eggs-and-ham breakfast: the chicken was 'involved' - the pig was
'committed'."




begin:vcard 
n:Ford;David
x-mozilla-html:TRUE
adr:;;
version:2.1
email;internet:[EMAIL PROTECTED]
title:Blue Labs Developer
x-mozilla-cpt:;14688
fn:David Ford
end:vcard

Re: [bug] usb-uhci locks up on boot half the time

[David Ford]

Greg KH wrote:

> On Wed, Nov 08, 2000 at 08:19:13PM -0800, David Ford wrote:
> > I am going thru the steps atm.  The JE driver also hangs.
>
> Thanks for doing this.

np.


> > More information.  I have an external USB 4 port hub, in which I have one
> > logitech mouse at the moment.  I can cold boot and reboot to my heart's
> > delight fine.  But if I unplug/plug in the mouse and reboot, it will hang.
> > Note, I have to unplug and plug back in the mouse to get it recognized by
> > the system before I can use it.
>
> Is the external hub a externally powered hub, or self powered hub (does
> it get it's power from a plug in the wall, or from the USB bus)?  Self
> powered hubs are notoriously flaky and have been known to do evil things
> to the USB bus.

Either.  Currently bus (self) powered.  This hub has worked fine on my other
computers without any adverse affect.

I've stepped through w/ kdb and found some more info.  I'm not experience
enough with kdb to provide more details, my apologies.

usb_uhci():2952
  start_uhci():2896
pci_write_config_word():

[kdb output trimmed]
pci_write_config_word+0x29:   call   *%eax
pci_conf1_write_config_word:   pushl  %ebp
  +0x1:   movl   %esp,%ebp
  +0x3:   pushl  %esi
  +0x4:   pushl  %ebx
  +0x5:   movl   0x8(%ebp),%edx
  +0x8:   movl   0xc(%ebp),%ecx
  +0xb:   movl   0x10(%ebp),%esi
  +0xe:   movl   0x10(%edx),%eax
  +0x11:   movzbl 0x3c(%eax),%ebx
  +0x15:   movl   0x20(%edx),%eax
  +0x18:   shll   $0x10,%ebx
  +0x1b:   shll   $0x8,%eax
  +0x1e:   movl   $0xcf8,%edx
  +0x23:   orl$0x8000,%eax
  +0x28:   orl%eax,%ebx
  +0x2a:   movl   %ecx,%eax
  +0x2c:   andb   $0xfc,%al
  +0x2e:   orl%eax,%ebx
  +0x30:   movl   %ebx,%eax
  +0x32:   outl   %eax,(%dx)
  +0x32:   outl   %eax,(%dx)
  +0x33:   movl   %ecx,%edx
  +0x35:   movl   %esi,%eax
  +0x37:   andl   $0x2,%edx
  +0x3a:   orl$0xcfc,%edx
  +0x40:   outw   %ax,(%dx)

And here is where it hangs.



--
"The difference between 'involvement' and 'commitment' is like an
eggs-and-ham breakfast: the chicken was 'involved' - the pig was
'committed'."




begin:vcard 
n:Ford;David
x-mozilla-html:TRUE
adr:;;
version:2.1
email;internet:[EMAIL PROTECTED]
title:Blue Labs Developer
x-mozilla-cpt:;14688
fn:David Ford
end:vcard

Re: Stange NFS messages - 2.2.18pre19

[Ion Badulescu]

On Wed, 8 Nov 2000 21:15:38 -0500, Scott McDermott <[EMAIL PROTECTED]> wrote:
> Sasi Peter on Tue  7/11 23:28 +0100:
>> I'm getting this under moderate NFS load:
>> Nov  6 17:39:56 iq kernel: svc: server socket destroy delayed (sk_inuse: 1)
>> Nov  6 17:40:08 iq kernel: svc: unknown program 100227 (me 13)
>> Nov  6 19:06:11 iq kernel: svc: server socket destroy delayed (sk_inuse: 1)
>> Nov  6 19:38:48 iq kernel: svc: server socket destroy delayed (sk_inuse: 1)
>> 
>> What do these means? Is this a kernel bug?
> 
> Your Suns are using TCP mounts, this got introduced into 2.2.18
> somewhere and is a bit broken, do a patch -R with
> ftp://oss.sgi.com/www.projects/nfs3/download/nfs_tcp-2.2.17.dif and
> these go away.  Suns try TCP mounts first.  Be careful to unmount them
> first or they will hang waiting for the TCP server to come back up.

I really really think this should be backed out -- or at the very least
disabled. The code wasn't part of the dhiggen merge, it wasn't tested,
and it doesn't work well. Heck, it's still experimental and not recommended
in 2.4.0-test.

What's worse, it will burn everybody out there who is using am-utils or 
an automounter that tries TCP mounts first. NFS/UDP server support in 2.2.18
is so much better than in previous versions, it would a shame to ruin
it with this ill-fated patch.


Ion

-- 
  It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: Spew from test11-pre1

[Andrey Savochkin]

Hello,

On Wed, Nov 08, 2000 at 04:14:39PM -0800, Robert Lynch wrote:
> No oops, but right after I installed test11-pre1, then tried to
> access a Windows box as a VNC client, this message started
> getting continuously dumped by syslog:
> ===
> ...
> Nov  8 15:32:01 ives kernel: eth0: card reports no RX buffers.
> Nov  8 15:32:04 ives kernel: eth0: card reports no resources.
[snip]
> ===  
> Doing a Yahoo search it seems this was previously reported
> eepro100 bug, which appears to have resurfaced.

It have never been finally fixed.
I'm working on a "next-generation workaround" right now.

Best regards
Andrey V.
Savochkin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: [bug] usb-uhci locks up on boot half the time

[David Ford]

> The NMI oopser for UP only trips in when the cpu is spinning.  If the
> cpu is in a halt state then NMI does not run.  But in a halt state you
> should be able to activate kdb via the pause key.  The only time you
> cannot get kdb via pause is if interrupts are disabled (but then the
> cpu should be spinning and NMI should kick in) or if the cpu or
> motherboard is totally wedged.

just a quick followup while i'm working at it.  the hardware is totally
hung, nothing gets to it, keyboard, serial, or nmi.

being there are a lot of usb functions, does anyone have some suggested
breakpoints?

-d

--
"The difference between 'involvement' and 'commitment' is like an
eggs-and-ham breakfast: the chicken was 'involved' - the pig was
'committed'."




begin:vcard 
n:Ford;David
x-mozilla-html:TRUE
adr:;;
version:2.1
email;internet:[EMAIL PROTECTED]
title:Blue Labs Developer
x-mozilla-cpt:;14688
fn:David Ford
end:vcard

Re: [bug] usb-uhci locks up on boot half the time

[Greg KH]

On Wed, Nov 08, 2000 at 08:19:13PM -0800, David Ford wrote:
> I am going thru the steps atm.  The JE driver also hangs.

Thanks for doing this.

> More information.  I have an external USB 4 port hub, in which I have one
> logitech mouse at the moment.  I can cold boot and reboot to my heart's
> delight fine.  But if I unplug/plug in the mouse and reboot, it will hang.
> Note, I have to unplug and plug back in the mouse to get it recognized by
> the system before I can use it.

Is the external hub a externally powered hub, or self powered hub (does
it get it's power from a plug in the wall, or from the USB bus)?  Self
powered hubs are notoriously flaky and have been known to do evil things
to the USB bus.

thanks,

greg k-h

-- 
greg@(kroah|wirex).com
http://immunix.org/~greg
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: B/W G3 - big IDE problems with 2.4.0-test10

[Derrik Pates]

On Wed, 8 Nov 2000, Andre Hedrick wrote:

> What is your chipset, CMD646 rev 5 Ultra DMA 33 ???

Yep. I've tried building with the CMD64x driver, and that didn't help
matters, if you were wondering. Any thoughts?

Derrik Pates  | Sysadmin, Douglas School|_   #linuxOS on EFnet
[EMAIL PROTECTED] |  District (dsdk12.net)  |   | |   and now OPN too!
   Student @ South Dakota School of Mines   | __| |___ _ _ _   ___ _ _   
   & Technology (www.sdsmt.edu) |/ _  / -_) ' \ '\/ _ \ ' \ ()
UNIX: Because you want to USE your computer.|\___,\___|_||_||_\___/_||_|

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

Re: B/W G3 - big IDE problems with 2.4.0-test10

[Andre Hedrick]

My PPC with an ACARD addon PPC card.

AEC6260R: IDE controller on PCI bus 00 dev 68
AEC6260R: chipset revision 1
AEC6260R: not 100% native mode: will probe irqs later
AEC6260R: ROM enabled at 0x8081
ide0: BM-DMA at 0x0800-0x0807, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0x0808-0x080f, BIOS settings: hdc:pio, hdd:pio

What is your chipset, CMD646 rev 5 Ultra DMA 33 ???


Andre Hedrick
CTO Timpanogas Research Group
EVP Linux Development, TRG
Linux ATA Development


Cannot find map file.
No module symbols loaded.
klogd 1.3-3, log source = ksyslog started.
<4>Total memory = 112MB; using 512kB for hash table (at c030)
<4>Linux version 2.4.0-test9 (root@ppc) (gcc version 2.95.2 19991024 (release)) #1 Thu 
Oct 5 02:02:51 PDT 2000
<6>PCI bus 0 controlled by bandit at f200
<6>Cache coherency enabled for bandit/PSX at fdef1000
<6>PCI bus 1 controlled by chaos at f000
<4>On node 0 totalpages: 28672
<4>zone(0): 28672 pages.
<4>zone(1): 0 pages.
<4>zone(2): 0 pages.
<4>Kernel command line: root=/dev/hda7 devfs=nomount
<4>System has 32 possible interrupts
<4>GMT Delta read from XPRAM: -420 minutes, DST: on
<6>via_calibrate_decr: ticks per jiffy = 111227 (667364 ticks)
<4>Console: colour dummy device 80x25
<4>Calibrating delay loop... 532.48 BogoMIPS
<4>Memory: 109080k available (1876k kernel code, 904k data, 268k init, 0k highmem)
<4>Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes)
<4>Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes)
<4>Page-cache hash table entries: 32768 (order: 5, 131072 bytes)
<4>Inode-cache hash table entries: 8192 (order: 4, 65536 bytes)
<5>VFS: Diskquotas version dquot_6.4.0 initialized
<4>POSIX conformance testing by UNIFIX
<4>PCI: Probing PCI hardware
<4>Macintosh CUDA driver v0.5 for Unified ADB.
<6>Linux NET4.0 for Linux 2.4
<6>Based upon Swansea University Computer Society NET3.039
<6>NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
<6>NET4: Linux TCP/IP 1.0 for NET4.0
<6>IP Protocols: ICMP, UDP, TCP, IGMP
<4>IP: routing cache hash table of 512 buckets, 4Kbytes
<4>TCP: Hash tables configured (established 8192 bind 8192)
<6>NET4: AppleTalk 0.18 for Linux NET4.0
<4>Initializing RT netlink socket
<4>Starting kswapd v1.8
<6>controlfb: Memory bank 1 present, bank 2 present, total VRAM 4MB
<6>Monitor sense value = 0x623, using video mode 18 and color mode 0.
<4>Console: switching to colour frame buffer device 144x54
<6>fb0: control display adapter
<6>MacOS display is /chaos/control
<4>PowerMac Z8530 serial driver version 2.0
<4>tty00 at 0xc8805020 (irq = 15) is a Z8530 ESCC, port = modem
<4>tty01 at 0xc880c000 (irq = 16) is a Z8530 ESCC, port = printer
<4>pty: 256 Unix98 ptys configured
<4>RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
<6>loop: enabling 8 loop devices
<6>Uniform Multi-Platform E-IDE driver Revision: 6.31
<4>ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
<4>AEC6260R: IDE controller on PCI bus 00 dev 68
<4>AEC6260R: chipset revision 1
<4>AEC6260R: not 100% native mode: will probe irqs later
<4>AEC6260R: ROM enabled at 0x8081
<4>ide0: BM-DMA at 0x0800-0x0807, BIOS settings: hda:pio, hdb:pio
<4>ide1: BM-DMA at 0x0808-0x080f, BIOS settings: hdc:pio, hdd:pio
<4>hda: QUANTUM FIREBALL CX10.2A, ATA DISK drive
<4>ide0 at 0x840-0x847,0x000 on irq 23
<4>ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
<6>hda: 20044080 sectors (10263 MB) w/418KiB Cache, CHS=19885/16/63, UDMA(66)
<6>Partition check:
<6> /dev/ide/host0/bus0/target0/lun0: [mac] p1 p2 p3 p4 p5 p6 p7 p8 p9 p10
<6>fd0: SWIM3 floppy controller 
<5>udf: registering filesystem
<6>Macintosh ADB mouse driver installed.
<7>IN from bad port 71 at c02600a0
<6>Real Time Clock Driver v1.10c
<6>Linux Tulip driver version 0.9.10 (September 6, 2000)
<4>PCI: Enabling device 00:0f.0 (0004 -> 0007)
<6>eth0: Lite-On 82c168 PNIC rev 32 at 0x400, 00:00:B5:94:AB:39, IRQ 25.
<6>eth0:  MII transceiver #1 config 3100 status 7829 advertising 01e1.
<6>eth1: MACE at 00:05:02:58:9d:48, chip revision 25.64
<4>scsi0 : MESH
<4>mesh: rejecting message from target 1: 1 1 3
<4>mesh: bs0=2f in msg_out
<4>mesh: rejecting message from target 1: 1 1 32
<4>mesh: bs0=2f in msg_out
<4>mesh: rejecting message from target 1: f
<4>  Vendor: SEAGATE   Model: ST32550N  Rev: 0011
<4>  Type:   Direct-Access  ANSI SCSI revision: 02
<6>mesh: target 3 synchronous at 5.0 MB/s
<4>  Vendor: MATSHITA  Model: CD-ROM CR-8008Rev: 8.0h
<4>  Type:   CD-ROM ANSI SCSI revision: 02
<4>scsi1 : 53C94
<4>  Vendor: MAXTORModel: LXT-213S SUN0207  Rev: 4.15
<4>  Type:   Direct-Access  ANSI SCSI revision: 01 CCS
<4>Detected scsi disk sda at scsi0, channel 0, id 1, lun 0
<4>Detected scsi disk sdb at scsi1, channel 0, id 6, lun 0
<4>SCSI device sda: 4194303 512-byte hdwr sectors (21

Re: Persistent module storage - modutils design

[Keith Owens]

On 8 Nov 2000 21:09:49 -0800, 
"H. Peter Anvin" <[EMAIL PROTECTED]> wrote:
>Remember that we cannot rely on ANY form of persistent storage to be
>available in the beginning; / may very well be readonly (on a ROM,
>say.)  Since that means that we can't rely on writable storage being
>available until at least one other filesystem has been mounted, it
>might as well be the standard for variable data, i.e. /var.

Agreed.  Default is /var/lib/modules-persist.  People who have a
separate /var partition that is mounted after modules are loaded can
use / and specify

persist /lib/modules/persist

in /etc/modules.conf.  If you have a separate /var and you do not want
to write to /, change your initialization scripts to load modules after
mounting /var.

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

Re: Persistent module storage - modutils design

[Keith Owens]

On Thu, 09 Nov 2000 15:52:47 +1100, 
Rusty Russell <[EMAIL PROTECTED]> wrote:
>In message <[EMAIL PROTECTED]> you write:
>> Looks like persistent data has to be stored in /lib/modules/persist (no
>> , see earlier mail).
>
>You need versions: binary data is too prone to change (proven kernel
>history).  It's the kernel installer's duty to know which ones can be
>safely linked/copied to the new version.

Not saving persistent data in binary format, so no problem.

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

Re: Persistent module storage - modutils design

[H. Peter Anvin]

Followup to:  <[EMAIL PROTECTED]>
By author:Rusty Russell <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
> 
> > Modules are loaded before non-root file systems are mounted, damn!
> 
> modules.conf already breaks FHS lib/ badly enough.  Modules loaded
> before /var is mounted won't get persistant data.  Too bad; they
> have to do something sane when it doesn't exist anyway.
> 

Last I checked modules.conf was in /etc, not in /lib.

> 
> > Looks like persistent data has to be stored in /lib/modules/persist (no
> > , see earlier mail).
> 
> You need versions: binary data is too prone to change (proven kernel
> history).  It's the kernel installer's duty to know which ones can be
> safely linked/copied to the new version.
> 
> Otherwise every data change requires a new symbol name: and this will
> happen all the time.
> 

Remember that we cannot rely on ANY form of persistent storage to be
available in the beginning; / may very well be readonly (on a ROM,
say.)  Since that means that we can't rely on writable storage being
available until at least one other filesystem has been mounted, it
might as well be the standard for variable data, i.e. /var.

-hpa
-- 
<[EMAIL PROTECTED]> at work, <[EMAIL PROTECTED]> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: need urgent help with 2.2.17 + ipchains

[Rusty Russell]

In message <[EMAIL PROTECTED]> you
 write:
> hi!
> 
> i have the following very nasty problem.
> everytime i execute ipchains -F [rule] my box freezes for 25 minutes!
> i run slackware on 2.2.17.

You mean `ipchains -F [chain]'?  It's possible that your rules could
be ordered so that this command breaks when executed remotely.  Are
you running this locally?

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

Re: Persistent module storage - modutils design

[Rusty Russell]

In message <[EMAIL PROTECTED]> you write:
> On Tue, 07 Nov 2000 10:30:39 -0300, 
> Horst von Brand <[EMAIL PROTECTED]> wrote:
> >Note! This _has_ to be in the / filesystem so it works before mounting the
> >rest of the stuff (if ever). This would rule out /var, and leave just
> >/lib/modules/. Makes me quite unhappy...
> 
> Modules are loaded before non-root file systems are mounted, damn!

modules.conf already breaks FHS lib/ badly enough.  Modules loaded
before /var is mounted won't get persistant data.  Too bad; they
have to do something sane when it doesn't exist anyway.

> Looks like persistent data has to be stored in /lib/modules/persist (no
> , see earlier mail).

You need versions: binary data is too prone to change (proven kernel
history).  It's the kernel installer's duty to know which ones can be
safely linked/copied to the new version.

Otherwise every data change requires a new symbol name: and this will
happen all the time.

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

2.4 test10 bug

[Eric Reischer]

When cross compiling a PowerPC kernel on an i386 machine, got the following 
error:

binfmt_elf.c: In function 'create_elf_tables':
binfmt_elf.c:166: 'CLOCKS_PER_SEC' undeclared (first use in this function)
binfmt_elf.c:166: (Each undeclared identifier is reported only once
binfmt_elf.c:166: for each function it appears in.)
make[2]: *** [binfmt_elf.o] Error 1

for folder /usr/src/cross/powerpc-unknown-linux-gnu/src/linux/fs

Copied the binfmt_elf.c code from the test9 tree and recompiled.  Compile 
then proceeded without errors.  If whoever is in charge of this section 
would like a copy of the .config file, I would be more than willing to 
attach it.  On a side note the kernel was being compiled for a POWER3 
processor, but it doesn't appear as though that would be a factor here.



--
Eric Reischer   "You can't depend on your eyes
[EMAIL PROTECTED]  if your imagination is out of focus."
[EMAIL PROTECTED]-- Mark Twain
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

B/W G3 - big IDE problems with 2.4.0-test10

[Derrik Pates]

I've been trying Debian woody for PowerPC on a blue-and-white G3 tower
machine (PPC750/350 MHz, 192 MB RAM). Finally got yaboot working, so now
I'm playing with getting 2.4.x going (in part to get the built-in support
for Mac-on-Linux). However, when I try to boot the kernel, I get errors
about conflicts in I/O address space, and the secondary IDE interface
(what 2.2.17 sees as hde/hdf) shows up as the primary, but both hard
drives (Linux installed on hdb, MacOS on hda) do not show at all. I can't
use serial-console, and I don't have an NFS server (I may have to setup a
basic NFS-root image on another machine to boot it from). Also, it has no
floppy drives. I can't scroll back, so I can't read all the messages.

I saw a previous post about a similar situation with test5 a ways back in
Geocrawler's linux-kernel archive, but I don't see any answer to the
earlier query.

Derrik Pates  | Sysadmin, Douglas School|_   #linuxOS on EFnet
[EMAIL PROTECTED] |  District (dsdk12.net)  |   | |   and now OPN too!
   Student @ South Dakota School of Mines   | __| |___ _ _ _   ___ _ _   
   & Technology (www.sdsmt.edu) |/ _  / -_) ' \ '\/ _ \ ' \ ()
UNIX: Because you want to USE your computer.|\___,\___|_||_||_\___/_||_|

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

Re: [bug] usb-uhci locks up on boot half the time

[David Ford]

I am going thru the steps atm.  The JE driver also hangs.

More information.  I have an external USB 4 port hub, in which I have one
logitech mouse at the moment.  I can cold boot and reboot to my heart's
delight fine.  But if I unplug/plug in the mouse and reboot, it will hang.
Note, I have to unplug and plug back in the mouse to get it recognized by
the system before I can use it.

So we're probably looking at something other than the uhci/je driver.

-d

Greg KH wrote:

> If you have the time, could you please do the debugging steps that Keith
> Owens just listed.  It might enable us to determine what is wrong with
> the usb-uhci.o driver (the JE driver doesn't work with all devices right
> now, so we are still dependent on usb-uhci.o).

--
"The difference between 'involvement' and 'commitment' is like an
eggs-and-ham breakfast: the chicken was 'involved' - the pig was
'committed'."




begin:vcard 
n:Ford;David
x-mozilla-html:TRUE
adr:;;
version:2.1
email;internet:[EMAIL PROTECTED]
title:Blue Labs Developer
x-mozilla-cpt:;14688
fn:David Ford
end:vcard

Re: [bug] usb-uhci locks up on boot half the time

[Greg KH]

On Wed, Nov 08, 2000 at 05:27:29PM -0800, David Ford wrote:
> I just recompiled using the JE driver and it doesn't lock up on boot.

If you have the time, could you please do the debugging steps that Keith
Owens just listed.  It might enable us to determine what is wrong with
the usb-uhci.o driver (the JE driver doesn't work with all devices right
now, so we are still dependent on usb-uhci.o).

thanks,

greg k-h

-- 
greg@(kroah|wirex).com
http://immunix.org/~greg
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: [PATCH] media/radio [check_region() removal... ]

[Jeff Garzik]

Bartlomiej Zolnierkiewicz wrote:
> 
> On Wed, 8 Nov 2000, Jeff Garzik wrote:
> 
> > Patch looks generally ok.  Some of the whitespace/formatting changes are
> > questionable, I usually leave that up to the maintainer unless it is
> > very gratuitously opposite to CodingStyle.
> >
> 
> These drivers seem to be unmantained :)
> Anyway if this is a problem I can undo these changes ...

I don't have any problem with them.  Make sure you CC the individual
maintainers of the drivers...  some of the pop up every now and then :)


> > Some of the driver messages ("foo version 1.0") are purposefully printed
> > -after-, not before, the device is probed and registered.  Your patch
> > gets this wrong in at least one place.
> >
> 
> Yes... I wasn't sure about this... can undo...

When in doubt, follow the behavior of the existing driver.  :) 
Especially since we're in a freeze, and stuff...

-- 
Jeff Garzik |
Building 1024   | Would you like a Twinkie?
MandrakeSoft|
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: pcmcia

[Horst von Brand]

David Feuer <[EMAIL PROTECTED]> said:
> What is the current status of PC-card support?  I've seen ominous signs on 
> this list about the state of support  I have a laptop with a PCMCIA 
> network card (a 3com thing). Will it work?

I've got a Toshiba Satellite Pro 4280xdvd + 3com cardbus 10/100 card. Works
fine with Red Hat 7, and also with 2.2.18pre20 + latest pcmcia-cs tools (X
doesn't work out of the box, I had to grab an X server from somewhere for
the S3 Savage IX the machine has. The builtin Lucent winmodem is hopeless,
BTW: The Lucent drivers just crash the kernel once the call is answered.)
--
Horst von Brand [EMAIL PROTECTED]
Casilla 9G, Vin~a del Mar, Chile   +56 32 672616
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

VPN Masquerade patch going into 2.2.18final?

[Dan Browning]

Would you care to comment on the VPN Masquerade patch that has been
floating around?  Will it make it into an official 2.2.x kernel soon?  The
VPN-Masq HOWTO seems to think it is going into 2.2.18 proper.

ftp://ftp.rubyriver.com/pub/jhardin/masquerade/ip_masq_vpn-2.2.17.patch.gz

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

[2.2pre] crash after unloading agpgart and loading mga DRM module

[Yann Dirson]

I could reproduce this with 2.2.18pre17 + Andrea's VM-global patch (-7),
pre20 with and without the VM patch.

Mainboard is a FIC VA503+, video is a G200.

Better run this with everything mounted RO:

$ insmod agpgart
$ rmmod agpgart
$ insmod agpgart
$ insmod mga

And here we go...

I tested a combinations, and what appears trigger the bug is the unloading
of agpgart and the subsequent loading of mga.


[Data gathered with vanilla pre20 - config file attached]

While in single-user mode, all FS mounted RO.

2 OOPSes at same EIP (locks_remove_flock+0x0E) for init are on screen,
similar ones for bash occured just before, although the 1st one for bash is
partly offscreen and I can't scrollback.

OOPSes per process are:

* paging request at e850097c (EFLAGS=00010286)
* NULL pointer dereference at 00...0008 (EFLAGS=00010292 in this case)

Not sure I remember the correct order, though.

A couple of "hda lost interrupt" also appear from time to time.  All of this
(OOPS+lost intr) do not appear at once, but usually all of them come after
waiting some time.  At the very least I only had bash not giving me a prompt
any more after hitting RETURN.

Anyone seing this ?
-- 
Yann Dirson<[EMAIL PROTECTED]> |Why make M$-Bill richer & richer ?
debian-email:   <[EMAIL PROTECTED]> |   Support Debian GNU/Linux:
| Cheaper, more Powerful, more Stable !
http://ydirson.free.fr/ | Check 


#
# Automatically generated make config: don't edit
#

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
CONFIG_M586TSC=y
# CONFIG_M686 is not set
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_TSC=y
# CONFIG_MICROCODE is not set
CONFIG_X86_MSR=m
CONFIG_X86_CPUID=m
CONFIG_1GB=y
# CONFIG_2GB is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_SMP is not set

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

#
# General setup
#
CONFIG_NET=y
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
# CONFIG_PCI_QUIRKS is not set
CONFIG_PCI_OLD_PROC=y
# CONFIG_MCA is not set
# CONFIG_VISWS is not set
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
# CONFIG_BINFMT_AOUT is not set
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=m
# CONFIG_BINFMT_JAVA is not set
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
# CONFIG_PARPORT_OTHER is not set
# CONFIG_APM is not set
# CONFIG_TOSHIBA is not set

#
# Plug and Play support
#
# CONFIG_PNP is not set

#
# Block devices
#
CONFIG_BLK_DEV_FD=m
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_BLK_DEV_IDECD=m
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_NS87415 is not set
CONFIG_BLK_DEV_VIA82C586=y
# CONFIG_BLK_DEV_CMD646 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_IDE_CHIPSETS is not set

#
# Additional Block Devices
#
CONFIG_BLK_DEV_LOOP=m
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_MD is not set
CONFIG_BLK_DEV_RAM=m
CONFIG_BLK_DEV_RAM_SIZE=4096
# CONFIG_BLK_DEV_XD is not set
# CONFIG_BLK_DEV_DAC960 is not set
CONFIG_PARIDE_PARPORT=m
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_HD is not set

#
# Networking options
#
CONFIG_PACKET=m
CONFIG_NETLINK=y
CONFIG_RTNETLINK=y
# CONFIG_NETLINK_DEV is not set
# CONFIG_FIREWALL is not set
# CONFIG_FILTER is not set
CONFIG_UNIX=y
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_IP_ROUTER is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_ALIAS is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set

#
# (it is safe to leave these untouched)
#
# CONFIG_INET_RARP is not set
# CONFIG_SKB_LARGE is not set
# CONFIG_IPV6 is not set

#
#  
#
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_BRIDGE is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_LLC is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set
# CONFIG_CPU_IS_SLOW is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set
# CONFIG_PHONE_IXJ is not set

#
# SCSI support
#
CONFIG_SCSI=m

Re: Stange NFS messages - 2.2.18pre19

[Scott McDermott]

Sasi Peter on Tue  7/11 23:28 +0100:
> I'm getting this under moderate NFS load:
> Nov  6 17:39:56 iq kernel: svc: server socket destroy delayed (sk_inuse: 1)
> Nov  6 17:40:08 iq kernel: svc: unknown program 100227 (me 13)
> Nov  6 19:06:11 iq kernel: svc: server socket destroy delayed (sk_inuse: 1)
> Nov  6 19:38:48 iq kernel: svc: server socket destroy delayed (sk_inuse: 1)
> 
> What do these means? Is this a kernel bug?

Your Suns are using TCP mounts, this got introduced into 2.2.18
somewhere and is a bit broken, do a patch -R with
ftp://oss.sgi.com/www.projects/nfs3/download/nfs_tcp-2.2.17.dif and
these go away.  Suns try TCP mounts first.  Be careful to unmount them
first or they will hang waiting for the TCP server to come back up.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: pcmcia

[FORT David]

David Ford wrote:

> You may be in the same boat I'm in then.  i82365 is what I used and it worked.
> yenta doesn't.  Right now I'm stuck with using my USB nic because neither the
> kernel's pcmcia or dh pcmcia work for me.
>
> -d
>
> Brett wrote:
>
> > Hey,
>

[]

>
> > > "The difference between 'involvement' and 'commitment' is like an
> > > eggs-and-ham breakfast: the chicken was 'involved' - the pig was
> > > 'committed'."
> > >
> > >
> > >
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to [EMAIL PROTECTED]
> > Please read the FAQ at http://www.tux.org/lkml/
>
> --
> "The difference between 'involvement' and 'commitment' is like an
> eggs-and-ham breakfast: the chicken was 'involved' - the pig was
> 'committed'."

I got the same problem for an old 486 with no PCI, as yenta_socket doesn't work, i
have to add CONFIG_I82365
in order to have things work. 'till this is set and recompiled, everything works
perfectly. The controller is a
VLSI 82C146.
I'm problably missing something, but these's two things i don't understand:
-why PCMCIA depends on PCI at compilation time
-why yenta is activated for i82365, as it doesn't do the job i82365 did.


--
%-%
% FORT David, %
% 7 avenue de la morvandière   0240726275 %
% 44470 Thouare, France[EMAIL PROTECTED] %
% ICU:78064991   AIM: enlighted popo [EMAIL PROTECTED] %
%--LINUX-HTTPD-PIOGENE%
%  -datamining <-/|   .~. %
%  -networking/flashed PHP3 coming soon   |   /V\L  I  N  U  X%
%  -opensource|  // \\ >Fear the Penguin< %
%  -GNOME/enlightenment/GIMP  | /(   )\   %
%   feel enlighted|  ^^-^^%
%   http://ibonneace.dnsalias.org/ when connected %
%-%



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

Errors in 2.4-test11 build

[J . A . Magallon]

Trying to build 2.4.0-test11-pre1 I get the following:

make[1]: Entering directory `/usr/src/linux-2.4.0-test11/arch/i386/kernel'
kgcc -D__ASSEMBLY__ -D__KERNEL__ -I/usr/src/linux/include -traditional -c
trampoline.S -o trampoline.o
gcc: installation problem, cannot exec `tradcpp0': No such file or directory
make[1]: *** [trampoline.o] Error 1

My egcs does not have a -traditional cpp (Mandrake 7.2, packages egcs and
egcs-cpp).

Is mandatory the -traditional flag in linux/arch/i386/kernel/Makefile ?

If I symlink /usr/lib/gcc-lib/i586-mandrake-linux/egcs-2.91.66/tradcpp0 -> cpp0,
or
remove -traditional:

kgcc -D__ASSEMBLY__ -D__KERNEL__ -I/usr/src/linux/include -c trampoline.S -o
trampoline.o
trampoline.S:47: unterminated character constant

Code is:
movl$0xA5A5A5A5, trampoline_data - r_base
 >  # write marker for master knows we're running

well, remove the comment. Then:

kgcc -D__ASSEMBLY__ -D__KERNEL__ -I/usr/src/linux/include -c trampoline.S -o
trampoline.o
/tmp/ccg9ZEBO.s: Assembler messages:
/tmp/ccg9ZEBO.s:806: Error: can't handle non absolute segment in `ljmp'

What's going on ??? Build works ok with 2.95.2.
Any idea ?

Thanks for reading...

-- 
Juan Antonio Magallon Lacarta #> cd /pub
mailto:[EMAIL PROTECTED] #> more beer

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

OOPS loading cs46xx module, test11-pre1

[David Ford]

Crystal 4280/461x + AC97 Audio, version 0.09, 16:07:04 Nov  8 2000
cs461x: Card found at 0xc780 and 0xc700, IRQ 11
cs461x: Voyetra at 0xc780/0xc700, IRQ 11
Unable to handle kernel paging request at virtual address a1d60878
 printing eip:
a1d60878
*pde = 
Oops: 
CPU:0
EIP:0010:[]
EFLAGS: 00010287
eax: 9192d469   ebx:    ecx: 0246   edx: 
esi: cf92e280   edi: cc18a000   ebp: cf92e280   esp: cc18bec8
ds: 0018   es: 0018   ss: 0018
Process modprobe (pid: 294, stackpage=cc18b000)
Stack: d091a06a d091c389 cf92e280 0003 0040 0001136a cf92e280
d091c8a3
   cf92e280 cf92e280 0468 0003 d092b0e8 c144a000 c700
d091cc36
   cf92e280 c144a000  0001 00011254 50533357 d091ce8e
c144a000
Call Trace: [] [] [] []
[] [] []
   [] [] [] [] []
Code:  Bad EIP value.


>From ksymoops 2.3.5:
>>EIP; a1d60878 Before first symbol   <=
Trace; d091a06a <[cs46xx]cs461x_poke+16/2c>
Trace; d091c389 <[cs46xx]cs461x_reset+15/78>
Trace; d091c8a3 <[cs46xx]cs_hardware_init+23b/30c>
Trace; d092b0e8 <[cs46xx]cards+10/6f>
Trace; d091cc36 <[cs46xx]cs_install+2c2/368>
Trace; d091ce8e <[cs46xx]cs_probe+62/cc>
Trace; d091a000 <[cs46xx]__module_kernel_version+0/1c>
Trace; d091cefd <[cs46xx]init_module+5/1c>
Trace; c0117bf9 
Trace; d0917000 <[ac97_codec]__kstrtab_ac97_read_proc+0/0>
Trace; d091a060 <[cs46xx]cs461x_poke+c/2c>
Trace; c010aaff 

This is also the card that doesn't init if it's compiled in and only
works as a module.

-d

--
"The difference between 'involvement' and 'commitment' is like an
eggs-and-ham breakfast: the chicken was 'involved' - the pig was
'committed'."




begin:vcard 
n:Ford;David
x-mozilla-html:TRUE
adr:;;
version:2.1
email;internet:[EMAIL PROTECTED]
title:Blue Labs Developer
x-mozilla-cpt:;14688
fn:David Ford
end:vcard

Re: [bug] usb-uhci locks up on boot half the time

[David Ford]

I just recompiled using the JE driver and it doesn't lock up on boot.

-d

Georg Nikodym wrote:

> > "DF" == David Ford <[EMAIL PROTECTED]> writes:
>
>  DF> Ok, in test10, for every 2 out of 5 boots, this particular
>  DF> workstation locks up hard as it reaches the following:
>
> I have a similar problem.  My work around is to, by hand, modprobe
> usbmouse, wait, modprobe usb-uhci...

--
"The difference between 'involvement' and 'commitment' is like an
eggs-and-ham breakfast: the chicken was 'involved' - the pig was
'committed'."




begin:vcard 
n:Ford;David
x-mozilla-html:TRUE
adr:;;
version:2.1
email;internet:[EMAIL PROTECTED]
title:Blue Labs Developer
x-mozilla-cpt:;14688
fn:David Ford
end:vcard

Re: pcmcia

[David Ford]

You may be in the same boat I'm in then.  i82365 is what I used and it worked.
yenta doesn't.  Right now I'm stuck with using my USB nic because neither the
kernel's pcmcia or dh pcmcia work for me.

-d

Brett wrote:

> Hey,
>
> I don't know if this counts as a _problem_,
> but I need to enable pci support to get pcmcia/cardbus activated.
> Is this really necessary ?? My current kernels work fine without pci
> support, and sure, enabling it won't hurt, just make the kernel bigger,
> but why is the restriction there ?
>
> Also, what has happened to the i82365 support that I need ?
> Its nicely commented out in drivers/net/pcmcia/Config.in
>
> I remember everything working fine up until about test3/4, since then I've
> had to revert to the pcmcia-cs package.
>
> Just wondering whats going on ?
>
> / Brett
>
> On Wed, 8 Nov 2000, David Ford wrote:
> >
> > With a few exceptions, it should work.  The problematic systems are few.
> >
> > -d
> >
> > David Feuer wrote:
> >
> > > What is the current status of PC-card support?  I've seen ominous signs on
> > > this list about the state of support  I have a laptop with a PCMCIA
> > > network card (a 3com thing). Will it work?
> >
> > --
> > "The difference between 'involvement' and 'commitment' is like an
> > eggs-and-ham breakfast: the chicken was 'involved' - the pig was
> > 'committed'."
> >
> >
> >
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> Please read the FAQ at http://www.tux.org/lkml/

--
"The difference between 'involvement' and 'commitment' is like an
eggs-and-ham breakfast: the chicken was 'involved' - the pig was
'committed'."




begin:vcard 
n:Ford;David
x-mozilla-html:TRUE
adr:;;
version:2.1
email;internet:[EMAIL PROTECTED]
title:Blue Labs Developer
x-mozilla-cpt:;14688
fn:David Ford
end:vcard

Re: [bug] usb-uhci locks up on boot half the time

[Keith Owens]

On Wed, 08 Nov 2000 16:35:36 -0800, 
David Ford <[EMAIL PROTECTED]> wrote:
>Ok, in test10, for every 2 out of 5 boots, this particular workstation
>locks up hard as it reaches the following:
>
>usb.c: registered new driver usbdevfs
>usb.c: registered new driver hub
>usb-uhci.c: $Revision: 1.242 $ time 15:53:47 Nov 8 2000
>usb-uhci.c: High bandwidth mode enabled
>usb-uhci.c: USB UHCI at I/O 0xb400, IRQ 9
>usb-uhci.c: Detected 2 ports
>

Apply the kernel debugger patch[*], select "APIC and IO-APIC support on
uniprocessors" then "NMI watchdog active for uniprocessors".  Compile,
install, reboot.  When the machine hangs, NMI should drop into kdb
after 5 seconds, 'bt' gives a backtrace.

ftp://oss.sgi.com/projects/kdb/download/ix86/kdb-v1.5-2.4.0-test10.gz

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

Linux 2.4 on Cobalt MiPS servers

[Jason Fayre]

Hello,
Does the 2.4 series compile on Cobalt Networks MIPS-based servers?  There
is a cobalt directory under the arch/mips directory.



-
Jason Fayre
Escalation Engineer
Cobalt Networks, Inc.
http://www.cobalt.com/support



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

Re: [bug] usb-uhci locks up on boot half the time

[Georg Nikodym]

> "DF" == David Ford <[EMAIL PROTECTED]> writes:

 DF> Ok, in test10, for every 2 out of 5 boots, this particular
 DF> workstation locks up hard as it reaches the following:

I have a similar problem.  My work around is to, by hand, modprobe
usbmouse, wait, modprobe usb-uhci...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: Pentium IV-summary

[Prasanna P Subash]

On Wed, Nov 08, 2000 at 03:14:22PM -0500, Frank Davis wrote:
> 3. 2.4.x may support processor speeds up to 100GHz, as well as Pentium IV. Linus 
>will have a Pentium IV available soon, but can someone test the kernel with a Pentium 
>IV sooner?

I've gotta Pentium IV 800MHz working on 2.4.0-test10. Just started testing it. It 
actually seems pretty stable.

-- 

Prasanna P Subash
[EMAIL PROTECTED]

 PGP signature

ISSUE: Locks up on boot with HPT370

[Christopher Thompson]

Resubmitting this bug as it happens both on -test10 and, I just 
verified, -test11-pre1.

(using the bug report form. if you wish to contact me, please 
do so off-list as I am not subscribed.) 

1. Locks up on boot with HPT370 
2. Using kernel 2.4.0-test10, my machine gets to the part of 
the bootup where it has detected drives and CD-ROM's on hda, 
hdc, hdd. It then locks up, the floppy light is on and the 
keyboard is non-responsive. Alt-SysRq-foo does nothing. Have 
to hard-reset. On 2.2.17 with the IDE backport, the kernel 
boots up fine, showing that it has found /dev/hde and continuing 
as usual. Have not tested with anything before test9-pre-foo, 
just got this motherboard. 
3. HPT370, Highpoint, HPT366, IDE, boot 
4. 2.4.0-test10 
5. No oops shown. Machine just locks up hard. 
6. Reproducable 100% of the time when booting my machine with 
2.4.0-test10. Please note that the HPT366 is, of course, 
compiled in and is not a module. 
7.1 Debian Potato install with the 2.4.0-test10 kernel from 
ftp.kernel.org 
7.2 $ cat /proc/cpuinfo 
processor : 0 
vendor_id : AuthenticAMD 
cpu family : 6 
model : 4 
model name : AMD Athlon(tm) Processor 
stepping : 2 
cpu MHz : 900.059 
cache size : 256 KB 
fdiv_bug : no 
hlt_bug : no 
sep_bug : no 
f00f_bug : no 
coma_bug : no 
fpu : yes 
fpu_exception : yes 
cpuid level : 1 
wp : yes 
flags : fpu vme de pse tsc msr 6 mce cx8 sep mtrr pge 
14 cmov pat 17 psn mmxext mmx fxsr 3dnowext 3dnow 
bogomips : 1795.69 

Note that this is with an Abit KT7-RAID motherboard. The hard 
drives are NOT in raid mode. 
7.3 No module information to show as the kernel does not boot. 
7.4 No SCSI drives installed, nothing compiled in. 
7.5 Works perfectly fine with kernel 2.2.17, Win98SE, Win2k. 
X. Have found no workaround. Cannot tell if the problem is in 
the HPT366/370 support or is caused elsewhere. Please contact 
me if you have any suggestions or have a patch you wish me to 
try out. Please note that on Thursday and Friday, I will be 
away from the Internet. 
I realise that the highpoint controllers are somewhat 
problematic but note that this system works fine in 2.2.17. 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

[bug] usb-uhci locks up on boot half the time

[David Ford]

Ok, in test10, for every 2 out of 5 boots, this particular workstation
locks up hard as it reaches the following:

usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.242 $ time 15:53:47 Nov 8 2000
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: USB UHCI at I/O 0xb400, IRQ 9
usb-uhci.c: Detected 2 ports


In test11, it locks up two lines earlier, right after 'enabled'

The normal sequence is:

usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.242 $ time 15:53:47 Nov  8 2000
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: USB UHCI at I/O 0xb400, IRQ 9
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
usb.c: registered new driver hid
usb.c: registered new driver dc2xx
usb.c: registered new driver dsbr100
usb.c: registered new driver usb-storage


It's a pII 300, not overclocked, ASUS P3BF motherboard.

00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge
(rev 03)
Subsystem: Asustek Computer, Inc.: Unknown device 7190
Flags: bus master, medium devsel, latency 64
Memory at d000 (32-bit, prefetchable) [size=256M]
Capabilities: [a0] AGP version 1.0

00:01.0 PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge
(rev 03)
Flags: bus master, 66Mhz, medium devsel, latency 64
Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
I/O behind bridge: d000-dfff
Memory behind bridge: cb80-cdef
Prefetchable memory behind bridge: cff0-cfff

00:04.0 ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02)
Flags: bus master, medium devsel, latency 0

00:04.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01)
(prog-if 80 [Master])
Flags: bus master, medium devsel, latency 32
I/O ports at b800 [size=16]

00:04.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01)
Flags: bus master, medium devsel, latency 32, IRQ 9
I/O ports at b400 [size=32]

00:04.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 02)
Flags: medium devsel

00:09.0 SCSI storage controller: Symbios Logic Inc. (formerly NCR)
53c875 (rev 14)
Subsystem: Diamond Multimedia Systems FirePort 40 Dual SCSI
Controller
Flags: bus master, medium devsel, latency 144, IRQ 9
I/O ports at b000 [size=256]
Memory at cb00 (32-bit, non-prefetchable) [size=256]
Memory at ca80 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at  [disabled] [size=64K]

00:09.1 SCSI storage controller: Symbios Logic Inc. (formerly NCR)
53c875 (rev 14)
Subsystem: Diamond Multimedia Systems FirePort 40 Dual SCSI
Controller
Flags: bus master, medium devsel, latency 144, IRQ 9
I/O ports at a800 [size=256]
Memory at ca00 (32-bit, non-prefetchable) [size=256]
Memory at c980 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at  [disabled] [size=64K]

00:0a.0 Ethernet controller: Digital Equipment Corporation DECchip 21140
[FasterNet] (rev 11)
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at a400 [size=128]
Memory at c900 (32-bit, non-prefetchable) [size=128]

00:0b.0 VGA compatible controller: Matrox Graphics, Inc. MGA 2164W
[Millennium II]
Subsystem: Matrox Graphics, Inc.: Unknown device 051b
Flags: medium devsel, IRQ 10
Memory at ce00 (32-bit, prefetchable) [disabled] [size=16M]
Memory at c880 (32-bit, non-prefetchable) [disabled]
[size=16K]
Memory at c800 (32-bit, non-prefetchable) [disabled]
[size=8M]
Expansion ROM at cdff [disabled] [size=64K]

00:0c.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24
[CrystalClear SoundFusion Audio Accelerator] (rev 01)
Subsystem: Voyetra Technologies: Unknown device 6003
Flags: bus master, slow devsel, latency 32, IRQ 11
Memory at c780 (32-bit, non-prefetchable) [size=4K]
Memory at c700 (32-bit, non-prefetchable) [size=1M]
Capabilities: [40] Power Management version 2

00:0d.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX
[Boomerang]
Flags: bus master, medium devsel, latency 32, IRQ 9
I/O ports at a000 [size=64]
Expansion ROM at  [disabled] [size=64K]

01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro AGP
1X/2X (rev 5c)
Subsystem: ATI Technologies Inc: Unknown device 4742
Flags: bus master, stepping, medium devsel, latency 64, IRQ 11
Memory at cc00 (32-bit, non-prefetchable) [size=16M]
I/O ports at d800 [size=256]
Memory at cb80 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at cffe [disabled] [size=128K]
Capabilities: [50] AGP version 1.0


# cat /proc/interrupts
   CPU0
  0:  37974  

Re: [PATCH] media/radio [check_region() removal... ]

[Bartlomiej Zolnierkiewicz]

On Wed, 8 Nov 2000, Jeff Garzik wrote:

> Patch looks generally ok.  Some of the whitespace/formatting changes are
> questionable, I usually leave that up to the maintainer unless it is
> very gratuitously opposite to CodingStyle.
>

These drivers seem to be unmantained :)
Anyway if this is a problem I can undo these changes ...

> Some of the driver messages ("foo version 1.0") are purposefully printed
> -after-, not before, the device is probed and registered.  Your patch
> gets this wrong in at least one place.
>

Yes... I wasn't sure about this... can undo...

> Finally, a word to you, Alan, and others doing request_region work:  it
> is more informative to pass the device name (minor, etc.) into
> request_region.  Ditto for request_irq.  Many (most, except net?)
> drivers use board/chip name instead of registered interface name.  If
> you can use the interface name for request_region or request_irq, use
> it... it allows differentiation between multiple boards of the same
> type.  That's especially when looking at ISA regions in /proc/ioports,
> or interrupt counts in /proc/interrupts.
> 
>   Jeff

Agree... but in this case it's less important until radio drivers
supports multiple boards...

thanks
--
Bartlomiej Zolnierkiewicz
<[EMAIL PROTECTED]>

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

Re: pcmcia

[Brett]

Hey,

I don't know if this counts as a _problem_, 
but I need to enable pci support to get pcmcia/cardbus activated.
Is this really necessary ?? My current kernels work fine without pci
support, and sure, enabling it won't hurt, just make the kernel bigger,
but why is the restriction there ?

Also, what has happened to the i82365 support that I need ? 
Its nicely commented out in drivers/net/pcmcia/Config.in

I remember everything working fine up until about test3/4, since then I've
had to revert to the pcmcia-cs package.

Just wondering whats going on ?

/ Brett

On Wed, 8 Nov 2000, David Ford wrote:
>
> With a few exceptions, it should work.  The problematic systems are few.
> 
> -d
> 
> David Feuer wrote:
> 
> > What is the current status of PC-card support?  I've seen ominous signs on
> > this list about the state of support  I have a laptop with a PCMCIA
> > network card (a 3com thing). Will it work?
> 
> --
> "The difference between 'involvement' and 'commitment' is like an
> eggs-and-ham breakfast: the chicken was 'involved' - the pig was
> 'committed'."
> 
> 
> 

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

Spew from test11-pre1

[Robert Lynch]

No oops, but right after I installed test11-pre1, then tried to
access a Windows box as a VNC client, this message started
getting continuously dumped by syslog:
===
...
Nov  8 15:32:01 ives kernel: eth0: card reports no RX buffers.
Nov  8 15:32:04 ives kernel: eth0: card reports no resources.
Nov  8 15:32:04 ives kernel: eth0: card reports no RX buffers.
Nov  8 15:32:04 ives kernel: eth0: card reports no resources.
Nov  8 15:32:05 ives kernel: eth0: card reports no RX
buffers.  
...
Nov  8 15:36:18 ives kernel: eth0: card reports no resources.
Nov  8 15:36:35 ives kernel: eth0: card reports no RX buffers.
Nov  8 15:36:49 ives kernel: SysRq: Emergency Sync
Nov  8 15:36:49 ives kernel: Syncing device 03:03 ... OK 
..
===
eth0 seems OK, I regularly check ifconfig after installing a new
kernel:
===
$ /sbin/ifconfig -a
eth0  Link encap:Ethernet  HWaddr 00:D0:B7:7A:00:B0
  inet addr:172.16.1.3  Bcast:172.16.1.255 
Mask:255.255.255.0
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:4 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:100
  Interrupt:9
...
===  
Doing a Yahoo search it seems this was previously reported
eepro100 bug, which appears to have resurfaced.

FWIW, Bob L.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: Pentium IV-summary

[H. Peter Anvin]

Followup to:  <[EMAIL PROTECTED]>
By author:Alan Cox <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> > Is this revamp only for processors that actually support the
> > CPUID-instruction, or will you fix the CPU-detection for non-CPUID
> > processors too?! There are quite a few processors that can be detected
> > properly but aren't (for instance, IBM 486slc/slc2/slc3)
> 
> Linus refused code to ident the ones that didnt matter because the code was
> (neccessarily) obscure, weird and didn't change anything but the string in
> procfs.
> 

It should be a lot cleaner to do that kind of stuff -- if you feel
it's worth bothering to -- in my changed version.  It's taking a bit
longer than I'd like, because I keep uncovering, ahem, "issues" with
the current code that can be easily fixed once one adds a real
framework for these things.  I hopefully will have something RSN.

-hpa
-- 
<[EMAIL PROTECTED]> at work, <[EMAIL PROTECTED]> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: [PATCH] media/radio [check_region() removal... ]

[Jeff Garzik]

Patch looks generally ok.  Some of the whitespace/formatting changes are
questionable, I usually leave that up to the maintainer unless it is
very gratuitously opposite to CodingStyle.

Some of the driver messages ("foo version 1.0") are purposefully printed
-after-, not before, the device is probed and registered.  Your patch
gets this wrong in at least one place.

Finally, a word to you, Alan, and others doing request_region work:  it
is more informative to pass the device name (minor, etc.) into
request_region.  Ditto for request_irq.  Many (most, except net?)
drivers use board/chip name instead of registered interface name.  If
you can use the interface name for request_region or request_irq, use
it... it allows differentiation between multiple boards of the same
type.  That's especially when looking at ISA regions in /proc/ioports,
or interrupt counts in /proc/interrupts.

Jeff


-- 
Jeff Garzik |
Building 1024   | Would you like a Twinkie?
MandrakeSoft|
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: Nvidia GeForce2 kernel driver - kernel 2.4.0 test-10

[J . A . Magallon]

On Wed, 08 Nov 2000 10:52:41 Anthony Chatman wrote:
> Speaking of Nvidia, I have a Nvidia GeForce2, and had problems loading 
> the NV kernel module with a patched test10 kernel (i was running test9 
> before).  I took a look at the test10 patch, and noticed the following 2 
> lines were taken out of  /include/linux/wrapper.h:
> 
> #define mem_map_inc_count(p) atomic_inc(&(p->count))
> #define mem_map_dec_count(p) atomic_dec(&(p->count))
> 
> I added those two defines back into wrapper.h and then was able to load 

I think you should never do that. Those macros are outdated and were
removed from kernel. Patch NVdriver instead. Patch is attached.

BTW: does your board run ok on 2.4 ? I have a TNT2 and have not been able
to get it working on a 2.4-smp. In 2.2-smp works fine. I don't know what
is bad...In a recent strace (with test10), it seemed to be hanged on a
poll() call...

-- 
Juan Antonio Magallon Lacarta #> cd /pub
mailto:[EMAIL PROTECTED] #> more beer

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

PATCH: rd - deadlock removal

[Neil Brown]

Linus,

 There is a problem with drivers/block/rd.c which can lead to a
 deadlock an SMP hardware.

 The scenario goes:

 Processor A   Processor B

 enter _make_request   in getblk (or elsewhere)
   (or generic_unplug_device)
   spin_lock(&lru_list_lock);
 spin_lock_irqsave(&io_request_lock)
   Take an interrupt
   for some block device
 call q->request_fn (== rd_rquest)
   spin_lock_irqsave(&io_request_lock);
 call getblk   BLOCK

 spin_lock(&lru_list_lock)
 BLOCK 
DEADLOCK


 I have two patches which address this problem.
 The first is simple and simply drops ui_request_lock before calling
 getblk.  This may be the appropriate one to use given the code
 freeze.

 The second is more elegant in that it side steps the problem by
 giving rd.c a make_request function instead of using the default
 _make_request.   This means that io_request_lock is simply never
 claimed my rd.

 I'll let you choose which is most appropriate for the current
 circumstances.  If you take the first, I will hold on the the second
 until 2.5.*

 Both patches also replace the usage for b_blocknr with the more
 correct b_rsector*(b_size>>9).  This would allow rd to be used under
 raid0 or lwm (should anyone choose to do so).

 For the first patch:

| sed -e '/^MARKER/,$d' | patch -p0

 for the second

| sed -e '1,/^MARKER/d' | patch -p0

NeilBrown


--- ./drivers/block/rd.c2000/11/08 23:38:33 1.1
+++ ./drivers/block/rd.c2000/11/08 23:39:45 1.2
@@ -225,8 +225,15 @@
goto repeat;
}
 
+   /* Possible deadlock when calling getblk as we currently have io_request_lock
+* and are about to take lru_list_lock.
+* Another processor may have taken lru_list_lock, and now be trying to take
+* io_request_lock from inside and interrupt handler
+*/
+   spin_unlock(&io_request_lock); /* interrupts are still disabled */
+
sbh = CURRENT->bh;
-   rbh = getblk(sbh->b_dev, sbh->b_blocknr, sbh->b_size);
+   rbh = getblk(sbh->b_dev, sbh->b_rsector/(sbh->b_size>>9), sbh->b_size);
if (CURRENT->cmd == READ) {
if (sbh != rbh)
memcpy(CURRENT->buffer, rbh->b_data, rbh->b_size);
@@ -235,6 +242,11 @@
memcpy(rbh->b_data, CURRENT->buffer, rbh->b_size);
mark_buffer_protected(rbh);
brelse(rbh);
+
+   spin_lock(&io_request_lock); /* reclaiming the lock - don't need
+   to worry about interrupts
+   because we know they are
+   disabled */
 
end_request(1);
goto repeat;


 
MARKER



--- ./include/linux/blk.h   2000/11/08 23:41:09 1.1
+++ ./include/linux/blk.h   2000/11/08 23:41:15 1.2
@@ -115,7 +115,6 @@
 
 /* ram disk */
 #define DEVICE_NAME "ramdisk"
-#define DEVICE_REQUEST rd_request
 #define DEVICE_NR(device) (MINOR(device))
 #define DEVICE_NO_RANDOM
 
--- ./drivers/block/rd.c2000/11/08 23:40:46 1.3
+++ ./drivers/block/rd.c2000/11/08 23:41:15 1.4
@@ -194,50 +194,47 @@
  * 19-JAN-1998  Richard Gooch <[EMAIL PROTECTED]>  Added devfs support
  *
  */
-static void rd_request(request_queue_t * q)
+static int rd_make_request(request_queue_t * q, int rw, struct buffer_head *sbh)
 {
unsigned int minor;
unsigned long offset, len;
struct buffer_head *rbh;
-   struct buffer_head *sbh;
 
-repeat:
-   INIT_REQUEST;

-   minor = MINOR(CURRENT->rq_dev);
+   minor = MINOR(sbh->b_rdev);
+
+   if (minor >= NUM_RAMDISKS)
+   goto fail;
 
-   if (minor >= NUM_RAMDISKS) {
-   end_request(0);
-   goto repeat;
-   }

-   offset = CURRENT->sector << 9;
-   len = CURRENT->current_nr_sectors << 9;
+   offset = sbh->b_rsector << 9;
+   len = sbh->b_size;
 
-   if ((offset + len) > rd_length[minor]) {
-   end_request(0);
-   goto repeat;
-   }
+   if ((offset + len) > rd_length[minor])
+   goto fail;
 
-   if ((CURRENT->cmd != READ) && (CURRENT->cmd != WRITE)) {
-   printk(KERN_INFO "RAMDISK: bad command: %d\n", CURRENT->cmd);
-   end_request(0);
-   goto repeat;
+   if (rw==READA)
+   rw=READ;
+   if ((rw != READ) && (rw != WRITE)) {
+   printk(KERN_INFO "RAMDISK: bad command: %d\n", rw);
+   goto fail;
}
 
-   sbh = CURRENT->bh;
-   rbh = getblk(sbh->b_dev, sbh->b_blocknr, sbh->b_size);
-   if (CURRENT->cmd == RE

Re: Looking for better VM

[Rik van Riel]

On Wed, 8 Nov 2000, Mikulas Patocka wrote:

> BTW. Why does your OOM killer in 2.4 try to kill process that mmaped
> most memory? mmap is hamrless. mmap on files can't eat memory and
> swap.

Because the thing is too stupid to take that into
consideration? :)

Btw, if your mmap()ed file still takes 1GB of memory,
you have 1GB of freeable memory left and you shouldn't
be out of memory ... or should you??

regards,

Rik
--
The Internet is not a network of computers. It is a network
of people. That is its real strength.

http://www.conectiva.com/   http://www.surriel.com/

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

[PATCH] media/radio [check_region() removal... ]

[Bartlomiej Zolnierkiewicz]

Hi!

Patch against 2.4.0-test11-pre1. It replaces check_region() by
request_region(), fixes some small bugs and tries to cleanup a bit
radio drivers... I have just seen 240t11p1ac1 and I think this
patch is superior then ac's radio part ;)

Please apply...

--
Bartlomiej Zolnierkiewicz
<[EMAIL PROTECTED]>


diff -uNr linux-240t11p1/drivers/media/radio/radio-aimslab.c 
linux/drivers/media/radio/radio-aimslab.c
--- linux-240t11p1/drivers/media/radio/radio-aimslab.c  Tue Oct  3 00:17:39 2000
+++ linux/drivers/media/radio/radio-aimslab.c   Thu Nov  9 00:37:48 2000
@@ -27,15 +27,17 @@
  *  
  */
 
-#include   /* Modules  */
-#include /* Initdata */
-#include   /* check_region, request_region */
-#include/* udelay   */
-#include /* outb, outb_p */
-#include/* copy to/from user*/
-#include /* kernel radio structs */
-#include   /* CONFIG_RADIO_RTRACK_PORT */
-#include  /* Lock for the I/O */
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+
+#define RTRACK_IO_EXTENT   0x02
 
 #ifndef CONFIG_RADIO_RTRACK_PORT
 #define CONFIG_RADIO_RTRACK_PORT -1
@@ -337,30 +339,28 @@
 
 static int __init rtrack_init(void)
 {
-   if(io==-1)
-   {
-   printk(KERN_ERR "You must set an I/O address with io=0x???\n");
+   printk(KERN_INFO "AIMSlab RadioTrack/RadioReveal card driver.\n");
+
+   if(io == -1) {
+   printk(KERN_ERR "rtrack: you must set an I/O address with 
+io=0x???\n");
return -EINVAL;
}
-
-   if (check_region(io, 2)) 
-   {
+   printk(KERN_INFO "rtrack: port 0x%x.\n", io);
+   if (!request_region(io, RTRACK_IO_EXTENT, "rtrack")) {
printk(KERN_ERR "rtrack: port 0x%x already in use\n", io);
return -EBUSY;
}
 
rtrack_radio.priv=&rtrack_unit;
-   
-   if(video_register_device(&rtrack_radio, VFL_TYPE_RADIO)==-1)
+
+   if(video_register_device(&rtrack_radio, VFL_TYPE_RADIO) == -1) {
+   release_region(io, RTRACK_IO_EXTENT);
return -EINVAL;
-   
-   request_region(io, 2, "rtrack");
-   printk(KERN_INFO "AIMSlab RadioTrack/RadioReveal card driver.\n");
+   }
 
/* Set up the I/O locking */
-   
init_MUTEX(&lock);
-   
+
/* mute card - prevents noisy bootups */
 
/* this ensures that the volume is all the way down  */
@@ -379,12 +379,11 @@
 
 EXPORT_NO_SYMBOLS;
 
-static void __exit cleanup_rtrack_module(void)
+static void __exit rtrack_cleanup(void)
 {
video_unregister_device(&rtrack_radio);
-   release_region(io,2);
+   release_region(io, RTRACK_IO_EXTENT);
 }
 
 module_init(rtrack_init);
-module_exit(cleanup_rtrack_module);
-
+module_exit(rtrack_cleanup);
diff -uNr linux-240t11p1/drivers/media/radio/radio-aztech.c 
linux/drivers/media/radio/radio-aztech.c
--- linux-240t11p1/drivers/media/radio/radio-aztech.c   Tue Oct  3 00:17:39 2000
+++ linux/drivers/media/radio/radio-aztech.cThu Nov  9 00:37:32 2000
@@ -24,14 +24,16 @@
  * - tuning structure changed - no more character arrays, other changes
 */
 
-#include   /* Modules  */
-#include /* Initdata */
-#include   /* check_region, request_region */
-#include/* udelay   */
-#include /* outb, outb_p */
-#include/* copy to/from user*/
-#include /* kernel radio structs */
-#include   /* CONFIG_RADIO_AZTECH_PORT */
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+#include 
+
+#define AZTECH_IO_EXTENT   0x02
 
 /* acceptable ports: 0x350 (JP3 shorted), 0x358 (JP3 open) */
 
@@ -288,28 +290,29 @@
 
 static int __init aztech_init(void)
 {
-   if(io==-1)
-   {
-   printk(KERN_ERR "You must set an I/O address with io=0x???\n");
+   printk(KERN_INFO "Aztech radio card driver v1.00/19990224 
[EMAIL PROTECTED]\n");
+
+   if (io == -1) {
+   printk(KERN_ERR "aztech: you must set an I/O address with 
+io=0x???\n");
return -EINVAL;
}
-
-   if (check_region(io, 2)) 
-   {
+   printk(KERN_INFO "aztech: port 0x%x.\n", io);
+   if (!request_region(io, AZTECH_IO_EXTENT, "aztech")) {
printk(KERN_ERR "aztech: port 0x%x already in use\n", io);
return -EBUSY;
}
 
init_MUTEX(&lock);
aztech_radio.priv=&aztech_unit;
-   
-   if(video_register_device(&aztech_radio, VFL_TYPE_RADIO)==-1)
+
+   if(video_register_device(&aztech_radio, VFL_TYPE_RADIO) == -1) {
+

Re: fpu now a must in kernel

[David Lang]

the problem is that unless your code does the save/restore of the FPU
registers you will corrupt user code that does floating point.

nothing else in the kernel is supposed to use the FPU, and as a result
(almost) no user->kernek->user transitions touch the FPU and therefor the
registers don't need to be saved.

If your code needs to use them it is your code's responsibility to get a
lock (to prevent something else from interrupting you), save teh
registers, do your work, restore the registers, and release the lock

there may not be a lock, but if not then you cannot schedule/sleep during
the time you have monkeyed with the FPU.

David Lang

 On Wed, 8 Nov 2000, Reto Baettig wrote:

> Date: Wed, 08 Nov 2000 10:46:25 -0800
> From: Reto Baettig <[EMAIL PROTECTED]>
> To: david <[EMAIL PROTECTED]>
> Cc: Linux Kernel List <[EMAIL PROTECTED]>
> Subject: Re: fpu now a must in kernel
> 
> When you add it to the task switcher, it takes away a lot of cpu cycles
> during each task switch and slows down your system. I think this was the
> main idea behind _not_ saving those registers. IMHO, it does not make
> sense to generally save these registers when nobody else but your driver
> uses them. 
> 
> Good luck!
> 
> Reto
> 
> david wrote:
> > 
> > hi i need fast fpu in the kernel for my lexos work
> > so how am i going to do it on the i386
> > 
> > 1 . can i add some save / restore code to the task swicher ( the right
> > way )
> >  so when it switchs from user to kernel task its saves the fpu state
> > ?
> > 
> > 2 . put the save / restore code in my code (NOT! GOOD! i do not wont to
> > do it this way it is not the right way)
> > 
> > so i have to use fpu in the kernel so its just how am i going to do it ?
> > 
> > thank you
> > 
> > David Rundle <[EMAIL PROTECTED]>
> > 
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to [EMAIL PROTECTED]
> > Please read the FAQ at http://www.tux.org/lkml/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> Please read the FAQ at http://www.tux.org/lkml/
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: pcmcia

[David Ford]

With a few exceptions, it should work.  The problematic systems are few.

-d

David Feuer wrote:

> What is the current status of PC-card support?  I've seen ominous signs on
> this list about the state of support  I have a laptop with a PCMCIA
> network card (a 3com thing). Will it work?

--
"The difference between 'involvement' and 'commitment' is like an
eggs-and-ham breakfast: the chicken was 'involved' - the pig was
'committed'."




begin:vcard 
n:Ford;David
x-mozilla-html:TRUE
adr:;;
version:2.1
email;internet:[EMAIL PROTECTED]
title:Blue Labs Developer
x-mozilla-cpt:;14688
fn:David Ford
end:vcard

Re: Linux 2.4.0test11pre1ac1

[Alan Cox]

> * CARDBUS is never defined.  Should that be CONFIG_CARDBUS?

Yep

> * just increment the version number.  There's no need to add "a" on the
> end...  this version number just differentiates us from the 'canonical'
> Donald Becker version of epic100.c.

Ok

> net/atm/pvc:  return the error value from sock_register, not toss it
> away.

> 
> 
> ramfs comments:

Note: the ramfs changes are in there for one reason only - that Im hacking
on some bits with a pda type box and I cannot be bothered to keep two
sets of trees

> That's one API change we shouldn't throw in without discussion, IMHO...
> it screams "ramfs-specific hack in core code!"

Absolutely

> And finally, don't you need to EXPORT_SYMBOL pm_devs_lock ?

Yep


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

Re: fpu now a must in kernel

[Reto Baettig]

When you add it to the task switcher, it takes away a lot of cpu cycles
during each task switch and slows down your system. I think this was the
main idea behind _not_ saving those registers. IMHO, it does not make
sense to generally save these registers when nobody else but your driver
uses them. 

Good luck!

Reto

david wrote:
> 
> hi i need fast fpu in the kernel for my lexos work
> so how am i going to do it on the i386
> 
> 1 . can i add some save / restore code to the task swicher ( the right
> way )
>  so when it switchs from user to kernel task its saves the fpu state
> ?
> 
> 2 . put the save / restore code in my code (NOT! GOOD! i do not wont to
> do it this way it is not the right way)
> 
> so i have to use fpu in the kernel so its just how am i going to do it ?
> 
> thank you
> 
> David Rundle <[EMAIL PROTECTED]>
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: PCI-PCI bridges mess in 2.4.x

[Richard Henderson]

On Wed, Nov 08, 2000 at 05:43:54PM -0500, Jeff Garzik wrote:
> FWIW, I just tested rth's update of your path on my x86 SMP box, and a
> laptop with two CardBus bridges (two CardBus slots).  Both worked
> fine...

x86 doesn't use this code at all.  Only alpha, arm, and mips.


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

Re: PCI-PCI bridges mess in 2.4.x

[Richard Henderson]

On Thu, Nov 09, 2000 at 01:03:36AM +0300, Ivan Kokshaysky wrote:
> But actually I'm concerned that all this code doesn't work at all -
> see reports from Michal Jaegermann (the bridge acts as if it drops
> config space transactions randomly).

I have no idea what Michal is seeing.  It does, however, work
just dandy on my rawhide:

-+-[01]-+-01.0
 |  +-02.0-[02]00.0
 |  +-04.0
 |  \-04.1
 \-[00]-+-01.0
+-02.0
\-05.0

01:02.0 PCI bridge: Digital Equipment Corporation DECchip 21050 (rev 02) \
(prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- \
Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- \
SERR- Reset- FastB2B-

02:00.0 SCSI storage controller: Q Logic ISP1020 (rev 02)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ \
Stepping- SERR+ FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- \
SERR- http://www.tux.org/lkml/

Re: fpu now a must in kernel

[Timur Tabi]

** Reply to message from david <[EMAIL PROTECTED]> on Thu, 09 Nov 2000
12:27:29 +1300


> 2 . put the save / restore code in my code (NOT! GOOD! i do not wont to
> do it this way it is not the right way)

That's how most people do it.



-- 
Timur Tabi - [EMAIL PROTECTED]
Interactive Silicon - http://www.interactivesi.com

When replying to a mailing-list message, please direct the reply to the mailing list 
only.  Don't send another copy to me.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: Linux 2.4.0test11pre1ac1

[Jeff Garzik]

the network driver changes look ok except for:
epic100:
* CARDBUS is never defined.  Should that be CONFIG_CARDBUS?
* just increment the version number.  There's no need to add "a" on the
end...  this version number just differentiates us from the 'canonical'
Donald Becker version of epic100.c.


net/atm/pvc:  return the error value from sock_register, not toss it
away.


ramfs comments:
* Hang on to the ramfs changes for a day or two, there is kmap cleanup
(now returns void*) going to Linus RSN.
* Does ramfs_statfs() need that sb lock in it?  Sure free_pages/inodes
might be getting updated on some other CPU, but its statfs so who
cares...
* the default ramfs maxsize, half of all RAM, seems a little
conservative.
* there is no need to kmalloc a private superblock structure, when room
is already allocated inside the superblock structure for private data. 
(sb->u)
* 


I wonder if we really need removepage added to struct address_space? 
That's one API change we shouldn't throw in without discussion, IMHO...
it screams "ramfs-specific hack in core code!"
 void __remove_inode_page(struct page *page)
 {
+   struct address_space *mapping = page->mapping;
+
+   if (mapping && mapping->a_ops && mapping->a_ops->removepage)
+   mapping->a_ops->removepage(page);
+


And finally, don't you need to EXPORT_SYMBOL pm_devs_lock ?



-- 
Jeff Garzik |
Building 1024   | Would you like a Twinkie?
MandrakeSoft|
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: Kernel oops!

[Venky]

Hi,

> > I am getting a whole lot of kernel oops, and I am not able to detect any
> > pattern.  The only thing common is the machine is pretty heavily loaded
> > at that time.  Am I having a hardware problem here, or is it something
> > else?

> looks like a memory problem, but i might be wrong.

Thanks for the tip.  I think it is a memory problem too.  Anyway, I ran
the oops text thru ksymoops (thanks, Tom).  Maybe this will give a
clearer picture.  

[ Am cross-posting this to the linux-kernel list.  Anyone replying from
that list, please include my address in the reply.  I am not on the
list. ]



ksymoops 0.7c on i586 2.2.16-3.  Options used
 -V (default)
 -k /proc/ksyms (default)
 -l /proc/modules (default)
 -o /lib/modules/2.2.16-3/ (default)
 -m /boot/System.map (specified)

Call Trace: [] 
Code: 8b 54 20 24 be 00 fe ff ff 83 7a 08 00 75 12 e8 50 96 ff ff 
Using defaults from ksymoops -t elf32-i386 -a i386

Trace; c0109f0c 
Code;   Before first symbol
 <_EIP>:
Code;   Before first symbol
   0:   8b 54 20 24   mov0x24(%eax,1),%edx
Code;  0004 Before first symbol
   4:   be 00 fe ff ffmov$0xfe00,%esi
Code;  0009 Before first symbol
   9:   83 7a 08 00   cmpl   $0x0,0x8(%edx)
Code;  000d Before first symbol
   d:   75 12 jne21 <_EIP+0x21> 0021 Before first symbol
Code;  000f Before first symbol
   f:   e8 50 96 ff ffcall   9664 <_EIP+0x9664> 9664 


Unable to handle kernel NULL pointer dereference at virtual address 0024
current->tss.cr3 = 03e97000, %cr3 = 03e97000
*pde = 
Oops: 
CPU:0
EIP:0010:[]
EFLAGS: 00010246
eax:    ebx:    ecx: 0001   edx: c2a66000
esi:    edi: bfffeec8   ebp:    esp: c2a67f98
ds: 0018   es: 0018   ss: 0018
Process wnlaunch (pid: 12823, process nr: 65, stackpage=c2a67000)
Stack:  bfffee78 c2a66000 40013ed0 c2a66000 c2a67fb8 c2a67fb8 c2a66000 
   c2a66000 c2a6608c c0109f0c  bfffeec8    
   bfffee78 0072 002b 002b 0072 400b28e9 0023 0202 
Call Trace: [] 
Code: 8b 54 24 24 be 00 fe ff ff 83 7a 08 00 75 12 e8 50 96 ff ff 

>>EIP; c0117c48<=
Trace; c0109f0c 
Code;  c0117c48 
 <_EIP>:
Code;  c0117c48<=
   0:   8b 54 24 24   mov0x24(%esp,1),%edx   <=
Code;  c0117c4c 
   4:   be 00 fe ff ffmov$0xfe00,%esi
Code;  c0117c51 
   9:   83 7a 08 00   cmpl   $0x0,0x8(%edx)
Code;  c0117c55 
   d:   75 12 jne21 <_EIP+0x21> c0117c69 
Code;  c0117c57 
   f:   e8 50 96 ff ffcall   9664 <_EIP+0x9664> c01112ac 


Unable to handle kernel NULL pointer dereference at virtual address 0024
current->tss.cr3 = 0392, %cr3 = 0392
*pde = 
Oops: 
CPU:0
EIP:0010:[]
EFLAGS: 00010246
eax:    ebx:    ecx: 0001   edx: c2a66000
esi:    edi: bfffeec8   ebp:    esp: c2a67f98
ds: 0018   es: 0018   ss: 0018
Process wnlaunch (pid: 14468, process nr: 65, stackpage=c2a67000)
Stack:  bfffee78 c2a66000 40013ed0 c2a66000 c2a67fb8 c2a67fb8 c2a66000 
   c2a66000 c2a6608c c0109f0c  bfffeec8    
   bfffee78 0072 002b 002b 0072 400b28e9 0023 0202 
Call Trace: [] 
Code: 8b 54 20 24 be 00 fe ff ff 83 7a 08 00 75 12 e8 50 96 ff ff 

>>EIP; c0117c48<=
Trace; c0109f0c 
Code;  c0117c48 
 <_EIP>:
Code;  c0117c48<=
   0:   8b 54 20 24   mov0x24(%eax,1),%edx   <=
Code;  c0117c4c 
   4:   be 00 fe ff ffmov$0xfe00,%esi
Code;  c0117c51 
   9:   83 7a 08 00   cmpl   $0x0,0x8(%edx)
Code;  c0117c55 
   d:   75 12 jne21 <_EIP+0x21> c0117c69 
Code;  c0117c57 
   f:   e8 50 96 ff ffcall   9664 <_EIP+0x9664> c01112ac 


Unable to handle kernel NULL pointer dereference at virtual address 0024
current->tss.cr3 = 02fca000, %cr3 = 02fca000
*pde = 
Oops: 
CPU:0
EIP:0010:[]
EFLAGS: 00010246
eax:    ebx:    ecx: 0001   edx: c2b84000
esi:    edi: bfffeeb8   ebp:    esp: c2b85f98
ds: 0018   es: 0018   ss: 0018
Process wnlaunch (pid: 32164, process nr: 65, stackpage=c2b85000)
Stack:  bfffee68 c2b84000 40013ed0 c2b84000 c2b85fb8 c2b85fb8 c2b84000 
   c2b84000 c2b8408c c0109f0c  bfffeeb8    
   bfffee68 0072 002b 002b 0072 400b28e9 0023 0202 
Call Trace: [] 
Code: 8b 54 20 24 be 00 fe ff ff 83 7a 08 00 75 12 e8 50 96 ff ff 

>>EIP; c0117c48<=
Trace; c0109f0c 
Code;  c0117c48 
 <_EIP>:
Code;  c0117c48<=
   0:   8b 54 20 24   mov0x24(%eax,1),%edx   <=
Code;  c01

fpu now a must in kernel

[david]

hi i need fast fpu in the kernel for my lexos work
so how am i going to do it on the i386

1 . can i add some save / restore code to the task swicher ( the right
way )
 so when it switchs from user to kernel task its saves the fpu state
?

2 . put the save / restore code in my code (NOT! GOOD! i do not wont to
do it this way it is not the right way)

so i have to use fpu in the kernel so its just how am i going to do it ?

thank you

David Rundle <[EMAIL PROTECTED]>


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

test9: running tasks not in run-queue

[Mike Kravetz]

I have been playing around with the scheduler in the test9
kernel and noticed that it sometimes chooses tasks to run
that are not on the run-queue.  This may seem strange, but
here is how it happens

task A on processor 0, calls __lock_sock() which does the
following:

void __lock_sock(struct sock *sk)
{
DECLARE_WAITQUEUE(wait, current);

add_wait_queue_exclusive(&sk->lock.wq, &wait);
for(;;) {
current->state = TASK_EXCLUSIVE | TASK_UNINTERRUPTIBLE;
spin_unlock_bh(&sk->lock.slock);
schedule();
spin_lock_bh(&sk->lock.slock);
if(!sk->lock.users)
break;
}
current->state = TASK_RUNNING;
remove_wait_queue(&sk->lock.wq, &wait);
}

Now when __lock_sock calls schedule, the task's state is set
as above and the following scheduler code removes the task from
the run-queue.

switch (prev->state & ~TASK_EXCLUSIVE) {
case TASK_INTERRUPTIBLE:
if (signal_pending(prev)) {
prev->state = TASK_RUNNING;
break;
}
default:
del_from_runqueue(prev);
case TASK_RUNNING:
}

After the task is removed from the run-queue, an interrupt is
serviced on another CPU which ultimately calls __wake_up_common().
__wake_up_common() chooses task A to wakeup and best_exclusive is
is set to A.  The following code in __wake_up_common() is then
executed:

if (best_exclusive)
best_exclusive->state = TASK_RUNNING;
wq_write_unlock_irqrestore(&q->lock, flags);

if (best_exclusive) {
if (sync)
wake_up_process_synchronous(best_exclusive);
else
wake_up_process(best_exclusive);
}

Note that the state of task A will then be set to TASK_RUNNING.
Now back on CPU 1 (where we are in the scheduler routine) we
perform the following test:

if (prev->state == TASK_RUNNING)
goto still_running;

Since the state of prev has been changed to TASK_RUNNING by the
__wake_up_common code, we set next = prev.  This means that we
potentially choose to continue running the current task, even
though the task has been deleted from the run-queue.

Now, what usually happens is that wake_up_process_synchronous or
wake_up_process will add the task back to the run-queue as soon
as the scheduler drops the run-queue lock.  Therefore, this does
not seem to cause any problems.

I'm curious, is this behavior by design OR are we just getting
lucky?

Thanks,
-- 
Mike Kravetz [EMAIL PROTECTED]
IBM Linux Technology Center
15450 SW Koll Parkway
Beaverton, OR 97006-6063 (503)578-3494
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: accessing on-card ram/rom

[Jeff Garzik]

[EMAIL PROTECTED] wrote:
> I looked at the IO-mapping.txt file. It says that
> on x86 architecture it should not make any difference.
> It also says that "on x86 it _is_ the same memory space. So
> on x86 it actually works to just dereference a pointer".

> Any inputs on this ?

Don't depend on architecture-specific guarantees like this, it could
change, etc.

Use ioremap, it's portable, it's standard, it's the way to go.  ;-)

Jeff


-- 
Jeff Garzik | "When I do this, my computer freezes."
Building 1024   |  -user
MandrakeSoft| "Don't do that."
|  -level 1
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

2.4.0-test10: "fatfs: bogus cluster size"

[Steven_Snyder]

Hello.

I am attempting to boot off a Compact Flash device which has a UMSDOS
filesystem.  When I do, I get text that looks like this:

 Partition check:
  hdc: hdc1 hdc2
 .
 .
 hdc: hdc1 hdc2
 hdc: hdc1 hdc2
 fatfs: bogus cluster size
 fatfs: bogus cluster size
 UMSDOS: msdos_read_super failed, mount aborted.

The bootable partion (/dev/hdc1) has a FAT16 filesystem and was created by
MS-DOS v6.2.  The 2nd partition (/dev/hdc2) is a Linux swap partition.  The
kernel itself is loaded by loadlin (not LILO).

This is a snippet of my configuration:

 CONFIG_FAT_FS=y
 CONFIG_MSDOS_FS=y
 CONFIG_UMSDOS_FS=y
 CONFIG_PROC_FS=y
 CONFIG_DEVPTS_FS=y
 CONFIG_EXT2_FS=y

The cluster size on this 128MB disk (a "SanDisk SDCFB-128 ATA DISK drive") is, I
 think, 2048 bytes.

(Of  possible relevance: when I do a "chkdsk" on this device, from either DOS or
Win95, I get a report that the validity cannot be checked because a path name is
illegally  longer  than  67  characters.   I  built  this  drive  by  installing
Slackware's ZipSlack package, then updating to the v2.4.0-test10 kernel.)

So... any thoughts on how to fix this complaint about cluster size?

Thank you.

(Sorry about the advertisement below.)




PLANET PROJECT will connect millions of people worldwide through the combined
technology of 3Com and the Internet. Find out more and register now at
http://www.planetproject.com


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

Linux 2.4.0test11pre1ac1

[Alan Cox]

This is the patches I have in my pending/twiddled with pile at the moment.
I'll also send bits of this off to Linus

Whats different

o   Ramfs allows size limiting (very handy when fiddling with PDA's)
o   Knows the 'kgcc' convention for conectiva/mandrake/red hat
o   Build ACPI if you have ACPI but no interpreter
o   Tidy up naming on machine check code
o   36bit MTRR
o   Fix PIV ident bug
o   Fix K6 CPU on dual board crash
o   Much faster block copy functions on the Athlon
o   Fix daemonize to do exit_files. All callers do this or should do
anyway
o   Cpqarray procfs fix
o   Fix build bug with old hard disk driver
o   Fix free then reference with pcbit isdn
o   Check/requestion region clean for radio drivers
o   Cleaner version of the PnP cadet radio patch
o   Seperate tx timeout code for 8390
o   Network driver request region fixes
o   de4x5 user space copy in spinlock fix
o   epic100 delay fixes
o   Avoid crash on iph5526 on out of memory
o   Fix locking bugs on roadrunner
o   Fix crash on insmod risk with many scsi drivers
o   Fix incorrect runtime panics in some scsi drivers
o   Fix HZ in the aha152x driver
o   Remove escaped and dead check for I2O in megaraid
o   Fix i810 audio driver
o   Fix cramfs initrd data loss bug
o   Fix power management locking
o   Fix resource printks that only print 4 digits
o   Fix missing return value in atm pvc
o   Disable SPX (doesnt work, no maintainer etc)

Alan

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

RE: accessing on-card ram/rom

[hiren_mehta]

I looked at the IO-mapping.txt file. It says that
on x86 architecture it should not make any difference.
It also says that "on x86 it _is_ the same memory space. So
on x86 it actually works to just dereference a pointer".

Any inputs on this ?

Thanks and regards,
-hiren

> -Original Message-
> From: Jeff Garzik [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, November 08, 2000 2:53 PM
> To: MEHTA,HIREN (A-SanJose,ex1)
> Cc: '[EMAIL PROTECTED]'
> Subject: Re: accessing on-card ram/rom
> 
> 
> "MEHTA,HIREN (A-SanJose,ex1)" wrote:
> > I have a PCI card which has on-card ram/rom which gets mapped
> > into pci address space and there is a separate base register
> > for this memory. Now the question is : can I access this on-card
> > memory by converting the pci base address into the virtual address
> > using bus_to_virt and adding the required offset ? Or do I need
> > to use ioremap function to map the physical address space starting
> > from the pci base address into the kernel virtual address space ?
> > Or is there any other interface to access the on-card memory ?
> > Is it that bus_to_virt can be used only for the normal RAM ?
> 
> Use ioremap.
> 
> For more details, read linux/Documentation/IO-mapping.txt.
> 
>   Jeff
> 
> 
> -- 
> Jeff Garzik | "When I do this, my computer freezes."
> Building 1024   |  -user
> MandrakeSoft| "Don't do that."
> |  -level 1
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: accessing on-card ram/rom

[Jeff Garzik]

"MEHTA,HIREN (A-SanJose,ex1)" wrote:
> I have a PCI card which has on-card ram/rom which gets mapped
> into pci address space and there is a separate base register
> for this memory. Now the question is : can I access this on-card
> memory by converting the pci base address into the virtual address
> using bus_to_virt and adding the required offset ? Or do I need
> to use ioremap function to map the physical address space starting
> from the pci base address into the kernel virtual address space ?
> Or is there any other interface to access the on-card memory ?
> Is it that bus_to_virt can be used only for the normal RAM ?

Use ioremap.

For more details, read linux/Documentation/IO-mapping.txt.

Jeff


-- 
Jeff Garzik | "When I do this, my computer freezes."
Building 1024   |  -user
MandrakeSoft| "Don't do that."
|  -level 1
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: panic in reiserfs: _get_block_create_0 gets bh_result->b_data = NULL

[Chris Mason]

On Friday, November 03, 2000 15:56:36 + Tigran Aivazian <[EMAIL PROTECTED]> wrote:

> On Fri, 3 Nov 2000, Tigran Aivazian wrote:
> 
>> Hi Hans,
>> 
>> Simply starting the validation phase of SPEC SFS with NFS mounted reiserfs
>> filesystem panics as shown in the log below. A quick look at the source
>> suggests that _get_block_create_0() (and therefore, more generally,
>> reiserfs_get_block()) was passed a buffer head bh_result with ->b_data =
>> NULL. So, we panic at line 256 of fs/reiserfs/inode.c when doing:
>> 
>> memset (bh_result->b_data, 0, inode->i_sb->s_blocksize)
>> 
> 

Ok, I've tracked these down to a few places in our tail handling code.  Working on the 
fixes now. 

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

accessing on-card ram/rom

[MEHTA,HIREN (A-SanJose,ex1)]

Hi All,

I have a PCI card which has on-card ram/rom which gets mapped
into pci address space and there is a separate base register
for this memory. Now the question is : can I access this on-card
memory by converting the pci base address into the virtual address
using bus_to_virt and adding the required offset ? Or do I need
to use ioremap function to map the physical address space starting
from the pci base address into the kernel virtual address space ?
Or is there any other interface to access the on-card memory ?
Is it that bus_to_virt can be used only for the normal RAM ?

I tried using bus_to_virt to get the virtual address and then access
it and the kernel panics.

Please copy me on your replies as I am not on the list.

Thanks and regards,
-hiren
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: Pentium IV-summary

[Alan Cox]

> Is this revamp only for processors that actually support the
> CPUID-instruction, or will you fix the CPU-detection for non-CPUID
> processors too?! There are quite a few processors that can be detected
> properly but aren't (for instance, IBM 486slc/slc2/slc3)

Linus refused code to ident the ones that didnt matter because the code was
(neccessarily) obscure, weird and didn't change anything but the string in
procfs.


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

Re: PCI-PCI bridges mess in 2.4.x

[Jeff Garzik]

Ivan Kokshaysky wrote:
> But actually I'm concerned that all this code doesn't work at all -
> see reports from Michal Jaegermann (the bridge acts as if it drops
> config space transactions randomly). I have a lot of suggestions, but
> it's a pain to debug something without access to real hardware - just
> a waste of the precious time of everyone who is involved...
> So I would probably wait a week or two until I'll have something with
> bridges :-(

FWIW, I just tested rth's update of your path on my x86 SMP box, and a
laptop with two CardBus bridges (two CardBus slots).  Both worked
fine...

I am still worried that the conditions which generate the following
message indicate a problem still exists.  (this message exists w/out
your patch..)
Unknown bridge resource 0: assuming transparent

Jeff


-- 
Jeff Garzik | "When I do this, my computer freezes."
Building 1024   |  -user
MandrakeSoft| "Don't do that."
|  -level 1
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: Pentium IV-summary##

[Alan Cox]

> that overwrites the capability state. It will be fixed in 2.2.18  by Dave Jones. 
>Should we also look at Peter Anvin's fix for the problem that Linus mentioned? What 
>are the other features of the Pentium IV should be included in the kernel pending the 
>capability state fix?

I'll send Linus the 2.2.18pre equivalent fix

Alan

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

Re: pcmcia

[Jeff Garzik]

David Feuer wrote:
> 
> What is the current status of PC-card support?  I've seen ominous signs on
> this list about the state of support  I have a laptop with a PCMCIA
> network card (a 3com thing). Will it work?

It should, yes.  Enable hotplug, cardbus, and 3com vortex/boomerang
support...

-- 
Jeff Garzik | "When I do this, my computer freezes."
Building 1024   |  -user
MandrakeSoft| "Don't do that."
|  -level 1
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

`smp_num_cpus' redefined

[Timur Tabi]

Compiling under 2.4, I get this:

/usr/include/linux/smp.h:80: warning: `smp_num_cpus' redefined
/usr/include/linux/modules/i386_ksyms.ver:82: warning: this is the location of
the previous definition
/usr/include/linux/smp.h:87: warning: `smp_call_function' redefined
/usr/include/linux/modules/i386_ksyms.ver:98: warning: this is the location of
the previous definition
/usr/include/linux/smp.h:88: warning: `cpu_online_map' redefined
/usr/include/linux/modules/i386_ksyms.ver:84: warning: this is the location of
the previous definition

Where does i386_ksyms.ver come from?



-- 
Timur Tabi - [EMAIL PROTECTED]
Interactive Silicon - http://www.interactivesi.com

When replying to a mailing-list message, please direct the reply to the mailing list 
only.  Don't send another copy to me.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

pcmcia

[David Feuer]

What is the current status of PC-card support?  I've seen ominous signs on 
this list about the state of support  I have a laptop with a PCMCIA 
network card (a 3com thing). Will it work?

--
This message has been brought to you by the letter alpha and the number pi.
David Feuer
[EMAIL PROTECTED]

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

Re: Network error

[Andre Tomt]

> Something I seen on a lug. Anyone have a patch for this?
>
> I'm trying to compile a 2.2.17 kernel.  When I do a make bzImage, I get
> this error.  It seems to be centering on networking areas (nfs, svclock,
> tcp, etc.)
>
> tcp_input.c:1393:52: warning: pasting would not give a valid preprocessing
> token
> tcp_input.c:1441:85: warning: pasting would not give a valid preprocessing
> token

This is a non fatal warning, not an error. However, newer "in-development"
gcc's have other issues making it refuse to build a full kernel image.
Either fix the makefile to use a compatible cc (egcs, kgcc for example),
define CC to make, or downgrade the default compiler to anything below or
including gcc-2.95.2

Whatever makes you sleep well at night.

--
André Tomt

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

Re: malloc(1/0) ??

[Rasmus Andersen]

On Wed, Nov 08, 2000 at 02:11:34PM -0800, H. Peter Anvin wrote:
> Followup to:  <[EMAIL PROTECTED]>
> By author:Igmar Palsenberg <[EMAIL PROTECTED]>
> In newsgroup: linux.dev.kernel

[snip]

> > May I remind you guys that a malloc(0) is equal to a free(). There is no
> > way that any mem get's malloced. 
> > 
> 
> Where the heck did you get idea?
> 
>   -hpa

Probably from the malloc man page where it is stated that *realloc* 
with size 0 equals free :)
-- 
Rasmus([EMAIL PROTECTED])

Which is worse: Ignorance or Apathy?
Who knows? Who cares?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: continuing VM madness

[Andrea Arcangeli]

On Wed, Nov 08, 2000 at 05:42:33PM +, Alan Cox wrote:
> add page aging then in theory it'll be as good as 2.2 but in practice who 

Agreed.

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

Re: malloc(1/0) ??

[H. Peter Anvin]

Followup to:  <[EMAIL PROTECTED]>
By author:Igmar Palsenberg <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> 
> > The program does not work. A program works if it does what it's supposed to
> > do. If you want to argue that this program is supposed to print "ff"
> > then explain to me why the 'malloc' contains a zero in parenthesis.
> > 
> > The program can't possibly work because it invokes undefined behavior. It
> > is impossible to determine what a program that invokes undefined behavior is
> > 'supposed to do'.
> 
> May I remind you guys that a malloc(0) is equal to a free(). There is no
> way that any mem get's malloced. 
> 

Where the heck did you get idea?

-hpa
-- 
<[EMAIL PROTECTED]> at work, <[EMAIL PROTECTED]> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Ethernet stops working in NFS

[Giuliano Pochini]

I have a Mac and a PC with a 3com 595 ethernet card. The Mac is the
nfs server. When I transfer from the PC to the Mac it's all right.
When I transfer a large file (50-100MB) from the Mac to the PC often
the connection breaks completely. I can't ping the other machine
anymore. Looking at ifconfig I see that the PC receives the pings
but it does not answer. I have to bring the PC's eth0 down and up
to get it working again. Large ping floods don't trigger the
problem.
And is it normal that I transfer at only ~5MB/s over a 100Mbps
ethernet ?

The PC runs 2.2.17 and the Mac 2.2.18pre19.

Bye.


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

Re: PCI-PCI bridges mess in 2.4.x

[Ivan Kokshaysky]

On Wed, Nov 08, 2000 at 09:37:44AM -0800, Richard Henderson wrote:
> Interesting.  I hadn't known that.  It didn't actually fail with
> the ALI bridge, I just assumed it was a mistake.  Can anyone with
> docs on non-DEC bridges confirm that this is a common thing?

It would be better if someone who has "PCI-to-PCI Bridge Architecture
Specification" handy could confirm this. Non-conforming hardware
must live in quirks/fixups etc. ;-)

I've found some interesting info today - application note on programming
the DEC 21052 bridge (ruffian has this chip, btw):
http://download.sourceforge.net/mirrors/NetBSD/misc/dec-docs/ec-qlzba-te.ps.gz

Particularly, there are examples for setting up that bridge for IO or MEM
only configurations. For example, with IO disabled:
1. Set IO base = 0x, limit = 0
2. Set command register = PCI_COMMAND_MEMORY | PCI_COMMAND_MASTER

> Certainly the fact should be commented if the old code goes back
> in to avoid disruption by helpful folks like myself.  :-)

That change wasn't bad at all - at least it's 100% safe :-)
But of course, it would be better to have unused regions disabled
in a clean way.

But actually I'm concerned that all this code doesn't work at all -
see reports from Michal Jaegermann (the bridge acts as if it drops
config space transactions randomly). I have a lot of suggestions, but
it's a pain to debug something without access to real hardware - just
a waste of the precious time of everyone who is involved...
So I would probably wait a week or two until I'll have something with
bridges :-(

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

Re: Installing kernel 2.4

[James A . Sutherland]

On Wed, 08 Nov 2000, George Anzinger wrote:
> "James A. Sutherland" wrote:
> > 
> > On Wed, 08 Nov 2000, George Anzinger wrote:
> > > But, here the customer did run the configure code (he said he did not
> > > change anything).  Isn't this where the machine should be diagnosed and
> > > the right options chosen?  Need a way to say it is a cross build, but
> > > that shouldn't be too hard.
> > 
> > Why default to incompatibility?! If the user explicitly says "I really do want
> > a kernel which only works on this specific machine as it is now, and I want it
> > to break otherwise", fine. Don't make it a default!
> 
> I could go along with this.  The user, however, had the default break,
> and, to my knowledge, there are no tools to diagnose the current (or any
> other) machine anywhere in the kernel.  Maybe it is time to do such a
> tool with exports that the configure programs could use as defaults.  My
> thought is that the tool could run independently on the target system
> (be it local or otherwise) with the results fed back to configure.

I think a default whereby the kernel built will run on any Linux-capable
machine of that architecture would be sensible - so if I grab the 2.4.0t10
tarball and build it now, with no changes, I'll be able to boot the kernel on
any x86 machine.

> (Oops, corollary to the rule that "The squeaking wheel gets the grease."
> is "S/he who complains most about the squeaking gets to do the
> greasing."  I better keep quiet :)

I'm still not convinced the wheel IS squeaking - anyone got those benchmarks??


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

problem with startx in linux kernel 2.4

[Anil kumar]

Hi,
  I ahave installed Red Hat 7.0 kernel ver 2.4.0-test9
  After I boot, when I do 
  #startx
   I get an error as server crash.
   My processor is Pentium II
 
  I am attaching with this mail the error output I get
  and also /var/log/XFree86.0.log file

  Please let me know how to fix this

  with regards,
Anil

__
Do You Yahoo!?
Thousands of Stores.  Millions of Products.  All in one Place.
http://shopping.yahoo.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

problem with shmat () and > 1GB memory in kernel 2.2.17

[Rolf Fokkens]

> Hi!
> 
> Recently we installed extra memory in our Oracle-on-Linux database server,
> it now has 1.25 GB. I installed a 2.2.17 kernel with the 2GB option
> enabled. I rebooted the machine (a Compaq Proliant 5500 dual PII 450MHz)
> and noticed that one of the databases wasn't able to start. After
> installing a 2.2.17 kernel without the 2GB option averything worked fine.
> 
> As said, one of the databases didn't start, it was the one with SID
> "linux" (this may be relevant to Oracle insiders), the other six databases
> started OK. After some reboots it appeared that espcially this database
> wouldn't start. Not being able to look into the source I did an strace on
> the server process that got into trouble, the text was something like
> "Unable to attach shared memory, OS Error 22". The strace generated a log
> which showed this:
> 
> shmget(IPC_PRIVATE, 33554432, IPC_CREAT|IPC_EXCL|0x1a0|0640) = 4872
> shmat(4872, 0x2940, 0)  = -1 EINVAL (Invalid argument)
> 
> This confirmed the problem of not being able to attach the shared memory.
> I also did an strace on this process on the 2.2.17 kernel without the 2GB
> option enabled, and it showd:
> 
> shmget(IPC_PRIVATE, 33554432, IPC_CREAT|IPC_EXCL|0x1a0|0640) = 2568
> shmat(2568, 0x2940, 0)  = 0x2940
> 
> The failing shmat isn't the first one, but the ones before all succeed,
> some lines from the strace log:
> 
> shmget(IPC_PRIVATE, 49152, IPC_CREAT|IPC_EXCL|0x1a0|0640) = 4865
> shmat(4865, 0x2000, 0)  = 0x2000
> shmget(IPC_PRIVATE, 26214400, IPC_CREAT|IPC_EXCL|0x1a0|0640) = 4866
> shmat(4866, 0x2040, 0)  = 0x2040
> shmget(IPC_PRIVATE, 23068672, IPC_CREAT|IPC_EXCL|0x1a0|0640) = 4867
> shmat(4867, 0x2200, 0)  = 0x2200
> shmget(IPC_PRIVATE, 19922944, IPC_CREAT|IPC_EXCL|0x1a0|0640) = 4868
> shmat(4868, 0x2380, 0)  = 0x2380
> shmget(IPC_PRIVATE, 17825792, IPC_CREAT|IPC_EXCL|0x1a0|0640) = 4869
> shmat(4869, 0x24c0, 0)  = 0x24c0
> shmget(IPC_PRIVATE, 29360128, IPC_CREAT|IPC_EXCL|0x1a0|0640) = 4870
> shmat(4870, 0x2600, 0)  = 0x2600
> shmget(IPC_PRIVATE, 22020096, IPC_CREAT|IPC_EXCL|0x1a0|0640) = 4871
> shmat(4871, 0x27c0, 0)  = 0x27c0
> shmget(IPC_PRIVATE, 33554432, IPC_CREAT|IPC_EXCL|0x1a0|0640) = 4872
> shmat(4872, 0x2940, 0)  = -1 EINVAL (Invalid argument)
> 
> On the 1GB kernel things go like this:
> 
> shmget(IPC_PRIVATE, 49152, IPC_CREAT|IPC_EXCL|0x1a0|0640) = 2561
> shmat(2561, 0x2000, 0)  = 0x2000
> shmget(IPC_PRIVATE, 26214400, IPC_CREAT|IPC_EXCL|0x1a0|0640) = 2562
> shmat(2562, 0x2040, 0)  = 0x2040
> shmget(IPC_PRIVATE, 23068672, IPC_CREAT|IPC_EXCL|0x1a0|0640) = 2563
> shmat(2563, 0x2200, 0)  = 0x2200
> shmget(IPC_PRIVATE, 19922944, IPC_CREAT|IPC_EXCL|0x1a0|0640) = 2564
> shmat(2564, 0x2380, 0)  = 0x2380
> shmget(IPC_PRIVATE, 17825792, IPC_CREAT|IPC_EXCL|0x1a0|0640) = 2565
> shmat(2565, 0x24c0, 0)  = 0x24c0
> shmget(IPC_PRIVATE, 29360128, IPC_CREAT|IPC_EXCL|0x1a0|0640) = 2566
> shmat(2566, 0x2600, 0)  = 0x2600
> shmget(IPC_PRIVATE, 22020096, IPC_CREAT|IPC_EXCL|0x1a0|0640) = 2567
> shmat(2567, 0x27c0, 0)  = 0x27c0
> shmget(IPC_PRIVATE, 33554432, IPC_CREAT|IPC_EXCL|0x1a0|0640) = 2568
> shmat(2568, 0x2940, 0)  = 0x2940
> shmget(IPC_PRIVATE, 32505856, IPC_CREAT|IPC_EXCL|0x1a0|0640) = 2569
> shmat(2569, 0x2b40, 0)  = 0x2b40
> shmget(3779348124, 13291520, IPC_CREAT|IPC_EXCL|0x1a0|0640) = 2570
> shmat(2570, 0x2d40, 0)  = 0x2d40
> 
> The only thing I see is that shmaddr (shmat's second argument) climbs
> above 0x2800. This is confirmed by another database that runs fine on
> the 2GB kernel:
> 
> shmget(IPC_PRIVATE, 49152, IPC_CREAT|IPC_EXCL|0x1a0|0640) = 7303
> shmat(7303, 0x2000, 0)  = 0x2000
> shmget(IPC_PRIVATE, 20971520, IPC_CREAT|IPC_EXCL|0x1a0|0640) = 7304
> shmat(7304, 0x2040, 0)  = 0x2040
> shmget(2522853243, 0, 0)= -1 ENOENT (No such file or
> directory)
> shmat(7305, 0x2180, 0)  = 0x2180
> shmat(7305, 0, 0)   = 0x2ac4a000
> shmat(7305, 0x2180, 0)  = 0x2180
> shmat(7303, 0x2000, 0)  = 0x2000
> shmat(7304, 0x2040, 0)  = 0x2040
> 
> All shmaddr's are below 0x2800 and everything is fine. This may be
> accidental, but it's all I see.
> 
> Because the machine is a production system I installed the 1GB 2.2.17
> kernel, but I saved the strace logs, so If any you want's then I can mail
> them.
> 
> Rolf
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: [ANNOUNCE] Generalised Kernel Hooks Interface (GKHI)

[Michael Rothwell]

Sounds great; unfortunately, the core group has spoken out against a
modular kernel.

Perhaps IBM should get together with SGI, HP and other interested
parties and start an Advanced Linux Kernel Project. Then they can run
off and make their scalable, modular, enterprise kernel and the Linus
Version can always merge back in features from it.

-M

[EMAIL PROTECTED] wrote:
> 
> We've just release version 0.6 of Generalised Kernel Hooks Interface (GKHI)
> see the IBM Linux Technology Centre's web page DProbes link:
> http://oss.software.ibm.com/developerworks/opensource/linux
> 
> Some folks expressed an interest in this type of facility recently in
> discussions concerning making call-backs from the kernel to kernel modules.
> 
> Here's the abstract for this facility. With this intend to modularise our
> RAS offerings, in particular DProbes, so that they can be applied
> dynamically without having to be carried as excess baggage.
> 
> Abstract:
> Generalised Kernel Hooks Interface (GKHI) is a generalised facility for
> placing hooks or exits in arbitrary kernel locations. It enables many
> kernel enhancements, which are  otherwise self-contained, to become
> loadable kernel modules and retain a substantial degree of independence
> from the kernel source. This affords advantages for maintenance and
> co-existence with other kernel enhancements. The hook interface allows
> multiple kernel modules to register their exits for a given hook, in order
> to receive control at that hook location. Multiple hooks may be defined
> within the kernel and a singe kernel module may register exits to use
> multiple hooks.  When hook exits register they may specify co-existence
> criteria. Hooks may be placed in kernel modules as well as the kernel
> itself with the proviso that the modules with hooks are loaded before the
> gkhi hook interfacing module. A hook exit receives control as if called
> from the code in which the hook is located. Parameters may be passed to a
> hook exit and may be modified by an exit. For more information down-load
> the tarball.
> 
> Note: GHKI is in late beta test - we currently do not support SMP, that
> will occur soon. We also plan to support dynamic hook definition as little
> later on so that kernel modules may dynamically register hooks for other
> kernel modules to use.
> 
> Richard Moore -  RAS Project Lead - Linux Technology Centre (PISC).
> 
> http://oss.software.ibm.com/developerworks/opensource/linux
> Office: (+44) (0)1962-817072, Mobile: (+44) (0)7768-298183
> IBM UK Ltd,  MP135 Galileo Centre, Hursley Park, Winchester, SO21 2JN, UK
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: multiple definition of `__module_kernel_version'

[Keith Owens]

On Wed, 08 Nov 2000 15:15:59 -0600, 
Timur Tabi <[EMAIL PROTECTED]> wrote:
>../support/schedule.h:16: parse error
>
>and line 16 says:
>
>#if LINUX_VERSION_CODE < KERNEL_VERSION(2,3,0)

#include 

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

[ANNOUNCE] Generalised Kernel Hooks Interface (GKHI)

[richardj_moore]

We've just release version 0.6 of Generalised Kernel Hooks Interface (GKHI)
see the IBM Linux Technology Centre's web page DProbes link:
http://oss.software.ibm.com/developerworks/opensource/linux

Some folks expressed an interest in this type of facility recently in
discussions concerning making call-backs from the kernel to kernel modules.

Here's the abstract for this facility. With this intend to modularise our
RAS offerings, in particular DProbes, so that they can be applied
dynamically without having to be carried as excess baggage.

Abstract:
Generalised Kernel Hooks Interface (GKHI) is a generalised facility for
placing hooks or exits in arbitrary kernel locations. It enables many
kernel enhancements, which are  otherwise self-contained, to become
loadable kernel modules and retain a substantial degree of independence
from the kernel source. This affords advantages for maintenance and
co-existence with other kernel enhancements. The hook interface allows
multiple kernel modules to register their exits for a given hook, in order
to receive control at that hook location. Multiple hooks may be defined
within the kernel and a singe kernel module may register exits to use
multiple hooks.  When hook exits register they may specify co-existence
criteria. Hooks may be placed in kernel modules as well as the kernel
itself with the proviso that the modules with hooks are loaded before the
gkhi hook interfacing module. A hook exit receives control as if called
from the code in which the hook is located. Parameters may be passed to a
hook exit and may be modified by an exit. For more information down-load
the tarball.

Note: GHKI is in late beta test - we currently do not support SMP, that
will occur soon. We also plan to support dynamic hook definition as little
later on so that kernel modules may dynamically register hooks for other
kernel modules to use.


Richard Moore -  RAS Project Lead - Linux Technology Centre (PISC).

http://oss.software.ibm.com/developerworks/opensource/linux
Office: (+44) (0)1962-817072, Mobile: (+44) (0)7768-298183
IBM UK Ltd,  MP135 Galileo Centre, Hursley Park, Winchester, SO21 2JN, UK


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

Re: multiple definition of `__module_kernel_version'

[Timur Tabi]

** Reply to message from Keith Owens <[EMAIL PROTECTED]> on Thu, 09 Nov 2000
08:08:31 +1100


> In 2.2 you have to
> #define __NO_VERSION__ before including module.h in all of the module
> objects except one.  Search 2.2 drivers for __NO_VERSION__ to see
> examples of this.

If I do that, I get this error:

../support/schedule.h:16: parse error

and line 16 says:

#if LINUX_VERSION_CODE < KERNEL_VERSION(2,3,0)



-- 
Timur Tabi - [EMAIL PROTECTED]
Interactive Silicon - http://www.interactivesi.com

When replying to a mailing-list message, please direct the reply to the mailing list 
only.  Don't send another copy to me.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: multiple definition of `__module_kernel_version'

[Keith Owens]

On Wed, 08 Nov 2000 14:09:43 -0600, 
Timur Tabi <[EMAIL PROTECTED]> wrote:
>I'm trying to port my driver from 2.4 to 2.2.  When I try to compile it, I get
>several "multiple definition of `__module_kernel_version'" errors:

include/linux/module.h was changed in the 2.3 kernels to define
__module_kernel_version and __module_using_checksums as static.
Without that change you get multiple definitions of the variables when
you link multiple objects into a single module.  In 2.2 you have to
#define __NO_VERSION__ before including module.h in all of the module
objects except one.  Search 2.2 drivers for __NO_VERSION__ to see
examples of this.

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

Re: Network error

[Carey M. Drake]

Guess: you're using RedHat 7.0 (or somehow else are using a "new"
version of gcc).
Either use make cc=kgcc for redhat or downgrade gcc to a supported
version.

James Simmons wrote:
> 
> Something I seen on a lug. Anyone have a patch for this?
> 
> I'm trying to compile a 2.2.17 kernel.  When I do a make bzImage, I get
> this error.  It seems to be centering on networking areas (nfs, svclock,
> tcp, etc.)
> 
> tcp_input.c:1393:52: warning: pasting would not give a valid preprocessing
> token
> tcp_input.c:1441:85: warning: pasting would not give a valid preprocessing
> token
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> Please read the FAQ at http://www.tux.org/lkml/

-- 
C.

--  

When in doubt, poke it with a stick

Disclaimer: the above is the author's personal opinion and is not the
opinion
or policy of his employer or of the little green men that have been
following
him all day.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Network error

[James Simmons]

Something I seen on a lug. Anyone have a patch for this?

I'm trying to compile a 2.2.17 kernel.  When I do a make bzImage, I get
this error.  It seems to be centering on networking areas (nfs, svclock,
tcp, etc.)

tcp_input.c:1393:52: warning: pasting would not give a valid preprocessing
token
tcp_input.c:1441:85: warning: pasting would not give a valid preprocessing
token

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

Re: sb.o support in 2.4-broken?

[Richard Torkar]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Richard Torkar wrote:

> Jim Bonnet wrote:
> 
> > I am using the 2.4.0-test10 kernel. I have a sound blaster 16 which
> > works fine under 2.2.17.
> >
> > I see that a while back someone posted on this problem previously but
> > there were no answers I can find..
> >
> > Is support for soundblaster16 ISA broken in the 2.4 kernel? Compiled in
> > or used as a module I can not get it to work. I have passed sb=220,5,1,5
> > during boot when compiled in and also sent those during insmod.
> >
> > When I boot to 2.2.17 these are the correct values and sound is happy :)
> >
> > I am subbed to this group so you may answer here so this is on record.
> >
> > Thanks much...
> 
> 
> What does 2.4.* say Jim?
> You have the right modutils installed?
> Any error msg?
> 
> I have an old SB16 ISA and it works without a problem on 2.4.0-test10.
> And it hasn't caused me any problems for a very long time :)
> 
> I have sound compiled as modules.
> My lilo.conf (sound part) looks like this.
 ^
Correction modules.conf I mean *duuuh*


> 
> path[sound]=/lib/modules/`uname -r`/kernel/drivers/sound
> alias sound-service-0-0 opl3
> alias sound-slot-0 sb
> options sound dmabuf=1
> alias midi opl3
> options opl3 io=0x388
> options sb io=0x220 irq=7 dma=1 dma16=5 mpu_io=0x330
> 
> I have no idea if the  sound-service-0-0 and sound-slot-0 part is right
> but it works and dosn't give any errors. I haven't had time to check what
> service and slot really affects...
> 
> Do you get any errors while inserting the modules?
> 
> 
> 
> /Richard
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> Please read the FAQ at http://www.tux.org/lkml/
>  Output from gpg 
> gpg: Signature made Wed 08 Nov 2000 09:49:39 PM CET using DSA key ID 8A36DD1B
> gpg: Good signature from "Richard Torkar (Linux) <[EMAIL PROTECTED]>"
> 
> 

/Richard
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE6Cb5IUSLExYo23RsRAhWPAKC2seiMwCKfQaDhs0/eYrUhorciXQCg4bwh
VMBEDzjthtT6bjEn69mtAcM=
=83jY
-END PGP SIGNATURE-


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

Re: major problem with linux-2.4.0test10

[Carey M. Drake]

Why not just remove the sa lines from /etc/crontab?

C.

Byron Stanoszek wrote:
> 
> On Wed, 8 Nov 2000, J.D. Hollis wrote:
> 
> > I've been having a problem with memory since 2.4.0test9...for some reason,
> > shortly after my system boots, my hard drive begins to seek rapidly for no
> > apparent reason, and suddenly about 150MB of my 256MB RAM is filled up with
> > something gtop labels 'Other.'  whatever's filling my memory isn't attached
> > to any process.   the one time I managed to get gtop open while the hard
> > drive was seeking, I noticed that kflushd was using about 98% of my
> > processor (an Athlon 900MHz).  I'm running Redhat 7.0 (although I have no
> > idea whether that makes a difference).
> 
> It's probably a program called 'sa' that anacron starts up right after boot
> (on RH 7.0). It's a system accounting program that starts up and scans the
> entire drive looking for stuff, which fills up cache in RAM.
> 
> I generally disable all anacron stuff and remove /etc/cron.??* and the
> daily/weekly/monthly entries in /etc/crontab, then I run
> '/etc/rc.d/init.d/crond restart'. That oughta fix it, but you might want to
> look into the cron scripts individually and selectively remove the lines you
> don't want. :-)
> 
> --
> Byron Stanoszek Ph: (330) 644-3059
> Systems Programmer  Fax: (330) 644-8110
> Commercial Timesharing Inc. Email: [EMAIL PROTECTED]
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> Please read the FAQ at http://www.tux.org/lkml/

-- 
C.

--  

When in doubt, poke it with a stick

Disclaimer: the above is the author's personal opinion and is not the
opinion
or policy of his employer or of the little green men that have been
following
him all day.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: sb.o support in 2.4-broken?

[Richard Torkar]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Jim Bonnet wrote:

> I am using the 2.4.0-test10 kernel. I have a sound blaster 16 which
> works fine under 2.2.17.
> 
> I see that a while back someone posted on this problem previously but
> there were no answers I can find..
> 
> Is support for soundblaster16 ISA broken in the 2.4 kernel? Compiled in
> or used as a module I can not get it to work. I have passed sb=220,5,1,5
> during boot when compiled in and also sent those during insmod.
> 
> When I boot to 2.2.17 these are the correct values and sound is happy :)
> 
> I am subbed to this group so you may answer here so this is on record.
> 
> Thanks much...


What does 2.4.* say Jim?
You have the right modutils installed?
Any error msg?

I have an old SB16 ISA and it works without a problem on 2.4.0-test10.
And it hasn't caused me any problems for a very long time :)

I have sound compiled as modules.
My lilo.conf (sound part) looks like this.

path[sound]=/lib/modules/`uname -r`/kernel/drivers/sound
alias sound-service-0-0 opl3
alias sound-slot-0 sb
options sound dmabuf=1
alias midi opl3
options opl3 io=0x388
options sb io=0x220 irq=7 dma=1 dma16=5 mpu_io=0x330

I have no idea if the  sound-service-0-0 and sound-slot-0 part is right
but it works and dosn't give any errors. I haven't had time to check what
service and slot really affects...

Do you get any errors while inserting the modules?



/Richard
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE6CbxjUSLExYo23RsRAtceAKCfB+8rU1vpBp8GaF2rL7LzUjVB7wCg6yGE
6p0NWko/dIB7/X36nILXGFc=
=gal1
-END PGP SIGNATURE-


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

Re: Pentium IV-summary

[David Weinehall]

On Wed, Nov 08, 2000 at 12:36:21PM -0800, H. Peter Anvin wrote:
> Followup to:  <[EMAIL PROTECTED]>
> By author:Frank Davis <[EMAIL PROTECTED]>
> In newsgroup: linux.dev.kernel
> > 
> > 2. There's a bug in get_model_name(),
> >cpuid(0x8001, &dummy, &dummy, &dummy, &(c->x86_capability));
> > 
> > that overwrites the capability state. It will be fixed in 2.2.18 by
> > Dave Jones. Should we also look at Peter Anvin's fix for the problem
> > that Linus mentioned? What are the other features of the Pentium IV
> > should be included in the kernel pending the capability state fix?
> > 
> 
> I'm working on a revamp of the i386 CPUID detection code, which will
> fix this problem as a side effect.

Is this revamp only for processors that actually support the
CPUID-instruction, or will you fix the CPU-detection for non-CPUID
processors too?! There are quite a few processors that can be detected
properly but aren't (for instance, IBM 486slc/slc2/slc3)


/David Weinehall
  _ _
 // David Weinehall <[EMAIL PROTECTED]> /> Northern lights wander  \\
//  Project MCA Linux hacker//  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/http://www.tux.org/lkml/

Re: Pentium IV-summary

[H. Peter Anvin]

Followup to:  <[EMAIL PROTECTED]>
By author:Frank Davis <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
> 
> 2. There's a bug in get_model_name(),
>cpuid(0x8001, &dummy, &dummy, &dummy, &(c->x86_capability));
> 
> that overwrites the capability state. It will be fixed in 2.2.18 by
> Dave Jones. Should we also look at Peter Anvin's fix for the problem
> that Linus mentioned? What are the other features of the Pentium IV
> should be included in the kernel pending the capability state fix?
> 

I'm working on a revamp of the i386 CPUID detection code, which will
fix this problem as a side effect.

-hpa
-- 
<[EMAIL PROTECTED]> at work, <[EMAIL PROTECTED]> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: major problem with linux-2.4.0test10

[Byron Stanoszek]

On Wed, 8 Nov 2000, J.D. Hollis wrote:

> I've been having a problem with memory since 2.4.0test9...for some reason,
> shortly after my system boots, my hard drive begins to seek rapidly for no
> apparent reason, and suddenly about 150MB of my 256MB RAM is filled up with
> something gtop labels 'Other.'  whatever's filling my memory isn't attached
> to any process.   the one time I managed to get gtop open while the hard
> drive was seeking, I noticed that kflushd was using about 98% of my
> processor (an Athlon 900MHz).  I'm running Redhat 7.0 (although I have no
> idea whether that makes a difference).

It's probably a program called 'sa' that anacron starts up right after boot
(on RH 7.0). It's a system accounting program that starts up and scans the
entire drive looking for stuff, which fills up cache in RAM.

I generally disable all anacron stuff and remove /etc/cron.??* and the
daily/weekly/monthly entries in /etc/crontab, then I run 
'/etc/rc.d/init.d/crond restart'. That oughta fix it, but you might want to
look into the cron scripts individually and selectively remove the lines you
don't want. :-)

-- 
Byron Stanoszek Ph: (330) 644-3059
Systems Programmer  Fax: (330) 644-8110
Commercial Timesharing Inc. Email: [EMAIL PROTECTED]

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

Re: Installing kernel 2.4

[George Anzinger]

"James A. Sutherland" wrote:
> 
> On Wed, 08 Nov 2000, George Anzinger wrote:
> > But, here the customer did run the configure code (he said he did not
> > change anything).  Isn't this where the machine should be diagnosed and
> > the right options chosen?  Need a way to say it is a cross build, but
> > that shouldn't be too hard.
> 
> Why default to incompatibility?! If the user explicitly says "I really do want
> a kernel which only works on this specific machine as it is now, and I want it
> to break otherwise", fine. Don't make it a default!

I could go along with this.  The user, however, had the default break,
and, to my knowledge, there are no tools to diagnose the current (or any
other) machine anywhere in the kernel.  Maybe it is time to do such a
tool with exports that the configure programs could use as defaults.  My
thought is that the tool could run independently on the target system
(be it local or otherwise) with the results fed back to configure.

(Oops, corollary to the rule that "The squeaking wheel gets the grease."
is "S/he who complains most about the squeaking gets to do the
greasing."  I better keep quiet :)

> 
> BTW: Has anyone benchmarked the different optimizations - i.e. how much
> difference does optimizing for a Pentium make when running on a PII? More to
> the point, how about optimizing non-exclusively for a Pentium, so the code
> still runs on earlier CPUs?
> 
> James.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: sb.o support in 2.4-broken?

[Kurt Roeckx]

On Wed, Nov 08, 2000 at 12:53:18PM -0800, Jim Bonnet wrote:
> I am using the 2.4.0-test10 kernel. I have a sound blaster 16 which
> works fine under 2.2.17.
> 
> I see that a while back someone posted on this problem previously but
> there were no answers I can find..
> 
> Is support for soundblaster16 ISA broken in the 2.4 kernel? Compiled in
> or used as a module I can not get it to work. I have passed sb=220,5,1,5
> during boot when compiled in and also sent those during insmod.

Use sb=0x220,5,1,5


Kurt

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

Pentium IV-summary

[Frank Davis]

Hello,

I think I have summarized the discussion for clarity: 

1. rep nop can used with all x86 boxes, unless a valid example can be found where it 
doesn't work. Athlon works with the rep nop. 

2. There's a bug in get_model_name(),
   cpuid(0x8001, &dummy, &dummy, &dummy, &(c->x86_capability));

that overwrites the capability state. It will be fixed in 2.2.18  by Dave Jones. 
Should we also look at Peter Anvin's fix for the problem that Linus mentioned? What 
are the other features of the Pentium IV should be included in the kernel pending the 
capability state fix?

3. 2.4.x may support processor speeds up to 100GHz, as well as Pentium IV. Linus will 
have a Pentium IV available soon, but can someone test the kernel with a Pentium IV 
sooner?

Regards,
Frank


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

Pentium IV-summary

[Frank Davis]

Hello,

I think I have summarized the discussion for clarity: 

1. rep nop can used with all x86 boxes, unless a valid example can be found where it 
doesn't work. Athlon works with the rep nop. 

2. There's a bug in get_model_name(),
   cpuid(0x8001, &dummy, &dummy, &dummy, &(c->x86_capability));

that overwrites the capability state. It will be fixed in 2.2.18  by Dave Jones. 
Should we also look at Peter Anvin's fix for the problem that Linus mentioned? What 
are the other features of the Pentium IV should be included in the kernel pending the 
capability state fix?

3. 2.4.x may support processor speeds up to 100GHz, as well as Pentium IV. Linus will 
have a Pentium IV available soon, but can someone test the kernel with a Pentium IV 
sooner?

Regards,
Frank


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

multiple definition of `__module_kernel_version'

[Timur Tabi]

I'm trying to port my driver from 2.4 to 2.2.  When I try to compile it, I get
several "multiple definition of `__module_kernel_version'" errors:

ver is 2.2.14-6.0
ld -r --print-map --cref -Map tdmcddk.map global.o init.o tiermap.o support.o
cccomp.o ccmp_sft.o lz77.o ccmp_s32.o gcmp_sft.o gencomp.o infoapi.o thread.o
callback.o -o tdmcddk.sys
init.o: In function `WaitStandardUnit':
/home/ttabi/src/tdimm/tdmcddk.sys/init.c:181: multiple definition of
`__module_kernel_version'
global.o(.modinfo+0x0):/home/ttabi/src/tdimm/tdmcddk.sys/global.c: first
defined here
tiermap.o: In function `FsbToDimmSlot':
/home/ttabi/src/tdimm/tdmcddk.sys/tiermap.c:10: multiple definition of
`__module_kernel_version'
global.o(.modinfo+0x0):/home/ttabi/src/tdimm/tdmcddk.sys/global.c: first
defined here
support.o: In function `IsGoodCpu':
/home/ttabi/src/tdimm/tdmcddk.sys/../support/common/cpuid.c:5: multiple
definition of `__module_kernel_version'
global.o(.modinfo+0x0):/home/ttabi/src/tdimm/tdmcddk.sys/global.c: first
defined here
cccomp.o: In function `CompressIntoCCache':
/home/ttabi/src/tdimm/tdmcddk.sys/cccomp.c:11: multiple definition of
`__module_kernel_version'
global.o(.modinfo+0x0):/home/ttabi/src/tdimm/tdmcddk.sys/global.c: first
defined here
ccmp_sft.o: In function `CompressIntoCCacheSoft':
/home/ttabi/src/tdimm/tdmcddk.sys/ccmp_sft.c:12: multiple definition of
`__module_kernel_version'
global.o(.modinfo+0x0):/home/ttabi/src/tdimm/tdmcddk.sys/global.c: first
defined here
lz77.o: In function `PackLZ77Triplette':
/home/ttabi/src/tdimm/tdmcddk.sys/lz77.c:95: multiple definition of
`__module_kernel_version'
global.o(.modinfo+0x0):/home/ttabi/src/tdimm/tdmcddk.sys/global.c: first
defined here
ccmp_s32.o: In function `CompressIntoCCacheS32':
/home/ttabi/src/tdimm/tdmcddk.sys/ccmp_s32.c:12: multiple definition of
`__module_kernel_version'
global.o(.modinfo+0x0):/home/ttabi/src/tdimm/tdmcddk.sys/global.c: first
defined here
gcmp_sft.o: In function `GenericCompressSoft':
/home/ttabi/src/tdimm/tdmcddk.sys/gcmp_sft.c:12: multiple definition of
`__module_kernel_version'
global.o(.modinfo+0x0):/home/ttabi/src/tdimm/tdmcddk.sys/global.c: first
defined here
gencomp.o: In function `GenericCompress':
/home/ttabi/src/tdimm/tdmcddk.sys/gencomp.c:11: multiple definition of
`__module_kernel_version'
global.o(.modinfo+0x0):/home/ttabi/src/tdimm/tdmcddk.sys/global.c: first
defined here
infoapi.o: In function `tdmGetDriverConfig':
/home/ttabi/src/tdimm/tdmcddk.sys/infoapi.c:12: multiple definition of
`__module_kernel_version'
global.o(.modinfo+0x0):/home/ttabi/src/tdimm/tdmcddk.sys/global.c: first
defined here
thread.o: In function `SetAnvilRestartTimer':
/home/ttabi/src/tdimm/tdmcddk.sys/thread.c:10: multiple definition of
`__module_kernel_version'
global.o(.modinfo+0x0):/home/ttabi/src/tdimm/tdmcddk.sys/global.c: first
defined here
callback.o: In function `InitializeCallbackQueue':
/home/ttabi/src/tdimm/tdmcddk.sys/callback.c:84: multiple definition of
`__module_kernel_version'
global.o(.modinfo+0x0):/home/ttabi/src/tdimm/tdmcddk.sys/global.c: first
defined here
make: *** [tdmcddk.sys] Error 1
[ttabi@one tdmcddk.sys]$ 

I've searched through the mailing list archives, but none of the "fixes"
suggested earlier seem to work.  Why does this happen?  And why doesn't it
happen with 2.4?



-- 
Timur Tabi - [EMAIL PROTECTED]
Interactive Silicon - http://www.interactivesi.com

When replying to a mailing-list message, please direct the reply to the mailing list 
only.  Don't send another copy to me.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

sb.o support in 2.4-broken?

[Jim Bonnet]

I am using the 2.4.0-test10 kernel. I have a sound blaster 16 which
works fine under 2.2.17.

I see that a while back someone posted on this problem previously but
there were no answers I can find..

Is support for soundblaster16 ISA broken in the 2.4 kernel? Compiled in
or used as a module I can not get it to work. I have passed sb=220,5,1,5
during boot when compiled in and also sent those during insmod.

When I boot to 2.2.17 these are the correct values and sound is happy :)

I am subbed to this group so you may answer here so this is on record.

Thanks much...


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

Re: Looking for better VM

[Ingo Oeser]

On Wed, Nov 08, 2000 at 05:36:40PM +0100, Mikulas Patocka wrote:
> BTW. Why does your OOM killer in 2.4 try to kill process that mmaped most
> memory? mmap is hamrless. mmap on files can't eat memory and swap.

Don't complain, build your own and test it ;-)

Apply my patch

http://www.tu-chemnitz.de/~ioe/oom_kill_api.patch

and install your own OOM handler using install_oom_killer() 
from . It has all the needed documentation inline
that will be build along the kernel-api-book.

Have fun researching in this area.

PS: Applies cleanly since oom_kill.c exists and also against
   2.4.0-test11-pre1.

Regards

Ingo Oeser
-- 
To the systems programmer, users and applications
serve only to provide a test load.
:x
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/