On Nov 20, 2014, at 3:07 AM, Michael Keuter <li...@mksolutions.info> wrote:
> > Am 20.11.2014 um 06:45 schrieb Michael Knill > <michael.kn...@ipcsolutions.com.au>: > >> I got this in the logs today. Is it bad? >> >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: ------------[ cut here >> ]------------ >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: WARNING: at >> kernel/softirq.c:159 local_bh_enable+0x32/0x81() >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: Hardware name: >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: Modules linked in: tun >> sch_sfq sch_htb xt_dscp xt_CLASSIFY xt_length xt_tcpudp ipt_MASQUERADE >> nf_nat_ftp iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_TCPMSS >> ipt_LOG ipt_REJECT iptable_mangle xt_multiport xt_state xt_l >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: Pid: 26493, comm: >> telnet Tainted: G O 3.2.62-astlinux #1 >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: Call Trace: >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<c1029614>] >> warn_slowpath_common+0x65/0x7a >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<c102da95>] ? >> local_bh_enable+0x32/0x81 >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<c1029638>] >> warn_slowpath_null+0xf/0x13 >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<c102da95>] >> local_bh_enable+0x32/0x81 >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<c121de31>] >> skb_checksum+0xff/0x205 >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<c12266f4>] >> skb_checksum_help+0x56/0xe9 >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<f82992b0>] >> rtl8168_hw_disable_mac_mcu_bps+0x33466/0x37916 [r8168] >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<c1226af8>] >> dev_hard_start_xmit+0x371/0x44b >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<c1236518>] >> sch_direct_xmit+0x55/0x141 >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<c1226e9e>] >> dev_queue_xmit+0x2cc/0x46a >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<c123ed00>] ? >> nf_ct_attach+0x25/0x30 >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<c1248796>] >> ip_finish_output+0x22d/0x275 >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<c1248871>] >> ip_output+0x93/0x9a >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<c1247ca5>] >> ip_local_out+0x1b/0x1e >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<c124819a>] >> ip_queue_xmit+0x2b6/0x306 >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<c1258066>] >> tcp_transmit_skb+0x6c0/0x6f7 >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<c125a249>] >> tcp_write_xmit+0x778/0x872 >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<c125a387>] >> __tcp_push_pending_frames+0x18/0x6f >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<c124f832>] >> tcp_sendmsg+0x832/0x91f >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<c1268682>] >> inet_sendmsg+0x77/0x80 >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<c1218683>] >> sock_aio_write+0xe8/0xf1 >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<c1022ec8>] ? >> get_parent_ip+0xb/0x31 >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<c1082aae>] >> do_sync_write+0x94/0xcf >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<c115bd4a>] ? >> tty_ldisc_deref+0x8/0xa >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<c1083308>] >> vfs_write+0x9a/0x102 >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<c1083407>] >> sys_write+0x3b/0x60 >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<c129b605>] >> syscall_call+0x7/0x7 >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: [<c1290000>] ? >> pci_fixup_video+0x30/0x8f >> Nov 20 14:58:18 4010-Breeze_HO-CM1 user.warn kernel: ---[ end trace >> 483286c9d7e3c9f1 ]--- >> >> Its a Jetway NF96FL-525. >> >> Regards >> Michael Knill > > Hi Michael, > > which AstLinux version are using, I had a similar problem with the latest > Realtek 8.039 drivers included in AstLinux 1.2.0, so we went down to 8.038 in > the upcoming 1.2.1 version. > It's available already on the build page. In my case the error appeared only > once some time (a few hours) after a reboot. > > Michael I concur with Michael, though this was a very rare occurrence as I wasn't able to reproduce the kernel oops with any of my r8168 NIC's... including the same Jetway board model number as Michael had issue with. Unlike the Intel kernel drivers with comprehensive change-logs and such, the Realtek kernel driver has no versioning info whatsoever. As Michael suggested, the SVN version uses Realtek 8.038, and a current SVN build should be solid for production use. Lonnie ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
