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

Maxim M. Kazachek wrote: SoftModems works (well, almost) perfectly under Windows. Some of these works under Linux. SoftModems is the best, because they are cheap and works under Windows. The FreeBSD is puny OS just because they lack support of Software modem. The thing is as worth as much you

Re: 5-STABLE cpufreq hotter than est from ports

Kevin Oberman wrote: Date: Tue, 9 Aug 2005 11:35:29 +0200 From: Bruno Ducrot <[EMAIL PROTECTED]> Sender: [EMAIL PROTECTED] On Tue, Aug 02, 2005 at 12:22:02AM +0200, Tijl Coosemans wrote: A couple days ago I updated my system and was excited to see cpufreq and powerd in 5-stable. Since then how

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

--- Begin Message --- Joel Rees wrote: I have two which reliably fail if you put TWO disks on them in a gmirror config within minutes of starting a "make buildworld". Pardon the interruption, but is this two drives on one channel? Two drives can not be on one channel on SATA controller.

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

SoftModems works (well, almost) perfectly under Windows. Some of these works under Linux. SoftModems is the best, because they are cheap and works under Windows. The FreeBSD is puny OS just because they lack support of Software modem. The thing is as worth as much you paid for it. If Silicon Ima

Re: IPv6 router solicitation not being received

Mark, On Thu, 11 Aug 2005, Mark Andrews wrote: > I have a problem in that the router solicitations are not > being received by my FreeBSD IPv6 router unless I enable > promiscuous mode on the tx0 interface. This causes delays > to autoconf for other IPv6 boxes on the net

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

I have two which reliably fail if you put TWO disks on them in a gmirror config within minutes of starting a "make buildworld". Pardon the interruption, but is this two drives on one channel? ___ freebsd-stable@freebsd.org mailing list http://lists.f

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

Karl Denninger wrote: From the online man page for ata.4, which is EXPLICITLY referenced as THE authoritative list of which disk controllers it supports: The currently supported ATA/SATA controller chips are: Acard: ATP850P, ATP860A, ATP860R, ATP865A, ATP865R ALI:

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

Chuck Swiger wrote: Karl Denninger wrote: On Thu, Aug 11, 2005 at 12:46:04AM +0200, S?ren Schmidt wrote: [ ... ] I've already gone WAY out of my way to try to support the sii3112, and I'm not inclined to waste more of my precious spare time on it. However, if it really is that important

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

On Wed, Aug 10, 2005 at 09:47:38PM -0400, Chuck Swiger wrote: > Karl Denninger wrote: > >On Thu, Aug 11, 2005 at 12:46:04AM +0200, S?ren Schmidt wrote: > [ ... ] > >>I've already gone WAY out of my way to try to support the sii3112, > >>and I'm not inclined to waste more of my precious spare time

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

Karl Denninger wrote: On Thu, Aug 11, 2005 at 12:46:04AM +0200, S?ren Schmidt wrote: [ ... ] I've already gone WAY out of my way to try to support the sii3112, and I'm not inclined to waste more of my precious spare time on it. However, if it really is that important to enough people to try

IPv6 router solicitation not being received

I have a problem in that the router solicitations are not being received by my FreeBSD IPv6 router unless I enable promiscuous mode on the tx0 interface. This causes delays to autoconf for other IPv6 boxes on the net until the periodic router announcement i

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

On Thu, Aug 11, 2005 at 12:46:04AM +0200, S?ren Schmidt wrote: > > On 10/08/2005, at 22:51, Karl Denninger wrote: > > > >This is the subject of the PR I filed back in February. > > > >Again, if you want either a controller shipped to you OR access to a > >development machine (e.g. ssh in and play)

Re: Q: How do I suggest a change to a FreeBSD Man page?

[Max, did you really direct your reply to <[EMAIL PROTECTED]> instead of <[EMAIL PROTECTED]>? Probably pushed the wrong button...] On 2005-08-10 at 23:33:29 Max Laier wrote: > As for the request itself. As for > the request itself, I am very reluctant to take manpages off the vendor > branch to

