Re: IDE DMA problems on 2.4.0 with vt82c686a driver

[Vojtech Pavlik]

On Thu, Jan 11, 2001 at 09:41:55AM -0500, Mark Hahn wrote:
> > Since this looks like either a chipset, drive, or driver problem, I am 
> 
> no: the only entities involved with udma crc's are the drive,
> the controller (and the cable).  the kernel is not involved in any way
> (except to configure udma, of course.)

Well, that's the part where it is really easy to cause crc errors. But I
believe I got that right in the driver. Tested successfully on many VIA
chipsets.

> > occasionally (not often/constant, but sometimes) get CRC errors:
> > hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> 
> nothing wrong here.  occasional crc retries cause no performance impact.

Also it should be noted that they don't cause any corruption (*). The worst
thing they can do is disabling DMA if they happen many times in a short
period of time. 

(*) - UDMA modes only. CRC errors are a big problem in PIO and
  MWDMA/SWDMA modes.

> > After reading some archives in linux-kernel, I tried changing some 
> > options. Then I changed out the 40 pin, 80 wire cable with a new one. 
> 
> great, since without the 80c cable, udma > 33 is illegal.

... note that he says 40pin, 80wire. That's the correct UDMA66 cable, it
has just 40 pins.

> is it safe to assume your cable is also 18" or less, with both ends
> plugged in (no stub)?  you might be able to minimize CRC retries
> by changing where the cable runs.  it's also conceivable that CRC
> errors would be caused by marginal power, bad trace layout on the 
> motherboard,

Bad trace on the motherboard is what I suspect on KT7's. It could be
designed a little longer or shorter than the others and a marginal clock
skew can cause the crc errors. Or the trace can lead too close to some
source of e/m noise.

> and definitely by overclocking (PCI other than 33 MHz).
> 
> > My main concern that I havnt beem able to find an answer for on any 
> > archives or documentation, Can this cause file system corruption in any way?
> 
> abosolutely not.  udma checksums each transfer.  when checksums don't match,
> the *hardware* retries the transfer (and incidentally reports the event,
> which Linux obligingly passes on to you.)

The software retries the transfer, the hardware just aborts. But it's
safe, anyways.

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

Re: khttpd beaten by boa

[David S. Miller]

Lars Marowsky-Bree writes:
 > This just goes on to show that khttpd is unnecessary kernel bloat
 > and can be "just as well" handled by a userspace application, minus
 > some rather very special cases which do not justify its inclusion
 > into the main kernel.

My take on this is that khttpd is unmaintained garbage.

TUX is evidence that khttpd can be done properly and
beat the pants off of anything done in userspace.

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]
Please read the FAQ at http://www.tux.org/lkml/

Re: IDE DMA problems on 2.4.0 with vt82c686a driver

[Vojtech Pavlik]

Hi!

I'm the current maintainer of the VIA driver. I'm pretty sure the
version in 2.4.0 programs the chips correctly for harddrives at various
speeds, even leaving some margins where it shouldn't need to.

I think there is not any problem with Western Digital drives, I've got
many reports of them working OK with different chipsets, including those
made by VIA.

However, I'm getting many many problem reports on Abit KT7's. It might
be that this is a very popular board, but nevertheless, I think at least
its earlier revisions had trouble with UDMA transfers.

At least on one of these boards a drive did work correctly, without CRC
errors on the secondary interface, and gave constant errors on the
primary. All other known problem causes were eliminated.

I think it's Abit this time who's to blame.

-

Anyway, you can try disabling VIA support in kernel, and if BIOS sets up
things correctly, you should be able to use UDMA as well. If it works
then, it would mean that my driver is a problem. I'd like to hear in
either case.

Vojtech

On Thu, Jan 11, 2001 at 09:38:26AM -0500, dep wrote:
> On Thursday 11 January 2001 08:33 am, James Brents wrote:
> 
> | Since this looks like either a chipset, drive, or driver problem, I
> | am submitting this.
> | I have recently started using DMA mode on my harddisk. However, I
> | occasionally (not often/constant, but sometimes) get CRC errors:
> | hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> | hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
> 
> welcome to the club. if you are given an answer off-list to this, i'd 
> love a copy, because i've had the same issue for six months now. some 
> have said that it's crosstalk in the cable -- in which case, all 
> three of the 80-conductor cables i've tried are insufficiently 
> shielded and we're in need of premium 80-conductor cables. and i 
> found this in the november 200 linux journal, page 82, last 
> paragraph, in an article on the ultimate linux box written by don 
> marti:
> 
> "earlier this year, kernel hacker andre hedrick, the maintainer of 
> linux's ide driver, tracked a user's problem to the fact that western 
> digital drives don't do error checking correctly. he posted to 
> linux-kernel, 'wdc drives blow off the crc check of udma . . . . this 
> is bad and stupid.' western digital fired back on their web site 
> with, 'if there's a problem using these drives in linux the problem 
> most likely lies with the software driver and not the hard drive 
> itself.' i'm going to believe the kernel hacker over the hardware 
> vendor and stay away from western digital drives for awhile."
> 
> this suggests a.) that we need to gently pressure the w.d. people to 
> come up with a fix or provide the specs necessary to fashion one -- 
> the latter being preferable -- and b.) that we need to figure out 
> some sort of hack that does -- what? in my experience, these error 
> messages actually signify nothing, but they're using up cycles. can 
> they be safely supressed? beats me. but they sold a hell of a lot of 
> these things.
> 
> though i've noticed that the problem seems to be limited to those of 
> us who have via chipset motherboards, suggesting that it is limited 
> to that chipset, that chipset is ubiquitous, or via chipset 
> motherboard owners are generally the complaining type. no idea which 
> applies there, either.
> 
> -- 
> dep
> --
> bipartisanship: an illogical construct not unlike the idea that
> if half the people like red and half the people like blue, the 
> country's favorite color is purple.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> Please read the FAQ at http://www.tux.org/lkml/

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

Re: Strange umount problem in latest 2.4.0 kernels

[Christoph Rohland]

On Fri, 12 Jan 2001, [EMAIL PROTECTED] wrote:
> Same cam be applied to shm ? Thus kernel Documentation/Changes
> should be changed:
[...]
> 
> none/dev/shmshm defaults0 0
> 
> to
> 
> shm/dev/shmshm defaults0 0
> 

Yes, I thought that I changed that :-( I always have the type as
device in my fstab. 

Linus, it is not really crucial, but still could be applied without
breaking anything for sure ;-) 

Greetings
Christoph

--- 2.4.0/Documentation/Changes Mon Jan  1 19:00:04 2001
+++ linux/Documentation/Changes Fri Jan 12 09:03:35 2001
@@ -121,7 +121,7 @@
 memory. Adding the following line to /etc/fstab should take care of
 things:
 
-none   /dev/shmshm defaults0 0
+shm/dev/shmshm defaults0 0
 
 Remember to create the directory that you intend to mount shm on if
 necessary (The entry is automagically created if you use devfs). You   
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: khttpd beaten by boa

[Lars Marowsky-Bree]

On 2001-01-11T22:20:56,
   Christoph Lameter <[EMAIL PROTECTED]> said:

> Then we decided to switch persistant connection off... But boa still wins.
> 
> What is wrong here? I would expect transferates of a 3-4 megabytes over a
> localhost interface. The file is certainly in some kind of cache.

This just goes on to show that khttpd is unnecessary kernel bloat and can be
"just as well" handled by a userspace application, minus some rather very
special cases which do not justify its inclusion into the main kernel.

Sincerely,
Lars Marowsky-Brée <[EMAIL PROTECTED]>

-- 
Perfection is our goal, excellence will be tolerated. -- J. Yahl

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

Re: [linux-usb-devel] [PATCH] USB Config fix for 2.2.19-pre7

[Greg KH]

On Thu, Jan 11, 2001 at 06:01:19PM +0100, Franz Sirl wrote:
> Why do the input handlers depend on CONFIG_USB_HID? On PPC we already have 
> trouble with them depending on CONFIG_USB, so everybody has to select 
> CONFIG_USB even if he just has ADB hardware.

Don't these input drivers _require_ the USB HID driver core to work
properly?  

Or am I mistaken, and this is the 2.4.0 input core code, but
not in a separate directory, like 2.4.0 has it?

thanks,

greg k-h

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

Question regarding driver developement

[Anders Johansson]

Hi

I am very sorry for disturbing the kernel development with this question
which I suspect might be off topic. If I am totally off topic please tell
me where to find help in your flame mails.

I am developing a device driver (will be GPL) for a PCI board hosting two
Digital Signal Processors (DSPs). The software running on the DSPs needs
disk access (~10Mb/s). The board has DMA engines built in to it's PCI
bridges which are capable of bus mastering. The Software running on the
DSPs requires soft realtime response from the disk access.

What I want to do is to stream data directly to a file on the hard drive if
possible.

The only way I have found so far is to write have two FIFO buffers in the
driver (in and out) and use a daemon running in user space to manage the
disk access. 

This is quite inefficient however since it requires at least 5 memcopy
operations before the data reaches the hard drive. 

I could dedicate one complete SCSI bus for the disk I/O.

Is it possible to write to a file from within a device driver? 
If it is it would save 3 memcopy operations (if I am correct :). 
Is it advisable?

I am not subscribed to this list so please reply to me personally.

Thank you very much for your help.
Best Regards,
//Anders

__
Anders JohanssonRoom 314,113  Australian Telecommunications .-_|\
Visiting Research Associate   Research Institute (ATRI)/ \
telephone:  +61 8 9266 3268   Curtin Uni of Technology P_.-._/
e-mail: [EMAIL PROTECTED]Bentley WA, 6102. o
__

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

Re: named streams, extended attributes, and posix

[James H. Cloos Jr.]

Michael> Please read and comment! :)

There should be some discussion on what to do about filenames which
contain colons in such a setup.  Moving a file w/ a colon from a fs
which does not support named streams to one which does should DTRT;
exactly what TRT is should be discussed.

-JimC
-- 
James H. Cloos, Jr.   1024D/ED7DAEA6 
<[EMAIL PROTECTED]>  E9E9 F828 61A4 6EA9 0F2B  63E7 997A 9F17 ED7D AEA6
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

khttpd beaten by boa

[Christoph Lameter]

I got into a bragging game whose webserver is the fastest with Jim Nelson
one of the authors of the boa webserver. We finally settled on the Zeus
test to decide the battle.

First boa won hands down because it supports persistant connections. Boa
on port 6000. Khttpd on port 80:
 
clameter@melchi:~$ ./zb localhost /index.html -k -c 215 -n 2 -p 6000
 
---
Server: Boa/0.94.8.3
Doucment Length:1666
Concurency Level:   215
Time taken for tests:   33.865 seconds
Complete requests:  2
Failed requests:0
Keep-Alive requests:20001
Bytes transfered:   37882109
HTML transfered:33321666
Requests per seconds:   590.58
Transfer rate:  1118.62 kb/s
 
Connnection Times (ms)
   min   avg   max
Connect: 0 2   346
Total: 258   360   485
---

clameter@melchi:~$ ./zb localhost /index.html -k -c 215 -n 2
 
---
Server: kHTTPd/0.1.6
Doucment Length:1666
Concurency Level:   215
Time taken for tests:   101.735 seconds
Complete requests:  2
Failed requests:0
Keep-Alive requests:0
Bytes transfered:   37096378
HTML transfered:33643204
Requests per seconds:   196.59
Transfer rate:  364.64 kb/s
 
Connnection Times (ms)
   min   avg   max
Connect:36   438  1084
Total: 394  1070  2009
---


Then we decided to switch persistant connection off... But boa still wins.

clameter@melchi:~$ ./zb localhost /index.html -c 215 -n 2 -p 6000
 
---
Server: Boa/0.94.8.3
Doucment Length:1666
Concurency Level:   215
Time taken for tests:   88.040 seconds
Complete requests:  2
Failed requests:0
Bytes transfered:   37352000
HTML transfered:33528250
Requests per seconds:   227.17
Transfer rate:  424.26 kb/s
 
Connnection Times (ms)
   min   avg   max
Connect: 1   305  3417
Total: 458   932  4232
---

This shows the following problems with khttpd:

1. Connect times are on average longer than boa. Why???

2. Transfers also take longer,


What is wrong here? I would expect transferates of a 3-4 megabytes over a
localhost interface. The file is certainly in some kind of cache.
 

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

Re: 2.4.1-pre1 breaks XFree 4.0.2 and "w"

[Udo A. Steinberg]

Linus Torvalds wrote:
> 
> Could people with Athlons please verify that pre3 works for them?

It works very well wrt. fxsr.

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

Re: 2.4.1-pre1 breaks XFree 4.0.2 and "w"

[TimO]

Linus Torvalds wrote:
> 
> Could people with Athlons please verify that pre3 works for them?
> 
> 
> Linus

Running nowuptime 6 minutes.

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

No Subject

[flyinglinux]

ÏëÒªÓµÓÐÖ§³Ö2000ÈËͬʱÔÚÏߵĸöÈËÁÄÌìÊÒÂð?ÄãÀ´µ±¹ÜÀíÔ±!
¿ìÀ´ÉêÇëÍøÒ×Ãâ·Ñ¸öÈËÁÄÌìÊÒ  http://ichat.163.com


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

Re: IDE DMA problems on 2.4.0 with vt82c686a driver

[Andre Hedrick]

On Thu, 11 Jan 2001, Alan Cox wrote:

> > us who have via chipset motherboards, suggesting that it is limited 
> > to that chipset, that chipset is ubiquitous, or via chipset 
> > motherboard owners are generally the complaining type. no idea which 
> > applies there, either.

Sheesh, when you can reprogram the chipset identity so that you can make
it appear to be mimic older chipsets that have current support, well you
get the headache!

> Or there are a lot of them. 90% of scsi bug reports I get are adaptec 29xx
> driver. Thats not because the adaptec 29xx is the most sucky driver 8)

It is not so much the chipset of the drivers, it is the jokers making
mainboards.  At the last meeting in Irvine there were issues about PCB
lane designs and chipset that cause problems in crosstalk or create bad
timing skews.  The problem is so wide spread in the industry that T13 is
looking at drafting a possible design annex for defined how to test and
create good hardware.  (I do not need the noise, I know this is what we
should be doing and not screwing up/down hardware) ;-)

> Firstly there are numerous reasons for CRC errors. At ATA100 even the track
> length and the capacitance of the connectors becomes an issue. It is quite
> possibly a driver issue. It could even be that specific combination of drives
> and ide controller is right on the edge of the spec limits and just slightly
> dipping over. It might be the odd power spike.

The 2.4.0 kernels now have the very first created in the software industry
of ATA an auto-dma-crc transfer rate recovery callback.  Thus if you get
only the 0x84/0x51 errors and there are no other problems and you chipset
code is full-featured to have a hwif->speedproc callback, it will auto set
the transfer-rate down until the iCRC errors stop.

> Providing the code is working sanely the odd CRC error shouldnt be a 
> problem and should be causing a command retry. The CRC checking used in ATA
> is very robust so unlike scsi parity errors which couldnt be ignored ATA
> ones on occassion are probably fine

(off to mark calender, a positive comment about ATA)

> ATA100 is another testimony to the fact that pigs can be made to fly given 
> sufficient thrust (to borrow an RFC)

But the price to pay is SCSI noise in ATA devices, or was that pig lips
flapping in the breeze...?


Andre Hedrick
Linux ATA Development

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

[semi-OT] Historic Linux Kernels.

[Nicholas Knight]

on kernel.org you can get old kernels clear back to 0.01 in
http://www.kernel.org/pub/linux/kernel/Historic/
but some things are missing, though nothing major

