凡走過必留下痕跡？？在那個 Intel CPU 稱王， Microsoft OS 獨大的 PC 年代，不只創造了『 Standard Bug 』和『 Final Beta 』之經典說法，更因微軟一路攻城掠地，蠶食鯨吞應用軟體市場，又與大學大打侵權之官司，據說搞的個天怒人怨，於是 Bill Gates 的笑話傳聞始終不斷。茲引幾則以饗讀者︰
(1) Bill and the Win 95
God calls Bill Gates, Bill Clinton and Boris Yeltsin to his office and says,
“The world will end in 30 days. Go back and tell your people.” so Boris Yeltsin goes to the Russian people and says: “I have bad news and I have worse news. The bad news is that we were wrong … there is a God. The worse news is that the world will end in 30 days.”
Bill Clinton goes on TV and tell the American people: “I have good news and I have bad news. The good news is that the basic family values upon which we have based our lives are right, there is a God … The bad news is that the world will end in 30 days.”
Bill Gates goes to his executive committee and announces: “I have great news and I have fabulous news. The great news is that God thinks I’m important. The fabulous news is that we don’t have to fix any of the Microsoft’s bugs.”
……
─── 出處《香港中文大學計算機科學與工程學系
Prof. John C.S. Lui
Jokes about Mr. Bill Gates》
自一九九一 Linux 首發，到二零零一《只為歡樂》︰
二零零一年，林納斯‧托瓦茲 Linus Torvalds ── Linux kernel 的創建者 ── 出版了一本他與大衛‧戴爾蒙德 David Diamond 聯合撰寫的幽默自傳《只為歡樂》 Just for Fun: The Story of an Accidental Revolutionary 。這本書提出了『 Linus 法則』 the Law of Linus that all evolution contributed by humanity starts for survival, sustains socially and entertains at last.
─── 摘自《音樂播放器原型機之《可能性》 Just for Fun》
十年磨成之劍，尚在淬火鍛鍊中。或因『吃著魚企鵝圖』的啟示， Tuz 之感召︰
已到春分，晝夜各半，日出前注目地平，那第一道《曙光》映射的正是大地『陽光均分』之時！不知從『太空』所見的『天際線』，能否使人體會『惠施』之【天與地卑，山與澤平。 】？
感受︰
『水藍地球』的『美』，她能是不能喚醒『仁民愛物』之『心』的呢？古往今來『大小觀』之『無窮思辯』，正高聲述說著『生命神奇』與『造化奧妙』的吧！！
想像︰
台灣的『玉山』海拔三千五百九十二公尺，假使站上了『玉山頂巔 』四目極望，是否『眼界』大到足以『擁抱』一整個『美麗寶島』的呢？？
深思︰
當鳳凰已去，麒麟不在，所謂『世界』會更『美麗』嗎？活著的人真很『富足』的耶？？
─── 《W!O+ 的《小伶鼬工坊演義》︰通往樹莓派 3 之 HEARSAY OS》
曾經有人高聲唱著︰
是我們改變了世界？還是世界改變了你和我！
並非作者想將之『鎖起來』不談？
Tue Jun 19, 2018 7:32 am
實因事有『變動』︰
尚待『釐清』呦！
期望『人工智慧』時代的 STEM 們，大刀闊斧創新『典範』也︰
Mon Jun 18, 2018 12:28 pm
wybielacz wrote: ↑
Mon Jun 18, 2018 11:31 am
jamesh wrote: ↑
Mon Jun 18, 2018 9:40 am
Sadly, I don’t have time to dig through pages of posts to find one line of information. Can you give specific instructions on what you do to make this go wrong, and any errors that may be display (e.g. syslogs). Since this does NOT appear to be the tcp segmentation offload issue (although symptoms appear the same – welcome to the wonderful world of ethernet bugs), it would be worth adding a very detailed issue in github (if you haven’t already done so) which is the official way of reporting bugs, it also means they do not get lost. Post a link here to the github issue to cross reference.
In the meantime, does forcing it to 100bT make the problem go away (yes, I know you want Gig ethernet, this is for testing purposes to narrow down the issue)
You already have a 3B+ with an sd card with this issue in your office. Anyway we can safely assume that every 3B+ has this issue, just the right steps needs to be performed to make it crash.
Steps to reproduce are as follows:
1. Install a fresh image of Raspbian
2. Update firmware
3. Mount a cifs network drive
4. 3B+ is dead overnight when using Ethernet, there are no errors, LAN chip is burning hot
Sadly, i do not have time anymore to invest in this, i literally setup my multiple RPi’s 3B+ in the past months hundreds of times new to help you debug and narrow down the issue, even that i am not responsible to do that…
All the 3B+ problems seems to me like this is a faulty ethernet hardware which you trying to cover with software fixes. If that is really the case then please at least do an official statement about it. I mean come on, it’s been 3 months…
I have already tested that sequence overnight and seen no issues, so No, your assumption that this is a problem with every 3B+ appears to be wrong. So there is probably an extra stage of usage or perhaps something about your particular network router that needs to be determined. For example, what is you network doing overnight? Is it in use? Is a lot of data being transferred? Do you have flow control turned on on your router? What software is running on the Pi that might have some impact?
As I said, 3 months is NOTHING when compared to the complexity of trying to figure out ethernet issues that some people see and others don’t. I’ve personally spent months working on ethernet or wifi issues on the Pi over the last years and a half. And what is annoying NONE of them were Raspberry Pi’s fault – they are either in the firmware of the device or in the driver. Neither of which we have much control over, apart from reporting them to the firmware writers, or mailing the Linux netdev group, or trying to figure them out ourselves.
Semi-Official statement. All software has bugs. All HW has bugs, Usually we can get round HW problems with software. In this case, we do not yet know where the problem arises. We have determined at least one cause so far, the tcp segmentation offloading, which has fixed networking problems for most people. There appears to still be something going on, so we will continue to investigate.
I would prefer the investigation to be done via github, because more engineers see it there.
故邀有興趣者自讀論壇哩！？
※ 須知︰
‧ 先認識 vcgencmd 用法︰
Verified commands
Command outputs are from firmware version 362371.
vcgencmd commands
Shows a list of possible commands.
root@raspberrypi:~# vcgencmd commands
commands="vcos, ap_output_control, ap_output_post_processing, vchi_test_init, vchi_test_exit,
pm_set_policy, pm_get_status, pm_show_stats, pm_start_logging, pm_stop_logging, version, commands,
set_vll_dir, led_control, set_backlight, set_logging, get_lcd_info, set_bus_arbiter_mode,
cache_flush, otp_dump, codec_enabled, measure_clock, measure_volts, measure_temp, get_config,
hdmi_ntsc_freqs, render_bar, disk_notify, inuse_notify, sus_suspend, sus_status, sus_is_enabled,
sus_stop_test_thread, egl_platform_switch, mem_validate, mem_oom, mem_reloc_stats, file,
vctest_memmap, vctest_start, vctest_stop, vctest_set, vctest_get"
……
‧ 不識者或許其他論壇中有說明︰
Thu May 12, 2016 11:04 am
Heater wrote:
$ vcgencmd get_throttled
throttled=0x50005
Okay, the bits in this number represent:
0: under-voltage
1: arm frequency capped
2: currently throttled
16: under-voltage has occurred
17: arm frequency capped has occurred
18: throttling has occurred
under-voltage occurs when voltage drops below 4.63V. The Pi is throttled
arm frequency capped occurs with temp > 80’C
over-temperature occurs with temp > 85’C. The Pi is throttled
Throttling removes turbo mode, which reduces core voltage, and sets arm and gpu frequencies to non-turbo value.
Capping just limits the arm frequency (somewhere between 600MHz and 1200MHz) to try to avoid throttling.
If you are throttled and not under-voltage then you can assume over-temperature. (confirm with vcgencmd measure_temp).
So 0x50005 means you are currently under-voltage and throttled.
If you want to be able to support this use case without throttling you will need a better power supply.
Although be aware running a stress test is not typical behaviour. If you never see a non-zero get_throttled value in normal usage, then you may not need to do anything.
此論壇，大部分『設定項』
framebuffer_height=2160
dtparam=eee=off
arm_freq=1200
sdram_freq=450
over_voltage_sdram_p=4
over_voltage_sdram_c=4
over_voltage=2
over_voltage_sdram_i=4
sdram_schmoo=0x01000010
出自
NOTE: Setting any overclocking parameters to values other than those used byraspi-config may set a permanent bit within the SoC, making it possible to detect that your Pi has been overclocked. The specific circumstances where the overclock bit is set are if force_turbo is set to 1 and any of the over_voltage_* options are set to a value > 0. See the blog post on Turbo Mode for more information.
The latest kernel has a cpufreq kernel driver with the “ondemand” governor enabled by default. It has no effect if you have no overclock settings, but if you overclock, the CPU frequency will vary with processor load. Non-default values are only used when required, according to the governor. You can adjust the minimum values with the *_min config options, or disable dynamic clocking (and force overclocking) with force_turbo=1. For more information see here.
Overclocking and overvoltage will be disabled at runtime when the SoC reaches 85°C in order to cool it down. You should not hit this limit on Raspberry Pi models 1 or 2, but it is more likely with the Raspberry Pi 3. For more information see here. Overclocking and overvoltage are also disabled when an undervoltage situation is detected.
文件裡☆
Roy Longbottom’s Raspberry Pi, Pi 2 and Pi 3 Benchmarks
種物品，物品 
的重量是 
，價格為 
。如果我們有個背包，最大能載重 
，要是各種物品只能選或者不選，那麼『最高價』的裝法是什麼？數學上來講，就是在『滿足』
的『條件』下，求
之『最大化』的問題。
![iperf3 -c 192.168.2.222 Connecting to host 192.168.2.222, port 5201 [ 4] local 192.168.2.223 port 58150 connected to 192.168.2.222 port 5201 [ ID] Interval Transfer Bandwidth Retr Cwnd [ 4] 0.00-1.00 sec 34.8 MBytes 292 Mbits/sec 55 105 KBytes [ 4] 1.00-2.00 sec 34.6 MBytes 290 Mbits/sec 60 53.7 KBytes [ 4] 2.00-3.00 sec 35.2 MBytes 295 Mbits/sec 56 38.2 KBytes [ 4] 3.00-4.00 sec 33.5 MBytes 281 Mbits/sec 47 29.7 KBytes [ 4] 4.00-5.00 sec 33.6 MBytes 281 Mbits/sec 37 25.5 KBytes [ 4] 5.00-6.00 sec 31.8 MBytes 267 Mbits/sec 48 147 KBytes [ 4] 6.00-7.00 sec 32.5 MBytes 273 Mbits/sec 50 62.2 KBytes [ 4] 7.00-8.00 sec 34.8 MBytes 292 Mbits/sec 39 96.2 KBytes [ 4] 8.00-9.00 sec 34.4 MBytes 289 Mbits/sec 46 22.6 KBytes [ 4] 9.00-10.00 sec 34.6 MBytes 290 Mbits/sec 48 39.6 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 340 MBytes 285 Mbits/sec 486 sender [ 4] 0.00-10.00 sec 339 MBytes 284 Mbits/sec receiver iperf Done. pi@raspberrypi:~](http://www.freesandal.org/wp-content/ql-cache/quicklatex.com-cad45a36affd3a93884f0a23fbfcc896_l3.png "Rendered by QuickLaTeX.com")
![iperf3 -c 192.168.2.222 Connecting to host 192.168.2.222, port 5201 [ 4] local 192.168.2.223 port 58170 connected to 192.168.2.222 port 5201 [ ID] Interval Transfer Bandwidth Retr Cwnd [ 4] 0.00-1.00 sec 37.6 MBytes 315 Mbits/sec 0 154 KBytes [ 4] 1.00-2.00 sec 37.0 MBytes 311 Mbits/sec 0 154 KBytes [ 4] 2.00-3.00 sec 37.2 MBytes 312 Mbits/sec 0 154 KBytes [ 4] 3.00-4.00 sec 37.0 MBytes 311 Mbits/sec 0 154 KBytes [ 4] 4.00-5.00 sec 37.3 MBytes 313 Mbits/sec 0 154 KBytes [ 4] 5.00-6.00 sec 37.0 MBytes 310 Mbits/sec 0 154 KBytes [ 4] 6.00-7.00 sec 37.4 MBytes 314 Mbits/sec 0 154 KBytes [ 4] 7.00-8.00 sec 36.8 MBytes 309 Mbits/sec 0 154 KBytes [ 4] 8.00-9.00 sec 37.5 MBytes 314 Mbits/sec 0 154 KBytes [ 4] 9.00-10.00 sec 37.1 MBytes 311 Mbits/sec 0 154 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 372 MBytes 312 Mbits/sec 0 sender [ 4] 0.00-10.00 sec 372 MBytes 312 Mbits/sec receiver iperf Done. pi@raspberrypi:~](http://www.freesandal.org/wp-content/ql-cache/quicklatex.com-8fc47f248163e54e25664ab030382b0c_l3.png "Rendered by QuickLaTeX.com")
，最佳選擇
路段要花的時間依賴『車流量』，大概需要 
分鐘，如果選擇先『到 B』 ，一般與『車流量』無關，是『固定的』四十五分鐘，可是 
要花的時間也依賴於『車流量』，時間差不多與『A』相同，也是 
分鐘。因此『理性』考慮『最短時間』，將會是『比較兩者』的『時間差』作選擇的吧？最後達到了『博奕論』Game Theory 所說的『納什均衡』 Nash equilibrium ，此時無論怎麽選擇『所需總時間』是一樣的 
不是比 
要小的嗎？由於 
的吧，到了『B 地』之後，依然還是 
能不是比 
小的嗎？於是乎，所有『非傻鳥』者『必走』 
，或許是 
，結果 
，果真是『傻鳥』的耶！！
vcgencmd get_throttled
throttled=0x0
pi@raspberrypi:~ 
graysky2 commented Mar 30, 2018