Dranoweb
Posts: 147
Joined: Thu Mar 20, 2014 3:01 pm

Raspberry Pi B+ Samba crash issues/problems

Tue Aug 05, 2014 11:02 am

Hi all.
Before I start - here is my setup:
--------equipment-------------
Raspberry pi B+
Raspicam NoIR module
2amp 12v lighter replacement module.
7ah 12v Gel cell with solar regulator for charging.
1watt Wifi module with 12db antenna array.
Led across GPIO #18 with 390 ohm resistor in series
Pushbutton across GPIO #17 with internal pull up resistor enabled
Optocoupler on GPIO #18 with 390 ohm resistor in series
-----------------------------------
------------situation start----------------------------------------
I've been researching this issue for a few days now and can't seem to find a reference anywhere, and I am beginning to think I may be the first, although unlikely.

I recently upgraded a prototype camera box from a B model to a B+, after an apt-get update and upgrade to get the USB ports working, I ordered extras for test bed units. so I have a spare B and B+ for testing.

-------------situation end ---------------------------------

----------Problem description start-------------------

When I try to access a samba share on a win7 machine, the pi crashes.

Definition of "Crash" - ceases to transmit data over wifi,
My LED stops flashing (on GPIO 17, shutdown python script running from button trigger on GPIO 18 - internal pull up enabled)
Activity light on Pi (B+) ceases.

Solutions attempted: (all in sudo)

Code: Select all

apt-get remove --purge samba
apt-get install samba
reboot
apt-get update && upgrade
reboot
Restored smb.conf from backups.

Errors during these processes: (all in SUDO)

Code: Select all

-during update and upgrade-
E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?
-during samba reinstall-

Code: Select all

pi@mobilecam ~ $ sudo apt-get install samba
sudo: unable to resolve host mobilecam
Reading package lists... Done
Building dependency tree
Reading state information... Done
samba is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]? y
Setting up uv4l-raspicam-extras (1.1) ...
update-rc.d: using dependency based boot sequencing
update-rc.d: warning: default start runlevel arguments (2 3 4 5) do not match uv4l_raspicam Default-Start values (S)
update-rc.d: warning: default stop runlevel arguments (0 1 6) do not match uv4l_raspicam Default-Stop values (none)
insserv: script uv4l_raspicam: service uv4l_raspicam already provided!
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error processing uv4l-raspicam-extras (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 uv4l-raspicam-extras
E: Sub-process /usr/bin/dpkg returned an error code (1)
----------Problem description end-------------------

-----------smb.conf----------------

Code: Select all

#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which 
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic 
# errors. 
# A well-established practice is to name the original file
# "smb.conf.master" and create the "real" config file with
# testparm -s smb.conf.master >smb.conf
# This minimizes the size of the really used smb.conf file
# which, according to the Samba Team, impacts performance
# However, use this with caution if your smb.conf file contains nested
# "include" statements. See Debian bug #483187 for a case
# where using a master file is not a good idea.
#

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = WORKGROUP

# server string is the equivalent of the NT Description field
   server string = %h server

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
#   wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
   dns proxy = no

# What naming service and in what order should we use to resolve host names
# to IP addresses
;   name resolve order = lmhosts host wins bcast

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
   max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
#   syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
   syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
#   security = user

# You may wish to use password encryption.  See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
   encrypt passwords = true

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.  
   passdb backend = tdbsam

   obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
   unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
   pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
   map to guest = bad user

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
;   domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the 
# SAMR RPC pipe.  
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.  
; add group script = /usr/sbin/addgroup --force-badname %g

########## Printing ##########

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
#   load printers = yes

# lpr(ng) printing. You may wish to override the location of the
# printcap file
;   printing = bsd
;   printcap name = /etc/printcap

# CUPS printing.  See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
;   printing = cups
;   printcap name = cups

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;   include = /home/samba/etc/smb.conf.%m

# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
#         SO_RCVBUF=8192 SO_SNDBUF=8192
#   socket options = TCP_NODELAY

# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
;   message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
#   domain master = auto

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;   idmap uid = 10000-20000
;   idmap gid = 10000-20000
;   template shell = /bin/bash

# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
;   winbind enum groups = yes
;   winbind enum users = yes

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
;   usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
   usershare allow guests = yes

#======================= Share Definitions =======================

[homes]
   comment = Home Directories
   browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
   read only = no

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
   create mask = 0777

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
   directory mask = 0777

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# The following parameter makes sure that only "username" can connect
# to \\server\username
# This might need tweaking when using external authentication schemes
   valid users = %S

[dcim]
   comment= dcim
   path=/home/pi/dcim
   browseable=Yes
   writeable=Yes
   only guest=no
   create mask=0777
   directory mask=0777
   public=yes

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles

;   path = /home/samba/profiles

;   guest ok = no

;   browseable = no

;   create mask = 0600
;   directory mask = 0700

[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin

# A sample share for sharing your CD-ROM with others.
;[cdrom]
;   comment = Samba server's CD-ROM
;   read only = yes
;   locking = no
;   path = /cdrom
;   guest ok = yes

# The next two parameters show how to auto-mount a CD-ROM when the
#	cdrom share is accesed. For this to work /etc/fstab must contain
#	an entry like this:
#
#       /dev/scd0   /cdrom  iso9660 defaults,noauto,ro,user   0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
#	is mounted on /cdrom
#
;   preexec = /bin/mount /cdrom
;   postexec = /bin/umount /cdrom
---------------------------------------

User avatar
RaTTuS
Posts: 10559
Joined: Tue Nov 29, 2011 11:12 am
Location: North West UK
Contact: Twitter YouTube

Re: Raspberry Pi B+ Samba crash issues/problems

Tue Aug 05, 2014 11:05 am

is the power browning out ?
what does dmesg say ?
can you tail -f /var/log/syslog
and make it crash
is the wifi pulling too much power ?
have yo upgraded the USB power to be be 1.2A
How To ask Questions :- http://www.catb.org/esr/faqs/smart-questions.html
WARNING - some parts of this post may be erroneous YMMV

1QC43qbL5FySu2Pi51vGqKqxy3UiJgukSX
Covfefe

User avatar
AndrewS
Posts: 3625
Joined: Sun Apr 22, 2012 4:50 pm
Location: Cambridge, UK
Contact: Website

Re: Raspberry Pi B+ Samba crash issues/problems

Tue Aug 05, 2014 1:27 pm

If you can temporarily connect a display and keyboard (or a USB TTL UART cable) that would make debugging much easier, as you'd be able to run commands without relying on the wifi connection...

Dranoweb
Posts: 147
Joined: Thu Mar 20, 2014 3:01 pm

Re: Raspberry Pi B+ Samba crash issues/problems

Tue Aug 05, 2014 3:55 pm

Have upgraded the 12v regulator to a 4a version since posting, with no change.
Power consumption at the 12v is is actually down by about 0.8w

Load tested the battery with 4amp shunt (as I did when first designed).
Battery seems to be within 90% of my readings when new.

I seem to be able to view html stream from motion MMAL with no issues.
File transfers still crash Samba before completing a single file.
Seems to be easy to reproduce, on mains supply or battery.
I have reproduced the error on my spare B+ on the desk via wired network.

SSH connection provides me a stable connection, and does not crash the wifi, it's only on file transfer that the issue occurs.
But, I can use my 2nd B+ to attempt this if needed, as the current design restricts access to the HDMI - and it's on upside-down, so my right-andle adaptors are useless.

--------------diagnostics------------------
Tail output:

Code: Select all

Aug  5 21:23:15 mobilecam dhclient: DHCPOFFER from 192.168.1.5
Aug  5 21:23:15 mobilecam dhclient: DHCPACK from 192.168.1.5
Aug  5 21:23:16 mobilecam dhclient: bound to 192.168.1.221 -- renewal in 36526 seconds.
Aug  5 21:23:17 mobilecam ntpd[2217]: Listen normally on 2 wlan0 192.168.1.221 UDP 123
Aug  5 21:23:17 mobilecam ntpd[2217]: peers refreshed
Aug  5 21:23:19 mobilecam ntpd_intres[2225]: DNS 0.debian.pool.ntp.org -> 192.189.54.17
Aug  5 21:23:19 mobilecam ntpd_intres[2225]: DNS 1.debian.pool.ntp.org -> 203.23.237.200
Aug  5 21:23:19 mobilecam ntpd_intres[2225]: DNS 2.debian.pool.ntp.org -> 202.127.210.37
Aug  5 21:23:19 mobilecam ntpd_intres[2225]: DNS 3.debian.pool.ntp.org -> 192.189.54.33
Aug  5 21:23:19 mobilecam ntpdate[2588]: the NTP socket is in use, exiting
----------------------------------------------

User avatar
RaTTuS
Posts: 10559
Joined: Tue Nov 29, 2011 11:12 am
Location: North West UK
Contact: Twitter YouTube

Re: Raspberry Pi B+ Samba crash issues/problems

Tue Aug 05, 2014 4:14 pm

what is the power measured from tp1 tp2 [model B] - model b+ should be fine so this is probably a red herring
with and without the wi-fi adapter
and with it [wifi] running
how much free space on the device you are coping to?
How To ask Questions :- http://www.catb.org/esr/faqs/smart-questions.html
WARNING - some parts of this post may be erroneous YMMV

1QC43qbL5FySu2Pi51vGqKqxy3UiJgukSX
Covfefe

Dranoweb
Posts: 147
Joined: Thu Mar 20, 2014 3:01 pm

Re: Raspberry Pi B+ Samba crash issues/problems

Tue Aug 05, 2014 4:20 pm

Further testing completed:

----------changes--------------
swapper card into spare B+ module.
detached LED
detached pushbutton
detached 1 watt WIFI module (atheros something with custom firmware)
detached NoIR raspicam
Attached micro Wifi module (RTL8187)
Attached HDMI monitor
Attached USB keyboard
Attached Standard Raspicam
-----------------------------------

-----------tests-----------------
waved in front of camera - success
camera saved images of waving - success
checked wicd-curses for auto connect to wifi - success
checked for samba presence on windows network - success
reconnected mapped network drive in win 7 - success
ran batch script to move all files to win 7 machine - success
-----------------------------------

I would say we indeed have a peripheral/power issue

The one this I now realize I did not check, is the polarity of the optocoupler connections when I swapped from the B to the B+
I will now do so as I recall the B+ had reports of sensitive pins, that when touched, would cause a restart/freeze.

Dranoweb
Posts: 147
Joined: Thu Mar 20, 2014 3:01 pm

Re: Raspberry Pi B+ Samba crash issues/problems

Tue Aug 05, 2014 4:38 pm

RESOLVED!

Wifi Card Issue.

It appears to be a damaged cable to the Wifi card.

Using a USB extender, I attached the RTL8187 micro usb WIFI adaptor and moved 250 files with no issue.

Reconnected the Atheros USB card, and I'm having severe stability issues.

Replaced the cable to the card and was able to transfer 3-4 files before a crash.
Apologies people - this one's a hardware one....

Dranoweb
Posts: 147
Joined: Thu Mar 20, 2014 3:01 pm

Re: Raspberry Pi B+ Samba crash issues/problems

Tue Aug 05, 2014 4:45 pm

ADDITIONAL:

Tested 1 Watt WIFI card on win7 system.

Copying a 1.5gb file averaged 900k/sec

Using the same cable.

I suspect this may be something to do with the Atheros drivers from the recent apt-get upgrade.

Dranoweb
Posts: 147
Joined: Thu Mar 20, 2014 3:01 pm

Re: Raspberry Pi B+ Samba crash issues/problems

Tue Aug 05, 2014 4:55 pm

Correction - 1 Watt WIFI card is a Ralink chipset.

Dranoweb
Posts: 147
Joined: Thu Mar 20, 2014 3:01 pm

Re: Raspberry Pi B+ Samba crash issues/problems

Tue Aug 05, 2014 5:24 pm

I now know this to be a driver issue with the Ralink 2870.

I am running kernel 3.12.22+

I have swapped out the drivers with older ones, and now have a non-working card lol>

Currently have two usb wifi modules attached so that I can diagnose more easily.
Will post when I have a solution.

Dranoweb
Posts: 147
Joined: Thu Mar 20, 2014 3:01 pm

Re: Raspberry Pi B+ Samba crash issues/problems

Wed Aug 06, 2014 3:05 pm

Currently attempting firmware update - had forgotten to do this when migrating to the B+

Code: Select all

sudo rpi-update
will keep you posted.

Dranoweb
Posts: 147
Joined: Thu Mar 20, 2014 3:01 pm

Re: Raspberry Pi B+ Samba crash issues/problems

Wed Aug 06, 2014 3:14 pm

Now running kernel 3.12.25+

Stability issues remain

However - freeze problem is no more.

SSH stays online, it just seems that samba crashed - and network name and shares disappear from Windows network.

all cables, power supply and pi board swapped for testing, with no change.

Dranoweb
Posts: 147
Joined: Thu Mar 20, 2014 3:01 pm

Re: Raspberry Pi B+ Samba crash issues/problems

Fri Aug 08, 2014 11:06 am

NOT RESOLVED!!!

re-ran the tests with the original B model Pi, and no issues at all.

swap the board for a B+ and I have dropouts - running the same card....

I'm about to lose my mind

User avatar
RaTTuS
Posts: 10559
Joined: Tue Nov 29, 2011 11:12 am
Location: North West UK
Contact: Twitter YouTube

Re: Raspberry Pi B+ Samba crash issues/problems

Fri Aug 08, 2014 11:16 am

see also
http://www.raspberrypi.org/forums/viewt ... 28&t=83881
there may be a power issue ....
dunno if related
How To ask Questions :- http://www.catb.org/esr/faqs/smart-questions.html
WARNING - some parts of this post may be erroneous YMMV

1QC43qbL5FySu2Pi51vGqKqxy3UiJgukSX
Covfefe

Dranoweb
Posts: 147
Joined: Thu Mar 20, 2014 3:01 pm

Re: Raspberry Pi B+ Samba crash issues/problems

Fri Aug 08, 2014 3:31 pm

Awesome!
You may be onto something there , I do remember reading something about that in the pre-release info for the B+

For the moment I have retrofitted the B model back into my project to get it running. I'll experiment with the B+ on my testbed - as I have two of everything....

Dranoweb
Posts: 147
Joined: Thu Mar 20, 2014 3:01 pm

Re: Raspberry Pi B+ Samba crash issues/problems

Mon Sep 15, 2014 8:54 am

Finally solved this - Thought I should follow up even though it has been a while.

End solution was three things:

Most importantly - I had to set GPIO #4 to high on boot. This apparently kicks in a second resistor on the brownout detector, increasing the "brownout condition" to 1200ma instead of 600ma.

Second: disconnected the Dallas RTC DS3231, as it was pulling the 3.3v line too low, along with the DHT22 seonsor.

Thirdly, the 5v switch mode regulator on my 12v usb adaptor was overheating - badly. IR temp meter clocked it at 85C.
overkilled the heatsink, and used the side of the ammo box and some heatsink compound to dissipate the excess heat.

at night when everything is working hardest, the atmospheric temp is lower and the heatsinking works well.

also now using the DHT22, to help out with an overtemp "cool off" routine, to shut down non essentials for a few min when it gets too hot.

Dranoweb
Posts: 147
Joined: Thu Mar 20, 2014 3:01 pm

Re: Raspberry Pi B+ Samba crash issues/problems

Mon Sep 15, 2014 8:55 am

oh and yes - I should add - a few extra bits got added between the last couple of posts.

guillier
Posts: 6
Joined: Mon Jan 12, 2015 10:10 pm

Re: Raspberry Pi B+ Samba crash issues/problems

Mon Jan 12, 2015 10:23 pm

Dranoweb wrote: Second: disconnected the Dallas RTC DS3231, as it was pulling the 3.3v line too low, along with the DHT22 sensor.
Hi,
thanks to your post I finally found the reason for my trouble (SD Card crash, inexplicable high load or Raspberry being very very slow).
My RTC module comes with both a DS3231 and a AT24C02 EEPROM on the same board. I assume the problem is related to https://github.com/raspberrypi/linux/issues/254 but I was wondering which IC (RTC or EEPROM) would be the clock stretcher as nobody else than you seems to have reported any problem with their DS3231.

Did you board also contain an EEPROM?

Thanks.

Dranoweb
Posts: 147
Joined: Thu Mar 20, 2014 3:01 pm

Re: Raspberry Pi B+ Samba crash issues/problems

Tue Jan 13, 2015 10:50 pm

No, my board did not contain an eeprom.
they were cheap Chinese addons I purchased for about $2 each, and had just a small super capacitor, quartz timing crystal and a single chip.

guillier
Posts: 6
Joined: Mon Jan 12, 2015 10:10 pm

Re: Raspberry Pi B+ Samba crash issues/problems

Wed Jan 14, 2015 8:22 pm

OK. Thanks a lot for the information.

Mine is also a chinese import but the cheapest I could find (£1.21 !) with CR2032 battery also had an eeprom (which I never used). Well at least my Raspberry Pi is now clocking along and we know the culprit even if I can't explain why...

Dranoweb
Posts: 147
Joined: Thu Mar 20, 2014 3:01 pm

Re: Raspberry Pi B+ Samba crash issues/problems

Thu Jan 15, 2015 1:04 am

I think the main issue is that I was running a DHT22 temp/humidity sensor from the same 3.3v output.
I think it was pulling that voltage down too low.

simple fix was pull the clock and use NTP.
I have a 5v to 3.3v adaptor board for arduino somewhere, I'll try feeding it off the 5v line when I can find the time.

guillier
Posts: 6
Joined: Mon Jan 12, 2015 10:10 pm

Re: Raspberry Pi B+ Samba crash issues/problems

Thu Jan 15, 2015 6:58 am

Good point. I also have a DHT22 on the 3.3V and a 3.3V <-> 5V converter plugged in so I can easily try to connect the DS3231 module on the 5V side.

guillier
Posts: 6
Joined: Mon Jan 12, 2015 10:10 pm

Re: Raspberry Pi B+ Samba crash issues/problems

Sat Jan 17, 2015 4:03 pm

Same unstable behaviour when plugged on the 5V side of I2C. Although this time I had a "[sched_delayed] sched: RT throttling activated" message. Heavy load collapses and sluggishness disappears when RTC board is unplugged. I still don't know the root cause but I am giving up using it!

Dranoweb
Posts: 147
Joined: Thu Mar 20, 2014 3:01 pm

Re: Raspberry Pi B+ Samba crash issues/problems

Sat Jan 17, 2015 10:19 pm

Perhaps get your 3.3v from somewhere else. Maybe use a 7803 regulator direct from the 5v in?
they go for about $1.50

guillier
Posts: 6
Joined: Mon Jan 12, 2015 10:10 pm

Re: Raspberry Pi B+ Samba crash issues/problems

Sun Jan 18, 2015 3:17 pm

Hum, since it has a similar behaviour either on 3.3V or 5V, I believe it has something to do either with the DS1307 module or more likely messing up with the I2C bus. I have a few other IC plugged on this bus (BMP085, LCM1602, ...) so it could be a bad interaction with them.

Return to “Troubleshooting”