What The Fur review

上次 FE 展后回顾所列的愿望：
Wishlist from Further Equinox’s review:

Some things to improve next con: take more photos, post more on Twitter, practice fursuit movements before con, mingle with non-fursuiters more, drink more water, and DON’T STAY IN FURSUIT for all of the dance competition.
下次去兽展，希望能: 拍更多的照片、发更多的推、走之前练习兽装动作、和非兽装穿着者互动更多、喝更多的水、还有不要整个舞蹈比赛都穿着兽装。

  • 拍照片——大约200张，其中64张能看的。 FE: 150张
    Photos — about 200, 64 of which looks okay. FE: 150
  • 发推——两次
    Tweeting – twice
  • 练习……根本没有时间啊
    Practising… no time!
  • 更多互动——缺乏，一穿了兽装就坐不下来，更不要说什么谈话或画图之类的事情了。
    More interaction — lacking. Once I put on fursuit, it’s impossible to sit down and stay put, let alone anything like chat or doodling!
  • 喝水——穿兽装每半小时休息，喝一杯水。所以，这次没有头疼，没有感冒，也没有展会综合征／水土不服之类的事情。
    Drink — break between every half an hour, and drink a glass of water. So no headaches, no flu, and no con crud this year!

I’m still disappointed that at fur cons, people stay up late and sleep in, so there aren’t much stuff happening in the mornings.
对于兽展大家都晚起晚睡这一点，我还是很失望。这样早晨起来就几乎没有什么事情可以做。

This year What The Fur has moved to Delta Centre-ville. The bad is it’s a large, expensive hotel, so there are many other guests staying. Also, the convention floor is underground and completely lacking in natural light, so photography is hard. The good is that the convention floor is spacious, and has a hub-and-spoke arrangement, so it’s easy to find and mingle with people. Also, there are many other guests staying, including families, tourists, and engineering students here for the annual concrete canoe competition (seriously)!
今年What The Fur 移动到了Delta Centre-ville. 不好的地方是这是个大型酒店，价格不菲，其他宾客也很多。另外，整个会议中心在地下二层，完全没有自然光，所以照相难。好处是会议中心面积很大，并且呈放射性排列，所以很容易和大家打成一片。另外，其他宾客也很多，包括家庭、游客、以及来这里参加每年的混凝土划艇比赛的工程系学生们 (真的) !

（How spacious is the convention floor? Every year in January, the very same hotel plays host to CUSEC, the Canadian University Software Engineering Conference. This year, 12 universities in Canada have have sent delegations, each having about a bus full of attendees. And 18 organizations set up tables at the career fair after lunches.
会议中心有多大？每年一月，CUSEC ——加拿大大学软件工程会议——在该酒店举办。今年 12 个大学派了代表团来，每个至少坐满了一车。午饭后的招聘会，有18个组织设展位。

I went to CUSEC this year. It’s actually kind of weird to come to the same convention space for a completely different convention.
我今年也参加了CUSEC. 在同一个会场参加完全不同的展会感觉好奇怪。）

Furnal Equinox epilude

*用语有误请多指教，一向作文不好……

And I’ve finally got around to say something about the first Furry Convention I’ve been to in almost a year and a half! (Not for lack of trying, though.) My last convention was Condition:Red in 2011, and after that I’ve been to several local anime conventions, and they have very awesome people as well, but it’s just not the same…
自2011年的Condition：Red之后一年半没有去过兽展之后(动漫展虽然强人很多，但是毕竟不一样)按耐不住决定去了多伦多的Furnal Equinox。今天终于有机会写一下回顾了。