Re: if_sk no PHY found, next iteration

On Wed, Aug 10, 2005 at 09:19:41PM +, Bjoern A. Zeeb wrote: > On Wed, 10 Aug 2005, Juergen Lock wrote: > > Hi, > > > Thanks for the info on your http://sources.zabbadoz.net/freebsd/if_sk.html > > page. Here is a dmesg snippet of another sk problem (Asus A8V deluxe, > > 5.4-R amd64): > > > >

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

On 11/08/2005, at 0:28, Randy Bush wrote: As I said I need reports on 6.0, the ATA driver as is in 5.4 is not supported by me unless you use the ATA mkIII patches.. you know, we just upgraded a system from 4.11 to 7.0 and see problems. we have been chasing cables, and never considered that w

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

On 10/08/2005, at 22:51, Karl Denninger wrote: Since I came in late in this, I need to know what kind of controller we are talking about, and if the problem is still present in 6.0. I plan to backport ATA from 6.0 to 5-stable when it has settled, so 6.0 is the one and only (pre)release to test

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

> As I said I need reports on 6.0, the ATA driver as is in 5.4 is not > supported by me unless you use the ATA mkIII patches.. you know, we just upgraded a system from 4.11 to 7.0 and see problems. we have been chasing cables, and never considered that we could blame all our problems on you and

VIA vt6202 controller not recognised by FreeBSD 5.4-Release (ehci)

Output from pciconf -lv [EMAIL PROTECTED]:7:2 class=0x0c0320 card=0x12340925 chip=0x31041106 rev=0x51 hdr=0x00 vendor= 'VIA Technologies Inc' device= 'VT6202 USB 2.0 Enhanced Host Controller' class= serial bus subclass= USB The same card has it's usb 1.0 compo

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

Am Mittwoch, 10. August 2005 19:48 CEST schrieb 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

Re: Q: How do I suggest a change to a FreeBSD Man page?

On Wednesday 10 August 2005 23:16, J. Nyhuis wrote: > I would like to suggest a change to the FreeBSD man page for > pf.conf. Since pf is now part of the FreeBSD source core, where do I go > to make my suggestion? No contact info is listed in the man page, as > there is for ports. I'm a li

Re: Q: How do I suggest a change to a FreeBSD Man page?

On Wed, Aug 10, 2005 at 02:16:53PM -0700, J. Nyhuis wrote.. > Greetings, > > I would like to suggest a change to the FreeBSD man page for > pf.conf. Since pf is now part of the FreeBSD source core, where do I go > to make my suggestion? No contact info is listed in the man page, as

Re: if_sk no PHY found, next iteration

On Wed, 10 Aug 2005, Juergen Lock wrote: Hi, > Thanks for the info on your http://sources.zabbadoz.net/freebsd/if_sk.html > page. Here is a dmesg snippet of another sk problem (Asus A8V deluxe, > 5.4-R amd64): > > skc0: port 0xa000-0xa0ff mem 0xfba0-0xfba03fff > irq 17 at device 10.0 on pc

Q: How do I suggest a change to a FreeBSD Man page?

Greetings, I would like to suggest a change to the FreeBSD man page for pf.conf. Since pf is now part of the FreeBSD source core, where do I go to make my suggestion? No contact info is listed in the man page, as there is for ports. I'm a little hesitant to just make a change and

if_sk no PHY found, next iteration

Thanks for the info on your http://sources.zabbadoz.net/freebsd/if_sk.html page. Here is a dmesg snippet of another sk problem (Asus A8V deluxe, 5.4-R amd64): skc0: port 0xa000-0xa0ff mem 0xfba0-0xfba03fff irq 17 at device 10.0 on pci0 skc0: Reserved 0x4000 bytes for rid 0x10 type 3 at 0xfb

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

On Wed, Aug 10, 2005 at 08:36:39PM +0200, S?ren Schmidt wrote: > > On 10/08/2005, at 20:05, Scot Hetzel wrote: > >> > >>Since I came in late in this, I need to know what kind of controller > >>we are talking about, and if the problem is still present in 6.0. > >>I plan to backport ATA from 6.0 to

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