what's missing that I'm most interested in is the linux boot-disk that
apparently came into being around .11.

to quote from
http://www.kernel.org/pub/linux/kernel/Historic/old-versions/RELNOTES-0.12:
2) Test out the linux boot-disk with the root file system.


and the .11 release notes/installation instructions (again quoting from
http://www.kernel.org/pub/linux/kernel/Historic/old-versions/RELNOTES-0.12)
INSTALLATION
This is a SHORT install-note. The installation is very similar to 0.11,
so read that (INSTALL-0.11) too.


none of these things are included in linux-0.11.tar.gz/bz2

I presume Linus just assumed that they'd be of no real interest to anyone
looking at the old kernels, but they'd be of interest to me as I'm quite
interested in what linux went through in early development beyond just
reading about it, I prefer to actually see these things for myself :)

So does anyone have these two things? (the .11 release notes/install
instructions and boot/root diskette) If so, I'd be grateful if you could
either point me to them, or email them to me ([EMAIL PROTECTED])

Thanks,
-NK


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

2.4.1-pre3 UP

[Garst R. Reese]

I think you missed an ifdef in ksyms,
We don't all have smp 
also update Makefile
Garst
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

[DOS] emulation under linux

[Jim M.]

Hi,
There is a compiler package that runs on DOS but not on Linux.
I was wondered how can i emulate DOS under linux so that i run the  compile 
package?. I have kernel 2.2.14-12. RH 6.2.
_
Get your FREE download of MSN Explorer at http://explorer.msn.com

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

Re: depmod -a and 2.4.0

[David Ford]

> pretty darned impressive :-).  Another oddity that someone else
> already reported: the ipv6 module shows a reference count of -1.

a ref count of -1 means the module decides when to unload.

-d



begin:vcard 
n:Ford;David
x-mozilla-html:TRUE
url:www.blue-labs.org
adr:;;
version:2.1
email;internet:[EMAIL PROTECTED]
title:Blue Labs Developer
note;quoted-printable:GPG key: http:[EMAIL PROTECTED]=0D=0A
x-mozilla-cpt:;9952
fn:David Ford
end:vcard

Re: 2.4.1-pre1 breaks XFree 4.0.2 and "w"

[Linus Torvalds]

On Fri, 12 Jan 2001, Andrea Arcangeli wrote:
> 
> Note that there was a precise reason for not implementing it as the TSC disable
> (infact at first in 2.2.x I was clearing the bigflag in x86_capabilities too).
> The reason is that the way TSC gets disabled breaks /proc/cpuinfo.

No.

It FIXES /proc/cpuinfo.

Your alternative patch is the thing that breaks.

We _want_ /proc/cpuinfo to reflect the fact that the kernel considers
FSXR/XMM to not exist. That is true information, and is in fact something
that install scripts etc can find extremely useful.

In particular, imagine an installation script that wants to install the
proper optimized version of a library on a machine. How is it supposed to
know whether it should use the mmx version, the xmm version, or the
integer version?

This is _exactly_ the kind of thing that /proc/cpuinfo was supposed to be
able to deal with, and that means that if the kernel doesn't like to use
xmm for some reason (ie the user explicitly told it to), then it shouldn't
show up in /proc/cpuinfo - because on that machine XMM simply does not
exist as far as user-land is concerned.

Similarly, when we disable TSC, it's also telling user-land that this
machine does not appear to have a working TSC for some reason. User-land
applications may also care about the fact that TSC seems to skip time if
the machine is idle etc (which was apparently the problem with some broken
Cyrix chips).

After all, a user can always do a "cpuid" to get to know what the CPU
itself reports. /proc/cpuinfo is supposed to be a higher-level interface,
where the buggy bits have been removed or renamed (ie AMD extensions are
properly renamed and can be easily recognized as such, without each
user-mode application having to know about the magic meaning of bits in
"cpuid" on different machines).

Linus

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

Re: IDE DMA problems on 2.4.0 with vt82c686a driver

[John O'Donnell]

Alan Cox wrote:

>> us who have via chipset motherboards, suggesting that it is limited 
>> to that chipset, that chipset is ubiquitous, or via chipset 
>> motherboard owners are generally the complaining type. no idea which 
>> applies there, either.
> 
> 
> Or there are a lot of them. 90% of scsi bug reports I get are adaptec 29xx
> driver. Thats not because the adaptec 29xx is the most sucky driver 8)
> 
> Firstly there are numerous reasons for CRC errors. At ATA100 even the track
> length and the capacitance of the connectors becomes an issue. It is quite
> possibly a driver issue. It could even be that specific combination of drives
> and ide controller is right on the edge of the spec limits and just slightly
> dipping over. It might be the odd power spike.
> 
> Providing the code is working sanely the odd CRC error shouldnt be a 
> problem and should be causing a command retry. The CRC checking used in ATA
> is very robust so unlike scsi parity errors which couldnt be ignored ATA
> ones on occassion are probably fine
> 
> ATA100 is another testimony to the fact that pigs can be made to fly given 
> sufficient thrust (to borrow an RFC)
> 
> Alan

I acquired a VIA Mobo (ASUS CUV4X) for home and it is workin pretty damn
spiffy with Linux - Even better with 2.4.0 with regards to IDE!!!
Once a month I boot WinDOS to play a game I can't play in Linux, THEN
my troubles begin!!!
parport_pc: Via 686A parallel port: io=0x378, irq=7, dma=3
VP_IDE: VIA vt82c686a IDE UDMA66 controller on pci0:4.1
etc... etc... etc...
yadda yadda yadda 

Alan,
My father repaired F-4 Phantoms in Vietnam.  He said the F-4 Phantom was
proof that if you put enough power behind a brick, it would fly!!!
Your comment remonded me of that - just had to share  :-)

-- 
 what's the difference between chattr and chmod?
 SomeLamer: man chattr > 1; man chmod > 2; diff -u 1 2 | less
-- Seen on #linux on irc
=== Never ask a geek why, just nod your head and slowly back away.===
+==++
| John O'Donnell (Sr. Systems Engineer, Net Admin, Webmaster, etc.) |
| Voice FX Corporation (a subsidiary of Student Advantage)  |
| One Plymouth Meeting | E-Mail: [EMAIL PROTECTED] |
| Suite 610|   www.voicefx.com  |
| Plymouth Meeting, PA 19462   | www.campusdirect.com   |
+==++

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

Re: Anyone else interested in a high-precision monotonic counter?

[Manfred Bartz]

"Christopher Friesen" <[EMAIL PROTECTED]> wrote:

> Manfred Bartz wrote:
> 
> > Why a new system call?
> Well, you'd be accessing a different kernel variable--"ytime" instead of
> "xtime". This new variable wouldn't be adjusted when the  system
> time/date was, it would start at zero and always increase. 

> > have you looked at the return-value of times(2)
> > Or roll your own using setitimer(2)
> 
> Both of these are precise only to jiffies, which defaults at 10
> milliseconds on x86 and PPC.  If you want microsecond timing, the only
> current standard way to do it is to use gettimeofday(), which is
> sensitive to changes in system date and time.

Ok.  A monotonic, high resolution timer would be useful.

Maybe one should then push for a full implementation of xtime
including TIME_MONOTONIC and TIME_TAI?




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

followup: depmod -a and 2.4.0

[Bob_Tracy]

Dooh!  Please ignore earlier bogus report of module loading
"trouble".  This was my bad: an old init script was running
"modprobe -a".  Sigh...

-- 
Bob Tracy[EMAIL PROTECTED]
-
 "We might not be in hell, but we can see the gates from here."
 --Phoenix resident, Summer of 2000
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

depmod -a and 2.4.0

[Bob_Tracy]

Maybe I missed the discussion, but why might "depmod -a" result
in every module getting installed?  This didn't happen under any
of the 2.4.0-testX releases that I recall, and I ran every one of
those and the prerelease without this "trouble".  Gotta say, the
screen output from running "lsmod" with everything installed is
pretty darned impressive :-).  Another oddity that someone else
already reported: the ipv6 module shows a reference count of -1.

Yes, I'm running modutils-2.4.1, and I get the same results with
modutils-2.3.15.

-- 
Bob Tracy[EMAIL PROTECTED]
-
 "We might not be in hell, but we can see the gates from here."
 --Phoenix resident, Summer of 2000
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: [PROBLEM] 2.4.1-pre2 - Undefined symbol `__buggy_fxsr_alignment' - (FIXED)

[Shawn Starr]

e i think it was just fixed in pre3 ;-)

+   if (offsetof(struct task_struct, thread.i387.fxsave) & 15) {
+   extern void __buggy_fxsr_alignment(void);
+   __buggy_fxsr_alignment();
+   }


> GCC 2.95.2 -> PGCC 2.95.2(3?) patched. 2.4.0 compiles fine
>
> init/main.o: In function `check_fpu':
> init/main.o(.text.init+0x53): undefined reference to `__buggy_fxsr_alignment'
>
> make: *** [vmlinux] Error 1
>
> On compiling (and recompiling) i get this fatal error. This function
> does not exist anymore?
>
> Anyone else having this problem?
>
> Shawn Starr.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> Please read the FAQ at http://www.tux.org/lkml/

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

Re: Linux 2.4.0-ac7

[Jens Axboe]

On Fri, Jan 12 2001, Bill Crawford wrote:
> depmod: *** Unresolved symbols in 
>/lib/modules/2.4.0-ac7/kernel/drivers/scsi/scsi_mod.o
> depmod: queued_sectors

Apologies, I didn't think of modular SCSI/IDE for this...

--- /opt/kernel/linux-2.4.0-ac7/drivers/block/ll_rw_blk.c   Fri Jan 12 04:47:18 
2001
+++ drivers/block/ll_rw_blk.c   Fri Jan 12 04:47:40 2001
@@ -1389,3 +1389,4 @@
 EXPORT_SYMBOL(generic_make_request);
 EXPORT_SYMBOL(blkdev_release_request);
 EXPORT_SYMBOL(generic_unplug_device);
+EXPORT_SYMBOL(queued_sectors);

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

Re: 2.4.1-pre1 breaks XFree 4.0.2 and "w"

[Andrea Arcangeli]

On Thu, Jan 11, 2001 at 06:08:21PM -0800, Linus Torvalds wrote:
> 
> Could people with Athlons please verify that pre3 works for them?

It works fine.

> It also makes the fxsr disable act the same way the TSC disable does.

Note that there was a precise reason for not implementing it as the TSC disable
(infact at first in 2.2.x I was clearing the bigflag in x86_capabilities too).
The reason is that the way TSC gets disabled breaks /proc/cpuinfo.  Furthmore
in english sense if "the cpu has fxsr or xmm" doesn't mean we can use them at
runtime in the kernel. Such wrong assumption was the source of the 2.4.0 md bug
in first place ;). So I'm not excited we're back in the old way. But of course
those are minor issues and I'm not that concerned /proc/cpuinfo changes even if
the CPU remains the same because nobody should need nofxsr and notsc anyways...

This is a leftover btw:

--- 2.4.1pre3/include/asm-i386/xor.h.~1~Fri Jan 12 04:14:36 2001
+++ 2.4.1pre3/include/asm-i386/xor.hFri Jan 12 04:23:32 2001
@@ -843,7 +843,7 @@
do {\
xor_speed(_block_8regs);\
xor_speed(_block_32regs);   \
-   if (HAVE_XMM)   \
+   if (cpu_has_xmm)\
xor_speed(_block_pIII_sse); \
if (md_cpu_has_mmx()) { \
xor_speed(_block_pII_mmx);  \
@@ -855,4 +855,4 @@
We may also be able to load into the L1 only depending on how the cpu
deals with a load to a line that is being prefetched.  */
 #define XOR_SELECT_TEMPLATE(FASTEST) \
-   (HAVE_XMM ? _block_pIII_sse : FASTEST)
+   (cpu_has_xmm ? _block_pIII_sse : FASTEST)



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

[PROBLEM] 2.4.1-pre2 - Undefined symbol `__buggy_fxsr_alignment'

[Shawn Starr]

GCC 2.95.2 -> PGCC 2.95.2(3?) patched. 2.4.0 compiles fine

init/main.o: In function `check_fpu':
init/main.o(.text.init+0x53): undefined reference to `__buggy_fxsr_alignment'

make: *** [vmlinux] Error 1

On compiling (and recompiling) i get this fatal error. This function
does not exist anymore?

Anyone else having this problem?

Shawn Starr.

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

