sudden and unexpected reboot; /var/log/messages: Jan 22 19:28:01 scaleo kernel: WARNING: / was not properly dismounted Jan 22 19:28:01 scaleo kernel: WARNING: /usr was not properly dismounted Jan 22 19:28:01 scaleo savecore: reboot after panic: page fault Jan 22 19:28:01 scaleo savecore: writing core to vmcore.0 has now occured two times when working with FreeBSD p.s.: how can I post a core file bz2 when i submit a bug via the web form http://www.freebsd.org/send-pr.html (too large for an email as well)?
State Changed From-To: open->feedback To submitter: Sending the core file (or even providing it for download) is not hugely useful, as getting useful information out of it is easiest done on the system with the issues. Can you please follow the instructions at http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html (specifically, obtaining the backtrace) and provide the result? Also, please give some details about this system: what are it's main roles (desktop, web server, dns server etc), has it been stable with previous versins of FreeBSD, and have any hardware changes been made recently, etc?
Responsible Changed From-To: freebsd-bugs->gavin Track
> p.s.: how can I post a core file bz2 when i submit a bug via the web > form http://www.freebsd.org/send-pr.html (too large for an email as well)? Please post it somewhere on the web and submit a followup with a URL to it. Thanks. mcl
gdb seems to have problems reading the core file: /var/crash/vmcore.0": not in executable format: File format not recognized Besides this there is no file called kernel.debug on my machine although the kernel sources seem to be installed at /usr/src/sys/i386 How can I post a message to this bug without sending an email? gavin@FreeBSD.org wrote: > Synopsis: [panic] unexpected crash due to page fault > > State-Changed-From-To: open->feedback > State-Changed-By: gavin > State-Changed-When: Sat Jan 24 19:03:37 UTC 2009 > State-Changed-Why: > To submitter: Sending the core file (or even providing it for download) is > not hugely useful, as getting useful information out of it is easiest done > on the system with the issues. Can you please follow the instructions at > http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html > (specifically, obtaining the backtrace) and provide the result? > > Also, please give some details about this system: what are it's main roles > (desktop, web server, dns server etc), has it been stable with previous > versins of FreeBSD, and have any hardware changes been made recently, etc? > > > Responsible-Changed-From-To: freebsd-bugs->gavin > Responsible-Changed-By: gavin > Responsible-Changed-When: Sat Jan 24 19:03:37 UTC 2009 > Responsible-Changed-Why: > Track > > http://www.freebsd.org/cgi/query-pr.cgi?pr=130941 > >
On Tue, 27 Jan 2009, Elmar Stellnberger wrote: > gdb seems to have problems reading the core file: > /var/crash/vmcore.0": not in executable format: File format not recognized Can you try "kgdb /boot/kernel/kernel.symbols /var/crash/vmcore.0" Or if kernel.symbols doesn't exist, "kgdb /boot/kernel/kernel /var/crash/vmcore.0" > Besides this there is no file called kernel.debug on my machine although > the kernel sources seem to be installed at /usr/src/sys/i386 That's expected, if it's not been compiled from source with debugging enabled. Gavin
Gavin Atkinson wrote: > On Tue, 27 Jan 2009, Elmar Stellnberger wrote: >> gdb seems to have problems reading the core file: >> /var/crash/vmcore.0": not in executable format: File format not >> recognized > > Can you try "kgdb /boot/kernel/kernel.symbols /var/crash/vmcore.0" > Or if kernel.symbols doesn't exist, > "kgdb /boot/kernel/kernel /var/crash/vmcore.0" > >> Besides this there is no file called kernel.debug on my machine although >> the kernel sources seem to be installed at /usr/src/sys/i386 > > That's expected, if it's not been compiled from source with debugging > enabled. > > Gavin >
Apologies for the long delay in responding. The debugging info you have provided so far is great. Could you do a couple more things please? On Wed, 2009-01-28 at 15:53 +0000, Elmar Stellnberger wrote: > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > (kgdb) up > #8 0xc073c286 in g_vfs_strategy (bo=0xc8dbeec4, bp=0xd91e1c14) at /usr/src/sys/geom/geom_vfs.c:107 > 107 g_io_request(bip, cp); > (kgdb) l - > 97 cp = bo->bo_private; > 98 G_VALID_CONSUMER(cp); > 99 > 100 bip = g_alloc_bio(); > 101 bip->bio_cmd = bp->b_iocmd; > 102 bip->bio_offset = bp->b_iooffset; > 103 bip->bio_data = bp->b_data; > 104 bip->bio_done = g_vfs_done; > 105 bip->bio_caller2 = bp; > 106 bip->bio_length = bp->b_bcount; > (kgdb) l > 107 g_io_request(bip, cp); > 108 } > 109 > 110 static void > 111 g_vfs_orphan(struct g_consumer *cp) > 112 { > 113 > 114 /* > 115 * Don't do anything here yet. > 116 * Here, please show the output of p (struct g_consumer) *cp p (struct bio) *bip Thanks, Gavin
Gavin Atkinson wrote: > Apologies for the long delay in responding. The debugging info you have > provided so far is great. Could you do a couple more things please? > > On Wed, 2009-01-28 at 15:53 +0000, Elmar Stellnberger wrote: > >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> >> (kgdb) up >> #8 0xc073c286 in g_vfs_strategy (bo=0xc8dbeec4, bp=0xd91e1c14) at /usr/src/sys/geom/geom_vfs.c:107 >> 107 g_io_request(bip, cp); >> (kgdb) l - >> 97 cp = bo->bo_private; >> 98 G_VALID_CONSUMER(cp); >> 99 >> 100 bip = g_alloc_bio(); >> 101 bip->bio_cmd = bp->b_iocmd; >> 102 bip->bio_offset = bp->b_iooffset; >> 103 bip->bio_data = bp->b_data; >> 104 bip->bio_done = g_vfs_done; >> 105 bip->bio_caller2 = bp; >> 106 bip->bio_length = bp->b_bcount; >> (kgdb) l >> 107 g_io_request(bip, cp); >> 108 } >> 109 >> 110 static void >> 111 g_vfs_orphan(struct g_consumer *cp) >> 112 { >> 113 >> 114 /* >> 115 * Don't do anything here yet. >> 116 * > > Here, please show the output of > > p (struct g_consumer) *cp > p (struct bio) *bip > > Thanks, > > Gavin >
For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped
Keyword: crash – in lieu of summary line prefix: [panic] * bulk change for the keyword * summary lines may be edited manually (not in bulk). Keyword descriptions and search interface: <https://bugs.freebsd.org/bugzilla/describekeywords.cgi>