Re: ZFS panic in -CURRENT

(follow up below) On 04/01/2014 06:57, R. Tyler Croy wrote: On Tue, 01 Apr 2014 09:41:45 +0300 Andriy Gapon wrote: on 01/04/2014 02:22 R. Tyler Croy said the following: Bumping this with more details On Fri, 28 Mar 2014 09:53:32 -0700 R Tyler Croy wrote: Apologies for the rough format he

Re: ZFS panic in -CURRENT

on 02/04/2014 19:48 R. Tyler Croy said the following: > On Wed, 02 Apr 2014 09:58:37 +0300 > Andriy Gapon wrote: > >> on 01/04/2014 16:57 R. Tyler Croy said the following: >>> On Tue, 01 Apr 2014 09:41:45 +0300 >>> Andriy Gapon wrote: >>> on 01/04/2014 02:22 R. Tyler Croy said the following

Re: ZFS panic in -CURRENT

On Wed, 02 Apr 2014 09:58:37 +0300 Andriy Gapon wrote: > on 01/04/2014 16:57 R. Tyler Croy said the following: > > On Tue, 01 Apr 2014 09:41:45 +0300 > > Andriy Gapon wrote: > > > >> on 01/04/2014 02:22 R. Tyler Croy said the following: > ... > >>> Also in addition to the photo from before of t

Re: ZFS panic in -CURRENT

on 01/04/2014 16:57 R. Tyler Croy said the following: > On Tue, 01 Apr 2014 09:41:45 +0300 > Andriy Gapon wrote: > >> on 01/04/2014 02:22 R. Tyler Croy said the following: ... >>> Also in addition to the photo from before of the panic, here's >>> another reproduction photo: >>>

Re: ZFS panic in -CURRENT

On Tue, 01 Apr 2014 09:41:45 +0300 Andriy Gapon wrote: > on 01/04/2014 02:22 R. Tyler Croy said the following: > > Bumping this with more details > > > > On Fri, 28 Mar 2014 09:53:32 -0700 > > R Tyler Croy wrote: > > > >> Apologies for the rough format here, I had to take a picture of > >> thi

Re: ZFS panic in -CURRENT

on 01/04/2014 02:22 R. Tyler Croy said the following: > Bumping this with more details > > On Fri, 28 Mar 2014 09:53:32 -0700 > R Tyler Croy wrote: > >> Apologies for the rough format here, I had to take a picture of this >> failure because I didn't know what else to do. >> >>

Re: ZFS panic in -CURRENT

Bumping this with more details On Fri, 28 Mar 2014 09:53:32 -0700 R Tyler Croy wrote: > Apologies for the rough format here, I had to take a picture of this > failure because I didn't know what else to do. > > > > I'm building off of the Gi

ZFS panic in -CURRENT

Apologies for the rough format here, I had to take a picture of this failure because I didn't know what else to do. I'm building off of the GitHub freebsd.git mirror here, and the latest commit in the tree is neel@'s "Add an ioctl to suspend

Re: Tmpfs panic in -current

On 四, 2012-06-28 at 10:09 +0300, Gleb Kurtsou wrote: > On (27/06/2012 13:29), Kevin Lo wrote: > > Kevin Lo wrote: > > > Konstantin Belousov wrote: > > > > On Tue, Jun 26, 2012 at 12:38:25PM +0800, Kevin Lo wrote: > > > > > Konstantin Belousov wrote: > > > > > > On Mon, Jun 25, 2012 at 10:03:28AM +0

Re: Tmpfs panic in -current

On (27/06/2012 13:29), Kevin Lo wrote: > Kevin Lo wrote: > > Konstantin Belousov wrote: > > > On Tue, Jun 26, 2012 at 12:38:25PM +0800, Kevin Lo wrote: > > > > Konstantin Belousov wrote: > > > > > On Mon, Jun 25, 2012 at 10:03:28AM +0800, Kevin Lo wrote: > > > > > > I've observed a panic in recent

Re: Tmpfs panic in -current

Konstantin Belousov wrote: > On Wed, Jun 27, 2012 at 01:29:14PM +0800, Kevin Lo wrote: > > Kevin Lo wrote: > > > Konstantin Belousov wrote: > > > > On Tue, Jun 26, 2012 at 12:38:25PM +0800, Kevin Lo wrote: > > > > > Konstantin Belousov wrote: > > > > > > On Mon, Jun 25, 2012 at 10:03:28AM +0800, Ke

