Re: [patch][rfc][rft] vm throughput 2.4.2-ac4

[Mike Galbraith]

> > Have you tried to use SWAP_SHIFT as 4 instead of 5 on a stock 2.4.2-ac5 to
> > see if the system still swaps out too much?
>
> Not yet, but will do.

Didn't help.  (It actually reduced throughput a little)

-Mike

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

making menuconfig on a 2.4.2-ac6 kernel :-)

[Lombardo, Federico]

Please report alan :-)



Menuconfig has encountered a possible error in one of the kernel's
configuration files and is unable to continue.  Here is the error
report:

 Q> scripts/Menuconfig: MCmenu0: command not found

Please report this to the maintainer <[EMAIL PROTECTED]>.  You may also
send a problem report to <[EMAIL PROTECTED]>.

Please indicate the kernel version you are trying to configure and
which menu you were trying to enter when this error occurred.

make: *** [menuconfig] Error 1
root@WEBSRV:/usr/src/linux#


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

Re: [PATCH][CFT] per-process namespaces for Linux

[Alexander Viro]

On Wed, 28 Feb 2001, Albert D. Cahalan wrote:

> Alexander Viro writes:
> 
> > * CLONE_NEWNS is made root-only (CAP_SYS_ADMIN, actually)
> 
> Would an unprivileged version that killed setuid be OK to have?
> 
> Evil idea of the day: non-directory (even non-existant) mount points and
> non-directory mounts. So then "mount --bind /etc/foo /dev/bar" works.

BTW, out of curiosity: what's that evil about non-directory mounts?
You obviously shouldn't mix directories with non-directories in that
context (userland will not take that lightly, same as with rename(),
etc.), but binding a non-directory over non-directory... Why not?
Me, I'm playing with
% mount -t devloop /tmp/image /dev/loop0 -o offset=4096
Yes, in that order. /dev/loop0 is the mountpoint here. ioctls? We don't
need on stinkin' ioctls. Now, _that_ I would call evil... Pretty simple,
actually - filesystem with ->read_super() making ->s_root not a directory
but a block device. And setting it up (lo_set_fd() with small modifications).
Still alpha, requires namespace patch (or at least s_lock one), but seems
to be working. Simpler than loop.c in official tree, BTW - no ioctls, no
handling pending requests since we unset device only upon umount, when
we have nobody keeping it open. losetup? What losetup? Shell script, if
somebody would bother to write it (going through losetup options and turning
them into mount ones).

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

Re: ISO-8859-1 completeness of kernel fonts?

[idalton]

Hello all..

I'm interested in making a 16x32 console font, so I can run my 21"
display at 100x37 text. I've asked on the framebuffer list already, but
have heard no reply, and the list seems to be defunct.

Since it's a fixed-frequency display, I want to have the framebuffer and
basic font in-kernel and loaded at boot time. I'm not sure where to find
the necessary tools/documentation to do all the steps, though. Could
someone point me in the right direction?

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

Report bug in kernel 2.4.x:

[Thomas Lau]

Well, someone using ne2000 chipset have same problem-drop connection

some people already post in mail list, but the sound like no one
interested about our problem

it will auto drop connection when used a long time ( over 24 hours )
I can not use ifconfig to restart the interface, so I must reboot the
kernel ( system )
I didn't reach this problem before, but in 2.4.x, I hope it will fix
soon and please help us to fix
my system config:
Cable modem
NE2000-PCI
problem type:
connection drop when used over 24 hours or more



Thanks

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

Re: [PATCH][CFT] per-process namespaces for Linux

[Alexander Viro]

On Wed, 28 Feb 2001, Albert D. Cahalan wrote:

> Alexander Viro writes:
> 
> > * CLONE_NEWNS is made root-only (CAP_SYS_ADMIN, actually)
> 
> Would an unprivileged version that killed setuid be OK to have?

Not until we get decent resource accounting here.

> Evil idea of the day: non-directory (even non-existant) mount points and
> non-directory mounts. So then "mount --bind /etc/foo /dev/bar" works.

Try it. It _does_ work.

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

Re: [PATCH][CFT] per-process namespaces for Linux

[Albert D. Cahalan]

Alexander Viro writes:

>   * CLONE_NEWNS is made root-only (CAP_SYS_ADMIN, actually)

Would an unprivileged version that killed setuid be OK to have?

Evil idea of the day: non-directory (even non-existant) mount points and
non-directory mounts. So then "mount --bind /etc/foo /dev/bar" works.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reserved memory for highmem bouncing

[Marcelo Tosatti]

Hi Ingo,

I have a question about the highmem page IO deadlock fix which is in
2.4.2-ac. (the emergency memory thing)

The old create_bounce code used to set PF_MEMALLOC on the task flags and
call wakeup_bdflush(1) in case GFP_BUFFER page allocation failed. That was
broken because flush_dirty_buffers() could try to flush a buffer pointing
to highmem page, which would end up in create_bounce again, but with
PF_MEMALLOC.

Have you tried to make flush_dirty_buffers() only flush buffers pointing
to lowmem pages in case the caller wants it to do so?

This way you can call flush_dirty_buffers() with the guarantee you're
going to free useful (lowmem) memory. This also throttles high mem writes
giving priority to low mem ones.


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

-ac6 mis-reports cpu clock

[bradley mclain]

here is an extract from dmesg from 2.4.2 and -ac6,
showing a disparity in cpu clock speed..

-ac6 has inserted a line claiming my clock is 400Mhz
(it is actually 533 -- and i believe my fsb is 133).

i don't think i compiled these two radically
differently.  what could i have done wrong to cause
this?  or has -ac6 introduced a bug of some sort?

any suggestions for debugging or additional
information?

thanks,
bradley mclain

__
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail. 
http://personal.mail.yahoo.com/
 compare

Re: [patch] patch-2.4.2-irda1 (irda-usb)

[Greg KH]

On Tue, Feb 27, 2001 at 06:41:09PM -0800, Jean Tourrilhes wrote:
> 
>   First thanks for Dag for bringing me into the conversation. I
> may add my little bit of spice, especially that I was the one pushing
> for having the driver in .../drivers/net/irda.
>   By the way, Greg, sorry if I hurt your feeling, I don't want
> to put down any of the great work that has been done on the USB stack.

Thanks, but it didn't bother me, or hurt any of my feelings at all.  I
just wanted to point out that all of the other usb drivers (with 2
exceptions) reside in the drivers/usb directory, and I didn't know if
you knew that.

(the exceptions are the input drivers, which are part of the input core,
and the cpia video driver, which has the parallel port and the usb
driver all together in one file.)

>   My feeling is that devices are mostly defined by their higher
> level interface, because this is what is closer to the user.
>   If I look at a Pcmcia Ethernet card, I will tend to associate
> more with a PCI Ethernet card rather than a Pcmcia SCSI card. Both
> card have the same high level interface (TCP/IP) even if their low
> level interface is different (Pcmcia, PCI).
>   People tend to agree with that, and that's why you have
> directories called drivers/net, drivers/scsi and driver/sound, rather
> that drivers/pci, drivers/isa, drivers/mca and drivers/pcmcia.

This argument has been discussed in the past (see the linux-usb-devel
and linux-kernel mailing list archives) but from what I remember, Linus
and others wanted them all to stay in the drivers/usb directory for now.

Personally I don't care either way, but it has been easier to do usb
core changes (such as the hotplug interface changes that I suggested for
your driver) with all of the drivers in one place, not that I can't do a
recursive grep :)

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]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [2.4.2-ac5] X (4.0.1) crashes

[Erik DeBill]

I'm having no problems with 2.4.2-ac6, using XFree86 4.0.2 and the
included nv (nvidia) driver.  Works great with my geForce2 GTS,
without any binary only drivers.  4.0.2 seemed to have improved
support for nvidia chips.

If it's any help, I'm also using the rivafb for console (although not
for X).


Erik


On Tue, Feb 27, 2001 at 03:08:30PM +0100, Manfred H. Winter wrote:
> Hi!
> 
> Yesterday I've upgraded my 2.4.2 kernel to ac5, because loop-device
> seems not to work in plain 2.4.2. But now my X-server crashes.
> 
> When I start with startx, X comes up, gnome starts, sawfish starts. Then
> the system freezes. Even SysRQ-keys don't work.
> 
> I use XFree86 4.0.1 with nvidia-drivers 0.96.
> 
> I can't find anything about the crash in the logs, even the output from
> X doesn't get written to disk.
> 
> Is this a known problem?
> 
> I'm going back to vanilla 2.4.2 for now. Is there another way to get
> loop to work?
> 
> Bye,
> 
> Manfred
> -- 
>  /"\| PGP-Key available at Public Key Servers
>  \ /  ASCII ribbon campaign | or at "http://www.mahowi.de/"
>   X   against HTML mail | RSA: 0xC05BC0F5 * DSS: 0x4613B5CA
>  / \  and postings  | GPG: 0x88BC3576 * ICQ: 61597169
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Alternative driver for Lucent 802.11 cards

[David Gibson]

I've written a driver for the Lucent and Cabletron 802.11 cards, to
replace the wvlan_cs driver. I'm looking for people to test this
driver with as many card/firmware variations as possible.

The new driver doesn't use the Lucent HCF-Light code, and as a
consequence the code should be easier to follow. The locking is also
slightly more sophisticated in that this driver shouldn't leave IRQs
disabled for long periods of time like wvlan_cs can.

The driver is basically complete, although it lacks a few features of
wvlan_cs (some less used iwconfig settings). Currently it supports the
Lucent and Cabletron cards, and it partially works (no WEP) on at
least one Prism based card (the Farallon Skyline). I hope to make it
support the Apple Airport cards as well, eventually.

wvlan_cs, the linux-wlan driver and the NetBSD if_wi driver were all
used quite heavily as references in writing this driver. This driver
is written (currently) strictly for use with 2.4 - it won't work with
2.2 or with the out-of-the-kernel pcmcia modules (mostly for trivial
reasons).

Currently it's not nicely packaged. The various files can be grabbed
from:
 http://www.linuxcare.com.au/dgibson/dldwd/
How to build and install the driver is left as an exercise to the
reader.

-- 
David Gibson, Technical Support Engineer, Linuxcare, Inc.
+61 2 6262 8990
[EMAIL PROTECTED] http://www.linuxcare.com/ 
Linuxcare. Putting open source to work.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [patch][rfc][rft] vm throughput 2.4.2-ac4

[Mike Galbraith]

On Tue, 27 Feb 2001, Marcelo Tosatti wrote:

> On Tue, 27 Feb 2001, Mike Galbraith wrote:
>
> > What the patch does is simply to push I/O as fast as we can.. we're
> > by definition I/O bound and _can't_ defer it under any circumstance,
> > for in this direction lies constipation.  The only thing in the world
> > which will make it better is pushing I/O.
>
> In your I/O bound case, yes. But not in all cases.

That's one reason I tossed it out.  I don't _think_ it should have any
negative effect on other loads, but a test run might find otherwise.

> > What we do right now (as kswapd) is scan a tiny portion of the active
> > page list, and then push an arbitrary amount of swap because we can't
> > possibly deactivate enough pages if our shortage is larger than the
> > search area (nr_active_pages >> 6).. repeat until give-up time.  In
> > practice here (test load, but still..), that leads to pushing soon
> > to be unneeded [supposition!] pages into swap a full 3/4 of the time.

(correction: it's 2/3 of the time not 3/4.. off by one bug in fingers;)

> Have you tried to use SWAP_SHIFT as 4 instead of 5 on a stock 2.4.2-ac5 to
> see if the system still swaps out too much?

Not yet, but will do.

-Mike

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

scripts/Menuconfig error

[Mark Pinto]

Using kernel 2.4.2 with ac6 patch attempting to run make menuconfig

Menuconfig has encountered a possible error in one of the kernel's
configuration files and is unable to continue.  Here is the error
report:

 Q> scripts/Menuconfig: MCmenu0: command not found

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

RE: [patch] patch-2.4.2-irda1 (irda-usb)

[Dunlap, Randy]

> From: Jean Tourrilhes [mailto:[EMAIL PROTECTED]]
> 
>   First thanks for Dag for bringing me into the conversation. I
> may add my little bit of spice, especially that I was the one pushing
> for having the driver in .../drivers/net/irda.
>   By the way, Greg, sorry if I hurt your feeling, I don't want
> to put down any of the great work that has been done on the USB stack.
> 
>   My feeling is that devices are mostly defined by their higher
> level interface, because this is what is closer to the user.
>   If I look at a Pcmcia Ethernet card, I will tend to associate
> more with a PCI Ethernet card rather than a Pcmcia SCSI card. Both
> card have the same high level interface (TCP/IP) even if their low
> level interface is different (Pcmcia, PCI).
>   People tend to agree with that, and that's why you have
> directories called drivers/net, drivers/scsi and driver/sound, rather
> that drivers/pci, drivers/isa, drivers/mca and drivers/pcmcia.
> 
>   If I get an IrDA-USB dongle, the feature that matter the most
> is that it does IrDA, the fact that it connect to my PC via USB is
> rather secondary.
>   That's it. I hope it explain some of the rationale and why we
> departed from the usual drivers/usb arrangement. Actually, I think
> that stuffing all USB drivers in drivers/usb is not that great, but
> that's not my call...

That has been discussed & Linus like[ds] it that way.

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

Re: [patch] set kiobuf io_count once, instead of increment

[Marcelo Tosatti]

On Tue, 27 Feb 2001, Robert Read wrote:

> Currently in brw_kiovec, iobuf->io_count is being incremented as each
> bh is submitted, and decremented in the bh->b_end_io().  This means
> io_count can go to zero before all the bhs have been submitted,
> especially during a large request. This causes the end_kio_request()
> to be called before all of the io is complete.  
> 
> This suggested patch against 2.4.2 sets io_count to the total amount
> before the bhs are submitted, although there is probably a better way
> to determine the io_count than this.
> 
> robert
> 
> diff -ru linux/fs/buffer.c linux-rm/fs/buffer.c
> --- linux/fs/buffer.c Mon Jan 15 12:42:32 2001
> +++ linux-rm/fs/buffer.c  Tue Jan 30 11:41:57 2001
> @@ -2085,6 +2085,7 @@
>   offset = iobuf->offset;
>   length = iobuf->length;
>   iobuf->errno = 0;
> + atomic_set(>io_count, length/size);
>   
>   for (pageind = 0; pageind < iobuf->nr_pages; pageind++) {
>   map  = iobuf->maplist[pageind];
> @@ -2119,8 +2120,6 @@
>   bh[bhind++] = tmp;
>   length -= size;
>   offset += size;
> -
> - atomic_inc(>io_count);
>  
>   submit_bh(rw, tmp);
>   /* 
> -

It seems your patch breaks bh allocation failure handling. If
get_unused_buffer_head() fails, iobuf->io_count never reaches 0, so
processes waiting on kiobuf_wait_for_io() will block forever.


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

2.4.2-ac6 hangs on boot w/AMD Elan SC520 dev board

[Brian Moyle]

Kernel 2.4.2-ac6 hangs while booting an AMD Elan SC520 development board.

Long-story-short

If I define "STANDARD_MEMORY_BIOS_CALL" in setup.S and misc.c, it boots 
fine.  Here are the results:

memory map that hangs (added debugging to setup.S to determine E820 map):
   hand-copied physical RAM map:
bios-e820: 0009f400 @  (usable)
bios-e820: 0c00 @ 0009f400 (reserved)
bios-e820: 03f0 @ 0010 (usable)
bios-e820: 03f0 @ 0010 (usable)
bios-e820: 0010 @ fff0 (reserved)

memory map that works (#define STANDARD_MEMORY_BIOS_CALL in setup.S & misc.c):
   BIOS-provided physical RAM map:
BIOS-88: 0009f000 @  (usable)
BIOS-88: 03f0 @ 0010 (usable)


Is this the result of a BIOS problem?


Long-story-long
===
(when STANDARD_MEMORY_BIOS_CALL is not defined)

Booting from a floppy, I see the following message:

   "Uncompressing Linux... Ok, booting the kernel."

That's the last print statement I see.

Adding debug, it appears to go through the following:

   init/main.c:
  start_kernel {
 ...
 setup_arch(_line);
 ...
  }

   arch/i386/kernel/setup.c:
  setup_arch {
 ...
 for (i = 0; i < e820.nr_map; i++) {
...
free_bootmem(PFN_PHYS(curr_pfn), PFN_PHYS(size)); ...
...
 }
 ...
  }

   mm/bootmem.c:
  free_bootmem{
 return(free_bootmem_core(contig_page_data.bdata, addr, size));
  }

   mm/bootmem.c:
  free_bootmem_core {
 ...
 for (i = sidx; i < eidx; i++) {
...
if (!test_and_clear_bit(i, bdata->node_bootmem_map)) {
   BUG();
}
 }
  }

   include/asm-i386/page.h:
  BUG {
 printk("kernel BUG at %s:%d!\n", __FILE__, __LINE__);
 ...
  }

   (at this point, it appears to be in an infinite printk loop )

I didn't spend much time looking into the printk loop, but it seems to 
end up there, even if CONFIG_DEBUG_BUGVERBOSE is not defined, as if the 
".byte 0x0f,0x0b" is causing the loop to begin.

Any ideas/suggestions/comments?

Brian
[EMAIL PROTECTED]

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

Re: rx_copybreak value for non-i386 architectures

[David S. Miller]

Jun Sun writes:
 > I notice that many net drivers set rx_copybreak to 1518 (the max packet size)
 > for non-i386 architectures.  Once I thought I understood it and it seems
 > related to cache line alignment.  However, I am not sure exactly about the
 > reason now.  Can someone enlighten me a little bit?

Most non-x86 architectures take a large hit for unaligned accesses.
If the ethernet chip cannot land the beginning of the packet at an
arbitrary byte offset (a modulo 2 offset for ethernet is needed for an
aligned IP header) then the rx_copybreak is set to the ethernet MTU
so that all packets get copied into new buffers where they can have
their header aligned.

Later,
David S. Miller
[EMAIL PROTECTED]

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

2.4.2 & eepro100

[Gashaw Teshome]

I recently compiled a fresh download of a 2.4.2 kernel to test a server
at work.  The machine is a dual P-III, 512 MB RAM on an Intel L440GX+
motherboard with a built in eepro100 network interface.  Almost
immediately after boot up, the kernel started reporting:

Feb 23 19:40:23 www136 kernel: NET: 486 messages suppressed.
Feb 23 19:40:29 www136 kernel: NET: 858 messages suppressed.
Feb 23 19:40:33 www136 kernel: NET: 879 messages suppressed.
Feb 23 19:40:38 www136 kernel: NET: 983 messages suppressed.
Feb 23 19:40:43 www136 kernel: NET: 1296 messages suppressed.
Feb 23 19:40:49 www136 kernel: NET: 1780 messages suppressed.
Feb 23 19:40:53 www136 kernel: NET: 1378 messages suppressed.
Feb 23 19:40:58 www136 kernel: NET: 246 messages suppressed.
Feb 23 19:41:04 www136 kernel: NET: 173 messages suppressed.
Feb 23 19:41:09 www136 kernel: NET: 32 messages suppressed.
Feb 23 19:42:32 www136 kernel: NET: 37 messages suppressed.

At the same time, our bandwidth graph (rrdtool) showed almost zero
network traffic.  Also, load on the test machine went to 30!  After the
errors went away, bandwidth returned to normal and load went down
considerably.

This cycle (error message, extremely high load, zero bandwidth) repeated
about every half hour and lasted for about 1 1/2 minutes.  I eventually
took the machine down and rebooted it with its original 2.2 kernel. 
There were no more error messages or bandwidth drops after that.

I have heard mentioned that there are some issues with the eepro100
driver in 2.4.x.  Could that be the cause of this strange behaviour? 
Any help would be appreciated.


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

Re: [patch] patch-2.4.2-irda1 (irda-usb)

[Jean Tourrilhes]

On Tue, Feb 27, 2001 at 01:58:11PM -0800, Greg KH wrote:
> On Tue, Feb 27, 2001 at 08:32:28PM +, Dag Brattli wrote:
> > > I'd recommend that this file be in the /drivers/usb directory, much like
> > > almost all other USB drivers are.
> > 
> > Yes, but do we want to spread the IrDA code around? The same argument
> > applies to IrDA device drivers!?
> 
> I agree, and am not saying that it _has_ to be there.  Just a
> suggestion, and if you're comfortable with it in the irda directory,
> that's fine.
> 
> thanks,
> 
> greg k-h

Hi,

First thanks for Dag for bringing me into the conversation. I
may add my little bit of spice, especially that I was the one pushing
for having the driver in .../drivers/net/irda.
By the way, Greg, sorry if I hurt your feeling, I don't want
to put down any of the great work that has been done on the USB stack.

My feeling is that devices are mostly defined by their higher
level interface, because this is what is closer to the user.
If I look at a Pcmcia Ethernet card, I will tend to associate
more with a PCI Ethernet card rather than a Pcmcia SCSI card. Both
card have the same high level interface (TCP/IP) even if their low
level interface is different (Pcmcia, PCI).
People tend to agree with that, and that's why you have
directories called drivers/net, drivers/scsi and driver/sound, rather
that drivers/pci, drivers/isa, drivers/mca and drivers/pcmcia.

If I get an IrDA-USB dongle, the feature that matter the most
is that it does IrDA, the fact that it connect to my PC via USB is
rather secondary.
That's it. I hope it explain some of the rationale and why we
departed from the usual drivers/usb arrangement. Actually, I think
that stuffing all USB drivers in drivers/usb is not that great, but
that's not my call...

Have fun...

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

rx_copybreak value for non-i386 architectures

[Jun Sun]

I notice that many net drivers set rx_copybreak to 1518 (the max packet size)
for non-i386 architectures.  Once I thought I understood it and it seems
related to cache line alignment.  However, I am not sure exactly about the
reason now.  Can someone enlighten me a little bit?

Basically I try to understand whether for MIPS architectures we need to set
this value as well.

Please CC your reply to my email address.

TIA.

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

Re: mke2fs hangs while running on /dev/loop0 - kernel version 2.4

[Arnaldo Carvalho de Melo]

Em Tue, Feb 27, 2001 at 06:25:08PM -0800, Amit D Chaudhary escreveu:
> I am hoping someone knows more about this case. I have a intel pc 
> running linux 2.4 and the last command below hangs and the statements as 
> they are printed. Even kill -9 does not get it to terminate.
> 
> #touch img.test
> #dd if=/dev/zero of=img.test bs=1k count=2000
> 2000+0 records in
> 2000+0 records out
> #losetup /dev/loop0 img.test
> #mke2fs
> 

known bug, try 2.4.2-ac5 (ac6 seems to have some small problems,
Keith seems to have fixed with a patch some moments ago) some friends of
mine said 2.4.2-ac seems to make loop behave, haven't checked

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

mke2fs hangs while running on /dev/loop0 - kernel version 2.4

[Amit D Chaudhary]

Hi,

I am hoping someone knows more about this case. I have a intel pc 
running linux 2.4 and the last command below hangs and the statements as 
they are printed. Even kill -9 does not get it to terminate.

#touch img.test
#dd if=/dev/zero of=img.test bs=1k count=2000
2000+0 records in
2000+0 records out
#losetup /dev/loop0 img.test
#mke2fs

mke2fs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
256 inodes, 2000 blocks
100 blocks (5.00%) reserved for the super user
First data block=1
1 block group
8192 blocks per group, 8192 fragments per group
256 inodes per group

Writing inode tables: done
..

Thanks
Amit

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

Error running menuconfig

[Nick Pasich]

 I received this error running "make menuconfig" after applying
 patch-2.4.2-ac6.bz2 to linux-2.4.2 ...

 ( Nick Pasich )

 
 

 Menuconfig has encountered a possible error in one of the kernel's
 configuration files and is unable to continue.  Here is the error
 report:

  Q> scripts/Menuconfig: MCmenu0: command not found

  Please report this to the maintainer <[EMAIL PROTECTED]>.  You may also
  send a problem report to <[EMAIL PROTECTED]>.

  Please indicate the kernel version you are trying to configure and
  which menu you were trying to enter when this error occurred.

  make: *** [menuconfig] Error 1

 
 

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

Re: Linux 2.4.2ac6

[Keith Owens]

On Tue, 27 Feb 2001 16:54:28 -0800 (PST), 
"Sergey Kubushin" <[EMAIL PROTECTED]> wrote:
>Menuconfig doesn't work. Worked fine in 2.4.2-ac5.

Against 2.4.2-ac6.

Index: 2.9/arch/i386/config.in
--- 2.9/arch/i386/config.in Wed, 28 Feb 2001 12:44:01 +1100 kaos 
(linux-2.4/T/c/36_config.in 1.1.2.1.1.2 644)
+++ 2.9(w)/arch/i386/config.in Wed, 28 Feb 2001 12:46:03 +1100 kaos 
+(linux-2.4/T/c/36_config.in 1.1.2.1.1.2 644)
@@ -379,6 +379,6 @@ bool '  Memory mapped I/O debugging' CON
 bool '  Magic SysRq key' CONFIG_MAGIC_SYSRQ
 bool '  Spinlock debugging' CONFIG_DEBUG_SPINLOCK
 bool '  Verbose BUG() reporting (adds 70K)' CONFIG_DEBUG_BUGVERBOSE
-endmenu
-
 fi
+
+endmenu

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

Re: Dynamically altering code segments

[Karim Yaghmour]

"Collins, Tom" wrote:
[snip]
> I have one more question:  My trace code is currently
> implemented as a kernel loadable module.  Would I need
> to change that so that it is built as part of the kernel,
> or can I keep it as a loadable module?  If I can keep it
> as a module, I would ensure that the module would be the
> only place that would enable/disable the trace, (don't
> want the kernel jumping to a nonexistant address :O  ..)
[snip]

No need to do that, except if you modify the binary dynamically.
If that's the case, then you'll probably have to make it part
of the kernel. But ... if you modify your code to use the
pre-existing hooks that come with LTT, you may not need to
modify anything more than what is provided with by the LTT
patch. That is, you may want to know that LTT provides a
hooking mechanism similar, but less flexible, than the one
GKHI provides. The advantage, though, is that there are pre-defined
hooks inserted with the LTT patch which can be used right
away without further instrumentation.

As this type of hooking comes more and more in need, I'm
currently discussing with Richard the possibility of using
the LTT pre-defined hooks with GKHI in order to provide an
extensible hooking mechanism for the kernel that comes equipped
with an already quite useful set of hooks, which, of course,
can be dynamically enabled/disabled.

Using this type of hooking, you only need to worry about
registering/unregistering your callbacks since the kernel
doesn't jump in your code, but in the hooks management code
first.

Best regards,

Karim

===
 Karim Yaghmour
   [EMAIL PROTECTED]
  Operating System Consultant
 (Linux kernel, real-time and distributed systems)
===
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.2ac6

[Sergey Kubushin]

Menuconfig doesn't work. Worked fine in 2.4.2-ac5.

Error message:

=== Cut ===
Menuconfig has encountered a possible error in one of the kernel's
configuration files and is unable to continue.  Here is the error
report:

 Q> scripts/Menuconfig: MCmenu0: command not found

Please report this to the maintainer <[EMAIL PROTECTED]>.  You may also
send a problem report to <[EMAIL PROTECTED]>.

Please indicate the kernel version you are trying to configure and
which menu you were trying to enter when this error occurred.
=== Cut ===

---
Sergey Kubushin Sr. Unix Administrator
CyberBills, Inc.Phone:  702-567-8857
874 American Pacific Dr,Fax:702-567-8808
Henderson, NV, 89014

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

Re: Linux 2.4.2ac6

[J . A . Magallon]

On 02.28 Alan Cox wrote:
> 
>   ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
> 
> 2.4.2-ac6

Warning: EXTRAVERSION is still -ac5.

-- 
J.A. Magallon  $> cd pub
mailto:[EMAIL PROTECTED]  $> more beer

Linux werewolf 2.4.2-ac5 #1 SMP Tue Feb 27 01:09:47 CET 2001 i686

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

Re: another Linux-2.4.2 splat: *** target pattern contains no `%'. Stop.

[Keith Owens]

On Tue, 27 Feb 2001 15:25:45 -0600, 
"David L. Nicol" <[EMAIL PROTECTED]> wrote:
>[david@nicol1 linux]$ make dep
>
>make[3]: Entering directory `/mnt/sdb2/src/linux-2.4.2/drivers'
>make -C acpi fastdep
>make[4]: Entering directory `/mnt/sdb2/src/linux-2.4.2/drivers/acpi'
>Makefile:29: *** target pattern contains no `%'.  Stop.

grep make Documentation/Changes

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

Re: [2.4.2-ac5] X (4.0.1) crashes

[Alan Cox]

> I use XFree86 4.0.1 with nvidia-drivers 0.96.

Take it up with nvidia. Obfuscated effectively binary only code isnt anyone
elses problem

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

Re: [2.4.2-ac5] X (4.0.1) crashes

[J Sloan]

"Manfred H. Winter" wrote:

> I'm going back to vanilla 2.4.2 for now. Is there another way to get
> loop to work?

Working fine here:

2.4.2 + Axboe's loop patch + Morton's low latency patch

jjs

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

Patchlet for drivers/usb/hub.c

[Peter Zaitcev]

--- linux-2.4.2-ac5/drivers/usb/hub.c   Tue Feb 27 15:52:05 2001
+++ linux-2.4.2-ac5-p3/drivers/usb/hub.cTue Feb 27 16:21:32 2001
@@ -150,14 +150,14 @@
unsigned int pipe;
int i, maxp, ret;
 
-   hub->descriptor = kmalloc(sizeof(hub->descriptor), GFP_KERNEL);
+   hub->descriptor = kmalloc(sizeof(*hub->descriptor), GFP_KERNEL);
if (!hub->descriptor) {
-   err("Unable to kmalloc %d bytes for hub descriptor", 
sizeof(hub->descriptor));
+   err("Unable to kmalloc %d bytes for hub descriptor", 
+sizeof(*hub->descriptor));
return -1;
}
 
/* Request the entire hub descriptor. */
-   ret = usb_get_hub_descriptor(dev, hub->descriptor, sizeof(hub->descriptor));
+   ret = usb_get_hub_descriptor(dev, hub->descriptor, sizeof(*hub->descriptor));
/* descriptor> is large enough for a hub with 127 ports;
 * the hub can/will return fewer bytes here. */
if (ret < 0) {
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[patch] set kiobuf io_count once, instead of increment

[Robert Read]

Currently in brw_kiovec, iobuf->io_count is being incremented as each
bh is submitted, and decremented in the bh->b_end_io().  This means
io_count can go to zero before all the bhs have been submitted,
especially during a large request. This causes the end_kio_request()
to be called before all of the io is complete.  

This suggested patch against 2.4.2 sets io_count to the total amount
before the bhs are submitted, although there is probably a better way
to determine the io_count than this.

robert

diff -ru linux/fs/buffer.c linux-rm/fs/buffer.c
--- linux/fs/buffer.c   Mon Jan 15 12:42:32 2001
+++ linux-rm/fs/buffer.cTue Jan 30 11:41:57 2001
@@ -2085,6 +2085,7 @@
offset = iobuf->offset;
length = iobuf->length;
iobuf->errno = 0;
+   atomic_set(>io_count, length/size);

for (pageind = 0; pageind < iobuf->nr_pages; pageind++) {
map  = iobuf->maplist[pageind];
@@ -2119,8 +2120,6 @@
bh[bhind++] = tmp;
length -= size;
offset += size;
-
-   atomic_inc(>io_count);
 
submit_bh(rw, tmp);
/* 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[2.4.2-ac5] X (4.0.1) crashes

[Manfred H. Winter]

Hi!

Yesterday I've upgraded my 2.4.2 kernel to ac5, because loop-device
seems not to work in plain 2.4.2. But now my X-server crashes.

When I start with startx, X comes up, gnome starts, sawfish starts. Then
the system freezes. Even SysRQ-keys don't work.

I use XFree86 4.0.1 with nvidia-drivers 0.96.

I can't find anything about the crash in the logs, even the output from
X doesn't get written to disk.

Is this a known problem?

I'm going back to vanilla 2.4.2 for now. Is there another way to get
loop to work?

Bye,

Manfred
-- 
 /"\| PGP-Key available at Public Key Servers
 \ /  ASCII ribbon campaign | or at "http://www.mahowi.de/"
  X   against HTML mail | RSA: 0xC05BC0F5 * DSS: 0x4613B5CA
 / \  and postings  | GPG: 0x88BC3576 * ICQ: 61597169
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Linux 2.4.2ac6

[Alan Cox]

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

2.4.2-ac6
o   Remove incorrect modules doc changes(Keith Owens)
o   Fix elf.h defines   (Keith Owens)
o   Add 0x2B mtrr decode for intel/cyrix III(me)
o   Make bigmem balancing somewhat saner(Mark Hemment)
o   Update irda (Dag Brattli)
o   New FIR dongle support  (Dag Brattli)
o   3ware driver updates(Adam Radford)
o   Further reiserfs tail conversion fixes  (Chris Mason)
o   Fix tpqic02 to use capable  (Rob Radez)
o   Set last_rx on comtrol hostess driver   (Arnaldo Carvalho 
 de Melo)
o   Raid Oops fix   (Neil Brown)
o   Fix last_rx/skb refs on cyc_x25 (Arnaldo Carvalho 
 de Melo)
o   Fix last_rx/skb refs on 3c589   (Arnaldo Carvalho 
 de Melo)
o   Highmem fixes for deadlock  (Andrea Arcangeli,
 Ingo Molnar)
o   Another minor tulip fix (Jeff Garzik)
o   Fix hinote and maybe other ps/aux hangs (me, Mark Clegg)
o   Fix resource handling on 53c7xxx(Rasmus Andersen)
o   Fix scsi_register failure handling on AMD scsi  (Rasmus Andersen)
o   Fix resource handling on aha1740(Rasmus Andersen)
o   Fix resource handling on blz1230(Rasmus Andersen)
o   Fix resource handling for dec_esp driver(Rasmus Andersen)
o   Fix resource handling for fastlane scsi (Rasmus Andersen)
o   Fix scsi_register failure on qlogic_fas (Rasmus Andersen)
o   Fix scsi_register failure on qlogicfc   (Rasmus Andersen)
o   Fix irq alloc failure leak on sun3x_esp (Rasmus Andersen)
o   Fix wd7000 init failures(Rasmus Andersen)
o   Fix nbd device  (Steve Whitehouse)
o   Fix try_atomic_semop(Manfred Spraul)
o   Parport fixes   (Tim Waugh)
o   Starfire start/stop if fix  (Ion Badulescu)
o   Fix raw.c off by one bug(Tigran Aivazian)
o   USB hub kmalloc wrong size corruption fix   (Peter Zaitcev)

2.4.2-ac5
o   Add Epson 1240U scanners to usb scanner (Joel Becker)
o   Fix eth= compatibility  (Andrew Morton)
| Should fix 3c509 problems for one
o   Add Pnp table to opl3sa2(Bill Nottingham)
o   Update loop driver fixes(Jens Axboe, Andrea
 Arcangeli, Al Viro)
o   Fix busy loop in usb storage(Arjan van de Ven)
o   Add cardbus support to olympic  (Mike Phillips)
o   Make BUG() configurable to save space   (Arjan van de Ven)
o   Add configurability to most kernel debugging(various people)
functions on x86
o   Richard Günther/binfmt_misc page move   (Richard Günther)
o   Fix de4x5 crash (Nikita Schmidt)
o   Hopefully fix the smc-mca driver(me)
o   Don't run the disk queue if we didnt launder(Marcelo Tosatti)
any pages
o   ALi 6 channel audio and sp/dif updates  (Matt Wu)
o   Fix USB thread wakeup scheduling(Arjan van de Ven)
o   Fix alignment problems with uni16_to_x8 (Ivan Kokshaysky)

2.4.2-ac4
o   Fix Make xconfig failure(J Magallon)
o   Fix a typo in the ISDN docs (Jim Freeman)
o   Fix the 3ware driver a bit more (Ben LaHaise)
| should now be usable
o   Update Dave Jones contact info  (Dave Jones)
o   Revert wavelan inline->macro change (Jean Tourillhes)
| CVS gcc and 2.96-74 don't accidentally unline it now
o   Zerocopy TCP/IP patches (Dave Miller, 
 Alexey Kuznetsov,
 and many more)
o   Fix up command line options to old ncr driver   (Martin Storsjö)
o   NFS locking should call fs layer locking if (Brian Dixon)
present
o   Fix cs46xx wakeup/poll problem  (David Huggins-Daines)
o   Add some missing MTD config help texts  (Steven Cole,
 David Woodhouse)
o   Fix Alpha build bug 

Linux 2.2.19pre16

[Alan Cox]

2.2.19pre16
o   Add Epson 1240 usb scanner id   (Joel Becker)
o   Starfire driver updates (Ion Badulescu)
o   Make xconfig fix(Craig Rogers)
o   Update credits for Richard Guenther (Richard Guenther)
o   strnlen_user fixups (Solar Designer)
o   Fix starfire netif_stop/start bug   (Ion Badulescu)
o   SIGIO from irq context fixes(Andi Kleen)

2.2.19pre15
o   Hugh Blemings has moved (Hugh Blemings)
o   Add support for usb hubs with many ports(Randy Dunlap)
o   Reapply make xconfig isdn fix   (Andrzej Krzysztofowicz)
o   Fix the tcp problems(Alexey Kuznetsov)
o   Kai Petzke has moved(Kai Petzke)
o   Add BUG() to S/390  (Ulrich Weigand)
o   Further S/390 fixes (Ulrich Weigand)
o   Add keventd from 2.4 to 2.2 (Ulrich Weigand)
| Needed for S/390 drivers
o   Remove dead isdn_init call  (Andrzej Krzysztofowicz)
o   Remove bogus aha1542/aha1740 sense check(Nick Holloway)
o   FPU emu fix (Ulrich Weigand)
o   EEpro100 posted writes fix  (Andrey Savochkin,
 Don Becker)

2.2.19pre14
o   Update slhc code for endianness (Dave Miller)
o   Update s390 dasd driver (Ulrich Weigand)
o   Allow more than 4K of partitions(Ulrich Weigand)
o   Fix check in sockfilter (Dave Miller)
o   Sparc updates (quad sbus sunhme detect, BUG())  (Dave Miller)
o   Fix hid locking and ston32 bugs (Paul Mackerras)
o   Update 3c59x drivers(Andrew Morton, Maciej Rozycki, 
 Fred Maciel, Georg Engstrand,
 Brett Frankenberger, Don Becker,
o   Fix a usb message   (Randy Dunlap)
o   Eicon driver updates(Armin Schindler)
o   Update 8139too driver   (Jens David)
o   Fix USB hub locks   (Paul Mackerras)
o   Fix missing keyspan config line (Paul Mackerras)
o   Merge S/390 bug fixes   (Ulrich Weigand)
o   Some S/390 cleanups (Ulrich Weigand)
o   Update S/390 ELF magic  (Ulrich Weigand)
o   Update hwc driver   (Ulrich Weigand)
o   Update ctc driver   (Ulrich Weigand)
o   Update iucv driver  (Ulrich Weigand)
o   S/390 warning fixes (Ulrich Weigand)

2.2.19pre13
o   Fix up missing bits of Soohoon Lee's exec patch (Michael Jaegerman)
| not sure where some bits of it escaped too...
o   Revert serial driver locking patch  (me)
| Seems to be causing crashes
o   PPC BUG(), and other compile fixes needed   (Benjamin Herrenschmidt)
o   ide_pmac_init to fix IDE probe power off(Benjamin Herrenschmidt)
o   atyfb128 and serial for pmac(Benjamin Herrenschmidt)
o   Workaround early imac firmware bug  (Benjamin Herrenschmidt)
o   Ensure task is running in mm faults (Roger Larsson)
| from 2.4
o   Fix nfs cache bug   (Neil Brown)
o   Further config.in cleanups/fixing   (Andrzej Krzysztofowicz)
o   Clean up tulip changes remove accidental fix(Jeff Garzik)
reversions
o   Update defconfig(Jeff Garzik)
o   Update usb printer driver in 2.2 to match 2.4   (Randy Dunlap)
o   Fix posix compliance on sockopts

2.2.19pre12
o   Update the DAC960 driver(Leonard Zubkoff)
o   Small PPC fixes (Benjamin Herrenschmidt)
o   Document irda options config(Steven Cole)
o   Small isdn fixes/obsolete code removal  (Kai Germaschewski)
o   Fix alpha kernel builds (Michal Jaegermann)
o   Update ver_linux to match the 2.4 one   (Steven Cole)
o   AVM isdn driver updates (Carsten Paeth)
o   ISDN capi/ppp fixes (Kai Germaschewski)

2.2.19pre11
o   Corrected version of ipc/shm.c fix  (Christoph Rohland)
o   Update/cleanup starfire (Ion Badulescu)
o   Update isdn makefiles   (Kai Germaschewski)
o   Eicon driver updates/new driver 

Re: Stale NFS handles on 2.4.2

[Neil Brown]

On Sunday February 25, [EMAIL PROTECTED] wrote:
> On Sun, Feb 25, 2001 at 08:25:10PM +1100, Neil Brown wrote:
> > On Saturday February 24, [EMAIL PROTECTED] wrote:
> > Verrry odd.  I can see why you were suspecting a cache.
> > I'm probably going to have to palm this off to Trond, the NFS client
> > maintainer (are you listening Trond?) but could please confirm that
> > from the client you can:
> > 
> >  1/ ping server
> >  2/ rpcinfo -p server
> >  3/ showmount -e server
> >  4/ mount server:/exported/filesys /some/other/mount/point
> > 
> > If all of these work, them I am mistified.  If one of these fails,
> > then that might point the way to further investigation.
> 
> I have server:/home mounted on /home, the directory /home/david is the
> mount file/directory on that mount that has a stale handle, everything
> else on that mount point works including accessing any file under
> /home/david.

So... you can access things under /home/david, but you cannot access
/home/david itself?
So, supposing that "fred" were some file that you happen to know is
in /home/david, then

ls /home/david fails with ESTALE and does not cause
   any traffic to the server and
ls -l /home/david/fred succeeds.

Is that right?

Could you try:
  echo 255 > /proc/sys/sunrpc/nfs_debug 

and then do the "ls /home/david" and see what gets put in 
/var/log/messages (or kern_log or syslog or where such things go).

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

Building autofs

[Rainer Mager]

Hi all,

I'm trying to use autofs for the first time and am running into some
problems. First,  the documentation seems quite weak, that is, I'm not sure
if what I have is what I should have. I managed to find an autofs version 4
pre 9 tarball on the kernel mirrors. This seem the latest but is still a bit
old and the referenced home page doesn't seem any newer. My real problem,
however, is that when I try to build it I get this error:

lookup_program.c:147: `OPEN_MAX' undeclared (first use in this function)

My understanding is that OPEN_MAX is defined in linux/limits.h but I
hesitate to change the code since I would expect this to build out of the
box.


Cas someone who is using autofs give me some pointers? Am I on the right
track?

Thanks,

--Rainer

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

Via-rhine is not finding its interrupts under 2.2.19pre14

[Michal Jaegermann]

After I booted 2.2.19pre14 on a system with two via-rhine cards I see the
following:

via-rhine.c:v1.08b-LK1.0.0 12/14/2000  Written by Donald Becker
  http://www.scyld.com/network/via-rhine.html
eth0: VIA VT3043 Rhine at 0x9400, 00:50:ba:c1:64:d9, IRQ 0.
eth0: MII PHY found at address 8, status 0x7809 advertising 05e1 Link .
eth1: VIA VT3043 Rhine at 0x8800, 00:50:ba:ab:60:64, IRQ 0.
eth1: MII PHY found at address 8, status 0x782d advertising 05e1 Link .

and a network does not work due to these IRQ 0, I guess.

In contrast when I will boot on the same hardware 2.4.2-ac5 then I get,
among other things,

via-rhine.c:v1.08b-LK1.1.7  8/9/2000  Written by Donald Becker
  http://www.scyld.com/network/via-rhine.html
PCI: Enabling device 00:09.0 (0094 -> 0097)
PCI: Found IRQ 9 for device 00:09.0
PCI: The same IRQ used for device 00:04.2
PCI: The same IRQ used for device 00:04.3
PCI: The same IRQ used for device 00:0d.0
eth0: VIA VT3043 Rhine at 0x9400, 00:50:ba:c1:64:d9, IRQ 9.
eth0: MII PHY found at address 8, status 0x7809 advertising 05e1 Link .
PCI: Enabling device 00:0c.0 (0094 -> 0097)
PCI: Found IRQ 11 for device 00:0c.0
eth1: VIA VT3043 Rhine at 0x8800, 00:50:ba:ab:60:64, IRQ 11.
eth1: MII PHY found at address 8, status 0x782d advertising 05e1 Link .


Devices in question can be seen here:

-[00]-+-00.0  VIA Technologies, Inc. VT8363/8365 [KT133/KM133]
  +-01.0-[01]00.0  ATI Technologies Inc Rage 128 RF
  +-04.0  VIA Technologies, Inc. VT82C686 [Apollo Super South]
  +-04.1  VIA Technologies, Inc. Bus Master IDE
  +-04.2  VIA Technologies, Inc. UHCI USB
  +-04.3  VIA Technologies, Inc. UHCI USB
  +-04.4  VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
  +-09.0  VIA Technologies, Inc. VT86C100A [Rhine 10/100]
  +-0a.0  Symbios Logic Inc. (formerly NCR) 53c810
  +-0c.0  VIA Technologies, Inc. VT86C100A [Rhine 10/100]
  +-0d.0  Ensoniq CT5880 [AudioPCI]
  \-11.0  Promise Technology, Inc. 20265


I do not have turned on a support for USB or audio in either of these
two kernels.  They are actually configured pretty similar (within a
reason :-).  But network is operational with 2.4.2-ac5.  Hm...

Even with these IRQ conflicts for eth0 one would think that eth1 should
get its interrupt.  It does not conflict with anything.  Forgotten
'pci_enable()' somewhere?

  Michal

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

Re: ISO-8859-1 completeness of kernel fonts?

[Andries . Brouwer]

>> kbd-1.05 comes with sun12x22.psfu, which essentially is the kernel font
>> together with a unimap.

> Note, that I also have a SuSE12x22 font, which is based on the Sun font,
> some charcaters slightly changed and added lots of 8859-1 symbols.
> Isn't it included in kbd-1.04 and later, Andries?

It may be that that is the one called sun12x22.psfu in kbd-1.05.
I think I first took your first version and later replaced it
with your latest version. Perhaps I did some work on it myself
as well, but maybe that was first for kbd-1.06. There was also
a Polish contribution for kbd-1.06, so the 1.06 version will have
a few more symbols, I think.

Andries

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

Re: 2.4 kernels - "attempt to access beyond end of device"

[Michal Jaegermann]

To add to my report about troubles with disk activity on a system with
PDC20265 IDE controller (this is on Asus AV7 mobo, BTW) I tried the
same experiments with 2.2.19pre14 patched with ide patches to get a
support for Promise.

I got similar results - i.e. problems after some 130-150 megabytes
was copied.  On different occasions I got things like that:

file_cluster badly computed!!! 0 <> 536870911
file_cluster badly computed!!! 1 <> 0

practically immediately and followed by a period of a lively disk
activity and a crash.

Whoops: end_buffer_io_async: b_count != 1 on async io.

after which 'cp' process hanged in a "D" state.

attempt to access beyond end of device
21:01: rw=0, want=537238629, limit=4506201
dev 21:01 blksize=512 blocknr=1074477258 sector=1074477258 size=512 count=1
...
(and more of these)  terminated with oops decoded below.

To take 'vfat' out of picture I also tried 'cp' from ext2 partitions
(I had to collect number of things as I do not have enough of data on
this system yet) to an ext2 partition while using 2.4.2-ac5.  This resulted
in:

EXT2-fs error (device ide3(34,9)): ext2_readdir: bad entry in
directory #16584: inode out of bounds - offset=0, inode=134234312,
rec_len=12, name_len=1
EXT2-fs error (device ide3(34,9)): ext2_readdir: bad entry in
directory #131542: inode out of bounds - offset=0, inode=134349270,
rec_len=12, name_len=1
EXT2-fs error (device ide3(34,9)): ext2_readdir: bad entry in
directory #82294: inode out of bounds - offset=0, inode=134300022,
rec_len=12, name_len=1
EXT2-fs error (device ide3(34,9)): ext2_readdir: bad entry in
directory #164456: inode out of bounds - offset=0, inode=134382184,
rec_len=12, name_len=1
EXT2-fs error (device ide3(34,9)): ext2_readdir: bad entry in
directory #98872: inode out of bounds - offset=0, inode=134316600,
rec_len=12, name_len=1
22:09: rw=0, want=537530884, limit=1574338
attempt to access beyond end of device
22:09: rw=0, want=537530884, limit=1574338
.
punctuated by oops.

Here is a decoded oops from 2.2.19pre14

Unable to handle kernel paging request at virtual address 0800
current->tss.cr3 = 1f052000, %cr3 = 1f052000
*pde = 1f67b067
Oops: 
CPU:0
EIP:0010:[]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010206
eax: 0800   ebx: 0007   ecx: 00053d24   edx: 0800
esi: 000d   edi: 2202   ebp: 0004906a   esp: de955e7c
ds: 0018   es: 0018   ss: 0018
Process cp (pid: 573, process nr: 19, stackpage=de955000)
Stack: 0004906a 2202 00053d24 c01277e8 2202 0004906a 0200  
   c0127b9a 2202 0004906a 0200  0004906a  ded6a200 
    c0145398 2202 0004906a 0200 c014a0db ded6a200 0004906a 
Call Trace: [] [] [] [] [] 
[] [] 
   [] [] [] 
Code: 8b 00 39 6a 04 75 15 8b 4c 24 20 39 4a 08 75 0c 66 39 7a 0c 

>>EIP; c01277a8<=
Trace; c01277e8 
Trace; c0127b9a 
Trace; c0145398 
Trace; c014a0db 
Trace; c0145b6c 
Trace; c014a26f 
Trace; c014784e 
Trace; c01262d9 
Trace; c01476d0 
Trace; c0109534 
Code;  c01277a8 
 <_EIP>:
Code;  c01277a8<=
   0:   8b 00 mov(%eax),%eax   <=
Code;  c01277aa 
   2:   39 6a 04  cmp%ebp,0x4(%edx)
Code;  c01277ad 
   5:   75 15 jne1c <_EIP+0x1c> c01277c4 
Code;  c01277af 
   7:   8b 4c 24 20   mov0x20(%esp,1),%ecx
Code;  c01277b3 
   b:   39 4a 08  cmp%ecx,0x8(%edx)
Code;  c01277b6 
   e:   75 0c jne1c <_EIP+0x1c> c01277c4 
Code;  c01277b8 
  10:   66 39 7a 0c   cmp%di,0xc(%edx)


And here is the one from ext2 to ext2 copy under 2.4.2-ac5

Unable to handle kernel paging request at virtual address ea096084
c0128edf
*pde = 
Oops: 
CPU:0
EIP:0010:[]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010003
eax: 081b   ebx: 081b   ecx: 0282   edx: ca096000
esi: dffd7cdc   edi:    ebp: 1000   esp: dec6de38
ds: 0018   es: 0018   ss: 0018
Process cp (pid: 543, stackpage=dec6d000)
Stack: 220a 0001220a 0286 0010 c17cb2e0  c0133314 dffd7cdc 
   0003 c17cb2e0  c01333d2 0001 0007ccfc  c0121be9 
   220a c17cb2e0 c17cb2e0 220a  c0133687 c17cb2e0 1000 
Call Trace: [] [] [] [] [] 
[] [] 
   [] [] [] [] [] [] 
Code: 8b 44 82 18 0f af 5e 0c 89 42 14 03 5a 0c 40 75 05 8b 02 89 

>>EIP; c0128edf<=
Trace; c0133314 
Trace; c01333d2 
Trace; c0121be9 
Trace; c0133687 
Trace; c01339ab <__block_prepare_write+4b/2b0>
Trace; c0123e8c 
Trace; c013423d 
Trace; c014ffb0 
Trace; c0126886 
Trace; c014ffb0 
Trace; c0124a70 
Trace; c0131468 
Trace; c01090a3 
Code;  c0128edf 
 <_EIP>:
Code;  c0128edf<=
   0:   8b 44 82 18   mov0x18(%edx,%eax,4),%eax   <=
Code;  c0128ee3 
   4:   0f af 5e 0c   imul   0xc(%esi),%ebx
Code;  c0128ee7 
   8:   89 42 14  mov%eax,0x14(%edx)

Re: timing out on a semaphore

[Davide Libenzi]

On 27-Feb-2001 Tim Waugh wrote:
> On Tue, Feb 27, 2001 at 10:40:35PM +, Andrew Morton wrote:
> 
>> 1: Your code is leaving the semaphore in a down'ed state
>>somehow.
> 
> This was probably it.  I don't know why it works for me but not some
> other people though. :-/

UP vs. MP ?



- Davide

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

Re: timing out on a semaphore

[Tim Waugh]

On Tue, Feb 27, 2001 at 10:40:35PM +, Andrew Morton wrote:

> 1: Your code is leaving the semaphore in a down'ed state
>somehow.

This was probably it.  I don't know why it works for me but not some
other people though. :-/

> (As you can tell, I'm desparately avoiding having
> to understand the semaphore code again :))

:-)

Tim.
*/

 PGP signature

Re: 2.2.18 IDE tape problem, with ide-scsi

[Khalid Aziz]

Andre Hedrick wrote:
> 
> Hi Khalid,
> 
> So, is HP going to allow linux to publsih "Tape Alert" as a means to
> assist with error checking and testing in general?  Also why did HP
> take the 14GB/20GB models and move off the standard QIC or TR-4
> IO-Firmware?
> 
> Cheers,
> 
> Andre Hedrick
> Linux ATA Development
> ASL Kernel Development

Hi Andre,

Unfortunately I am not in a position to know answers to these questions.
These questions would need to go way higher up than to a lowly software
engineer :-)

BTW, I am not familar with "Tape alert". Can you give me more info. A
private email might be more approrpiate. 

-- 
Khalid


Khalid Aziz Linux Development Laboratory
(970)898-9214Hewlett-Packard
[EMAIL PROTECTED]Fort Collins, CO
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [NFS] Updated patch for the [2.4.x] NFS 'missing directory entry a.k.a. IRIX server' problem...

[H . J . Lu]

On Tue, Feb 27, 2001 at 03:04:32PM -0800, H . J . Lu wrote:
> > entry->prev_cookie = entry->cookie;
> > -   p = xdr_decode_hyper(p, >cookie);
> > +   p = xdr_decode_hyper(p, cookie);
> > +   entry->cookie = nfs_transform_cookie64(cookie);
> 
> I don't understand this. As far as I can tell, "cookie" is not
> initialized at all. Even if it is initialized, what does
> 
>   p = xdr_decode_hyper(p, cookie);
> 

Trond, I think you missed

p = xdr_decode_hyper(p, );
^

Yes, it does seem to work.


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

Re: binfmt_script and ^M

[David]

Alistair Riddell wrote:

> On Tue, 27 Feb 2001, Heusden, Folkert van wrote:
> 
>> But; it's not that much of hassle to run it trough some awk/sed/whatsoever
>> script, would it? Imho there should be as less as possible code in the
> 
> 
> man fromdos (on most linux systems anyway)
> 

tr -d '\r' < infile > outfile

We wouldn't make the kernel translate m$ word docs into files the kernel 
can parse.  It's a userland thing and changing the kernel would change a 
legacy that would cause a lot of confusion I would expect.

-d

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

Re: 3c59x new version, help me please with the new kernels

[Andrew Morton]

Mario Vanoni wrote:
> 
> PCI 3COM 3C905B COMBO Etherlink XL 10/100Mbit BNC+RJ-45
> running a LAN with 3 machines 10MB with BNC/RG-58U cable.
> 

Which interface do you actually want to use?  BNC?

Try `options=3'.

If that doesn't work, please send me (off-list) the log
output from the driver when it is loaded an opened
with the `debug=4' module parm.


I suspect what has happened is this:  in older kernels,
the interface selection code would try different interfaces
even if the user has selected, say, 10baseT.  This was causing
the driver to select 10base2 when the RJ45 is unplugged. It
gets stuck there, necessitating a reboot or driver reload.
So I changed the driver so that if the user says 10baseT,
we unconditionally _use_ 10baseT, dammit.

The module option (and patch) which you've been using
were relying on the old behaviour - they select the
10baseT interface.  This interface doesn't have link beat,
so the driver tries 10base2 and all is happy.

Using `options=3' will select 10base2 immediately. For the
non-modular case you'll need to use the `ether=' LILO option.

hmm..  In fact, you shouldn't need any option for 10base2 - perhaps
your EEPROM doesn't have the correct "available media" info.  Please
send me the output of `vortex-diag -aaee' - http://www.scyld.com/diag/#pci-diags

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

Re: ISO-8859-1 completeness of kernel fonts?

[Kurt Garloff]

On Tue, Feb 27, 2001 at 08:58:37PM +0100, Guest section DW wrote:
> On Tue, Feb 27, 2001 at 09:37:55AM -0800, H. Peter Anvin wrote:
> 
> > You're much better off designing a larger ISO-8859-1 font and load in in
> > user space.  You can use the 12x22 font in the kernel as a base.
> 
> kbd-1.05 comes with sun12x22.psfu, which essentially is the kernel font
> together with a unimap.

Note, that I also have a SuSE12x22 font, which is based on the Sun font,
some charcaters slightly changed and added lots of 8859-1 symbols.
Isn't it included in kbd-1.04 and later, Andries?

I also have a patch to make it available for the kernel ...
http://www.garloff.de/kurt/linux/

Regards,
-- 
Kurt Garloff   <[EMAIL PROTECTED]> [Eindhoven, NL]
Physics: Plasma simulations  <[EMAIL PROTECTED]>  [TU Eindhoven, NL]
Linux: SCSI, Security  <[EMAIL PROTECTED]>   [SuSE Nuernberg, FRG]
 (See mail header or public key servers for PGP2 and GPG public keys.)

 PGP signature

Re: [OT] Re: binfmt_script and ^M

[Jamie Lokier]

Tim Waugh wrote:
> > Isn't `perl' overkill?  Why not just:
> > 
> > tr -d '\r'
> 
> while read line; do echo ${line%?}; done

And those can be convert a set of files as "fromdos *.c" can they?

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

Re: Promise Ultra100 IDE PDC20265 chip problem

[Richard B. Johnson]

On Tue, 27 Feb 2001 [EMAIL PROTECTED] wrote:

> 
> (I am not subscribed to this list, if it is in fact a list. Please CC any
> replies to me directly - Thanks)
> 

If you are, in fact, I suggest you contact RedHat.

> hde: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=32885055, sector=0
  
This is something that windows has been hiding from you.


Cheers,
Dick Johnson

Penguin : Linux version 2.4.1 on an i686 machine (799.53 BogoMips).

"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.


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

Re: Announce: modutils 2.4.3 is available

[Kurt Garloff]

On Tue, Feb 27, 2001 at 09:41:26AM +1100, Keith Owens wrote:
> On Mon, 26 Feb 2001 11:08:59 +0100, 
> Stefan Smietanowski <[EMAIL PROTECTED]> wrote:
> >Keith Owens wrote
> >> modutils-2.4.3.tar.gz   Source tarball, includes RPM spec file
> >
> >IIRC 2.4.2 was 2.4 only, and was released under protest, is it the same
> >for 2.4.3?
> 
> modutils 2.4 will work on kernel 2.0 and libc 5, one of the changes in
> 2.4.3 is for libc5 support.  The protest period has expired.

To clearify: The incompatibility only affects the hotplug kernel device
tables ... 
As there was no support amongst USB crowds for adding a version info for the
table formats, the modutils-2.4.2 could not provide support for per 2.4.0
kernel hotplug device tables. Nor can 2.4.3. The rest of the functionality
is unaffected.
Keith, correct me if I misunderstood ...

Regards,
-- 
Kurt Garloff  <[EMAIL PROTECTED]>  Eindhoven, NL
GPG key: See mail header, key servers Linux kernel development
SuSE GmbH, Nuernberg, FRG   SCSI, Security

 PGP signature

Re: rsync over ssh on 2.4.2 to 2.2.18

[Eugene Crosser]

In article <[EMAIL PROTECTED]>,
Russell King <[EMAIL PROTECTED]> writes:

> I'm seeing odd behaviour with rsync over ssh between two x86 machines -

I've seen hanging rsync over ssh more than once, while sending much data
from an x86 running Linux (late 2.3.x) to Sparc/Solaris2.5.1 over ssh
1.2.26.  I had a feeling that it was triggered by certain data patterns
because it often stopped at the same spot after restart (and therefore
I attributed it to a bug in rsync).  I did not investigate further.

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

Re: [NFS] Updated patch for the [2.4.x] NFS 'missing directory entry a.k.a. IRIX server' problem...

[H . J . Lu]

On Thu, Feb 22, 2001 at 03:48:50PM +0100, Trond Myklebust wrote:
> 
> The above fixes should ensure that all cookies taking values between 0
> and (2^32-1) on the NFS server are preserved through the 32-bit VFS
> interface, and are accepted by glibc as valid entries. It should also
> work fine with existing 64-bit architectures.
> 
> Please could people give this a try, and report if it fixes the
> problems.

Have you tried it against a Linux NFS V3 server? When I log in
with my home directory mounted from a Linux NFS V3 server, I
got kernel oops when I do

# cat /proc/mounts

I think the problem may be cookie transform thing.

> --- linux-2.4.2-fh_align/fs/nfs/nfs3xdr.c Fri Feb  9 20:29:44 2001
> +++ linux-2.4.2-dir/fs/nfs/nfs3xdr.c  Thu Feb 22 10:47:49 2001
> @@ -523,6 +523,13 @@
>   return 0;
>  }
>  
> +/* Hack to sign-extending 32-bit cookies */
> +static inline
> +u64 nfs_transform_cookie64(u64 cookie)
> +{
> + return (cookie & 0x8000) ? (cookie ^ 0x) : cookie;
> +}
> +
>  /*
>   * Encode arguments to readdir call
>   */
> @@ -533,7 +540,7 @@
>   int buflen, replen;
>  
>   p = xdr_encode_fhandle(p, args->fh);
> - p = xdr_encode_hyper(p, args->cookie);
> + p = xdr_encode_hyper(p, nfs_transform_cookie64(args->cookie));
>   *p++ = args->verf[0];
>   *p++ = args->verf[1];
>   if (args->plus) {
> @@ -635,6 +642,7 @@
>  nfs3_decode_dirent(u32 *p, struct nfs_entry *entry, int plus)
>  {
>   struct nfs_entry old = *entry;
> + u64 cookie;
>  
>   if (!*p++) {
>   if (!*p)
> @@ -648,7 +656,8 @@
>   entry->name = (const char *) p;
>   p += XDR_QUADLEN(entry->len);
>   entry->prev_cookie = entry->cookie;
> - p = xdr_decode_hyper(p, >cookie);
> + p = xdr_decode_hyper(p, cookie);
> + entry->cookie = nfs_transform_cookie64(cookie);

I don't understand this. As far as I can tell, "cookie" is not
initialized at all. Even if it is initialized, what does

p = xdr_decode_hyper(p, cookie);

do?


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

Re: Wine + kernel ?? How to do that?

[Dan Kegel]

[EMAIL PROTECTED] asked:
> hey, I hear that wine ( windows emulator ) can port into kernel and make 
> it running faster, How can I do it? 
> or anyone can make a patch to add wine code into kernel? 
> waiting for answer, Thanks 

It's not ready for prime time yet.

There is some discussion of the issues at 
  news://news.winehq.com/wine.devel 

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

Re: [patch][rfc][rft] vm throughput 2.4.2-ac4

[Marcelo Tosatti]

On Tue, 27 Feb 2001, Mike Galbraith wrote:

> On Tue, 27 Feb 2001, Rik van Riel wrote:
> 
> > On Tue, 27 Feb 2001, Mike Galbraith wrote:
> >
> > > Attempting to avoid doing I/O has been harmful to throughput here
> > > ever since the queueing/elevator woes were fixed. Ever since then,
> > > tossing attempts at avoidance has improved throughput markedly.
> > >
> > > IMHO, any patch which claims to improve throughput via code deletion
> > > should be worth a little eyeball time.. and maybe even a test run ;-)
> > >
> > > Comments welcome.
> >
> > Before even thinking about testing this thing, I'd like to
> > see some (detailed?) explanation from you why exactly you
> > think the changes in this patch are good and how + why they
> > work.
> 
> Ok.. quite reasonable ;-)
> 
> First and foremost:  What does refill_inactive_scan do?  It places
> work to do on a list.. and nothing more.  It frees no memory in and
> of itself.. none (but we count it as freed.. that's important). It
> is the amount of memory we want desperately to free in the immediate
> future.  We count on it getting freed.  The only way to free I/O bound
> memory is to do the I/O.. as fast as the I/O subsystem can sync it.
> 
> This is the nut.. scan/deactivate percentages are fairly meaningless
> unless we do something about these pages.
> 
> What the patch does is simply to push I/O as fast as we can.. we're
> by definition I/O bound and _can't_ defer it under any circumstance,
> for in this direction lies constipation.  The only thing in the world
> which will make it better is pushing I/O.

In your I/O bound case, yes. But not in all cases.

> If you test the patch, you'll notice one very important thing.  The
> system no longer over-reacts.. as badly.  That's a diagnostic point.
> (On my system under my favorite page turnover rate load, I see my box
> drowning in a pool of dirty pages.. which it's not allowed to drain)
> 
> What we do right now (as kswapd) is scan a tiny portion of the active
> page list, and then push an arbitrary amount of swap because we can't
> possibly deactivate enough pages if our shortage is larger than the
> search area (nr_active_pages >> 6).. repeat until give-up time.  In
> practice here (test load, but still..), that leads to pushing soon
> to be unneeded [supposition!] pages into swap a full 3/4 of the time.

Have you tried to use SWAP_SHIFT as 4 instead of 5 on a stock 2.4.2-ac5 to
see if the system still swaps out too much?

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

Re: CLOCAL and TIOCMIWAIT

[Theodore Y. Ts'o]

   Date:Mon, 26 Feb 2001 22:19:20 -0500
   From: Jeremy Jackson <[EMAIL PROTECTED]>

   I had written a simple program 10-20 lines C to count pulses at rate
   of 1 per second give or take.  It turned out that the driver disabled
   the UART's generation of interrupts completely for certain signals.
   I don't remember which exactly, but I think it was DCD; I was using
   CLOCAL so the hangups wouldn't close the descriptor.  The problems
   was that by disabling the interrupt at the source, the ioctl's to
   read the bits stopped working!  not what I wanted.

This was a bug which was fixed for 2.2 in the 8250/16550 serial driver;
CLOCAL should change the behaviour open/close/hangup processing, as per
POSIX, but it shouldn't change the behaviour of TIOCMIWAIT or TIOCMGET.

   > My question is: what's the correct interpretation of CLOCAL?? If the
   > serial driver's interpretation is the correct one, I'll be more than happy
   > to change the Cyclades' driver to comply with that, I just want to make
   > sure that this is the expected behavior before I patch the driver.

CLOCAL's behaviour is defined under POSIX, although the behaviour of
TIOCMIWAIT and TIOMGET aren't.  So one could make the argument that 
(to use Al Gore's words) there "no controlling legal authority" saying
that an implementation where TIOCMIWAIT depending on CLOCAL being clear
is illegal or violates some standard.  However, it seems downright silly.

So I would argue that it would be better to make things consistent by
making CLOCAL only affect those things which are specifically specified
by POSIX.1, and not make it affect the behaviour of TIOCMIWAIT and
TIOCMGET, et. al.

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

Re: rsync over ssh on 2.4.2 to 2.2.18

[Russell King]

[EMAIL PROTECTED] writes:
> Moreover, even not _one_ wakeup is missing. At least two, because
> wakeups in read and write are separate and you have stuck in both directions.
> 8)8)

I'll see if I can strace it from the start until it hangs tomorrow.

> Well, if it was one I would start to dig ground inside tcp instantly.
> But as soon as two of them are missing, I have to suspect wake_up itself.
> At least, we had such bugs there until 2.4.0.

I was running at one point a 2.4.0-test kernel, but I didn't see these
effects back then (but then I wasn't monitoring the system as closely as
I am at the moment).

--
Russell King ([EMAIL PROTECTED])The developer of ARM Linux
 http://www.arm.linux.org.uk/personal/aboutme.html

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

Promise Ultra100 IDE PDC20265 chip problem

[Peter . Havens]

(I am not subscribed to this list, if it is in fact a list. Please CC any
replies to me directly - Thanks)

I am attempting to install the new beta release of Red Hat (fisher) on my
home computer. It has an Asus A7V motherboard and a Promise Ultra100 IDE
controller (PDC20265 chip), with two partitions. Windows ME is installed in
the first partition. The second one is where I'm attempting to install Red
Hat.

In previous releases of the Linux kernel, my hard drive was not seen at all.
I could go all the way up to the point in the Red Hat installation where it
wanted to do disk geometry, and then said that I didn't have any mass media
device. Searching through various mail archives lead me to believe the
culprit was the PDC20265 controller chip and the fact that it was too new to
be recognized.

In the new kernel 2.4.0 (and thereby the fisher release of Red Hat), I now
see the error below printed out to the console when booting from the Red Hat
installation floppy. After the error is printed out, my computer hangs. I
apologize in advance if this is not a Linux kernel issue, and appreciate any
help that can be provided.

--Pete

[snip]

PDC 20265: chipset revision 2
PDC 20265: not 100% native mode: will probe irqs later

[snip]

Partition Check:
hde: [PTBL] [1826/255/63] hde1 hde2 < hde5hde: dma_intr: status=0x51 {
DriveReady SeekComplete Error }
hde: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=32885055, sector=0
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }

[last repeats 3-4 times]

hde: DMA disabled

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

Re: Will Mosix go into the standard kernel?

[zbrown]

argh. OK

On Tue, Feb 27, 2001 at 01:56:25PM -0800, Zack Brown wrote:
> Do the Mosix folks have anything to add about possible integration into the
> kernel? (should have cced them earlier, but it slipped my mind)
> 
>  On Tue, 27 Feb 2001, David L. Nicol wrote:
> 
> > Zack Brown wrote:
> > > 
> > > Just curious, are there any plans to put Mosix into the standard kernel,
> > > maybe in 2.5, so folks could just configure it and go? it seems that the
> > > number of people with more than one computer might make this a feature many
> > > would at least want to try, especially if it was available as an option by
> > > default. Is there anything in the Mosix folks' implementation that would
> > > prevent this?
> > 
> > I'm not a knowledgeable person, but I've been following Mosix/beowulf/? for
> > a few years and trying to keep up.
> > 
> > I've thought that it would be good to break up the different clustering
> > frills -- node identification, process migration, process hosting, distributed
> > memory, yadda yadda blah, into separate bite-sized portions.  
> > 
> > Centralization would be good for standardizing on what /proc/?/?/? you read to
> > find out what clusters you are in, and whatis your node number there.  There
> > is a lot of theorhetical work to be done.
> > 
> > Until then, I don't expect to see the Complete Mosix Patch Set available
> > from ftp.kernel.org in its current form, as a monolithic set that does many things,
> > including its Very Own Distributed File System Architecture.
> > 
> > If any of the work from Mosix will make it Into The Standard Kernel it will be
> > by backporting and standardization.
> > 
> > 
> > Is there a good list to discuss this on?  Is this the list?  Which pieces of
> > clustering-scheme patches would be good to have? 
> > 
> > I think a good place to start would be node numbering.
> > 
> > The standard node numbering would need to be flexible enough to have one machine
> > participating in multiple clusters at the same time.
> > 
> > /proc/cluster/  this would be standard root point for clustering stuff
> > 
> > /proc/mosix would go away, become proc/cluster/mosix
> > 
> > and the same with whatever bproc puts into /proc; that stuff would move to
> > /proc/cluster/bproc
> > 
> > 
> > Or, the status quo will endure, with cluster hackers playing catch-up.
> 
> On Tue, 27 Feb 2001, Alexander Viro wrote:
> 
> |
> |#include 
> |
> |Guys, if you want a large subtree in /proc - whack yourself over the head
> |until you realize that you want an fs of your own. I'll be more than
> |happy to help with both parts.
> 
> Rik van Riel said:
> 
> > I know each of the cluster projects have mailing lists, but
> > I've never heard of a list where the different projects come
> > together to eg. find out which parts of the infrastructure
> > they could share, or ...
> > 
> > Since I agree with you that we need such a place, I've just
> > created a mailing list:
> > 
> > [EMAIL PROTECTED]
> > 
> > To subscribe to the list, send an email with the text
> > "subscribe linux-cluster" to:
> > 
> > [EMAIL PROTECTED]
> > 
> > 
> > I hope that we'll be able to split out some infrastructure
> > stuff from the different cluster projects and we'll be able
> > to put cluster support into the kernel in such a way that
> > we won't have to make the choice which of the N+1 cluster
> > projects should make it into the kernel...
> 
> 
> 
> -- 
> Zack Brown
> 
> 
> 
> 
> 
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

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

Re: timing out on a semaphore

[Andrew Morton]

Tim Waugh wrote:
> 
> On Sun, Feb 25, 2001 at 11:10:39PM +, Andrew Morton wrote:
> 
> > I think there might be a bogon in __down_interruptible's
> > handling of the semaphore state in this case.  I remember
> > spotting something a few months back but I can't immediately
> > remember what it was :(
> >
> > I'd suggest you slot a
> >
> >   sema_init(>physport->ieee1284.irq, 1);
> >
> > into parport_wait_event() prior to adding the timer.  If that
> > fixes it I'll go back through my patchpile, see if I can
> > resurrect that grey cell.
> 
> I haven't been able to confirm that it works around it (can't repeat
> the problem here), but what would you say if I said it did? ;-)

One of two things:

1: Your code is leaving the semaphore in a down'ed state
   somehow.

2: The semaphore code is leaving the semaphore in a funny
   state.

hmm.  I see from your other email that the sema_init() has 
made the problem go away.  Could you please review the code,
see if there's an imbalance somewhere?

What is parport_ieee1284_write_compat() trying to do with
the semaphore?  It will leave the semaphore in a downed
state.  Intentional?  Is this code actually being used
by the person who is having the problem?  Could this
loop be replaced by a simple sema_init()?

(As you can tell, I'm desparately avoiding having
to understand the semaphore code again :))

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

Re: Will Mosix go into the standard kernel?

[J . A . Magallon]

On 02.27 Zack Brown wrote:
> Do the Mosix folks have anything to add about possible integration into the
> kernel? (should have cced them earlier, but it slipped my mind)
> 

And also beowulf people, [EMAIL PROTECTED]

-- 
J.A. Magallon  $> cd pub
mailto:[EMAIL PROTECTED]  $> more beer

Linux werewolf 2.4.2-ac5 #1 SMP Tue Feb 27 01:09:47 CET 2001 i686

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

Re: 2.2.18 IDE tape problem, with ide-scsi

[Alan Cox]

> Wish i knew, I'm praying that 2.2.19 hasn't/doesn't implement the ide patches like 
>2.4.x did.  If so, and a major problem is found in
> 2.2.18, then I have to maintain another machine running 2.2.18 to restore tapes.  
>Also means i'd have to stop using taper or dump,
> and stick to tar only, as both want to read the tape back in at some point.

2.2 isnt likely to ever see the IDE patches as standard.

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

Re: Will Mosix go into the standard kernel?

[Zack Brown]

Do the Mosix folks have anything to add about possible integration into the
kernel? (should have cced them earlier, but it slipped my mind)

 On Tue, 27 Feb 2001, David L. Nicol wrote:

> Zack Brown wrote:
> > 
> > Just curious, are there any plans to put Mosix into the standard kernel,
> > maybe in 2.5, so folks could just configure it and go? it seems that the
> > number of people with more than one computer might make this a feature many
> > would at least want to try, especially if it was available as an option by
> > default. Is there anything in the Mosix folks' implementation that would
> > prevent this?
> 
> I'm not a knowledgeable person, but I've been following Mosix/beowulf/? for
> a few years and trying to keep up.
> 
> I've thought that it would be good to break up the different clustering
> frills -- node identification, process migration, process hosting, distributed
> memory, yadda yadda blah, into separate bite-sized portions.  
> 
> Centralization would be good for standardizing on what /proc/?/?/? you read to
> find out what clusters you are in, and whatis your node number there.  There
> is a lot of theorhetical work to be done.
> 
> Until then, I don't expect to see the Complete Mosix Patch Set available
> from ftp.kernel.org in its current form, as a monolithic set that does many things,
> including its Very Own Distributed File System Architecture.
> 
> If any of the work from Mosix will make it Into The Standard Kernel it will be
> by backporting and standardization.
> 
> 
> Is there a good list to discuss this on?  Is this the list?  Which pieces of
> clustering-scheme patches would be good to have? 
> 
> I think a good place to start would be node numbering.
> 
> The standard node numbering would need to be flexible enough to have one machine
> participating in multiple clusters at the same time.
> 
> /proc/cluster/this would be standard root point for clustering stuff
> 
> /proc/mosix would go away, become proc/cluster/mosix
> 
> and the same with whatever bproc puts into /proc; that stuff would move to
> /proc/cluster/bproc
> 
> 
> Or, the status quo will endure, with cluster hackers playing catch-up.

On Tue, 27 Feb 2001, Alexander Viro wrote:

|
|#include 
|
|Guys, if you want a large subtree in /proc - whack yourself over the head
|until you realize that you want an fs of your own. I'll be more than
|happy to help with both parts.

Rik van Riel said:

> I know each of the cluster projects have mailing lists, but
> I've never heard of a list where the different projects come
> together to eg. find out which parts of the infrastructure
> they could share, or ...
> 
> Since I agree with you that we need such a place, I've just
> created a mailing list:
> 
> [EMAIL PROTECTED]
> 
> To subscribe to the list, send an email with the text
> "subscribe linux-cluster" to:
> 
> [EMAIL PROTECTED]
> 
> 
> I hope that we'll be able to split out some infrastructure
> stuff from the different cluster projects and we'll be able
> to put cluster support into the kernel in such a way that
> we won't have to make the choice which of the N+1 cluster
> projects should make it into the kernel...



-- 
Zack Brown







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

[patch] 2.4.2: irq-driven lp stalls

[Tim Waugh]

Hi Linus,

This patch seems to cure some printing stalls that some people have
been seeing.  The down_trylock call isn't really needed there anyway.

Please apply.

Tim.
*/

2001-02-27  Tim Waugh  <[EMAIL PROTECTED]>

* drivers/parport/ieee1284_ops.c: Remove down_trylock call,
which seems to prevent stalls.
* drivers/parport/ChangeLog: Updated.

--- linux/drivers/parport/ieee1284_ops.c.sema   Tue Feb 27 21:43:49 2001
+++ linux/drivers/parport/ieee1284_ops.cTue Feb 27 21:44:16 2001
@@ -50,9 +50,6 @@
if (port->irq != PARPORT_IRQ_NONE) {
parport_enable_irq (port);
no_irq = 0;
-
-   /* Clear out previous irqs. */
-   while (!down_trylock (>physport->ieee1284.irq));
}
 
port->physport->ieee1284.phase = IEEE1284_PH_FWD_DATA;
--- linux/drivers/parport/ChangeLog.semaTue Feb 27 21:44:21 2001
+++ linux/drivers/parport/ChangeLog Tue Feb 27 21:45:43 2001
@@ -0,0 +1,7 @@
+2001-02-27  Tim Waugh  <[EMAIL PROTECTED]>
+
+   * ieee1284_ops.c (parport_ieee1284_write_compat): Don't use
+   down_trylock to reset the IRQ count.  Don't even use sema_init,
+   because it's not even necessary to reset the count.  I can't
+   remember why we ever did.
+
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [patch] patch-2.4.2-irda1 (irda-usb)

[Greg KH]

On Tue, Feb 27, 2001 at 08:32:28PM +, Dag Brattli wrote:
> > I'd recommend that this file be in the /drivers/usb directory, much like
> > almost all other USB drivers are.
> 
> Yes, but do we want to spread the IrDA code around? The same argument
> applies to IrDA device drivers!?

I agree, and am not saying that it _has_ to be there.  Just a
suggestion, and if you're comfortable with it in the irda directory,
that's fine.

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]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [ANOMALIES]: 2.4.2 - __alloc_pages: failed - Causes more thenjust msgs

[Shawn Starr]

When added with BUG(); it will hang /dev/dsp.

I'm not sure if it did without it. I'll be restarting with the removed
BUG(); soon.

On Tue, 27 Feb 2001, Mike Galbraith wrote:

> On Mon, 26 Feb 2001, Shawn Starr wrote:
>
> > It may not be an important message but what does happen is /dev/dsp becomes
> > hung and no sound works after the fault. So something is definately wrong.
>
> Do you mean it hangs without the BUG() inserted, or only after the oops?
>
>   -Mike
>
>
>

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

Re: Will Mosix go into the standard kernel?

[Rik van Riel]

On Tue, 27 Feb 2001, David L. Nicol wrote:

> I've thought that it would be good to break up the different
> clustering frills -- node identification, process migration,
> process hosting, distributed memory, yadda yadda blah, into
> separate bite-sized portions.

It would also be good to share parts of the infrastructure
between the different clustering architectures ...

> Is there a good list to discuss this on?  Is this the list?
> Which pieces of clustering-scheme patches would be good to have?

I know each of the cluster projects have mailing lists, but
I've never heard of a list where the different projects come
together to eg. find out which parts of the infrastructure
they could share, or ...

Since I agree with you that we need such a place, I've just
created a mailing list:

[EMAIL PROTECTED]

To subscribe to the list, send an email with the text
"subscribe linux-cluster" to:

[EMAIL PROTECTED]


I hope that we'll be able to split out some infrastructure
stuff from the different cluster projects and we'll be able
to put cluster support into the kernel in such a way that
we won't have to make the choice which of the N+1 cluster
projects should make it into the kernel...

regards,

Rik
--
Linux MM bugzilla: http://linux-mm.org/bugzilla.shtml

Virtual memory is like a game you can't win;
However, without VM there's truly nothing to lose...

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

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

Re: ISO-8859-1 completeness of kernel fonts?

[Mack Stevenson]

Thank you for your help; I'll try to use a psf editor on the Sun 12x22 font 
in the new kbd package.

Cheers,

Mack
_
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

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

[OT] Re: binfmt_script and ^M

[Tim Waugh]

On Tue, Feb 27, 2001 at 12:59:48PM -0700, Don Dugger wrote:

> Isn't `perl' overkill?  Why not just:
> 
>   tr -d '\r'

while read line; do echo ${line%?}; done
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Will Mosix go into the standard kernel?

[Alexander Viro]

On Tue, 27 Feb 2001, David L. Nicol wrote:

> /proc/cluster/this would be standard root point for clustering stuff
> 
> /proc/mosix would go away, become proc/cluster/mosix
> 
> and the same with whatever bproc puts into /proc; that stuff would move to
> /proc/cluster/bproc

#include 

Guys, if you want a large subtree in /proc - whack yourself over the head
until you realize that you want an fs of your own. I'll be more than
happy to help with both parts.

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

Re: binfmt_script and ^M

[Rogier Wolff]

Ivo Timmermans wrote:
> Heusden, Folkert van wrote:
> > > When running a script (perl in this case) that has DOS-style newlines
> > > (\r\n), Linux 2.4.2 can't find an interpreter because it doesn't
> > > recognize the \r.  The following patch should fix this (untested).
> > 
> > _should_ it work with the \r in it?
> 
> IMHO, yes.  This set of files were created on Windows, then zipped and
> uploaded to a Linux server, unpacked.  This does not change the \r.

Use the right option on "unzip" to unpack with cr/lf conversion.

Otherwise, use a script that does it afterwards. 

Roger.

-- 
** [EMAIL PROTECTED] ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots. 
* There are also old, bald pilots. 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[patch] patch-2.4.2-irda4 (misc fixes 2nd part)

[Dag Brattli]

Linus,

These are various irda patches (2nd part) to fix various bit of the stack. Please
apply to your latest Linux-2.4.2 code. Changes:

o Fix socket stuck in CONN_PEND
o NSC wakeup fix
o Fix for IrDA stack static init

diff -u -p linux/net/irda/irlmp_event.d7.c linux/net/irda/irlmp_event.c
--- linux/net/irda/irlmp_event.d7.c Tue Feb 20 14:14:33 2001
+++ linux/net/irda/irlmp_event.cTue Feb 20 14:41:31 2001
@@ -472,8 +472,6 @@ static int irlmp_state_disconnected(stru
irlmp_start_watchdog_timer(self, 5*HZ);
break;
case LM_CONNECT_INDICATION:
-   irlmp_next_lsap_state(self, LSAP_CONNECT_PEND);
-
if (self->conn_skb) {
WARNING(__FUNCTION__ 
"(), busy with another request!\n");
@@ -481,6 +479,8 @@ static int irlmp_state_disconnected(stru
}
self->conn_skb = skb;
 
+   irlmp_next_lsap_state(self, LSAP_CONNECT_PEND);
+
irlmp_do_lap_event(self->lap, LM_LAP_CONNECT_REQUEST, NULL);
break;
default:
@@ -562,6 +562,15 @@ static int irlmp_state_connect_pend(stru
switch (event) {
case LM_CONNECT_REQUEST:
/* Keep state */
+   break;
+   case LM_CONNECT_INDICATION:
+   /* Will happen in some rare cases when the socket get stuck,
+* the other side retries the connect request.
+* We just unstuck the socket - Jean II */
+   IRDA_DEBUG(0, __FUNCTION__ "(), LM_CONNECT_INDICATION, "
+  "LSAP stuck in CONNECT_PEND state...\n");
+   /* Keep state */
+   irlmp_do_lap_event(self->lap, LM_LAP_CONNECT_REQUEST, NULL);
break;
case LM_CONNECT_RESPONSE:
IRDA_DEBUG(0, __FUNCTION__ "(), LM_CONNECT_RESPONSE, "

diff -u -p linux/drivers/net/irda/nsc-ircc.j1.c linux/drivers/net/irda/nsc-ircc.c
--- linux/drivers/net/irda/nsc-ircc.j1.cFri Feb 23 15:56:05 2001
+++ linux/drivers/net/irda/nsc-ircc.c   Fri Feb 23 16:01:20 2001
@@ -251,9 +251,14 @@ static int nsc_ircc_open(int i, chipio_t
 
IRDA_DEBUG(2, __FUNCTION__ "()\n");
 
+   MESSAGE("%s, Found chip at base=0x%03x\n", driver_name,
+   info->cfg_base);
+
if ((nsc_ircc_setup(info)) == -1)
return -1;
 
+   MESSAGE("%s, driver loaded (Dag Brattli)\n", driver_name);
+
/* Allocate new instance of the driver */
self = kmalloc(sizeof(struct nsc_ircc_cb), GFP_KERNEL);
if (self == NULL) {
@@ -699,8 +704,6 @@ static int nsc_ircc_setup(chipio_t *info
ERROR("%s, Wrong chip version %02x\n", driver_name, version);
return -1;
}
-   MESSAGE("%s, Found chip at base=0x%03x\n", driver_name, 
-   info->cfg_base);
 
/* Switch to advanced mode */
switch_bank(iobase, BANK2);
@@ -729,8 +732,6 @@ static int nsc_ircc_setup(chipio_t *info
outb(0x0d, iobase+2); /* Set SIR pulse width to 1.6us */
outb(0x2a, iobase+4); /* Set beginning frag, and preamble length */
 
-   MESSAGE("%s, driver loaded (Dag Brattli)\n", driver_name);
-
/* Enable receive interrupts */
switch_bank(iobase, BANK0);
outb(IER_RXHDL_IE, iobase+IER);
@@ -1859,7 +1860,7 @@ static int nsc_ircc_net_open(struct net_
if (request_dma(self->io.dma, dev->name)) {
WARNING("%s, unable to allocate dma=%d\n", driver_name, 
self->io.dma);
-   free_irq(self->io.irq, self);
+   free_irq(self->io.irq, dev);
return -EAGAIN;
}

@@ -2011,18 +2012,10 @@ static void nsc_ircc_suspend(struct nsc_
 
 static void nsc_ircc_wakeup(struct nsc_ircc_cb *self)
 {
-   int iobase;
-
if (!self->io.suspended)
return;
 
-   iobase = self->io.fir_base;
-
-   /* Switch to advanced mode */
-   switch_bank(iobase, BANK2);
-   outb(ECR1_EXT_SL, iobase+ECR1);
-   switch_bank(iobase, BANK0);
-
+   nsc_ircc_setup(>io);
nsc_ircc_net_open(self->netdev);

MESSAGE("%s, Waking up\n", driver_name);

diff -urpN linux-2.4.1-pre8/init/main.c linux-2.4.1-pre8-irda-patch/init/main.c
--- linux-2.4.1-pre8/init/main.cThu Jan  4 05:45:26 2001
+++ linux-2.4.1-pre8-irda-patch/init/main.c Mon Jan 22 00:53:49 2001
@@ -726,6 +726,7 @@ static void __init do_basic_setup(void)
filesystem_setup();
 
 #ifdef CONFIG_IRDA
+   irda_proto_init();
irda_device_init(); /* Must be done after protocol initialization */
 #endif
 #ifdef CONFIG_PCMCIA




Dag Brattli <[EMAIL PROTECTED]>
My homepage http://www.brattli.net/dag/
Try Linux-IrDA: http://irda.sourceforge.net/
Try Pygmy:  http://pygmy.sourceforge.net/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message 

Re: [patch][rfc][rft] vm throughput 2.4.2-ac4

[Mike Galbraith]

On Tue, 27 Feb 2001, Rik van Riel wrote:

> On Tue, 27 Feb 2001, Mike Galbraith wrote:
>
> > Attempting to avoid doing I/O has been harmful to throughput here
> > ever since the queueing/elevator woes were fixed. Ever since then,
> > tossing attempts at avoidance has improved throughput markedly.
> >
> > IMHO, any patch which claims to improve throughput via code deletion
> > should be worth a little eyeball time.. and maybe even a test run ;-)
> >
> > Comments welcome.
>
> Before even thinking about testing this thing, I'd like to
> see some (detailed?) explanation from you why exactly you
> think the changes in this patch are good and how + why they
> work.

Ok.. quite reasonable ;-)

First and foremost:  What does refill_inactive_scan do?  It places
work to do on a list.. and nothing more.  It frees no memory in and
of itself.. none (but we count it as freed.. that's important). It
is the amount of memory we want desperately to free in the immediate
future.  We count on it getting freed.  The only way to free I/O bound
memory is to do the I/O.. as fast as the I/O subsystem can sync it.

This is the nut.. scan/deactivate percentages are fairly meaningless
unless we do something about these pages.

What the patch does is simply to push I/O as fast as we can.. we're
by definition I/O bound and _can't_ defer it under any circumstance,
for in this direction lies constipation.  The only thing in the world
which will make it better is pushing I/O.

If you test the patch, you'll notice one very important thing.  The
system no longer over-reacts.. as badly.  That's a diagnostic point.
(On my system under my favorite page turnover rate load, I see my box
drowning in a pool of dirty pages.. which it's not allowed to drain)

What we do right now (as kswapd) is scan a tiny portion of the active
page list, and then push an arbitrary amount of swap because we can't
possibly deactivate enough pages if our shortage is larger than the
search area (nr_active_pages >> 6).. repeat until give-up time.  In
practice here (test load, but still..), that leads to pushing soon
to be unneeded [supposition!] pages into swap a full 3/4 of the time.

> IMHO it would be good to not apply ANY code to the stable
> kernel tree unless we understand what it does and what the
> author meant the code to do...

Yes.. I agree 100%.  I was not suggesting that this be blindly
integrated.  (I know me.. can get all cornfoosed and fsck up;)

-Mike

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

another Linux-2.4.2 splat: *** target pattern contains no `%'. Stop.

[David L. Nicol]

[david@nicol1 linux]$ make dep

make[3]: Entering directory `/mnt/sdb2/src/linux-2.4.2/drivers'
make -C acpi fastdep
make[4]: Entering directory `/mnt/sdb2/src/linux-2.4.2/drivers/acpi'
Makefile:29: *** target pattern contains no `%'.  Stop.
make[4]: Leaving directory `/mnt/sdb2/src/linux-2.4.2/drivers/acpi'
make[3]: *** [_sfdep_acpi] Error 2
make[3]: Leaving directory `/mnt/sdb2/src/linux-2.4.2/drivers'
make[2]: *** [fastdep] Error 2
make[2]: Leaving directory `/mnt/sdb2/src/linux-2.4.2/drivers'
make[1]: *** [_sfdep_drivers] Error 2
make[1]: Leaving directory `/mnt/sdb2/src/linux-2.4.2'
make: *** [dep-files] Error 2

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

3c59x new version, help me please with the new kernels

[Mario Vanoni]

PCI 3COM 3C905B COMBO Etherlink XL 10/100Mbit BNC+RJ-45
running a LAN with 3 machines 10MB with BNC/RG-58U cable.

2.2.12 ... 2.2.19pre7aa1 no problems,

kernel with modules, /etc/modules.conf:
alias eth0 3c59x
options 3x59x options=0

kernel _without_ modules, my usual and preferred mode,
with the following little patch from Andrea
in /usr/src/linux/drivers/net/3c59x.c, original:
static int options[MAX_UNITS] = { -1, -1, -1, -1, -1, -1, -1, -1,};
always manually changed to:
static int options[MAX_UNITS];

booting message without modules:

eth0: 3Com 3c905B Cyclone 10/100/BNC at 0xa000,  00:50:04:9b:f0:b8 IRQ11
  8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface.
  Media override to transceiver type 0 (10baseT)
  Enabling bus-master transmits and whole-frame receives.
(the 1st line after 00:50 ... is different on all 3 machines!)

Works since over an year perfectly.
---

2.2.19pre15aa1 (same effect with 2.4.2pre?):

neither telnet nor mount -t nfs work,
rebooting to 2.2.19pre7aa1, _all_ works always perfectly.

Checked with 3c59x as module, without modules,
with/without Andrea's change, rien ne va plus.

gcc-2.95.3.test3, all kernels since test1 compiled with in
/usr/src/linux/arch/i386/Makefile:
ifdef CONFIG_M686
CFLAGS := ... -march=i686 ... in place of -m486
(stolen from 2.4.2pre?)

All machines PIII550, 2 UP's 512MB mem, 1 SMP Dual 1024MB.
glib-2.1.3
base old SuSE 6.4 with many updgrades via sources
*.tar.gz/*tar.bz2, never with rpm!

Not in lkml, CC if necessary.

I will do every test is needed/requested !!!

Regards and many thanks
Mario

PS Why _all_ machines swap copying 545MB, 5 files ~115MB,
   from a mounted /cdrom to /tmp?  With the newest kernels!
   AT SVR2...3.2 in over 12 years newer swapped with cp(1).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Will Mosix go into the standard kernel?

[David L. Nicol]

Zack Brown wrote:
> 
> Just curious, are there any plans to put Mosix into the standard kernel,
> maybe in 2.5, so folks could just configure it and go? it seems that the
> number of people with more than one computer might make this a feature many
> would at least want to try, especially if it was available as an option by
> default. Is there anything in the Mosix folks' implementation that would
> prevent this?

I'm not a knowledgeable person, but I've been following Mosix/beowulf/? for
a few years and trying to keep up.

I've thought that it would be good to break up the different clustering
frills -- node identification, process migration, process hosting, distributed
memory, yadda yadda blah, into separate bite-sized portions.  

Centralization would be good for standardizing on what /proc/?/?/? you read to
find out what clusters you are in, and whatis your node number there.  There
is a lot of theorhetical work to be done.

Until then, I don't expect to see the Complete Mosix Patch Set available
from ftp.kernel.org in its current form, as a monolithic set that does many things,
including its Very Own Distributed File System Architecture.

If any of the work from Mosix will make it Into The Standard Kernel it will be
by backporting and standardization.


Is there a good list to discuss this on?  Is this the list?  Which pieces of
clustering-scheme patches would be good to have? 

I think a good place to start would be node numbering.

The standard node numbering would need to be flexible enough to have one machine
participating in multiple clusters at the same time.

/proc/cluster/  this would be standard root point for clustering stuff

/proc/mosix would go away, become proc/cluster/mosix

and the same with whatever bproc puts into /proc; that stuff would move to
/proc/cluster/bproc


Or, the status quo will endure, with cluster hackers playing catch-up.




-- 
  David Nicol 816.235.1187 [EMAIL PROTECTED]
 "Americans are a passive lot, content to let so-called
  experts run our lives" -- Dr. Science

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

Re: ISO-8859-1 completeness of kernel fonts?

[H. Peter Anvin]

Thorsten Glaser Geuer wrote:
> 
> I always do it by a BASIC programme under DOS (yep I know
> this isn't pure but I have a font editor from S-DOS aka
> PTS-DOS (the free version)). The SFE.COM allows me to design
> 8x8 8x12 8x14 8x16 fonts; the unicode table I write in the
> MC or VC (NC clone for DOS) editor; my BASIC pgm converts
> them together to PSFU. It's very easy once you read the psf
> docs.
> It's a pity that I've to mkfs the DOS partitions of my HDDs
> every handfull of weeks, otherwise I'd put them onto a ftp
> server somewhere. But I call you to try it by yourself.
> (perl prolly isn't that easy coz it goes to binary values,
> but GW-BASIC is fine)
> 

I published a DOS-based PSF editor a long, long time ago (look for
fontedit.exe; if it isn't on the net anywhere remind me and I'll put it
back up.)  Use psfaddtable then to combine it into PSFU.

However, having something running under Linux would make more sense.

-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]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] quick reboot on i386

[Oswald Buddenhagen]

> > remember quarterdeck's quickreboot from "good" (*cough*) old D{o|O}S
> > days? here it is for linux! it's only of limited use, especially
> > in it's current state, but some people might find it useful.
> 
> Hmm, I'm probably going to apply this one, as I hate behaviour of my
> bios: if you power off during POST it will not come up next time
> asking for you to adjust CPU frequency.
> 
"nice" bios ... :-/
so now pray, that your hardware configuration allows a second boot
without being reset. (yes, this is the downside of qreboot).
to make it work always, we would need a "deep" reset of at least the 
pci and isa-pnp busses, presumably a chipset reset. sadly, i have
no idea, how to do this. possibly this would require an additional
reset function for every chipset. anyone can add something useful here?

best regards

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
--
Nothing is fool-proof to a sufficiently talented fool.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Linux Socket Filter sudden CPU use increase

[Eduardo Magaña Lizarrondo]

I have been testing Linux Socket Filters (LSF) these weeks (kernels
2.2.12,
2.2.14, 2.2.18, 2.4.1) with libpcap (0.4 - 0.6.2) and I have observed 
something curious. I make a program that increase number of simultaneous 
LSF filters (5, 10, 15..) and when this number is between 15 and 50,
suddenly
CPU consumed by kernel increases suddenly. Any idea? 
(you can see a figure of CPU vs. number of LSF filter in 
http://www.tlm.unavarra.es/~eduardo/varios/lsf.gif)

I do not see anything stranger. Only, using Linux Trace Toolkit with
some 
modifications when there are few filters, I observe that of timer Bottom
Half 
follows IRQ 0. And when there are more filters, IRQ 0 takes place when
the 
network Bottom Half is taking place, so the timer Bottom Half is delayed
to
the end of the network Bottom Half. Can it be related?

To measure kernel CPU I have used the trick of running another CPU with
low 
priority. According to the time this second process is delayed an
aproximate 
%CPU is obtained.

I do not understand what is happening. Any help would be very useful.

Eduardo

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

Re: Compilation problems

[Brian Gerst]

Rob wrote:
> 
> gcc --version gives me pgcc-2.91.66
> 
> I have a bootable 2.2.4 kernel I just can no longer recompile it for some
> reason.

IIRC, pgcc is known to be broken.  Use standard gcc 2.91.66 or later.

--

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

Re: nfs_refresh_inode ?

[Trond Myklebust]

> " " == Zdravko Spoljar <[EMAIL PROTECTED]> writes:

 > Hi i'm running 2.2.19pre14+RAID+ide and get this message from
 > kernel:

 > nfs_refresh_inode: inode number mismatch expected
 > (0x0/0x0), got (0x0002b0001/0x5605)
 >

Could you get a tcpdump of a the traffic when this happens? I suspect
a server bug.

 > marked numbers vary from message to message. i can triger this
 > by doing "make test;chmod 777 test" on some nfs mounted file
 > sistem some times repeated chmod generate more messages,
 > sometimes are executed ok. i have feeling it happend more often
 > when there is some cpu and net load.


 > linux nfs client is dual pentium II (266) on P2B-DS with 2
 > promise IDE cards, net card is smc (using realtek 8139 driver),
 > ide and scsi disks are in RAID 5 setup.

 > nfs server is Apple Network server running AIX4.1.5 net conn is
 > 100MB over Cisco switch

 > ah, there is one more thing. on boot when nfs get mounted i
 > find in dmesg: "nfs warning: mount version older than kernel"
 > WTF? :)

It means that your 'mount' program is too old, and so you won't be
able to mount NFSv3 partitions.

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

Re: rsync over ssh on 2.4.2 to 2.2.18

[Russell King]

David S. Miller writes:
> How do you know this?  There are so many deadly TCP bugs fixed
> since 2.2.15pre13 I don't know how you can assert this.

Through the evidence I gave.  

Firstly, if the receiving side is saying that it has a window of 0, then
it is not going to accept any more data.

Secondly, the receiving side has data waiting in the receive queue.

Thirdly, the receiving process is selecting on the socket, and dispite
there being data waiting, select is saying that there is no data waiting.

All the data is pointing at the 2.4 kernel as being the culprit.

I'm surprised at your response given the amount of hard evidence I gave that
supports my assertion.

--
Russell King ([EMAIL PROTECTED])The developer of ARM Linux
 http://www.arm.linux.org.uk/personal/aboutme.html

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

Re: rsync over ssh on 2.4.2 to 2.2.18

[kuznet]

Hello!

> netstat on isdn-gw shows the following:
> 
>   Proto Recv-Q Send-Q Local Address   Foreign Address State
>   tcp72868  0 isdn-gw.piltdown.a:1023 pilt-gw.piltdown.at:ssh ESTABLISHED
plus
> select(4, [3], [3], NULL, NULL) = 2 (in [3], out [3])


> Maybe there is a race condition or missing wakeup in the TCP code?

Moreover, even not _one_ wakeup is missing. At least two, because
wakeups in read and write are separate and you have stuck in both directions.
8)8)

Well, if it was one I would start to dig ground inside tcp instantly.
But as soon as two of them are missing, I have to suspect wake_up itself.
At least, we had such bugs there until 2.4.0.

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

Re: [PATCH] quick reboot on i386

[Pavel Machek]

Hi!

> remember quarterdeck's quickreboot from "good" (*cough*) old D{o|O}S
> days? here it is for linux! it's only of limited use, especially
> in it's current state, but some people might find it useful.

Hmm, I'm probably going to apply this one, as I hate behaviour of my
bios: if you power off during POST it will not come up next time
asking for you to adjust CPU frequency.
Pavel
-- 
I'm [EMAIL PROTECTED] "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.2.18 IDE tape problem, with ide-scsi

[Andre Hedrick]

Hi Khalid,

So, is HP going to allow linux to publsih "Tape Alert" as a means to
assist with error checking and testing in general?  Also why did HP
take the 14GB/20GB models and move off the standard QIC or TR-4
IO-Firmware?

Cheers,

Andre Hedrick
Linux ATA Development
ASL Kernel Development
-
ASL, Inc. Toll free: 1-877-ASL-3535
1757 Houret Court Fax: 1-408-941-2071
Milpitas, CA 95035Web: www.aslab.com

On Tue, 27 Feb 2001, Khalid Aziz wrote:

> Camm Maguire wrote:
> > 
> > Greetings!  OK, with st debugging, here are the most common errors
> > with the Conner:
> > 
> > Feb 27 14:46:39 intech9 kernel: st0: Error: 2800, cmd: 8 1 0 0 40 0 Len: 16
> > Feb 27 14:46:39 intech9 kernel: Info fld=0x24, Current st09:00: sns = f0  8
> > Feb 27 14:46:39 intech9 kernel: ASC=14 ASCQ= 3
> > Feb 27 14:46:39 intech9 kernel: Raw sense data:0xf0 0x00 0x08 0x00 0x00 0x00 0x24 
>0x0a 0x00 0x00 0x00 0x00 0x14 0x03 0x00 0x00
> > Feb 27 14:46:39 intech9 kernel: st0: Sense: f0  0  8  0  0  0 24  a
> > Feb 27 14:46:39 intech9 kernel: st0: Tape error while reading.
> 
> This was a read command that failed. Request sense information shows a
> sense key of 0x08 which is a "Blank check". This sense key indicates
> either a blank medium found or another error at EOD. ASC/ASCQ of
> 0x14/0x03 say "End-Of-Data not found". This indicates something wrong
> with the tape or maybe the drive needs cleaning. Do you get this error
> with more than one tape?
> 
> 
> > Feb 27 14:46:40 intech9 kernel: st0: Error: 2800, cmd: 5 0 0 0 0 0 Len: 16
> > Feb 27 14:46:40 intech9 kernel: [valid=0] Info fld=0x0, Current st09:00: sns = 70  
>5
> > Feb 27 14:46:40 intech9 kernel: ASC=20 ASCQ= 0
> > Feb 27 14:46:40 intech9 kernel: Raw sense data:0x70 0x00 0x05 0x00 0x00 0x00 0x00 
>0x0a 0x00 0x00 0x00 0x00 0x20 0x00 0x00 0x00
> > Feb 27 14:46:40 intech9 kernel: st0: Can't read block limits.
> 
> This was a "Read Block Limits" command which the drive claimed it does
> not recognize. "Read Block Limits" is a mandatory command for SCSI
> sequential access devices which is why "st" is issuing this command. The
> tape drive you have is not SCSI, so the manufacturer chose not to
> implement this command. The driver may still be able to work after "Read
> Block Limits" fails, but I have not read enough code to be sure.
> 
> > Feb 27 14:46:40 intech9 kernel: st0: Mode sense. Length 11, medium b6, WBS 10, BLL 
>8
> > Feb 27 14:46:40 intech9 kernel: st0: Density 45, tape length: 0, drv buffer: 1
> > Feb 27 14:46:40 intech9 kernel: st0: Block size: 512, buffer size: 32768 (64 
>blocks).
> > 
> > Any advice appreciated!
> 
> 
> Khalid Aziz Linux Development Laboratory
> (970)898-9214Hewlett-Packard
> [EMAIL PROTECTED]Fort Collins, CO

Andre Hedrick
Linux ATA Development
ASL Kernel Development
-
ASL, Inc. Toll free: 1-877-ASL-3535
1757 Houret Court Fax: 1-408-941-2071
Milpitas, CA 95035Web: www.aslab.com

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

èÏÔÉÔÅÓÔÁÔØÄÉÐÌÏÍÁÔÏÍ?èÏÔÉÔÅÉÍÅÔØÄÉÐÌÏÍÁÔÉÞÅÓËÉÊÓÔÁÔÕÓ?ôÏÇÄÁÜÔÏÉÍÅÎÎÏÔÏ,ÞÔÏ÷ÁÍÎÅÏÂÈÏÄÉÍÏ.(ðÉÓØÍÏ). Email, 095-7059285#92889

[Serg]

õ×ÁÖÁÅÍÙÅ ÇÏÓÐÏÄÁ.

ðÒÉÎÏÓÉÍ Ó×ÏÉ ÉÚ×ÉÎÅÎÉÑ ÚÁ ×ÍÅÛÁÔÅÌØÓÔ×Ï × ÷ÁÛÅ ÜÌÅËÔÒÏÎÎÏÅ ÐÒÏÓÔÒÁÎÓÔ×Ï, ÎÏ ÷ÁÛ 
ÜÌÅËÔÒÏÎÎÙÊ ÁÄÒÅÓ ÂÙÌ ×ÚÑÔ ÉÚ ÏÔËÒÙÔÙÈ ÉÓÔÏÞÎÉËÏ×. äÁÎÎÁÑ ÒÁÓÓÙÌËÁ ÎÏÓÉÔ ÉÓËÌÀÞÉÔÅÌØÎÏ 
ÒÁÚÏ×ÙÊ ÈÁÒÁËÔÅÒ É ÂÏÌÅÅ ÐÏ×ÔÏÒÑÔØÓÑ ÎÅ ÂÕÄÅÔ.

ðÒÅÄÌÁÇÁÅÍ Ë ÐÒÉÏÂÒÅÔÅÎÉÀ óÁÍÏÅ ÐÏÌÎÏÅ É ÍÁËÓÉÍÁÌØÎÏ ÐÏÄÒÏÂÎÏÅ ÒÕËÏ×ÏÄÓÔ×Ï:

"îÅÔÒÁÄÉÃÉÏÎÎÙÊ ÐÕÔØ ÐÏÌÕÞÅÎÉÑ ÄÉÐÌÏÍÁÔÉÞÅÓËÏÇÏ ÓÔÁÔÕÓÁ"

äÁÎÎÏÅ ÒÕËÏ×ÏÄÓÔ×Ï ÂÙÌÏ ÉÚÄÁÎÏ × ìÏÎÄÏÎÅ áÎÇÌÉÊÓËÏÊ áÄ×ÏËÁÔÓËÏÊ ëÏÍÐÁÎÉÅÊ, ÂÏÌÅÅ 
ÎÉËÏÇÄÁ É 
ÎÉÇÄÅ ÎÅ ÉÚÄÁ×ÁÌÁÓØ É ÎÅ ÐÅÒÅÉÚÄÁ×ÁÌÁÓØ.

äÁÎÎÏÅ ÉÚÄÁÎÉÅ ÓÏÄÅÒÖÉÔ ÐÏÄÒÏÂÎÅÊÛÉÅ ÉÎÓÔÒÕËÃÉÉ, ÐÏÒÑÄÏË ÄÅÊÓÔ×ÉÊ, ÏÂÒÁÚÃÙ ÐÉÓÅÍ É 
ÄÏËÕÍÅÎÔÏ×, ÚÁËÏÎÏÄÁÔÅÌØÎÙÅ ÁËÔÙ.

÷ÓÑ ÉÎÆÏÒÍÁÃÉÑ ÎÅÏÄÎÏËÒÁÔÎÏ ÐÒÏ×ÅÒÅÎÁ É ÏÔÎÏÓÉÔÓÑ ÁÂÓÏÌÀÄÎÏ ËÏ ×ÓÅÍ, ÎÉ ÇÒÁÖÄÁÎÓÔ×Ï, 
ÎÉ 
ÐÒÏÐÉÓËÁ, ÎÉËÁËÉÅ ÉÎÙÅ ÄÁÎÎÙÅ ÐÒÉÎÃÉÐÉÁÌØÎÏÇÏ ÚÎÁÞÅÎÉÑ ÎÅ ÉÍÅÀÔ.

âÏÌÅÅ ÐÏÄÒÏÂÎÏÊ É ÔÏÞÎÏÊ ÉÎÆÏÒÍÁÃÉÉ ÷Ù ÎÅ ÓÍÏÖÅÔÅ ÂÏÌÅÅ ÎÁÊÔÉ ÎÉÇÄÅ.

ñÚÙË ÒÕËÏ×ÏÄÓÔ×Á ÒÕÓÓËÉÊ ÉÌÉ ÁÎÇÌÉÊÓËÉÊ ÐÏ ÷ÁÛÅÍÕ ×ÙÂÏÒÕ.

÷ÁÒÉÁÎÔÙ:

- Ô×ÅÒÄÙÊ ÐÅÒÅÐÌÅÔ-  50 Õ.Å.
- ÍÑÇËÉÊ ÐÅÒÅÐÌÅÔ -   40 Õ.Å.
- ÜÌÅËÔÒÏÎÎÁÑ ×ÅÒÓÉÑ - 30 Õ.Å.

äÏÓÔÁ×ËÁ:  îÁÌÏÖÎÙÊ ÐÌÁÔÅÖ; á×ÁÎÓÏ×ÙÊ ÐÌÁÔÅÖ; ëÕÒØÅÒÓËÁÑ.

óÔÏÉÍÏÓÔØ ÄÏÓÔÁ×ËÉ ÐÏ íÏÓË×Å É íÏÓËÏ×ÓËÏÊ ÏÂÌÁÓÔÉ ×ÈÏÄÉÔ × ÓÔÏÉÍÏÓÔØ(ËÒÏÍÅ ËÕÒØÅÒÓËÏÊ).

óËÉÄËÉ:
- ÏÔ 10 ÜËÚ. - 10%
- ÏÔ 25 ÜËÚ. - 15%
- ÏÔ 50 ÜËÚ. - 20%
- Á×ÁÎÓÏ×ÙÊ ÐÌÁÔÅÖ - 10%.

ïÂÒÁÝÁÊÔÅÓØ. íÙ ÖÄÅÍ ÷ÁÓ!

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

Re: Compilation problems

[Richard B. Johnson]

On Tue, 27 Feb 2001, Rob wrote:

> Hi, I've encountered a problem compiling the 2.4.2 kernel.
> 
> I downloaded the source, did a make menuconfig, make dep, make bzImage;
> everything went ok, but I didn't have the NIC working correctly. I
> recompiled, it seemed to go ok but still the NIC didn't work.  Then I
> tried make clean, make mrproper, make menuconfig, make dep, make bzImage,
> and now I keep getting an error at the very end of the compile process...
> 
> init/main.o(.text.init+0x53): undefined reference to
> `__buggy_fxsr_alignment'
> make: ***[vmlinux] Error 1
> 

You need to upgrade your binutils or 'C' compiler. This is a forced error
caused by task struct member, 'thread.i387.fxsave' not being aligned on a
16-byte boundary.  In the meantime, you could actually create a global
function in main.c and see if the machine runs.

__buggy_fxsr_alignment(){}


Cheers,
Dick Johnson

Penguin : Linux version 2.4.1 on an i686 machine (799.53 BogoMips).

"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.


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

Re: Compilation problems

[Brian Gerst]

Rob wrote:
> 
> Hi, I've encountered a problem compiling the 2.4.2 kernel.
> 
> I downloaded the source, did a make menuconfig, make dep, make bzImage;
> everything went ok, but I didn't have the NIC working correctly. I
> recompiled, it seemed to go ok but still the NIC didn't work.  Then I
> tried make clean, make mrproper, make menuconfig, make dep, make bzImage,
> and now I keep getting an error at the very end of the compile process...
> 
> init/main.o(.text.init+0x53): undefined reference to
> `__buggy_fxsr_alignment'
> make: ***[vmlinux] Error 1
> 
> I've even tried removing the source tree and re extracting from the tar
> ball again but it always stops at the same place now.  If you have any
> ideas, please let me know.  I'm not a member of the list so a cc would
> really be great.

GCC version?

--

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

Re: 2.2.18 IDE tape problem, with ide-scsi

[Khalid Aziz]

Camm Maguire wrote:
> 
> Greetings!  OK, with st debugging, here are the most common errors
> with the Conner:
> 
> Feb 27 14:46:39 intech9 kernel: st0: Error: 2800, cmd: 8 1 0 0 40 0 Len: 16
> Feb 27 14:46:39 intech9 kernel: Info fld=0x24, Current st09:00: sns = f0  8
> Feb 27 14:46:39 intech9 kernel: ASC=14 ASCQ= 3
> Feb 27 14:46:39 intech9 kernel: Raw sense data:0xf0 0x00 0x08 0x00 0x00 0x00 0x24 
>0x0a 0x00 0x00 0x00 0x00 0x14 0x03 0x00 0x00
> Feb 27 14:46:39 intech9 kernel: st0: Sense: f0  0  8  0  0  0 24  a
> Feb 27 14:46:39 intech9 kernel: st0: Tape error while reading.

This was a read command that failed. Request sense information shows a
sense key of 0x08 which is a "Blank check". This sense key indicates
either a blank medium found or another error at EOD. ASC/ASCQ of
0x14/0x03 say "End-Of-Data not found". This indicates something wrong
with the tape or maybe the drive needs cleaning. Do you get this error
with more than one tape?


> Feb 27 14:46:40 intech9 kernel: st0: Error: 2800, cmd: 5 0 0 0 0 0 Len: 16
> Feb 27 14:46:40 intech9 kernel: [valid=0] Info fld=0x0, Current st09:00: sns = 70  5
> Feb 27 14:46:40 intech9 kernel: ASC=20 ASCQ= 0
> Feb 27 14:46:40 intech9 kernel: Raw sense data:0x70 0x00 0x05 0x00 0x00 0x00 0x00 
>0x0a 0x00 0x00 0x00 0x00 0x20 0x00 0x00 0x00
> Feb 27 14:46:40 intech9 kernel: st0: Can't read block limits.

This was a "Read Block Limits" command which the drive claimed it does
not recognize. "Read Block Limits" is a mandatory command for SCSI
sequential access devices which is why "st" is issuing this command. The
tape drive you have is not SCSI, so the manufacturer chose not to
implement this command. The driver may still be able to work after "Read
Block Limits" fails, but I have not read enough code to be sure.

> Feb 27 14:46:40 intech9 kernel: st0: Mode sense. Length 11, medium b6, WBS 10, BLL 8
> Feb 27 14:46:40 intech9 kernel: st0: Density 45, tape length: 0, drv buffer: 1
> Feb 27 14:46:40 intech9 kernel: st0: Block size: 512, buffer size: 32768 (64 blocks).
> 
> Any advice appreciated!


Khalid Aziz Linux Development Laboratory
(970)898-9214Hewlett-Packard
[EMAIL PROTECTED]Fort Collins, CO
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [patch] patch-2.4.2-irda1 (irda-usb)

[Dag Brattli]

On Tue, 27 Feb 2001 09:33:29 -0800, Greg KH wrote:
> On Tue, Feb 27, 2001 at 08:29:03AM +, Dag Brattli wrote:
> > Linus,
> > 
> > Please apply this patch to your latest Linux-2.4.2 source. Changes:
> > 
> > o IrDA-USB dongle support [new feature]
> 
> I'd recommend that this file be in the /drivers/usb directory, much like
> almost all other USB drivers are.

Yes, but do we want to spread the IrDA code around? The same argument
applies to IrDA device drivers!?

> > +/* These are the currently known IrDA USB dongles. Add new dongles here */
> > +struct irda_usb_dongle dongles[] = { /* idVendor, idProduct, idCapability */
> > +   /* ACTiSYS Corp,  ACT-IR2000U FIR-USB Adapter */
> > +   { 0x9c4, 0x011, IUC_SPEED_BUG | IUC_NO_WINDOW },
> > +   /* KC Technology Inc.,  KC-180 USB IrDA Device */
> > +   { 0x50f, 0x180, IUC_SPEED_BUG | IUC_NO_WINDOW },
> > +   /* Extended Systems, Inc.,  XTNDAccess IrDA USB (ESI-9685) */
> > +   { 0x8e9, 0x100, IUC_SPEED_BUG | IUC_NO_WINDOW },
> > +   { 0, 0, 0 }, /* The end */
> > +};
> 
> You should also probably add the following snippet to allow the USB
> hotplug functionality to work properly:
> 
> static __devinitdata struct usb_device_id id_table [] = {
> { USB_DEVICE(0x09c4, 0x0011) },
> { USB_DEVICE(0x050f, 0x0180) },
> { USB_DEVICE(0x08e9, 0x0100) },
> { } /* Terminating entry */
> };
> MODULE_DEVICE_TABLE (usb, id_table);  

OK!

> If IRDA has a class descriptor, can't you just rely on that, and not
> have to worry about the individual device vendor and product ids?

Sorry, some of the dongles don't follow the spec fully, as you can see from
our table. Actually none of them follow the spec, since they are all based
on the same chip which was made before the spec was finished. But there 
should be a new dongle out now which do follow the spec (but we haven't 
got hold of it yet)

> 
> > + * This routine is called by the USB subsystem for each new device
> > + * in the system. We need to check if the device is ours, and in
> > + * this case start handling it.
> > + * Note : it might be worth protecting this function by a global
> > + * spinlock...
> > +static void *irda_usb_probe(struct usb_device *dev, unsigned int ifnum,
> > +  const struct usb_device_id *id)
> 
> A spinlock is not needed as the probe functions are called sequentially.
> 
> thanks,
> 
> greg k-h


Dag Brattli <[EMAIL PROTECTED]>
My homepage http://www.brattli.net/dag/
Try Linux-IrDA: http://irda.sourceforge.net/
Try Pygmy:  http://pygmy.sourceforge.net/

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

Re: binfmt_script and ^M

[Don Dugger]

Isn't `perl' overkill?  Why not just:

tr -d '\r'

On Tue, Feb 27, 2001 at 08:20:59PM +0100, Jamie Lokier wrote:
> Ivo Timmermans wrote:
> > > _should_ it work with the \r in it?
> > 
> > IMHO, yes.  This set of files were created on Windows, then zipped and
> > uploaded to a Linux server, unpacked.  This does not change the \r.
> 
> Use `fromdos' to convert the files.  Or this little Perl gem, which
> takes a list of files or standard input as argument:
> 
> #!/usr/bin/perl -pi
> s/\r\n$/\n/
> 
> -- Jamie
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
[EMAIL PROTECTED]
Ph: 303/938-9838
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH][CFT] per-process namespaces for Linux

[Alexander Viro]

New version uploaded on ftp.math.psu.edu/pub/viro/namespaces-d-S2.gz

Changes:
* fixed an idiotic bug in get_filesystem_info() that din't 
unfortunately) show up on UP.
* nosuid/nodev/noexec work in any combinations (had been b0rken in
previous version).
* fixed multiple-mount (had been b0rken; --bind worked, but attempt
to mount the device you've already had mounted did bad things).
* sanity checks for mount --move were missing. Fixed.
* Assorted cleanups.

Folks, please help with testing.
Cheers,
Al

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

Re: ISO-8859-1 completeness of kernel fonts?

[Thorsten Glaser Geuer]

- Original Message - 
From: "H. Peter Anvin" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 27, 2001 7:49 PM
Subject: Re: ISO-8859-1 completeness of kernel fonts?


> Followup to:  <01c0a0ed$1ea188d0$[EMAIL PROTECTED]>
> By author:"Thorsten Glaser Geuer" <[EMAIL PROTECTED]>
> In newsgroup: linux.dev.kernel
> > 
> > My second suggestion: code it as .psfu and load it by setfont, including
> > the appropiate console-map. AFAIK all the kernel default fonts are cp437
> > (linux/drivers/char/cp437.uni; consolemap.*)
> > 
> 
> Something that would be really good is if someone could contribute PSF
> (v1 and v2) support for gfe 
> or some other free font editor.
> 
> -hpa

I always do it by a BASIC programme under DOS (yep I know
this isn't pure but I have a font editor from S-DOS aka
PTS-DOS (the free version)). The SFE.COM allows me to design
8x8 8x12 8x14 8x16 fonts; the unicode table I write in the
MC or VC (NC clone for DOS) editor; my BASIC pgm converts
them together to PSFU. It's very easy once you read the psf
docs.
It's a pity that I've to mkfs the DOS partitions of my HDDs
every handfull of weeks, otherwise I'd put them onto a ftp
server somewhere. But I call you to try it by yourself.
(perl prolly isn't that easy coz it goes to binary values,
but GW-BASIC is fine)

-mirabilos


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

Compilation problems

[Rob]

Hi, I've encountered a problem compiling the 2.4.2 kernel.

I downloaded the source, did a make menuconfig, make dep, make bzImage;
everything went ok, but I didn't have the NIC working correctly. I
recompiled, it seemed to go ok but still the NIC didn't work.  Then I
tried make clean, make mrproper, make menuconfig, make dep, make bzImage,
and now I keep getting an error at the very end of the compile process...

init/main.o(.text.init+0x53): undefined reference to
`__buggy_fxsr_alignment'
make: ***[vmlinux] Error 1

I've even tried removing the source tree and re extracting from the tar
ball again but it always stops at the same place now.  If you have any
ideas, please let me know.  I'm not a member of the list so a cc would
really be great.

-- 
Rob Connor
TWR Communications
301 777 2692 x131
[EMAIL PROTECTED]

Good judgement comes from experience, and experience -
well, that comes from poor judgement.


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

Disk change messages

[Petr Konecny]

Hi,

I've been trying to use vold to automount CDs. The daemon tries to open
/dev/cdrom and if it succeeds it examines the media and mounts it under
/cdrom/volume_name.

The problem is that when there is no disk in the drive the following
message:
  VFS: Disk change detected on device ide1(22,0)
is written to system log during each open call.  Vold calls open every 5
seconds, so it's 17280 lines in log/day. I have been able to avoid these
messages by commenting out a line in drivers/ide/ide-cd.c (patch
included) and have not seen any problems yet.

I guess I have three questions:
 1. can this patch break things ? I suppose it could happen only
if cdrom_saw_media_change was not called when the CD is changed.
 2. is it possible to avoid the message by modifying vold ? E.g. finding
out that there is no media in the drive without calling open.
 3. is there a clean way to avoid these repeated messages ?

Thanks, Petr

--- ide-cd.c2001/02/22 22:30:02 1.1.1.11
+++ ide-cd.c2001/02/27 19:51:58
@@ -601,7 +601,7 @@

/* Check for tray open. */
if (sense_key == NOT_READY) {
-   cdrom_saw_media_change (drive);
+/* cdrom_saw_media_change (drive); */
} else if (sense_key == UNIT_ATTENTION) {
/* Check for media change. */
cdrom_saw_media_change (drive);

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

Re: New net features for added performance

[kuznet]

Hello!

> > 3) Enforce correct usage of it in all the networking :-)
> 
> ,) -- the tricky part.

No tricks, IP[v6] is already enforced to be clever; all the rest are free
to do this, if they desire. And btw, driver need not to parse anything,
but its internal stuff and even aligning eth II header can be made
in eth_type_trans().

Actually, it is possible now not changing anything but driver.
Fortunately, I removed stupid tulip from alpha, so that I have
no impetus to try this myself. 8)

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

Re: ISO-8859-1 completeness of kernel fonts?

[Guest section DW]

On Tue, Feb 27, 2001 at 09:37:55AM -0800, H. Peter Anvin wrote:

> You're much better off designing a larger ISO-8859-1 font and load in in
> user space.  You can use the 12x22 font in the kernel as a base.

kbd-1.05 comes with sun12x22.psfu, which essentially is the kernel font
together with a unimap.

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

Re: Posible bug in gcc

[Ville Herva]

On Mon, Feb 26, 2001 at 01:02:45PM -0500, you [Richard B. Johnson] claimed:
> 
> Script started on Mon Feb 26 12:54:20 2001
> # gcc -o xxx bug.c
> # ./xxx
> Correct output: 5 2
> GCC output:  5 2
> # gcc --version
> egcs-2.91.66
> # gcc -O2 -o xxx bug.c
> # ./xxx
> Correct output: 5 2
> GCC output:  10 5
> # exit
> exit

Funny:

vherva@babbage:/tmp>/usr/bin/gcc  c.c -o c; ./c ; /usr/bin/gcc --version 
Correct output: 5 2
GCC output:  5 2
2.96
vherva@babbage:/tmp>/usr/bin/gcc -O2 c.c -o c; ./c ; /usr/bin/gcc --version
Correct output: 5 2
GCC output:  10 5
2.96
vherva@babbage:/tmp>/usr/bin/gcc -O6 c.c -o c; ./c ; /usr/bin/gcc --version
Correct output: 5 2
GCC output:  10 5
2.96
vherva@babbage:/tmp>rpm -q gcc
gcc-2.96-74

vherva@babbage:/tmp>kgcc c.c  -o c; ./c ; kgcc --version 
Correct output: 5 2
GCC output:  5 2
egcs-2.91.66
vherva@babbage:/tmp>kgcc c.c -O2 -o c; ./c ; kgcc --version
Correct output: 5 2
GCC output:  10 5
egcs-2.91.66
vherva@babbage:/tmp>kgcc c.c -O6 -o c; ./c ; kgcc --version
Correct output: 5 2
GCC output:  10 5
egcs-2.91.66
vherva@babbage:/tmp>rpm -q kgcc
kgcc-1.1.2-40

vherva@babbage:/tmp>/usr/local/bin/gcc c.c -o c; ./c ;/usr/local/bin/gcc --version
Correct output: 5 2
GCC output:  5 2
pgcc-2.95.1
vherva@babbage:/tmp>/usr/local/bin/gcc c.c -O2 -o c; ./c ;/usr/local/bin/gcc --version
Correct output: 5 2
GCC output:  5 2
pgcc-2.95.1
vherva@babbage:/tmp>/usr/local/bin/gcc c.c -O6 -o c; ./c ;/usr/local/bin/gcc --version 
Correct output: 5 2
GCC output:  5 2
pgcc-2.95.1

I guess pgcc is not that buggy EVERY time. (Sorry for the off topic post, I
couldn't resist.)


-- v --

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

Re: 2.2.18 IDE tape problem, with ide-scsi

[Camm Maguire]

Greetings!  OK, with st debugging, here are the most common errors
with the Conner:

Feb 27 14:46:39 intech9 kernel: st0: Error: 2800, cmd: 8 1 0 0 40 0 Len: 16
Feb 27 14:46:39 intech9 kernel: Info fld=0x24, Current st09:00: sns = f0  8
Feb 27 14:46:39 intech9 kernel: ASC=14 ASCQ= 3
Feb 27 14:46:39 intech9 kernel: Raw sense data:0xf0 0x00 0x08 0x00 0x00 0x00 0x24 0x0a 
0x00 0x00 0x00 0x00 0x14 0x03 0x00 0x00 
Feb 27 14:46:39 intech9 kernel: st0: Sense: f0  0  8  0  0  0 24  a
Feb 27 14:46:39 intech9 kernel: st0: Tape error while reading.
Feb 27 14:46:40 intech9 kernel: st0: Error: 2800, cmd: 5 0 0 0 0 0 Len: 16
Feb 27 14:46:40 intech9 kernel: [valid=0] Info fld=0x0, Current st09:00: sns = 70  5
Feb 27 14:46:40 intech9 kernel: ASC=20 ASCQ= 0
Feb 27 14:46:40 intech9 kernel: Raw sense data:0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x0a 
0x00 0x00 0x00 0x00 0x20 0x00 0x00 0x00 
Feb 27 14:46:40 intech9 kernel: st0: Can't read block limits.
Feb 27 14:46:40 intech9 kernel: st0: Mode sense. Length 11, medium b6, WBS 10, BLL 8
Feb 27 14:46:40 intech9 kernel: st0: Density 45, tape length: 0, drv buffer: 1
Feb 27 14:46:40 intech9 kernel: st0: Block size: 512, buffer size: 32768 (64 blocks).


Any advice appreciated!

Khalid Aziz <[EMAIL PROTECTED]> writes:

> Camm Maguire wrote:
> > 
> > Thanks for the error identification.  The other drive is of a
> > *different* model.  This drive showed this behavior from the day I
> > bought it.  The drive could be going bad, but I doubt it.  Is it
> > possible that this manufacturer (Conner) has some peculiar
> > implementation of the spec?  I recall reading on this list sometime
> > back of similar workarounds to unusual drives.
> 
> Since the non-wroking drive is a different model, other drive working
> does not mean the st driver is sending only valid commands to the
> drives. st driver is sending a command to this drive which the drive
> does not like. It will help to know what that command is.
> 
> > 
> > > st driver prints the SCSI command that may have caused this error only
> > > when compiled with debug turned on. Maybe st driver should always print
> > > the command that results in a check condition as long as the command is
> > > not a Test Unit Ready or Mode Sense.
> > >
> > 
> > Can I turn on debug mode in runtime, or do I need to recompile
> > ide-scsi?
> 
> This is a compile time option, so you will have to recompile "st"
> driver. If you look at drivers/scsi/st.c, near the top of the file (line
> 44 for 2.4.2) you will see a line
> 
> #define DEBUG 0
> 
> Change this line to set DEBUG to 1 and recompile. This may generate lot
> of messages from Test Unit Ready and Mode Sense commands. You can
> suppress these messages by replacing the code block within "if
> (debugging)" conditional at line 241 with following:
> 
> if (SRpnt->sr_cmnd[0] != MODE_SENSE &&
>  SRpnt->sr_cmnd[0] != TEST_UNIT_READY) {
> printk(ST_DEB_MSG "st%d: Error: %x, cmd: %x %x %x %x %x
> %x Len: %d\n",
>dev, result,
>SRpnt->sr_cmnd[0], SRpnt->sr_cmnd[1],
> SRpnt->sr_cmnd[2],
>SRpnt->sr_cmnd[3], SRpnt->sr_cmnd[4],
> SRpnt->sr_cmnd[5],
>SRpnt->sr_bufflen);
> if (driver_byte(result) & DRIVER_SENSE)
> print_req_sense("st", SRpnt);
> }
> 
>  
> 
> Khalid Aziz Linux Development Laboratory
> (970)898-9214Hewlett-Packard
> [EMAIL PROTECTED]Fort Collins, CO
> 
> 

-- 
Camm Maguire[EMAIL PROTECTED]
==
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: "io mapaddr 0xXXXXX not valid" in smc-mca in 2.4.x

[Stephen Mollett]

On Monday 26 February 2001  8:15 pm, Alan Cox wrote:
> ... I had a look and a guess at a fix is in ac5 (out RSN)

You'll be glad to hear that the driver is now working perfectly. Thanks!

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