kern/188897: [dc] dc ethernet driver seems to prevent the detection of other NIC chipsets

Sat May 10 15:30:01 UTC 2014

The following reply was made to PR kern/188897; it has been noted by GNATS.

From: "Mr. Clif" <test at eugeneweb.com>
To: bug-followup at FreeBSD.org, clif at eugeneweb.com
Cc:  
Subject: Re: kern/188897: [dc] dc ethernet driver seems to prevent the detection
 of other NIC chipsets
Date: Sat, 10 May 2014 08:29:03 -0700

 This is a multi-part message in MIME format.
 --------------030302030805050404010504
 Content-Type: text/plain; charset=ISO-8859-1; format=flowed
 Content-Transfer-Encoding: 7bit

 On 04/30/2014 09:12 AM, John Baldwin wrote:
 > On Tuesday, April 29, 2014 7:42:29 pm Mr. Clif wrote:
 >> Hi Guys,
 >>
 >> I've been playing with the new patch, and found a few problems that I
 >> posted in PR 188897:
 >>
 >> http://www.freebsd.org/cgi/query-pr.cgi?pr=188897
 >>
 >> and this one is about another quad port card in the same Atom MoBo:
 >>
 >> http://www.freebsd.org/cgi/query-pr.cgi?pr=188899
 >>
 >> I would be happy to test any new fixes you want me to try.
 > Can you disable agp and see if that fixes things?  (hint.agp.0.disabled=1 at
 > the loader prompt)
 >

 On 05/01/2014 09:27 AM, Mr. Clif wrote:
 > Ok,
 >
 > sorry about the delay, now that I'm set up again the turnaround time 
 > should be a lot faster.
 >
 > At the loader prompt I typed:
 >
 > set hint.agp.0.disabled=1
 > boot
 >
 > After a lot of testing, the only possible difference I can see is that 
 > the re0 interface is always? there when the agp is disabled and not 
 > always there by default. By the way, this board doesn't have an AGP 
 > port. Oh and I only checked the dc board, since it didn't work I 
 > didn't go on to the sun board. :-)
 >
 >     Clif
 >

 On 05/08/2014 09:10 AM, John Baldwin wrote:
 > On Wednesday, May 07, 2014 6:37:59 pm Mr. Clif wrote:
 >> Ok sorry I didn't get anywhere with the AGP experiment. I guess I'll put
 >> the machine away until you have other things for me to try.
 > Sorry, I have been focusing on another PCI bug people were running into that
 > was fixed earlier this week.  However, that one involved resources failing to
 > allocate at all, so I'm not sure it is related to your case.  Hmm, I see your
 > last issue was related to the special ISA decoding bits.  Can you pick one
 > of the cases to focus on for now and capture a verbose dmesg from a HEAD
 > kernel?  'devinfo -r' and 'devinfo -u' output from the non-working kernel
 > would also be good.
 >
 On 05/10/2014 08:18 AM, Mr. Clif wrote:
 > Opps I almost didn't see this email, too much spam I guess :-(
 >
 > Sounds like you want me to get the latest from the FreeBSD repo. Could 
 > you please give me the URL and commands for that so I don't get the 
 > wrong code?
 >
 > By last issue do you mean PR 179033? 
 > <http://www.freebsd.org/cgi/query-pr.cgi?pr=179033> Since that one was 
 > closed I opened 188897 but they are both basically the same.
 > I'm not sure what symtoms the ISA decoding bits cause, to me it's just 
 > that some of the NICs are unusable, but sure I can run those commands, 
 > If you give me the git commands to get the correct code. I'll get the 
 > non-working kernel now too.
 >
 >     Clif

 --------------030302030805050404010504
 Content-Type: text/html; charset=ISO-8859-1
 Content-Transfer-Encoding: 7bit

 <html>
   <head>

     <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
   </head>
   <body bgcolor="#FFFFFF" text="#000000">
     <div class="moz-cite-prefix">On 04/30/2014 09:12 AM, John Baldwin
       wrote:<br>
     </div>
     <blockquote cite="mid:201404301212.28623.jhb at freebsd.org"
       type="cite">
       <pre wrap="">On Tuesday, April 29, 2014 7:42:29 pm Mr. Clif wrote:
 </pre>
       <blockquote type="cite">
         <pre wrap="">Hi Guys,

 I've been playing with the new patch, and found a few problems that I 
 posted in PR 188897:

 <a class="moz-txt-link-freetext" href="http://www.freebsd.org/cgi/query-pr.cgi?pr=188897">http://www.freebsd.org/cgi/query-pr.cgi?pr=188897</a>

 and this one is about another quad port card in the same Atom MoBo:

 <a class="moz-txt-link-freetext" href="http://www.freebsd.org/cgi/query-pr.cgi?pr=188899">http://www.freebsd.org/cgi/query-pr.cgi?pr=188899</a>

 I would be happy to test any new fixes you want me to try.
 </pre>
       </blockquote>
       <pre wrap="">Can you disable agp and see if that fixes things?  (hint.agp.0.disabled=1 at 
 the loader prompt)

 </pre>
     </blockquote>
     <br>
     <div class="moz-cite-prefix">On 05/01/2014 09:27 AM, Mr. Clif wrote:<br>
     </div>
     <blockquote cite="mid:536275F7.1050200 at eugeneweb.com" type="cite">Ok,

       <br>
       <br>
       sorry about the delay, now that I'm set up again the turnaround
       time should be a lot faster. <br>
       <br>
       At the loader prompt I typed: <br>
       <br>
       set hint.agp.0.disabled=1 <br>
       boot <br>
       <br>
       After a lot of testing, the only possible difference I can see is
       that the re0 interface is always? there when the agp is disabled
       and not always there by default. By the way, this board doesn't
       have an AGP port. Oh and I only checked the dc board, since it
       didn't work I didn't go on to the sun board. :-) <br>
       <br>
           Clif <br>
       <br>
     </blockquote>
     <br>
     <div class="moz-cite-prefix">On 05/08/2014 09:10 AM, John Baldwin
       wrote:<br>
     </div>
     <blockquote cite="mid:201405081210.24208.jhb at freebsd.org"
       type="cite">
       <pre wrap="">On Wednesday, May 07, 2014 6:37:59 pm Mr. Clif wrote:
 </pre>
       <blockquote type="cite">
         <pre wrap="">Ok sorry I didn't get anywhere with the AGP experiment. I guess I'll put 
 the machine away until you have other things for me to try.
 </pre>
       </blockquote>
       <pre wrap="">Sorry, I have been focusing on another PCI bug people were running into that 
 was fixed earlier this week.  However, that one involved resources failing to 
 allocate at all, so I'm not sure it is related to your case.  Hmm, I see your
 last issue was related to the special ISA decoding bits.  Can you pick one
 of the cases to focus on for now and capture a verbose dmesg from a HEAD
 kernel?  'devinfo -r' and 'devinfo -u' output from the non-working kernel 
 would also be good.

 </pre>
     </blockquote>
     <div class="moz-cite-prefix">On 05/10/2014 08:18 AM, Mr. Clif wrote:<br>
     </div>
     <blockquote cite="mid:536E4345.30902 at eugeneweb.com" type="cite">
       Opps I almost didn't see this email, too much spam I guess :-(<br>
       <br>
       Sounds like you want me to get the latest from the FreeBSD repo.
       Could you please give me the URL and commands for that so I don't
       get the wrong code?<br>
       <br>
       By last issue do you mean PR <a moz-do-not-send="true"
         href="http://www.freebsd.org/cgi/query-pr.cgi?pr=179033">179033?</a>
       Since that one was closed I opened 188897 but they are both
       basically the same.<br>
       I'm not sure what symtoms the ISA decoding bits cause, to me it's
       just that some of the NICs are unusable, but sure I can run those
       commands, If you give me the git commands to get the correct code.
       I'll get the non-working kernel now too.<br>
       <br>
           Clif<br>
     </blockquote>
   </body>
 </html>

 --------------030302030805050404010504--