Oh, and in case this might be relevant. The board is powered by USB, with
only ethernet plugged in.
On Mon, Jul 13, 2015 at 12:01 PM, William Hermans wrote:
> debian@beaglebone:~$ uptime
> 11:58:48 up 23:22, 1 user, load average: 0.22, 0.07, 0.06
> debian@beaglebone:~$ uname -a
> Linux beagle
debian@beaglebone:~$ uptime
11:58:48 up 23:22, 1 user, load average: 0.22, 0.07, 0.06
debian@beaglebone:~$ uname -a
Linux beaglebone 4.1.0-rc8-bone9 #1 Tue Jun 16 23:45:22 UTC 2015 armv7l
GNU/Linux
debian@beaglebone:~$ cat /etc/dogtag
BeagleBoard.org Debian Image 2015-03-01
debian@beaglebone:~$
On Mon, Jul 13, 2015 at 8:46 AM, Graham Haddock wrote:
> What does "cpufreq-set -g performance" do?
> Sounds like it would lock the BBB at max CPU clock speed, or at least, not
> let it go down to the lowest speeds.
Correct...
> I found the generic Debian docs on cpufreq-set, but not the BBB spe
What does "cpufreq-set -g performance" do?
Sounds like it would lock the BBB at max CPU clock speed, or at least, not
let it go down to the lowest speeds.
I found the generic Debian docs on *cpufreq-set*, but not the BBB specific
instruction set and meanings.
--- Graham
On Mon, Jul 13, 2015 at
OK.
I took my Rev.C unit (1c:ba:8c:d9:5e:dd) and loaded
"bone-debian-8.1-lxqt-4gb-armhf-2015-07-05-4gb.img" onto a
16 GB uSD card. Unit, power supply and card are "trusted."
Absolutely no changes to the image, just install, boot, run. No updates,
additions or modifications.
No cape, only connecti
>
> *(3) System bb4f8e still has 4.1.0-rc8-bone9 #1 Wed Jun 17 00:05:43 UTC
> 2015 armv7l GNU/Linux: but cpufreq-set -g performance: no more reboot*
Interesting . . . If memory serves correctly, that was the "fix" for an
older kernel. So possibly older code crept into the newer ?
On Sun, Jul 12,
Results from overnight test:
I used the worst rebooters for some tests:
(1) System bb1cf1 got installed with 3.19.3-bone4: *no more reboot*
uptime
03:23:37 up 14:50, 1 user, load average: 0.00, 0.01, 0.05
(2) System bb6c1f: installed with 4.1.1-ti-r2 #1 SMP PREEMPT Wed Jul 8
17:03:29 UTC 201
Thanks Peter for the in depth explanation. I was actually just reading a
very detailed blog post by a person bug hunting in fedora 20 . . . the blog
post could be considered a book in of its self, and wow yes, lots of
learning to do before I can achieve the same myself.
On Sun, Jul 12, 2015 at 2:1
On 07/12/2015 04:41 PM, William Hermans wrote:
> /Yeah, I think the transition to linear irq domain (added at 3.18) made
> cpsw/
> /a little extra flaky. Plus the new omap_8250 serial driver is not
> bug-free;/
> /just found a flow control bug in the h/w last week./
> //
> /I'
ah I see. following my own advice comes in handy sometimes . . . as in
GitBisect. A bit out of my abilities.
On Sun, Jul 12, 2015 at 1:41 PM, William Hermans wrote:
> *Yeah, I think the transition to linear irq domain (added at 3.18) made
>> cpsw*
>> * a little extra flaky. Plus the new omap_825
>
> *Yeah, I think the transition to linear irq domain (added at 3.18) made
> cpsw*
> * a little extra flaky. Plus the new omap_8250 serial driver is not
> bug-free;*
> * just found a flow control bug in the h/w last week.*
>
> * I've had ssh shells go sideways on occasion, but not with that kind o
On 07/12/2015 03:35 PM, Graham Haddock wrote:
> Hi William:
> Doing nothing with the board. It is just sitting on the side connected to
> +5V power and Ethernet.
> So, for example, late last night (Central US time) I loaded
> "bone-debian-8.1-lxqt-4gb-armhf-2015-07-05-4gb.img"
> onto a trusted u
Something else that might help troubleshoot this issue if we can get a
"snapshot" of each system by way of *ps aux *and store them somewhere for
later examination. maybe pastebin.
http://pastebin.com/ydneAtne
On Sun, Jul 12, 2015 at 12:50 PM, 'dl4mea' via BeagleBoard <
beagleboard@googlegroups.co
I now have one of the worst case rebooters running on 3.19.3-bone4 (already
installed 8h ago)
root@bb1cf1:~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 8.1 (jessie)
Release:8.1
Codename: jessie
root@bb1cf1:~# uname -a
Linux rc
>
>
> *Hi William:*
>
> *Doing nothing with the board. It is just sitting on the side connected
> to +5V power and Ethernet.*
> *So, for example, late last night (Central US time) I loaded
> "bone-debian-8.1-lxqt-4gb-*
> *armhf-2015-07-05-4gb.img"*
>
> *onto a trusted uSD card expanded the memory
Hi William:
Doing nothing with the board. It is just sitting on the side connected to
+5V power and Ethernet.
So, for example, late last night (Central US time) I loaded
"bone-debian-8.1-lxqt-4gb-armhf-2015-07-05-4gb.img"
onto a trusted uSD card expanded the memory using gparted to the full 16GB,
> W: Failed to fetch
>> http://repos.rcn-ee.com/debian/dists/jessie/main/binary-armhf/Packages
>> Hash Sum mismatch
>>
>
Solution:
http://askubuntu.com/questions/41605/trouble-downloading-packages-list-due-to-a-hash-sum-mismatch-error
Simply: rm -rf /var/lib/apt/lists/*
--
For more optio
By the way, currently on sdcard I am running wheezy 7.8 I believe.
debian@beaglebone:~$ cat /etc/dogtag
BeagleBoard.org Debian Image 2015-03-01
debian@beaglebone:~$ uname -a
Linux beaglebone 3.8.13-bone70 #1 SMP Fri Jan 23 02:15:42 UTC 2015 armv7l
GNU/Linux
So I could apt-get install linux-image-4
Anyway, guys, give me an idea of what you're doing on these boards. When
you get random system reset, and I'll test here too. I have a couple free
beaglebones I can run arbitrary tests on at the moment.
On Sun, Jul 12, 2015 at 12:19 PM, William Hermans wrote:
> I've had this, or something simila
I've had this, or something similar happen to me a few times. When I did
apt-get update again right after, it succeeded. But I'm still not sure of
the cause.
On Sun, Jul 12, 2015 at 11:48 AM, 'dl4mea' via BeagleBoard <
beagleboard@googlegroups.com> wrote:
> If I look on one - but not the target "
If I look on one - but not the target "worst case" Beaglebone, I see only
one package matching Robert's suggestion
apt-cache search linux-image | grep ti | grep 4.1
linux-image-4.1.1-ti-r2 - Linux kernel, version 4.1.1-ti-r2
However, if I want to apt-get update on the two current worst case targe
I will try it by reloading a totally untouched
"bone-debian-8.1-lxqt-4gb-armhf-2015-07-05-4gb.img",
and report back. No cape, trusted Rev.C hardware and power supply. All
communications via
Ethernet.
By my saying that 3.14 is rock solid, this includes up to
"bone-debian-8.1-lxqt-4gb-armhf-2015-
watchdog was the first thing that popped into my mind heh.
On Sun, Jul 12, 2015 at 10:46 AM, Robert Nelson
wrote:
>
> On Jul 12, 2015 12:20 PM, "'dl4mea' via BeagleBoard" <
> beagleboard@googlegroups.com> wrote:
> >
> > Instabilities have been found by just flashing elinux.org images from,
> for
On Jul 12, 2015 12:20 PM, "'dl4mea' via BeagleBoard" <
beagleboard@googlegroups.com> wrote:
>
> Instabilities have been found by just flashing elinux.org images from,
for example,
>
http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Jessie_Snapshot_console,
in special Flasher: (console) (BeagleBo
Instabilities have been found by just flashing elinux.org images from, for
example,
http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Jessie_Snapshot_console,
in special *Flasher: (console) (BeagleBone Black eMMC)*
and letting the board idle with network + serial console connected
Also, is 4.
Instabilities have been found by just flashing elinux.org images from, for
example,
http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Jessie_Snapshot_console,
in special *Flasher: (console) (BeagleBone Black eMMC)*
and letting the board idle with network + serial console connected
Also, is 4.
On 07/12/2015 10:17 AM, Graham wrote:
> I have several Rev C BBB units, that have been in use enough to be considered
> "trusted" hardware.
>
> All of them, running Debian 8.1 kernel 3.14 are rock solid. By that, I mean
> that they will run for months without problems.
> Maybe longer, I have no
I have several Rev C BBB units, that have been in use enough to be
considered "trusted" hardware.
All of them, running Debian 8.1 kernel 3.14 are rock solid. By that, I
mean that they will run for months without problems.
Maybe longer, I have not left them undisturbed for any longer than that.
28 matches
Mail list logo