On Wed, Aug 10, 2005 at 07:24:01PM +0200, S?ren Schmidt wrote: > > On 10/08/2005, at 17:44, Scot Hetzel wrote: > > >On 8/10/05, Karl Denninger <[EMAIL PROTECTED]> wrote: > > > >>On Wed, Aug 10, 2005 at 09:51:03AM -0400, Mike Tancsa wrote: > >> > >>>At 09:31 AM 10/08/2005, Karl Denninger wrote: >

Re: 5-STABLE cpufreq hotter than est from ports

> Date: Tue, 9 Aug 2005 11:35:29 +0200 > From: Bruno Ducrot <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > On Tue, Aug 02, 2005 at 12:22:02AM +0200, Tijl Coosemans wrote: > > A couple days ago I updated my system and was excited to see cpufreq > > and powerd in 5-stable. Since then however I

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

On 10/08/2005, at 20:29, J. T. Farmer wrote: Scot Hetzel wrote: On 8/10/05, Søren Schmidt <[EMAIL PROTECTED]> wrote: Since I came in late in this, I need to know what kind of controller we are talking about, and if the problem is still present in 6.0. I plan to backport ATA from 6.0 to 5

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

On 10/08/2005, at 20:05, Scot Hetzel wrote: Since I came in late in this, I need to know what kind of controller we are talking about, and if the problem is still present in 6.0. I plan to backport ATA from 6.0 to 5-stable when it has settled, so 6.0 is the one and only (pre)release to test wit

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

Scot Hetzel wrote: On 8/10/05, Søren Schmidt <[EMAIL PROTECTED]> wrote: Since I came in late in this, I need to know what kind of controller we are talking about, and if the problem is still present in 6.0. I plan to backport ATA from 6.0 to 5-stable when it has settled, so 6.0 is the one a

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

On 8/10/05, Søren Schmidt <[EMAIL PROTECTED]> wrote: > > On 10/08/2005, at 17:44, Scot Hetzel wrote: > > > On 8/10/05, Karl Denninger <[EMAIL PROTECTED]> wrote: > > > >> On Wed, Aug 10, 2005 at 09:51:03AM -0400, Mike Tancsa wrote: > >> > >>> At 09:31 AM 10/08/2005, Karl Denninger wrote: > >>> > >

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

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. A

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

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 wa

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

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 th

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

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.

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

On 10/08/2005, at 17:44, Scot Hetzel wrote: On 8/10/05, Karl Denninger <[EMAIL PROTECTED]> wrote: On Wed, Aug 10, 2005 at 09:51:03AM -0400, 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 suc

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

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

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

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 so

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

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 m

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

On 8/10/05, Karl Denninger <[EMAIL PROTECTED]> wrote: > On Wed, Aug 10, 2005 at 09:51:03AM -0400, 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 forthcom

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

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 B

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

On Wed, Aug 10, 2005 at 09:51:03AM -0400, 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

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

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 h

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

On Wed, Aug 10, 2005 at 08:15:50AM -0400, Mike Tancsa wrote: > At 10:46 PM 09/08/2005, 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 > >>

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

At 10:46 PM 09/08/2005, 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 >che

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

On Wed, Aug 10, 2005 at 04:46:18AM +0200, 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

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

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 dr

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

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 beha

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

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, u

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

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 Rap

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

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

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

O. Hartmann wrote: Sometimes I get this error: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599 while the machine still keeps working. Check your disks with MHDD (http://mhdd.com/). -- WBR, Andrey V. Elsukov ___ freebsd-stabl

Re: dhclient: send_packet: No buffer space available

Chuck Swiger wrote: Does the problem go away if you use a trivial "permit all" PF ruleset? When i took off scrub & altq "No buffer space available" messages were gone, but dhclient did still renew the same address. Does the problem go away if you use a trivial IPFW "permit all" instead of

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

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 **

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

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 so

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

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 ** **