[patch[ 2.4.1-pre3 HAVE_XMM compile error

[Mohammad A. Haque]

patch to let 2.4.1-pre3 compile on PIII
we are moving from HAVE_XMM to cpu_has_xmm right?

-- 

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

  "Alcohol and calculus don't mix. Project Lead
   Don't drink and derive." --Unknown  http://wm.themes.org/
   [EMAIL PROTECTED]
=

--- linux/include/asm-i386/xor.h.orig   Thu Jan 11 21:55:49 2001
+++ linux/include/asm-i386/xor.hThu Jan 11 22:22:18 2001
@@ -843,7 +843,7 @@
do {\
xor_speed(_block_8regs);\
xor_speed(_block_32regs);   \
-   if (HAVE_XMM)   \
+   if (cpu_has_xmm)\
xor_speed(_block_pIII_sse); \
if (md_cpu_has_mmx()) { \
xor_speed(_block_pII_mmx);  \
@@ -855,4 +855,4 @@
We may also be able to load into the L1 only depending on how the cpu
deals with a load to a line that is being prefetched.  */
 #define XOR_SELECT_TEMPLATE(FASTEST) \
-   (HAVE_XMM ? _block_pIII_sse : FASTEST)
+   (cpu_has_xmm ? _block_pIII_sse : FASTEST)

Linux 2.4.0-ac7

[Bill Crawford]

depmod: *** Unresolved symbols in /lib/modules/2.4.0-ac7/kernel/drivers/scsi/scsi_mod.o
depmod: queued_sectors

-- 
/* Bill Crawford, Unix Systems Developer, ebOne, formerly GTS Netcom */
#include "stddiscl.h"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: Floating point broken between 2.4.0-ac4 and -ac5?

[Aaron Lehmann]

On Wed, Jan 10, 2001 at 08:58:00PM -0800, [EMAIL PROTECTED] wrote:
> A Duron box running 2.4.0-ac5 (and -ac6) shows NaN in many
> places (such as df output showing usage "nan%").  Right now I
> reverted back to 2.4.0-ac4 which does not show the problem.
> The kernel was compiled with CONFIG_MK7 and without
> MATH_EMULATION, if that makes any difference.

I just had exactly the same problem with ac6 and an Athlon. Many
floating point numbers were replaced with nan. XFree86 broke.

 PGP signature

various issues/questions

[Mohammad A. Haque]

Kernel 2.4.0-prerelease through 2.4.1-pre2

I recently got a Pioneer 105S 16x slot loading DVD drive and have been
getting lots os the following messages when playing dvds and cdroms

hdb: DSC timeout
hdb: cdrom_decode_status: status=0x51 { DriveReady SeekComplete Error }
hdb: cdrom_decode_status: error=0xb0
hdb: cdrom_decode_status: status=0x51 { DriveReady SeekComplete Error }
hdb: cdrom_decode_status: error=0xb0
hdb: cdrom_decode_status: status=0x51 { DriveReady SeekComplete Error }
hdb: cdrom_decode_status: error=0xb0
hdb: DMA disabled
hdb: ATAPI reset complete
hdb: cdrom_read_intr: data underrun (4 blocks)
end_request: I/O error, dev 03:40 (hdb), sector 1748
hdb: tray open
end_request: I/O error, dev 03:40 (hdb), sector 1748
hdb: tray open
end_request: I/O error, dev 03:40 (hdb), sector 1748
hdb: tray open
end_request: I/O error, dev 03:40 (hdb), sector 1748
hdb: tray open
end_request: I/O error, dev 03:40 (hdb), sector 2448
hdb: tray open
end_request: I/O error, dev 03:40 (hdb), sector 204


Is this possibly specific to slot loading drives? I didn't have problems
with my old Creative 2x dvd drive.



I also saw the following but don;t know what was happening on my machine
at the time.

__alloc_pages: 3-order allocation failed.
__alloc_pages: 3-order allocation failed.
__alloc_pages: 3-order allocation failed.
__alloc_pages: 3-order allocation failed.
__alloc_pages: 3-order allocation failed.
__alloc_pages: 3-order allocation failed.
__alloc_pages: 2-order allocation failed.
__alloc_pages: 2-order allocation failed.
__alloc_pages: 2-order allocation failed.
__alloc_pages: 2-order allocation failed.
__alloc_pages: 2-order allocation failed.
__alloc_pages: 2-order allocation failed.
__alloc_pages: 2-order allocation failed.
__alloc_pages: 2-order allocation failed.
__alloc_pages: 2-order allocation failed.
__alloc_pages: 2-order allocation failed.
__alloc_pages: 2-order allocation failed.
__alloc_pages: 2-order allocation failed.
__alloc_pages: 2-order allocation failed.
__alloc_pages: 2-order allocation failed.
__alloc_pages: 2-order allocation failed.
__alloc_pages: 2-order allocation failed.
__alloc_pages: 2-order allocation failed.
__alloc_pages: 2-order allocation failed.
__alloc_pages: 2-order allocation failed.
__alloc_pages: 3-order allocation failed.


-- 

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

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

[depmod] question

[Jim M.]

Hello all,
I have kernel verison 2.2.14-12 version with RH6.2.
I do "cd /sbin" and i see "depmod" there in the /sbin
directory. But somehow seems like load module is not
working. Maybe this is the reason why system freezes happen
in my RH. A driver for a custom built pci card is not
loaded properly. Maybe i should do "/sbin/modprobe pci.driver"
manually or put it in my rc.local file. Please clarify if possible.
Thanks in advance.
J
_
Get your FREE download of MSN Explorer at http://explorer.msn.com

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

O_NONBLOCK, read(), select(), NFS, Ext2, etc.

[Michael Rothwell]

The man pages for open, read and write say that if a file is opened
using the O_NONBLOCK flag, then read() and write() will always return
immediately and not block the calling process. This does not appear to
be true; but perhaps I am doing something wrong. If I open() a file (on
2.2.18) from a floppy or NFS mount (to test in a slow environment) with
O_NONBLOCK|O_RDONLY, read() will still block. If I try to select() on
the file descriptor, select() always returns 0.

Is there a way to make open(), read() and write() live up to their
manpages?

-M

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

Re: Where did vm_operations_struct->unmap in 2.4.0 go?

[Keith Owens]

On Fri, 12 Jan 2001 03:12:47 +0100, 
Ingo Oeser <[EMAIL PROTECTED]> wrote:
>So why don't we use sth. like depmod for these issues and get the
>link order automagically (like we get module load order)?

depmod handles dependencies on symbols.  Module Y needs a symbol from
module X so modprobe must load X before Y.  This is a link/load problem
which depmod handles fairly well.

The initialisation order is a dependency on actions, not on symbols.
Code F cannot start until code E has initialised so execute E before F.
This should have *NOTHING* to do with link order, but it is implemented
as a side effect of link ordering which confuses people.

People need to realise that the problem is initialisation order,
nothing more, nothing less.  You have to determine and document the
startup requirements for your code.  Only you know what the startup
pre-requisites for your code are, there is no way for another program
to determine this from the source.  Document your startup requirements,
implement according to the documentation and your problems go away.

Initialisation order is not the problem, the implementation is the
problem.  The method currently used to control initialisation order
sucks.  It is better than the original method (lots of conditional
calls in main.c) but it still sucks.

* Initialisation order is set by the order of structures in section
  .initcall.init.
* The order of the structures in .initcall.init is set by the order
  that objects are linked into vmlinux.
* The link order for vmlinux is derived from a combination of line
  order within a Makefile plus an overriding directory link order from
  the top level Makefile and parent Makefiles.
* Because order is a side effect of adding a line to a Makefile, the
  order requirements are rarely documented.

It is no wonder that people have problems getting the initialisation
order correct.

I want to completely remove this multi layered method for setting
initialisation order and go back to basics.  I want the programmer to
say "initialise E and F after G, H and I".  The kernel build system
works out the directed graph of initialisation order then controls the
execution of startup code to satisfy this graph.

That still means controlling link order to achieve the required result.
But with my approach the complexity would be handled by kbuild based on
explicit rules which are documented in the local Makefile, instead of
the complexity being handled by programmer via implicit rules scattered
over several layers of Makefiles.

A typical graph would have scsi disk depends on scsi host adaptor group
which depends on pci.  Within the scsi host adaptor group you might
need to initialise one driver before another, so just declare the few
inter-driver dependencies.  kbuild would automatically initialise pci
then the scsi host adaptors (in the correct order) then scsi disk.

Most of the objects have fairly simple execution dependencies, e.g.
all file systems depend on core fs code having already executed.  There
are no dependencies between most file systems so most file systems
could initialise in any order[1] which means they could be linked in
any order within the file system group.

I am ready and willing to code this method, it would make kbuild a lot
easier to code, as well as making future maintainence a lot easier.
Linus refuses to accept this approach.  He insists that kernel coders
explicitly specify the link order for everything, via Makefile
order[2].  As long as Linus insists on kernel coders explicitly
controlling the entire link order, we are stuck with the current
method.  I have tried to change his mind without success.

[1] vfat is one obvious exception, it needs dos first.  Also the first
few built in file systems must execute in a defined order because
that in turn controls the probe order for mount.  But this order
should be explicitly declared, not as a side effect of the line
order in fs/Makefile.

[2] http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg10520.html

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

Re: 2.4.1-pre1 breaks XFree 4.0.2 and "w"

[Linus Torvalds]

Could people with Athlons please verify that pre3 works for them?

It's basically Andrea's patch, but I moved the FPU save/restore games away
from arch/i386/lib/mmx.c, so that everything is properly done in one place
and others call the appropriate helper functions instead of thinking that
they know how the lazy FP switching is done.

It also makes the fxsr disable act the same way the TSC disable does.

(And yes, I forgot to update the Makefile release number - sue me, I'm
too lazy to upload a new patch with that fixed ;).

Linus

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

Re: [PLEASE-TESTME] Zerocopy networking patch, 2.4.0-1

[Stephen C. Tweedie]

Hi,

On Tue, Jan 09, 2001 at 11:14:54AM -0800, Linus Torvalds wrote:
> In article <[EMAIL PROTECTED]>,
> 
> kiobufs are crap. Face it. They do NOT allow proper multi-page scatter
> gather, regardless of what the kiobuf PR department has said.

It's not surprising, since they were designed to solve a totally
different problem.

Kiobufs were always intended to represent logical buffers --- a virtual
address range from some process, or a region of a cached file.  The
purpose behind them was, if you remember, to allow something like
map_user_kiobuf() to produce a list of physical pages from the user VA
range.

This works exactly as intended.  The raw IO device driver may build a
kiobuf to represent a user VA range, and the XFS filesystem may build
one for its pagebuf abstraction to represent a range within a file in
the page cache.  The lower level IO routines just don't care where the
buffers came from.

There are still problems here --- the encoding of block addresses in
the list, dealing with a stack of completion events if you push these
buffers down through various layers of logical block device such as
raid/lvm, carving requests up and merging them if you get requirest
which span a raid or LVM stripe, for example.  Kiobufs don't solve
those, but neither do skfrags, and neither does the MSG_MORE concept.

If you want a scatter-gather list capable of taking individual
buffer_heads and merging them, then sure, kiobufs won't do the trick
as they stand now: they were never intended to.  The whole point of
kiobufs was to encapsulate one single buffer in the higher layers, and
to allow lower layers to work on that buffer without caring where the
memory came from.  

But adding the sub-page sg lists is a simple extension.  I've got a
number of raw IO fixes pending, and we've just traced the source of
the last problem that was holding it up, so if you want I'll add the
per-page offset/length with those. 

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

Re: Ingo's RAID patch for 2.2.18 final?

[Andrea Arcangeli]

On Thu, Jan 11, 2001 at 03:36:13PM -0600, Jens Petersohn wrote:
> My appologies if this has been asked before. I'm looking for
> Ingo Molnar's RAID patch for 2.2.18-final. I tried applying A2, but
> it has a number of conflicts in raid1.c which I cannot resolve in
> my meager spare time.

I had to fix those things myself too. However I stay on top of 2.2.19pre7 not
on top of 2.2.18. Raid 0.90 is included into 2.2.19pre7aa1:


ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.2/2.2.19pre7aa1.bz2

The single raid patch can be downloaded from the the below link but it's going
to reject too if applied on top of 2.2.19pre7 because of lvm that is applied
first (it is equivalent to the raid-2.2.18-A2).


ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.2/2.2.19pre7aa1/93_raid-2.2.18-A2_2.2.19pre7aa1-5.bz2

Then later on the generic-map patch changes both lvm and raid to make them
stackable (also for GFS).

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

Linux 2.4.0ac7

[Alan Cox]

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

2.4.0-ac7
o   Export a KMALLOC_MAXSIZE for drivers to check   (Hans Grobler)
| this is needed to verify things like firmware
| sizes passed by users
o   Fix highmem compile issues  (Ingo Molnar)
o   Fix kmalloc check missing in hades-pci  (Hans Grobler)
o   Fix kmalloc fail crash in sdla_ppp  (Hans Grobler)
o   cfi locking fixes   (Hans Grobler)
o   Fix missing spin_unlock_irq in hd6457x.c(Hans Grobler)
o   Fix lmc_main missing skb_unlock on error case   (Hans Grobler)
o   Handle out of memory on lanstreamer (Hans Grobler)
o   Bring cs46xx.c into working state for non   (Hans Grobler)
module. Fix locking
o   Fix filesystem locking documentation(Al Viro)
o   Fusion driver updates   (Steve Ralston)
o   Correct netfilter url   (Rusty Russell)
o   rcpci45 fix the pci_table name (again)  (Hans Grobler)
o   Fix scsi option ordering bug noted by   (Michael Zieger)
o   Config.h include updates(Niels Jensen)
o   LFS handling cleanup, move some checks to   (Al Viro)
vmtruncate
o   Fix missing s->maxbytes setup for procfs(me)
o   Replace epic100 patches with alternatives   (Jeff Garzik)
o   eepro fixes for older cards (Aristeu Sergio
 Rozanski Filho)
o   Buz error handling fix  (Hans Grobler)
o   DGRS driver cleanups/kmalloc checks (Arnaldo Carvalho 
de Melo)
o   Fix ioremap leak in zr36120 (Hans Grobler)
o   FIx iounmap leaks in Stradis driver (Hans Grobler)
o   Further mtd fixes   (David Woodhouse)
o   Update yellowfin driver (Jeff Garzik, from
 Don Beckers drivers)
o   Fix iounmap bugs in vga16   (Hans Grobler)
o   TCP odd error fix   (Dave Miller)
o   ll_rw_blk enhancements  (Jens Axboe)
o   DMFE driver cleanup (Pavel Rabel)
o   iucv fix for S/390 build when non SMP   (Ulrich Weigand)
o   Merge linus -pre2
o   Fix ixj kmalloc checks  (Ingo Molnar)
o   Fix null pointer check in ibm partition code(Ingo Molnar)
o   Fix kmalloc check in pc_keyb(Ingo Molnar)
o   Fix kmalloc check in atari_pamsnet  (Ingo Molnar)
o   Fix kmalloc check in 3c515  (Ingo Molnar)
o   Tidy up defxx/fix module locks etc  (Jeff Garzik)
o   Fix kmalloc check in atari_bionet   (Ingo Molnar)
o   Fix kmalloc check in olympic driver (Ingo Molnar)
o   Fix kmalloc checks in avmb1 driver  (Ingo Molnar)
o   Tokenring needs to be an object file as its (Jeff Garzik)
using initcalls

2.4.0-ac6
o   Sunrpc locking fix  ()
o   Made agpgart smarter about i815 (Charles McLachlan)
o   Speed up truncate for shmem and clean up(Christoph Rohland)
o   Fix kmalloc test in udf (Ingo Molnar)
o   Fix ramfs kmalloc testing   (Ingo Molnar)
o   Fix irq and sense handling bugs in S/390(Holger Smolinksi)
o   Fix string.h for userspace accidental include   (me)
| noted by Ulrich Weigand
o   Red Hat office move (David Woodhouse)
o   Fix missing highmem includes(Jens Axboe)
o   Fix nfs_flushd deadlock (Andrew Morton)
o   Honour owner in mpu401  (Chris Rankin)
o   Fix raid5 kmalloc check (Ingo Molnar)
o   Export mmu_cr4_features (Adam J Richter)
o   Update ide floppy maintainer(Paul Bristow)
o   Fix IP_ADD_MEMBERSHIP case  (Stefan Jonsson)
o   Wavelan resource leak fixes (Hans Grobler)
o   Fix spinlock error introduced from 2.4.1pre (Benjamin Redelings)
o   Fix u32 classifier possible hang(Dave Miller)
o   Further warning fixes   (Rich Baum)
o   RCPCI driver further cleanups   (Rasmus Andersen)
o   Remove unneeded test from rlimit code   (Hans Grobler)
o   Generate header file tags as well as code   (Hans Grobler)
o   Fix ppp_generic label problem   (William Lee Irwin)
o 

ENOMEM on socket writes

[Paul Mackerras]

Using 2.4, and the prereleases since about early December or so, I
have been seeing rsync dying with an error "write: unable to allocate
memory".  Rsync is writing on a socket which is set non-blocking and
the write is apparently returning ENOMEM.

Is this actually a new behaviour, or just something which was possible
all along but which has been made more likely by the recent VM
changes?

>From the point of view of the application, ENOMEM is a little hard to
deal with constructively.  Select will say that the socket is
writable, so there doesn't seem to be a good way of waiting until the
write has a chance of succeeding.  About the only thing that I can see
to do is just to spin trying the write over and over - does anyone
have a better idea?

Paul.

-- 
Paul Mackerras, Open Source Research Fellow, Linuxcare, Inc.
+61 2 6262 8990 tel, +61 2 6262 8991 fax
[EMAIL PROTECTED], http://www.linuxcare.com.au/
Linuxcare.  Support for the revolution.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

2.4.1-pre2: q: EXPORT_SYMBOL(rpc_release_task) and mmu_cr4_features

[Bjoern Kriews]

--- linux-2.4.1-pre2-rfs-i/arch/i386/kernel/i386_ksyms.c~   Thu Dec 
7 06:00:12 2000
+++ linux-2.4.1-pre2-rfs-i/arch/i386/kernel/i386_ksyms.cFri Jan
12 01:58:37 2001
@@ -71,6 +71,8 @@
 EXPORT_SYMBOL(apm_info);
 EXPORT_SYMBOL(gdt);
 
+EXPORT_SYMBOL(mmu_cr4_features);
+
 EXPORT_SYMBOL_NOVERS(__down_failed);
 EXPORT_SYMBOL_NOVERS(__down_failed_interruptible);
 EXPORT_SYMBOL_NOVERS(__down_failed_trylock);
--- linux/net/sunrpc/sunrpc_syms.c~ Sat Apr 22 01:08:52 2000
+++ linux/net/sunrpc/sunrpc_syms.c  Fri Jan 12 01:50:10 2001
@@ -36,6 +36,7 @@
 EXPORT_SYMBOL(rpciod_up);
 EXPORT_SYMBOL(rpc_new_task);
 EXPORT_SYMBOL(rpc_wake_up_status);
+EXPORT_SYMBOL(rpc_release_task);
 
 /* RPC client functions */
 EXPORT_SYMBOL(rpc_create_client);
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: Where did vm_operations_struct->unmap in 2.4.0 go?

[Ingo Oeser]

On Fri, Jan 12, 2001 at 12:14:44AM +1100, Keith Owens wrote:
> >What happens when we get a loop in init order because of binding and other init
> >order conflicts?
> 
> The kernel does not support circular dependencies between providers and
> consumers.  It does not matter whether they are built into vmlinux or
> loaded as modules, there can be no loops in the directed graph of
> dependencies.  It just does not make sense.

So why don't we use sth. like depmod for these issues and get the
link order automagically (like we get module load order)?

Keith: Perhaps you could explain, why this is impossible.

Regards

Ingo Oeser
-- 
10.+11.03.2001 - 3. Chemnitzer LinuxTag 
    come and join the fun   
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: [2.2.18] outgoing connections getting stuck in SYN_SENT

[Mark Longair]

On Thursday 11 January, Richard B. Johnson wrote ("Re: [2.2.18] outgoing connections 
getting stuck in SYN_SENT"):
[...]
> You probably compiled your kernel with "CONFIG_INET_ECN" set.
> If so, you need to turn it OFF in /proc/sys/net/...something_ecn.

I don't have an ECN option available in this kernel (2.2.18) - I
thought it only appeared in 2.3...

> Many/most/all servers are "not ready for prime time" and will
> reject packets that have "strange" bits set.
[...]

I compiled in the QoS support - could that possibly cause a similar
effect?  I'm not actually using the QoS tools at the moment, but I
intend to soon.  I'll post the selected options in my .config if that
would be helpful.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: [patch] Re: That horrible hack from hell called A20

[Kai Germaschewski]

On Wed, 10 Jan 2001, rdunlap wrote:

> Here's a patch to 2.2.19-pre7 that is essentially a backport of the
> 2.4.0 gate-A20 code.
>
> This speeds up booting on my fast-A20 board (Celeron 500 MHz, no KBC)
> from 2 min:15 seconds to .
>
> Kai, you reported that your system was OK with 2.4.0-test12-pre6.
> Does that mean that it's OK with 2.4.0-final also?

Yes, i would have complained otherwise ;-)

> Comments?  Should we be merging Peter's int 0x15-first patch with this?
> And test for A20-gated after each step, before going to the next
> method?  Get that working and then backport it to 2.2.19?
> Have their been any test reports on Peter's last patch?  I didn't see
> any, but if that should be the goal, I'll give it a whirl.
>
> I'd like to see this applied to 2.2.19.  At least changing the long
> delay so that it doesn't appear that Linux isn't going to boot...

For what it's worth, 2.2.19pre7+your patch works fine here (across
suspend).

--Kai




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

[PATCH] fix nfs as module on 2.4.0-pre2

[Kai Germaschewski]

Obvious, I guess.

--Kai

diff -ur linux-2.4.1-pre2/net/sunrpc/sunrpc_syms.c 
linux-2.4.1-pre2-makefixes-3/net/sunrpc/sunrpc_syms.c
--- linux-2.4.1-pre2/net/sunrpc/sunrpc_syms.c   Sat Apr 22 01:08:52 2000
+++ linux-2.4.1-pre2-makefixes-3/net/sunrpc/sunrpc_syms.c   Fri Jan 12 01:00:40 
+2001
@@ -35,6 +35,7 @@
 EXPORT_SYMBOL(rpciod_down);
 EXPORT_SYMBOL(rpciod_up);
 EXPORT_SYMBOL(rpc_new_task);
+EXPORT_SYMBOL(rpc_release_task);
 EXPORT_SYMBOL(rpc_wake_up_status);

 /* RPC client functions */



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

Re: [patch] Re: That horrible hack from hell called A20

[H. Peter Anvin]

I think the way to go is to do the INT 15-first; possibly augmented with
a "test before even doing INT 15"...

-hpa


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

Re: QUESTION: Network hangs with BP6 and 2.4.x kernels, hardware related?

[Frank de Lange]

On Thu, Jan 11, 2001 at 02:23:53PM -0500, Jeff Garzik wrote:
> Just out of curiosity, if you boot a Linux 2.4.0 kernel with the
> "noapic" command line option, does behavior improve?

For the curious, here's a summary of some tests I did:

apic, 2 cpu's, no smp affinity -> network hangs under load
apic, maxcpus=1, no smp affinity -> network hangs under load
apic, 2 cpu's, smp affinity for all irq's on CPU1 -> network hangs under load
noapic, 2 cpu's, no smp affinity -> NO HANG, WORKSFORME

Quick and dirty conclusion: as soon as the apic comes in to play, things get
messy...

ps. load == 2 simultaneous nfs cp -rd  sessions and streaming
esd audio over the network

Cheers//Frank
-- 
  W  ___
 ## o o\/ Frank de Lange \
 }#   \|   /  \
  ##---# _/   \
      \  +31-320-252965/
   \[EMAIL PROTECTED]/
-
 [ "Omnis enim res, quae dando non deficit, dum habetur
et non datur, nondum habetur, quomodo habenda est."  ]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: [2.2.18] outgoing connections getting stuck in SYN_SENT

[Richard B. Johnson]

On Fri, 12 Jan 2001, Mark Longair wrote:

> I'm having a problem where twice a day or so, any new tcp connection
> it gets stuck in SYN_SENT.  Eventually this situation rights itself,
> but obviously in the meantime many services (e.g. squid, X) are
> broken.  The machine does IP masquerdading with ipchains, and
> masqueraded connections through it seem to be unaffected.  The kernel
> version is 2.2.18, although the same happened with 2.2.17.
> 
[SNIPPED]

You probably compiled your kernel with "CONFIG_INET_ECN" set.
If so, you need to turn it OFF in /proc/sys/net/...something_ecn.

Many/most/all servers are "not ready for prime time" and will
reject packets that have "strange" bits set.


Cheers,
Dick Johnson

Penguin : Linux version 2.4.0 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]
Please read the FAQ at http://www.tux.org/lkml/

RESEND: [ PATCH ] externalize (new) scsi timer function

[Matthew Jacob]

I sent this about a month ago. I think it's important. For what it's worth,
Doug Gilbert thought it was a good idea too. Can you please reconsider and
drop it in.

-

Late in the game, and possibly questionable, but it would be helpful to have
the (new) scsi timer functions externalized so that loadable HBA modules can
easily see them.

This is needed because, particularly for Fibre Channel, it's only the HBA that
knows when a command is actually sent to the device as opposed to being
(temporarily) queued up locally while some Fibre Channel or SCSI reset
wreckage is being cleared. The time limit for a command should be while it's
actually active- not while it's waiting to be started.

The alternative of returning commands as having not been queued doesn't work
as well because of race conditions. You can, with several type os HBA, get
cases of having queued up one or more commands and after returning success to
the midlayer, still get an interrupt that says, "that command you thought I
started? Ooops... Sorry. I lied. I couldn't get it started, but it's really
okay to start it now...".

At any rate- it's a minor change, which I've been using for a bit, which
really only is an aid to the case that you have a loadable module that wants
this symbol (natuarally, resident drivers don't care). The only real downside
to any of this is that effectively use the scsi_add_timer to restart a timer

is that you have to use a portion of the Scsi_Cmnd that is not marked as
public. An alternative could be to change the midlayer to add a function to
pause and restart the timer.

-matt

--- linux.orig/drivers/scsi/scsi_syms.c Wed Nov 29 18:19:45 2000
+++ linux/drivers/scsi/scsi_syms.c Wed Nov 29 18:18:35 2000
@@ -91,3 +91,10 @@
 EXPORT_SYMBOL(scsi_devicelist);
 EXPORT_SYMBOL(scsi_device_types);

+/*
+ * Externalize timers so that HBAs can safely start/restart commands.
+ */
+extern void scsi_add_timer(Scsi_Cmnd *, int, void ((*) (Scsi_Cmnd *)));
+extern int scsi_delete_timer(Scsi_Cmnd *);
+EXPORT_SYMBOL(scsi_add_timer);
+EXPORT_SYMBOL(scsi_delete_timer);



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

Re: Ingo's RAID patch for 2.2.18 final?

[Matthias Kilian]

On Thu, 11 Jan 2001, Takacs Sandor wrote:

> If I see it there is no raid patch for 2.2.18 final, only
> 2.2.18pre13. This patch (raid-2.2.18-A2) rejects some diffs. I will apply
> it by hand :)

I've allready done it:
http://www.escape.de/users/outback/linux/raid-2.2.18.bz2

But it's untested, since I'm now using 2.4.0 :-)

Bye,
Kili

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

Critical compile bug: 2.4.1-pre2 alpha

[Shawn Starr]

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

On compiling (and recompiling) i get this fatal error. This function
does not exist anymore?

Shawn Starr.


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

[2.2.18] outgoing connections getting stuck in SYN_SENT

[Mark Longair]

I'm having a problem where twice a day or so, any new tcp connection
it gets stuck in SYN_SENT.  Eventually this situation rights itself,
but obviously in the meantime many services (e.g. squid, X) are
broken.  The machine does IP masquerdading with ipchains, and
masqueraded connections through it seem to be unaffected.  The kernel
version is 2.2.18, although the same happened with 2.2.17.

I can't work out what's causing this to happen, or how to fix it when
it occurs, short of rebooting.  (Killing off daemons, lowering and
raising the network interfaces, etc. have no effect on the problem.)
It is still possible to connect to the computer (e.g. with ssh) while
the problem is happening.  I'm logging all packets that are rejected
by the ipchains setup, but no rejected packets appear in the logs when
you attempt an outgoing connection.

I've included a tcpdump of an attempt to `wget http://www.yahoo.com/'
while the problem is occuring.  (This is a dump of the external
network interface, an EtherExpress Pro100.)  AIUI, the first two lines
are as you would expect, but then it tells the server that the
external interface is unreachable.  I'm not sure what this means; that
address can still be pinged from everywhere.

I've searched around for similar problems on this list, the web and
dejanews, but I haven't found anything that has helped.  I'd be very
grateful for any suggestions - my apologies if I've missed something
obvious.

cheers
mark

This output is from `tcpdump -i eth0 -vvv | grep yahoo' just before
`wget http://www.yahoo.com/':

18:38:15.361774 starfruit.iw3d.co.uk.2327 > www9.dcx.yahoo.com.www: S 
2996758185:2996758185(0) win 32120  (DF) (ttl 
64, id 14541)
18:38:15.465524 www9.dcx.yahoo.com.www > starfruit.iw3d.co.uk.2327: S 
3898083689:3898083689(0) ack 2996758186 win 17520  (DF) [tos 0x60] (ttl 44, 
id 51680)
18:38:15.472910 starfruit.iw3d.co.uk > www9.dcx.yahoo.com: icmp: host 
starfruit.iw3d.co.uk unreachable [tos 0xc0] (ttl 255, id 14557)
18:38:15.472943 starfruit.iw3d.co.uk > www3.dcx.yahoo.com: icmp: host 
starfruit.iw3d.co.uk unreachable [tos 0xc0] (ttl 255, id 14558)
18:38:18.352908 starfruit.iw3d.co.uk.2327 > www9.dcx.yahoo.com.www: S 
2996758185:2996758185(0) win 32120  (DF) (ttl 
64, id 14564)
18:38:18.456461 www9.dcx.yahoo.com.www > starfruit.iw3d.co.uk.2327: . ack 1 win 17520 
(DF) [tos 0x60] (ttl 44, id 57794)
18:38:18.463769 www9.dcx.yahoo.com.www > starfruit.iw3d.co.uk.2327: S 
3898083689:3898083689(0) ack 2996758186 win 17520  (DF) [tos 0x60] (ttl 44, 
id 57809)
18:38:20.602904 starfruit.iw3d.co.uk.2325 > www3.dcx.yahoo.com.www: S 
2983862334:2983862334(0) win 32120  (DF) (ttl 
64, id 14569)
18:38:20.729037 www3.dcx.yahoo.com.www > starfruit.iw3d.co.uk.2325: . ack 2983862335 
win 17520 (DF) [tos 0x60] (ttl 44, id 49883)
18:38:21.145902 www3.dcx.yahoo.com.www > starfruit.iw3d.co.uk.2325: S 
992130302:992130302(0) ack 2983862335 win 17520  (DF) [tos 0x60] (ttl 44, id 
50913)
18:38:21.452904 starfruit.iw3d.co.uk > www3.dcx.yahoo.com: icmp: host 
starfruit.iw3d.co.uk unreachable [tos 0xc0] (ttl 255, id 14570)
18:38:21.452920 starfruit.iw3d.co.uk > www3.dcx.yahoo.com: icmp: host 
starfruit.iw3d.co.uk unreachable [tos 0xc0] (ttl 255, id 14571)
18:38:24.352902 starfruit.iw3d.co.uk.2327 > www9.dcx.yahoo.com.www: S 
2996758185:2996758185(0) win 32120  (DF) (ttl 
64, id 14573)
18:38:24.457700 www9.dcx.yahoo.com.www > starfruit.iw3d.co.uk.2327: . ack 1 win 17520 
(DF) [tos 0x60] (ttl 44, id 4335)
18:38:24.468653 www9.dcx.yahoo.com.www > starfruit.iw3d.co.uk.2327: S 
3898083689:3898083689(0) ack 2996758186 win 17520  (DF) [tos 0x60] (ttl 44, 
id 4354)
18:38:24.727569 www3.dcx.yahoo.com.www > starfruit.iw3d.co.uk.2326: S 
1025447007:1025447007(0) ack 2988099611 win 17520  (DF) [tos 0x60] (ttl 44, 
id 59842)
18:38:25.092905 starfruit.iw3d.co.uk > www3.dcx.yahoo.com: icmp: host 
starfruit.iw3d.co.uk unreachable [tos 0xc0] (ttl 255, id 14574)
18:38:25.092924 starfruit.iw3d.co.uk > www9.dcx.yahoo.com: icmp: host 
starfruit.iw3d.co.uk unreachable [tos 0xc0] (ttl 255, id 14575)

This is the start of the output of `netstat -ape' from another
occasion when the problem occurred - I've snipped most of the (very
similar) output; any new outgoing connections get into the same
SYN_SENT, one byte in Send-Q state that the fetchmail daemons at the
top are in.

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address   Foreign Address State   User   
Inode  PID/Program name   
tcp0  1 starfruit.iw3d.co.:2391 mango.iw3d.co.uk:pop3   SYN_SENTmark   
11996  828/fetchmail   
tcp0  1 starfruit.iw3d.co.:2387 eidosnet.co.uk:pop3 SYN_SENTmjs
11739  493/fetchmail   
tcp0  1 starfruit.iw3d.co.:2384 mango.iw3d.co.uk:pop3   SYN_SENTmjs
11594  493/fetchmail   
tcp0  1 starfruit.iw3d.co.:2383 mango.iw3d.co.uk:pop3   SYN_SENTmark   
11590  

kernel.org signer broken?

[Jeremy M. Dolan]

The signature on man-pages-1.34.tar.gz is bad:

  gpg: Signature made Sun Dec 24 10:56:01 2000 CST using DSA key ID
   517D0F0E
  gpg: BAD signature from "Linux Kernel Archives Verification Key
   <[EMAIL PROTECTED]>"

I retrieved the man pages from ftp.kernel.org and ftp.us.kernel.org
with ftp(1) from NetKit and lftp. The md5sum's of all match:

13d544485d6021e3b0585ad963bfd814  man-pages-1.34.tar.gz
29f314640ef28a47f0ed15247c1efcd7  man-pages-1.34.tar.gz.sign

(transfered the .sign file in both bin and ascii modes, no differance)

Everything else I've gotten recently has had a valid signature;
linux-2.4.0.tar.gz and patch-2.4.1-pre1.gz.

Since man pages can be used as trojans, this may be a problem.

-- 
Jeremy M. Dolan <[EMAIL PROTECTED]>
OpenPGP key = http://turbogeek.org/openpgp-key
OpenPGP fingerprint = 494C 7A6E 19FB 026A 1F52  E0D5 5C5D 6228 DC43 3DEE
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: Cannot compile my kernel due to unpredictible situations:

[Yin Tan Cui]

On Thu, 11 Jan 2001, Gregg Lloyd wrote:

>Hi,
>I have downloaded linux kernel 2.4.
>In /usr/src, I did untar the file:
>gzip -cd  linux-2.4.0.tar.gz  | tar xvf -
>I see several files being copied to several locations (/linux/Documentation,
>/linux/arch/..etc..). The problem is that there's no linux 2.4   directory created
>under /usr/src or anywhere else on my system! Anyway, there's nothing new
>under /usr/src!!!

I guess it has overwrite the files in /usr/src/linux which is the link to
your linux-2.2.5. this is why you did not see any new file/dir created.

>how can I make sure that I  am  re-compiling my kernel (currently kernel 2.2.5) with
>the right 2.4 kernel?? (Kernel howto talks about going to /usr/src/linux and
>start compiling..but current /usr/src/linux is a link to my current 2.2.5
> kernel !!!)

but the files in /usr/src/linux has probably being overwritten by files
from 2.4.0.

you should always remove the link /usr/src/linux before you untar the
kernel under /use/src or untar it in some other directory and rename it
and then move it under /usr/src.

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

Re: Cannot compile my kernel due to unpredictible situations:

[J . A . Magallon]

On 2001.01.12 Gregg Lloyd wrote:
> the right 2.4 kernel?? (Kernel howto talks about going to /usr/src/linux and
> start compiling..but current /usr/src/linux is a link to my current 2.2.5
> kernel !!!)
> 
So you have just wrote kernel2.4 OVER your kernel2.2.

Kernel tarballs always untar and give a directory named 'linux'. So suppose
you have a setup like:
ls /usr/src:
linux -> linux-2.2.5
linux-2.2.5

If you untar linux-2.4.0.tar.gz in /usr/src, it writes over 'linux' that points
to you 2.2.5.
What I usually do is
rm -f linux (is just a link)
gtar zxf linux-2.4.0.tar.gz (gives a new REAL directory named 'linux')
mv linux linux-2.4.0
ln -s linux-2.4.0 linux

I don't know why kernels are not tarred as linux-X.X.X, but there will be
a reason, I suppose... (that will ease very much everyone's life).

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

Linux werewolf 2.4.0-ac5 #1 SMP Wed Jan 10 23:36:11 CET 2001 i686

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

Re: 2.4.0 Keyboard and mouse lock

[Andrea Ferraris]

> > I don't know if it's the 2.4.0 I installed since few days, but before I
> never seen that on my PC.
>
> The PC (RH 6.2 + updates), looked fully freezed and Sysreq didn't
> work. 

Sorry, It couldn't: the sysreq value in /proc/kernel/sysreq was 0, as the log 
says. So maybe it could work and it's a semistandard thing with Netscape
and and maybe the mouse on my PC (I already seen that), but also ALT+FX
didn't work.

Andrea

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

Cannot compile my kernel due to unpredictible situations:

[Gregg Lloyd]

Hi,
I have downloaded linux kernel 2.4. 
In /usr/src, I did untar the file: 
gzip -cd  linux-2.4.0.tar.gz  | tar xvf - 
I see several files being copied to several locations (/linux/Documentation, 
/linux/arch/..etc..). The problem is that there's no linux 2.4   directory created 
under /usr/src or anywhere else on my system! Anyway, there's nothing new 
under /usr/src!!! 
Linux is not new to me, so I know that this is weird ( I even tried it with  "tar 
-zxvf  linux-2.4.0.tar.gz", "gzcat  linux-2.4.0.tar.gz | tar xvf - " ..etc). Same 
result. 
Anyway, let's say that it doesn't matter whether there's a new kernel 2.4 directory or 
not..
how can I make sure that I  am  re-compiling my kernel (currently kernel 2.2.5) with 
the right 2.4 kernel?? (Kernel howto talks about going to /usr/src/linux and start 
compiling..but current /usr/src/linux is a link to my current 2.2.5 kernel !!!)

Current OS: Red Hat Linux 6.0 Kernel 2.2.5

Thanks



Get your small business started at Lycos Small Business at 
http://www.lycos.com/business/mail.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: Strange umount problem in latest 2.4.0 kernels

[J . A . Magallon]

On 2001.01.11 [EMAIL PROTECTED] wrote:
> > The "none" bit puzzles me the most.
> 
> It is a common misconfiguration. Given a line
> 
>   device  dir  type  options  garbage
> 
> in /etc/fstab, some umount versions will complain "device busy"
> when the umount fails. Thus, it is better to use
> 
>   proc/proc proc
>   devpts  /dev/pts  devpts
> 
> instead of
> 
>   none/proc proc
>   none/dev/pts  devpts
> 
> so as to avoid this silly "none busy".
> But many distributions come misconfigured like this.
> 

Same cam be applied to shm ? Thus kernel Documentation/Changes should be
changed:

System V shared memory is now implemented via a virtual filesystem.
You do not have to mount it to use it. SYSV shared memory limits are
set via /proc/sys/kernel/shm{max,all,mni}.  You should mount the
filesystem under /dev/shm to be able to use POSIX shared
memory. Adding the following line to /etc/fstab should take care of
things:

none/dev/shmshm defaults0 0

to

shm/dev/shmshm defaults0 0


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

Linux werewolf 2.4.0-ac5 #1 SMP Wed Jan 10 23:36:11 CET 2001 i686

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

2.4.0 Keyboard and mouse lock

[Andrea Ferraris]

I don't know if it's the 2.4.0 I installed since few days, but before I never 
seen that on my PC.

The PC (RH 6.2 + updates), looked fully freezed and Sysreq didn't
work. I had a Netscape window on my screen. The mouse didn't move.

I login without problem from another PC. I tried to kill the X server, but 
without issue, it is the server died, but the screen, the keyboard and the 
mouse stayed in the same unusable state.

The reboot was OK. If that could be of interested I attach the part of 
/var/log/message (p file) since the boot previous such keyboard and mouse 
lock and the .configure of my 2.4.0.

Andrea

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

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

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

#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
CONFIG_M686=y
# CONFIG_M686FXSR is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_X86_TSC=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_PGE=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
# CONFIG_TOSHIBA is not set
CONFIG_MICROCODE=y
# CONFIG_X86_MSR is not set
CONFIG_X86_CPUID=m
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
CONFIG_MTRR=y
# CONFIG_SMP is not set
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_LOCAL_APIC=y

#
# General setup
#
CONFIG_NET=y
# CONFIG_VISWS is not set
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_NAMES=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
CONFIG_HOTPLUG=y

#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
CONFIG_BINFMT_AOUT=m
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=m
CONFIG_PM=y
# CONFIG_ACPI is not set
CONFIG_APM=y
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
# CONFIG_APM_DO_ENABLE is not set
# CONFIG_APM_CPU_IDLE is not set
# CONFIG_APM_DISPLAY_BLANK is not set
# CONFIG_APM_RTC_IS_GMT is not set
# CONFIG_APM_ALLOW_INTS is not set
# CONFIG_APM_REAL_MODE_POWER_OFF is not set

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

#
# Parallel port support
#
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_PC_FIFO=y
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_AMIGA is not set
# CONFIG_PARPORT_MFC3 is not set
# CONFIG_PARPORT_ATARI is not set
# CONFIG_PARPORT_SUNBPP is not set
# CONFIG_PARPORT_OTHER is not set
CONFIG_PARPORT_1284=y

#
# Plug and Play configuration
#
CONFIG_PNP=y
CONFIG_ISAPNP=y

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

#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
CONFIG_MD_RAID1=y
# CONFIG_MD_RAID5 is not set
CONFIG_MD_BOOT=y
CONFIG_AUTODETECT_RAID=y
CONFIG_BLK_DEV_LVM=m
CONFIG_LVM_PROC_FS=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_NETLINK=y
CONFIG_RTNETLINK=y
CONFIG_NETLINK_DEV=y
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_FILTER=y
CONFIG_UNIX=y
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_RTNETLINK=y
CONFIG_NETLINK=y
CONFIG_IP_MULTIPLE_TABLES=y
# CONFIG_IP_ROUTE_FWMARK is not set
CONFIG_IP_ROUTE_NAT=y
# CONFIG_IP_ROUTE_MULTIPATH is not set
CONFIG_IP_ROUTE_TOS=y
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_ROUTE_LARGE_TABLES is not set
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
# CONFIG_ARPD is not set
# CONFIG_INET_ECN is not set
CONFIG_SYN_COOKIES=y

#
#   IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
CONFIG_IP_NF_FTP=m
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_MAC=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_UNCLEAN=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_MIRROR=m
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_MARK=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_COMPAT_IPCHAINS=m

Re: Ingo's RAID patch for 2.2.18 final?

[Takacs Sandor]

On Thu, 11 Jan 2001, Jens Petersohn wrote:

> > > try http://www.linuxraid.org/
> > 
> Check lower on the page. There is a patch for the patch to bring it up
> to A3. This resulting patch will apply semi-cleanly (with fuzz) to the
> final kernel.

Oh, I see it. So, mingo why not create an A3 patch for 2.2.18? :)

-- 
Takika

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

[PATCH] missing export in sunrpc_syms.c

[Alexander Viro]

rpc_release_task is required by nfs.o.

--- net/sunrpc/sunrpc_syms.cFri Apr 21 19:08:52 2000
+++ net/sunrpc/sunrpc_syms.cThu Jan 11 18:01:50 2001
@@ -36,6 +36,7 @@
 EXPORT_SYMBOL(rpciod_up);
 EXPORT_SYMBOL(rpc_new_task);
 EXPORT_SYMBOL(rpc_wake_up_status);
+EXPORT_SYMBOL(rpc_release_task);

 /* RPC client functions */
 EXPORT_SYMBOL(rpc_create_client);


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

Re: Poll and Select not scaling

[Micah Gorrell]

I would just like to thank every one for your help.  I have found the
problem and it is now working wonderfuly.

Micah

-Original Message-
From: "David Schwartz" <[EMAIL PROTECTED]>
To: "Micah Gorrell" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Date: Thursday, January 11, 2001 3:42 PM
Subject: RE: Poll and Select not scaling


>
>> I have been trying to increase the scalabilty of an email server that has
>> been ported to Linux.  It was originally written for Netware, and there
we
>> are able to provide over 30,000 connections at any given time.  On Linux
>> however select stops working after the first 1024 connections.  I have
>> changed include/linux/fs.h and updated NR_FILE to be 81920.  In test
>> applications I have been able to create well over 30,000 connections but
I
>> am unable to do either a select or a poll on them.  Does any one
>> know what I
>> can do to fix this?
>
> Multithread.
>
> DS
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to [EMAIL PROTECTED]
>Please read the FAQ at http://www.tux.org/lkml/
>
>

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

Re: Strange umount problem in latest 2.4.0 kernels

[David Ford]

"Udo A. Steinberg" wrote:

> "Udo A. Steinberg" wrote:
> >
> > The very strange stuff is umount at reboot:
> >
> > umount: none busy - remounted read-only
> > umount: /: device is busy
> > Remounting root-filesystem read-only
> > mount: / is busy
> > Rebooting.

Are you using devfs and do kernel threads have /dev/initctl open?

# lsof /dev
COMMAND PID USER   FD   TYPE DEVICE SIZE NODE NAME
init  1 root   10u  FIFO0,5   574 /dev/initctl
keventd   2 root   10u  FIFO0,5   574 /dev/initctl
kapm-idle 3 root   10u  FIFO0,5   574 /dev/initctl
kswapd4 root   10u  FIFO0,5   574 /dev/initctl
kreclaimd 5 root   10u  FIFO0,5   574 /dev/initctl
bdflush   6 root   10u  FIFO0,5   574 /dev/initctl
kupdate   7 root   10u  FIFO0,5   574 /dev/initctl
i2oevtd   8 root   10u  FIFO0,5   574 /dev/initctl
i2oblock  9 root   10u  FIFO0,5   574 /dev/initctl
khubd12 root   10u  FIFO0,5   574 /dev/initctl
khttpd   16 root   10u  FIFO0,5   574 /dev/initctl

-d



begin:vcard 
n:Ford;David
x-mozilla-html:TRUE
url:www.blue-labs.org
adr:;;
version:2.1
email;internet:[EMAIL PROTECTED]
title:Blue Labs Developer
note;quoted-printable:GPG key: http:[EMAIL PROTECTED]=0D=0A
x-mozilla-cpt:;9952
fn:David Ford
end:vcard

Re: 2.4.0-ac6: drivers/net/rcpci45.c typo

[Rasmus Andersen]

On Thu, Jan 11, 2001 at 01:06:32PM +0100, Rasmus Andersen wrote:
> On Thu, Jan 11, 2001 at 01:59:31PM +0200, Hans Grobler wrote:
> > Yes we know about this one. This is a bug that was killed, and then came
> > back to life. We're still trying to figure out how... :)
> > 
> I feel that I must step up and claim responsibility here: The patch is
> mine and I apparently messed it up. I will get back with a better one
> this evening.

Hi again.

The attached patch is against ac6 and hopefully fixes the problems
reported (I personally inspected it to make sure that the rcpci45_pci_table
stuff was correct). An updated patch against 240p2 can be found at
www.jaquet.dk/kernel/patches/rcpci.patch.gz



On closer look this patch (against ac6) might be a bit to large to 
post to linux-kernel. I will make it available at 
www.jaquet.dk/kernel/patches/rcpci.patch.ac6.gz instead.

-- 
Regards,
Rasmus([EMAIL PROTECTED])

If we do not succeed, then we run the risk of failure.
-- Vice President Dan Quayle, to the Phoenix Republican
   Forum, March 1990
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: Compatibility issue with 2.2.19pre7

[Russell King]

Andrea Arcangeli writes:
> This patch looks fine w.r.t. alignment but given the below seems called
> at runtime (not just at mount time) for performance and to save a dozen of bytes
> of kernel stack it would probably better to use the nfs_fh structure in
> 2.2.19pre7 for the in-kernel representation and to define a new structure for
> userspace message passing (defined as the nfs_fh in 2.2.19pre6). But at least
> now we see _why_ it broke ;)

Ok, this ties up 100% with my suggestion number (1), so I'm happy. ;)
   _
  |_| - ---+---+-
  |   | Russell King[EMAIL PROTECTED]  --- ---
  | | | | http://www.arm.linux.org.uk/personal/aboutme.html   /  /  |
  | +-+-+ --- -+-
  /   |   THE developer of ARM Linux  |+| /|\
 /  | | | ---  |
+-+-+ -  /\\\  |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: Ingo's RAID patch for 2.2.18 final?

[Jens Petersohn]

> 
> On Thu, 11 Jan 2001, Alan Cox wrote:
> 
> > > I tried to apply it. If I finish it I will send the patch to mingo :)
> > 
> > try http://www.linuxraid.org/
> 
> If I see it there is no raid patch for 2.2.18 final, only
> 2.2.18pre13. This patch (raid-2.2.18-A2) rejects some diffs. I will apply
> it by hand :)
> 
> -- 
> Takika

Check lower on the page. There is a patch for the patch to bring it up
to A3. This resulting patch will apply semi-cleanly (with fuzz) to the
final kernel.

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

[PATCH] free_page(0) freed pagenr 0x40000

[Hugh Dickins]

sys_mount(), and probably others, calls free_page(0) when
no page was got.  free_pages() allows for this explicitly if
CONFIG_DISCONTIGMEM, and _appears_ to allow for it generally
by testing VALID_PAGE() - but that test is inadequate, if
over 1GB of memory then pagenr 0x4 can be wrongly freed
(in i386 case).  Complicate the test, for what? or simply...

--- linux-2.4.1-pre2/mm/page_alloc.cThu Jan 11 13:44:43 2001
+++ linux/mm/page_alloc.c   Thu Jan 11 21:41:39 2001
@@ -542,14 +542,8 @@
 
 void free_pages(unsigned long addr, unsigned long order)
 {
-   struct page *fpage;
-
-#ifdef CONFIG_DISCONTIGMEM
-   if (addr == 0) return;
-#endif
-   fpage = virt_to_page(addr);
-   if (VALID_PAGE(fpage))
-   __free_pages(fpage, order);
+   if (addr != 0)
+   __free_pages(virt_to_page(addr), order);
 }
 
 /*

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

Re: Strange umount problem in latest 2.4.0 kernels

[Udo A. Steinberg]

[EMAIL PROTECTED] wrote:
> 
> These days umount is done by directory, not by device,
> since a device may be mounted multiple times, so
> I expect the silly message is gone.
> (Is your umount recent?)
> 
> [But this is only about the "none". I don't know what is
> wrong in your situation.]

My umount is 2.10r. Alan says he knows what is wrong,
so we're all curiously expecting -ac7 ;)

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

Re: Ingo's RAID patch for 2.2.18 final?

[Takacs Sandor]

On Thu, 11 Jan 2001, Alan Cox wrote:

> > I tried to apply it. If I finish it I will send the patch to mingo :)
> 
> try http://www.linuxraid.org/

If I see it there is no raid patch for 2.2.18 final, only
2.2.18pre13. This patch (raid-2.2.18-A2) rejects some diffs. I will apply
it by hand :)

-- 
Takika

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

RE: Poll and Select not scaling

[David Schwartz]

> I have been trying to increase the scalabilty of an email server that has
> been ported to Linux.  It was originally written for Netware, and there we
> are able to provide over 30,000 connections at any given time.  On Linux
> however select stops working after the first 1024 connections.  I have
> changed include/linux/fs.h and updated NR_FILE to be 81920.  In test
> applications I have been able to create well over 30,000 connections but I
> am unable to do either a select or a poll on them.  Does any one
> know what I
> can do to fix this?

Multithread.

DS

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

Re: Strange umount problem in latest 2.4.0 kernels

[Andries . Brouwer]

> The "none" bit puzzles me the most.

It is a common misconfiguration. Given a line

  device  dir  type  options  garbage

in /etc/fstab, some umount versions will complain "device busy"
when the umount fails. Thus, it is better to use

  proc/proc proc
  devpts  /dev/pts  devpts

instead of

  none/proc proc
  none/dev/pts  devpts

so as to avoid this silly "none busy".
But many distributions come misconfigured like this.

These days umount is done by directory, not by device,
since a device may be mounted multiple times, so
I expect the silly message is gone.
(Is your umount recent?)

[But this is only about the "none". I don't know what is
wrong in your situation.]

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

Re: swap size

[Andries . Brouwer]

> what's the maximum swap size

See mkswap(8), making sure you have a non-ancient page
(one that mentions Linux 2.1.117).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: bugreporting script - second try

[David Ford]

Matthias Juchem wrote:

> On Wed, 10 Jan 2001, Richard Torkar wrote:
>
> > I do not have any PPP, and no kdb installed on that machine, neither do I
> > have procinfo. Shouldn't it say N/A or not found instead of the above? The
> > ppp part is not true ;-).
>
> > Other thing I thought about was the Ctrl-D thingy when entering text.
> > What if ppl don't have any text to enter? Shouldn't is say on each line
> > that if you don't have anything to write then just write N/A and press
> > Ctrl-D? Because pressing Ctrl-D directly doesn't do any good.
>
> Could you please check the new version here:
>
>   http://www.brightice.de/src/bugreport.sh

problem: exits top level shell if no filename is specified, annoyance
aesthetics: cat: /proc/scsi/scsi: No such file or directory, simple
aesthetics:  GNU make   3.79.1,
problem:  Linux libc5 C Library  5@..
aesthetics:  Linux libc6 C Library  2.2,
problem:  Linux C++ library  27@..
problem:  Net-tools
problem:  PPPfile
aesthetics: .config, recommend stripping the ^CONFIG_ and =, combine all 'y'
and 'm'

example fix for C library:
   sed \
 '/C [lL]ibrary /!d; s/[^0-9]*\([0-9.]*\).*/\1/' \
 /lib/libc.so.6

example fix for C++ library:
   basename $(/usr/bin/ls -f /usr/i486-linux-libc5/lib/libg++.so.27 \
 |gawk '{print $NF}')

example fix for GNU make:
   make --version|sed '/version/!d; s/[^0-9]*\([0-9.]*\).*/\1/'

example fix for net-tools:
   1) hostname from sh-utils:
   hostname --version|sed '/GNU sh/!d; s/[^0-9]*\([0-9.]*\).*/\1/'
   2) ifconfig from net-tools:
  ifconfig --version 2>&1|sed '/net\-tools/!d; s/[^0-9]*\([0-9.]*\).*/\1/'

pppd requires a proper /etc/ppp/options file before printing the version, if
you have devfs and a disconnecting modem, i.e. usb modem, it must be
attached for the /dev entry or pppd will refuse to run.

I prefer using e2fsck to report the version:
   e2fsck -V 2>&1 |sed '/e2fsck/!d; s/e2fsck [^0-9]*\([0-9.]*\).*/\1/'


---
-d



begin:vcard 
n:Ford;David
x-mozilla-html:TRUE
url:www.blue-labs.org
adr:;;
version:2.1
email;internet:[EMAIL PROTECTED]
title:Blue Labs Developer
note;quoted-printable:GPG key: http:[EMAIL PROTECTED]=0D=0A
x-mozilla-cpt:;9952
fn:David Ford
end:vcard

Re: Ingo's RAID patch for 2.2.18 final?

[Alan Cox]

> I tried to apply it. If I finish it I will send the patch to mingo :)

try http://www.linuxraid.org/

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

Re: Ingo's RAID patch for 2.2.18 final?

[Takacs Sandor]

On Thu, 11 Jan 2001, Jens Petersohn wrote:

> My appologies if this has been asked before. I'm looking for
> Ingo Molnar's RAID patch for 2.2.18-final. I tried applying A2, but
> it has a number of conflicts in raid1.c which I cannot resolve in
> my meager spare time.

I tried to apply it. If I finish it I will send the patch to mingo :)

-- 
Takika

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

Re: named streams, extended attributes, and posix

[Michael Rothwell]

CORRECTION:

> existing, widely-deployed filesystems (e.g., NFS, XFS, BeFS, HFS, etc.),
NTFS---^
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: [PATCH] improved IDE OnStream support for linux 2.4

[Andre Hedrick]

Its cool with me...

On Thu, 11 Jan 2001, Marcel J.E. Mol wrote:

> Hi guys,
> 
> Below is a patch to fix some problems in the OnStream tape drive support
> in ide-tape.c.
> 
> - It implements Early Warning (e.g. retuns ENOSPC) for reaching end-of-tape. 
>   This fixes a real nasty problem when writing beyond end-of-tape, rendering
>   the 'backup' more ore less useless.
> - Includes a workaround for a read error around block 3000.
> - The module use counts were gone allowing to remove the module while it was
>   still busy.
> - Support for other IDE OnStream tape drives (e.g. DI-50).
> - A few cosmetic fixes to improve readability.
> 
> Patch is against linux 2.4.0-prerelease.
> 
> Andre: a patch for 2.2.18 is almost ready to be included in the ide patchset.
> 
> -Marcel
> -- 
>  == Marcel J.E. MolMESA Consulting B.V.
> ===-ph. +31-(0)6-54724868  P.O. Box 112
> ===-[EMAIL PROTECTED] 2630 AC  Nootdorp
> __ www.mesa.nl ---U_n_i_x__I_n_t_e_r_n_e_t The Netherlands 
>  They couldn't think of a number, so they gave me a name!
> -- Rupert Hine   http://www.ruperthine.com/
> 
> --- linux/drivers/ide/ide-tape.c.org  Wed Jan  3 00:13:40 2001
> +++ linux/drivers/ide/ide-tape.c  Thu Jan 11 22:41:36 2001
> @@ -1,5 +1,5 @@
>  /*
> - * linux/drivers/ide/ide-tape.c  Version 1.16f   Dec  15, 1999
> + * linux/drivers/ide/ide-tape.c  Version 1.17Jan, 2001
>   *
>   * Copyright (C) 1995 - 1999 Gadi Oxman <[EMAIL PROTECTED]>
>   *
> @@ -274,6 +274,18 @@
>   *   this section correctly, a hypothetical and unwanted situation
>   *is being described)
>   * Ver 1.16f Dec 15 99   Change place of the secondary OnStream header frames.
> + * Ver 1.17  Nov 2000 / Jan 2001  Marcel Mol, [EMAIL PROTECTED]
> + *   - Add idetape_onstream_mode_sense_tape_parameter_page
> + * function to get tape capacity in frames: tape->capacity.
> + *   - Add support for DI-50 drives( or any DI- drive).
> + *   - 'workaround' for read error/blank block arround block 3000.
> + *   - Implement Early warning for end of media for Onstream.
> + *   - Cosmetic code changes for readability.
> + *   - Idetape_position_tape should not use SKIP bit during
> + * Onstream read recovery.
> + *   - Add capacity, logical_blk_num and first/last_frame_position
> + * to /proc/ide/hd?/settings.
> + *   - Module use count was gone in the Linux 2.4 driver.
>   *
>   *
>   * Here are some words from the first releases of hd.c, which are quoted
> @@ -384,7 +396,7 @@
>   *   sharing a (fast) ATA-2 disk with any (slow) new ATAPI device.
>   */
>  
> -#define IDETAPE_VERSION "1.16f"
> +#define IDETAPE_VERSION "1.17"
>  
>  #include 
>  #include 
> @@ -421,7 +433,11 @@
>  #define OS_CONFIG_PARTITION  (0xff)
>  #define OS_DATA_PARTITION(0)
>  #define OS_PARTITION_VERSION (1)
> +#define OS_EW300
> +#define OS_ADR_MINREV2
>  
> +#define OS_DATA_STARTFRAME1  20
> +#define OS_DATA_ENDFRAME12980
>  /*
>   * partition
>   */
> @@ -512,12 +528,33 @@
>  } os_header_t;
>  
>  /*
> + *   OnStream Tape Parameters Page
> + */
> +typedef struct {
> + unsignedpage_code   :6; /* Page code - Should be 0x2b */
> + unsignedreserved1_6 :1;
> + unsignedps  :1;
> + __u8reserved2;
> + __u8density;/* kbpi */
> + __u8reserved3,reserved4;
> + __u16   segtrk; /* segment of per track */
> + __u16   trks;   /* tracks per tape */
> + __u8reserved5,reserved6,reserved7,reserved8,reserved9,reserved10;
> +} onstream_tape_paramtr_page_t;
> +
> +/*
>   * OnStream ADRL frame
>   */
>  #define OS_FRAME_SIZE(32 * 1024 + 512)
>  #define OS_DATA_SIZE (32 * 1024)
>  #define OS_AUX_SIZE  (512)
>  
> +/*
> + * internal error codes for onstream
> + */
> +#define OS_PART_ERROR2
> +#define OS_WRITE_ERROR   1
> +
>  #include 
>  
>  / Tunable parameters */
> @@ -949,6 +986,7 @@
>   int eod_frame_addr;
>   unsigned long cmd_start_time;
>   unsigned long max_cmd_time;
> + unsigned capacity;
>  
>   /*
>* Optimize the number of "buffer filling"
> @@ -1157,7 +1195,7 @@
>  typedef union {
>   unsigned all:8;
>   struct {
> - unsigned dma:1; /* Using DMA of PIO */
> + unsigned dma:1; /* Using DMA or PIO */
>   unsigned reserved321:3; /* Reserved */
>   unsigned 

[PATCH] improved IDE OnStream support for linux 2.4

[Marcel J.E. Mol]

Hi guys,

Below is a patch to fix some problems in the OnStream tape drive support
in ide-tape.c.

- It implements Early Warning (e.g. retuns ENOSPC) for reaching end-of-tape. 
  This fixes a real nasty problem when writing beyond end-of-tape, rendering
  the 'backup' more ore less useless.
- Includes a workaround for a read error around block 3000.
- The module use counts were gone allowing to remove the module while it was
  still busy.
- Support for other IDE OnStream tape drives (e.g. DI-50).
- A few cosmetic fixes to improve readability.

Patch is against linux 2.4.0-prerelease.

Andre: a patch for 2.2.18 is almost ready to be included in the ide patchset.

-Marcel
-- 
 == Marcel J.E. MolMESA Consulting B.V.
===-ph. +31-(0)6-54724868  P.O. Box 112
===-[EMAIL PROTECTED] 2630 AC  Nootdorp
__ www.mesa.nl ---U_n_i_x__I_n_t_e_r_n_e_t The Netherlands 
 They couldn't think of a number, so they gave me a name!
-- Rupert Hine   http://www.ruperthine.com/

--- linux/drivers/ide/ide-tape.c.orgWed Jan  3 00:13:40 2001
+++ linux/drivers/ide/ide-tape.cThu Jan 11 22:41:36 2001
@@ -1,5 +1,5 @@
 /*
- * linux/drivers/ide/ide-tape.cVersion 1.16f   Dec  15, 1999
+ * linux/drivers/ide/ide-tape.cVersion 1.17Jan, 2001
  *
  * Copyright (C) 1995 - 1999 Gadi Oxman <[EMAIL PROTECTED]>
  *
@@ -274,6 +274,18 @@
  * this section correctly, a hypothetical and unwanted situation
  *  is being described)
  * Ver 1.16f Dec 15 99   Change place of the secondary OnStream header frames.
+ * Ver 1.17  Nov 2000 / Jan 2001  Marcel Mol, [EMAIL PROTECTED]
+ * - Add idetape_onstream_mode_sense_tape_parameter_page
+ *   function to get tape capacity in frames: tape->capacity.
+ * - Add support for DI-50 drives( or any DI- drive).
+ * - 'workaround' for read error/blank block arround block 3000.
+ * - Implement Early warning for end of media for Onstream.
+ * - Cosmetic code changes for readability.
+ * - Idetape_position_tape should not use SKIP bit during
+ *   Onstream read recovery.
+ * - Add capacity, logical_blk_num and first/last_frame_position
+ *   to /proc/ide/hd?/settings.
+ * - Module use count was gone in the Linux 2.4 driver.
  *
  *
  * Here are some words from the first releases of hd.c, which are quoted
@@ -384,7 +396,7 @@
  * sharing a (fast) ATA-2 disk with any (slow) new ATAPI device.
  */
 
-#define IDETAPE_VERSION "1.16f"
+#define IDETAPE_VERSION "1.17"
 
 #include 
 #include 
@@ -421,7 +433,11 @@
 #define OS_CONFIG_PARTITION(0xff)
 #define OS_DATA_PARTITION  (0)
 #define OS_PARTITION_VERSION   (1)
+#define OS_EW  300
+#define OS_ADR_MINREV  2
 
+#define OS_DATA_STARTFRAME120
+#define OS_DATA_ENDFRAME1  2980
 /*
  * partition
  */
@@ -512,12 +528,33 @@
 } os_header_t;
 
 /*
+ * OnStream Tape Parameters Page
+ */
+typedef struct {
+   unsignedpage_code   :6; /* Page code - Should be 0x2b */
+   unsignedreserved1_6 :1;
+   unsignedps  :1;
+   __u8reserved2;
+   __u8density;/* kbpi */
+   __u8reserved3,reserved4;
+   __u16   segtrk; /* segment of per track */
+   __u16   trks;   /* tracks per tape */
+   __u8reserved5,reserved6,reserved7,reserved8,reserved9,reserved10;
+} onstream_tape_paramtr_page_t;
+
+/*
  * OnStream ADRL frame
  */
 #define OS_FRAME_SIZE  (32 * 1024 + 512)
 #define OS_DATA_SIZE   (32 * 1024)
 #define OS_AUX_SIZE(512)
 
+/*
+ * internal error codes for onstream
+ */
+#define OS_PART_ERROR2
+#define OS_WRITE_ERROR   1
+
 #include 
 
 / Tunable parameters */
@@ -949,6 +986,7 @@
int eod_frame_addr;
unsigned long cmd_start_time;
unsigned long max_cmd_time;
+   unsigned capacity;
 
/*
 * Optimize the number of "buffer filling"
@@ -1157,7 +1195,7 @@
 typedef union {
unsigned all:8;
struct {
-   unsigned dma:1; /* Using DMA of PIO */
+   unsigned dma:1; /* Using DMA or PIO */
unsigned reserved321:3; /* Reserved */
unsigned reserved654:3; /* Reserved (Tag Type) */
unsigned reserved7  :1; /* Reserved */
@@ -1287,7 +1325,9 @@
  * by ide-tape.
  */
 #defineIDETAPE_CAPABILITIES_PAGE   0x2a
+#define IDETAPE_PARAMTR_PAGE  

Re: QUESTION: Network hangs with BP6 and 2.4.x kernels, hardware related?

[Frank de Lange]

On Thu, Jan 11, 2001 at 04:47:00PM -0500, Jeff Garzik wrote:
> Are you judging based on the error message?  The 'netdev watchdog ...'
> message is a generic error message that could have any number of
> causes.  It's just saying, well, what it says :)  The kernel was unable
> to transmit a packet in a certain amount of time.  You might get these
> messages if you unplug a cable suddenly, or if your hardware isn't
> delivering interrupts, or many other things...

No, I'm judging based on the fact that I found reports from people using
NE2K-PCI with several cards as well as tulip-based cards (different driver) on
abit BP6 as well as Gigabyte motherboards, mostly on 2.3.x/2.4.x kernels. I
found some postings with these problems on 2.2.x kernels.

Cheers//Frank
-- 
  W  ___
 ## o o\/ Frank de Lange \
 }#   \|   /  \
  ##---# _/   \
      \  +31-320-252965/
   \[EMAIL PROTECTED]/
-
 [ "Omnis enim res, quae dando non deficit, dum habetur
et non datur, nondum habetur, quomodo habenda est."  ]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: QUESTION: Network hangs with BP6 and 2.4.x kernels, hardware related?

[Jeff Garzik]

Frank de Lange wrote:
> 
> OK, just one last addition to what has nearly become my own thread...
> 
> I now am fairly certain that the problem (network stalls on multiprocessor systems) 
>is not BP6 or NE2K-PCI specific. I found several postings which relate to similar 
>problems on dissimilar hardware. Another interesting one is:

>I have reported it some time ago, and now all I get with
>2.4.0-test11-pre4 and I think a additional patch is  NETDEV WATCHDOG:
>eth0: transmit timed out, and something in the console about lost irq?



Are you judging based on the error message?  The 'netdev watchdog ...'
message is a generic error message that could have any number of
causes.  It's just saying, well, what it says :)  The kernel was unable
to transmit a packet in a certain amount of time.  You might get these
messages if you unplug a cable suddenly, or if your hardware isn't
delivering interrupts, or many other things...

Jeff


-- 
Jeff Garzik   | "You see, in this world there's two kinds of
Building 1024 |  people, my friend: Those with loaded guns
MandrakeSoft  |  and those who dig. You dig."  --Blondie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: Strange umount problem in latest 2.4.0 kernels

[Andreas Dilger]

Udo, you write:
> Anyway, disabled both lpd and httpd from the startup scripts
> and now the bug is triggered *every* time. I cannot reboot
> a single time without partitions being busy. When neither
> lpd nor httpd run, fsck finds nothing wrong.
> 
> The very strange stuff is umount at reboot:
> 
> umount: none busy - remounted read-only
  
Check the output of "mount" and/or your /etc/fstab for a device called
"none".  On my system, there is devpts which has device "none", so it
is possible this is busy, and can't be unmounted, and hence root is also
busy and can't be ro remounted.  Maybe also check /proc/mounts for "none".

> umount: /: device is busy
> Remounting root-filesystem read-only
> mount: / is busy
> Rebooting.

Cheers, Andreas
-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/   -- Dogbert
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Ingo's RAID patch for 2.2.18 final?

[Jens Petersohn]

My appologies if this has been asked before. I'm looking for
Ingo Molnar's RAID patch for 2.2.18-final. I tried applying A2, but
it has a number of conflicts in raid1.c which I cannot resolve in
my meager spare time.

Thanks in advance,

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

Re: Strange umount problem in latest 2.4.0 kernels

[Alan Cox]

> I've checked a couple of other machines, different setups etc.
> all with -ac6 and all show this behavior - also the umount stuff.

Wait for -ac7 and see if that fixes it. I think I know whats up there

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

Re: [linux-audio-dev] low-latency scheduling patch for 2.4.0

[David S. Miller]

Nigel Gamble writes:
 > That's why MontaVista's kernel preemption patch uses sleeping mutex
 > locks instead of spinlocks for the long held locks.

Anyone who uses sleeping mutex locks is asking for trouble.  Priority
inversion is an issue I dearly hope we never have to deal with in the
Linux kernel, and sleeping SMP mutex locks lead to exactly this kind
of problem.

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]
Please read the FAQ at http://www.tux.org/lkml/

Re: Linux driver: __get_free_pages()

[Arnaldo Carvalho de Melo]

Em Thu, Jan 11, 2001 at 04:01:08PM -0500, Richard B. Johnson escreveu:
> If all you need is a kernel buffer to store the stuff that will be
> written to NVRAM, then just use kmalloc(). It is virtual and will

s/kmalloc/vmalloc/

> seem contiguous to your driver.

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

Re: QUESTION: Network hangs with BP6 and 2.4.x kernels, hardware related?

[Frank de Lange]

OK, just one last addition to what has nearly become my own thread...

I now am fairly certain that the problem (network stalls on multiprocessor systems) is 
not BP6 or NE2K-PCI specific. I found several postings which relate to similar 
problems on dissimilar hardware. Another interesting one is:

Re: PROBLEM : Networking stops working with kernel 2.4.0-test11 
  (http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg18722.html)

"...I have an almos identical system as you, 2x200MMX motherboard (Gigabyte
   586DX) also Voodoo3 (2000 pci) the same nic Realtek 8029AS, also a bt848
   tv card, also SCSI (Aic-7880 onboard, but not used).

   I have reported it some time ago, and now all I get with
   2.4.0-test11-pre4 and I think a additional patch is  NETDEV WATCHDOG:
   eth0: transmit timed out, and something in the console about lost irq?

   I can't reproduce it with a uniprocesor kernel, and I have a 3c503 card
   wich uses the 8390 module, so I suppose that the problem it's not in the
   8390, and it seems to be smp related"


ne2k-pci freezes with APIC error on 2.4.0-testX SMP
  (http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg14468.html)

"...

   When doing massive NFS transfers (2.4 machine as the client) on my SMP
   box
   (Abit BP6 2x celeronA 533mhz (non-overclocked) 64Mb ram, latest
   apt-get-ed
   debian woody) my ne2k-pci card (Realtek Semiconductor Co., Ltd.
   RTL-8029(AS)
(rev 0)) suddenly stops working. test5 spits that in syslog:..."

More to be found when searching the archives. This problem has been around for
a long, long time (probably since the current level of apic-support was added,
somewhere around 2.3.1x?). It has been reported by several people, several
times. I feel like rigging every apic-related piece of code with a zillion
bells and printk's but that would surely only create more mayhem as this whole
thing seems to be timing-related...

Anyone got any idea's on how to tackle this? Anyone who is 'intimate with' the
apic-related code? It'll take me some time to dive into that part, so if there
is anyone who already has taken the plunge, do tell...

Cheers//Frank

[ who is still running apic-less, without problems [
-- 
  W  ___
 ## o o\/ Frank de Lange \
 }#   \|   /  \
  ##---# _/   \
      \  +31-320-252965/
   \[EMAIL PROTECTED]/
-
 [ "Omnis enim res, quae dando non deficit, dum habetur
et non datur, nondum habetur, quomodo habenda est."  ]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

2.4.0 eth0 timeout after wake from suspend

[Mihai Christodorescu]

I jsut upgraded to 2.4.0 and I started getting eth timeouts after the machine
wakes from suspend. The sequence of log events is:

Jan 11 07:16:34 HOST apmd[420]: System Suspend
Jan 11 12:20:27 HOST kernel: PCI: Found IRQ 5 for device 00:0a.0
Jan 11 12:20:41 HOST apmd[420]: Normal Resume after 05:04:07 (-1% unknown) AC
power
Jan 11 12:20:41 HOST anacron[3599]: Anacron 2.3 started on 2001-01-11
Jan 11 12:20:41 HOST anacron[3599]: Normal exit (0 jobs run)
Jan 11 12:20:49 HOST kernel: NETDEV WATCHDOG: eth0: transmit timed out

The kernel is compiled with APM, but without ACPI support. The bios (Award
BIOS on Asus A7V motherboard) is configured to go to suspend mode, and it
support ACPI (if I compile the kernel with ACPI support, it detects the bios
support, but it no longer goes into suspend). The network card is a NetGear
FA310TX (with a DEC 21140AE chipset), and I am running it with the tulip
driver. The boot detection of the card looks like:

eth0: Lite-On 82c168 PNIC rev 32 at 0x9400, 00:A0:CC:40:B4:AD, IRQ 5.
eth0:  MII transceiver #1 config 3000 status 7829 advertising 01e1.
PPP generic driver version 2.4.1
eth0: Setting full-duplex based on MII#1 link partner capability of
41e1. 

(it says lite-on, but it is a NetGear FA310TX)

When it comes back from suspend, I have to unload the driver (modprobe -r
tulip) and load it again in order to get the network running. Kernel 2.2.17
used to wake from suspend just fine.
Any suggestions? Please CC: me ([EMAIL PROTECTED]), as I am not on the kernel
mailing list.

Thanks,

Mihai

-- 
 Mihai Christodorescu -=- [EMAIL PROTECTED] - http://www.cs.wisc.edu/~mihai
.---
|   The man of knowledge must be able not only to love his enemies but also
| to hate his friends.- Friedrich Nietzsche
`---
PGP signature block might follow.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: [eepro100] Ok, I'm fed up now

[Dragan Stancevic]

On Tue, Jan 09, 2001, Kambo Lohan <[EMAIL PROTECTED]> wrote:
; I am having the same problems, I have duplicated the hard lockups / ethernet 
; hangs on two intel 815EE boards.  It happens when send traffic through the 
; onboard eepro100 is high, and sometimes running something like vmstat 1 in 
; the background triggers the lockup faster.  When it locks up there is 
; nothing in the log, no oops or anything.  Sometimes it just hangs eth0 with 
; the (cmd timeout) msgs and an ifconfig down/up fixes it temporarily.
; 


Kambo,

can you run the driver with a high debug flag and log what is going on,
make sure you have alot of space since it talks alot.

The card seems to be locking up with a couple of commands in the register that
are not known to me, my specs don't list them, hopefully the new specs talk
about it. At this time it's not known where the command comes from, I am
working on a patch that will tell a bit more about that...


-- 
I knew I was alone, I was scared, it was getting dark and
it was a hardware problem.

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

Re: Linux driver: __get_free_pages()

[Richard B. Johnson]

On Thu, 11 Jan 2001, Paul Powell wrote:

> Our driver is trying to allocate a DMA buffer to flash
> an adapter's firmware.  This can require as much as
> 512K ( of contiguous DMA memory ). We are using the
> function __get_free_pages( GFP_KERNEL | GFP_DMA, order
> ) .  The call is failing if 'order' is greater than 6.
> The problem is seen on systems with system memory of
> only 64MB.  It works fine on systems with more memory.
>  Does it make sense that a system with 64MB would not
> have 512K ( contiguous ) available?  The most that can
> be allocated successfully on the 64MB system appears
> to be 256K.  (Nothing else is running that would eat
> up 64MB of memory).
> 
> Does this make sense and/or is there another way that
> the DMA memory could be allocated successfully?
> 

Are you sure it needs memory? Usually, you need address-space
to flash firmware. Also, in recent months, I've evaluated a
lot of NVRAM from flash to single-bit SEEPROM. I have never
seen anything that would `know` how to flash from DMA.

Typically, with NVRAM, you scribble some 0xaaa, 0x555, 0xetc, at some
specified offset, then you write a single byte/word/longword (depending
upon its addressing), at the location to program. Then you loop, waiting
for it to "take", then you do the next. All stuff you would never do with
DMA.

If all you need is a kernel buffer to store the stuff that will be
written to NVRAM, then just use kmalloc(). It is virtual and will
seem contiguous to your driver.

If you have to 'bus-master' data from your buffer to the NVRAM, you
just do it one page at a time, using the same page.

Cheers,
Dick Johnson

Penguin : Linux version 2.4.0 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]
Please read the FAQ at http://www.tux.org/lkml/

