Re: libfftw3.so.5: compile error on port of awesome

2012-01-18 Thread Marcelo/Porks
On Wed, Jan 18, 2012 at 03:04, Kevin Oberman kob6...@gmail.com wrote:
 On Tue, Jan 17, 2012 at 5:09 PM, Marcelo/Porks marceloro...@gmail.com
 wrote:

 Hi guys, I do not know if this is the correct mail list to report this.

 I'm trying to compile the port x11-wm/awesome but failed with the error:

 [ 37%] Building C object CMakeFiles/awesome.dir/common/tokenize.c.o
 Linking C executable awesome
 [ 37%] Built target awesome
 Scanning dependencies of target generated_icons
 [ 38%] Generating themes/zenburn/titlebar/maximized_normal_active.png
 Shared object libfftw3.so.5 not found, required by convert*** Error
 code 1

 Stop in /usr/ports/x11-wm/awesome/work/awesome-3.4.11.
 *** Error code 1

 I'm using the head and the workaround of UNAME_r=9.9-CURRENT

 BARAD-DUR# uname -a
 FreeBSD BARAD-DUR 9.9-CURRENT FreeBSD 10.0-CURRENT #6 r230290M: Tue Jan 17
 22:22:46 BRST 2012 root@BARAD-DUR:/usr/clang/obj/usr/src/sys/GENERIC
  amd64
 BARAD-DUR# echo $UNAME_r
 u9.9-CURRENT

 (GMT-2)

 I have on my system /usr/local/lib/libfftw3.so.6
 I can compile making:
 ln -s /usr/local/lib/libfftw3.so /usr/local/lib/libfftw3.so.5

 (I know, this is a bad thing to do)

 Could someone check if on your system the same happen?


 Yes, it's risky to do that.

 The problem is that some port on your system needs to re-link against
 /usr/local/lib/libfftw3.so.6.

 You can find the ports that link to non-existent libs by installing
 sysutils/bsdadminscripts and running pkg_libchk. It will list all
 executables that are linked against non-existent libs. Note that it does
 generate a few false positives. See the man page for details, but none of
 the false positives is likely to show up for libfftw3.

 Re-install any port with files linked against libfftw3.so.5. While you are
 at it, fix any other errors found, though you may skip openoffice and Java
 (false positives).

I didn't know about the sysutils/bsdadminscripts:pkg_libchk. It was
really helpful.

The problem was an old version of ImageMagick installed on my system.

Once the ImageMagick's port also failed to compile. I tried to install
the last version of the package at ftp.freebsd.org and so the issue
about libfftw3.so.5 was gone.

Thanks

 --
 R. Kevin Oberman, Network Engineer
 E-mail: kob6...@gmail.com





-- 
Marcelo Rossi
This e-mail is provided AS IS with no warranties, and confers no rights.
I have nothing against God, I just hate His fan club
___
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: [RFT] Major snd_hda rewrite

2012-01-18 Thread Alexander Motin

On 01/12/12 15:04, Yuri Pankov wrote:

On Thu, Jan 12, 2012 at 02:57:52PM +0200, Alexander Motin wrote:

On 01/12/12 14:18, Yuri Pankov wrote:

On Wed, Jan 11, 2012 at 09:33:17PM +0200, Alexander Motin wrote:

I would like request for testing of my work on further HDA sound driver
improvement.

[...]

Patch can be found here:
http://people.freebsd.org/~mav/hda.rewrite.patch

Patch was generated for 10-CURRENT, but should apply to fresh 9-STABLE
and 8-STABLE branches also.


Patch applied cleanly to r230008 using `svn patch`.

