[ANNOUNCEMENT] Wiki for discussing P35/IHC9(R)/SATA issues set up

[Aryeh Friedman-2]

http://www.flosoft-systems.com/wiki/index.php

The goals of the wiki are:

1. Clearinghouse for known issues and solutions
2. Cordinate the development of patch set(s) to fix the issues
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

[Justin Hibbits-2]

On Sunday 04 November 2007 01:20:33 Aryeh M. Friedman wrote:
> http://www.flosoft-systems.com/wiki/index.php
>
> The goals of the wiki are:
>
> 1. Clearinghouse for known issues and solutions
> 2. Cordinate the development of patch set(s) to fix the issues

Isn't this what PRs are for?
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

[Aryeh Friedman-2]

Justin Hibbits wrote:

> On Sunday 04 November 2007 01:20:33 Aryeh M. Friedman wrote:
>  
>> http://www.flosoft-systems.com/wiki/index.php
>>
>> The goals of the wiki are:
>>
>> 1. Clearinghouse for known issues and solutions
>> 2. Cordinate the development of patch set(s) to fix the issues
>>    
>
> Isn't this what PRs are for?
>  

There are several people working on the issues thus we are using the
wiki to do internal coordination all the announcement was for was to let
people know where to find intermediate results.

_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

[Xin LI-2]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Aryeh M. Friedman wrote:

> Justin Hibbits wrote:
>> On Sunday 04 November 2007 01:20:33 Aryeh M. Friedman wrote:
>>  
>>> http://www.flosoft-systems.com/wiki/index.php
>>>
>>> The goals of the wiki are:
>>>
>>> 1. Clearinghouse for known issues and solutions
>>> 2. Cordinate the development of patch set(s) to fix the issues
>>>    
>> Isn't this what PRs are for?
>>  
>
> There are several people working on the issues thus we are using the
> wiki to do internal coordination all the announcement was for was to let
> people know where to find intermediate results.

That's exactly why mailing lists exist.

Cheers,
- --
Xin LI <[hidden email]> http://www.delphij.net/
FreeBSD - The Power to Serve!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHLmfMhcUczkLqiksRAmUvAKDa8jZAdO33ecPPdRk8PVURcfrmEgCgw7SP
FW1ANUGXEYrbocm1HRl7VNg=
=pLa9
-----END PGP SIGNATURE-----
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

[Aryeh Friedman-2]

Xin LI wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Aryeh M. Friedman wrote:
>  
>> Justin Hibbits wrote:
>>    
>>> On Sunday 04 November 2007 01:20:33 Aryeh M. Friedman wrote:
>>>  
>>>      
>>>> http://www.flosoft-systems.com/wiki/index.php
>>>>
>>>> The goals of the wiki are:
>>>>
>>>> 1. Clearinghouse for known issues and solutions
>>>> 2. Cordinate the development of patch set(s) to fix the issues
>>>>    
>>>>        
>>> Isn't this what PRs are for?
>>>  
>>>      
>> There are several people working on the issues thus we are using the
>> wiki to do internal coordination all the announcement was for was to let
>> people know where to find intermediate results.
>>    
>
> That's exactly why mailing lists exist.

The wiki was not meant to replace the list just be a central record
keeping location for the group working on the issue.
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

[Xin LI-2]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Aryeh M. Friedman wrote:
> The wiki was not meant to replace the list just be a central record
> keeping location for the group working on the issue.

Well, I think that if there is a problem then we need to work it out
ASAP, and this is not what a wiki for.  What wiki's are better suited
for is some issues that are not easily resolved, and be documented.

Let's see what the "issues" on the wiki:

 - Mis-numbered adXXX on SATA drives
This is non-issue.  It's well documented in ata(4) that you can change
the behavior by removing the anti-foot-shooting option ATA_STATIC_ID
from your kernel configuration;

 - Wrong SATA type/speed reported
More information is needed if you really want to have this problem
resolved, like atacontrol output, etc.

 - PATA/SATA co-existence
Is the PATA chip supported by the driver?  What's its PCI IDs?

Also I would like to say that it is much more useful if you will have
someone who donate the proper hardware to sos@, our Mr. ATA.  He is very
knowledgeable about the driver and ATA/SATA stuff, and a very responsive
person.

Cheers,
- --
Xin LI <[hidden email]> http://www.delphij.net/
FreeBSD - The Power to Serve!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHLrIQhcUczkLqiksRAuuoAKDBGDUhfRsPWWqL+jgI02+eYTnwNACgldao
ANdGNE+XmjvF8zgNhtbiVLk=
=CRXn
-----END PGP SIGNATURE-----
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

[Aryeh Friedman-2]

