Re: No disks usable on a P5NE MB (aka regession is r219737)

2012-03-28 Thread John Baldwin
On Tuesday, November 15, 2011 6:12:53 pm Baptiste Daroussin wrote:
 On Tue, Nov 15, 2011 at 12:46:41PM -0500, John Baldwin wrote:
 [...]
  and
   10 remove that block :
   http://people.freebsd.org/~bapt/workaround-to-boot-p5ne.diff
  
  Yeah, the problem is that NVIDIA chipsets seem to have really odd behavior 
  in 
  that once you turn MSI mapping on for a given node in the HyperTransport 
  tree 
  it expects all child devices to only use MSI and not INTx.  Linux has a lot 
  of 
  quirk code to try to handle this by only turning on the mapping window when 
  MSI is enabled for a given device.  However, it has lots of hacks to try to 
  find the right Host-PCI Bridge that a given device is a child of.  I'm 
  mostly 
  tempted to just disable MSI on NVIDIA chipsets that have these issues 
  rather 
  than adding the same number of quirks.  However I haven't really had time 
  to 
  sit down and look at this.
  
 
 Thanks for reply, if you can do some testing for you if you want.

Please try http://www.FreeBSD.org/~jhb/patches/hostb_htmsi.patch

-- 
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: No disks usable on a P5NE MB (aka regession is r219737)

2012-03-28 Thread Baptiste Daroussin
On Wed, Mar 28, 2012 at 02:38:42PM -0400, John Baldwin wrote:
 On Tuesday, November 15, 2011 6:12:53 pm Baptiste Daroussin wrote:
  On Tue, Nov 15, 2011 at 12:46:41PM -0500, John Baldwin wrote:
  [...]
   and
10 remove that block :
http://people.freebsd.org/~bapt/workaround-to-boot-p5ne.diff
   
   Yeah, the problem is that NVIDIA chipsets seem to have really odd 
   behavior in 
   that once you turn MSI mapping on for a given node in the HyperTransport 
   tree 
   it expects all child devices to only use MSI and not INTx.  Linux has a 
   lot of 
   quirk code to try to handle this by only turning on the mapping window 
   when 
   MSI is enabled for a given device.  However, it has lots of hacks to try 
   to 
   find the right Host-PCI Bridge that a given device is a child of.  I'm 
   mostly 
   tempted to just disable MSI on NVIDIA chipsets that have these issues 
   rather 
   than adding the same number of quirks.  However I haven't really had time 
   to 
   sit down and look at this.
   
  
  Thanks for reply, if you can do some testing for you if you want.
 
 Please try http://www.FreeBSD.org/~jhb/patches/hostb_htmsi.patch
 
works perfectly thanks

regards,
Bapt


pgp4ls8rzuDuw.pgp
Description: PGP signature


Re: No disks usable on a P5NE MB (aka regession is r219737)

2012-03-28 Thread John Baldwin
On Wednesday, March 28, 2012 3:24:13 pm Baptiste Daroussin wrote:
 On Wed, Mar 28, 2012 at 02:38:42PM -0400, John Baldwin wrote:
  On Tuesday, November 15, 2011 6:12:53 pm Baptiste Daroussin wrote:
   On Tue, Nov 15, 2011 at 12:46:41PM -0500, John Baldwin wrote:
   [...]
and
 10 remove that block :
 http://people.freebsd.org/~bapt/workaround-to-boot-p5ne.diff

Yeah, the problem is that NVIDIA chipsets seem to have really odd 
behavior in 
that once you turn MSI mapping on for a given node in the 
HyperTransport tree 
it expects all child devices to only use MSI and not INTx.  Linux has a 
lot of 
quirk code to try to handle this by only turning on the mapping window 
when 
MSI is enabled for a given device.  However, it has lots of hacks to 
try to 
find the right Host-PCI Bridge that a given device is a child of.  I'm 
mostly 
tempted to just disable MSI on NVIDIA chipsets that have these issues 
rather 
than adding the same number of quirks.  However I haven't really had 
time to 
sit down and look at this.

   
   Thanks for reply, if you can do some testing for you if you want.
  
  Please try http://www.FreeBSD.org/~jhb/patches/hostb_htmsi.patch
  
 works perfectly thanks

Really?  Ok, thanks!

Hmm, I've updated it to so that it should work in the non-ACPI case.  Can you
try it with ACPI disabled?  (If this is on amd64 you might need to add
'device mptable' to your kernel config.)