hdacc0:NVidia GT220 HDA CODEC   at cad 0 on hdac0
hdaa0:NVidia GT220 HDA CODEC Audio Function Group   at nid 1 on hdacc0
pcm0:NVidia GT220 HDA CODEC PCM (DisplayPort 8ch)   at nid 5 on hdaa0
hdacc1:NVidia GT220 HDA CODEC   at cad 1 on hdac0
hdaa1:NVidia GT220 HDA CODEC Audio Function Group   at nid 1 on hdacc1
pcm1:NVidia GT220 HDA CODEC PCM (DisplayPort 8ch)   at nid 5 on hdaa1
hdacc2:NVidia GT220 HDA CODEC   at cad 2 on hdac0
hdaa2:NVidia GT220 HDA CODEC Audio Function Group   at nid 1 on hdacc2
pcm2:NVidia GT220 HDA CODEC PCM (DisplayPort 8ch)   at nid 5 on hdaa2
hdacc3:NVidia GT220 HDA CODEC   at cad 3 on hdac0
hdaa3:NVidia GT220 HDA CODEC Audio Function Group   at nid 1 on hdacc3
pcm3:NVidia GT220 HDA CODEC PCM (DisplayPort 8ch)   at nid 5 on hdaa3
hdacc4:IDT 92HD75BX HDA CODEC   at cad 0 on hdac1
hdaa4:IDT 92HD75BX HDA CODEC Audio Function Group   at nid 1 on hdacc4
pcm4:IDT 92HD75BX HDA CODEC PCM (Analog)   at nid 13 and 11 on hdaa4
pcm5:IDT 92HD75BX HDA CODEC PCM (Analog)   at nid 15 and 24 on hdaa4
pcm6:IDT 92HD75BX HDA CODEC PCM (Front Digital)   at nid 30 on hdaa4

pcm4 (builtin speakers) and pcm5 (headphones) seem to work fine, however


Thank you.


I'm not getting anything out of pcm0-pcm3 (connected to a TV via HDMI),
mplayer just pauses at the beggining, trying to cat anything to
/dev/dsp{0-3}.0 gives:

pcm0: chn_write(): pcm0:virtual:dsp0.vp0: play interrupt timeout, channel dead

It was the same with the old driver and I'm not sure if it's (most
likely) my misconfiguration or a driver problem.


It sounds more like a driver problem. HDMI audio is still not very well
discovered area, and, according to ALSA reading, NVidia HDMI is also not
very standard. Probably I'll finally have to buy something to
experiment. What card do you have?


It's a laptop with nVidia Corporation GT216 [GeForce GT 230M] (as
identified by x11/nvidia-driver).


I've reproduced it on NVidia GT210. It seems there is some problem with 
MSI generation. Switching to legacy PCI interrupts fixes problem for me. 
Linux HDA driver disables MSI for all NVidia controllers.


Try to add hint.hdac.0.msi=0 into the /boot/loader.conf.

--
Alexander Motin
___
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: [RFT] Major snd_hda rewrite

2012-01-18 Thread Alexander Motin

On 01/16/12 13:26, Mickaël Maillot wrote:

it could be realy nice to have nvidia hdmi support first 2 channels and
next 8 channels.
i have an ION2 platform and i'm open to test everything.


I've just committed (http://svn.freebsd.org/changeset/base/230312) to 
head patch (http://people.freebsd.org/~mav/hda.hdmi.patch), 
significantly improving HDMI/DisplayPort audio support. Testers, go! :)


--
Alexander Motin
___
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


CARP on -CURRENT

2012-01-18 Thread Andrew Hobbs
Is CARP implemented on -CURRENT (FreeBSD 10)?

I'm playing around with some test boxes in the office running -CURRENT;
testbox# uname -a
FreeBSD testbox.ai.net 10.0-CURRENT FreeBSD 10.0-CURRENT #0: Wed Jan 18 
19:21:12 EST 2012 r...@testbox.ai.net:/usr/obj/usr/src/sys/CARP  amd64

I can't seem to create a carp interface despite having compiled a kernel with 
device  carp in it. Attempts to create a carp interface fail;
# ifconfig carp create
ifconfig: SIOCIFCREATE2: Invalid argument