Xin LI wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Aryeh M. Friedman wrote:
>  
>> The wiki was not meant to replace the list just be a central record
>> keeping location for the group working on the issue.
>>    
>
> Well, I think that if there is a problem then we need to work it out
> ASAP, and this is not what a wiki for.  What wiki's are better suited
> for is some issues that are not easily resolved, and be documented.
>  

Since I am not the only person with these issues, see "sata ihc9r"
thread in -current, just the only one to document them formally (so far)
[hopefully the other two will write a good summary of the acd issue they
are seeing] there is need for easy reference for anyone working on
patches (or new frameworks such as one of person informed me of
privately).   Among other things the wiki is meant as a way of knowinig
the status of each task (may not be issue based per se).  I suspect some
of these issues may be quickly resolved and the others will require some
research thus they may spread out of a few weeks or months.
> Let's see what the "issues" on the wiki:
>
>  - Mis-numbered adXXX on SATA drives
> This is non-issue.  It's well documented in ata(4) that you can change
> the behavior by removing the anti-foot-shooting option ATA_STATIC_ID
> from your kernel configuration;
>  

The default behaviour should be fixed if it is so easy then.
>  - Wrong SATA type/speed reported
> More information is needed if you really want to have this problem
> resolved, like atacontrol output, etc.
>  

See the SATA ihc9 and previous threads if you really need to know all
the messy details but the bottom line is I have been told by several of
the ATA developers that since they do not have IHC9 machines P35/IHC9
owners where on their own (and thus the need for informal group the wiki
is aimed at)

>  - PATA/SATA co-existence
> Is the PATA chip supported by the driver?  What's its PCI IDs?
>  

You accuse me of not doing my research... a simple search of the various
threads these issues have come up will tell you that:

1. Yes it does show up (I can even boot from it) but it is complete gone
from dmesg (even verbose), pciutil, etc.

2. The answer to the type/speed type issue from the commuhity is the
same one I got here

> Also I would like to say that it is much more useful if you will have
> someone who donate the proper hardware to sos@, our Mr. ATA.  He is very
> knowledgeable about the driver and ATA/SATA stuff, and a very responsive
> person.
>  

1. I will have to look it up but I think he is the one of the people
that told me p35/ihc9 owners where on their own.

2. Some of the issues are pressing and some are just annonyances the
only pressing one for me is the PATA/SATA one and that is likelly to be
the last one fixed because I suspect it relies on fixing the type/speed
and (yet to be documented) acd issue(s).


--
Aryeh M. Friedman
Developer, no business friendly
http://www.flosoft-systems.com

_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

[Xin LI-2]

Aryeh M. Friedman wrote:
> Since I am not the only person with these issues, see "sata ihc9r"
> thread in -current, just the only one to document them formally (so far)
> [hopefully the other two will write a good summary of the acd issue they
> are seeing] there is need for easy reference for anyone working on
> patches (or new frameworks such as one of person informed me of
> privately).   Among other things the wiki is meant as a way of knowinig
> the status of each task (may not be issue based per se).  I suspect some
> of these issues may be quickly resolved and the others will require some
> research thus they may spread out of a few weeks or months.

Ok

>> Let's see what the "issues" on the wiki:
>>
>>  - Mis-numbered adXXX on SATA drives
>> This is non-issue.  It's well documented in ata(4) that you can change
>> the behavior by removing the anti-foot-shooting option ATA_STATIC_ID
>> from your kernel configuration;
>>  
>
> The default behaviour should be fixed if it is so easy then.

How come the number is so important for you?  What do you think if you
have to drop into single user mode and adjust fstab manually and the box
is several thousands of miles away from you after a simple 'make
kernel'?  I think changing this behavior is a big POLA and not the right
thing to do.

>>  - Wrong SATA type/speed reported
>> More information is needed if you really want to have this problem
>> resolved, like atacontrol output, etc.
>
> See the SATA ihc9 and previous threads if you really need to know all
> the messy details but the bottom line is I have been told by several of
> the ATA developers that since they do not have IHC9 machines P35/IHC9
> owners where on their own (and thus the need for informal group the wiki
> is aimed at)

Please provide links on the wiki if you really want it to be useful.

I think the only ich9 issue I am aware of so far is that a specific
model of it is not recognized.  This is fixed in HEAD and RELENG_7.

>>  - PATA/SATA co-existence
>> Is the PATA chip supported by the driver?  What's its PCI IDs?
>
> You accuse me of not doing my research... a simple search of the various
> threads these issues have come up will tell you that:
>
> 1. Yes it does show up (I can even boot from it) but it is complete gone
> from dmesg (even verbose), pciutil, etc.

Ditto.

> 2. The answer to the type/speed type issue from the commuhity is the
> same one I got here