Unfortunately I had a cold that week, so I couldn’t be fursuiting on Friday. That said I took the time to take some photos, which are on Flickr if you haven’t seen them! And also this time I finally got to hear one of Nuka-kitty‘s lectures sessions panels on furry psychology in full. Because SCIENCE! And of course the improv night was hilarious, especially with Nuka in fursuit. Almost braved and went in fursuit too, but I decided to make sure not to overexert myself.
不行的是去之前感冒了，所以周五没有机会穿兽装。不过趁这个机会照了些照片，传到了Flickr上，没看的话赶快去看。 （很抱歉，Flickr在大陆不能正常访问。）另外，终于能够从头到尾地听一次Nuka 的兽控心理学讲座了。(国内动漫展好像没有讲座的样子?)科学万岁！还有晚上的即兴表演，笑翻天笑死人不偿命～特别是当Nuka穿兽装上去的时候!

(今年第二次感冒参加展会了，怎么回事啊。）
（Second time to a con with a flu this year, why… just why?)

Woke to an early start on Saturday and fursuited as much as I can. The sponsor pizza party was cool, although the first batch of pizza was a bit stale (later batches are fine) and I can’t decide which table to sit at. Did a little fursuit dance then went to bed.
周六早晨提早起床，尽可能地多穿兽装。升级到赞助者级别彻底发挥作用了:早饭是赞助者休息室的火鸡三明治，午饭是赞助者休息室的火鸡三明治，晚上是赞助者休息室的匹萨派对……不过第一批匹萨有点潮了(后面几批都没问题). 晚上稍微跳了一下舞就睡觉了。

On Sunday I went to watch the dance competition. I could still hardly believe that this is the first time Furnal Equinox hosted a dance competition, and the first time almost all the contestants are participating! (And almost all of them didn’t sleep or eat much…) All 9 of them are full of energy and rhythm, and their performance are very fun to watch, as well as full of surprises! Especially the first place :snapback:, who built their own suit and is just as adorable as an otter can ever be; yet on the dance floor, she is a force to be reckoned with. Kudos to all the participants – the Original Nine Crew!
周日早晨去观看了舞蹈比赛。记忆已经模糊，但忘不了的是参赛的九位兽装穿着者，每个都那么充满了活力和激情。真不能想象这都是他们第一次参加舞蹈比赛 (而且大多都没吃饭没睡觉)，也不能想象这是第一次 FE 举办舞蹈比赛……特别要提一下的是第一名 Snapback, 平常是再可爱不过的小水獭，一到舞池就成为一股不可抗拒的力量。而且ta的兽装是自己做的，这家伙有多厉害?!这里再次对所有参赛者致敬!

The con wasn’t as exciting as I thought, as a whole, and perhaps it’s because the novelty has worn off, or perhaps because I was too worried about school; but nevertheless it was full of highlights!
总体来说这次兽展没有像想象当中的那么刺激，也许是新奇感已经退去，也许是太担心学习；但是仍然有许多精彩的瞬间，值得回忆……

A lot of time was spent at the sponsor lounge eating and mingling. Food at the sponsor lounge is simple, but the turkey sandwich was okay and at least I didn’t go hungry. But I did not eat much and moved a lot, so I lost a kilogram (2-3 pounds) during the convention. It would have been even better to have someone to go together to Tim Hortons for breakfast, but I don’t know any people who sleep and wake early at fur cons…
这次到FE, 很多时间在赞助者休息室吃东西聊天。休息室供应的食品很简单，但是火鸡三明治还凑合，至少没饿着肚子。不过我吃的不多，动得很多，所以整个兽展瘦了一公斤。如果早晨有人能陪我一起去 Tim Hortons 吃早饭就好了，不过我不认识谁在兽展那么早就起床的……

