Le Mon, 16 Mar 2009 14:49:43 -0600,
Dan Allen danalle...@airwired.net:
For now, can you just provide the stack trace?
How do I do this? Is there a tool that I run against the core dump?
See
http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html
Regards.
Le Tue, 3 Mar 2009 23:51:06 +0100,
Paul B. Mahol one...@gmail.com:
The problem was simply that the frequency was lowered too many. I
have to limit the frequency with debug.cpufreq.lowest.
How much small it was?
powerd -b min with 125 freq works fine on CURRENT with ndis for me
(except
Le Sun, 1 Mar 2009 13:00:18 +0100,
Patrick Lamaizière patf...@davenulle.org:
[7-STABLE/i386-SMP]
When I enable powerd, ndis takes all the CPU. Powerd alone and ndis
alone works fine.
The kernel threads Windows DCP0 and ndis0 taskq run at
100%. But the machine is still running
Le Sat, 21 Feb 2009 12:27:02 +0100,
Lars Engels l...@freebsd.org:
I've tested most of the driver and I think (hope) this is ok.
http://user.lamaiziere.net/patrick/glxsb-6-130209.tar.gz
Let me know how it works.
Sorry for the late reply. I just tried the new version (thanks for
Le Thu, 12 Feb 2009 22:34:43 +0100,
Lars Engels l...@freebsd.org:
Hi,
I just tried it, but I get this message:
glxsb0: AMD Geode LX Security Block (AES-128-CBC, RNG) mem
0xefff4000-0xefff7fff irq 9 at device 1.2 on pci0
glxsb0: cannot allocate DMA memory of 32768 bytes (12)
I think you
Le Fri, 13 Feb 2009 15:43:33 +0100,
Patrick Lamaizière patf...@davenulle.org:
Le Thu, 12 Feb 2009 22:34:43 +0100,
Lars Engels l...@freebsd.org:
Hi,
I just tried it, but I get this message:
glxsb0: AMD Geode LX Security Block (AES-128-CBC, RNG) mem
0xefff4000-0xefff7fff irq 9
Hi,
I've just found that the files for glxsb(4) in RELENG_7 are older than
in RELENG_7_1. I don't think this is normal?
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/glxsb/glxsb.c?only_with_tag=RELENG_7
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/glxsb/glxsb.c?only_with_tag=RELENG_7_1
Hi,
I've backported the glxsb(4) driver to RELENG_6 (to use it on FreeNAS by
instance).
http://user.lamaiziere.net/patrick/glxsb-6-100209.tar.gz
I am not able to test it, but I hope it will work.
You can test with openssl:
openssl enc -e -aes-128-cbc -in file -out file.enc -k abcdefgh -nosalt
Hi,
I've installed FreeBSD on my MacBook Pro via bootcamp and sysinstall
breaks the partitions: Mac os X is not able to see his partition any
more. Only the freebsd slice is bootable.
- bootcamp to make a 'windows' (tm) partition,
- boot on the FreeBSD's dvd and install it.
I didn't notice when
Le Fri, 16 Jan 2009 14:44:59 -0500,
grarpamp grarp...@gmail.com a écrit :
GENERIC, RELENG_7 a few days past the 7.1 release.
SuperMicro 370DER motherboard, most recent bios.
The Nikon is set to mass storage. The RCA has no such option.
Both have the latest firmware.
By the way, the RCA
Le Tue, 09 Dec 2008 21:39:26 -0500,
Ken Smith kensm...@cse.buffalo.edu a écrit :
Hello,
So... Two show-stoppers, one Security Advisory, and one Gee. Did we
really implement that new interface that way? That needs a bit more
work. later...
Can we know what were these two show-stoppers? In
Le Tue, 9 Dec 2008 11:16:57 +0100,
Ruben van Staveren [EMAIL PROTECTED] a écrit :
Sure, but show me how to go to http://svn.freebsd.org/viewvc/base/
and see commit log per branch or any other way to see what is
going on in a branch. Fisheye gives you that in a really clear way
and it
Le Fri, 10 Oct 2008 09:08:47 -0400,
Stephen Clark [EMAIL PROTECTED] a écrit :
On both of the above platforms this does not work and the platforms
reboot when watchdogd is killed with a kill pid,
after the timeout value (-t) that had been specified to watchdogd
when starting it has
Le Wed, 08 Oct 2008 15:07:06 -0400,
Stephen Clark [EMAIL PROTECTED] a écrit :
Hello List,
We have 2 different platforms that we are trying to use the watchdog
timer and watchdogd program on. One is a Soekris 5501:
CPU: Geode(TM) Integrated Processor by AMD PCS (433.25-MHz 586-class
CPU)
Le Wed, 09 Jul 2008 15:31:30 -0400,
Mike Tancsa [EMAIL PROTECTED] a écrit :
Without the module loaded, I can do something simple like
# sh s
# cat s
MEOUTSIDE=64.x.x.x
MEINSIDE=192.168.5.0/24
REMOTEOUTSIDE=64.y.y.y
REMOTEINSIDE=192.168.1.0/24
IPSECKEY=zxzpprlNH61N11SGfrCa8dxZ
Le Wed, 09 Jul 2008 15:31:30 -0400,
Mike Tancsa [EMAIL PROTECTED] a écrit :
Without the module loaded, I can do something simple like
glxsb0: detached
glxsb0: AMD Geode LX Security Block
(AES-128-CBC,RNG) mem 0xa000-0xa0003fff irq 10 at device 1.2 on
pci0 # sh s
The result of line 1:
Le Sun, 22 Jun 2008 21:20:02 +0200,
Ivan Voras [EMAIL PROTECTED] a écrit :
Hi,
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes256 bytes 1024 bytes
8192 bytes aes-128 cbc 5359.57k 5577.49k 5654.53k
5639.81k 5679.65k
Le Fri, 6 Jun 2008 23:41:35 +0200,
Patrick Lamaizière [EMAIL PROTECTED] a écrit :
Hello,
I'm trying to port the glxsb driver from OpenBSD to FreeBSD 7-STABLE
(via the NetBSD port).
The glxsb driver supports the security block of the Geode LX
series processors. The Geode LX is a member
Le Fri, 20 Jun 2008 07:34:35 -0300,
JoaoBR [EMAIL PROTECTED] a écrit :
my amd64 crashs under heavy disk i/o as each night at 0300 daily
cron, also often after some minutes when compiling world. Also with
kde and after some flash videos (youtube) or large file copying
I do not see this
Le Sun, 22 Jun 2008 19:40:04 +0200,
Ivan Voras [EMAIL PROTECTED] a écrit :
Ivan Voras wrote:
The results are practically the same.
On the other hand:
ursaminor:~/admin/glxsb dd if=/dev/zero bs=4k count=10 | openssl
enc -aes-128-cbc -e -out /dev/null -nosalt -k abcdefhij
10+0
Le Sat, 14 Jun 2008 01:52:29 +0200,
Patrick Lamaizière [EMAIL PROTECTED] a écrit :
I made few tests and the panic occurs with a -s of 3989 bytes.
ping -s 3988 = ok
ping -s 3989 = panic
The coredump seems to be ok.
http://user.lamaiziere.net/patrick/coredump.txt
I will try
Le Fri, 13 Jun 2008 01:57:35 +0200,
Kris Kennaway [EMAIL PROTECTED] a écrit :
Hello,
[...]
#17 0xc0700746 in crypto_invoke (cap=0x8, crp=0xd61a0950,
hint=-1616994916) at cryptodev_if.h:53
Previous frame inner to this frame (corrupt stack?)
(kgdb)
Unfortunately the trace is bogus.
[FreeBSD 7-STABLE/i386]
Hello,
I've got a 100 % reproductible panic with ipsec when using a
'ping -s 4000'. It works without ipsec
My ipsec setup is very simple, i just use setkey:
/etc/ipsec.conf
flush;
spdflush;
add 192.168.1.21 192.168.1.200 esp 1011 -E rijndael-cbc
0123456789012345;
add
Le Vendredi 19 Mai 2006 18:27, Ulrich Spoerlein a écrit :
Hi guys,
Hello,
is it just me, or is no one actually using ipw(4) under 6.1? Anyway, I
set up a FreeBSD based AP using an ural(4) device. I'm connecting to it
via laptop and ipw(4). This works fine, as long as you don't push it.
Niki Denev :
Hello,
I've just upraded my Xorg port to the latest relase 6.9,
and begin to get this when i start X :
agp0: binding memory at bad offset 0
error: [drm:pid610:radeon_cp_init] *ERROR* radeon_cp_init called without
lock held
error: [drm:pid610:drm_unlock] *ERROR* Process 610
Le Vendredi 30 Décembre 2005 16:05, Gianmarco Giovannelli a écrit :
Is there anyone here that can share it's
xorg.conf to use something of the new accel features of the card.
There are only few parameters, see man i810
___
freebsd-stable@freebsd.org
Le Vendredi 30 Décembre 2005 16:12, Gianmarco Giovannelli a écrit :
I am not able to succeded in making a make update when I use the iwi0
card.
I always get :
TreeList failed: Network write failure ...
Is there someone else that is having the same problem ?
Yes, there was a thread about
Le Jeudi 29 Décembre 2005 07:59, Gianmarco Giovannelli a écrit :
The plain xorg 6.8.2 seems not be able to
recognize the card (at least the mine).
Do you have used the patch :
http://apocalyptech.com/linux/nc6120/xorg-6.8.2-i810.patch
to compile it ?
No it works out of the box for me.
I
Le Lundi 19 Décembre 2005 21:35, Oliver Fromme :
Patrick Lamaizière [EMAIL PROTECTED] wrote:
But dri does not work, Xorg seems to look for a /dev/dri/card0 and
i've got only one device /dev/dri/card1 ?
Strange. It works fine for me:
With the patch from Alexey Popov (ftp
Le Mardi 27 Décembre 2005 02:48, Julian Stecklina a écrit :
Hello,
I just discovered that the DRM drivers have been updated and my 855GM
is now supported by i915.ko.
If I load the module, the driver attaches:
...
The problem is easily spotted, as there is only /dev/dri/card1. If I
try to
Le Dimanche 18 Décembre 2005 01:31, Gianmarco a écrit :
I am trying to use the latest drm hook for i915, but I get this error:
drmsub0: Intel i915GM port 0x1800-0x1807 mem
0xb008-0xb00f,0xc000-0xcfff,0xb000-0xb003 irq 16
at device 2.0 on pci0
error:
Le Mercredi 26 Octobre 2005 02:46, Joel Hatton a écrit :
most files in /etc/rc.d changed, so installing them all with
mergemaster was laborious - a note in UPDATING similar to that for
5.x:
The simplest solution is an 'rm -rf /etc/rc.d/*' and then
Le Lundi 18 Juillet 2005 10:50, Jonathan Weiss a écrit :
Hi,
When I do a boot in safe mode, everything is ok.
Attachted is the dmesg from the verbose boot.
Did you try without acpi ?
I've got a similar problem with a nforce2 based mother board.
Regards.
33 matches
Mail list logo