Is the problem still exist for latest RELENG_7 and RELENG_6?  Who can
provide some basic testing for a new snapshot?

No, it does not help if that's just "it panics", "foo is not supported"
if no detailed information is provided and we don't have our hands on
the actual hardware.

>> Also I would like to say that it is much more useful if you will have
>> someone who donate the proper hardware to sos@, our Mr. ATA.  He is very
>> knowledgeable about the driver and ATA/SATA stuff, and a very responsive
>> person.
>
> 1. I will have to look it up but I think he is the one of the people
> that told me p35/ihc9 owners where on their own.

Again, it does not make sense if we don't even know how to contact these
users.

> 2. Some of the issues are pressing and some are just annonyances the
> only pressing one for me is the PATA/SATA one and that is likelly to be

Could you please provide some more detailed information (e.g. previous
posted message-id or a link to mail archive)?

> the last one fixed because I suspect it relies on fixing the type/speed
> and (yet to be documented) acd issue(s).

Cheers,
--
Xin LI <[hidden email]> http://www.delphij.net/
FreeBSD - The Power to Serve!

[Aryeh Friedman-2]

LI Xin wrote:

>
>>> Let's see what the "issues" on the wiki:
>>>
>>>  - Mis-numbered adXXX on SATA drives
>>> This is non-issue.  It's well documented in ata(4) that you can change
>>> the behavior by removing the anti-foot-shooting option ATA_STATIC_ID
>>> from your kernel configuration;
>>>  
>>>      
>> The default behaviour should be fixed if it is so easy then.
>>    
>
> How come the number is so important for you?  What do you think if you
> have to drop into single user mode and adjust fstab manually and the box
> is several thousands of miles away from you after a simple 'make
> kernel'?  I think changing this behavior is a big POLA and not the right
> thing to do.
>  

It prevents certain automated config issues that may or may not be
issues as stuff moves more mass market... I know FreeBSD unlike Linux
has no aim to be a non-techinical enduser OS but I find my self
increasingly recommended it as the prefered UNIX desktop enviroment
because so stability and the general ease of using the ports/pkg system
compared to RPM's... sad to say many of the end-user oriented tools
occasionally make naive but critical assumptions about how a machine is
layed out.

>  
>>>  - Wrong SATA type/speed reported
>>> More information is needed if you really want to have this problem
>>> resolved, like atacontrol output, etc.
>>>      
>> See the SATA ihc9 and previous threads if you really need to know all
>> the messy details but the bottom line is I have been told by several of
>> the ATA developers that since they do not have IHC9 machines P35/IHC9
>> owners where on their own (and thus the need for informal group the wiki
>> is aimed at)
>>    
>
> Please provide links on the wiki if you really want it to be useful.
>  

I am at the end of a long day so I will dig the links up and post them
tommorow (and send you copies)
> I think the only ich9 issue I am aware of so far is that a specific
> model of it is not recognized.  This is fixed in HEAD and RELENG_7.
>  

If you don't have an ICH machine I invite you to get one and verify the
issues ;-)

>  
>>>  - PATA/SATA co-existence
>>> Is the PATA chip supported by the driver?  What's its PCI IDs?
>>>      
>> You accuse me of not doing my research... a simple search of the various
>> threads these issues have come up will tell you that:
>>
>> 1. Yes it does show up (I can even boot from it) but it is complete gone
>> from dmesg (even verbose), pciutil, etc.
>>    
>
> Ditto.
>
>  
>> 2. The answer to the type/speed type issue from the commuhity is the
>> same one I got here
>>    
>
> Is the problem still exist for latest RELENG_7 and RELENG_6?  Who can
> provide some basic testing for a new snapshot?
>  

I csup my version of -CURRENT every day (do a buildkernel anytime there
are more then 10 commulative changes):

FreeBSD monster 8.0-CURRENT FreeBSD 8.0-CURRENT #1: Sat Nov  3 21:33:49
EDT 2007     aryeh@monster:/usr/obj/usr/src/sys/MONSTER  amd64

and do a build world about once a week plus a ground up rebuild of all
ports twice a month... in other words I am as current as anyone and the
issues still persist.
> No, it does not help if that's just "it panics", "foo is not supported"
> if no detailed information is provided and we don't have our hands on
> the actual hardware.
>  

I have submitted the complete verbose dmesg, pciutil -l and everything
to several people and all of them have come to the conclusion that there
is no obvious smoking gone beyond ("it just doesn't work")...  Thus the
comment of ICH9 owners are on their own... Next time I reboot I will
send you a copy if you really want it.