Re: Tmpfs panic in -current

On Wed, Jun 27, 2012 at 01:29:14PM +0800, Kevin Lo wrote: > Kevin Lo wrote: > > Konstantin Belousov wrote: > > > On Tue, Jun 26, 2012 at 12:38:25PM +0800, Kevin Lo wrote: > > > > Konstantin Belousov wrote: > > > > > On Mon, Jun 25, 2012 at 10:03:28AM +0800, Kevin Lo wrote: > > > > > > I've observed

Re: Tmpfs panic in -current

Kevin Lo wrote: > Konstantin Belousov wrote: > > On Tue, Jun 26, 2012 at 12:38:25PM +0800, Kevin Lo wrote: > > > Konstantin Belousov wrote: > > > > On Mon, Jun 25, 2012 at 10:03:28AM +0800, Kevin Lo wrote: > > > > > I've observed a panic in recent -current several times but I only > > > > > have a

Re: Tmpfs panic in -current

Konstantin Belousov wrote: > On Tue, Jun 26, 2012 at 12:38:25PM +0800, Kevin Lo wrote: > > Konstantin Belousov wrote: > > > On Mon, Jun 25, 2012 at 10:03:28AM +0800, Kevin Lo wrote: > > > > I've observed a panic in recent -current several times but I only > > > > have a picture of the backtrace: >

Re: Tmpfs panic in -current

On Tue, Jun 26, 2012 at 12:38:25PM +0800, Kevin Lo wrote: > Konstantin Belousov wrote: > > On Mon, Jun 25, 2012 at 10:03:28AM +0800, Kevin Lo wrote: > > > I've observed a panic in recent -current several times but I only > > > have a picture of the backtrace: > > > http://people.freebsd.org/~kevlo/

Re: Tmpfs panic in -current

Konstantin Belousov wrote: > On Mon, Jun 25, 2012 at 10:03:28AM +0800, Kevin Lo wrote: > > I've observed a panic in recent -current several times but I only > > have a picture of the backtrace: > > http://people.freebsd.org/~kevlo/panic_tmpfs.jpg > > > > Does this look at all familiar to anyone? >

Re: Tmpfs panic in -current

Hello Kevin, May you rebuild your kernel with some options that will make the dump of the crash easier to send to people? Try to follow these steps: 1) Configure KERNEL with the folowing options: options KDB options GDB options DDB 2) Configure rc.conf: dumpdev="/dev/ad0s1

Re: Tmpfs panic in -current

On Mon, Jun 25, 2012 at 10:03:28AM +0800, Kevin Lo wrote: > I've observed a panic in recent -current several times but I only > have a picture of the backtrace: > http://people.freebsd.org/~kevlo/panic_tmpfs.jpg > > Does this look at all familiar to anyone? Can you look up the line corresponding

Tmpfs panic in -current

I've observed a panic in recent -current several times but I only have a picture of the backtrace: http://people.freebsd.org/~kevlo/panic_tmpfs.jpg Does this look at all familiar to anyone? Kevin ___ freebsd-current@freebsd.org mailing list htt

Re: [CURRENT] Panic in -CURRENT of 20031105

On Friday 07 November 2003 07:49 am, Jaco H. van Tonder wrote: > Hi All, > > I get panics at random times of the day with -CURRENT from 20031105, with > absolutely no load on the machine. > > The machine acts as a dial-up server/gateway/firewall for my local lan. I > managed to get a coredump. > >

[CURRENT] Panic in -CURRENT of 20031105

Hi All, I get panics at random times of the day with -CURRENT from 20031105, with absolutely no load on the machine. The machine acts as a dial-up server/gateway/firewall for my local lan. I managed to get a coredump. The contents of the rt pointer passed to RTFREE() does really not look right t

Re: Options MAXMEM added to GENERIC kernel config causes kernel panic in -current

On Sun, 2003-01-26 at 19:08, walt wrote: > Steve Kargl wrote: > > On Sun, Jan 26, 2003 at 05:08:40PM -0500, Eric Jones wrote: > > >>Is there any reason, on newer motherboards, to need the MAXMEM option? > > > I don't know. I've always used MAXMEM. Guess it's > > time to remove it from my kerne

Re: Options MAXMEM added to GENERIC kernel config causes kernel panic in -current

