Hi Timmothy, thanks for the tip! ;-) I think I found it: => https://forum.ipfire.org/viewtopic.php?f=17&t=17195&p=100915#p100914 Bug reported: https://bugzilla.ipfire.org/show_bug.cgi?id=11192 Best, Matthias On 23.09.2016 21:31, IT Superhack wrote: > Hello Matthias, > > there are some complaints about kernel errors in this forum branch: > http://forum.ipfire.org/viewtopic.php?f=17&t=17195&p=100655 > > Some of them look quite similar to those you encountered. > > Personally, I cannot confirm this on my IPFire machine (ARM board > with 32GB SD card), but maybe the error only occurs if a "real" HDD > is in use. > > Best regards, > Timmothy Wilson > > Matthias Fischer: >> Hi list, >> >> I'm experiencing an interesting problem here: >> >> *Exactly* after rebooting after upgrading to Core 104, which worked >> without any problems, I find that I got a lot of kernel errors: >> >> ... >> 21:50:22 kernel: REJECT_FORWARD IN=green0 OUT=red0 MAC=00:02:b3:1a:b0:96:00:07:e9:40:b8:29:08:00 SRC=192.168.100.1 DST=192.168.100.254 LEN=52 TOS=0x00 PREC=0x00 TTL=127 ID=17075 DF PROTO=TCP SPT=50633 DPT=444 WINDOW=8192 RES=0x00 SYN URGP=0 >> 21:50:32 kernel: Kernel logging (proc) stopped. >> 21:50:32 kernel: Kernel log daemon terminating. >> 21:52:40 kernel: IPv6: ADDRCONF(NETDEV_UP): green0: link is not ready >> 21:52:40 kernel: e100 0000:00:03.0 green0: NIC Link is Up 100 Mbps Full Duplex >> 21:52:41 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): green0: link becomes ready >> 21:52:41 kernel: IPv6: ADDRCONF(NETDEV_UP): red0: link is not ready >> 21:52:41 kernel: e100 0000:00:06.0 red0: NIC Link is Up 100 Mbps Full Duplex >> 21:52:41 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): red0: link becomes ready >> 21:54:01 kernel: perf samples too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 50100 >> 21:55:01 kernel: sd 1:0:0:0: [sda] Unhandled error code >> 21:55:01 kernel: sd 1:0:0:0: [sda] >> 21:55:01 kernel: Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK >> 21:55:01 kernel: sd 1:0:0:0: [sda] CDB: >> 21:55:01 kernel: ATA command pass through(16): 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 >> 21:55:01 kernel: sd 1:0:0:0: [sda] Unhandled error code >> 21:55:01 kernel: sd 1:0:0:0: [sda] >> 21:55:01 kernel: Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK >> 21:55:01 kernel: sd 1:0:0:0: [sda] CDB: >> 21:55:01 kernel: ATA command pass through(16): 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 >> ... >> >> Profile: >> http://fireinfo.ipfire.org/profile/63d7b5d45f8a7816ca68810ed0061d7ff95a9958 >> >> Nothing was changed, I tested the drive including cables => no problems: >> >> ***SNIP*** >> root(a)ipfire: / # smartctl -a /dev/sda >> smartctl 6.5 2016-05-07 r4318 [i686-linux-3.14.79-ipfire-pae] (IPFire 2.19) >> Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org >> >> === START OF INFORMATION SECTION === >> Vendor: IBM >> Product: DDYS-T36950M >> Revision: S96H >> User Capacity: 36,703,918,080 bytes [36.7 GB] >> Logical block size: 512 bytes >> Rotation Rate: 10000 rpm >> Logical Unit id: 0x5005076707c1df6e >> Serial number: 4FY3P734 >> Device type: disk >> Transport protocol: Fibre channel (FCP-2) >> Local Time is: Fri Sep 23 18:46:45 2016 CEST >> SMART support is: Available - device has SMART capability. >> SMART support is: Enabled >> Temperature Warning: Enabled >> >> === START OF READ SMART DATA SECTION === >> SMART Health Status: OK >> >> Current Drive Temperature: 42 C >> Drive Trip Temperature: 85 C >> >> Manufactured in week 46 of year 2001 >> Specified cycle count over device lifetime: 10000 >> Accumulated start-stop cycles: 139 >> Elements in grown defect list: 2 >> >> Error counter log: >> Errors Corrected by Total Correction Gigabytes Total >> ECC rereads/ errors algorithm processed uncorrected >> fast | delayed rewrites corrected invocations [10^9 bytes] errors >> read: 0 0 0 3 3 2490.529 0 >> write: 0 2 0 16 16 1534.193 0 >> verify: 0 0 0 0 0 73.408 0 >> >> Non-medium error count: 0 >> ***SNAP*** >> >> What puzzles me is the fact that these errors first *occur right after rebooting with Core104*, >> but *never* before, all hardware is running and seems to be ok. No Panic, no crash, nothing, >> just these kernel errors since upgrading. >> >> Does anyone have an idea? >> >> Best, >> Matthias >> > >