>  
>>> Also I would like to say that it is much more useful if you will have
>>> someone who donate the proper hardware to sos@, our Mr. ATA.  He is very
>>> knowledgeable about the driver and ATA/SATA stuff, and a very responsive
>>> person.
>>>      
>> 1. I will have to look it up but I think he is the one of the people
>> that told me p35/ihc9 owners where on their own.
>>    
>
> Again, it does not make sense if we don't even know how to contact these
> users.
>  

I will pull this data when I get in tommorow.

--
Aryeh M. Friedman
Developer, not business, friendly
http://www.flosoft-systems.com

_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

[Xin LI-2]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Aryeh M. Friedman wrote:
> LI Xin wrote:
[...]

>>>>      
>>> The default behaviour should be fixed if it is so easy then.
>>>    
>> How come the number is so important for you?  What do you think if you
>> have to drop into single user mode and adjust fstab manually and the box
>> is several thousands of miles away from you after a simple 'make
>> kernel'?  I think changing this behavior is a big POLA and not the right
>> thing to do.
>
> It prevents certain automated config issues that may or may not be
> issues as stuff moves more mass market... I know FreeBSD unlike Linux
> has no aim to be a non-techinical enduser OS but I find my self
> increasingly recommended it as the prefered UNIX desktop enviroment
> because so stability and the general ease of using the ports/pkg system
> compared to RPM's... sad to say many of the end-user oriented tools
> occasionally make naive but critical assumptions about how a machine is
> layed out.

Which tool?  This is apparently a bug of the tool, because the tool
won't work on Solaris either.

>>>>  - Wrong SATA type/speed reported
>>>> More information is needed if you really want to have this problem
>>>> resolved, like atacontrol output, etc.
>>>>      
>>> See the SATA ihc9 and previous threads if you really need to know all
>>> the messy details but the bottom line is I have been told by several of
>>> the ATA developers that since they do not have IHC9 machines P35/IHC9
>>> owners where on their own (and thus the need for informal group the wiki
>>> is aimed at)
>>>    
>> Please provide links on the wiki if you really want it to be useful.
>>  
> I am at the end of a long day so I will dig the links up and post them
> tommorow (and send you copies)
>
>> I think the only ich9 issue I am aware of so far is that a specific
>> model of it is not recognized.  This is fixed in HEAD and RELENG_7.
>
> If you don't have an ICH machine I invite you to get one and verify the
> issues ;-)

Mine has no problem, and I can not afford to buy a new piece of hardware
right now.

>>> 2. The answer to the type/speed type issue from the commuhity is the
>>> same one I got here
>>>    
>> Is the problem still exist for latest RELENG_7 and RELENG_6?  Who can
>> provide some basic testing for a new snapshot?
>>  
>
> I csup my version of -CURRENT every day (do a buildkernel anytime there
> are more then 10 commulative changes):
>
> FreeBSD monster 8.0-CURRENT FreeBSD 8.0-CURRENT #1: Sat Nov  3 21:33:49
> EDT 2007     aryeh@monster:/usr/obj/usr/src/sys/MONSTER  amd64
>
> and do a build world about once a week plus a ground up rebuild of all
> ports twice a month... in other words I am as current as anyone and the
> issues still persist.

PCI ID and dmesg?

>> No, it does not help if that's just "it panics", "foo is not supported"
>> if no detailed information is provided and we don't have our hands on
>> the actual hardware.
>
> I have submitted the complete verbose dmesg, pciutil -l and everything
> to several people and all of them have come to the conclusion that there
> is no obvious smoking gone beyond ("it just doesn't work")...  Thus the
> comment of ICH9 owners are on their own... Next time I reboot I will
> send you a copy if you really want it.

Yes, please.  These information is very important for knowing how to
change the situation, thanks.

Cheers,
- --
Xin LI <[hidden email]> http://www.delphij.net/
FreeBSD - The Power to Serve!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHL12ahcUczkLqiksRAieBAJ0Ut4zyLxTzQD3O6xlcKI+8forcMgCgxrCM
6aqCOI+3FikoTFFG54GFzOQ=
=1uQ2
-----END PGP SIGNATURE-----
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

[Samira Nox]

Please let me know which files you need.


sam