(题外话:2011年去AC的时候每天早晨卡库尔第一个醒来，吃完早饭带回房间一盒子甜甜圈。）
(Off topic: At Anthrocon 2011, I’m always the first to rise, and bring a box of donuts to the room after breakfast.)

There are a couple people I thought I would see but didn’t, like :linkbattykoha: and :linkErisValgen:, and some people I expected to see like :linkAmico: and :linkblondiepup:, some I didn’t expect to see like Zanni (:linktherian:). Some people I just get excited to finally see in the fur like :linkflowkitty:. And then there are new faces like Kelsey (karlounichou) (finally I get to see a :iconKalamari: fursuit in meatspace!) and :snapback: of course!
有几个人想见到没有见到，例如 battykoha 和 erisvalgen，但还是见到了Amico 和 blondiepup，以及没有预料到能见到的像是 Zanni. 有些终于能亲眼见到，例如 Flow, 以及新面孔，像是Kelsey和Snapback!

Some things to improve next con: take more photos, post more on Twitter, practice fursuit movements before con, mingle with non-fursuiters more,  drink more water, and DON’T STAY IN FURSUIT for all of the dance competition. (I was dehydrated on Sunday and came back home with a headache! Buying a sport drink at the bus rest stop helped, though.) A final regret is haven’t bought the “Blueper” hand puppet. (Practically 20% off if you figure in shipping!)
下次去兽展，希望能: 拍更多的照片、发更多的推、走之前练习兽装动作、和非兽装穿着者互动更多、喝更多的水、还有不要整个舞蹈比赛都穿着兽装。 (周日走的时候严重脱水, 头痛！ 乘车停下来的时候买了瓶运动饮料好像对此有一些作用。)最后的遗憾是没有决定买下 “Blueper” 手偶. （加上送货费相当于打八折!)

A shout out to :icondizzywizzy: for running the sponsor’s lounge, :iconskyr3der: for organizing the dancing competition, and :iconolefin: for the con videos, as well as thanks for rest of the staff and attendees! Another to my roommates :linkdarkysabretooth: :linkspikekitty69: :linkGozob:. And finally another round of applause to :iconSnapback:, you’re the most awesome ever!
感谢Wizzy看管赞助者休息室、Ronnie组织舞蹈大赛、Olefin录像、以及Furnal Equinox的所有其他工作人员和参加者！ 还有我的室友们 Darky, Spike 和 Garou! 最后请为 Snapback 热烈鼓掌——你是最棒的!

 

Oh yes and :linkPazzix:! Long time no see!

The Reboot Loops of Galaxy Nexus

Last night when I was eating out with friends, my phone (Samsung Galaxy Nexus) restarted itself during use. Since it has been doing that for a while, I didn’t think too much of it. But on my way back home I noticed the phone would restart after just a few minutes of usage, sometimes even stuck in a “reboot loop” where it would restart before the boot sequence is completed.
昨天晚上和朋友出去吃饭的时候我的电话 (三星Galaxy Nexus) 用到一半自己重新启动了。因为这样子不止是一天两天了，也就没在意。但是回家的时候手机开始用几分钟就重新启动一次，有时候甚至会不停重启。

After searching for similar occurrences, several attempts to reproduce the problem (under the assumption of a misbehaving app), and detours involving safe mode and recovery mode, I noticed in a forum post about Galaxy Nexus tips on xda-developers mentioned finding and posting LAST_KMSG (the Linux kernel message log from last boot) for trouble shooting. Since I already had Android SDK installed, I pulled the message log using adb. Normal apps shouldn’t trigger reboots, so the kernel log will likely offer more clues as to where the problem is.
搜索相似情况之后，找了多次哪个程序是罪魁祸首之后，数次切换安全模式之后，我注意到 xda-developers 论坛上一条置顶消息中提到哪里可以找到 LAST_KMSG (Linux 内核最后一次启动时的消息日志)。因为我正好已经安装了 Android 软件开发包 ，我用了 adb 从设备上取得了消息日志。

Caution: Saving the log (or full device backup or bug report) in the same directory as adb and then updating Android SDK, may delete your saved log (or backup)! It’s good to backup, but save your backup somewhere else.
注意： 将消息日志(或错误报告，或设备备份)保存在 adb 所在的目录之后更新 Android 软件开发包，可能会删除你保存的内容！ 备份是好事，但是请保存在别的地方。

While at first I was misled by the “no errors detected” message at the end, as well as the stack trace there, soon I understood that the problem has to do with not able to write internal storage leading to file system not able to maintain consistency, causing the reboot:
一开始被最后面的 “没有检测到错误” 消息和呼叫记录搞糊涂了的我，不久就发现实际的问题是设备无法写入内部存储空间，导致文件系统不能保证一致性，最后设备重启：