On Sun, Jan 26, 2003 at 05:08:40PM -0500, Eric Jones wrote: > On Thu, 2003-01-23 at 23:56, Steve Kargl wrote: > > > > > > > Disable acpi. acpi is broken. > > I had the same problem until today. If ACPI was enabled, I would get a > panic on boot. I removed MAXMEM from my kernel conf, recompiled

Re: Options MAXMEM added to GENERIC kernel config causes kernel panic in -current

On Thu, 2003-01-23 at 23:56, Steve Kargl wrote: Sorry if this is the second copy, I'm not sure if it went out the first time or not > On Thu, Jan 23, 2003 at 05:40:16PM -1000, Vincent Poy wrote: > > > > /boot/kernel/acpi.ko text=0x2fab4 data=-0x1a84+0x6e0 > > syms=[0x4+0x5540+0x702d|] > > snip

Re: Options MAXMEM added to GENERIC kernel config causes kernel panic in -current

On Thu, 2003-01-23 at 23:56, Steve Kargl wrote: > On Thu, Jan 23, 2003 at 05:40:16PM -1000, Vincent Poy wrote: > > > > /boot/kernel/acpi.ko text=0x2fab4 data=-0x1a84+0x6e0 > > syms=[0x4+0x5540+0x702d|] > > snip > > > embedded 0 6 A 0x60 3 4 5 6 7 9 10 11 12 14 15 > > panic: pmap_mapd

Re: Options MAXMEM added to GENERIC kernel config causes kernel panic in -current

On Thu, Jan 23, 2003 at 05:40:16PM -1000, Vincent Poy wrote: > > /boot/kernel/acpi.ko text=0x2fab4 data=-0x1a84+0x6e0 > syms=[0x4+0x5540+0x702d|] snip > embedded 0 6 A 0x60 3 4 5 6 7 9 10 11 12 14 15 > panic: pmap_mapdev: Couldn't alloc kernel virtual memory > Debugger("panic") > Sto

Re: Options MAXMEM added to GENERIC kernel config causes kernel panic in -current

In the last episode (Jan 23), Vincent Poy said: > Greetings everyone, > > With the latest -CURRENTs ever since atleast September 12, 2002 > that I have tested on several different machines ranging from > PII/PIII/PIV Desktop and Notebooks, whenever the following option is > added to the GENERIC

Re: GEOM panic in current kernel

* De: Terry Lambert <[EMAIL PROTECTED]> [ Data: 2002-09-28 ] [ Subjecte: Re: GEOM panic in current kernel ] > Juli Mallett wrote: > > * De: Terry Lambert <[EMAIL PROTECTED]> [ Data: 2002-09-28 ] > > > Poul-Henning Kamp wrote: > > > &

Re: GEOM panic in current kernel

Juli Mallett wrote: > * De: Terry Lambert <[EMAIL PROTECTED]> [ Data: 2002-09-28 ] > > Poul-Henning Kamp wrote: > > > + bzero(&mymutex, sizeof mymutex); > > > mtx_init(&mymutex, "g_up", MTX_DEF, 0); > > > > > > Too bad mtx_init() doesn't really initialize the mutex, or > > this would

Re: GEOM panic in current kernel

Poul-Henning Kamp wrote: > + bzero(&mymutex, sizeof mymutex); > mtx_init(&mymutex, "g_up", MTX_DEF, 0); Too bad mtx_init() doesn't really initialize the mutex, or this would not be necessary. 8-(. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-

Re: GEOM panic in current kernel

* De: Terry Lambert <[EMAIL PROTECTED]> [ Data: 2002-09-28 ] [ Subjecte: Re: GEOM panic in current kernel ] > Poul-Henning Kamp wrote: > > + bzero(&mymutex, sizeof mymutex); > > mtx_init(&mymutex, "g_up", MTX_DEF, 0); > > >

Re: GEOM panic in current kernel

> >> Uhm, what was the actual panic message ? > >mutex g_up 0xe0499cb8 already initialized > > Can you try this patch ? Works great! Thanks! Marc msg43552/pgp0.pgp Description: PGP signature

Re: GEOM panic in current kernel

In message <[EMAIL PROTECTED]>, Marc Recht writes: >--=./s+MTW'WA?QFc= >Content-Type: text/plain; charset=US-ASCII >Content-Transfer-Encoding: 7bit > >> >After the latest geom_* commits I get a panic while booting. The panic occurs >before mounting the disks, so I had to hand-write it down.. >>

