On Thu, 2006-01-12 at 09:46 +0000, James Pattinson wrote:
> Ming Zhang wrote:
>
> >if this is not too troublesome, could u change to another NIC and see if
> >ok?
> >
> >
> Sure, I can try that if I get a chance at the weekend. I have some 3com
> cards laying around that I can use.
do it when u have time.
>
> >i saw a lot of retrans, checksum error, and spanning tree packets and
> >time delay between them are pretty long. so iscsi layer might begin to
> >do task management or relogin or many ugly stuff. :P
> >
> >
> Sounds yucky! Strange that it worked with older kernel though.
yes, one way is to find all kernel release between these 2 and try one
by one. :P way too trouble.
>
> >>2. crocodile - amd64 machine running 64 bit kernel, worked fine at
> >>2.6.12 and 2.6.14-r2 with 0.4.12 each time
> >>
> >>
> >
> >so this one u did not tried the svn code?
> >
> >
> Nope - it works at the moment and I don't want to break it. However I
> could try SVN if it will help you out.
u can always have different source dir. so what u need to do is just
reboot and a "make install". just want to see which one, new kernel, or
new iet code, cause this.
>
> James
>
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
|