[   77.674102] mmcblk0: timed out sending r/w cmd command, card status 0x900
[   77.674316] mmcblk0: not retrying timeout
[   77.674621] end_request: I/O error, dev mmcblk0, sector 2391056
[   77.675018] Aborting journal on device mmcblk0p12-8.
[   78.695343] journal commit I/O error
[   78.695648] journal commit I/O error
[   78.752777] EXT4-fs error (device mmcblk0p12): ext4_journal_start_sb:296: Detected aborted journal
[   78.753051] EXT4-fs (mmcblk0p12): Remounting filesystem read-only
[   78.754119] Kernel panic - not syncing: EXT4-fs panic from previous error
[   78.754119] 
[   78.754272] Backtrace: 
[   78.754425] [] (dump_backtrace+0x0/0x10c) from [] (dump_stack+0x18/0x1c)
[   78.754516]  r6:c060fe88 r5:00000000 r4:c084e480 r3:00000000
[   78.754852] [] (dump_stack+0x0/0x1c) from [] (panic+0x80/0x1b0)
[   78.754943] [] (panic+0x0/0x1b0) from [] (__ext4_abort+0xd8/0xec)
[   78.755035]  r3:88020840 r2:00000000 r1:c4e7fc2c r0:c0759830
[   78.755340]  r7:c4e7e000
[   78.755462] [] (__ext4_abort+0x4/0xec) from [] (ext4_journal_start_sb+0x84/0x128)
[   78.755584]  r6:00000003 r5:c715fc00 r4:c7229e00
[   78.755798] [] (ext4_journal_start_sb+0x0/0x128) from [] (ext4_setattr+0x2b4/0x43c)
[   78.755920]  r8:00000000 r7:0000a068 r6:0000a068 r5:c4e7fdd8 r4:c76e5670
[   78.756256] [] (ext4_setattr+0x0/0x43c) from [] (notify_change+0x11c/0x2c4)
[   78.756347] [] (notify_change+0x0/0x2c4) from [] (do_truncate+0x7c/0x98)
[   78.756469] [] (do_truncate+0x0/0x98) from [] (do_last.isra.31+0x528/0x6a0)
[   78.756622]  r5:c4ea71e0 r4:c4e7fed8
[   78.756805] [] (do_last.isra.31+0x0/0x6a0) from [] (path_openat+0xc0/0x3ac)
[   78.756896] [] (path_openat+0x0/0x3ac) from [] (do_filp_open+0x34/0x88)
[   78.757019] [] (do_filp_open+0x0/0x88) from [] (do_sys_open+0xe4/0x17c)
[   78.757080]  r7:00000001 r6:00000017 r5:00020242 r4:c2a2c000
[   78.757385] [] (do_sys_open+0x0/0x17c) from [] (sys_open+0x28/0x2c)
[   78.757476] [] (sys_open+0x0/0x2c) from [] (ret_fast_syscall+0x0/0x30)
[   78.757568] CPU1: stopping
[   78.757629] Backtrace: 
[   78.757812] [] (dump_backtrace+0x0/0x10c) from [] (dump_stack+0x18/0x1c)
[   78.757873]  r6:c004f090 r5:c65fa000 r4:c07f9550 r3:00000000
[   78.758209] [] (dump_stack+0x0/0x1c) from [] (do_IPI+0x1c8/0x1fc)
[   78.758300] [] (do_IPI+0x0/0x1fc) from [] (__irq_usr+0x48/0xe0)
[   78.758361] Exception stack(0xc65fbfb0 to 0xc65fbff8)
[   78.758483] bfa0:                                     40c32928 40c308d0 00000001 00000000
[   78.758544] bfc0: 407c31a8 40cf3ad8 407c31a8 40c308d0 00013392 7fffffff 00013393 00000001
[   78.758666] bfe0: 514bd078 beac3960 407509f4 407508c4 80000010 ffffffff
[   78.758758] Rebooting in 5 seconds..
[   83.039154] Restarting Linux version 3.0.31-g6fb96c9 (android-build@vpbs1.mtv.corp.google.com) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Thu Jun 28 11:02:39 PDT 2012
[   83.039184] 