On Mon, 05 Nov 2007 19:14:50 +0100, Xin LI <[hidden email]> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Aryeh M. Friedman wrote:
>> LI Xin wrote:
> [...]
>>>>>
>>>> The default behaviour should be fixed if it is so easy then.
>>>>
>>> How come the number is so important for you?  What do you think if you
>>> have to drop into single user mode and adjust fstab manually and the  
>>> box
>>> is several thousands of miles away from you after a simple 'make
>>> kernel'?  I think changing this behavior is a big POLA and not the  
>>> right
>>> thing to do.
>>
>> It prevents certain automated config issues that may or may not be
>> issues as stuff moves more mass market... I know FreeBSD unlike Linux
>> has no aim to be a non-techinical enduser OS but I find my self
>> increasingly recommended it as the prefered UNIX desktop enviroment
>> because so stability and the general ease of using the ports/pkg system
>> compared to RPM's... sad to say many of the end-user oriented tools
>> occasionally make naive but critical assumptions about how a machine is
>> layed out.
>
> Which tool?  This is apparently a bug of the tool, because the tool
> won't work on Solaris either.
>
>>>>>  - Wrong SATA type/speed reported
>>>>> More information is needed if you really want to have this problem
>>>>> resolved, like atacontrol output, etc.
>>>>>
>>>> See the SATA ihc9 and previous threads if you really need to know all
>>>> the messy details but the bottom line is I have been told by several  
>>>> of
>>>> the ATA developers that since they do not have IHC9 machines P35/IHC9
>>>> owners where on their own (and thus the need for informal group the  
>>>> wiki
>>>> is aimed at)
>>>>
>>> Please provide links on the wiki if you really want it to be useful.
>>>
>> I am at the end of a long day so I will dig the links up and post them
>> tommorow (and send you copies)
>>
>>> I think the only ich9 issue I am aware of so far is that a specific
>>> model of it is not recognized.  This is fixed in HEAD and RELENG_7.
>>
>> If you don't have an ICH machine I invite you to get one and verify the
>> issues ;-)
>
> Mine has no problem, and I can not afford to buy a new piece of hardware
> right now.
>
>>>> 2. The answer to the type/speed type issue from the commuhity is the
>>>> same one I got here
>>>>
>>> Is the problem still exist for latest RELENG_7 and RELENG_6?  Who can
>>> provide some basic testing for a new snapshot?
>>>
>>
>> I csup my version of -CURRENT every day (do a buildkernel anytime there
>> are more then 10 commulative changes):
>>
>> FreeBSD monster 8.0-CURRENT FreeBSD 8.0-CURRENT #1: Sat Nov  3 21:33:49
>> EDT 2007     aryeh@monster:/usr/obj/usr/src/sys/MONSTER  amd64
>>
>> and do a build world about once a week plus a ground up rebuild of all
>> ports twice a month... in other words I am as current as anyone and the
>> issues still persist.
>
> PCI ID and dmesg?
>
>>> No, it does not help if that's just "it panics", "foo is not supported"
>>> if no detailed information is provided and we don't have our hands on
>>> the actual hardware.
>>
>> I have submitted the complete verbose dmesg, pciutil -l and everything
>> to several people and all of them have come to the conclusion that there
>> is no obvious smoking gone beyond ("it just doesn't work")...  Thus the
>> comment of ICH9 owners are on their own... Next time I reboot I will
>> send you a copy if you really want it.
>
> Yes, please.  These information is very important for knowing how to
> change the situation, thanks.
>
> Cheers,
> - --
> Xin LI <[hidden email]> http://www.delphij.net/
> FreeBSD - The Power to Serve!
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (FreeBSD)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFHL12ahcUczkLqiksRAieBAJ0Ut4zyLxTzQD3O6xlcKI+8forcMgCgxrCM
> 6aqCOI+3FikoTFFG54GFzOQ=
> =1uQ2
> -----END PGP SIGNATURE-----
> _______________________________________________
> [hidden email] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to  
> "[hidden email]"

--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

[Xin LI-2]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

sam wrote:
> Please let me know which files you need.

/var/run/dmesg.boot
and output from:
pciconf -lv

Thanks!

Cheers,
- --
Xin LI <[hidden email]> http://www.delphij.net/
FreeBSD - The Power to Serve!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHL2dzhcUczkLqiksRAt4uAJ0YDZyBrZLibr48iUbOxvOvBtNXNQCeL7dg
Sd2v/naNEiZZwziFhgeMuZY=
=dLsK
-----END PGP SIGNATURE-----
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

[Samira Nox]

here they are, thanks

sam


On Mon, 05 Nov 2007 19:56:51 +0100, Xin LI <[hidden email]> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> sam wrote:
>> Please let me know which files you need.
>
> /var/run/dmesg.boot
> and output from:
> pciconf -lv
>
> Thanks!
>
> Cheers,
> - --
> Xin LI <[hidden email]> http://www.delphij.net/
> FreeBSD - The Power to Serve!
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (FreeBSD)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFHL2dzhcUczkLqiksRAt4uAJ0YDZyBrZLibr48iUbOxvOvBtNXNQCeL7dg
> Sd2v/naNEiZZwziFhgeMuZY=
> =dLsK
> -----END PGP SIGNATURE-----

--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

[Xin LI-2]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi, Sam,

sam wrote:
> here they are, thanks

