Bug 92279 - [dc] Core faults everytime I reboot, possible NIC issue.
Summary: [dc] Core faults everytime I reboot, possible NIC issue.
Status: Closed Not Enough Information
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-net (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-24 18:10 UTC by Paul Belanger
Modified: 2018-05-28 20:30 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Belanger 2006-01-24 18:10:02 UTC
Everytime I reboot my machine, I get a core fault.  Below is a back trace.  As you can see the problem seems to lie around my NIC.

[12:47:43] Tue 01/24/2006 [lab76.lab.ottawa.pt.com] [/usr/obj/usr/src/sys/DIMENSION] [pbelanger@ttyp0] # kgdb kernel.debug /var/crash/vmcore.1
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd".

Unread portion of the kernel message buffer:
<118>Jan 24 12:40:36 lab76 syslogd: exiting on signal 15
<118>Jan 24 12:40:36 amd[444]: /etc/amd.map unmounted fstype toplvl from /net
<118>Jan 24 12:40:37 amd[444]: /etc/amd.map unmounted fstype toplvl from /host
<118>Jan 24 12:40:38 amd[444]: Finishing with status 0
Waiting (max 60 seconds) for system process `vnlru' to stop...done
Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining...3 3 2 2 0 0 0 done
All buffers synced.
Uptime: 46m29s
Shutting down ACPI


Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0x18
fault code              = supervisor write, page not present
instruction pointer     = 0x20:0xc05cca3d
stack pointer           = 0x28:0xc7b5ec70
frame pointer           = 0x28:0xc7b5ec9c
code segment            = base rx0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 14 (irq3: dc0)
trap number             = 12
panic: page fault
Uptime: 46m29s
Dumping 127 MB (3 chunks)
  chunk 0: 1MB (159 pages) ... ok
  chunk 1: 64MB (16381 pages) 49 33 17 ... ok
  chunk 2: 63MB (16128 pages) 48 32 16

#0  doadump () at pcpu.h:165
165             __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb) list *0xc05cca3d
0xc05cca3d is in dc_rxeof (/usr/src/sys/pci/if_dc.c:2779).
2774                     * If we are on an architecture with alignment problems, or
2775                     * if the allocation fails, then use m_devget and leave the
2776                     * existing buffer in the receive ring.
2777                     */
2778                    if (dc_quick && dc_newbuf(sc, i, 1) == 0) {
2779                            m->m_pkthdr.rcvif = ifp;
2780                            m->m_pkthdr.len = m->m_len = total_len;
2781                            DC_INC(i, DC_RX_LIST_CNT);
2782                    } else
2783    #endif

How-To-Repeat: For me, I reboot and it happens.
Comment 1 Volker Werth freebsd_committer freebsd_triage 2009-01-14 21:47:07 UTC
State Changed
From-To: open->feedback

Paul, 
by any chance, do you have a backtrace for us? 
w/o a backtrace, I don't see a chance to imagine the call 
path and thus we don't know where it breaks. 
If you don't have one handy and can't reprodruce the panic, 
please give us feedback so we can close the PR - thanks. 


Comment 2 Volker Werth freebsd_committer freebsd_triage 2009-01-14 21:47:07 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-net


Over to maintainer(s).
Comment 3 Volker Werth freebsd_committer freebsd_triage 2009-01-14 22:19:53 UTC
State Changed
From-To: feedback->suspended

mail to submitter bounces
Comment 4 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:44:27 UTC
batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.
Comment 5 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 20:30:13 UTC
mail to submitter bounces