From what I've read in the handbook entry on CARP 
(http://www.freebsd.org/doc/handbook/carp.html), I should be able to either 
compile in the carp device, as above, or load the if_carp.ko kern module. 
There doesn't appear to be a if_carp.ko module in the -CURRENT source tree, 
however. Only the carp module itself;
# ls -ald /usr/src/sys/modules/*carp*
drwxr-xr-x  2 root  wheel  512 Dec 27 15:12 /usr/src/sys/modules/carp

Am I missing something completely obvious? Was the functionality of if_carp.ko 
rolled into another module?

-Andrew

___
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: CARP on -CURRENT

2012-01-18 Thread Freddie Cash
On Wed, Jan 18, 2012 at 12:54 PM, Andrew Hobbs andrew.ho...@ai.net wrote:
 Is CARP implemented on -CURRENT (FreeBSD 10)?

Search through the mailing list archives for -current, and possibly
-stable.  There's a major reworking of CARP underway in -CURRENT.
It's no longer a separate interface, but options assigned to an
interface.  There's a couple really long messages that cover it in the
archives.

-- 
Freddie Cash
fjwc...@gmail.com
___
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: CARP on -CURRENT

2012-01-18 Thread Sergey Kandaurov
On 19 January 2012 00:54, Andrew Hobbs andrew.ho...@ai.net wrote:
 Is CARP implemented on -CURRENT (FreeBSD 10)?

 I'm playing around with some test boxes in the office running -CURRENT;
 testbox# uname -a
 FreeBSD testbox.ai.net 10.0-CURRENT FreeBSD 10.0-CURRENT #0: Wed Jan 18 
 19:21:12 EST 2012     r...@testbox.ai.net:/usr/obj/usr/src/sys/CARP  amd64

 I can't seem to create a carp interface despite having compiled a kernel with 
 device      carp in it. Attempts to create a carp interface fail;
 # ifconfig carp create
 ifconfig: SIOCIFCREATE2: Invalid argument

 From what I've read in the handbook entry on CARP 
 (http://www.freebsd.org/doc/handbook/carp.html), I should be able to either 
 compile in the carp device, as above, or load the if_carp.ko kern module. 
 There doesn't appear to be a if_carp.ko module in the -CURRENT source tree, 
 however. Only the carp module itself;
 # ls -ald /usr/src/sys/modules/*carp*
 drwxr-xr-x  2 root  wheel  512 Dec 27 15:12 /usr/src/sys/modules/carp

 Am I missing something completely obvious? Was the functionality of 
 if_carp.ko rolled into another module?

You should definitely read this changeset:
http://svn.freebsd.org/changeset/base/228571

and the updated carp ifconfig syntax in man carp. As for if_carp.ko,
it was renamed into carp.ko as part of the CARP implementation overhaul.

This only affects CURRENT.

-- 
wbr,
pluknet
___
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: [RFT] Major snd_hda rewrite

2012-01-18 Thread Mickaël Maillot
2012/1/18 Alexander Motin m...@freebsd.org

 On 01/16/12 13:26, Mickaël Maillot wrote:

 it could be realy nice to have nvidia hdmi support first 2 channels and
 next 8 channels.
 i have an ION2 platform and i'm open to test everything.


 I've just committed 
 (http://svn.freebsd.org/**changeset/base/230312http://svn.freebsd.org/changeset/base/230312)
 to head patch 
 (http://people.freebsd.org/~**mav/hda.hdmi.patchhttp://people.freebsd.org/~mav/hda.hdmi.patch),
 significantly improving HDMI/DisplayPort audio support. Testers, go! :)


Thank a lot !

kernel patched, reboot, and still no sound over hdmi, so i add in my
loader.conf:
hint.hdac.1.msi=0
reboot, and now it works ! so your patch does not disable msi by default
for my chip.
i tried AC3, DTS, DTS ES 6.1, and all works fine like on optical output.
tomorow i'll try 8 channels with DTS HDMA, Dolby TrueHD and LPCM 7.1 (i
need to recompile xbmc with some changes)

you can find verbose dmesg here:
http://fneufn.eu/freebsd/dmesg.verb.htpc.20120118.txt
___
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: [panic] intr_event_execute_handlers() - Corrupted DWARF expression

2012-01-18 Thread Glen Barber
On Wed, Jan 18, 2012 at 05:01:37PM -0500, Glen Barber wrote:
 I have kgdb output attached, and I'll be happy to provide whatever
 additional information that may be needed.
 

This time with the attachment...

Glen

Script started on Wed Jan 18 16:42:35 2012

nucleus# kgdb kernel.debug /var/crash/vmcore.4
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB.  Type show warranty for details.
This GDB was configured as amd64-marcel-freebsd...

Unread portion of the kernel message buffer:
ACPI Warning: Large Reference Count (0x806) in object 0xfe000449fc80 
(20120111/utdelete-491)
ACPI Warning: Large Reference Count (0x807) in object 0xfe000449fc80 
(20120111/utdelete-491)
kernel trap 12 with interrupts disabled


Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 04
fault virtual address   = 0x18
fault code  = supervisor read data, page not present
instruction pointer = 0x20:0x805c2098
stack pointer   = 0x28:0xff8000269a50
frame pointer   = 0x28:0xff8000269aa0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= resume, IOPL = 0
current process = 12 (swi4: clock)
trap number = 12
panic: page fault
cpuid = 2
KDB: stack backtrace:
#0 0x806009ce at kdb_backtrace+0x5e
#1 0x805d06a8 at panic+0x1d8
#2 0x8081a000 at trap_fatal+0x290
#3 0x8081a63d at trap+0x29d
#4 0x808063bf at calltrap+0x8
#5 0x80609bdd at sleepq_timeout+0x1d
#6 0x805e238f at softclock+0x29f
#7 0x805ab904 at intr_event_execute_handlers+0x64
#8 0x805ac567 at ithread_loop+0x97
#9 0x805a975d at fork_exit+0x11d
#10 0x808068ee at fork_trampoline+0xe
Uptime: 2h42m5s
Dumping 2511 out of 7846 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%

kgdb: kvm_read: invalid address (0x64)
Reading symbols from /boot/kernel/vesa.ko...Reading symbols from 
/boot/kernel/vesa.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/vesa.ko
Reading symbols from /boot/kernel/zfs.ko...Reading symbols from 
/boot/kernel/zfs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/zfs.ko
Reading symbols from /boot/kernel/opensolaris.ko...Reading symbols from 
/boot/kernel/opensolaris.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/opensolaris.ko
Reading symbols from /boot/kernel/linux.ko...Reading symbols from 
/boot/kernel/linux.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/linux.ko
Reading symbols from /boot/kernel/coretemp.ko...Reading symbols from 
/boot/kernel/coretemp.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/coretemp.ko
Reading symbols from /boot/kernel/sem.ko...Reading symbols from 
/boot/kernel/sem.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/sem.ko
Reading symbols from /boot/kernel/i915.ko...Reading symbols from 
/boot/kernel/i915.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/i915.ko
Reading symbols from /boot/kernel/iicbb.ko...Reading symbols from 
/boot/kernel/iicbb.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/iicbb.ko
Reading symbols from /boot/kernel/iicbus.ko...Reading symbols from 
/boot/kernel/iicbus.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/iicbus.ko
Reading symbols from /boot/kernel/iic.ko...Reading symbols from 
/boot/kernel/iic.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/iic.ko
Reading symbols from /boot/kernel/drm.ko...Reading symbols from 
/boot/kernel/drm.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/drm.ko
Reading symbols from /boot/kernel/geom_eli.ko...Reading symbols from 
/boot/kernel/geom_eli.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/geom_eli.ko
Reading symbols from /boot/kernel/crypto.ko...Reading symbols from 
/boot/kernel/crypto.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/crypto.ko
Reading symbols from /boot/kernel/zlib.ko...Reading symbols from 
/boot/kernel/zlib.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/zlib.ko
#0  doadump (textdump=Variable textdump is not available.
) at pcpu.h:224
224 __asm(movq %%gs:0,%0 : =r (td));
(kgdb) list *0x805c2098
0x805c2098 is in thread_lock_flags_ 
(/usr/src/sys/kern/kern_mutex.c:589).
584 KASSERT(m-mtx_lock != MTX_DESTROYED,
585 (thread_lock() of destroyed mutex @ %s:%d, file, 
line));
586 KASSERT(LOCK_CLASS(m-lock_object) == 
lock_class_mtx_spin,
587 (thread_lock() of sleep mutex %s @ %s:%d,
588 m-lock_object.lo_name, file, line));
589 if (mtx_owned(m))
590   

[panic] intr_event_execute_handlers() - Corrupted DWARF expression

2012-01-18 Thread Glen Barber
Hi,

I'm running -CURRENT from about 5 days ago:

nucleus# uname -a
FreeBSD nucleus 10.0-CURRENT FreeBSD 10.0-CURRENT #3 r230037M: Fri Jan
13 17:48:14 EST 2012 gjb@nucleus:/usr/obj/usr/src/sys/NUCLEUS  amd64

(The 'M' is kib's DRM patches for Intel GPU.)

So far, I haven't had much problem with this laptop, but just had the
machine panic.

I have kgdb output attached, and I'll be happy to provide whatever
additional information that may be needed.

I have core.txt.N available here:

  http://people.freebsd.org/~gjb/core.txt

Regards,

Glen

___
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


Intermittent re0 phy failure

2012-01-18 Thread Michael Butler
At random intervals, when re0 is without any significant load; idle for
lengthy periods, I see ..

kernel: re0: PHY read failed
last message repeated 4 times
kernel: re0: link state changed to DOWN

Unplugging the cable and re-inserting is sufficient to restore
functionality.

kernel is @ SVN r230276

Any ideas how to track this down?

imb
___
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: Intermittent re0 phy failure

2012-01-18 Thread Michael Butler
On 01/18/12 19:54, YongHyeon PYUN wrote:
 On Wed, Jan 18, 2012 at 05:48:47PM -0500, Michael Butler wrote:
 At random intervals, when re0 is without any significant load; idle for
 lengthy periods, I see ..

 kernel: re0: PHY read failed
 last message repeated 4 times
 kernel: re0: link state changed to DOWN

 Unplugging the cable and re-inserting is sufficient to restore
 functionality.

 kernel is @ SVN r230276

 Any ideas how to track this down?
 
 Knowing which kind of controller you have would be more helpful.
 Show me both re(4)/rgephy(4) related message from dmesg and
 'devinfo -rv | grep rgephy' output.
 

As requested:

dmesg:

re0: RealTek 8168/8111 B/C/CP/D/DP/E/F PCIe Gigabit Ethernet port
0x2000-0x20ff mem 0xf070-0xf0700fff,0xf020-0xf0203fff irq 17 at
device 0.0 on pci3
re0: MSI count : 1
re0: MSI-X count : 4
re0: attempting to allocate 1 MSI-X vectors (4 supported)
msi: routing MSI-X IRQ 257 to local APIC 0 vector 51
re0: using IRQ 257 for MSI-X
re0: Using 1 MSI-X message
re0: ASPM disabled
re0: Chip rev. 0x2800
re0: MAC rev. 0x
miibus0: MII bus on re0
rgephy0: RTL8169S/8110S/8211 1000BASE-T media interface PHY 1 on miibus0
rgephy0: OUI 0x00e04c, model 0x0011, rev. 2
rgephy0:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX,
100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master,
1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow,
1000baseT-FDX-flow-master, auto, auto-flow

devinfo -rv | grep rgephy
rgephy0 pnpinfo oui=0xe04c model=0x11 rev=0x2 at phyno=1

imb
___
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: Intermittent re0 phy failure

2012-01-18 Thread YongHyeon PYUN
On Wed, Jan 18, 2012 at 05:48:47PM -0500, Michael Butler wrote:
 At random intervals, when re0 is without any significant load; idle for
 lengthy periods, I see ..
 
 kernel: re0: PHY read failed
 last message repeated 4 times
 kernel: re0: link state changed to DOWN
 
 Unplugging the cable and re-inserting is sufficient to restore
 functionality.
 
 kernel is @ SVN r230276
 
 Any ideas how to track this down?

Knowing which kind of controller you have would be more helpful.
Show me both re(4)/rgephy(4) related message from dmesg and
'devinfo -rv | grep rgephy' output.

___
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: Intermittent re0 phy failure

2012-01-18 Thread YongHyeon PYUN
On Wed, Jan 18, 2012 at 08:01:42PM -0500, Michael Butler wrote:
 On 01/18/12 19:54, YongHyeon PYUN wrote:
  On Wed, Jan 18, 2012 at 05:48:47PM -0500, Michael Butler wrote:
  At random intervals, when re0 is without any significant load; idle for
  lengthy periods, I see ..
 
  kernel: re0: PHY read failed
  last message repeated 4 times
  kernel: re0: link state changed to DOWN
 
  Unplugging the cable and re-inserting is sufficient to restore
  functionality.
 
  kernel is @ SVN r230276
 
  Any ideas how to track this down?
  
  Knowing which kind of controller you have would be more helpful.
  Show me both re(4)/rgephy(4) related message from dmesg and
  'devinfo -rv | grep rgephy' output.
  
 
 As requested:
 
 dmesg:
 
 re0: RealTek 8168/8111 B/C/CP/D/DP/E/F PCIe Gigabit Ethernet port
 0x2000-0x20ff mem 0xf070-0xf0700fff,0xf020-0xf0203fff irq 17 at
 device 0.0 on pci3
 re0: MSI count : 1
 re0: MSI-X count : 4
 re0: attempting to allocate 1 MSI-X vectors (4 supported)
 msi: routing MSI-X IRQ 257 to local APIC 0 vector 51
 re0: using IRQ 257 for MSI-X
 re0: Using 1 MSI-X message
 re0: ASPM disabled
 re0: Chip rev. 0x2800
 re0: MAC rev. 0x
 miibus0: MII bus on re0
 rgephy0: RTL8169S/8110S/8211 1000BASE-T media interface PHY 1 on miibus0
 rgephy0: OUI 0x00e04c, model 0x0011, rev. 2
 rgephy0:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX,
 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master,
 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow,
 1000baseT-FDX-flow-master, auto, auto-flow
 
 devinfo -rv | grep rgephy
 rgephy0 pnpinfo oui=0xe04c model=0x11 rev=0x2 at phyno=1
 

Thanks a lot.
Would you try attached patch?
Index: sys/dev/re/if_re.c
===
--- sys/dev/re/if_re.c	(revision 230315)
+++ sys/dev/re/if_re.c	(working copy)
@@ -1433,11 +1433,16 @@
 			sc-rl_flags |= RL_FLAG_MACSLEEP;
 		/* FALLTHROUGH */
 	case RL_HWREV_8168CP:
-	case RL_HWREV_8168D:
 		sc-rl_flags |= RL_FLAG_PHYWAKE | RL_FLAG_PAR |
 		RL_FLAG_DESCV2 | RL_FLAG_MACSTAT | RL_FLAG_CMDSTOP |
 		RL_FLAG_AUTOPAD | RL_FLAG_JUMBOV2 | RL_FLAG_WOL_MANLINK;
 		break;
+	case RL_HWREV_8168D:
+		sc-rl_flags |= RL_FLAG_PHYWAKE | RL_FLAG_PHYWAKE_PM |
+		RL_FLAG_PAR | RL_FLAG_DESCV2 | RL_FLAG_MACSTAT |
+		RL_FLAG_CMDSTOP | RL_FLAG_AUTOPAD | RL_FLAG_JUMBOV2 |
+		RL_FLAG_WOL_MANLINK;
+		break;
 	case RL_HWREV_8168DP:
 		sc-rl_flags |= RL_FLAG_PHYWAKE | RL_FLAG_PAR |
 		RL_FLAG_DESCV2 | RL_FLAG_MACSTAT | RL_FLAG_AUTOPAD |
___
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: [RFT] Major snd_hda rewrite

2012-01-18 Thread Alexander Motin

On 01/19/12 00:04, Mickaël Maillot wrote:

2012/1/18 Alexander Motin m...@freebsd.org mailto:m...@freebsd.org

On 01/16/12 13:26, Mickaël Maillot wrote:

it could be realy nice to have nvidia hdmi support first 2
channels and
next 8 channels.
i have an ION2 platform and i'm open to test everything.


I've just committed (http://svn.freebsd.org/__changeset/base/230312
http://svn.freebsd.org/changeset/base/230312) to head patch
(http://people.freebsd.org/~__mav/hda.hdmi.patch
http://people.freebsd.org/~mav/hda.hdmi.patch), significantly
improving HDMI/DisplayPort audio support. Testers, go! :)


Thank a lot !

kernel patched, reboot, and still no sound over hdmi, so i add in my
loader.conf:
hint.hdac.1.msi=0
reboot, and now it works ! so your patch does not disable msi by default
for my chip.
i tried AC3, DTS, DTS ES 6.1, and all works fine like on optical output.
tomorow i'll try 8 channels with DTS HDMA, Dolby TrueHD and LPCM 7.1 (i
need to recompile xbmc with some changes)

you can find verbose dmesg here:
http://fneufn.eu/freebsd/dmesg.verb.htpc.20120118.txt


I don't see there neither controller PCI ID, nor ELD content. Could you 
show also `pciconf -lv` and verbose `dmesg` after Xorg start (if this 
was before)?


--
Alexander Motin
___
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: Intermittent re0 phy failure

2012-01-18 Thread Michael Butler
On 01/18/12 20:52, YongHyeon PYUN wrote:
 
 Thanks a lot.
 Would you try attached patch?

Compiled, installed and running - I'll see if I can reproduce the failure.

Thanks very much for your quick response :-)

imb
___
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: [RFT] Major snd_hda rewrite

2012-01-18 Thread Mickaël Maillot
2012/1/19 Alexander Motin m...@freebsd.org

 On 01/19/12 00:04, Mickaël Maillot wrote:

 2012/1/18 Alexander Motin m...@freebsd.org mailto:m...@freebsd.org


On 01/16/12 13:26, Mickaël Maillot wrote:

it could be realy nice to have nvidia hdmi support first 2
channels and
next 8 channels.
i have an ION2 platform and i'm open to test everything.


I've just committed 
 (http://svn.freebsd.org/__**changeset/base/230312http://svn.freebsd.org/__changeset/base/230312

 http://svn.freebsd.org/**changeset/base/230312http://svn.freebsd.org/changeset/base/230312)
 to head patch

 (http://people.freebsd.org/~__**mav/hda.hdmi.patchhttp://people.freebsd.org/~__mav/hda.hdmi.patch

 http://people.freebsd.org/~**mav/hda.hdmi.patchhttp://people.freebsd.org/~mav/hda.hdmi.patch),
 significantly

improving HDMI/DisplayPort audio support. Testers, go! :)


 Thank a lot !

 kernel patched, reboot, and still no sound over hdmi, so i add in my
 loader.conf:
 hint.hdac.1.msi=0
 reboot, and now it works ! so your patch does not disable msi by default
 for my chip.
 i tried AC3, DTS, DTS ES 6.1, and all works fine like on optical output.
 tomorow i'll try 8 channels with DTS HDMA, Dolby TrueHD and LPCM 7.1 (i
 need to recompile xbmc with some changes)

 you can find verbose dmesg here:
 http://fneufn.eu/freebsd/**dmesg.verb.htpc.20120118.txthttp://fneufn.eu/freebsd/dmesg.verb.htpc.20120118.txt


 I don't see there neither controller PCI ID, nor ELD content. Could you
 show also `pciconf -lv` and verbose `dmesg` after Xorg start (if this was
 before)?