Re: Strange umount problem in latest 2.4.0 kernels

[Udo A. Steinberg]

"Udo A. Steinberg" wrote:
> 
> The very strange stuff is umount at reboot:
> 
> umount: none busy - remounted read-only
> umount: /: device is busy
> Remounting root-filesystem read-only
> mount: / is busy
> Rebooting.

I just noticed another strange effect:

ps uxa misses a couple dozen processes. Effectively I'm seeing
only the kernel processes, all gettys, rpc.portmap, bash and ps.
All other processes, all daemons etc. are invisible. If I kill
portmap another process becomes visible.

I've checked a couple of other machines, different setups etc.
all with -ac6 and all show this behavior - also the umount stuff.

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

Re: Linux driver: __get_free_pages()

[Arnaldo Carvalho de Melo]

Em Thu, Jan 11, 2001 at 12:39:33PM -0800, Paul Powell escreveu:

> Our driver is trying to allocate a DMA buffer to flash an adapter's
> firmware.  This can require as much as 512K ( of contiguous DMA memory ).
> We are using the function __get_free_pages( GFP_KERNEL | GFP_DMA, order)
> .  The call is failing if 'order' is greater than 6.  The problem is seen
> on systems with system memory of only 64MB.  It works fine on systems
> with more memory.  Does it make sense that a system with 64MB would not
> have 512K ( contiguous ) available?  The most that can be allocated
> successfully on the 64MB system appears to be 256K.  (Nothing else is
> running that would eat up 64MB of memory).
 
