powerd rc script failing to start after fresh build

[Shawn Debnath]

Synced to r298678 this evening and after a reboot, powerd fails to start
with the following error in messages:

  Apr 26 17:54:12 titan root: /etc/rc: WARNING: failed to start powerd

Manually trying to start it via service throws:

  $ sudo service powerd start
  Starting powerd.
  powerd: no cpufreq(4) support -- aborting: No such file or directory
  /etc/rc.d/powerd: WARNING: failed to start powerd

dmesg shows:

  CPU: Intel(R) Xeon(R) CPU   X5670  @ 2.93GHz (2933.50-MHz K8-class
  CPU)
Origin="GenuineIntel"  Id=0x206c2  Family=0x6  Model=0x2c  Stepping=2

Features=0xbfebfbff

Features2=0x29ee3ff
AMD Features=0x2c100800
AMD Features2=0x1
VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
TSC: P-state invariant, performance statistics
  real memory  = 68719476736 (65536 MB)
  avail memory = 66696982528 (63607 MB)
  Event timer "LAPIC" quality 600
  ACPI APIC Table: 
  FreeBSD/SMP: Multiprocessor System Detected: 24 CPUs
  FreeBSD/SMP: 2 package(s) x 6 core(s) x 2 hardware threads
  random: unblocking device.
  ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aControlBlock: 32,
  using default 16 (20150818/tbfadt-730)
  ACPI BIOS Warning (bug): Invalid length for FADT/Pm2ControlBlock: 32,
  using default 8 (20150818/tbfadt-730)

This wasn't the case till the update today, including the ACPI BIOS
warning.

Any help appreciated or let me know what else I can provide to help find
the root cause.

Thanks,
Shawn
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

RFC on a published change to FreeBSD 11 kqueue file ops.

[Julian Elischer]

the following change is sitting out at github, to add kqueue support 
for more file operations:


https://github.com/dmatveev/libinotify-kqueue/blob/master/patches

does anyone have reasons why we shouldn't import this change.

libinotify is now a port and could use these.


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

RE: Weird portupgrade error on current amd64 [and powerpc64?]

[Mark Millard]

https://lists.freebsd.org/pipermail/freebsd-ports/2016-April/102983.html 
reported a "Broken pipe" problem with portupgrade on 11.0-CURRENT on amd64.

FYI: I had the/a "Broken pipe" portupgrade problem on powerpc64 under 
11.0-CURRENT -r298518 on 2016-Apr-23 updating from /usr/ports -r413230 to 
-r413919. If this might be the same I do not know. The relevant part of the 
script log is:

> > Compressing man pages (compress-man)
> --->  Backing up the old version
> --->  Uninstalling the old version
> [Reading data from pkg(8) ... - 68 packages found - done]
> --->  Deinstalling 'perl5-5.22.1_7'
> [Reading data from pkg(8) ... - 68 packages found - done]
> ** Listing the failed packages (-:ignored / *:skipped / !:failed)
> ! perl5-5.22.1_7(Broken pipe)
> --->  Skipping 'ports-mgmt/portlint' (portlint-2.16.8) because a requisite 
> package 'perl5-5.22.1_7' (lang/perl5.22) failed (specify -k to force)

ruby was still lang/ruby21 at the time.

I used portmaster instead and everything worked fine.

===
Mark Millard
markmi at dsl-only.net

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

Re: r296548 breaks external DP and HDMI on HD4000

[Ian FREISLICH]

Hi

Replying to myself...

The monitor works with in 1920x1080.  Any higher resolution and the
monitor displays rapidly changing random colours filled over the entire
screen.  I'm currently using r298115 with no improvement on the situation.

Ian

On 03/14/16 13:59, Ian FREISLICH wrote:
> Hi
>
> With r296548 on the following hardware:
>
> vgapci0@pci0:0:2:0: class=0x03 card=0x15171043 chip=0x01668086
> rev=0x09 hdr=0x00
> vendor = 'Intel Corporation'
> device = '3rd Gen Core processor Graphics Controller'
> class  = display
> subclass   = VGA
> cap 05[90] = MSI supports 1 message enabled with 1 message
> cap 01[d0] = powerspec 2  supports D0 D3  current D0
> cap 13[a4] = PCI Advanced Features: FLR TP
>
> I get the following console messages when X starts and my external
> monitor (Samsung U28E590) goes into epileptic fit attack mode.
>
> [drm] Initialized i915 1.6.0 20080730 for drmn0 on minor 0
> [drm:pid0:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting
> [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
> [drm:pid0:intel_cpt_verify_modeset] *ERROR* mode set failed: pipe 0 stuck
> [drm:pid1100:ironlake_check_fdi_lanes] *ERROR* WARN ON:
> I915_READ(SOUTH_CHICKEN1) & FDI_BC_BIFURCATION_SELECT
> [drm:pid1100:ivb_manual_fdi_link_train] *ERROR* FDI train 1 fail!
> [drm:pid1100:ivb_manual_fdi_link_train] *ERROR* FDI train 2 fail!
>
> The good news is that I no longer need the following hack to turn on the
> back light this laptop's LVDS display:
>
> Index: sys/dev/drm2/i915/intel_display.c
> ===
> --- sys/dev/drm2/i915/intel_display.c   (revision 296547)
> +++ sys/dev/drm2/i915/intel_display.c   (working copy)
> @@ -6960,7 +6960,7 @@
>  */
> I915_WRITE(BLC_PWM_CPU_CTL2, PWM_ENABLE);
> I915_WRITE(BLC_PWM_CPU_CTL, 0);
> -   I915_WRITE(BLC_PWM_PCH_CTL1, PWM_ENABLE);
> +   I915_WRITE(BLC_PWM_PCH_CTL1, PWM_ENABLE | (1<<30));
>  }
>  
>  void intel_modeset_init_hw(struct drm_device *dev)
>

-- 
Ian Freislich
(M) +1 404 574 0228


-- 
 

Cape Augusta Digital Properties, LLC a Cape Augusta Company

*Breach of confidentiality & accidental breach of confidentiality *

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If you have received this email in error please notify the system manager. 
This message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and 
delete this e-mail from your system. If you are not the intended recipient 
you are notified that disclosing, copying, distributing or taking any 
action in reliance on the contents of this information is strictly 
prohibited.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"