No errors detected
Boot info:
Last reset was warm software reset (PRM_RSTST=0x2)

(A “kernel panic” is the Linux equivalent of Windows “Stop Error” or “Bluescreen”/“BSoD”, where the operating system kernel has encountered a fault it’s not able to recover from. It’s usually caused by faulty hardware or drivers.
Linux的 “内核错误” 相当于 Windows 的 “蓝屏死机”，都是操作系统内核遇到了无法恢复的错误的情况。一般原因是硬件故障或是驱动程序有问题。 (Panic 是 “抓狂” 的意思。))

Since I can’t replace the internal storage, I sent it back to the carrier (Wind Mobile) today for repairs. It should take up to three weeks for (in-warranty) repair. (Unlike Dell’s out-of-warranty repair, which returned the computer in only one week!) The store rented me a LG Optimus 2X for $10, which is a pretty cool phone actually.
既然不能更换集成的闪存，最后只能今天送修。修理手机 (保修期内) 大概要三个星期。 (不像戴尔的保修期外修理……一个星期就退回来了！) 零售店$10租给我了一个LG Optimus 2X，算是个挺酷的手机呢。

This isn’t the first time I had a problem with failing storage. Back when my Nexus One still had a working power button, the memory card corrupted, leading to some interesting pictures. And my XPS laptop went through two failed hard drives.
这不是第一次遇到存储出问题的事情了。以前我的 Nexus One 还能开机的时候，SD卡出了问题，产生了几张“很有意思”的照片。而我的XPS笔记本电脑上硬盘也换了两次。

Considering the underlying causes of the reboot, the general advice (and my first reflex) of resetting the device would likely only result in temporary relief.
考虑到不断重启的根本原因，一般对这种情况的重置设备的建议 (也是我的第一反应) 可能只会带来一时的缓解，而不会解决真正问题吧。

This still leaves two other questions. Even though I only had the device for 4 months, it can take a long time for apps to respond, especially with Google Search. I always thought it may be because beginning in Android 4+, user-accessible data is stored together with system files and data, but could it have been a sign that the storage is failing? Also, would a file system check help any in this occasion?
最后还有两个疑问。虽然这个手机只用了四个月，应用程序经常要等好长时间才反应，特别是 Google 搜索特别慢。我一直觉得这可能是因为 Android 4+ 将用户可见的数据和系统文件放在一起，但是会不会实际上是闪存问题的前兆呢？另外，文件系统查错会不会对这种情况有任何帮助呢？

Need help: Fursuiter + Bedbug problems (again)

So I came back home to find a slip of paper under my door, informing my house will be steamed because of a bedbug problem. I had an experience with a bedbug infestation two years ago, and it was an ordeal. The landlord called someone to apply insecticides, but bedbugs are highly resilient creatures, and seems like they have been found somewhere else in the building. So this time, they are applying hot steam to the house, which is the sure fire way to eliminate bedbugs, because they cannot survive the heat. For this reason, all the clothes have to be dried on high heat as well.

Which poses a problem for fursuits, as the fake fur and foam can be badly damaged by the high heat. So, what should I do to clean the fursuit, and is it necessary? What I plan to do now is put the fursuit in a bag and shelf it before I find a way, but that’s only a stopgap measure before I find a treatment.

I’m also worried about my other stuff, like electronics, two shelves of books, plushies, and a self-inflating mattress. Any advice will be grately appreciated.

The house is set to be steamed on Wednesday and we just got the notice today. Which means I have tomorrow to dry every clothing I have, including the ones that aren’t to be dried. It’s also the week for midterms; I have two, and a chemistry lab to prepare for. To top it off, I lost a fursuit handpaw on the bus and has to check the lost and found. So good.