search for: net_tx_act

Displaying 11 results from an estimated 11 matches for "net_tx_act".

2002 Mar 06
1
ext3 error messages??
...d see was the following: Mar 6 05:12:31 kanga syslogd 1.4.1: restart. Mar 6 05:12:30 kanga kernel: [ext3:__insmod_ext3_S.bss_L1024+163840/116200300] __insmod_wd_S.bss_L1376 [wd] 0x20 Mar 6 05:12:30 kanga kernel: [<c8842020>] __insmod_wd_S.bss_L1376 [wd] 0x20 Mar 6 05:12:30 kanga kernel: [net_tx_action+142/160] net_tx_action [kernel] 0x8e Mar 6 05:12:30 kanga kernel: [<c01c0e0e>] net_tx_action [kernel] 0x8e Mar 6 05:12:30 kanga kernel: [ext3:__insmod_ext3_S.bss_L1024+163840/116200300] __insmod_wd_S.bss_L1376 [wd] 0x20 Mar 6 05:12:31 kanga kernel: [<c8842020>] __insmod_wd_S.bss_L...
2005 Feb 16
0
Oops in 2.6.8.1 at __journal_drop_transaction
...c8>] __journal_clean_checkpoint_list+0xa8/0xb0 [jbd] [<f88a4958>] journal_commit_transaction+0x2b8/0x1690 [jbd] [<c011e420>] autoremove_wake_function+0x0/0x60 [<c02347ca>] netif_receive_skb+0x1ba/0x230 [<c011e420>] autoremove_wake_function+0x0/0x60 [<c023450a>] net_tx_action+0x5a/0x160 [<c0119f78>] recalc_task_prio+0xa8/0x1a0 [<c029c9b7>] schedule+0x4b7/0x8a0 [<c01296da>] del_timer_sync+0x9a/0xe0 [<f88a8642>] kjournald+0xf2/0x2e0 [jbd] [<c011e420>] autoremove_wake_function+0x0/0x60 [<c011e420>] autoremove_wake_function+0x0/0...
2010 May 31
0
Kernel panic is occured when multi VMs is booting togeter
...6c0 ffff880002cb9f68 ffffffff88478732 ffff88007cf37800 0000000000000036 Call Trace: <IRQ> [<ffffffff88478732>] :netbk:netif_be_start_xmit+0x241/0x471 [<ffffffff8042ac95>] __qdisc_run+0x136/0x1f9 [<ffffffff803ae6cc>] unmask_evtchn+0x2d/0xd7 [<ffffffff8041be2d>] net_tx_action+0xc9/0xf1 [<ffffffff80212c99>] __do_softirq+0x8d/0x13b [<ffffffff80260da4>] call_softirq+0x1c/0x278 [<ffffffff8026e0ab>] do_softirq+0x31/0x98 [<ffffffff8026df37>] do_IRQ+0xec/0xf5 [<ffffffff803af054>] evtchn_do_upcall+0x13b/0x1fb [<ffffffff802608d6>] do_...
2002 Jul 16
1
kernel BUG at commit.c:535 invalid operand
...f956c0 f468b1a0 Jul 16 01:45:34 ETG3 kernel: Call Trace: [<f8865eee>] .rodata.str1.1 [jbd] 0x26e Jul 16 01:45:34 ETG3 kernel: [<c01d8d0c>] kfree_skbmem [kernel] 0xc Jul 16 01:45:34 ETG3 kernel: [<c01d8ea7>] __kfree_skb [kernel] 0x137 Jul 16 01:45:34 ETG3 kernel: [<c01dd0f2>] net_tx_action [kernel] 0x62 Jul 16 01:45:34 ETG3 kernel: [<c0120f3b>] do_softirq [kernel] 0x7b Jul 16 01:45:34 ETG3 kernel: [<c0119048>] schedule [kernel] 0x348 Jul 16 01:45:34 ETG3 kernel: [<f88617d6>] kjournald [jbd] 0x136 Jul 16 01:45:34 ETG3 kernel: [<f8861680>] commit_timeout [jbd...
2018 Nov 13
0
centos 7.5 crashed, kernel BUG at net/core/skbuff.c:3668!
...4bf>] start_xmit+0x19f/0x500 [virtio_net] [ 728.985925] [<ffffffffae7f02e6>] dev_hard_start_xmit+0x246/0x3b0 [ 728.986741] [<ffffffffae81bc0a>] sch_direct_xmit+0x11a/0x250 [ 728.987489] [<ffffffffae81bdce>] __qdisc_run+0x8e/0x360 [ 728.988182] [<ffffffffae7ef3e6>] net_tx_action+0x1d6/0x240 [ 728.988924] [<ffffffffae29dba5>] __do_softirq+0xf5/0x280 [ 728.989634] [<ffffffffae928cec>] call_softirq+0x1c/0x30 [ 728.990322] [<ffffffffae22e625>] do_softirq+0x65/0xa0 [ 728.990994] [<ffffffffae29df25>] irq_exit+0x105/0x110 [ 728.991680] [<ff...
2011 Feb 02
6
Backtrace in xen/next-2.6.38 when running guest
...ack] [<ffffffff8102abf9>] ? pvclock_clocksource_read+0x48/0xb7 [<ffffffff81006a3a>] ? xen_vcpuop_set_next_event+0x51/0x63 [<ffffffff8107a4a3>] ? clockevents_program_event+0x8e/0x90 [<ffffffff8107b4b7>] ? tick_dev_program_event+0x36/0xf3 [<ffffffffa022cd97>] ? net_tx_action+0x1e/0x590 [xen_netback] [<ffffffff8105a1ed>] ? arch_local_irq_restore+0xb/0xd [<ffffffff810066d5>] ? xen_force_evtchn_callback+0xd/0xf [<ffffffff81006c72>] ? check_events+0x12/0x20 [<ffffffff8105a6d5>] ? tasklet_action+0x7f/0xd2 [<ffffffff8105b090>] ? __d...
2003 Jun 09
7
Dual T400P, SMP, performance issues
Hi, We are trying to validate Asterisk as a media gateway PRI <-> SIP with two T400P (8 T1s) per box. The first experience with BOX1 (Compaq, 2.53 GHz, 1 Gb RAM) and just one T400P was encouraging - on the load test with 3 T1s worth of calls we had on average 75% idle CPU. Not so with BOX2 (Dell, single 2.6 GHz Xeon, 1 Gb RAM, 2 T400P) and BOX3 (Dell, dual 2.6 GHz Xeon, 2 Gb RAM, 2 T400P,
2007 Apr 18
4
[Bridge] [PATCH/RFC] Let {ip, arp}tables "see" bridged VLAN tagged {I, AR}P packets
...it vlan_cleanup_devices( } } rtnl_unlock(); +#ifdef CONFIG_BRIDGE_NETFILTER + vlan_dev_hard_start_xmit_p = NULL; +#endif } /* --- linux-2.6.0-test6/net/core/dev.c Sun Sep 28 02:50:20 2003 +++ linux-2.6.0-test6-new/net/core/dev.c Sun Oct 5 21:56:15 2003 @@ -1489,6 +1489,14 @@ static void net_tx_action(struct softirq } #if defined(CONFIG_BRIDGE) || defined (CONFIG_BRIDGE_MODULE) + +#if defined(CONFIG_VLAN_8021Q) || defined(CONFIG_VLAN_8021Q_MODULE) +#ifdef CONFIG_BRIDGE_NETFILTER +/* net/bridge/br_netfilter.c needs the address of vlan_dev_hard_start_xmit */ +int (*vlan_dev_hard_start_xmit_...
2007 Mar 20
62
RFC: [0/2] Remove netloop by lazy copying in netback
Hi Keir: These two patches remove the need for netloop by performing the copying in netback and only if it is necessary. The rationale is that most packets will be processed without delay allowing them to be freed without copying at all. So instead of copying every packet destined to dom0 we''ll only copy those that linger longer than a specified amount of time (currently 0.5s). As it
2013 Feb 01
45
netback Oops then xenwatch stuck in D state
We''ve been hitting the following issue on a variety of hosts and recent Xen/dom0 version combinations. Here''s an excerpt from our latest: Xen: 4.1.4 (xenbits @ 23432) Dom0: 3.7.1-x86_64 BUG: unable to handle kernel NULL pointer dereference at 000000000000001c IP: [<ffffffff8141a301>] evtchn_from_irq+0x11/0x40 PGD 0 Oops: 0000 [#1] SMP Modules linked in: ebt_comment
2010 Aug 21
24
Freeze with 2.6.32.19 and xen-4.0.1rc5
Hi, i have big trouble with a Debian Lenny dom0 and latest kernel 2.6.32.19 with xen-4.0.1rc5. Due some reason the system freezes from time to time. I used kernel 2.6.31.9 with xen-3.4.2 before. The machine doesn''t write anything to serial console so there are no errors or something like that. Perhaps there is something to see from the logs ... Hardware Board: Intel DQ45CB CPU: