Home of the Squeezebox™ & Transporter® network music players.
Page 2 of 5 FirstFirst 1234 ... LastLast
Results 11 to 20 of 42
  1. #11
    Junior Member
    Join Date
    May 2019
    Posts
    27
    I've just had this exact thing happen to me, Also running PiZero, with HifiBerry Dac Zero, on PcP 5.0, I was originally running 4.1 and upgrades have been with the card in the Pi.

    On my LMS webinterface, the player called 'Orange' simply vanished. Music stopped straight away. Listening to a 128KBps radio station at the time.

    I was already logged in on SSH and can still access the webinterface, here's what the diagnostics has to say:

    [ INFO ] Squeezelite process:
    /usr/local/bin/squeezelite -n Orange -o hw:CARD=sndrpihifiberry -a 80 4 1 -v -C 15

    Squeezelite still seems to be running:
    Code:
    tc@PiZero:~$ ps -A | grep squeeze
     2121 root      3:07 /usr/local/bin/squeezelite -n Orange -o hw:CARD=sndrpihifiberry -a 80 4  1 -v -C 15
    My network connection seems OK:
    Code:
    tc@PiZero:~$ iwconfig wlan0
    wlan0     IEEE 802.11  ESSID:"xxxxxx"  
              Mode:Managed  Frequency:2.447 GHz  Access Point: xxxxxxxx
              Bit Rate=65 Mb/s   Tx-Power=31 dBm   
              Retry short limit:7   RTS thr:off   Fragment thr:off
              Power Management:off
              Link Quality=50/70  Signal level=-60 dBm  
              Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
              Tx excessive retries:282  Invalid misc:0   Missed beacon:0
    dmesg did show this at the end however:

    Code:
    [ 2105.052866] pcm5102a-codec pcm5102a-codec: pcm5102a_dai_startup: Limiting sample rate support to 192kHz MAX
    [ 3454.877425] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
    Complete dmesg is at: https://paste2.org/fwb6g9PO

    The Volume was not properly unmounted error seemed to occur around the same time as the player vanished from LMS, but I'm not really sure how to run fsck under PCP, but I can try if this may stop this from happening.

    After around 5-10 mins the player has reappeared on the LMS webinterface, and is now playing music again, this time some FLAC's without issue, I did not reboot it.

    Could this be some of sort SD card issue? Next time I have the player apart I can try restarting PCP with a different SD card and see if it happens again, but it takes a while for me to take the player out as it's bolted into a case.

    Other things I checked:
    CPU Temp:
    cat /sys/class/thermal/thermal_zone0/temp = 58376
    58 degrees C

    power throttling?
    cat /sys/devices/platform/soc/soc:firmware/get_throttled = 0
    no power throttling
    Last edited by TheHypnoToad; 2019-07-31 at 08:20. Reason: extra info added

  2. #12
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    2,001
    The fat error is pretty harmless, and would be unrelated.

    from your log,
    Code:
    [   31.100454] pcm5102a-codec pcm5102a-codec: pcm5102a_dai_startup: Limiting sample rate support to 192kHz MAX
    [   31.655319] brcmfmac: power management disabled
    [   31.767930] pcm5102a-codec pcm5102a-codec: pcm5102a_dai_startup: Limiting sample rate support to 192kHz MAX
    [   33.950362] Finished piCorePlayer v5.0.0 startup.
    [  901.862425] sched: RT throttling activated
    [ 1101.212729] pcm5102a-codec pcm5102a-codec: pcm5102a_dai_startup: Limiting sample rate support to 192kHz MAX
    [ 1513.817876] pcm5102a-codec pcm5102a-codec: pcm5102a_dai_startup: Limiting sample rate support to 192kHz MAX
    [ 1917.770103] pcm5102a-codec pcm5102a-codec: pcm5102a_dai_startup: Limiting sample rate support to 192kHz MAX
    [ 1943.594702] pcm5102a-codec pcm5102a-codec: pcm5102a_dai_startup: Limiting sample rate support to 192kHz MAX
    [ 1946.969047] pcm5102a-codec pcm5102a-codec: pcm5102a_dai_startup: Limiting sample rate support to 192kHz MAX
    [ 2074.775198] pcm5102a-codec pcm5102a-codec: pcm5102a_dai_startup: Limiting sample rate support to 192kHz MAX
    [ 2104.959325] pcm5102a-codec pcm5102a-codec: pcm5102a_dai_startup: Limiting sample rate support to 192kHz MAX
    [ 2105.052866] pcm5102a-codec pcm5102a-codec: pcm5102a_dai_startup: Limiting sample rate support to 192kHz MAX
    [ 3454.877425] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
    I'm not sure why that message is being repeated so many times, normally you might see that only at startup. Seems like to me the card is disappearing. Perhaps you guys might want to check your connections on the GPIO header.
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  3. #13
    Junior Member
    Join Date
    May 2019
    Posts
    27
    Quote Originally Posted by paul- View Post
    The fat error is pretty harmless, and would be unrelated.
    Nice, I was going to try and somehow start messing about with fsck, glad I don't have to now.

    Quote Originally Posted by paul- View Post
    I'm not sure why that message is being repeated so many times, normally you might see that only at startup. Seems like to me the card is disappearing. Perhaps you guys might want to check your connections on the GPIO header.
    I will double and triple check my connections and soldering next time the pi is onbolted, I do need do re-do some cabling also so it will be the perfect time to do so. I'm running a normal header connection for the DAC.

    However I've found I always get the:
    'Limiting sample rate support to 192kHz MAX'
    Message whenever I turn the player on in the LMS webinterface.

    I've just turned it off then on again in LMS webinterface, this is the last message:

    [ 5453.232414] pcm5102a-codec pcm5102a-codec: pcm5102a_dai_startup: Limiting sample rate support to 192kHz MAX

    'uptime' shows:
    16:32:09 up 1:31, 2 users, load average: 1.06, 1.11, 1.09

    1hr 31min = 5460 seconds, above message is at 5453 seconds which is around the same time.

  4. #14
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    2,001
    Which hifiberry board are you guys using?
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  5. #15
    Senior Member sbp's Avatar
    Join Date
    Apr 2010
    Location
    Denmark
    Posts
    1,162
    Another question: are you using the normal kernel or the rt kernel?
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like piCorePlayer

  6. #16
    Senior Member
    Join Date
    May 2017
    Posts
    551
    Normal version.
    SqueezeBoxes: 1x Transporter (Living room) 1x SB2 (shed), 1x Radio (Kitchen), 1x Boom (Dining room), 1x piCorePlayer (jacuzzi), 1x piCorePlayer (Garden) 1x OSMC + Squeezelite (Movie room), 1x Touch (Study 2), few spare unit's
    Server: LMS on Pi3 7.9.1. on PcP 3.21
    Network: AVM Fritzbox, Netgear Smart Switch 24p, 3x Ubiquity

  7. #17
    Senior Member Greg Erskine's Avatar
    Join Date
    Sep 2006
    Location
    Sydney, Australia
    Posts
    1,719
    Hi edwin2006,

    Try removing "-C 15" from the Squeezelite command line. This is usually added for Shairport-sync".

    I haven't seen "[ 901.862425] sched: RT throttling activated" in dmesg before? I would have assumed you are using the RT kernel.

    I'd be tempted to enable "all=info" to see if the problem coincides with playing certain files.

    As mentioned having the dirty bit set is usually not a problem. If you really want to reset the dirty bit try "http://192.168.1.xxx/cgi-bin/xtras_dosfsck.cgi"

    regards
    Greg

  8. #18
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    2,001
    Okay, I dug into that rate limiting message. Since rpi started to merge some of the 384k support, I decided to start including the full 384k patch set in the regular kernel. The PCM5102a driver has a parameter to the dtoverlay to enable the 384k support. So that's why that message is printing. You can go into card control and check the 384k parameter and that will enable 384k sample rates for your card.....or just ignore the message.

    The RT throttling message is related to threads marked as SCHED_FIFO in which I believe that the only process getting set with that scheduling priority is the output thread in squeezelite.

    Is your zero just a player. Or have you added alot of "extras" that we offer with pCP.
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  9. #19
    Senior Member
    Join Date
    May 2017
    Posts
    551
    Quote Originally Posted by Greg Erskine View Post
    Hi edwin2006,

    Try removing "-C 15" from the Squeezelite command line. This is usually added for Shairport-sync".

    I haven't seen "[ 901.862425] sched: RT throttling activated" in dmesg before? I would have assumed you are using the RT kernel.

    I'd be tempted to enable "all=info" to see if the problem coincides with playing certain files.

    As mentioned having the dirty bit set is usually not a problem. If you really want to reset the dirty bit try "http://192.168.1.xxx/cgi-bin/xtras_dosfsck.cgi"

    regards
    Greg
    Hi Greg.
    The stopping of squeezelite is now and then. It can run for weeks and then suddenly stop.
    Hardware consists out of Pi Zero W + HiFiBerry DAC+ Zero - RCA
    Software piCorePlayer v5.0.1 | linux 4.19.40-pcpCore | piCore v10.1pCP | Squeezelite v1.9.2-1158-pCP => with ALSA 10 band Equalizer enabled
    No really special add-on's. No problem on SBT, SB1, Boom, Radio and another pi (Pi3-1Gb with piCorePlayer v3.20beta5 | linux 4.9.17-pcpCore_v7+ | piCore v8.01 | Squeezelite v1.8.6-945)

    regards, Edwin
    SqueezeBoxes: 1x Transporter (Living room) 1x SB2 (shed), 1x Radio (Kitchen), 1x Boom (Dining room), 1x piCorePlayer (jacuzzi), 1x piCorePlayer (Garden) 1x OSMC + Squeezelite (Movie room), 1x Touch (Study 2), few spare unit's
    Server: LMS on Pi3 7.9.1. on PcP 3.21
    Network: AVM Fritzbox, Netgear Smart Switch 24p, 3x Ubiquity

  10. #20
    Junior Member
    Join Date
    May 2019
    Posts
    27
    Ok, I've had my player apart today and double checked my GPIO solders, and all are measured OK with multimeter with continuity test, so hardware side is good.

    Quote Originally Posted by paul- View Post
    Which hifiberry board are you guys using?
    I'm using a board which is essentially the same as the hifiberry DAC+ Zero - It's the Pimoroni Phat DAC, it uses the same components, and same hardware overlay, more info about it is here: https://learn.pimoroni.com/tutorial/...at-dac-install

    "dtoverlay=hifiberry-dac

    pHAT DAC uses the same hardware as HiFi Berry, so we're borrowing their device-tree overlay!"

    Quote Originally Posted by sbp View Post
    Another question: are you using the normal kernel or the rt kernel?
    Normal kernel, uname -a shows this:
    Linux PiZero 4.19.40-pcpCore #1 Sat May 11 13:40:46 EDT 2019 armv6l GNU/Linux

    Quote Originally Posted by paul- View Post
    You can go into card control and check the 384k parameter and that will enable 384k sample rates for your card.....or just ignore the message.
    I'll ignore the message I think, I don't have any audio files over 96K so I'll leave 384k turned off.

    Quote Originally Posted by paul- View Post
    Is your zero just a player. Or have you added alot of "extras" that we offer with pCP.
    I am running a few extras, I'm using JiveLite with a HDMI touchscreen. 'top' is showing Jivelite is using around 50-60% CPU.

    I'm also using 'sbpd' which allows me to have rotary encoder up to the GPIO runs, and gives me a non-touchscreen volume control and play/pause buttons.

    Finally I've also added in the PWM kernel module for backlight dimming of the screen, however I only added this recently and before that I still experienced this issue.

    Here's my squeezelite command string:

    /usr/local/bin/squeezelite -n "Orange" -o hw:CARD=sndrpihifiberry -a 80:4::1 -v -C 15

    I'm not running Equalizer but I am running Shairport-sync, most of my settings are defaults apart from the above mentions tweaked.

    I have other Squeezebox devices and 2 other picoreplayer devices, and not had this issue with any other device.

    It's happened again today, it seem that squeezelite crashing or going into some sort of infinite loop, when the player dissappears from the LMS, squeezelite CPU usage maxes out, here's the output from the 'top' command:

    Code:
    Mem: 173672K used, 318588K free, 14360K shrd, 17260K buff, 62444K cached
    CPU: 95.8% usr  0.3% sys  0.0% nic  3.8% idle  0.0% io  0.0% irq  0.0% sirq
    Load average: 5.01 3.76 2.38 1/113 7861
      PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND
     2138     1 root     S    15384  3.1   0 94.8 /usr/local/bin/squeezelite -n Orange -o hw:CARD=sndrpihifiberry -a 80 4  1
     7860  7754 tc       R     3200  0.6   0  0.3 top
     7753  7750 tc       S     5108  1.0   0  0.1 ssh
    Jivelite UI is frozen also, I still have (slow) ssh access, CPU temp is 60, network is fine. squeezelite usually uses between 5-10% CPU on my PiZero.
    Last edited by TheHypnoToad; 2019-08-01 at 09:32. Reason: extra info added

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •