Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 11 Jul 2002 16:45:58 +0200 (MEST)
From:      Lutz Kittler <Lutz.Kittler@sse-erfurt.de>
To:        "Jonas Sonntag" <js@setcom.de>
Cc:        <freebsd-questions@freebsd.org>
Subject:   has squid shot down the kernel?
Message-ID:  <15661.39462.967156.15091@master.sse-erfurt.de>
In-Reply-To: <KIEEILJCLAIJNFGECHJOAEDADKAA.js@setcom.de>
References:  <KIEEILJCLAIJNFGECHJOAEDADKAA.js@setcom.de>

next in thread | previous in thread | raw e-mail | index | archive | help
Jonas Sonntag writes:
 > hello
 > 
 > our 4.6-stable server has just rebootet itself.
 > this looks to me like squid has caused an error, but how come that the
 > machine reboots itself?
 > has anyone seen this behaviour before?
 > it's squid 2.4_8 from the ports.
 > 
 > here's the log, thanks for any advise:
 > 
 > Jul 11 16:06:56 tesla /kernel:
 > Jul 11 16:06:56 tesla /kernel:
 > Jul 11 16:06:56 tesla /kernel: Fatal trap 12: page fault while in kernel
 > mode
 > Jul 11 16:06:56 tesla /kernel: fault virtual address    = 0x8769c1b2
 > Jul 11 16:06:56 tesla /kernel: fault code               = supervisor read,
 > page not present
 > Jul 11 16:06:56 tesla /kernel: instruction pointer      = 0x8:0xc0199760
 > Jul 11 16:06:56 tesla /kernel: stack pointer            = 0x10:0xd7b03d80
 > Jul 11 16:06:56 tesla /kernel: frame pointer            = 0x10:0xd7b03d9c
 > Jul 11 16:06:56 tesla /kernel: code segment             = base 0x0, limit
 > 0xfffff, type 0x1b
 > Jul 11 16:06:56 tesla /kernel: = DPL 0, pres 1, def32 1, gran 1
 > Jul 11 16:06:56 tesla /kernel: processor eflags = interrupt enabled, resume,
 > IOPL = 0
 > Jul 11 16:06:56 tesla /kernel: current process          = 238 (squid)
 > Jul 11 16:06:56 tesla /kernel: interrupt mask           =
 > Jul 11 16:06:57 tesla /kernel: trap number              = 12
 > Jul 11 16:06:57 tesla /kernel: panic: page fault
 > Jul 11 16:06:57 tesla /kernel:
 > Jul 11 16:06:57 tesla /kernel: syncing disks... 25 1

 Hi,

I had the same problem  not only with squid but with all things that 
access net , eg. slogin , X , smbd and so on. Everytime I got
the same error.
I didnt find any reason.
I did cvsup , I also built new kernel with different options , no way out.
If I started the old kernels I had no troubles.
I installed clean FreeBSD vom CD and everything was alright.
I'm also interested in this error.

 Lutz

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15661.39462.967156.15091>