According to your dmesg.boot output it seems that all devices has been
successfully probed:

ad4: 305244MB <WDC WD3200AAKS-00VYA0 12.01B02> at ata2-master SATA300
ad6: 305244MB <WDC WD3200AAKS-00VYA0 12.01B02> at ata3-master SATA300
ad8: 238475MB <WDC WD2500KS-00MJB0 02.01C03> at ata4-master SATA300
acd0: DVDR <Optiarc DVD RW AD-7170S/1.00> at ata5-master SATA150
acd1: DVDROM <ASUS DVD-E616A3T/1.11> at ata6-master SATA150
acd2: DVDROM <ASUS DVD-E616A3T/1.11> at ata7-master SATA150

Does this match your hardware configuration, or do you have some other
problems with the driver?

Cheers,
- --
Xin LI <[hidden email]> http://www.delphij.net/
FreeBSD - The Power to Serve!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHL2sChcUczkLqiksRAhpLAJ9UlI6yi5qL7qAhMJhUJs9l/kqP7QCgubc/
mHEueOYcLFblVinJHCJWWdM=
=I69/
-----END PGP SIGNATURE-----
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

[Byung-Hee HWANG]

On Sun, 2007-11-04 at 16:46 -0800, Xin LI wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Aryeh M. Friedman wrote:
[...snip...]
> > There are several people working on the issues thus we are using the
> > wiki to do internal coordination all the announcement was for was to let
> > people know where to find intermediate results.
>
> That's exactly why mailing lists exist.

+999 ;;;;;;;;;;;;;;;;;;

--
"Don Michael."
                -- Peter Clemenza, "Chapter 31", page 435

_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

[Samira Nox]

Hi

The information FreeBSD returns about the drives is correct.

I noticed following problems

1) Trying to mount a cd is one of the problems. This freezes the system
for about 1 to 2 minutes.
Nov  5 20:17:46 sam kernel: acd1: FAILURE - MODE_SENSE_BIG timed out
Nov  5 20:18:17 sam kernel: acd1: TIMEOUT - READ_BIG retrying (1 retry  
left)
Nov  5 20:18:48 sam kernel: acd1: TIMEOUT - READ_BIG retrying (0 retries  
left)
Nov  5 20:19:18 sam kernel: acd1: FAILURE - READ_BIG timed out
Nov  5 20:19:19 sam kernel: GEOM_LABEL: Label for provider acd1t01 is  
iso9660/FreeBSD_bootonly.
After that, the cd is mounted and works just fine.

2) Trying to watch a dvd.
Nov  5 20:24:19 sam kernel: acd1: FAILURE - MODE_SENSE_BIG timed out
Nov  5 20:24:49 sam kernel: acd1: WARNING - SETFEATURES SET TRANSFER MODE  
taskqueue timeout - completing request directly
Nov  5 20:24:53 sam kernel: acd1: WARNING - SETFEATURES SET TRANSFER MODE  
taskqueue timeout - completing request directly
Nov  5 20:24:53 sam kernel: acd1: FAILURE - SEND_KEY timed out
Nov  5 20:25:03 sam kernel: acd1: FAILURE - MODE_SENSE_BIG timed out
I tried this with several dvds of code 1 and 2. The same behaviour on the
Optiarc and on the Asus drives.

3) If I add device atapicam to the kernel, the system won't boot. It will
still recognize the drives, but it will then produce read timeouts, over
and over. I tried this with hw.ata.atapi_dma set to 0 and 1.

4) Audio CDs don't seem to be recognized as such in the asus drives. It
seems, that the Optiarc recognizes and plays them. Again, testet with  
different
cds. The errors of the drives are:
asus:
Nov  5 20:39:10 sam kernel: acd1: TIMEOUT - READ_BIG retrying (0 retries  
left)
Nov  5 20:39:41 sam kernel: acd1: FAILURE - READ_BIG timed out
Nov  5 20:41:30 sam kernel: acd1: FAILURE - MODE_SENSE_BIG timed out
Nov  5 20:42:02 sam kernel: acd1: TIMEOUT - READ_BIG retrying (1 retry  
left)
Nov  5 20:42:32 sam kernel: acd1: TIMEOUT - READ_BIG retrying (0 retries  
left)
Nov  5 20:43:03 sam kernel: acd1: FAILURE - READ_BIG timed out
optiarc
Nov  5 20:44:11 sam kernel: acd0: FAILURE - MODE_SENSE_BIG timed out
But as mentioned, Optiarc is able to play the audiocd.

5) My devices are numberd from 4 upward. This is not a big deal. But it
is confusing. If I activate the onboard jmicron controller the ad4 moves
to ad10. [Motherboard Gigabyte P35-DS4]

