Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

[Unix]

Matthias Buelow wrote:


Karl Denninger wrote:

 


SII chipsets were ok in 4.x, but the newer ATA code broke badly with them.
I've had a PR open on this since February, and many others have reported
similar issues.  The problems still exist in the 6.x-BETA releases I've
checked out, and are in some cases MORE severe (for me anyway) than they are
in 5.4.
   



Well, it doesn't affect just the SII chips.. I see the same on an
Intel ICH6 chipset but never after the kernel has mounted the root
fs. Sometimes it takes several attempts until it manages to do so,
though. The machine works w/o any such problems on other OSes. I've
deferred update of another machine (which is a hosted box and cannot
afford random hangs at boot) because of general flakeyness of the
ATA/SATA code in 5.4 (significantly worse than with 5.3, imho). If
these issues don't go away completely soon (in 6.x) I'll have to
look for some alternative system which doesn't make such a fuss
with mainstream hardware.

mkb.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

 

i knew about the problems with the sii chipset, had no idea it was just 
as bad with the ich6 chipset, I  have a Seagate 160gb SATA drive on an 
Intel SATA controller so far no problems though in 5.4-stable, my system 
did not like 6 at all, 7 was fine again..

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

[Unix]

Joel Rees wrote:



On 平成 17/08/10, at 7:36, O. Hartmann wrote:


[...] When is SCSI back for desktops?



I vote for that.

In my opinion, ATA is primarily for home media systems, if that.

Joel Rees   <[EMAIL PROTECTED]>
digitcom, inc.   株式会社デジコム
Kobe, Japan   +81-78-672-8800
**  **




___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

I thought the WD Raptors were supposed to replace the SCSI for that 
purpose. I used to run one in a Powermac and performance wise it behaved 
very well, unfortunately I haven't had the chance to test the 30 or 70 
GB WD Raptor SATA in FreeBSD..S/ATA drives should never be used for 24/7 
or server use anyway, they die after a while, in my case, two 80gb 
seagate drives after 1.5 yrs with proper cooling...thing is that SCSI 
drives are not affordable to the regular home server user...if they 
were, I bet more people would use them so that's why the current 
alternatives are ATA and SATA and SATA Raptors.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

[Unix]

Dmitry Mityugov wrote:


On 8/10/05, Unix <[EMAIL PROTECTED]> wrote:
...
 


I thought the WD Raptors were supposed to replace the SCSI for that
purpose. I used to run one in a Powermac and performance wise it behaved
very well, unfortunately I haven't had the chance to test the 30 or 70
GB WD Raptor SATA in FreeBSD..S/ATA drives should never be used for 24/7
or server use anyway
   


...

There are Maxtor MaXLine II and III, and perhaps several other models,
that are supposed to work 24/7.

 

Yes, but I don't like Maxtor drives, the ones I've used always failed 
after a year or less than a year...

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

[Unix]

Dmitry Mityugov wrote:


On 8/10/05, Unix <[EMAIL PROTECTED]> wrote:
 


Dmitry Mityugov wrote:

   


On 8/10/05, Unix <[EMAIL PROTECTED]> wrote:
...


 


I thought the WD Raptors were supposed to replace the SCSI for that
purpose. I used to run one in a Powermac and performance wise it behaved
very well, unfortunately I haven't had the chance to test the 30 or 70
GB WD Raptor SATA in FreeBSD..S/ATA drives should never be used for 24/7
or server use anyway


   


...

There are Maxtor MaXLine II and III, and perhaps several other models,
that are supposed to work 24/7.



 


Yes, but I don't like Maxtor drives, the ones I've used always failed
after a year or less than a year...
   



Western Digital produces similar drives as well - from
http://store.westerndigital.com/product.asp?sku=2700729: ..."24x7 100%
duty cycle–the highest available reliability rating on high capacity
drives"...

 


thanks, I need to get some new drives anyway...and WD was on my list...
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

[Unix]