Re: GEOM panic in current kernel

> >After the latest geom_* commits I get a panic while booting. The panic occurs >before mounting the disks, so I had to hand-write it down.. > >panic.. > >mtx_init(e0499ce8, e0396b85, 0, 0, 748f6273) at mtx_init + 0x5f > >... g_up_procbody + 0x34 > >... Wow! That was a fast reply. :-) > Uhm, w

Re: GEOM panic in current kernel

In message <[EMAIL PROTECTED]>, Marc Recht writes: >--=.8yCGZQ.c,FaLiI >Content-Type: text/plain; charset=US-ASCII >Content-Transfer-Encoding: 7bit > >Hi! > >After the latest geom_* commits I get a panic while booting. The panic occurs before >mounting the disks, so I had to hand-write it down..

GEOM panic in current kernel

Hi! After the latest geom_* commits I get a panic while booting. The panic occurs before mounting the disks, so I had to hand-write it down.. panic.. mtx_init(e0499ce8, e0396b85, 0, 0, 748f6273) at mtx_init + 0x5f ... g_up_procbody + 0x34 ... Please let me know if/how I could provide more info.

Re: Panic in -current when using i386_set_ioperm()

On Sun, 21 Jul 2002, Mark Peek wrote: > There is a reproducible panic in -current after using > i386_set_ioperm(). The extended pcb is attempted to be freed in > cpu_thread_exit() using kmem_free(). Via private mail, Alan Cox > explained it to me as such: > > "The p

Panic in -current when using i386_set_ioperm()

There is a reproducible panic in -current after using i386_set_ioperm(). The extended pcb is attempted to be freed in cpu_thread_exit() using kmem_free(). Via private mail, Alan Cox explained it to me as such: "The problem runs deeper than Giant not being held: cpu_thread_exit() really

Re: Promise/ATA-Raid making panic in -CURRENT?

It seems Tom Servo wrote: > I finally pulled the Promise out and it boots. Since I > need it for some Windows apps on the same box I put it > back in and commented some lines in ata driver > regarding the detection of Promise Fasttrak > controllers and it boots now w/o detecting it. This is stran

Re: Promise/ATA-Raid making panic in -CURRENT?

> > Here's the box: > > > > Asus CUV4X-D mainboard, VIA 694X, dual-capable > > 2x P3-933, 768MB PC133 RAM in 3 DIMM(s) > > Two IBM IC35L 60.1GB disks on first IDE > > Pioneer DVD-A05SZ on second IDE > > Two IBM IC35L 60.1GB on Promise Fasttrak TX2 > > (PDC20268/70) in RAID0 > > > > How do I dump

Re: Promise/ATA-Raid making panic in -CURRENT?

> > I finally pulled the Promise out and it boots. > Since I > > need it for some Windows apps on the same box I > put it > > back in and commented some lines in ata driver > > regarding the detection of Promise Fasttrak > > controllers and it boots now w/o detecting it. > > This is strange, the

Re: Promise/ATA-Raid making panic in -CURRENT?

It seems Tom Servo wrote: > > The "bad ivar request (4)" message does *not*?come > > from the ATA driver, you must have something else > > that is ruining your day... Does it boot if you > > take out the promise board ? > > I was in a hurry yesterday and let the kernel compile > w/o the ata drive

Re: Promise/ATA-Raid making panic in -CURRENT?

> The "bad ivar request (4)" message does *not* come > from the ATA driver, you must have something else > that is ruining your day... Does it boot if you > take out the promise board ? I was in a hurry yesterday and let the kernel compile w/o the ata driver while being under the shower. Without

Promise/ATA-Raid making panic in -CURRENT?

Hi! I checked and compiled the recent -CURRENT tree, buildworld and buildkernel goes all fine. When booting it seems to crash on initialization of my Promise controller and get "bad ivar request (4)". I stripped all possible drivers out of the kernelconfig, except for the ata driver, and it stil

Re: Promise/ATA-Raid making panic in -CURRENT?

> > I finally pulled the Promise out and it boots. > Since I > > need it for some Windows apps on the same box I > put it > > back in and commented some lines in ata driver > > regarding the detection of Promise Fasttrak > > controllers and it boots now w/o detecting it. > > This is strange, the

Re: Promise/ATA-Raid making panic in -CURRENT?