6) Boot freeze [timeout of drives] when having a cdrom in the drive.




sam



On Mon, 05 Nov 2007 20:12:02 +0100, Xin LI <[hidden email]> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi, Sam,
>
> sam wrote:
>> here they are, thanks
>
> According to your dmesg.boot output it seems that all devices has been
> successfully probed:
>
> ad4: 305244MB <WDC WD3200AAKS-00VYA0 12.01B02> at ata2-master SATA300
> ad6: 305244MB <WDC WD3200AAKS-00VYA0 12.01B02> at ata3-master SATA300
> ad8: 238475MB <WDC WD2500KS-00MJB0 02.01C03> at ata4-master SATA300
> acd0: DVDR <Optiarc DVD RW AD-7170S/1.00> at ata5-master SATA150
> acd1: DVDROM <ASUS DVD-E616A3T/1.11> at ata6-master SATA150
> acd2: DVDROM <ASUS DVD-E616A3T/1.11> at ata7-master SATA150
>
> Does this match your hardware configuration, or do you have some other
> problems with the driver?
>
> Cheers,
> - --
> Xin LI <[hidden email]> http://www.delphij.net/
> FreeBSD - The Power to Serve!
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (FreeBSD)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFHL2sChcUczkLqiksRAhpLAJ9UlI6yi5qL7qAhMJhUJs9l/kqP7QCgubc/
> mHEueOYcLFblVinJHCJWWdM=
> =I69/
> -----END PGP SIGNATURE-----

--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

[韓家標 Bill Hacker]

sam wrote:

> Hi
>
> The information FreeBSD returns about the drives is correct.
>
> I noticed following problems
>
> 1) Trying to mount a cd is one of the problems. This freezes the system
> for about 1 to 2 minutes.
> Nov  5 20:17:46 sam kernel: acd1: FAILURE - MODE_SENSE_BIG timed out
> Nov  5 20:18:17 sam kernel: acd1: TIMEOUT - READ_BIG retrying (1 retry
> left)
> Nov  5 20:18:48 sam kernel: acd1: TIMEOUT - READ_BIG retrying (0 retries
> left)
> Nov  5 20:19:18 sam kernel: acd1: FAILURE - READ_BIG timed out
> Nov  5 20:19:19 sam kernel: GEOM_LABEL: Label for provider acd1t01 is
> iso9660/FreeBSD_bootonly.
> After that, the cd is mounted and works just fine.
>
> 2) Trying to watch a dvd.
> Nov  5 20:24:19 sam kernel: acd1: FAILURE - MODE_SENSE_BIG timed out
> Nov  5 20:24:49 sam kernel: acd1: WARNING - SETFEATURES SET TRANSFER
> MODE taskqueue timeout - completing request directly
> Nov  5 20:24:53 sam kernel: acd1: WARNING - SETFEATURES SET TRANSFER
> MODE taskqueue timeout - completing request directly
> Nov  5 20:24:53 sam kernel: acd1: FAILURE - SEND_KEY timed out
> Nov  5 20:25:03 sam kernel: acd1: FAILURE - MODE_SENSE_BIG timed out
> I tried this with several dvds of code 1 and 2. The same behaviour on the
> Optiarc and on the Asus drives.
>
> 3) If I add device atapicam to the kernel, the system won't boot. It will
> still recognize the drives, but it will then produce read timeouts, over
> and over. I tried this with hw.ata.atapi_dma set to 0 and 1.
>
> 4) Audio CDs don't seem to be recognized as such in the asus drives. It
> seems, that the Optiarc recognizes and plays them. Again, testet with
> different
> cds. The errors of the drives are:
> asus:
> Nov  5 20:39:10 sam kernel: acd1: TIMEOUT - READ_BIG retrying (0 retries
> left)
> Nov  5 20:39:41 sam kernel: acd1: FAILURE - READ_BIG timed out
> Nov  5 20:41:30 sam kernel: acd1: FAILURE - MODE_SENSE_BIG timed out
> Nov  5 20:42:02 sam kernel: acd1: TIMEOUT - READ_BIG retrying (1 retry
> left)
> Nov  5 20:42:32 sam kernel: acd1: TIMEOUT - READ_BIG retrying (0 retries
> left)
> Nov  5 20:43:03 sam kernel: acd1: FAILURE - READ_BIG timed out
> optiarc
> Nov  5 20:44:11 sam kernel: acd0: FAILURE - MODE_SENSE_BIG timed out
> But as mentioned, Optiarc is able to play the audiocd.
>
> 5) My devices are numberd from 4 upward. This is not a big deal. But it
> is confusing. If I activate the onboard jmicron controller the ad4 moves
> to ad10. [Motherboard Gigabyte P35-DS4]
>
> 6) Boot freeze [timeout of drives] when having a cdrom in the drive.
>
>
>
>
> sam

