We have a box running 6.2-RELEASE smoothly, once we boot
with 6.3-RELEASE. It panics in hptmv0, I have kernel dump available.
Any ideas?
Regards,
Rong-En Fan
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xfffb5444efc5
fault code = supervisor read
Hi all,
we are experiencing repeated crash on a Dell PowerEdge 2950 (rev 1 or 2).
FBSD release is 6.2-RELEASE-p5 , AMD64. 2xXeon QuadCore and 8G of Ram.
MySQL Version is 5.0.41 with following configuration settings:
set-variable= key_buffer=768M
set-variable= table_cache=800
On Mon, Feb 04, 2008 at 02:08:32PM +0700, Eugene Grosbein wrote:
Personally, I never understood the concept of dial-in and call-out
devices on FreeBSD. I ran BBS software for years on both Apple II
hardware and PC hardware; there was no distinction between such devices.
A serial port is a
On Mon, Feb 04, 2008 at 02:08:32PM +0700, Eugene Grosbein wrote:
Personally, I never understood the concept of dial-in and call-out
devices on FreeBSD. I ran BBS software for years on both Apple II
hardware and PC hardware; there was no distinction between such devices.
A serial
On Mon, Feb 04, 2008 at 12:50:32PM +, Primeroz lists wrote:
we are experiencing repeated crash on a Dell PowerEdge 2950 (rev 1 or 2).
FBSD release is 6.2-RELEASE-p5 , AMD64. 2xXeon QuadCore and 8G of Ram.
MySQL Version is 5.0.41 with following configuration settings:
{snip}
There's
Just wanted to point out that anyway our crash is a Kernel panic crash and
not a Mysqld crash.
Platform is AMD64 so , i'm don't think it can be a problem of process size :
$ sudo -u mysql limits
Resource limits (current):
cputime infinity secs
filesize infinity kB
On Mon, Feb 04, 2008 at 05:10:20AM -0800, Jeremy Chadwick wrote:
Also, the above mechanism must be fairly old, because I imagine it would
be more effective to utilise kqueue/kevent to inform said programs of
when the serial port is available for use.
The kqueue/kevent had appeared only in 4.x
There's additional information needed to help with this:
1) Contents of /boot/loader.conf
empty
2) What scheduler you're using in your kernel configuration
We using the 4bsd Scheduler (ULE is commented out in kernel conf)
3) Your kernel configuration in its entirity, if possible
On Mon, Feb 04, 2008 at 12:50:32PM +, Primeroz lists wrote:
Hi all,
we are experiencing repeated crash on a Dell PowerEdge 2950 (rev 1 or 2).
FBSD release is 6.2-RELEASE-p5 , AMD64. 2xXeon QuadCore and 8G of Ram.
MySQL Version is 5.0.41 with following configuration settings:
On Mon, Feb 04, 2008 at 02:50:09PM +, Primeroz lists wrote:
Just wanted to point out that anyway our crash is a Kernel panic crash and
not a Mysqld crash.
But the process that's inducing the panic *every time* is mysqld; this
you've already confirmed. To me this means that mysqld is
on 01/02/2008 11:38 Vojtech Pavlik said the following:
On Fri, Feb 01, 2008 at 11:35:33AM +0200, Andriy Gapon wrote:
I compared FreeBSD and Linux sources more thoroughly and found the
following:
http://lxr.linux.no/linux+v2.6.24/drivers/input/mouse/psmouse-base.c#L464
static int
On Mon, Feb 04, 2008 at 04:35:13PM +, Primeroz lists wrote:
The vm_map.c does not contain a call to the vm_map_unlock() at the
line 3074.
Mine does ... is Revision *1.366.2.3 *on Freebsd CVS for vm_map.c , CVS TAG
RELENG_6_2
Not according to either the kgdb output you included or
We use mysql-server-5.0.45 (fairly old, since newest is 5.0.51a); yours
is a bit older. I'll have to look at the ChangeLog between 5.0.41 and
5.0.51a to see if there's any relevant changes which might give hints to
what's causing it.
I don't see any changes relevant between 5.0.41 and
Personally, I never understood the concept of dial-in and call-out
devices on FreeBSD. I ran BBS software for years on both Apple II
hardware and PC hardware; there was no distinction between such devices.
A serial port is a serial port. Chances are I'm not understanding why
The vm_map.c does not contain a call to the vm_map_unlock() at the
line 3074.
Mine does ... is Revision *1.366.2.3 *on Freebsd CVS for vm_map.c , CVS TAG
RELENG_6_2
Please, rebuild you kernel from scratch. In case this does not help,
I ask you to show the backtrace from the ddb. Also, to
Personally, I never understood the concept of dial-in and call-out
devices on FreeBSD. I ran BBS software for years on both Apple II
hardware and PC hardware; there was no distinction between such devices.
A serial port is a serial port. Chances are I'm not understanding why
there's a
On Mon, Feb 04, 2008 at 07:04:19AM -0800, Jeremy Chadwick wrote:
But the process that's inducing the panic *every time* is mysqld; this
you've already confirmed. To me this means that mysqld is responsible
for tickling some sort of condition that causes a panic; it could be the
fault of mysqld or
Hello, Ivan.
You wrote 3 февраля 2008 г., 23:35:44:
If so, this is the same class of errors as ZFS (some would call it
tuning errors)
Why this is ever possible on stable (I know, that stable doesn't
meand really stable these days, but at least it is not -CURRENT,
whcih can be experimental)
Hello List,
I am trying to debug a 6.1 panic. When I run kgdb kernel.debug
/var/crash/vmcore.7 all I get is:
kgdb: kvm_read: invalid address (0x24)
kgdb: kvm_read: invalid address (0x24)
kgdb: kvm_read: invalid address (0x24)
kgdb: kvm_read: invalid address (0x24)
kgdb: kvm_read: invalid
On Mon, Feb 04, 2008 at 02:19:05PM +, Primeroz lists wrote:
We using the 4bsd Scheduler (ULE is commented out in kernel conf)
That's good, as it confirms you're not hitting ULE bugs.
3) Your kernel configuration in its entirity, if possible :-)
attached
I don't see anything in your
Stephen Clark wrote:
Hello List,
I am trying to debug a 6.1 panic. When I run kgdb kernel.debug
/var/crash/vmcore.7 all I get is:
kgdb: kvm_read: invalid address (0x24)
kgdb: kvm_read: invalid address (0x24)
kgdb: kvm_read: invalid address (0x24)
kgdb: kvm_read: invalid address (0x24)
kgdb:
On Monday 04 February 2008 11:38:06 am Stephen Clark wrote:
Stephen Clark wrote:
Hello List,
I am trying to debug a 6.1 panic. When I run kgdb kernel.debug
/var/crash/vmcore.7 all I get is:
kgdb: kvm_read: invalid address (0x24)
kgdb: kvm_read: invalid address (0x24)
kgdb:
On 03/01/2008, at 11:56 AM, Marc G. Fournier wrote:
As noted in my original report, this isn't a nagios issue per se ...
my first
experience with this issue was with Azureus/java ... so its a
'threading issue
in general' ...
A patch to force the package to link against libthr() has been
Ok, subsystem can not work efficiently. Degrade service. Swith to
one 512 byte sector per second speed mode. Disable all caches, doesn't
try to work with all features. Complain 10 times/second on console (and
dmesg buffer). Ok. But PANIC?! NO-NO-NO!!!
Yes given the fact I had a panic and
At 06:17 PM 2/4/2008, Jarrod Sayers wrote:
On 03/01/2008, at 11:56 AM, Marc G. Fournier wrote:
As noted in my original report, this isn't a nagios issue per se ...
my first
experience with this issue was with Azureus/java ... so its a
'threading issue
in general' ...
A patch to force the
Primeroz lists wrote:
Hi all,
we are experiencing repeated crash on a Dell PowerEdge 2950 (rev 1 or 2).
FBSD release is 6.2-RELEASE-p5 , AMD64. 2xXeon QuadCore and 8G of Ram.
SNIP
$ sudo kgdb /usr/obj/usr/src/sys/PE2950/kernel.debug vmcore.2
SNIP
This back trace will be useless, I
Hi,
I'm having trouble mounting external NTFS hard drive using fusefs-ntfs
port on Dell Latitude D620.
devil# uname -an
FreeBSD devil.micom.mng.net 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #3:
Tue Feb 5 10:29:24 ULAT 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/DEVIL i386
devil#
Hi,
I'm having trouble using Orinoco Silver a/b/g combo pcmcia card on Dell
Latitude D620.
It happens in following order:
1. First I reboot FreeBSD-7.0 laptop with Orinoco combo card plugged in.
2. Then when I try to unplug the card it panics.
However after rebooting (without plugged in
Is there anything like mount -p that will print the current NFS options
in use? TCP vs UDP, v2 vs v3, read/write sizes etc. It doesn't have to
be in fstab format; I just need to be able to see what the flags are for
an active mount.
This would be useful in tracking down an irritating NFS
On Feb 4, 2008 10:31 PM, Ganbold [EMAIL PROTECTED] wrote:
I'm having trouble mounting external NTFS hard drive using fusefs-ntfs
port on Dell Latitude D620.
I havn't seen this specific problem, but on my Dell XPS 1730
(core-2-duo-extreme) The NTFS-3g mounts doen't seem to shutdown properly.
Hi,
I've upgraded one of my boxes from 6.2 to freeBSD 6.3. I have on-board LSI
Logic 1030 SCSI Ultra4 Adapter, on it I have attached two IBM Ultra-320 SCSI
36GB disks. The machine is IBM xServer 225.
See the dmesg output:
..
mpt0: LSILogic 1030 Ultra4 Adapter port 0xb000-0xb0ff mem
31 matches
Mail list logo