It seems Tom Servo wrote: > I finally pulled the Promise out and it boots. Since I > need it for some Windows apps on the same box I put it > back in and commented some lines in ata driver > regarding the detection of Promise Fasttrak > controllers and it boots now w/o detecting it. This is stran

Re: Promise/ATA-Raid making panic in -CURRENT?

> > Here's the box: > > > > Asus CUV4X-D mainboard, VIA 694X, dual-capable > > 2x P3-933, 768MB PC133 RAM in 3 DIMM(s) > > Two IBM IC35L 60.1GB disks on first IDE > > Pioneer DVD-A05SZ on second IDE > > Two IBM IC35L 60.1GB on Promise Fasttrak TX2 > > (PDC20268/70) in RAID0 > > > > How do I dump

Re: Promise/ATA-Raid making panic in -CURRENT?

It seems Tom Servo wrote: > > Hmm, I need alot more info the, board chipset, what > > exact > > Promise controller etc etc, and of cause the usual > > dmesg > > Here's the box: > > Asus CUV4X-D mainboard, VIA 694X, dual-capable > 2x P3-933, 768MB PC133 RAM in 3 DIMM(s) > Two IBM IC35L 60.1GB dis

Re: Promise/ATA-Raid making panic in -CURRENT?

> > I was in a hurry yesterday and let the kernel > compile > > w/o the ata driver while being under the shower. > > Without the ata driver it does boot. Just wanted > to > > let you know. I'll take the Promise out when I got > > some more time (latest friday evening). > > Hmm, I need alot more

Re: Promise/ATA-Raid making panic in -CURRENT?

It seems Tom Servo wrote: > > The "bad ivar request (4)" message does *not*?come > > from the ATA driver, you must have something else > > that is ruining your day... Does it boot if you > > take out the promise board ? > > I was in a hurry yesterday and let the kernel compile > w/o the ata drive

Re: Promise/ATA-Raid making panic in -CURRENT?

> The "bad ivar request (4)" message does *not* come > from the ATA driver, you must have something else > that is ruining your day... Does it boot if you > take out the promise board ? I was in a hurry yesterday and let the kernel compile w/o the ata driver while being under the shower. Without

Re: Promise/ATA-Raid making panic in -CURRENT?

> > I checked and compiled the recent -CURRENT tree, > > buildworld and buildkernel goes all fine. > > > > When booting it seems to crash on initialization > of my > > Promise controller and get "bad ivar request (4)". > I > > stripped all possible drivers out of the > kernelconfig, > > except fo

Re: Promise/ATA-Raid making panic in -CURRENT?

It seems Tom Servo wrote: > Hi! > > I checked and compiled the recent -CURRENT tree, > buildworld and buildkernel goes all fine. > > When booting it seems to crash on initialization of my > Promise controller and get "bad ivar request (4)". I > stripped all possible drivers out of the kernelconf

Promise/ATA-Raid making panic in -CURRENT?

Hi! I checked and compiled the recent -CURRENT tree, buildworld and buildkernel goes all fine. When booting it seems to crash on initialization of my Promise controller and get "bad ivar request (4)". I stripped all possible drivers out of the kernelconfig, except for the ata driver, and it stil

NULLFS panic in -CURRENT