Presuming a good cable, this looks very much like a hardware (and its onboard
firmware) issue from where I sit.

I've had one of the R&D boxen with the JMicron JMB363 controller turned
back-to-front for a month, didn't notice it was equipped with an ancient 48X CD
unit that had been seriously problematic on early 4.X.

On either a GA G33-DS3R or Asus P5K, there has been no difficulty with what it
sees as a "CD-948E/TKU/T4B" on acd0.

Spins it up and takes a, extra few seconds (only) to sneak a peek at the media
during boot if there IS any media, else not, but no significant delay.

Thereafter it has been used to install a great many odds and sods to Qemu host,
sometimes left attached to the guests and media ejected/changed, again w/o
hiccups from either CLI or xfce4. Never an errmsg, and operates fast.

FreeBSD 6.X, 7-CURRENT, 7-PRE, 7-BETA1, 8-CURRENT, both i386 & AMD-64.

Mind - this is a pretty 'basic' unit as well as obsolete, but I'd still suggest
trying the system with one or more other CDR/DVD - even antiques - than the one
you now have to see if the problem migrates with the drive hardware rahter than
the MB/controller or OS.

Bill Hacker

>
>
>
> On Mon, 05 Nov 2007 20:12:02 +0100, Xin LI <[hidden email]> wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi, Sam,
>>
>> sam wrote:
>>> here they are, thanks
>>
>> According to your dmesg.boot output it seems that all devices has been
>> successfully probed:
>>
>> ad4: 305244MB <WDC WD3200AAKS-00VYA0 12.01B02> at ata2-master SATA300
>> ad6: 305244MB <WDC WD3200AAKS-00VYA0 12.01B02> at ata3-master SATA300
>> ad8: 238475MB <WDC WD2500KS-00MJB0 02.01C03> at ata4-master SATA300
>> acd0: DVDR <Optiarc DVD RW AD-7170S/1.00> at ata5-master SATA150
>> acd1: DVDROM <ASUS DVD-E616A3T/1.11> at ata6-master SATA150
>> acd2: DVDROM <ASUS DVD-E616A3T/1.11> at ata7-master SATA150
>>
>> Does this match your hardware configuration, or do you have some other
>> problems with the driver?
>>
>> Cheers,
>> - --
>> Xin LI <[hidden email]>    http://www.delphij.net/
>> FreeBSD - The Power to Serve!
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.7 (FreeBSD)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>>
>> iD8DBQFHL2sChcUczkLqiksRAhpLAJ9UlI6yi5qL7qAhMJhUJs9l/kqP7QCgubc/
>> mHEueOYcLFblVinJHCJWWdM=
>> =I69/
>> -----END PGP SIGNATURE-----
>
>
>
> --Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
> _______________________________________________
> [hidden email] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "[hidden email]"
>

_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

[Samira Nox]

On Mon, 05 Nov 2007 21:24:37 +0100, 韓家標 Bill Hacker  
<[hidden email]> wrote:


> On either a GA G33-DS3R or Asus P5K, there has been no difficulty with  
> what it sees as a "CD-948E/TKU/T4B" on acd0.
Is this an IDE or SATA drive?


sam


--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

[韓家標 Bill Hacker]

sam wrote:

> On Mon, 05 Nov 2007 21:24:37 +0100, 韓家標 Bill Hacker
> <[hidden email]> wrote:
>
>
>> On either a GA G33-DS3R or Asus P5K, there has been no difficulty with
>> what it sees as a "CD-948E/TKU/T4B" on acd0.
> Is this an IDE or SATA drive?
>
>
> sam
>

IDE & ancient.

Grant - SATA has to be better sorted than it is now, but the suggestion to try
(an)other CD/DVD drive(s) holds, as much for pinning down the fault as fixing it.

Dfferent place must be looked at if it faults with PATA as well as SATA, or only
with one not the other.

JFWIW, I've also run 2.5" and 3.5" PATA HDD and 2.5: and 3.5" SATA HDD with 3
different makes of PATA-SATA PCB adaptors on that same IDE channel here.

Only hassle when I had both the HDD and CD jumpered as 'master' or a WD HDD not
jumpered as master-with-slave-present.

Ergo I still think it is specific to your hardware, ELSE it would be a far more
commonly reported issue already. Note that MOST such posts have had to do with
HDD or arrays of same, not nearly as many about CD / DVD.

Bill


_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"

[Aryeh Friedman-2]

Sam--

    Can you update the issues page on the wiki so we have a record of
these problems.

--
Aryeh M. Friedman
Developer, not business, friendly
http://www.flosoft-systems.com

_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"