search for: dpb

...g banner message Product: Portable OpenSSH Version: 3.7p1 Platform: Sparc OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: openssh-bugs at mindrot.org ReportedBy: dpb at bl.com I have a long, 1184 bytes, banner file. It is the one that Titan installs. and with the 3.6 version of ssh it prints fine. With the 3.7 version only part of it prints. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assigne...

...-q option Product: Portable OpenSSH Version: -current Platform: All OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: openssh-bugs at mindrot.org ReportedBy: dpb at bl.com If I ssh to another 3.7.1p2 system and it is configured for a banner and the file either doesn't exist or is zero length I get "xmalloc: zero size" The patch also seems to disable the -q option to eliminate the banner. We use it for scripts. Just to make matters a bit...

...Summary: Fix Android build Product: rsync Version: 3.1.0 Platform: All OS/Version: Other Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: dpb at corrigendum.ru QAContact: rsync-qa at samba.org Created attachment 8851 --> https://bugzilla.samba.org/attachment.cgi?id=8851 Old config.{guess,sub} don't recognize the Android toolchains rsync, as it currently is, fails to build for Android because of some minor (and one mo...

...er way for now. But in the future the plan is definitely to move to separate channels. > > Regarding "non-obvious" values for H264 decoding, looking at nouveau_vp3_video_vp.c, it looks like there are several unknown values in the H264 picture parameter structure, especially for the DPB reference table. This seems like a potential cause for your MSDEC[12]-specific hangs; incorrect DPB state can be difficult to figure out from picture parameter dumps, and the PDEC response to incorrect DPB state is generally to simply hang. There are no significant differences between MSDEC[12] (...

On Thu, Nov 21, 2013 at 5:22 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > On Thu, Nov 21, 2013 at 5:07 PM, Benjamin Morris <bmorris at nvidia.com> wrote: >> On 11/19/2013 08:16 PM, Ilia Mirkin wrote: >>> Hello, >>> >>> I hope this is an appropriate style of request for this forum. I added >>> code to support video decoding on the tesla

...e channel usage that you need to have for MSDEC4 should also be used for everything down to G84. Regarding "non-obvious" values for H264 decoding, looking at nouveau_vp3_video_vp.c, it looks like there are several unknown values in the H264 picture parameter structure, especially for the DPB reference table. This seems like a potential cause for your MSDEC[12]-specific hangs; incorrect DPB state can be difficult to figure out from picture parameter dumps, and the PDEC response to incorrect DPB state is generally to simply hang. There are no significant differences between MSDEC[12] (...

...T" , "ENI.MI" , "VOW.BE" , "CS.PA" , "DAI.DE" , "ALV.DE" , "EOAN.DE" , "CA.PA" , "G.MI" , "DE" , "EXR.MI" , "MUV2.BE" , "UG.PA" , "PRU.L", "VOD.L" , "DPB.BE" , "REP.MC" , "RWE.BE" , "AGN.AS" , "FTE.PA" , "EAD" , "LGEN.L" , "CNP.PA" , "ULVR.L" , "TKA.BE" , "RIO.L" , "NOK" , "SGO.PA" , "RNO.PA" , "VIE.PA" , &...

....h: in the future, the compiler will take precedence configure: WARNING: ## ------------------------------------------- ## configure: WARNING: ## Report this to openssh-unix- dev at mindrot.org ## configure: WARNING: ## ------------------------------------------- ## Darryl Baker dpb at bl.com

Hi guys and gals, I'm working on improving nouveau's support for MXM (Mobile PCI Express Module) chips and need some more data to check my implementation. To see if you can help, the first thing to do is jump over to /sys/firmware/acpi/tables and run "grep MXMS *". [root at nisroch tables]# grep MXMS * Binary file DSDT matches [root at nisroch tables]# If this isn't

https://bugs.freedesktop.org/show_bug.cgi?id=101404 Bug ID: 101404 Summary: GTX 970M (GM204-A) not powered off when not in use (DynPwr in stead of DynOff) Product: xorg Version: unspecified Hardware: Other OS: Linux (All) Status: NEW Severity: normal Priority: medium

Hello, I am encountering a 30 second hang during boot, in the Xorg process just before the display manager comes up. I have bisected the problem to the following commit: commit 2b700825e7a7702fb862edba1262c98040dc1bf6 Author: Ben Skeggs <bskeggs at redhat.com> Date: Thu Aug 20 14:54:22 2015 +1000 drm/nouveau/mc: move device irq handling to platform-specific code The hang only

....959923] snd_hda_codec_realtek hdaudioC0D0: inputs: [ 2.959926] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [ 2.959928] snd_hda_codec_realtek hdaudioC0D0: Dock Mic=0x19 [ 2.959930] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 2.983182] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5 [ 2.995536] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9 [ 2.996475] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10 [ 2.996548] input: HDA Intel PCH Dock Mic as /devices/p...