> Does this make sense and/or is there another way that the DMA memory
> could be allocated successfully?

look at mm/bootmem.c

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

Re: [linux-audio-dev] low-latency scheduling patch for 2.4.0

[Nigel Gamble]

On Wed, 10 Jan 2001, David S. Miller wrote:
> Opinion: Personally, I think the approach in Andrew's patch
>is the way to go.
> 
>Not because it can give the absolute best results.
>But rather, it is because it says "here is where a lot
>  of time is spent".
> 
>This has two huge benefits:
>1) It tells us where possible algorithmic improvements may
>   be possible.  In some cases we may be able to improve the
>   code to the point where the pre-emption points are no
>   longer necessary and can thus be removed.

This is definitely an important goal.  But lock-metering code in a fully
preemptible kernel an also identify spots where algorithmic improvements
are most important.

>2) It affects only code which can burn a lot of cpu without
>   scheduling.  Compare this to schemes which make the kernel
>   fully pre-emptable, causing _EVERYONE_ to pay the price of
>   low-latency.  If we were to later fine algorithmic
>   improvements to the high-latency pieces of code, we
> couldn't then just "undo" support for pre-emption because
>   dependencies will have swept across the whole kernel
>   already.
> 
> Pre-emption, by itself, also doesn't help in situations
>   where lots of time is spent while holding spinlocks.
>   There are several other operating systems which support
>   pre-emption where you will find hard coded calls to the
>   scheduler in time-consuming code.  Heh, it's almost like,
>   "what's the frigging point of pre-emption then if you
>   still have to manually check in some spots?"