sorry, i was booting on the wrong kernel .
here is the good verbose dmesg with ELD: http://fneufn.eu/freebsd/**
dmesg.verb.htpc.20120119.txthttp://fneufn.eu/freebsd/dmesg.verb.htpc.20120118.txt

pciconf -vl with nvidia part:

vgapci0@pci0:3:0:0: class=0x03 card=0x841f1043 chip=0x0a6410de
rev=0xa2 hdr=0x00
vendor = 'nVidia Corporation'
device = 'GT218 [ION]'
class  = display
subclass   = VGA
hdac1@pci0:3:0:1:   class=0x040300 card=0x841f1043 chip=0x0be310de
rev=0xa1 hdr=0x00
vendor = 'nVidia Corporation'
device = 'High Definition Audio Controller'
class  = multimedia
subclass   = HDA
___
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


Google Code-In 2011 is over; 56 tasks got completed for FreeBSD!

2012-01-18 Thread Wojciech A. Koszek

Hello,

(This is cross-posted message between current@, stable@ and hackers@; for
eventual discussion, please use hackers@ mailing list.)

I am glad to announce that we've successfully reached the end of Google
Code-In 2011 Contest!

FreeBSD participated first time, and in my personal opinion GCIN has proven
to be a big success. I want to thank all the participants for their time,
cooperation and dedication.

