[DragonFlyBSD - Bug #2413] (Resolved) kernel panic bsd4_unqueue

Issue #2413 has been updated by Ferruccio Zamuner. Status changed from Feedback to Resolved Thank you, you have fixed. Bug #2413: kernel panic bsd4_unqueue http://bugs.dragonflybsd.org/issues/2413 Author: Ferruccio Zamuner Status: Resolved Priority

[DragonFlyBSD - Bug #2413] kernel panic bsd4_unqueue

l file. Bye and thank you, \ferz Bug #2413: kernel panic bsd4_unqueue http://bugs.dragonflybsd.org/issues/2413 Author: Ferruccio Zamuner Status: Feedback Priority: High Assignee: Category: Target version: I've updated sources this

[DragonFlyBSD - Bug #2413] (Feedback) kernel panic bsd4_unqueue

Issue #2413 has been updated by Alex Hornung. Status changed from New to Feedback Should be fixed in f3025b16812bc484c7b518058fe2f5324dc310ae Bug #2413: kernel panic bsd4_unqueue http://bugs.dragonflybsd.org/issues/2413 Author: Ferruccio Zamuner Status

[DragonFlyBSD - Bug #2413] kernel panic bsd4_unqueue

Issue #2413 has been updated by Alex Hornung. Could you please give some more information on your machine? In particular, which CPU manufacturer, model? Cheers, Alex Bug #2413: kernel panic bsd4_unqueue http://bugs.dragonflybsd.org/issues/2413 Author

[DragonFlyBSD - Bug #2413] kernel panic bsd4_unqueue

Issue #2413 has been reported by Ferruccio Zamuner. Bug #2413: kernel panic bsd4_unqueue http://bugs.dragonflybsd.org/issues/2413 Author: Ferruccio Zamuner Status: New Priority: High Assignee: Category: Target version: I've updated sources

[DragonFlyBSD - Bug #2250] Kernel panic

Issue #2250 has been reported by Adam Kirchhoff. Bug #2250: Kernel panic http://bugs.dragonflybsd.org/issues/2250 Author: Adam Kirchhoff Status: New Priority: Normal Assignee: Category: Target version: In an attempt to diagnose issues with the re(4

[issue2126] kernel panic when removing the network cable

Ralf Schmitt added the comment: I've rebuild world and kernel and now can't reproduce the issue either. My current version is v2.13.0-14-g01c7831 on x86_64. _ DragonFly issue tracker __

Re: [issue2126] kernel panic when removing the network cable

> Thomas Nikolajsen added the comment: > > I can't reproduce this on master on i386. > > Do you still see this problem? > If you do, please give more details on how to reproduce. I'll rebuild world next week when I'm back at work and try it again.

[issue2126] kernel panic when removing the network cable

Thomas Nikolajsen added the comment: I can't reproduce this on master on i386. Do you still see this problem? If you do, please give more details on how to reproduce. -- status: unread -> chatting _ DragonFly issue tracker

[issue2126] kernel panic when removing the network cable

New submission from Ralf Schmitt : I'm getting a kernel panic if I remove the network cable and plug it in again. I'm running dhclient on this machine and if I turn it off I can unplug the network cable and plug it in again without getting a kernel panic. crash dump is available

Re: Kernel panic: CPU APIC ID out of range

On Thu, 21 Apr 2011 18:21:33 +0200, Andrej Podzimek wrote: I suggest you to try: http://avalon.dragonflybsd.org/snapshots/x86_64/DragonFly-x86_64-LATEST-ISO.iso.bz2 Thank you for your suggestion. The CD I tried before was dfly-x86_64-2.8.2_REL.iso. With the CD you suggest, the boot proces

Re: Kernel panic: CPU APIC ID out of range

booting DragonFly BSD from a CD ends with a kernel panic. A screenshot of the console is attached. The machine is a Dell PowerEdge M610 blade. The same problem occurs on both of our M610s, one with older 45nm Xeons and one with newer 32nm Xeons. I'd like to run some performance benchmarks o

Re: Kernel panic: CPU APIC ID out of range

On Thu, Apr 21, 2011 at 8:37 PM, Andrej Podzimek wrote: > Hello, > > booting DragonFly BSD from a CD ends with a kernel panic. A screenshot of > the console is attached. The machine is a Dell PowerEdge M610 blade. The > same problem occurs on both of our M610s, one with older 45n

Kernel panic: CPU APIC ID out of range

Hello, booting DragonFly BSD from a CD ends with a kernel panic. A screenshot of the console is attached. The machine is a Dell PowerEdge M610 blade. The same problem occurs on both of our M610s, one with older 45nm Xeons and one with newer 32nm Xeons. I'd like to run some perfor

kernel panic, when run boot0cfg

boot0cfg -s 1 /dev/serno/... cause following panic: panic: assertion: LIST_FIRST(&bp->b_dep) == NULL in vfs_vmio_release cpuid = 0 Trace beginning at frame 0xdabf49f0 panic(,0,c03d2dec,dabf4a24,dab811d8) at panic+0x19d panic(c03d2dec,c03fa8b0,c03bcdbe,c4358c18,c1236038) at panic+0x19d vfs_

[issue1830] kernel panic v2.7.3.863.gaa25c-DEVELOPMENT

Peter Avalos added the comment: I'm going to call this fixed. -- status: chatting -> resolved _ DragonFly issue tracker _

Re: kernel panic v2.7.3.863.gaa25c-DEVELOPMENT

I think what we may have here is a data overflow somewhere interfering with adjacent mbufs in memory. I will commit some additional asserts to try to catch it earlier. I have gotten similar crashes. -Matt

kernel panic v2.7.3.863.gaa25c-DEVELOPMENT

Got a kernel panic tonight on a GENERIC kernel v2.7.3.863.gaa25c-DEVELOPMENT. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x10 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0344101 stack pointer = 0x10

Re: kernel panic, x86, 2.7.3.859.ge5104

I've pushed a bunch of work, please update to the latest master and continue testing! No smoking gun but I suspect machine load may be causing m_reclaim() to get run, which drains various protocol caches. Those caches were not MPSAFE. The changes address that issue. If t

Re: kernel panic, x86, 2.7.3.859.ge5104

On Wed, 8 Sep 2010 10:12:00 -0700 (PDT) Matthew Dillon wrote: > Adam, was the machine that crashed serving NFS ? I was able to > reproduce the exact same crash while serving NFS. > > -Matt The NFS server was running, but nothing was connec

Re: kernel panic, x86, 2.7.3.859.ge5104

Adam, was the machine that crashed serving NFS ? I was able to reproduce the exact same crash while serving NFS. -Matt

Re: kernel panic, x86, 2.7.3.859.ge5104

:> I was building some packages in the background at the time. I was ssh'ed :> in from a linux box, and running x2x to allow me to move the mouse and :> keyboard from the linux box to the DF box. At the time of the lock up, I :> was moving the mouse around on the DF box. Though I have no idea i

Re: kernel panic, x86, 2.7.3.859.ge5104

On Tuesday 07 September 2010 19:22:57 Adam K Kirchhoff wrote: > SMP enabled, otherwise a GENERIC kernel. > > Full backtrace: > > (kgdb) bt > #0 _get_mycpu (di=0xc06ebee0) at ./machine/thread.h:83 > #1 md_dumpsys (di=0xc06ebee0) at > /usr/src/sys/platform/pc32/i386/dump_machdep.c:263 > #2 0xc03

kernel panic, x86, 2.7.3.859.ge5104

SMP enabled, otherwise a GENERIC kernel. Full backtrace: (kgdb) bt #0 _get_mycpu (di=0xc06ebee0) at ./machine/thread.h:83 #1 md_dumpsys (di=0xc06ebee0) at /usr/src/sys/platform/pc32/i386/dump_machdep.c:263 #2 0xc0315d31 in dumpsys () at /usr/src/sys/kern/kern_shutdown.c:880 #3 0xc03162f1

[issue1789] kernel panic with sk network driver

Sepherosa Ziehau added the comment: committed: http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/070470e6ff073011effcdb33b2e60894377429cb -- status: chatting -> resolved _ DragonFly issue tracker

[issue1789] kernel panic with sk network driver

VOROSKOI Andras added the comment: Thanks for the quick reply from both of you. Sephe's patch fixes my problem. _ DragonFly issue tracker _

Re: [issue1789] kernel panic with sk network driver

On Thu, Jul 1, 2010 at 11:43 PM, VOROSKOI Andras (via DragonFly issue tracker) wrote: > > New submission from VOROSKOI Andras : > > I have a kernel panic at bootup. I've tried to add dumpdev to > /boot/loader.conf > but does not help, I can not get a kernel dump. > &

Re: [issue1789] kernel panic with sk network driver

> I have a kernel panic at bootup. I've tried to add dumpdev to > /boot/loader.conf > but does not help, I can not get a kernel dump. Try removing the sk driver from your kernel conf file and rebuild/install kernel. Then load the module manually after box has booted. # kldload if_sk Max

Re: [issue1789] kernel panic with sk network driver

Hi, > I have a kernel panic at bootup. I've tried to add dumpdev to > /boot/loader.conf > but does not help, I can not get a kernel dump. I'm experiencing exactly the same kernel panic ever since I did a full build- and installworld/kernel last week! I managed to get thi

[issue1789] kernel panic with sk network driver

New submission from VOROSKOI Andras : I have a kernel panic at bootup. I've tried to add dumpdev to /boot/loader.conf but does not help, I can not get a kernel dump. I have made some pictures anyway: http://frugalware.org/~voroskoi/dfly/img1.jpg http://frugalware.org/~voroskoi/dfly/img

[issue1594] Kernel panic during boot from Live CD on Dell E6400

Tomas Bodzar added the comment: set debug.acpi.disabled="cmbat" is working at least for installer. I'm installing now to test other bugs. _ DragonFly issue tracker _

[issue1594] Kernel panic during boot from Live CD on Dell E6400

Alexander Polakov added the comment: Try to drop into loader prompt and set debug.acpi.disabled="cmbat". _ DragonFly issue tracker _

Re: [issue1594] Kernel panic during boot from Live CD on Dell E6400

7.2 and some 6. Can't remember exactly now. But no one was current. On Tue, Nov 3, 2009 at 3:27 PM, Alexander Polakov (via DragonFly issue tracker) wrote: > > Alexander Polakov added the comment: > > Which version of FreeBSD have you tried, 7.2 or 8.0? > > -- > status: unread -> chatting

[issue1594] Kernel panic during boot from Live CD on Dell E6400

Alexander Polakov added the comment: Which version of FreeBSD have you tried, 7.2 or 8.0? -- status: unread -> chatting _ DragonFly issue tracker __

[issue1314] NFS /etc/exports: -public flag results in kernel panic

Antonio Huete Jimenez added the comment: Fix committed by Dillon. d246c910c836dc336f1e64e1bb60c8302e8c3a62 -- status: chatting -> resolved _ DragonFly issue tracker ___

[issue1314] NFS /etc/exports: -public flag results in kernel panic

Antonio Huete Jimenez added the comment: Michael, Have you tried this with HAMMER and null-mounted PFSs? Can you please try with UFS? I've tried with UFS on a vkernel without problems. _ DragonFly issue tracker

[issue1314] NFS /etc/exports: -public flag results in kernel panic

Antonio Huete Jimenez added the comment: Let me give this a try. -- assignedto: -> tuxillo nosy: +tuxillo _ DragonFly issue tracker _

[issue1420] UP kernel, panic during installworld (mtree)

Sepherosa Ziehau added the comment: Heh, my fault. It turns out my sound.ko is not built for several months :P Close it. -- status: unread -> resolved _ DragonFly issue tracker __

Re: UP kernel, panic during installworld (mtree)

:Hi, : :Single user mode during installworld, UP kernel (100% panic): : :mtree -deU -f /usr/src/etc/mtree/BSD.root.dist -p / : :Fatal trap 12: page fault while in kernel mode :... :... I haven't been able to reproduce this yet. I did find a problem with the keyboard not working sometimes

Re: UP kernel, panic during installworld (mtree)

:Hi, : :Single user mode during installworld, UP kernel (100% panic): : :mtree -deU -f /usr/src/etc/mtree/BSD.root.dist -p / : :Fatal trap 12: page fault while in kernel mode :... :... : :Stopped at hashdev+0x2f: cmpl 0x24(%esi),%ebx :hashdev() :get_dev() :spec_getattr() :ufsspec_getattr() :ufs_vn

UP kernel, panic during installworld (mtree)

Hi, Single user mode during installworld, UP kernel (100% panic): mtree -deU -f /usr/src/etc/mtree/BSD.root.dist -p / Fatal trap 12: page fault while in kernel mode ... ... Stopped at hashdev+0x2f: cmpl 0x24(%esi),%ebx hashdev() get_dev() spec_getattr() ufsspec_getattr() ufs_vnoperatespec() vop

NFS /etc/exports: -public flag results in kernel panic

Hi, It's reproducable. I've a simple /etc/exports file like this: /data -alldirs -public It gives a kernel panic (lockmgr) when NFS is started. Without -public it works. Regards, Michael

[issue636] kernel panic

Simon 'corecode' Schubert added the comment: thanks, closing. -- status: chatting -> resolved _ DragonFly issue tracker _

Re: [issue636] kernel panic

On Sun, Jan 25, 2009 at 10:52:00PM +, Simon 'corecode' Schubert (via DragonFly issue tracker) wrote: > > Simon 'corecode' Schubert added the comment: > > is this still present? No. Joe

[issue636] kernel panic

Simon 'corecode' Schubert added the comment: is this still present? _ DragonFly issue tracker _

[issue827] kernel panic on HEAD from Oct. 4th sources

Simon 'corecode' Schubert added the comment: fixed in various commits -- status: chatting -> resolved _ DragonFly issue tracker _

[issue539] DFBSD 1.8 - Kernel panic under heavy load - Not reproducible

Simon 'corecode' Schubert added the comment: original has been resolved -- status: chatting -> resolved _ DragonFly issue tracker _

[issue131] Kernel panic on VMWare

Simon 'corecode' Schubert added the comment: timeout -- status: chatting -> resolved _ DragonFly issue tracker _

Re: [issue827] kernel panic on HEAD

:Matt, : :This looks like it could be easy (for you anyway) to fix...Just wanted :to make sure you've seen it. : :--Peter :... :#15 0xc03101b7 in calltrap () at /usr/src/sys/platform/pc32/i386/exception.= :s:785 :#16 0xc01a5e09 in fill_kinfo_proc (p=3D0xda308598, kp=3D0xee07664c) at :/usr/src/sys/

[issue827] kernel panic on HEAD from Oct. 4th sources

Peter Avalos <[EMAIL PROTECTED]> added the comment: I just got another one very similar to this with HEAD sources from about 10 days ago. kernel and vmcore (*.21) are being uploaded to leaf right now. Unread portion of the kernel message buffer: panic: vm_fault: unrecoverable fault at 0xdeadc000

[issue797] kernel panic

Peter Avalos <[EMAIL PROTECTED]> added the comment: I haven't seen it in awhile, so I'm going to call it resolved. -- status: chatting -> resolved _ DragonFly issue tracker <[EMAIL PROTECTED]> _

Re: kernel panic under install CD boot (cd9660-related)

So, I finally managed to get a verbose boot dmesg after about a week's worth of trying random shit just to get it to boot, where even pxe was b0rked. Enjoy the dmesg.txt, I sure didn't. I hope that'll be helpful in getting things one step further. Copyright (c) 2003-2008 The DragonFly Projec

Re: kernel panic under install CD boot (cd9660-related)

YONETANI Tomokazu wrote: Can you try booting with ACPI disabled and see anything changes? I was fairly certain I had tried (but forgotten to mention it), but I just tried again. normal, without acpi and in safemode, they all end up with mountroot, unfortunately.

Re: kernel panic under install CD boot (cd9660-related)

On Fri, Aug 22, 2008 at 05:47:52PM +0200, Jan Martin Mathiassen wrote: > Hi, I've got a bit of a problem with the install CD. I've tested this on > 2.0 and 2.1.0-DEV (i.e. the daily iso downloadable on 2008.08.22). This > happens way before I can make any sort of FS, but the same machine's > booted

Re: kernel panic under install CD boot (cd9660-related)

Attached is the pciconf taken from fbsd7.0 [EMAIL PROTECTED]:0:0:0:class=0x06 card=0x81ea1043 chip=0x29a08086 rev=0x02 hdr=0x00 [EMAIL PROTECTED]:0:1:0:class=0x060400 card=0x8086 chip=0x29a18086 rev=0x02 hdr=0x01 [EMAIL PROTECTED]:0:26:0: class=0x0c0300 card=0x81ec1

Re: kernel panic under install CD boot (cd9660-related)

Just did a bit more testing. Windows XP: works fine. Debian 3.0: hangs during bootup of install cd Debian 4.0r4: works fine. FBSD7.0: complains with the following: acd0: TIMEOUT - READ_BIG retrying (1 retry left) acd0: TIMEOUT - READ_BIG retrying (0 retries left) acd0: FAILURE - READ_BIG timed o

Re: kernel panic under install CD boot (cd9660-related)

Jan Martin Mathiassen wrote: Hi, I've got a bit of a problem with the install CD. I've tested this on 2.0 and 2.1.0-DEV (i.e. the daily iso downloadable on 2008.08.22). This happens way before I can make any sort of FS, but the same machine's booted up XP, Kubuntu and FBSD5.4. Anyway, what I can

kernel panic under install CD boot (cd9660-related)

Hi, I've got a bit of a problem with the install CD. I've tested this on 2.0 and 2.1.0-DEV (i.e. the daily iso downloadable on 2008.08.22). This happens way before I can make any sort of FS, but the same machine's booted up XP, Kubuntu and FBSD5.4. Anyway, what I can see on the bootup screen of t

[issue1076] HAMMER kernel panic on git-clone

YONETANI Tomokazu <[EMAIL PROTECTED]> added the comment: This has been resolved before the release. -- priority: -> bug status: chatting -> resolved _ DragonFly issue tracker <[EMAIL PROTECTED]>

Re: HAMMER kernel panic on git-clone

:> Ok, let me fix this one, I have a patch set from the other work almost :> ready to go and I'll just add the appropriate code for the cross link :> check. : :Sure, I can try patches anytime. : :Thanks. Ok, its all committed. -Matt

Re: HAMMER kernel panic on git-clone

On Fri, Jul 18, 2008 at 08:51:03PM -0700, Matthew Dillon wrote: > Bleh. I just thought of another problem. The kernel has no clue > about PFS's. I guess we have to do the cross-device link check in > HAMMER anyway, so it can also check for attempts to link across PFS > boundaries

Re: HAMMER kernel panic on git-clone

Bleh. I just thought of another problem. The kernel has no clue about PFS's. I guess we have to do the cross-device link check in HAMMER anyway, so it can also check for attempts to link across PFS boundaries. Ok, let me fix this one, I have a patch set from the other work a

Re: HAMMER kernel panic on git-clone

:A-ha, looking at ktrace output (somehow truss stuck in the middle of :execution) and the UFS source code, HAMMER lacks cross-device link checks :in nlink and nrename. I'll work on a patch for this one. : :Cheers. Oh, sorry, as usual I didn't completely read your short posting :-) If yo

Re: HAMMER kernel panic on git-clone

:A-ha, looking at ktrace output (somehow truss stuck in the middle of :execution) and the UFS source code, HAMMER lacks cross-device link checks :in nlink and nrename. I'll work on a patch for this one. : :Cheers. Ah, ok, you can abort that core dump download then. The DragonFly kernel i

Re: HAMMER kernel panic on git-clone

On Sat, Jul 19, 2008 at 12:07:35PM +0900, YONETANI Tomokazu wrote: > #7 0xc0256ca9 in hammer_modify_inode (ip=0xd5e05500, flags=1) > at /home/source/dragonfly/R2_0/src/sys/vfs/hammer/hammer_inode.c:1342 > #8 0xc025e448 in hammer_ip_add_directory (trans=0xd5eb7af0, dip=0xd2981250, > name=0

HAMMER kernel panic on git-clone

Hi. Running git-clone to a HAMMER filesystem instantly triggers a kernel panic while just cpdup'ing the repository to a HAMMER filesystem doesn't. Both kernel and the world is freshly built from the latest 2.0 source. I also ran newfs_hammer to make sure I don't have stale fil

[issue947] Kernel panic during boot in usb_add_task

Cristi Măgheruşan <[EMAIL PROTECTED]> added the comment: Hello, I also have a HP 6710b laptop, and when I first got this panic I started hunting for devices, and I noticed that the crash is triggered only when the bluetooth adapter is enabled in BIOS and when it is already started at boot time,

[issue947] Kernel panic during boot in usb_add_task

Michael Neumann <[EMAIL PROTECTED]> added the comment: This is fixed in revision 1.44 of src/sys/bus/usb/usb.c. -- status: chatting -> resolved _ DragonFly issue tracker <[EMAIL PROTECTED]>

[issue1017] Kernel panic on most recent snapshot

Matthew Dillon <[EMAIL PROTECTED]> added the comment: Same as 1016, fix committed. -- priority: -> bug status: chatting -> resolved superseder: +mount_cd9660 crashes the kernel _ DragonFly issue tracker <[EMAIL PROTECTED]>

Re: Kernel panic on most recent snapshot

Matthew Dillon wrote: > Ok, this is definitely the same bug as issue 1016 and I've got it > reproduced and will be committing a fix today. I think you already found the bug. It is definitively related to CAM, because for some reason, after I cvs-updated my sources and those CAM changes ca

Re: Kernel panic on most recent snapshot

Ok, this is definitely the same bug as issue 1016 and I've got it reproduced and will be committing a fix today. -Matt Matthew Dillon <[EMAIL PROTECTED]>

Re: Kernel panic on most recent snapshot

:: ::Anyone else getting a kernel panic using the most recent HEAD revision? :: ::When booting from CD: :: :: Mounting root from cd9660:cd0c :: :: :: Fatal trap 12: page fault while in kernel mode :: fault virtual address = 0x8 :: ... :: ... :: ... :: kernel

Re: Kernel panic on most recent snapshot

:Hi, : :Anyone else getting a kernel panic using the most recent HEAD revision? : :When booting from CD: : : Mounting root from cd9660:cd0c : : : Fatal trap 12: page fault while in kernel mode : fault virtual address = 0x8 : ... : ... : ... : kernel: type

Re: Kernel panic on most recent snapshot

> Anyone else getting a kernel panic using the most recent HEAD revision? > > When booting from CD: > >Mounting root from cd9660:cd0c > > >Fatal trap 12: page fault while in kernel mode >fault virtual address = 0x8 >... >

Kernel panic on most recent snapshot

Hi, Anyone else getting a kernel panic using the most recent HEAD revision? When booting from CD: Mounting root from cd9660:cd0c Fatal trap 12: page fault while in kernel mode fault virtual address = 0x8 ... ... ... kernel: type 12 trap

[issue797] kernel panic

Dion Blazakis <[EMAIL PROTECTED]> added the comment: What ever happened with this? Was this resolved, Peter? Is there a chance the work done for: http://www.dragonflybsd.org/cvsweb/src/sys/netinet/in.c?rev=1.26&content-type=text/x-cvsweb-markup could have fixed this issue? -- Dion --

Re: [issue947] Kernel panic during boot in usb_add_task

2008/2/13, Matthew Dillon <[EMAIL PROTECTED]>: > :New submission from Michael Neumann <[EMAIL PROTECTED]>: > : > :I tried my brand new HP Compaq laptop 6710b under DragonFly, but during boo= > :ting > :the installer CD it "throws" a page fault: > : > : uhub0: 2 ports ... > : uhub0: > : > : Fata

Re: [issue947] Kernel panic during boot in usb_add_task

happens with the latest snapshot version as of yesterday and also with= : the :1=2E10 release. : :FreeBSD 7.0-BETA3 silently hangs during boot, while NetBSD 4.0RC_4 works li= :ke a :charm (it can even dual-boot windows natively)!=20 : :There exists a thread on dragonfly.kernel named "Kernel

Re: [issue947] Kernel panic during boot in usb_add_task

Thomas E. Spanjaard wrote: Michael Neumann wrote: uhub0: 2 ports ... uhub0: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 ... stopped at usb_add_task+0x4c:movl %edi,0(%eax) Smells of a null pointer dereference to me. Could we get a bac

Re: [issue947] Kernel panic during boot in usb_add_task

Michael Neumann wrote: uhub0: 2 ports ... uhub0: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 ... stopped at usb_add_task+0x4c:movl %edi,0(%eax) Smells of a null pointer dereference to me. -- Thomas E. Spanjaard [EMAIL PR

[issue947] Kernel panic during boot in usb_add_task

ay and also with the 1.10 release. FreeBSD 7.0-BETA3 silently hangs during boot, while NetBSD 4.0RC_4 works like a charm (it can even dual-boot windows natively)! There exists a thread on dragonfly.kernel named "Kernel panic during boot in usb_add_task" about this issue. -- mes

[issue947] Kernel panic during boot in usb_add_task

Michael Neumann <[EMAIL PROTECTED]> added the comment: The "bug" disappears if I compile a kernel without USB support. -- status: unread -> chatting _ DragonFly issue tracker <[EMAIL PROTECTED]>

[issue910] Kernel panic while doing sysctl -a

Matthias Schmidt <[EMAIL PROTECTED]> added the comment: Close this issue. A stress test with module loading/unloading and sysctl shows that nth@'s recent zdestroy() patch fixes that issue. -- priority: -> bug status: chatting -> resolved __

Re: Kernel panic while doing sysctl -a

:I think we don't have function to destroy zone initialized by zinit() :(used by pf), so currently pf module can't be unloaded. : :Best Regards, :sephe ZONE_DESTROY() in pfvar.h is a NOP. Anyone want to have a go at writing a zdestroy() function for vm/vm_zone.c to complement the zini

Re: Kernel panic while doing sysctl -a

On Jan 8, 2008 6:16 PM, Matthias Schmidt <[EMAIL PROTECTED]> wrote: > He sephe, > > * Sepherosa Ziehau wrote: > > On Jan 8, 2008 4:51 PM, Matthias Schmidt <[EMAIL PROTECTED]> wrote: > > > * Matthew Dillon wrote: > > > > > > > > The vm_zone->zname is pointing to illegal storage. Very weird, a

Re: Kernel panic while doing sysctl -a

He sephe, * Sepherosa Ziehau wrote: > On Jan 8, 2008 4:51 PM, Matthias Schmidt <[EMAIL PROTECTED]> wrote: > > * Matthew Dillon wrote: > > > > > > The vm_zone->zname is pointing to illegal storage. Very weird, a > > > whole > > > bunch of zones have bad zname's. They look like they've co

Re: Kernel panic while doing sysctl -a

On Jan 8, 2008 4:51 PM, Matthias Schmidt <[EMAIL PROTECTED]> wrote: > * Matthew Dillon wrote: > > > > The vm_zone->zname is pointing to illegal storage. Very weird, a whole > > bunch of zones have bad zname's. They look like they've come from a > > dynamic module, and there are a whol

Re: Kernel panic while doing sysctl -a

* Matthew Dillon wrote: > > The vm_zone->zname is pointing to illegal storage. Very weird, a whole > bunch of zones have bad zname's. They look like they've come from a > dynamic module, and there are a whole bunch of them. Is there a module > you are loading and unloading a lot

Re: Kernel panic while doing sysctl -a

:Hi, : :one of my machines running HEAD experienced a kernel panic. The command I :executed before the panic was "sysctl -a | less" to get a list of sysctls. :It seems that there is an overflow within the strlen function ... : :kernel, crash dump, dmesg and pciconf -lv is available her

Re: kernel panic on HEAD from Oct. 4th sources

:I think we should simply prevent these almost reaped processes from :staying in the zombie list. I suggest the attached fix (not yet tested). : :cheers : simon It is probably a good idea to remove it from the list before or after the "reap3" sleep loop. That particular patch may brea

Re: kernel panic on HEAD from Oct. 4th sources

Matthew Dillon wrote: :Just got this, and it appears similar to the previous one: : :dumping to dev #da/0x20001, blockno 378927 : :(kgdb) bt :#7 0xc019b833 in fill_kinfo_proc (p=3D0xe8bd1ee0, kp=3D0xe926c628) at /usr= :/src/sys/kern/kern_kinfo.c:97 :.. : :This happened with the system doing some

Re: kernel panic on HEAD from Oct. 4th sources

:Just got this, and it appears similar to the previous one: : :dumping to dev #da/0x20001, blockno 378927 : :(kgdb) bt :#7 0xc019b833 in fill_kinfo_proc (p=3D0xe8bd1ee0, kp=3D0xe926c628) at /usr= :/src/sys/kern/kern_kinfo.c:97 :.. : :This happened with the system doing some serious paging. Sourc

Re: kernel panic on HEAD from Oct. 4th sources

On Wed, Oct 17, 2007 at 04:32:04PM -0700, Matthew Dillon wrote: > :Just had this one last night: > : > :... > :#7 0xc018cb85 in fill_kinfo_proc (p=3D0xe8c21ba0, kp=3D0xec319628) at /usr= > :/src/sys/kern/kern_kinfo.c:66 > > I have committed a fix for what I believe the problem was. > Just g

Kernel panic while doing sysctl -a

Hi, one of my machines running HEAD experienced a kernel panic. The command I executed before the panic was "sysctl -a | less" to get a list of sysctls. It seems that there is an overflow within the strlen function ... kernel, crash dump, dmesg and pciconf -lv is available h

Re: kernel panic

:Since ifa_addr is points at the correct memory position but rest of :the pointers are 'deadc0de', the on-list dead in_ifaddr may go through :following code and become dead: :netinet/in.c: : :in_ifinit() :{ :... :if (scrub) { :ia->ia_ifa.ifa_addr =3D (struct sockaddr *)&oldaddr; :

Re: kernel panic

On Fri, Dec 28, 2007 at 08:43:43PM +0800, Sepherosa Ziehau wrote: > > My question about the panic is: > Have you assigned IP address to the tap(4) device via -I option to vkernel? Yes. > The patch looks good to me; it still needs little modification tho. > If you had not assign IP address to tap

Re: kernel panic

On Fri, Dec 28, 2007 at 09:13:51PM +0800, Sepherosa Ziehau wrote: > > I think in_ifscrub() killed the last reference, but this code path is > rarely stressed: > 1) From SIOCSIFADDR, which is not used by ifconfig(8) or vkernel(7) > 2) From sppp_set_ip_addr(), is it used on the panic system? > spp

Re: kernel panic

On Aug 30, 2007 12:50 PM, Matthew Dillon <[EMAIL PROTECTED]> wrote: > > :Another page fault kernel panic, but it doesn't look the same as issue530. > : > :The sources are from July 11: > : > :DragonFly ylem.theshell.com 1.9.0-DEVELOPMENT DragonFly 1.9.0-DEVELOPMENT &

Re: kernel panic

On Sep 17, 2007 10:32 AM, Peter Avalos <[EMAIL PROTECTED]> wrote: > > On Sat, Sep 01, 2007 at 05:54:10PM -0400, Peter Avalos wrote: > > On Wed, Aug 29, 2007 at 09:50:27PM -0700, Matthew Dillon wrote: > > > > > > So we need to audit all the code that manipulates the in_ifaddrhead > > > list

Re: [issue829] kernel panic when initializing dummynet

Ah, excellent! -Matt Matthew Dillon <[EMAIL PROTECTED]>

  1   2   3   >