My -CURRENT box got this panic tonight. Apparently, null_inactive tries to vput NULL lowervp vnode, but how lowervp has managed to become NULL is not immediately clear for me :( I have crash dump available, if anyone is interested. #0 dumpsys () at ../../../kern/kern_shutdown.c:492 #1 0xc01f4a

Re: kernel panic in -current, ithread or newcard related ?

On 17-Apr-01 Jesper Skriver wrote: > On Mon, Apr 16, 2001 at 08:10:37PM -0700, John Baldwin wrote: >> >> On 15-Apr-01 Jesper Skriver wrote: >> > About every other time I boot my IBM ThinkPad 600E I get this panic >> > (hand typed, as I don't have a second machine here to be able to use a >> > se

Re: kernel panic in -current, ithread or newcard related ?

On Mon, Apr 16, 2001 at 08:10:37PM -0700, John Baldwin wrote: > > On 15-Apr-01 Jesper Skriver wrote: > > About every other time I boot my IBM ThinkPad 600E I get this panic > > (hand typed, as I don't have a second machine here to be able to use a > > serial console). > > > > Fatal trap 12: page

RE: kernel panic in -current, ithread or newcard related ?

On 15-Apr-01 Jesper Skriver wrote: > About every other time I boot my IBM ThinkPad 600E I get this panic > (hand typed, as I don't have a second machine here to be able to use a > serial console). > > Fatal trap 12: page fault while in kernel mode > Fault virtual address = 0x28 It's a null poin

kernel panic in -current, ithread or newcard related ?

About every other time I boot my IBM ThinkPad 600E I get this panic (hand typed, as I don't have a second machine here to be able to use a serial console). Fatal trap 12: page fault while in kernel mode Fault virtual address = 0x28 Fault code = supervisor read, page

Re: NFS/VM panic in current with INVARIANTS

: :It looks like you guys got it! What is currently checked in (by Assar) :is working fine! :-) : :M Excellent news! -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: NFS/VM panic in current with INVARIANTS

It looks like you guys got it! What is currently checked in (by Assar) is working fine! :-) M > :--=-=-= > : > :Matt Dillon <[EMAIL PROTECTED]> writes: > :> Well, yes... that's essentially what I suggested. You didn't say > :> anything about removing the externalized inlines, which is w

Re: NFS/VM panic in current with INVARIANTS

> On Tue, Dec 26, 2000 at 02:00:54PM +0200, Mark Murray wrote: > > > I'm getting a reliable panic on CURRENT (2000/12/26) with INVARIANTS > > set. I suppose I could "fix" this by taking out INVARIANTS, but it > > seems to make more sense to try to get it fixed. > > Do you have NFS compiled in to

Re: NFS/VM panic in current with INVARIANTS

:--=-=-= : :Matt Dillon <[EMAIL PROTECTED]> writes: :> Well, yes... that's essentially what I suggested. You didn't say :> anything about removing the externalized inlines, which is what you :> do in your patch. Looks like a fine patch to me. : :Except it didn't work. Now here's a

Re: NFS/VM panic in current with INVARIANTS

Matt Dillon <[EMAIL PROTECTED]> writes: > Well, yes... that's essentially what I suggested. You didn't say > anything about removing the externalized inlines, which is what you > do in your patch. Looks like a fine patch to me. Except it didn't work. Now here's a patch that survive

Re: NFS/VM panic in current with INVARIANTS

:Matt Dillon <[EMAIL PROTECTED]> writes: :> We can't just go do an end-run around the established API as a :> hack around the problem. : :I fail too se how my suggestion would change the API at all, but in :case I was unclear, diffs are below. : :/assar : Well, yes... that's essential

Re: NFS/VM panic in current with INVARIANTS

Matt Dillon <[EMAIL PROTECTED]> writes: > We can't just go do an end-run around the established API as a > hack around the problem. I fail too se how my suggestion would change the API at all, but in case I was unclear, diffs are below. /assar Index: vm_zone.c

Re: NFS/VM panic in current with INVARIANTS

: :Matt Dillon <[EMAIL PROTECTED]> writes: :> I think the only real solution is to rip out the externally visible :> zalloc/zfree inlines and replace them with real routines. I will happily :> do this, those inlines have always been an eyesore to me and the :> performance benefit

Re: NFS/VM panic in current with INVARIANTS

Matt Dillon <[EMAIL PROTECTED]> writes: > I think the only real solution is to rip out the externally visible > zalloc/zfree inlines and replace them with real routines. I will happily > do this, those inlines have always been an eyesore to me and the > performance benefit is mini

Re: NFS/VM panic in current with INVARIANTS

:Do you have NFS compiled in to the kernel? I've had trouble using :INVARIANTS in the kernel and NFS as a module many times - it always :panics in the zone allocation stuff. : :(Either you always need to compile modules with the same INVARIENTS :options as the kernel, or we need to fix INVARIENTS

Re: NFS/VM panic in current with INVARIANTS

On Tue, Dec 26, 2000 at 02:00:54PM +0200, Mark Murray wrote: > I'm getting a reliable panic on CURRENT (2000/12/26) with INVARIANTS > set. I suppose I could "fix" this by taking out INVARIANTS, but it > seems to make more sense to try to get it fixed. Do you have NFS compiled in to the kernel? I

Re: NFS/VM panic in current with INVARIANTS

:Hi Matt : :I'm getting a reliable panic on CURRENT (2000/12/26) with INVARIANTS :set. I suppose I could "fix" this by taking out INVARIANTS, but it :seems to make more sense to try to get it fixed. : :The panic() is "freeing free entry", and the traceback (minus most :of the numbers) is: : :panic

NFS/VM panic in current with INVARIANTS

Hi Matt I'm getting a reliable panic on CURRENT (2000/12/26) with INVARIANTS set. I suppose I could "fix" this by taking out INVARIANTS, but it seems to make more sense to try to get it fixed. The panic() is "freeing free entry", and the traceback (minus most of the numbers) is: panic zerror zf

Re: [jhb@FreeBSD.org: RE: Panic in -current]

> I would like to see full dump of 'vidcontrol -i adapter', > 'vidcontrol -i mode' and dmesg after the vesa module is loaded > (you get very verbose output from the vesa module init code > if you boot the kernel with 'boot -v'). I think this is what you asked for, otherwise please let me know. B

Re: [jhb@FreeBSD.org: RE: Panic in -current]

>Andrea Campi <[EMAIL PROTECTED]> writes: >> Ok, I will try each one. At the moment, I'm using logo_saver. >> I will let you know. > >Take a long hard look at vesa_set_mode() and vesa_set_origin() in >sys/i386/isa/vesa.c. If the panic occurs while the console is still in >text mode, the bug is in

Re: [jhb@FreeBSD.org: RE: Panic in -current]

Andrea Campi <[EMAIL PROTECTED]> writes: > Ok, I will try each one. At the moment, I'm using logo_saver. > I will let you know. Take a long hard look at vesa_set_mode() and vesa_set_origin() in sys/i386/isa/vesa.c. If the panic occurs while the console is still in text mode, the bug is in vesa_se

Re: [jhb@FreeBSD.org: RE: Panic in -current]

Sorry, I guess I should specify that this is a desktop with APM enabled in the BIOS, but not being used otherwise... VESA module loaded. #uname -a FreeBSD cae88-102-101.sc.rr.com 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sat Dec 2 16:07:54 EST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/RHIANNON

Re: [jhb@FreeBSD.org: RE: Panic in -current]

Just as a data point, I just tried this as well... The daemon saver was ok, the fire saver was ok, but as soon as I loaded logo_saver and it activated, I got a 'dc0 timeout'(?) and I was unable to access any of the vtys after that... I could switch vtys, but could not type anything. The fire_sa

Re: [jhb@FreeBSD.org: RE: Panic in -current]

On 05-Dec-00 Andrea Campi wrote: >> > More details: this is an IBM Thinkpad laptop with APM enabled and in the >> > kernel. >> > As usual, any hint is more than welcome. This used to work... >> >> Which screen saver? Does it do it with all of them? Just graphical ones, >> just >> text ones, ju

Re: [jhb@FreeBSD.org: RE: Panic in -current]

> > More details: this is an IBM Thinkpad laptop with APM enabled and in the > > kernel. > > As usual, any hint is more than welcome. This used to work... > > Which screen saver? Does it do it with all of them? Just graphical ones, just > text ones, just green_saver, etc.? Rrrright... I can as

Re: [jhb@FreeBSD.org: RE: Panic in -current]

On 05-Dec-00 Andrea Campi wrote: >> > >> > db> x/i,10 0xc025ad3c >> > scrn_timer: pushl %ebp >> > [...] >> > >> > nm just confirmed this, so it definitely looks like scrn_timer is to blame >> > here. Any other instructions? ;-) For the time being, vidcontrol -t off >> > (seems to) keep the

Re: [jhb@FreeBSD.org: RE: Panic in -current]

> > > > db> x/i,10 0xc025ad3c > > scrn_timer: pushl %ebp > > [...] > > > > nm just confirmed this, so it definitely looks like scrn_timer is to blame > > here. Any other instructions? ;-) For the time being, vidcontrol -t off > > (seems to) keep the machine up. > > > > Bye, > > Andrea

Re: [jhb@FreeBSD.org: RE: Panic in -current]

> > Bad callout handler: c_func = 0xc025ad3c, c_arg=0xc0338460, c_flags=7 > > > > First I tried a > > > > db> x/i,10 0xc025ad3c > > scrn_timer: pushl %ebp > > [...] > > > > nm just confirmed this, so it definitely looks like scrn_timer is to blame > > here. Any other instructions? ;-) For t