Hello, following up on myself, it was suggested on IRC that I better attach a dmesg output. Here's the output of a clean boot & echo 0f > /sys/.../pstate cycle. I can't spot a message that relates to the reclock action, and there's only one weird "nouveau 0000:04:00.0: clk: base: 7 MHz, boost: 7 MHz" message. On the other hand: # cat

...DhABSNT=Mz=$kZIB;CD8HQJ_9R1E@N*af3P z2?ea{;`+jOkVrl@(&eVZ4V@6%dpcln_4Z6!%Xo5y?^w7kA@<wexax|w%EK9i(7$RI z)~3p;%Bz4a%?d08tg6Y#A6ONyx77kFo4p@|!6<wCO;&apCV*SXDoQI9{B`(VpWfTo zq4pX)gkKD<o|BzA6%I3LE6KCCU8}*;K8Qp3rTjWnG|>#UK)d`|Z#o`LB$SJOpqx+4 zk$kxsXuc`D!u@9zBu}(}Y?I_jstCZi)1b)CPdd`{7@dpb*3Z|M_BE~fCn0@*(z=^O zsL-6l${5)tA|6I;BA#l8-V&j$F;0(8uhd)o<QHVudD?rJ4yRw#mG>h>&FR42`)tZ7 z*~JQi!*r&S$53s`;l4WhT>%)?x!BkZ%$w=5v{V6o*_l`Wf-lga>0a^>WOv2BC;6@B z6m3EpgITS;rcF^W*}tCmUV;>X=HXppZ=asOP=W=Q(^#aX!C$U9Q)XqzeJ*tvLxOpM zJoVMdti5)>5(jE{VZ!AWu7!FDcx0tRsmpkRuZ!yn7...

...}S0C~EGV+L3HN4dvyf;#&@<;+v(P at a2&J z{K{3(6IdEPR9cb+_hy at 0VLDc&qBsO_9xs(ph%ktQ{aECOX^d$!Tqf at gPhCcPS_*(6 zr2t=an^EJdE{P4S_T`~#8FgXD`++beZG5m0fG;DF>#?c^qBX-zS!Qse*npBnGhS0U zA)nQ2*SvdYhNXUmw@^?$%dgT!m*dZ>m}u0>p7)`?p6o!8#q+?oZuDkE-UcD8 at aGmK z^@$RyvGAU3{;KM7fCY>?>yDPB!t;K{qn;=sS2XQQYf$I_VA8LN*vv0pUR%8HoB74Y zv68ws{9gUgqdRGGVTR+hvP3MxD8I`=3d0r2$_g>L1h|Fn4^zGI)}S{n9?CqjVLmE1 z1c<ZBUw%{l`#j~g17UO at j7{bUk`)z|`<D~Hs%&j3v>il_5i9iHJU8(}{<l9SrPq8B zY-pe~gX}23_A3<_R<y5X-McqU86_<<)C+<zV0E?qAUu49K*fgzToT`n#<sdLZ!wN5 z&pkJbZ?e1*y8H...

The previous posting on this topic was correct in this is a harmless message but my problem is I'm getting what looks like message per packet sent, or maybe received, or both. Let's just say a crap load. How do I fix it so this message goes away? I would like to be able to see any other error messages that might be more important. Darryl -------------- next part --------------