Yes, I agree. I don't think anyone wants to blame the entire FreeBSD 
community for not being up to date on everything but if it is a known 
problem we should know. I know that the developers work for free and I, 
for one, appreciate all the work they've done. I know I would help if I 
could..but my programming knowledges are too poor..if there is a problem 
though, like the one with the SII and ICH chipsets maybe a FreeBSD 
developer should send an email asking for our help and I bet there would 
be plenty of people to test and script and like...


J. T. Farmer wrote:


Mike Tancsa wrote:


At 09:31 AM 10/08/2005, Karl Denninger wrote:

Also, I've yet to see a developer commit on the list that they WILL 
fix it if
such a controller board is forthcoming (and will return the board 
when they're
done) - I've got two of these cards here (choose between Adaptec and 
Bustek)
and would be happy to UPS one to someone IF I had a firm commitment 
that 6.x
would NOT go out without this being addressed and that the board 
would be

returned to me when work was complete.




You demand to see support for this chipset fixed, yet, you cant pony 
up a measly hundred bucks to donate the card to the developer who is 
not being paid to develop anything.



Why?  It was claimed that the code was developed to support this chipset.
Was that done in the dark, without hardware?  And why must it be a
hardware donation?  Karl has offered access to the hardware.  Asking to
get it back afterwards is a reasonable thing.  If the developer wants to
keep the card as part of a verification hardware suite, then they should
open their mouth and say so.  I suspect that Karl, and many other people,
would be more forthcoming with such donations if 1.) They were asked
in a reasonable manner, 2.) The hardware in question have not already
been listed as working under 5.x, and 3.) They had some assurance that
the problem would be fixed.

And finally, the problem has been reported in 5.4 and apparently in
6.0-Beta _not _only_ for the SII chipset & SATA, but also for some
of the Intel ICH chipsets.  And others, such as myself, are seeing the
same problem with plain PATA drives and controllers that are listed
as being supported by the ata driver.

In my case, a vanilla, OLD but working Via KT266A/8235 chipset MB
_will_not_boot an install kernel unless booted in safe mode.  I don't 
have

the resources to just give away hardware or buy replacements, just to
run FreeBSD as my desktop/development machine.  It runs WinXP and
Linux just fine.  However I _want_ to run FreeBSD.  Part of the that
machine's rational is so that I can contribute in my areas of interest
(sound & video editing/production tools, documentation).  I chose to
install 5.4, the PRODUCTION version, because I did not want any
surprises, did not want to be hacking a basic system functions.

At what point do I give up and just reformat the FreeBSD partition
and either release it to use with WinXP or install Linux?  Now mind
you, I've used FreeBSD, as a production platform, since 2.0.X.  I've
survived a fair number of "bumps."   But I'm at the point that I really
want the things that are claimed to work to just work.  I continue  to
run my servers under 4.X because or all the upheaval in 5.0/5.1/etc.
But 5.4 was supposed to have those teething problems behind it.
And the so far the only answer I get is try the ATA MkIII patches for
a partial fix, move to 6.0 for a real solution.
So when will 6.X really be Stable?  Yes, I understand that the RE is
working on getting 6.0 out the door.  But what users are trying to tell
you is that we need an answer for these problems.  If the production
release is broken for certain hardware, say so.  If FreeBSD developers
would rather work on big hairy server oriented problems, then say so.
If we have to run beta code to get old hardware to work, then say so.
Then we can make a choice as to what we run or try to use.  If
no one is interested in making FreeBSD work on the vanilla hardware
that is out there, then say so.  If FreeBSD is only going to run on
expensive hand picked hardware (the Sun approach) then say so.
Those of us who want to switch desktops and light duty servers
to FreeBSD will give up and move to Linux.  OR back to WinXP.

John

--
John T. FarmerOwner & CTOGoldSword Systems
[EMAIL PROTECTED] 865-691-6498   Knoxville TN
   Consulting, Design, & Development of Networks & Software

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

[Unix]

Matthias Buelow wrote:


J. T. Farmer wrote:

 


Those of us who want to switch desktops and light duty servers
to FreeBSD will give up and move to Linux.  OR back to WinXP.
   



I myself am just waiting for NetBSD 3.0, which will hopefully support
the ICH6 SATA stuff I have here (2.0.2 doesn't support it) and then
I'll move some machines to it. I don't want to start a flamewar but
they seem to have a somewhat higher quality output as of lately..
that is, when they advertise something as "working", one can be pretty
confident that it actually does work.

mkb.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

 

NetBSD 3.0 is also supposed to work somewhat with the Intel HD Audio 
controller..at least it gets detected...I'm in the same boat..I love 
FreeBSD and I'd prefer to keep it, I want to buy a Fujitsu MO Drive and 
I heard it only works in FreeBSD..but if I can't get good audio support 
in the near future and a stable S/ATA controller I'll consider switching...

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

[Unix]

It's sad isn't it, Mike..I don't know what the hd manufacturers are 
doing to the HD drives..ok, the systems get faster, there's usually bad 
cooling unless you build your own system...but even if you get enough 
cooling that won't change a thing some hds are prone to die an early 
death such as the Maxtors..I used to love Maxtor and hated Seagate now 
it's the other way around but my #1 HD still is Western Digital...I have 
an old Maxtor drive here 6 gb that's still running perfectly, just like 
3 40gb Seagate Barracuda and Western Digital Caviar...I had a 120gb 
Hitachi that died after 1 yr of use...



Mike Jakubik wrote:


On Wed, August 10, 2005 6:37 am, Dmitry Mityugov said:

 


There are Maxtor MaXLine II and III, and perhaps several other models,
that are supposed to work 24/7.
   



Right, i have a dead 250GB Maxline Plus II drive on my desk, only after
about 1.5 years. At least its still on warranty.



 



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

[Unix]

O. Hartmann wrote:


Mike Jakubik wrote:


On Wed, August 10, 2005 6:37 am, Dmitry Mityugov said:



There are Maxtor MaXLine II and III, and perhaps several other models,
that are supposed to work 24/7.




Right, i have a dead 250GB Maxline Plus II drive on my desk, only after
about 1.5 years. At least its still on warranty.



On the other hand: In the department for physics of the athmosphere, 
where I built six years ago a server for meteorological data, a RAID-5 
with 4 older IBM U160 SCSI discs still works - 24/7. Never had a problem!


I still own old 1-2 GB old SCSI disks and these are still working, I 
also had an old 500mb SCSI disk that was in an old Mac that also worked 
but I trashed it since it was that old and no longer of use...

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: firefox, Xorg and crash.

[Unix]

Yann Golanski wrote:


Firefox keeps taking X11 and then the whole machine with it.  It
requires a hard reset as even pinging the machine does not work.  Only
Firefox seems to be doing this.  

Does anyone else have the same problem?  


Anyone knows how to solve/debug this?

; uname -a
FreeBSD rubicon.york.ac.uk 5.4-STABLE FreeBSD 5.4-STABLE #0: Mon Aug  8
16:18:46 BST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP
i386
; pkg_info | grep xorg
xorg-6.8.2  X.Org distribution metaport
; pkg_info | grep firefox
firefox-1.0.6_1,1   Web browser based on the browser portion of Mozilla

 


no running fine and stable on my machine, 5.4-STABLE
$ uname -a
FreeBSD canis.local 5.4-STABLE FreeBSD 5.4-STABLE #0: Fri Aug 12 
19:36:45 CEST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CANIS  i386


Firefox 1.0.6_1,1 and xorg6.8.2, both packages and not compiled from source
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

AMD (Stable problem)

[Unix]

Hi,

I was updating my laptop as usual and I ran into this problem today
after I finished make buidlworld; make buildkernel KERNCONF=heMatrix;
make installkernel KERNCONF=TheMatrix; reboot :

Sep 28 13:43:06 freebee /kernel: Starting final network daemons:
Sep 28 13:43:06 freebee /kernel: nfsiod
Sep 28 13:43:06 freebee /kernel: NFS access cache time=2
Sep 28 13:43:06 freebee /kernel: amd
Sep 28 13:43:06 freebee /kernel: .
Sep 28 13:43:07 freebee /kernel: ELF ldconfig path: /usr/lib
/usr/lib/compat /usr/X11R6/lib /usr/local/lib
Sep 28 13:43:07 freebee /kernel: Sep 28 13:43:07 freebee /kernel: nfs
send error 13 for server pid107@freebee:/host
Sep 28 13:43:07 freebee /kernel: a.out ldconfig path: /usr/lib/aout
/usr/lib/compat/aout /usr/X11R6/lib/aout
Sep 28 13:43:07 freebee /kernel: Sep 28 13:43:07 freebee /kernel: nfs
send error 13 for server pid107@freebee:/net
Sep 28 13:43:07 freebee /kernel: Starting standard daemons:
Sep 28 13:43:07 freebee /kernel: inetd
Sep 28 13:43:07 freebee /kernel: cron
Sep 28 13:43:07 freebee /kernel: Sep 28 13:43:07 freebee amd[107]:
unable to register (AMQ_PROGRAM=300019, AMQ_VERSION, tcp)
Sep 28 13:43:07 freebee /kernel: sshd

At Reboot the network is gone, a simple ping to localhost
gets a permission denied, no network.

I had to fall back to my old kernel: septembre 13.
FreeBSD freebee.henocoffice.com 4.7-PRERELEASE FreeBSD 4.7-PRERELEASE
#1: Fri Sep 13 22:17:16 EDT 2002
[EMAIL PROTECTED]:/usr/obj/.amd_mnt/haydn/host/usr/src/sys/TheMatrix  i386

Thanks in advance.







To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Re: running out of mbuf

[Unix Tools]

We had the same problem
changed the NMBCLUSTERS value in the kernel config file and recompiled the
kernel.

That fixed it.
options NMBCLUSTERS=4096


- Original Message -
From: "Wahyu Hidayat" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Friday, September 06, 2002 07:02 AM
Subject: running out of mbuf


> Hello,
>
> Firstly I am not a member of this mailling-list, so
> please CC to me, or if this is not the right forum,
> give me a direction where I  could post it.
>
> I have a machine running squid cache-server and apache
> to answer squidGuard redirectors. When running under
> heavy load it complains about mbuf:
>
> Sep  6 07:42:40 cache2 squid[5735]: aclMatchProxyAuth:
> user 'imon' tries to use multple IP addresses!
> Sep  6 07:43:22 cache2 squid[5735]:
> aclDecodeProxyAuth: Disallowing empty passwo
> rd,user is ''
> Sep  6 07:43:26 cache2 last message repeated 2 times
> Sep  6 07:43:50 cache2 /kernel: looutput: mbuf
> allocation failed
> Sep  6 07:44:43 cache2 squid[5735]:
> aclDecodeProxyAuth: Unsupported proxy-auth sheme,
> 'owqeko=f|xjbd'
>
> I thought I've configured my kernel with enough mbuf,
> but even one-half have not used yet. My netstat -m:
>
> 22070/22544/81920 mbufs in use (current/peak/max):
> 20490 mbufs allocated to data
> 1580 mbufs allocated to packet headers
> 20462/20480/20480 mbuf clusters in use
> (current/peak/max)
> 46596 Kbytes allocated to network (7% of mb_map in
> use)
> 87932 requests for memory denied
> 274 requests for memory delayed
> 0 calls to protocol drain routines
>
> This problem bothers me, as our http traffic comes
> from this server, and I have to reconfigure squid
> processes (the same as restarting I think) to free up
> mbuf.
>
> If you have any idea how to solve this please let me
> know. Any help of reference would be greatly
> appreciated.
>
> Best regards.
> -why-
>
> __
> Do You Yahoo!?
> Yahoo! Finance - Get real-time stock quotes
> http://finance.yahoo.com
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-questions" in the body of the message
>

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message