-- 
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: No disks usable on a P5NE MB (aka regession is r219737)

2012-03-28 Thread Baptiste Daroussin
On Wed, Mar 28, 2012 at 04:41:35PM -0400, John Baldwin wrote:
 On Wednesday, March 28, 2012 3:24:13 pm Baptiste Daroussin wrote:
  On Wed, Mar 28, 2012 at 02:38:42PM -0400, John Baldwin wrote:
   On Tuesday, November 15, 2011 6:12:53 pm Baptiste Daroussin wrote:
On Tue, Nov 15, 2011 at 12:46:41PM -0500, John Baldwin wrote:
[...]
 and
  10 remove that block :
  http://people.freebsd.org/~bapt/workaround-to-boot-p5ne.diff
 
 Yeah, the problem is that NVIDIA chipsets seem to have really odd 
 behavior in 
 that once you turn MSI mapping on for a given node in the 
 HyperTransport tree 
 it expects all child devices to only use MSI and not INTx.  Linux has 
 a lot of 
 quirk code to try to handle this by only turning on the mapping 
 window when 
 MSI is enabled for a given device.  However, it has lots of hacks to 
 try to 
 find the right Host-PCI Bridge that a given device is a child of.  
 I'm mostly 
 tempted to just disable MSI on NVIDIA chipsets that have these issues 
 rather 
 than adding the same number of quirks.  However I haven't really had 
 time to 
 sit down and look at this.
 

Thanks for reply, if you can do some testing for you if you want.
   
   Please try http://www.FreeBSD.org/~jhb/patches/hostb_htmsi.patch
   
  works perfectly thanks
 
 Really?  Ok, thanks!

Yes really :)
 
 Hmm, I've updated it to so that it should work in the non-ACPI case.  Can you
 try it with ACPI disabled?  (If this is on amd64 you might need to add
 'device mptable' to your kernel config.)
 

Also tested and works fine thank you very much (yes this is amd64)

regards,
Bapt


pgpWGFCZOk27R.pgp
Description: PGP signature


Re: No disks usable on a P5NE MB (aka regession is r219737)

2011-11-15 Thread John Baldwin
On Friday, November 11, 2011 5:59:07 pm Baptiste Daroussin wrote:
 On Fri, Nov 11, 2011 at 11:10:58PM +0100, Baptiste Daroussin wrote:
  On Thu, Sep 29, 2011 at 12:22:54AM +0200, Baptiste Daroussin wrote:
   On Sun, Sep 11, 2011 at 10:39:38PM +0200, Baptiste Daroussin wrote:
  the result is:
  db show intrcnt
  cpu0: timer4510
  irq256: hdac0   1
  cpu3: timer 29
  cpu1: timer 3036
  cpu2: timer 31
  db
  
  I did break at the mountfrom prompt
  If I break before I only have the cpu0 and irq256 entries.
 
 Hmmm, is there any way you can build a 9 kernel without sound 
support (since 
 that clutters up bootverbose) and capture a verbose dmesg, using a 
serial 
 console or PXE booting to an NFS root of some sort?
 
I can't pxe boot, but I can record the build on my camera:
http://people.freebsd.org/~bapt/9-fail.avi (18MB)

(this is 9.0-BETA2 memstick)

Hope that could help

   
   Apparently this doesn't help, given that I have no way to netboot this 
box, may
   that be from pxe and that there is no serial console, what can I do more 
to help
   fixing this?
   
   I would love to be able to run 9 on my box
   
   regards,
   Bapt
  
  After trying lots of different kernel it appears that the regression was
  introduce in r219737. I'm trying to figure out to solve this.
  
  If you have any clue tell me.
  
  regards,
  Bapt
 
 
 
 With the help of cognet, I workaround this and have been able to boot both 9 
and
 10 remove that block :
 http://people.freebsd.org/~bapt/workaround-to-boot-p5ne.diff

Yeah, the problem is that NVIDIA chipsets seem to have really odd behavior in 
that once you turn MSI mapping on for a given node in the HyperTransport tree 
it expects all child devices to only use MSI and not INTx.  Linux has a lot of 
quirk code to try to handle this by only turning on the mapping window when 
MSI is enabled for a given device.  However, it has lots of hacks to try to 
find the right Host-PCI Bridge that a given device is a child of.  I'm mostly 
tempted to just disable MSI on NVIDIA chipsets that have these issues rather 
than adding the same number of quirks.  However I haven't really had time to 
sit down and look at this.