Here's the list of this years participants:

Alex Rucker, Andrey Sinitsyn, Anikan, Astha Sethi, Bebacz, 
Bharath Mohan, doctorkohaku, Eric Newberry, GarrettF,
Isabell Long (issyl0), mpaloski, Violet Lin (n00l3), Nagato Yuki,
Nathan, passstab, Reid Anderson, Robin, Roger, Rushil Paul,
Thomas Turney, Utkarsh Pant, Zacharias Mitzelos 

I would like to point out Isabell Long (issyl0) completed 13 tasks for us
and holds this years record.

Some other numbers...

We've had 19 mentors. I send special thanks to those who offered their help
in mentoring/administration, since accepting/reviewing/judging tasks has
proven to be challenging.

We've had 78 tasks published. 56 tasks got completed, leading to ~72%
successful completions.

1 task was claimed at the time of hitting the deadline, 10 tasks were
claimed, but never  finished, thus got reopened. 12 of tasks were never
claimed. List of tasks, together with their outcome (uploaded results)
are present here:

http://www.google-melange.com/gci/org/google/gci2011/freebsd

It would be my wish to have the work done in GCIN commited to FreeBSD with:

Submitted by:   Name email (Google Code-In 2011)

header or similar, clearly stating work comes from GCIN 2011.

The hardest expectations for mentors was short response time. For students
I think it was meeting FreeBSD's standards, however I'm positively surprised
by the quality of submitted work.

The complaint which I've heard is: Not enough coding tasks. We should fix
it next time, since most of the tasks were related with documentation and
outreach/promotion.

I think GCIN should become an integral part of the FreeBSD involvement in
promotion of the Open Source software.

Thank you.

-- 
Wojciech A. Koszek
wkos...@freebsd.czest.pl
http://FreeBSD.czest.pl/~wkoszek/
___
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