I would like to automate generating the prototype list for smbfs. The list
in include/linux/smb_fs.h is probably mostly correct ... or not.
Does anyone use this type of tool anywhere else in the kernel sources?
Any input on how to set it up right is appreciated.
Here is what I have right now.
I would like to automate generating the prototype list for smbfs. The list
in include/linux/smb_fs.h is probably mostly correct ... or not.
Does anyone use this type of tool anywhere else in the kernel sources?
Any input on how to set it up right is appreciated.
Here is what I have right now.
1-smbfs/fs/smbfs/ChangeLog Tue Jun 12 20:34:32 2001
@@ -1,5 +1,10 @@
ChangeLog for smbfs.
+2001-06-12 Urban Widmark <[EMAIL PROTECTED]>
+
+ * proc.c: replace the win95-flush fix with smb_seek, when needed.
+ * proc.c: readdir 'lastname' bug (NetApp dir listing fix)
+
2001-05-
/smbfs/ChangeLog Tue Jun 12 20:34:32 2001
@@ -1,5 +1,10 @@
ChangeLog for smbfs.
+2001-06-12 Urban Widmark [EMAIL PROTECTED]
+
+ * proc.c: replace the win95-flush fix with smb_seek, when needed.
+ * proc.c: readdir 'lastname' bug (NetApp dir listing fix)
+
2001-05-08 Urban Widmark [EMAIL
> >Are you sure. What's the version of your driver. Please tell me. It's
> >important.
> >I remember we have fixed it already.
>
> The driver version (dlkfet.sys) is 2.52 from 08/06/2000. this is the lastest
> driver from the original dlink site.
Perhaps Yiping Chen was talking about a D-Link
Are you sure. What's the version of your driver. Please tell me. It's
important.
I remember we have fixed it already.
The driver version (dlkfet.sys) is 2.52 from 08/06/2000. this is the lastest
driver from the original dlink site.
Perhaps Yiping Chen was talking about a D-Link linux
On Wed, 30 May 2001, Rose, Daniel wrote:
> It seems as though my card will not reset anymore after running windows 98,
> even after a cold boot, and recompiling the kernel. Below is the output of
> dmesg, lspci -n and ifconfig. Does anyone have any ideas? (please cc
> replies)
Have you tried
On Wed, 30 May 2001, Rose, Daniel wrote:
It seems as though my card will not reset anymore after running windows 98,
even after a cold boot, and recompiling the kernel. Below is the output of
dmesg, lspci -n and ifconfig. Does anyone have any ideas? (please cc
replies)
Have you tried
On 29 May 2001, Daniel Rose wrote:
> Ok, I have decided the problem lays in via-rhine.c, the ethernet driver
> for my card. The second boot finds the mac address as 00's all the time,
> regardless of whether the driver is compiled as a module, or monolith.
Do you boot something else in between?
On 29 May 2001, Daniel Rose wrote:
Ok, I have decided the problem lays in via-rhine.c, the ethernet driver
for my card. The second boot finds the mac address as 00's all the time,
regardless of whether the driver is compiled as a module, or monolith.
Do you boot something else in between?
On 25 May 2001, Jay Thorne wrote:
> Netperf is a pretty good idea. Should not be a cpu bottleneck. Thats a
> good thing. So pretty much the same results as wu-ftpd: Note that I used
> the 466 mhz quad with a via-rhine, since the 400 locked up and was still
> fscking when I started this test.
>
On 25 May 2001, Jay Thorne wrote:
Netperf is a pretty good idea. Should not be a cpu bottleneck. Thats a
good thing. So pretty much the same results as wu-ftpd: Note that I used
the 466 mhz quad with a via-rhine, since the 400 locked up and was still
fscking when I started this test.
On Wed, 23 May 2001, Xuan Baldauf wrote:
> Urban Widmark wrote:
>
> > The only other way I have found so far to get it to return the right file
> > size is to do a "seek-to-end". That still means an extra SMB but it avoids
> > the very painful "sync
On Mon, 21 May 2001, Xuan Baldauf wrote:
> That is annoying, because it heavily slows down bulk transfers of small
> writes, like automatically unzipping a new mozilla build from the linux box to
> the windows box. Every write of say 100 bytes is implemented as
>
> send write req
> recv write
On Mon, 21 May 2001, Xuan Baldauf wrote:
That is annoying, because it heavily slows down bulk transfers of small
writes, like automatically unzipping a new mozilla build from the linux box to
the windows box. Every write of say 100 bytes is implemented as
send write req
recv write ack
On Wed, 23 May 2001, Xuan Baldauf wrote:
Urban Widmark wrote:
The only other way I have found so far to get it to return the right file
size is to do a seek-to-end. That still means an extra SMB but it avoids
the very painful sync to disk.
Fortunately the seek is only necessary when
On Mon, 21 May 2001, Eric S. Raymond wrote:
> the NEW tag). That phase ended almost a month ago. Nobody who has
> actually tried the CML2 tools more recently has reported that the UI
> changes present any difficulty.
What happened with the discussion on configurable colors in make
menuconfig?
On Mon, 21 May 2001, Xuan Baldauf wrote:
> Hello Urban,
>
> I've been playing around a while with that patch and so far could not find any
> problems anymore. But I've noticed some other annoying behaviour, which might
Good.
> be caused by trying to work around the initially reported bug
On Mon, 21 May 2001, Xuan Baldauf wrote:
Hello Urban,
I've been playing around a while with that patch and so far could not find any
problems anymore. But I've noticed some other annoying behaviour, which might
Good.
be caused by trying to work around the initially reported bug where the
On Mon, 21 May 2001, Eric S. Raymond wrote:
the NEW tag). That phase ended almost a month ago. Nobody who has
actually tried the CML2 tools more recently has reported that the UI
changes present any difficulty.
What happened with the discussion on configurable colors in make
menuconfig?
On 7 May 2001, Linus Torvalds wrote:
> It has code to do that in smb_revalidate_inode(), but it may be that
> something else refreshes the inode size _without_ doing the proper
> invalidation checks. Or maybe Urban broke that logic by mistake while
> fixing the other one ;)
No, I broke it when
On 7 May 2001, Linus Torvalds wrote:
It has code to do that in smb_revalidate_inode(), but it may be that
something else refreshes the inode size _without_ doing the proper
invalidation checks. Or maybe Urban broke that logic by mistake while
fixing the other one ;)
No, I broke it when
On Sun, 6 May 2001, Xuan Baldauf wrote:
> it does not fix|work around the bug completely:
>
> 1. windows: Create a file, e.g. with 741 bytes.
> 2. linux: "ls -la" will show you the file with the correct size (741)
> 3. linux: read the file into your smbfs cache (e.g. "less file")
> 4. windows:
On Sun, 6 May 2001, Xuan Baldauf wrote:
it does not fix|work around the bug completely:
1. windows: Create a file, e.g. with 741 bytes.
2. linux: ls -la will show you the file with the correct size (741)
3. linux: read the file into your smbfs cache (e.g. less file)
4. windows: add some
On Thu, 3 May 2001, Eric S. Raymond wrote:
> In many cases there is no way to define "upper" or "lower". (X86 and
> SMP) implies RTC!=n is actually a good example. Here's where they fit
> in the tree:
>
> main 'Linux Kernel Configuration System'
> arch
On Thu, 3 May 2001, Eric S. Raymond wrote:
In many cases there is no way to define upper or lower. (X86 and
SMP) implies RTC!=n is actually a good example. Here's where they fit
in the tree:
main 'Linux Kernel Configuration System'
arch 'Processor
/MAINTAINERS
--- linux-2.4.4-orig/MAINTAINERSWed May 2 20:01:07 2001
+++ linux-2.4.4-smbfs/MAINTAINERS Wed May 2 20:42:24 2001
@@ -1171,7 +1171,7 @@
SMB FILESYSTEM
P: Urban Widmark
-M: [EMAIL PROTECTED]
+M: [EMAIL PROTECTED]
W: http://samba.org/
L:
-2.4.4-orig/MAINTAINERSWed May 2 20:01:07 2001
+++ linux-2.4.4-smbfs/MAINTAINERS Wed May 2 20:42:24 2001
@@ -1171,7 +1171,7 @@
SMB FILESYSTEM
P: Urban Widmark
-M: [EMAIL PROTECTED]
+M: [EMAIL PROTECTED]
W: http://samba.org/
L: [EMAIL PROTECTED]
S
On Sun, 1 Apr 2001, Xuan Baldauf wrote:
> there is something wrong with smbfs caching which makes my
> applications fail. The behaviour happens with
> linux-2.4.3-pre4 and linux-2.4.3-final.
>
> Consider following shell script: (where /mnt/n is a
> smbmounted smb share from a Win98SE box)
Try
On Sun, 1 Apr 2001, Xuan Baldauf wrote:
there is something wrong with smbfs caching which makes my
applications fail. The behaviour happens with
linux-2.4.3-pre4 and linux-2.4.3-final.
Consider following shell script: (where /mnt/n is a
smbmounted smb share from a Win98SE box)
Try the
On Sun, 1 Apr 2001, Xuan Baldauf wrote:
> Hello,
>
> there is something wrong with smbfs caching which makes my
> applications fail. The behaviour happens with
> linux-2.4.3-pre4 and linux-2.4.3-final.
Any version you know it doesn't happen with? (including 2.2 versions)
> Consider following
On Sun, 1 Apr 2001, Xuan Baldauf wrote:
Hello,
there is something wrong with smbfs caching which makes my
applications fail. The behaviour happens with
linux-2.4.3-pre4 and linux-2.4.3-final.
Any version you know it doesn't happen with? (including 2.2 versions)
Consider following shell
On Wed, 7 Mar 2001, Pete Zaitcev wrote:
> Trace; c0127414
> Trace; c0136a2d
> Trace; c012722e
> Trace; c0127290
> Trace; c0127414
> Trace; c014cdec
> Trace; c0143f80
> Trace; c0144aae
> Trace; c014cdec
> Trace; c01392c9
> Trace; c0138130
> Trace; c013805d
> Trace; c0148b97
> Trace;
On Wed, 7 Mar 2001, Pete Zaitcev wrote:
Trace; c0127414 handle_mm_fault+114/1a0
Trace; c0136a2d kunmap_high+7d/90
Trace; c012722e do_anonymous_page+de/110
Trace; c0127290 do_no_page+30/a0
Trace; c0127414 handle_mm_fault+114/1a0
Trace; c014cdec dput+1c/170
Trace; c0143f80
/smbfs/ChangeLogThu Feb 22 20:52:03 2001
+++ linux-2.4.2-ac12-smbfs/fs/smbfs/ChangeLog Tue Mar 6 23:50:06 2001
@@ -1,9 +1,22 @@
ChangeLog for smbfs.
+2001-03-06 Urban Widmark <[EMAIL PROTECTED]>
+
+ * cache.c: d_add on hashed dentries corrupts d_hash list and
+ causes
/smbfs/ChangeLogThu Feb 22 20:52:03 2001
+++ linux-2.4.2-ac12-smbfs/fs/smbfs/ChangeLog Tue Mar 6 23:50:06 2001
@@ -1,9 +1,22 @@
ChangeLog for smbfs.
+2001-03-06 Urban Widmark [EMAIL PROTECTED]
+
+ * cache.c: d_add on hashed dentries corrupts d_hash list and
+ causes loops
Is it valid to call d_add on a negative dentry?
(or on a dentry that is already linked in d_hash, but all negative
dentries are, right?)
I'm guessing it isn't because I think that is how I can get my machine to
hang in d_lookup, looping on a corrupt d_hash list.
The problem can be reproduced
Is it valid to call d_add on a negative dentry?
(or on a dentry that is already linked in d_hash, but all negative
dentries are, right?)
I'm guessing it isn't because I think that is how I can get my machine to
hang in d_lookup, looping on a corrupt d_hash list.
The problem can be reproduced
On Tue, 27 Feb 2001, Michal Jaegermann wrote:
>
> After I booted 2.2.19pre14 on a system with two via-rhine cards I see the
> following:
>
> via-rhine.c:v1.08b-LK1.0.0 12/14/2000 Written by Donald Becker
> http://www.scyld.com/network/via-rhine.html
> eth0: VIA VT3043 Rhine at 0x9400,
On Wed, 28 Feb 2001, Rainer Mager wrote:
> Hi all,
>
> I'm trying to use autofs for the first time and am running into some
> problems. First, the documentation seems quite weak, that is, I'm not sure
I am sure the maintainer would appreciate if you wrote down what you found
On Wed, 28 Feb 2001, Rainer Mager wrote:
Hi all,
I'm trying to use autofs for the first time and am running into some
problems. First, the documentation seems quite weak, that is, I'm not sure
I am sure the maintainer would appreciate if you wrote down what you found
On Tue, 27 Feb 2001, Michal Jaegermann wrote:
After I booted 2.2.19pre14 on a system with two via-rhine cards I see the
following:
via-rhine.c:v1.08b-LK1.0.0 12/14/2000 Written by Donald Becker
http://www.scyld.com/network/via-rhine.html
eth0: VIA VT3043 Rhine at 0x9400,
On Mon, 26 Feb 2001, Arnaldo Carvalho de Melo wrote:
> thanks, I'll take that into account for the remaining ones and this should
> be checked by the driver authors for the ones I've already sent.
The pkt_len variant is already in 2.4.1-ac15 and probably before that
(changed by Manfred Spraul
On Mon, 26 Feb 2001, Arnaldo Carvalho de Melo wrote:
thanks, I'll take that into account for the remaining ones and this should
be checked by the driver authors for the ones I've already sent.
The pkt_len variant is already in 2.4.1-ac15 and probably before that
(changed by Manfred Spraul
Hello
Unless I misunderstand s_maxbytes it says how large a file can be on the
fs. I assume it is enough for a fs to set that and then it knows the vfs
will not ask it to go beyond that limit?
Is it ok to at mount time set it to non-LFS and then later change it to be
something larger? smbfs
Hello
Unless I misunderstand s_maxbytes it says how large a file can be on the
fs. I assume it is enough for a fs to set that and then it knows the vfs
will not ask it to go beyond that limit?
Is it ok to at mount time set it to non-LFS and then later change it to be
something larger? smbfs
On Fri, 9 Feb 2001, Kaj-Michael Lang wrote:
> I don't know if it should work or not but using a VIA Rhine compatible card
> on my LX164 locks it solid when transfering large packets:
> ping -f host.on.100mbit.lan works
> ping -f -s 1024 same.host locks it solid as does
> untarring to a NFS
On Fri, 9 Feb 2001, Kaj-Michael Lang wrote:
I don't know if it should work or not but using a VIA Rhine compatible card
on my LX164 locks it solid when transfering large packets:
ping -f host.on.100mbit.lan works
ping -f -s 1024 same.host locks it solid as does
untarring to a NFS mount.
I
On Wed, 7 Feb 2001 [EMAIL PROTECTED] wrote:
> I've compiled a number of 2.4.1 and 2.4.0 kernels (actually supports the 4GB
> RAM!!! Yay), and I have only one more problem to sort out. Under
> 2.4.x, the mount completes successfully, but 'ls /net' causes an OOPS: .
Try
On Wed, 7 Feb 2001 [EMAIL PROTECTED] wrote:
I've compiled a number of 2.4.1 and 2.4.0 kernels (actually supports the 4GB
RAM!!! Yay), and I have only one more problem to sort out. Under
2.4.x, the mount completes successfully, but 'ls /net' causes an OOPS: .
Try
On Mon, 5 Feb 2001, Manfred Spraul wrote:
> 6 ms is quite long:
> I added a reset into tx_timeout, and that function should not take more
> than 1 ms or so.
> Did you find something about the delay in the documentation? Is it
> possible to poll for reset completion?
I don't know how long. For
On Mon, 5 Feb 2001, Manfred Spraul wrote:
6 ms is quite long:
I added a reset into tx_timeout, and that function should not take more
than 1 ms or so.
Did you find something about the delay in the documentation? Is it
possible to poll for reset completion?
I don't know how long. For
On Sun, 4 Feb 2001, Manfred Spraul wrote:
> > Oh, that's known already. They haven't released any info on the older
> > "VT3043" chip either, afaik. And the vt86c100a.pdf document is just a
> > preliminary version.
> >
> Where can I find that file?
> I'll try to implement tx_timeout()
> This sounds every much like it's related to the problems we're having with
> the card not initialising on reboot from Windows.
It's not the same problem. Here the card initializes just fine. And it
works for a while.
The "transmit timed out" message is simply saying that we told the card to
On Sun, 4 Feb 2001, Manfred Spraul wrote:
Oh, that's known already. They haven't released any info on the older
"VT3043" chip either, afaik. And the vt86c100a.pdf document is just a
preliminary version.
Where can I find that file?
I'll try to implement tx_timeout()
On Sat, 3 Feb 2001 [EMAIL PROTECTED] wrote:
> I noticed that the mac address was stored in the registers and
> eprom. I guess it would not be as easy as just writing the mac
> back in the blank eprom and registers?
What my changed via-diag tries to do is to tell the chip to reload things
from
On Sat, 3 Feb 2001, Jonathan Morton wrote:
> Do you want me to try this again, after first setting the card into
> non-working condition?
Yes, the idea was to start from non-working, test -I and then ifconfig
down/up. Getting the working card to work is a much simpler problem :)
/Urban
-
To
On Sat, 3 Feb 2001 [EMAIL PROTECTED] wrote:
> VIA VT3065 Rhine-II chip registers at 0xd400
> 0x000: 0804
>
> 0x020: 0400
>
> 0x040:
On Sat, 3 Feb 2001 [EMAIL PROTECTED] wrote:
VIA VT3065 Rhine-II chip registers at 0xd400
0x000: 0804
0x020: 0400
0x040:
On Sat, 3 Feb 2001, Jonathan Morton wrote:
Do you want me to try this again, after first setting the card into
non-working condition?
Yes, the idea was to start from non-working, test -I and then ifconfig
down/up. Getting the working card to work is a much simpler problem :)
/Urban
-
To
> >I did this and compiled it into the kernel. It detects it at boot (via-
> >rhine v1.08-LK1.1.6 8/9/2000 Donald Becker) but says the
> >hardware address (mac address?) is 00-00-00-00-00-00.
This is a good example of what is missed by not copying the exact message.
For example, mine says:
I did this and compiled it into the kernel. It detects it at boot (via-
rhine v1.08-LK1.1.6 8/9/2000 Donald Becker) but says the
hardware address (mac address?) is 00-00-00-00-00-00.
This is a good example of what is missed by not copying the exact message.
For example, mine says:
eth0: VIA
Hello again
This patch is more complete than the version posted earlier. It implements
support for OS/2 (and possibly things even older than that :) and have
been more tested. This borrows a lot from the ncpfs dircache code.
Smbfs testers wanted, with or without highmem boxes.
Bugs
Hello again
This patch is more complete than the version posted earlier. It implements
support for OS/2 (and possibly things even older than that :) and have
been more tested. This borrows a lot from the ncpfs dircache code.
Smbfs testers wanted, with or without highmem boxes.
Bugs
On Thu, 18 Jan 2001, Mike A. Harris wrote:
> I now believe that it is indeed caused by booting to windows 98
> (by accident). ;o)
Don't do that then :)
> Doesn't matter if a driver is installed in win or not as I've
> tried both. Just booting win at all causes the card to go
> berzerk next
On Thu, 18 Jan 2001, Mike A. Harris wrote:
I now believe that it is indeed caused by booting to windows 98
(by accident). ;o)
Don't do that then :)
Doesn't matter if a driver is installed in win or not as I've
tried both. Just booting win at all causes the card to go
berzerk next boot.
There have been a few reports on oopses in smbfs on 2.4 boxes with highmem
support enabled. This patch tries to fix that.
The patch replaces the smbfs dir cache code with something based on the
ncpfs code. Petr should recognize almost all of it. And the ntfs code has
contributed with new time
There have been a few reports on oopses in smbfs on 2.4 boxes with highmem
support enabled. This patch tries to fix that.
The patch replaces the smbfs dir cache code with something based on the
ncpfs code. Petr should recognize almost all of it. And the ntfs code has
contributed with new time
On Thu, 18 Jan 2001, Petr Vandrovec wrote:
> > Rainer Mager reported the same thing yesterday ("Oops with 4GB memory
> > setting in 2.4.0 stable" if you want to read the thread).
>
> I think that I found source of problem. I have no simple solution :-(
>
I think the source of the problem is
On Thu, 18 Jan 2001, Petr Vandrovec wrote:
Rainer Mager reported the same thing yesterday ("Oops with 4GB memory
setting in 2.4.0 stable" if you want to read the thread).
I think that I found source of problem. I have no simple solution :-(
I think the source of the problem is that this
On Thu, 18 Jan 2001, Rainer Mager wrote:
> Here is a newly parsed oops, this time using the /var/log/ksymoops method
> mentioned by Keith Owens. Does this look better?
Yes, and it sort of matches the other oops someone sent. Thanks.
I have a changed version now, based on the ncpfs directory
On Wed, 17 Jan 2001, Scott A. Sibert wrote:
> I'm consistently getting an oops when accessing any smbfs mount whether
> running 'ls' inside the smbfs mount or hitting TAB for filename
> completion of a directory in an smbfs mount. I have another machine
> (dual P2/300 w/320MB memory) that does
On Wed, 17 Jan 2001, Petr Vandrovec wrote:
> Hi,
> Maarten de Boer pointed to me, that if you load some simple program,
> such as 'void main(void) {}', trace into main (break main; run)
> and then quit from gdb (Really exit? yes), child process is then
> killed due to INT3 (probably). Then
On Wed, 17 Jan 2001, Petr Vandrovec wrote:
Hi,
Maarten de Boer pointed to me, that if you load some simple program,
such as 'void main(void) {}', trace into main (break main; run)
and then quit from gdb (Really exit? yes), child process is then
killed due to INT3 (probably). Then
On Wed, 17 Jan 2001, Scott A. Sibert wrote:
I'm consistently getting an oops when accessing any smbfs mount whether
running 'ls' inside the smbfs mount or hitting TAB for filename
completion of a directory in an smbfs mount. I have another machine
(dual P2/300 w/320MB memory) that does not
On Tue, 16 Jan 2001, richard.morgan9 wrote:
> I have the same problem as Urban with a recent DLink 530tx
> (rhine2). Pulling the power cable from my atx psu (while the
> computer was "off") fixed the card, until my next reboot from
> win98.
I'm not the one with a problem but maybe it has
On Tue, 16 Jan 2001, Petr Vandrovec wrote:
> If there is new dentry, which is at fpos postion, and it is child of
> readdir-ed directory, we should return it anyway, no? There must not be
> two ncpfs dentries with same d_parent and d_fsdata if d_fsdata != 0,
> as each dentry can be in only one
On Tue, 16 Jan 2001, Petr Vandrovec wrote:
> smb_get_dircache looks suspicious to me, as it can try to map unlimited
> number of pages with kmap. And kmaps are not unlimited resource...
> You have 512 kmaps, but one SMBFS cache page can contain about 504
> pages... So two smbfs cached
On Tue, 16 Jan 2001, Rainer Mager wrote:
> Hi all,
>
> I have a 100% reproducable bug in all of the 2.4.0 kernels including the
> latest stable one. The issue is that if I compile the kernel to support 4GB
> RAM (I have 1 GB) and then try to access a samba mount I get an oops. This
I'll
On Tue, 16 Jan 2001, Rainer Mager wrote:
Hi all,
I have a 100% reproducable bug in all of the 2.4.0 kernels including the
latest stable one. The issue is that if I compile the kernel to support 4GB
RAM (I have 1 GB) and then try to access a samba mount I get an oops. This
I'll have a
On Tue, 16 Jan 2001, Petr Vandrovec wrote:
smb_get_dircache looks suspicious to me, as it can try to map unlimited
number of pages with kmap. And kmaps are not unlimited resource...
You have 512 kmaps, but one SMBFS cache page can contain about 504
pages... So two smbfs cached directories
On Tue, 16 Jan 2001, Petr Vandrovec wrote:
If there is new dentry, which is at fpos postion, and it is child of
readdir-ed directory, we should return it anyway, no? There must not be
two ncpfs dentries with same d_parent and d_fsdata if d_fsdata != 0,
as each dentry can be in only one
On Tue, 16 Jan 2001, richard.morgan9 wrote:
I have the same problem as Urban with a recent DLink 530tx
(rhine2). Pulling the power cable from my atx psu (while the
computer was "off") fixed the card, until my next reboot from
win98.
I'm not the one with a problem but maybe it has something
On Sun, 14 Jan 2001, Mike A. Harris wrote:
> Becker's latest via-rhine driver ontop 2.2.18..
>
> ...
> eth1: Transmit timed out, status , PHY status ,
> resetting...
[snip]
> Keeps going nonstop until I ifdown eth1.
>
> Card worked fine 2 days ago...
So what did you change?
Has the
On Sun, 14 Jan 2001, Mike A. Harris wrote:
Becker's latest via-rhine driver ontop 2.2.18..
...
eth1: Transmit timed out, status , PHY status ,
resetting...
[snip]
Keeps going nonstop until I ifdown eth1.
Card worked fine 2 days ago...
So what did you change?
Has the machine been
On Wed, 20 Dec 2000, Hans-Joachim Baader wrote:
> Then run the program. It should copy the files to the current
> directory. Then run it under gdb. It should hang until you kill
> gdb.
Hello again
(Sorry for the long response time but this really is the busiest time of
the year, or maybe it's
On Wed, 20 Dec 2000, Hans-Joachim Baader wrote:
Then run the program. It should copy the files to the current
directory. Then run it under gdb. It should hang until you kill
gdb.
Hello again
(Sorry for the long response time but this really is the busiest time of
the year, or maybe it's the
On Tue, 19 Dec 2000, Hans-Joachim Baader wrote:
> and so on, endlessly. So, AFAIK, smbfs thinks it has lost connection and
> tells smbmount to re-establish it, which succeeds (at least smbmount
> thinks so). This happens several times per second.
-512 means that the recv was interrupted by a
On Tue, 19 Dec 2000, Hans-Joachim Baader wrote:
and so on, endlessly. So, AFAIK, smbfs thinks it has lost connection and
tells smbmount to re-establish it, which succeeds (at least smbmount
thinks so). This happens several times per second.
-512 means that the recv was interrupted by a
0
Annapolis MD 21403
Support and updates available at
- http://cesdis.gsfc.nasa.gov/linux/drivers/via-rhine.html
+ http://www.scyld.com/network/via-rhine.html
+
+
+ Linux kernel version history:
+
+ LK1.0.0:
+ - Urban Widmark: merges from Beckers 1.08b v
http://cesdis.gsfc.nasa.gov/linux/drivers/via-rhine.html
+ http://www.scyld.com/network/via-rhine.html
+
+
+ Linux kernel version history:
+
+ LK1.0.0:
+ - Urban Widmark: merges from Beckers 1.08b version and 2.4.0 (VT6102)
*/
-static const char *versionA =
-"vi
On Wed, 13 Dec 2000, Igor Yu. Zhbanov wrote:
> I think your testprogram is broken (or else my testprogram is broken :).
Yes, you were right. Mine must have been broken (possibly caused by
trying to make it readable :). Thanks.
Alan, if you still have the patch please apply it to smbfs in 2.2
On Wed, 13 Dec 2000, Igor Yu. Zhbanov wrote:
I think your testprogram is broken (or else my testprogram is broken :).
Yes, you were right. Mine must have been broken (possibly caused by
trying to make it readable :). Thanks.
Alan, if you still have the patch please apply it to smbfs in 2.2
On Sun, 10 Dec 2000, Mohammad A. Haque wrote:
> Could someome who knows what they are doing check over the following
> patch please?
I wouldn't say that I do, but no one else seems to be answering this.
list_add_tail does head->prev and making the call with a NULL 'head' looks
bad to me. I
On Tue, 5 Dec 2000, Linus Torvalds wrote:
> In comparison to these dentry host problems, your patch looks fine. But I
> suspect that you _can_ trigger the BUG() with an empty dentry list due to
> dentry shrinking. So what I did is basically to (a) apply your patch and
> (b) set writepage to NULL
On Tue, 5 Dec 2000, Linus Torvalds wrote:
In comparison to these dentry host problems, your patch looks fine. But I
suspect that you _can_ trigger the BUG() with an empty dentry list due to
dentry shrinking. So what I did is basically to (a) apply your patch and
(b) set writepage to NULL in
On Sun, 10 Dec 2000, Mohammad A. Haque wrote:
Could someome who knows what they are doing check over the following
patch please?
I wouldn't say that I do, but no one else seems to be answering this.
list_add_tail does head-prev and making the call with a NULL 'head' looks
bad to me. I would
On Tue, 5 Dec 2000, Igor Yu. Zhbanov wrote:
> Hello!
Hello again
> As I see now in 2.2.18pre24 NCPFS is fixed but VFAT and SMBFS doesn't. (This
> happened because the maintainer of NCPFS resent my patch to Alan Cox but only the
> part of patch related to NCPFS). So I resent you patch for VFAT
On Tue, 5 Dec 2000, Igor Yu. Zhbanov wrote:
Hello!
Hello again
As I see now in 2.2.18pre24 NCPFS is fixed but VFAT and SMBFS doesn't. (This
happened because the maintainer of NCPFS resent my patch to Alan Cox but only the
part of patch related to NCPFS). So I resent you patch for VFAT and
On Fri, 24 Nov 2000, Igor Yu. Zhbanov wrote:
> Hello!
Hello, sorry for the slow response.
> I have found a bug in drivers of file systems which use a DOS-like format
> of date (16 bit: years since 1980 - 7 bits, month - 4 bits, day - 5 bits).
[snip]
> 2) VFAT for example have three kinds of
1 - 100 of 124 matches
Mail list logo