-- 
John Baldwin
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: No disks usable on a P5NE MB (aka regession is r219737)

2011-11-15 Thread Baptiste Daroussin
On Tue, Nov 15, 2011 at 12:46:41PM -0500, John Baldwin wrote:
[...]
 and
  10 remove that block :
  http://people.freebsd.org/~bapt/workaround-to-boot-p5ne.diff
 
 Yeah, the problem is that NVIDIA chipsets seem to have really odd behavior in 
 that once you turn MSI mapping on for a given node in the HyperTransport tree 
 it expects all child devices to only use MSI and not INTx.  Linux has a lot 
 of 
 quirk code to try to handle this by only turning on the mapping window when 
 MSI is enabled for a given device.  However, it has lots of hacks to try to 
 find the right Host-PCI Bridge that a given device is a child of.  I'm mostly 
 tempted to just disable MSI on NVIDIA chipsets that have these issues rather 
 than adding the same number of quirks.  However I haven't really had time to 
 sit down and look at this.
 

Thanks for reply, if you can do some testing for you if you want.

regards,
Bapt


pgpJ14LcnsP9S.pgp
Description: PGP signature


Re: No disks usable on a P5NE MB (aka regession is r219737)

2011-11-11 Thread Baptiste Daroussin
On Thu, Sep 29, 2011 at 12:22:54AM +0200, Baptiste Daroussin wrote:
 On Sun, Sep 11, 2011 at 10:39:38PM +0200, Baptiste Daroussin wrote:
the result is:
db show intrcnt
cpu0: timer4510
irq256: hdac0   1
cpu3: timer 29
cpu1: timer 3036
cpu2: timer 31
db

I did break at the mountfrom prompt
If I break before I only have the cpu0 and irq256 entries.
   
   Hmmm, is there any way you can build a 9 kernel without sound support 
   (since 
   that clutters up bootverbose) and capture a verbose dmesg, using a serial 
   console or PXE booting to an NFS root of some sort?
   
  I can't pxe boot, but I can record the build on my camera:
  http://people.freebsd.org/~bapt/9-fail.avi (18MB)
  
  (this is 9.0-BETA2 memstick)
  
  Hope that could help
  
 
 Apparently this doesn't help, given that I have no way to netboot this box, 
 may
 that be from pxe and that there is no serial console, what can I do more to 
 help
 fixing this?
 
 I would love to be able to run 9 on my box
 
 regards,
 Bapt

After trying lots of different kernel it appears that the regression was
introduce in r219737. I'm trying to figure out to solve this.

If you have any clue tell me.

regards,
Bapt


pgpirJOgABgTZ.pgp
Description: PGP signature


Re: No disks usable on a P5NE MB (aka regession is r219737)

2011-11-11 Thread Baptiste Daroussin
On Fri, Nov 11, 2011 at 11:10:58PM +0100, Baptiste Daroussin wrote:
 On Thu, Sep 29, 2011 at 12:22:54AM +0200, Baptiste Daroussin wrote:
  On Sun, Sep 11, 2011 at 10:39:38PM +0200, Baptiste Daroussin wrote:
 the result is:
 db show intrcnt
 cpu0: timer4510
 irq256: hdac0   1
 cpu3: timer 29
 cpu1: timer 3036
 cpu2: timer 31
 db
 
 I did break at the mountfrom prompt
 If I break before I only have the cpu0 and irq256 entries.

Hmmm, is there any way you can build a 9 kernel without sound support 
(since 
that clutters up bootverbose) and capture a verbose dmesg, using a 
serial 
console or PXE booting to an NFS root of some sort?

   I can't pxe boot, but I can record the build on my camera:
   http://people.freebsd.org/~bapt/9-fail.avi (18MB)
   
   (this is 9.0-BETA2 memstick)
   
   Hope that could help
   
  
  Apparently this doesn't help, given that I have no way to netboot this box, 
  may
  that be from pxe and that there is no serial console, what can I do more to 
  help
  fixing this?
  
  I would love to be able to run 9 on my box
  
  regards,
  Bapt
 
 After trying lots of different kernel it appears that the regression was
 introduce in r219737. I'm trying to figure out to solve this.
 
 If you have any clue tell me.
 
 regards,
 Bapt



With the help of cognet, I workaround this and have been able to boot both 9 and
10 remove that block :
http://people.freebsd.org/~bapt/workaround-to-boot-p5ne.diff

regards,
Bapt


pgpJfjCrudnpY.pgp
Description: PGP signature