Spinlocks should not be held for lots of time.  This adversely affects
SMP scalability as well as latency.  That's why MontaVista's kernel
preemption patch uses sleeping mutex locks instead of spinlocks for the
long held locks.  In a fully preemptible kernel that is implemented
correctly, you won't find any hard-coded calls to the scheduler in time
consuming code.  The scheduler should only be called in response to an
interrupt (IO or timeout) when we know that a higher priority process
has been made runnable, or when the running process sleeps (voluntarily
or when it has to wait for something) or exits.  This is the case in
both of the fully preemptible kernels which I've worked on (IRIX and
REAL/IX).

Nigel Gamble[EMAIL PROTECTED]
Mountain View, CA, USA. http://www.nrg.org/

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

Re: Compatibility issue with 2.2.19pre7

[Trond Myklebust]

> " " == Andrea Arcangeli <[EMAIL PROTECTED]> writes:

 > On Thu, Jan 11, 2001 at 07:30:49PM +0100, Trond Myklebust
 > wrote:
>> OK. In that case my patch, would just be amended to eliminate
>> the redundant comparison as is the case below.

 > This patch looks fine w.r.t. alignment but given the below
 > seems called at runtime (not just at mount time) for
 > performance and to save a dozen of bytes of kernel stack it
 > would probably better to use the nfs_fh structure in 2.2.19pre7
 > for the in-kernel representation and to define a new structure
 > for userspace message passing (defined as the nfs_fh in
 > 2.2.19pre6). But at least now we see _why_ it broke ;)