Re: [jhb@FreeBSD.org: RE: Panic in -current]

On 29-Nov-00 Andrea Campi wrote: >> Then when it panics write down the values that get printed out. Next, >> do 'nm /sys/compile/MYKERNEL/kernel.debug | sort' and look for the function >> whose address matches the c_func address printed out, then send this info >> back >> please. :) > > This ti

Re: [jhb@FreeBSD.org: RE: Panic in -current]

> Then when it panics write down the values that get printed out. Next, > do 'nm /sys/compile/MYKERNEL/kernel.debug | sort' and look for the function > whose address matches the c_func address printed out, then send this info back > please. :) This time it took me 1 hour to get the panic, compar

Re: [jhb@FreeBSD.org: RE: Panic in -current]

On 29-Nov-00 Andrea Campi wrote: >> >> We want mtxd_file and mtxd_line. If you look at the output of the last >> command, it will probably look something like this: > > ../../kern/kern_timeout.c, line 139 Hmm, and the failed assertion was: panic: mutex Giant owned at ../../kern/kern_intr.c:2

Re: [jhb@FreeBSD.org: RE: Panic in -current]

> > We want mtxd_file and mtxd_line. If you look at the output of the last > command, it will probably look something like this: ../../kern/kern_timeout.c, line 139 Hope it helps, Andrea -- Andrea Campi mailto:[EMAIL PROTECTED] I.NET S.p.A.

RE: Panic in -current

On 28-Nov-00 Andrea Campi wrote: > Latest (this night) current, no system activity: > > panic: mutex Giant owned at ../../kern/kern_intr.c:238 > > I can sen you kernel conf if needed. > > Is this known or should I invest some time to debug it? Eek! I haven't seen this. If you can reproduce

Panic in -current

Latest (this night) current, no system activity: panic: mutex Giant owned at ../../kern/kern_intr.c:238 I can sen you kernel conf if needed. Is this known or should I invest some time to debug it? Bye, Andrea -- 0 and 1. Now what could be so hard about that? To Unsubsc

panic in -current with pcm and xl0

[I had sent this mail to -current before, but no one replied. I'm trying again.] I havne't been able to get my machine to boot with pcm enabled since Feb 5. The last working kernel I have is from Jan 18. Here's the panic (I have a debug kernel lying around from this panic): Here's the panic:

panic in -current from 02/05

I got a panic from -current (02/05 approx 4am EST) It looks like a problem with the pcm driver. I've removed pcm from my config, and my machine boots ok now. I can also boot fine with pcm in my config from a kernel and world from jan 18th. Here's my config (when it panics): config file with

Re: Repeatable panic in current, cause Netscape

On Wed, Sep 29, 1999 at 07:42:50PM +0200, Marcel Moolenaar <[EMAIL PROTECTED]> wrote: > > The latest -current system crashes while starting up Netscape, mine > > version is 4.61, Linux one. It's fully repeatable in my case. I got > > crash dump and here's my dmesg and gdb trace: > > Make sure th

Re: Repeatable panic in current, cause Netscape

Vallo Kallaste wrote: > The latest -current system crashes while starting up Netscape, mine > version is 4.61, Linux one. It's fully repeatable in my case. I got > crash dump and here's my dmesg and gdb trace: Make sure that the linux module is as uptodate as the kernel is. As a rule of thumb: r

Re: Repeatable panic in current, cause Netscape

On Wed, Sep 29, 1999 at 09:51:49AM -0700, Alfred Perlstein <[EMAIL PROTECTED]> wrote: > excellent, using kgbd, can you please type "up" until you hit > frame 5 and print the value of the ndp and some of the other > variables? A listing of the code at that location would also > be great. ('list'

Re: Repeatable panic in current, cause Netscape

On Wed, 29 Sep 1999, Vallo Kallaste wrote: > Hello > > The latest -current system crashes while starting up Netscape, mine > version is 4.61, Linux one. It's fully repeatable in my case. I got > crash dump and here's my dmesg and gdb trace: > > Copyright (c) 1992-1999 The FreeBSD Project. >

Repeatable panic in current, cause Netscape

Hello The latest -current system crashes while starting up Netscape, mine version is 4.61, Linux one. It's fully repeatable in my case. I got crash dump and here's my dmesg and gdb trace: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents

panic in -current (trap 12)

This is with a current kernel - a kernel built 2 days ago runs ok. The system crashes at boot, just after the disk checks. I don't have a core dump, only the message printed on screen: fault code: supervisor read , page not present instruction pointer: 0xc0175396 from my kernel: c0175234 t vfs