Pedro Almeida wrote:
I upgraded my system from 6.2 to 7.0 using cvsup.
I'm using ULE and device polling. After doing make installworld and
reboot, the system
don't boot anymore. I have some variables in make.conf, but I don't know
if this the cause of the problem.
CPUTYPE?=p3
CFLAGS= -O2 -pipe
-funroll-loops -ffast-math
COPTFLAGS= -O2 -pipe -funroll-loops -ffast-math
Any ideas of how to fix this? Thanks a lot
Can't work out which disk we are booting from.
Guessed BIOS device 0x not found by probes, defaulting to disk0:
panic: free: guard1 fail @ 0x6c23c
from /usr/src/
The machine passed the memory test while on battery fine. however, while
on battery the checksum failed with i/o errors, it did complete the
checksum normally while on AC. I think my next step will be to try and
disable acpi, and to try and reproduce the error again. i suppose it could
be an issue
7_releng) just a couple days ago in an effort to resolve this issue, to
> no change.
>
>
> Here are the last few lines of the kernel panic (as read through strings):
>
> panic: initiate_write_filepage: dir inum 1576702754 != new 0
> cpuid = 0
> Uptime: 1h42m24s
> Physical
Nathan Alan Souer wrote:
>> Nathan Alan Souer wrote:
>>> In advance, I appreciate any help that anyone has to offer. When my
>>> laptop
>>> is running on battery and there is heavy i/o on the disk The machine
>>> kernel panics and reboots. I have updated my base system to current
>>> (7_releng) jus
> Nathan Alan Souer wrote:
>> In advance, I appreciate any help that anyone has to offer. When my
>> laptop
>> is running on battery and there is heavy i/o on the disk The machine
>> kernel panics and reboots. I have updated my base system to current
>> (7_releng) just a couple days ago in an effor
> Nathan Alan Souer wrote:
>> In advance, I appreciate any help that anyone has to offer. When my
>> laptop
>> is running on battery and there is heavy i/o on the disk The machine
>> kernel panics and reboots. I have updated my base system to current
>> (7_releng 2/9/08) just a couple days ago in a
Nathan Alan Souer wrote:
In advance, I appreciate any help that anyone has to offer. When my laptop
is running on battery and there is heavy i/o on the disk The machine
kernel panics and reboots. I have updated my base system to current
(7_releng) just a couple days ago in an effort to resolve th
.
Here are the last few lines of the kernel panic (as read through strings):
panic: initiate_write_filepage: dir inum 1576702754 != new 0
cpuid = 0
Uptime: 1h42m24s
Physical memory: 1003 MB
Dumping 147 MB: 132 116 100 84 68 52 36 20 4
Should I just look into disabling acpi? Please let me know what
we were trying to use a 8KB sector size on the geli
provider, which caused the panic.
using 4KB as sector size works.
the command before:
geli init -bP -e 3DES -K /my/test.key -s 8192 /dev/da0
and after:
geli init -bP -e 3DES -K /my/test.key -s 4096 /dev/da0
thank you for info. i use
> during copying ~350GB from one volume to another on
> the local machine (separate disks, separate fs's) i
> get the following panic:
> start = 0, len = 23691, fs = /newdata
> panic: ffs_alloccg: map corrupted
> KDB: enter: panic
> [ thread pid 835 tid 10070 ]
&g
On Fri, February 1, 2008 16:30, [EMAIL PROTECTED]@mgEDV.net wrote:
>
> hi folks,
>
> during copying ~350GB from one volume to another on
> the local machine (separate disks, separate fs's) i
> get the following panic:
>
> start = 0, len = 23691, fs = /newdata
> p
hi folks,
during copying ~350GB from one volume to another on
the local machine (separate disks, separate fs's) i
get the following panic:
start = 0, len = 23691, fs = /newdata
panic: ffs_alloccg: map corrupted
KDB: enter: panic
[ thread pid 835 tid 10070 ]
stopped at kdb_enter +0x2c:
On Jan 29, 2008 8:19 AM, Mel <[EMAIL PROTECTED]> wrote:
> On Tuesday 29 January 2008 13:04:48 Drew wrote:
> > Hello,
> > I'm posting this in the hopes that someone can point me in the right
> > direction, and that it may possibly help someone else. The kernel pani
On Tuesday 29 January 2008 13:04:48 Drew wrote:
> Hello,
> I'm posting this in the hopes that someone can point me in the right
> direction, and that it may possibly help someone else. The kernel panic
> below is generated at boot, and is reproduceable as many times as you want
Hello,
I'm posting this in the hopes that someone can point me in the right
direction, and that it may possibly help someone else. The kernel panic
below is generated at boot, and is reproduceable as many times as you want
to do it. A few details on the hardware, the machine is a couple of
Michael Lednev wrote:
Hello, Kris.
On 2 ?? 2008 ?., 14:07:36 you wrote:
KK> Yes, long-standing issue with unexpected mounted device removal. Don't
KK> do that :)
Thanks, already found this PR, it's already 5 yo, wow :)
There have been some recent partial workarounds committed in curren
Hello, Kris.
On 2 ?? 2008 ?., 14:07:36 you wrote:
KK> Yes, long-standing issue with unexpected mounted device removal. Don't
KK> do that :)
Thanks, already found this PR, it's already 5 yo, wow :)
--
Best regards,
Michael mailto:[EMAIL PROTECTED]
___
Michael Lednev wrote:
Hello, freebsd-questions.
After the following actions:
1. Insert USB Flash
2. mount_msdosfs /dev/da0s1 /mnt
3. Remove USB Flash
4. umount -f /mnt
I have kernel panic every time. Is this a known issue? My system is
FreeBSD 7.0-RC1 from 1.01.2008.
Yes, long-standing
Hello, freebsd-questions.
After the following actions:
1. Insert USB Flash
2. mount_msdosfs /dev/da0s1 /mnt
3. Remove USB Flash
4. umount -f /mnt
I have kernel panic every time. Is this a known issue? My system is
FreeBSD 7.0-RC1 from 1.01.2008.
--
Best regards,
Michael
Iain Dooley wrote:
> i'm just running a web application on it. it's a total pain though. i
> should have just bought a late model second hand p4 or something rather
> than a state of the art machine. i'm too out of touch with modern
> hardware to have known what i was getting myself into. live and
hi ivan,
uname -a
FreeBSD HOSTNAME 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30
UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386
running on dual quad core intel xeons with 4gb ram.
Are you using PAE? (probably not if this is the generic SMP configuration).
no, i checked
Iain Dooley wrote:
> hi all,
>
> uname -a
> FreeBSD HOSTNAME 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30
> UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386
>
> running on dual quad core intel xeons with 4gb ram.
Are you using PAE? (probably not if this is the generic SMP con
, def32 1, gran 1
processor eflags = resume, IOPL = 0
current process = 12 (idle: cpu5)
trap number = 12
panic: page fault
cpuid = 5
uptime 24m41s
cannot dump. no dump device specified
i've configured the dump device and will follow the kernel debugging
details in the handbook if it happens
= DPL 0, pres 1, def32 1, gran 1
processor eflags = resume, IOPL = 0
current process = 12 (idle: cpu5)
trap number = 12
panic: page fault
cpuid = 5
uptime 24m41s
cannot dump. no dump device specified
i've configured the dump device and will follow the kernel debugging
details i
, pres 1, def32 1, gran 1
processor eflags = resume, IOPL = 0
current process = 12 (idle: cpu5)
trap number = 12
panic: page fault
cpuid = 5
uptime 24m41s
cannot dump. no dump device specified
i've configured the dump device and will follow the kernel debugging details in
the handbook if it ha
Hi!
Just a few minutes ago, I noticed one of my machines was stuck with this
message on the console:
GEOM_RAID5: KASSERT in line 1352
panic: incompetent for BIO_WRITE
cpuid = 0
Uptime: 1h33m15s
GEOM_RAID5: raid5/raid5: device is still open, so it cannot be
definitely removed.
GEOM_RAID5: raid5
have done that a few times.
If you can, separate the power to the hard drives to separate lines
from the power supply rather than daisy chaining a power line with
multiple connectors on it.
Have you tried other bootable OS's just to see if they crash too?
I was on the verge of panic mysel
At 07:32 PM 12/15/2007, jekillen wrote:
On Dec 15, 2007, at 5:21 PM, jekillen wrote:
Hello;
I have had an AMD64 754 system that I have 64 bit SCSI card and
two 15k rpm SCSI drives. It has been running fine with FreeBSD v 6.0
for about two years now. I have several things I wanted to change
and
On Dec 15, 2007, at 5:21 PM, jekillen wrote:
Hello;
I have had an AMD64 754 system that I have 64 bit SCSI card and
two 15k rpm SCSI drives. It has been running fine with FreeBSD v 6.0
for about two years now. I have several things I wanted to change
and reconfigure, software wise, and hardware
Hello;
I have had an AMD64 754 system that I have 64 bit SCSI card and
two 15k rpm SCSI drives. It has been running fine with FreeBSD v 6.0
for about two years now. I have several things I wanted to change
and reconfigure, software wise, and hardware wise. The first was a new
case which I got toda
many people using, looking at or working
on the FreeBSD kernel, I knew it had to be something other than just
my applications causing a kernel panic.
thanks,
kelly
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fr
Kelly Martin wrote:
I'm getting daily kernel panics. The server was running fine for about
a month, the only changes I've made recently have been to update all
my ports. It's running on older i386 hardware, no special devices
Like the others said -- I'd seriously suspect hardware problems. Mem
Kelly Martin wrote:
On Nov 9, 2007 10:41 AM, Kris Kennaway <[EMAIL PROTECTED]> wrote:
This looks pretty suspicious to me, I'd guess your hardware has failed.
This same hardware has run OpenBSD for years.
Not really relevant. When something makes the transition from "working"
to "broken" th
/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html
Thanks, I've setup a dump directory now for the next kernel panic...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsu
limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, IOPL = 0
current process = 10 (idle: cpu0)
trap number = 30
panic: reserved (unknown) fault
cupid = 0
Uptime 19h28m38s
Cannot dum
limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, IOPL = 0
current process = 10 (idle: cpu0)
trap number = 30
panic: reserved (unknown) fault
cupid = 0
Uptime 19h28m38s
Cannot dump. No dump device define
files to
the new box, I can reliably crash it after about 20 minutes; often
quicker if I do something else intensive at the same time, like
compile MySQL. Here are the box specs:
ASUS M2NPV-VM motherboard
AMD A64 3800+ 2.4G CPU
...
Most times, I don't even get a core dump. Here's one I did
Kris Kennaway wrote:
Doug Poland wrote:
I'd like to report the details but I'm unfamiliar with the process.
Should I post here on -questions or on -current mailing list?
-stable.
I know 7-BETA1 is currently in a region somewhere between -current and
-stable but I thought the -current list
Kris Kennaway wrote:
Doug Poland wrote:
I'd like to report the details but I'm unfamiliar with the process.
Should I post here on -questions or on -current mailing list?
-stable.
Looks like the issue is: kernel: current process = 46 (ath0 taskq)
Well, unfortunately that doesn't really say
Doug Poland wrote:
I'd like to report the details but I'm unfamiliar with the process.
Should I post here on -questions or on -current mailing list?
-stable.
Looks like the issue is: kernel: current process = 46 (ath0 taskq)
Well, unfortunately that doesn't really say anything. Read the c
I'd like to report the details but I'm unfamiliar with the process.
Should I post here on -questions or on -current mailing list?
Looks like the issue is: kernel: current process = 46 (ath0 taskq)
--
Regards,
Doug
___
freebsd-questions@freebsd.org m
ig file and
> seeing if that solves it?
Yes, I see that this is the obvious solution if I wanted to just get
my drive working. But I think that this should not cause a panic,
and that I might help track this down. The panic is repeatable.
Also, the drive works if it's plugged in while booti
Hello, list!
Jeg just bought a LaCie external USD hdd to store my pictures. When
I plug it in, it causes my laptop to panic after ~15-20 seconds.
After a reboot (with the disc still plugged in) it functions properly.
These are the messages I get when I plug it in:
umass0: on uhub3
da0 at
> On the machine itself no messages are shown and the machine responds to
> repeated ENTER key presses with the login prompt. Once you enter "root"
> [ENTER] then no further responses (except line feeds as you press ENTER).
>
> What kind of hang is this? Could it be a DoS attack? Or is it some
On a FreeBSD 5.2.1 box that has been in production a long time, I have had
a new type of hang on two days this week, the type of which I have not
seen before. (No recent software/hardware changes).
Symptom: The machine is a web/email server only. It stops receiving new
SSH/HTTP/IMAP/POP connecti
s; and there was no
change from kernel panic and reboot.
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-options.html
>
> You should get a prompt when it panics.
There was no prompt.
> Then you type in "bt" for backtrace.
> Maybe yo
On Saturday 06 October 2007, Joe Altman wrote:
> chthonic.com/crash-crash-crash
Hi,
Do you have "options KDB" in your kernel config file ?
http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-options.html
You should get a prompt when it panics. Then you type in "bt"
NB: I've copied -usb because it looks to me like it's definitely USB
that's implicated; but I still need a clue for getting a crash dump;
-questions seems the place to ask for that.
On Sun, Sep 23, 2007 at 07:57:41PM -0400, Joe Altman wrote:
>
> uname for the machine on which it fails:
>
> 6.2-S
usb3: on ehci0
uhub3: on usb3
Both of thease chipsets freeze at ramdom times under FreeBSD 6.2 and
7-CURRENT (as of a few days ago)
The errors on the screen which dont make it to the log are;
sleeping thread (tid 100015, pid 19) owns a non-sleepable-lock
panic: sleeping thread
cpuid=1
: on usb3
Both of thease chipsets freeze at ramdom times under FreeBSD 6.2 and
7-CURRENT (as of a few days ago)
The errors on the screen which dont make it to the log are;
sleeping thread (tid 100015, pid 19) owns a non-sleepable-lock
panic: sleeping thread
cpuid=1
and
panic: Trying sleep
Hi,
I'm running
> FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007
> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP
I just purchased a nice outboard USB 2.0 drive and, well, I'd like to
leave that drive plugged in while I reboot my machine. However, when I
do so, BTX panics and spews all over the
Jan Henrik Sylvester wrote:
With '/dev/ad0s1 /mnt/ad0s1 ntfs ro,noauto 0 0' in fstab, if I issue
'mount /mnt/ad0s1' twice, I always get a panic with the message:
panic: lockmgr: locking against myself
I should have done some more intelligent research before...
kern/8
Hello!
With '/dev/ad0s1 /mnt/ad0s1 ntfs ro,noauto 0 0' in fstab, if I issue
'mount /mnt/ad0s1' twice, I always get a panic with the message:
panic: lockmgr: locking against myself
If I issue 'mount_ntfs /dev/ad0s1 /mnt/ad0s1' twice, there is no panic.
I on
On Mon, 13 Aug 2007 20:43:45 -0500
Doug Poland <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I've got an HP/Compaq nx7400 and am having trouble with kernel
> loadable object generated by ndisgen. (6.2-STABLE, i386).
>
> Following the man page for ndisgen(4), I have the following files:
>
> -rwx-
pt enabled,
resume, IOPL = 0
Aug 13 16:44:42 hpnx7400 kernel: current process = 5822 (kldload)
Aug 13 16:44:42 hpnx7400 kernel: trap number = 12
Aug 13 16:44:42 hpnx7400 kernel: panic: page fault
Aug 13 16:44:42 hpnx7400 kernel: cpuid = 1
Aug 13 16:44:42 hpnx7400 kernel: Uptime: 8m45s
2 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 44922 (reboot)
panic: from debugger
Uptime: 2h45m36s
Dumping 1022 MB (2 chunks)
chunk 0: 1MB (159 pages) ... ok
chunk 1: 1022MB (261600 pages) 1006 990 974 958 942 926 910 894 878 862
846 830 814 798 782 766 750 734 718 7
On Wed, Jul 25, 2007 at 01:55:45PM +0800, Zhang hw wrote:
> Sometimes when I shutdown my system, it would tell me :
> "...
> All buffers synced
> Swap_pager: I/O error - pagein failed, blkno 744, size 4096, error 5
> panic: swap_pager_force_pagein: read from swap failed
>
Hi,
Cannot dump. No dump device defined.
At least I know what this means. If you don't define a dump device, the
swapper can't dump the corrupted swap data anywhere so you can analyse
it later. Rather than explain here I recommend you, and everyone else in
fact, read and digest these tutori
Sometimes when I shutdown my system, it would tell me :
"...
All buffers synced
Swap_pager: I/O error - pagein failed, blkno 744, size 4096, error 5
panic: swap_pager_force_pagein: read from swap failed
Uptime:...
Cannot dump. No dump device defined.
Automatic reboot in 15 seconds -> pre
Tamouh H. wrote:
> The first thing I'd try is boot direct to the drive, without the RAID card.
> It seems from the dump it paniced after loading the 3ware drivers:
>
> "RocketRAID 232x controller driver v1.02 (Jul 16 2007 17:38:56)
> panic: pmap_mapdev: Couldn'
>
> Hi!
>
> A machine of mine is panicking during cold boot on FreeBSD
> 6.2-RELEASE-p6. No kernel dump is available, as the panic
> occurs so early.
>
> My machine is an Athlon XP 2000+ on an ECS K7S5A-Pro (SIS735
> chipset) with 1GB PC3200 RAM.
>
> The
Hi!
A machine of mine is panicking during cold boot on FreeBSD
6.2-RELEASE-p6. No kernel dump is available, as the panic occurs so early.
My machine is an Athlon XP 2000+ on an ECS K7S5A-Pro (SIS735 chipset)
with 1GB PC3200 RAM.
The root filesystem is a mirror on a 3Ware Escalade 8006-2LP SATA
20 minutes; often
quicker if I do something else intensive at the same time, like
compile MySQL. Here are the box specs:
ASUS M2NPV-VM motherboard
AMD A64 3800+ 2.4G CPU
...
Most times, I don't even get a core dump. Here's one I did get:
panic: double fault
...
#9 0x8
x27;t even get a core dump. Here's one I did get:
panic: double fault
Uptime: 20m26s
Dumping 2014 MB (2 chunks)
chunk 0: 1MB (159 pages) ... ok
chunk 1: 2014MB (515552 pages) 1998 1982 1966 1950 1934 1918 1902
1886 1870 1854 1838 1822 1806 1790 1774 1758 1742 1726 1710 1694 1678
1662 1646
times, I don't even get a core dump. Here's one I did get:
> panic: double fault
> Uptime: 20m26s
> Dumping 2014 MB (2 chunks)
> chunk 0: 1MB (159 pages) ... ok
> chunk 1: 2014MB (515552 pages) 1998 1982 1966 1950 1934 1918 1902
> 1886 1870 1854 1838 1822 1806 1790
box specs:
ASUS M2NPV-VM motherboard
AMD A64 3800+ 2.4G CPU
2 x 1 GB SuperTalent DDR2 667 RAM
2 x 500G Samsung SATA2 drives
MATSHITADVD-ROM SR-8585 DVD drive (ancient)
Most times, I don't even get a core dump. Here's one I did get:
panic: double fault
Uptime: 20m26s
Dumping 2014 MB
. (buildworld log available on request)
However: upon reboot the kernel panics and drops into KDB. (Whereupon
the console freezes ... but that's an old problem.) The specific context:
kbd0 at ukbd0
panic: corrupt spinlock
KDB: enter: panic
[threat pid 0
Hi,
When attempting to backup data to a new 500GB sata HDD I'm getting
a kernel panic, followed by reboot after the 15 second timeout.
I've tried the drive in my XP machine and formated/written to it fine,
I've also tried mounting the drive as a USB2 device via an external
enclo
e problem is, it hasn't been
> fixed.
No, it indicates that there was another problem which:
* may or may not be the same as yours. "Similar panic string" is no
indication of cause.
* may or may not be fixed, because "6.x" encompasses several years of
releases an
Because it's an *old* server, and because 5.4-r should
be a mature enough distribution by now that any bugs
which were going to be fixed would already be fixed.
I could only find one reference to a problem like this
one, and in that case it was happening in 6.x, which
indicates that whatever the p
On Wed, Apr 04, 2007 at 05:51:55PM -0400, m yelle wrote:
> I tried posting this earlier, but it appears my
> message didn't post. Please pardon if it did post
> without my noticing
It did, and I already replied to you. Please read your email.
Kris
pgpMcBpZurU26.pgp
Description: PGP signature
onths. I'm installing to a tested clean/blank scsi
hdd.
After the cd boots, it loads the BTX loader, does a
partial boot sequence then asks for which kernel to
load- acpi, non-acpi, safe, etc. No matter which
option I choose, there is an identical kernel panic
immediately afterwards, every single
On Wed, Apr 04, 2007 at 03:00:34PM -0400, m yelle wrote:
> I'm attempting to install 5.4-r on an old server which
> has been running 4.9-stable for the last few years
> without any problems, with longest uptime of just over
> 6 months. I'm installing to a tested clean/blank scsi
> hdd.
Why are you
t sequence then asks for which kernel to
load- acpi, non-acpi, safe, etc. No matter which
option I choose, there is an identical kernel panic
immediately afterwards, every single time.
Booting from floppies, the kernel panic still occurs.
Is there a a way around this, or do I need to use a
different
Hi,
After 370 days of uptime, I suddenly got an "ffs_valloc: dup alloc"
panic under our production server, for the swap partition.
-
Dump header from device /dev/da0s1b
Architecture: i386
Architecture Version: 2
Dump Length: 4026068992B (3839 MB)
Bloc
ing a large copy, after a while, the kernel panic occurs.
Quoting "Brian A. Seklecki" <[EMAIL PROTECTED]>:
From a troubleshooting standpoint, I would check the following:
1) A Quick Memtest86
2) The management interface to the RAID (functional CLI in FBSD?
otherwise BIOS
FreeBSD store01 6.1-RELEASE-p12 FreeBSD
> 6.1-RELEASE-p12 #0: Mon Jan 22 11:20:03 UTC 2007
>
> I use this machine mainly for backups and NFS mount points. The
> problem is that when I perform backups at night, within 1 hour or so
> the machine reboots because of kernel panic. Th
oblem = is that when I perform backups at night, within 1 hour or so
the machine re= boots because of kernel panic. The exact error message
is:
Mar 31 00:29:05 store01 syslogd: kernel boot file is
/boot/kernel/kernel Mar 31 00:29:05 store01 kernel: start = 0, len =
11431, fs =
/usr
I perform backups at night, within 1 hour or so
the machine reboots because of kernel panic. The exact error message is:
Mar 31 00:29:05 store01 syslogd: kernel boot file is /boot/kernel/kernel
Mar 31 00:29:05 store01 kernel: start = 0, len = 11431, fs = /usr
Mar 31 00:29:05 store01 ker
Rajkumar S wrote:
> On 3/22/07, Sam Leffler <[EMAIL PROTECTED]> wrote:
>> I have no context. I see a device not attaching for some reason. Then
>> /dev/crypto not being present (is cryptodev loaded in the kernel?). But
>> a subject line about a panic.
>
> Th
Well, this means that, since your previous kernel panicked but was not
able to save a coredump, when you boot up from another kernel there is
simply nothing there for savecore to recover. As a result savecore is
reporting that there is nothing to recover for you.
But that's the way to set it up.
On 3/22/07, Rajkumar S <[EMAIL PROTECTED]> wrote:
On 3/22/07, Simon Chang <[EMAIL PROTECTED]> wrote:
> Check out "man savecore" for a list of flags.
Thanks, I will check that out.
I have reinstalled and now starting from scratch to see if I can get
the core dump o
ms like it. I can see where the safe(4) device might depend
> completely on DMA.
>
>
I have no context. I see a device not attaching for some reason. Then
/dev/crypto not being present (is cryptodev loaded in the kernel?). But
a subject line about a panic.
If you've submitted
On 3/22/07, Simon Chang <[EMAIL PROTECTED]> wrote:
Check out "man savecore" for a list of flags.
Thanks, I will check that out.
Have you submitted a formal PR? I have to say that I have not had
experience with that device or driver. What other responses have you
gotten from people?
Yes, 1
On 3/22/07, Sam Leffler <[EMAIL PROTECTED]> wrote:
I have no context. I see a device not attaching for some reason. Then
/dev/crypto not being present (is cryptodev loaded in the kernel?). But
a subject line about a panic.
The device is not attaching because bus_dma_tag_create fu
"Rajkumar S" <[EMAIL PROTECTED]> writes:
> Further to my previous mail.
>
> On 3/20/07, Rajkumar S <[EMAIL PROTECTED]> wrote:
>> safe0 mem 0xf612-0xf6121fff irq 22 at device 10.0 on pci0
>> safe0: cannot allocate DMA tag
>> device_attach: safe0 attach returned 6
>
> While running cryptokeytest
ags="-v -z",
where -v puts in extra debugging information and -z compresses the
coredump so that you save some space.
The panic happens only when safenet driver is complied in., GENERIC
freebsd kernel boots up fine. I am using Axiomtek NA-1281A* I have
reported the details about the p
On 3/16/07, Rajkumar S <[EMAIL PROTECTED]> wrote:
safe0 mem 0xf612-0xf6121fff irq 5 at device 10.0 on pci0
safe0: cannot allocate DMA tag
Hi,
I have managed to track down this issue. The problem was that one
bus_dma_tag_create (at line 300) was failing to create dma tag, and
was returning
Hi,
Thanks for your reply!
On 3/21/07, Simon Chang <[EMAIL PROTECTED]> wrote:
From what you are saying it sounds like you are getting the panic on
bootup. Is that correct?
Yes. immediately on boot up.
In looking through your config I don't see anything that really stands
out
Hey there,
From what you are saying it sounds like you are getting the panic on
bootup. Is that correct?
In looking through your config I don't see anything that really stands
out (although I would use "/var/crash" for dumpdir, and you didn't
specify savecore_flags).
Further to my previous mail.
On 3/20/07, Rajkumar S <[EMAIL PROTECTED]> wrote:
safe0 mem 0xf612-0xf6121fff irq 22 at device 10.0 on pci0
safe0: cannot allocate DMA tag
device_attach: safe0 attach returned 6
While running cryptokeytest from /usr/src/tools/tools/crypto
test 0
cryptokeytest:
turned 6
but the machine remains stable, with no panic. But I still get the
"cannot allocate DMA tag" error that I got when the safenet is
compiled in.
I am not sure if this is normal and I can put the machine live.
If that doesn't give you a clue, you will need to try kernel
debugging
fter I boot with safe module enabled I get a kernel panic.
You do have one of those cards installed, I assume?
Have you tried booting a GENERIC kernel and loading the kernel module
for the safenet support?
If that doesn't give you a clue, you will need to try ker
Hi,
I am trying to get core dump of a kernel panic relating to safenet
driver, so that I can file a meaning full PR or even try to debug
myself. But I am not getting a core dump after panic. I have gone
thorough the developers manual and I believe I have taken care of all
the usual stuff
Hi,
I am trying to install SafeNet 1141 support in one of the freebsd
boxes here. according to safe(4), I have to add "device safe" into my
kernel config and compile to enable hardware crypto acceleration. But
after I boot with safe module enabled I get a kernel panic.
The last coupl
Joe Auty <[EMAIL PROTECTED]> writes:
> I guess the trick here was not considering that user space apps would
> be trying to do a kldload, and that calling upon a module that is
> either missing in /boot/kernel or /boot/modules or resides outside
> of /boot can trigger these panics.
That is
- Original Message -
From: "Mike Meyer" <[EMAIL PROTECTED]>
To: "Ted Mittelstaedt" <[EMAIL PROTECTED]>
Cc: "Joe Auty" <[EMAIL PROTECTED]>; "Daan Vreeken [PA4DAN]"
<[EMAIL PROTECTED]>; "Kip Macy" <[EMAIL PROTECT
- Original Message -
From: "Joe Auty" <[EMAIL PROTECTED]>
To: "Ted Mittelstaedt" <[EMAIL PROTECTED]>
Cc: "Daan Vreeken [PA4DAN]" <[EMAIL PROTECTED]>; "Kip Macy"
<[EMAIL PROTECTED]>; ;
Sent: Monday, February 26, 2007 10:01
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sort of...
Thanks for everybody that has helped me!
It turns out I had a couple of rc.d scripts in /usr/local/etc/rc.d
that were doing kldloads: rtc.sh and kqemu.sh - one of these was
causing the panic. It might be worthwhile adding to the
301 - 400 of 1049 matches
Mail list logo