I'm not at all convinced that saving us a copy of 66 bytes in NLM is
really worth the effort. It certainly isn't worth the ugliness of
living with arrays of (void *) in order to match the alignment of a
fake pointer. I'd rather we make them integers.
If we really are to change struct nfs_fh, I therefore propose that we
also make struct nfs_fhbase reflect the fact that fb_dentry is a
32-bit cookie. That means that both nfs_fh and knfs_fh would be
integer-aligned.

The following is untested, but should be correct.

Cheers,
  Trond

diff -u --recursive --new-file linux-2.2.18/fs/lockd/svcsubs.c 
linux-2.2.18-fix_ppc/fs/lockd/svcsubs.c
--- linux-2.2.18/fs/lockd/svcsubs.c Mon Dec 11 01:49:44 2000
+++ linux-2.2.18-fix_ppc/fs/lockd/svcsubs.c Thu Jan 11 20:37:37 2001
@@ -44,6 +44,10 @@
  * Note that we open the file O_RDONLY even when creating write locks.
  * This is not quite right, but for now, we assume the client performs
  * the proper R/W checking.
+ *
+ * BEWARE:
+ * The cast to struct knfs_fh in this routine, imposes an alignment
+ * requirement on (struct nfs_fh)->data for some platforms.
  */
 u32
 nlm_lookup_file(struct svc_rqst *rqstp, struct nlm_file **result,
@@ -63,8 +67,7 @@
down(_file_sema);
 
for (file = nlm_files[hash]; file; file = file->f_next) {
-   if (file->f_handle.fh_dcookie == fh->fh_dcookie &&
-   !memcmp(>f_handle, fh, sizeof(*fh)))
+   if (!memcmp(>f_handle, fh, sizeof(*fh)))
goto found;
}
 
diff -u --recursive --new-file linux-2.2.18/fs/nfs/inode.c 
linux-2.2.18-fix_ppc/fs/nfs/inode.c
--- linux-2.2.18/fs/nfs/inode.c Mon Dec 11 01:49:44 2000
+++ linux-2.2.18-fix_ppc/fs/nfs/inode.c Thu Jan 11 21:13:04 2001
@@ -273,9 +273,8 @@
struct nfs_server   *server;
struct rpc_xprt *xprt = 0;
struct rpc_clnt *clnt = 0;
-   struct nfs_fh   *root_fh = NULL,
-   *root = >root,
-   fh;
+   struct nfs_fh   fh,
+   *root_fh = NULL;
struct inode*root_inode = NULL;
unsigned intauthflavor;
struct sockaddr_in  srvaddr;
@@ -290,7 +289,6 @@
goto failure;
}
 
-   memset(, 0, sizeof(fh));
if (data->version != NFS_MOUNT_VERSION) {
printk(KERN_WARNING "nfs warning: mount version %s than kernel\n",
data->version < NFS_MOUNT_VERSION ? "older" : "newer");
@@ -298,12 +296,21 @@
data->namlen = 0;
if (data->version < 3)
data->bsize  = 0;
-   if (data->version < 4) {
+   if (data->version < 4)
data->flags &= ~NFS_MOUNT_VER3;
-   root = 
-   root->size = NFS2_FHSIZE;
-   memcpy(root->data, data->old_root.data, NFS2_FHSIZE);
+   }
+
+   memset(, 0, sizeof(fh));
+   if (data->version < 4) {
+   fh.size = NFS2_FHSIZE;
+   memcpy(fh.data, data->old_root.data, NFS2_FHSIZE);
+   } else {
+   fh.size = (data->flags & NFS_MOUNT_VER3) ? data->root.size : 
+NFS2_FHSIZE;
+   if (fh.size > sizeof(fh.data)) {
+   printk(KERN_WARNING "NFS: mount program passes invalid 
+filehandle!\n");
+   goto failure;
}
+   memcpy(fh.data, data->root.data, fh.size);
}
 
/* We now require that the mount process passes the remote address */
@@ -351,19 +358,15 @@
if (data->flags & NFS_MOUNT_VER3) {
 #ifdef CONFIG_NFS_V3
server->rpc_ops = _v3_clientops;
-   NFS_SB_FHSIZE(sb) = sizeof(unsigned short) + NFS3_FHSIZE;
+   NFS_SB_FHSIZE(sb) = NFS3_FHSIZE;
version = 3;
-   if (data->version < 4) {
-   printk(KERN_NOTICE "NFS: NFSv3 not supported by mount 
program.\n");
-   goto failure_unlock;
-   }
 #else
printk(KERN_NOTICE "NFS: NFSv3 not supported.\n");
goto failure_unlock;
 #endif
} else {
   

Linux driver: __get_free_pages()

[Paul Powell]

Our driver is trying to allocate a DMA buffer to flash
an adapter's firmware.  This can require as much as
512K ( of contiguous DMA memory ). We are using the
function __get_free_pages( GFP_KERNEL | GFP_DMA, order
) .  The call is failing if 'order' is greater than 6.
The problem is seen on systems with system memory of
only 64MB.  It works fine on systems with more memory.
 Does it make sense that a system with 64MB would not
have 512K ( contiguous ) available?  The most that can
be allocated successfully on the 64MB system appears
to be 256K.  (Nothing else is running that would eat
up 64MB of memory).

Does this make sense and/or is there another way that
the DMA memory could be allocated successfully?


__
Do You Yahoo!?
Yahoo! Photos - Share your holiday photos online!
http://photos.yahoo.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: Poll and Select not scaling

[dean gaudet]

On Wed, 10 Jan 2001, Dan Kegel wrote:

> select() is usually limited to 1024 file descriptors

oh hey, this limit is only a libc limit these days.  you can do this:

#define MY_FD_SETSIZE (16384)
typedef struct {
__fd_mask __fds_bits[MY_FD_SETSIZE / __NFDBITS];
} my_fd_set;
#define MY_FD_ZERO(_f)  (memset((_f), 0, sizeof(my_fd_set)))

and do select()s of 16384 descriptors.

> poll() is a slightly better choice.  However, although
> it can handle 3 file descriptors, the performance sucks;
> see http://www.kegel.com/dkftpbench/Poller_bench.html#results

poll() stops working at 16384 file descriptors (as of 2.2.14-foo original
redhat 6.2 kernel).  at least that's where i think it is, maybe it's
32768.  it's limited by the maximum kmalloc() size of 128k.  this is
somewhat unfortunate.  even though we know it'll stop performing well.

-dean

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

Re: Strange umount problem in latest 2.4.0 kernels

[Udo A. Steinberg]

Alexander Viro wrote:

> > umount: none busy - remounted read-only
> 
> > The "none" bit puzzles me the most. /etc/fstab and /etc/mtab
> > look perfectly ok.
> >
> > Has anyone got an idea? Everything worked well with 2.4.0 and
> > Alan's tree up to -ac4, didn't try ac5, and ac6 is what messes
> > up now.
> 
> Try to revert to -ac4 fs/super.c and see if it helps

That makes no difference. Still acting weird. Must be something
else.

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

Re: QUESTION: Network hangs with BP6 and 2.4.x kernels, hardware related?

[Frank de Lange]

Hm, the noapic option seems to help, as I'm currently beating the network to
death but it won't die... As the problem is elusive, it is hard to tell, and it
would not surprise me if the net dropped dead the moment this mail went
through, but current indication is that noapic makes the sudden net-death
disappear.

So we're still left with the question 'is this hardware-related, or is it a
software/configuration problem'? Other people seem to have similar problems
with dissimilar hardware (tulip cards instead of Winbond, etc), on 2.2.x as
well as 2.3/4.x. As I do not run Windows (NT or 2K), I can not tell if this
problem also occurs there. And my FreeBSD-box is uniprocessor... So... has
anyone seen anything like this on other 'true' (SMP) OS's? If so, that would
indicate a hardware problem...

Cheers//Frank
-- 
  W  ___
 ## o o\/ Frank de Lange \
 }#   \|   /  \
  ##---# _/   \
      \  +31-320-252965/
   \[EMAIL PROTECTED]/
-
 [ "Omnis enim res, quae dando non deficit, dum habetur
et non datur, nondum habetur, quomodo habenda est."  ]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Re: IDE DMA problem in 2.4.0

[Adrian Bunk]

On Thu, 11 Jan 2001, Tobias Ringstrom wrote:

> When copying huge files from one disk to another (hda->hdc), I get the
> following error (after some hundred megabytes):
>
> hdc: timeout waiting for DMA
> ide_dmaproc: chipset supported ide_dma_timeout func only: 14
> hdc: irq timeout: status=0xd1 { Busy }
> hdc: DMA disabled
> ide1: reset: success
>...
> VP_IDE: VIA vt82c596b IDE UDMA66 controller on pci0:7.1
>...
> Did I miss anything?

Could you try if the (experimental) version 3.11 of the VIA IDE driver
(announced by Vojtech Pavlik in [1]) fixes your problem? Simply copy the
two files you find there to drivers/ide after you unpacked the kernel
source.

> /Tobias

cu,
Adrian

[1] http://www.lib.uaa.alaska.edu/linux-kernel/archive/2001-Week-02/0737.html


-- 
A "No" uttered from deepest conviction is better and greater than a
"Yes" merely uttered to please, or what is worse, to avoid trouble.
-- Mahatma Ghandi

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

Re: Strange umount problem in latest 2.4.0 kernels

[Alexander Viro]

On Thu, 11 Jan 2001, Udo A. Steinberg wrote:

> > /dev/hdb1: Inode 522901, i_blocks is 64, should be 8. FIXED

> umount: none busy - remounted read-only
 
> The "none" bit puzzles me the most. /etc/fstab and /etc/mtab
> look perfectly ok.
> 
> Has anyone got an idea? Everything worked well with 2.4.0 and
> Alan's tree up to -ac4, didn't try ac5, and ac6 is what messes
> up now.

Try to revert to -ac4 fs/super.c and see if it helps

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

Re: sym-2.1.0-20001230 vs. sg (cdrecord)

[Gérard Roudier]

On Thu, 11 Jan 2001, Boszormenyi Zoltan wrote:

> Hi!
> 
> I just wanted to let you know that I successfully ruined
> a CD with 2.4.0 + sym-2.1.0-20001230. The system is a RH 7.0
> with glibc-2.2-9, cdrecord-1.9.

Thanks for the report.
But with so tiny information, it gives about no usefulness to me.

> When will it be really usable?

A single ruined CD is probably too weak a symptom for stating any serious
sickness in the driver. FYI, I cannot even personnaly try to ruin a single
CDR, for the reason I don't have CDR.

If you can retrieve information related to the failure, you may send me
them (syslog messages, cdrecord output messages, etc...). Thanks in
advance. You may also give a try with stable kernel and related stuff and 
let me know the result.

Regards,
  Gérard.

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

Re: Oops while loading ppa in 2.2.19-pre7

[f5ibh]

Hi Tim,

>> I got this non-fatal oops while loading the ppa module for my IOMEGA parallel
>> port ZIP drive.

>It doesn't look like it's related to the ZIP drive though:

>> Warning: kfree_skb passed an skb still on a list (from c8074fc1).
>> Oops: 0002
>> CPU:0
>> EIP:0010:[skb_recv_datagram+359/416]
>>   ^

>   Seems to be a networking problem..

You are probably right as I can see in tne oops :
Process tnt (pid: 388, process nr: 29, stackpage=c6fe1000)

tnt is a program for hamradio (packet transmission over radio). And this is
related to the network.



Regards

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

named streams, extended attributes, and posix

[Michael Rothwell]

Now that 2.4 is out, it will probably be a few .x releases until 2.5
begins.

A discussion on Named Streams and Extended Attributes was put off until
2.5 earlier in the 2.4 development cycle. For compatibility with
existing, widely-deployed filesystems (e.g., NFS, XFS, BeFS, HFS, etc.),
Linux needs a standard way to expose and interact with these filesystem
features. A draft of a paper proposing a methd for accomplishing this on
Posix systems is available at:

http://www.flyingbuttmonkeys.com/streams-on-posix.txt
http://www.flyingbuttmonkeys.com/streams-on-posix.pdf

Please read and comment! :)

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