Bug 767110 - Kernel: WARNING: at kernel/sched.c:5915 thread_return
Summary: Kernel: WARNING: at kernel/sched.c:5915 thread_return
Keywords:
Status: CLOSED DUPLICATE of bug 766051
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.2
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Red Hat Kernel Manager
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-13 09:48 UTC by Liang Zheng
Modified: 2013-01-11 01:56 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-13 12:05:35 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Liang Zheng 2011-12-13 09:48:50 UTC
Description of problem:
When I ifup a bnx2x NIC ,found fan failure,then the kernel print the warning trace.
[root@hp-dl585g7-02 ~]# ifup eth4
bnx2x 0000:08:00.0: firmware: requesting bnx2x/bnx2x-e1h-7.0.23.0.fw
bnx2x 0000:08:00.0: eth4: Warning: PHY was not initialized, Port 0
bnx2x 0000:08:00.0: eth4: using MSI-X  IRQs: sp 93  fp[0] 95 ... fp[14] 125
[bnx2x_attn_int_deasserted0:3341(eth4)]SPIO5 hw attention
[bnx2x_attn_int_deasserted0:3341(eth4)]SPIO5 hw attention
bnx2x 0000:08:00.0: eth4: Fan Failure on Network Controller has caused the driver to shutdown the card to prevent permanent damage.  Please contact OEM Support for assistance
bnx2x 0000:08:00.0: eth4: Fan Failure on Network Controller has caused the driver to shutdown the card to prevent permanent damage.  Please contact OEM Support for assistance
ADDRCONF(NETDEV_UP): eth4: link is not ready

Version-Release number of selected component (if applicable):
kernel 2.6.32-223.el6

How reproducible:
N/A

Steps to Reproduce:
1.
2.
3.
  
Actual results:
[root@hp-dl585g7-02 ~]# ------------[ cut here ]------------
WARNING: at kernel/sched.c:5915 thread_return+0x232/0x79d() (Tainted: G           ---------------- T)
Hardware name: ProLiant DL585 G7
Modules linked in: bnx2x libcrc32c mdio autofs4 sunrpc ipv6 bna(T) cxgb4 power_meter hpwdt hpilo microcode netxen_nic serio_raw k10temp amd64_edac_mod edac_core edac_mce_amd i2c_piix4 sg shpchp ext4 mbcache jbd2 sd_mod crc_t10dif sr_mod cdrom hpsa ata_generic pata_acpi pata_atiixp ahci radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core dm_mirror dm_region_hash dm_log dm_mod [last unloaded: mdio]
Pid: 6873, comm: matahari-qmf-ho Tainted: G           ---------------- T 2.6.32-223.el6.x86_64 #1
Call Trace:
 [<ffffffff81069997>] ? warn_slowpath_common+0x87/0xc0
 [<ffffffff810699ea>] ? warn_slowpath_null+0x1a/0x20
 [<ffffffff814ecbd5>] ? thread_return+0x232/0x79d
 [<ffffffff810958e3>] ? __hrtimer_start_range_ns+0x1a3/0x460
 [<ffffffff81094dc1>] ? lock_hrtimer_base+0x31/0x60
 [<ffffffff814ee3a8>] ? schedule_hrtimeout_range+0xc8/0x160
 [<ffffffff81094b70>] ? hrtimer_wakeup+0x0/0x30
 [<ffffffff81095bd4>] ? hrtimer_start_range_ns+0x14/0x20
 [<ffffffff8118b079>] ? poll_schedule_timeout+0x39/0x60
 [<ffffffff8118bdcb>] ? do_sys_poll+0x45b/0x520
 [<ffffffff8118b820>] ? __pollwait+0x0/0xf0
 [<ffffffff81275266>] ? vsnprintf+0x2b6/0x5f0
 [<ffffffff81198988>] ? seq_printf+0x58/0x90
 [<ffffffff811e3069>] ? proc_pid_status+0x5a9/0x600
 [<ffffffff81061c15>] ? enqueue_entity+0x125/0x420
 [<ffffffff8102fd8e>] ? physflat_send_IPI_mask+0xe/0x10
 [<ffffffff8102a1d9>] ? native_smp_send_reschedule+0x49/0x60
 [<ffffffff8104d768>] ? resched_task+0x68/0x80
 [<ffffffff8104d80d>] ? check_preempt_curr+0x6d/0x90
 [<ffffffff8105e782>] ? default_wake_function+0x12/0x20
 [<ffffffff8104c969>] ? __wake_up_common+0x59/0x90
 [<ffffffff81012b59>] ? read_tsc+0x9/0x20
 [<ffffffff8109b629>] ? ktime_get_ts+0xa9/0xe0
 [<ffffffff8118b02d>] ? poll_select_set_timeout+0x8d/0xa0
 [<ffffffff8118c08c>] ? sys_poll+0x7c/0x110
 [<ffffffff8100b0f2>] ? system_call_fastpath+0x16/0x1b
---[ end trace 6e16fe51c77568d9 ]---
Bridge firewalling registered


Expected results:


Additional info:

Comment 1 Larry Woodman 2011-12-13 12:05:35 UTC

*** This bug has been marked as a duplicate of bug 766051 ***


Note You need to log in before you can comment on or make changes to this bug.