On Monday, July 29, 2013 3:31:49 am varanasi sainath wrote:
> Hello,
>
> I am writing a kernel module in which I am trying to connect to a UNIX
> socket
> (UNIX domain sockets use the file system as their address name space).
> Kernel module (loadable) acts as a client and User mode program acts a
On 29/07/2013 08:31, varanasi sainath wrote:
Hello,
I am writing a kernel module in which I am trying to connect to a UNIX
socket
(UNIX domain sockets use the file system as their address name space).
Kernel module (loadable) acts as a client and User mode program acts as
server,
I have loaded t
On 09/08/2012 15:52, dude golden wrote:
> hope my email find you well,first of all thank you very much for your
> grate response always in answering my emails, now i am using freeBSD
> 8.3 in a Intel corI5 server with 12 G of RAM and 500 G HDD sata .we
> have a voip soft switch application installe
Hi,
On 25 May 2012 20:01:44 -
"John Levine" wrote:
JL> >panic: ffs_clusteralloc: map mismatch
JL>
JL> Something's fairly badly screwed up on your disk. My advice would
JL> be to boot from a CD or USB key and run fsck to try to repair it.
the disk was pretty much f...ed up. I always got an
>panic: ffs_clusteralloc: map mismatch
Something's fairly badly screwed up on your disk. My advice would be
to boot from a CD or USB key and run fsck to try to repair it.
R's,
John
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org
In response to the related thread started by Martin McCormick we did run
a `zpool scrub` on the zpool, and the scrub completed successfully with
no repairs performed.
I successfully tried importing the zpool in Linux using the native Linux
ZFS module. However attempting to remove the files via
> On 8/9/11 10:33 PM, Daryl Sayers wrote:
>> I have a FreeBSD 8.2-STABLE (64bit) system with 4G mem installed. I have
>> had a few kernel panics over the last few weeks and would like to capture
>> a core dump. I have added the following to /etc/rc.conf
>>
>> dumpdev="AUTO"
>> dumpdir=/var/crash
On 8/9/11 10:33 PM, Daryl Sayers wrote:
> I have a FreeBSD 8.2-STABLE (64bit) system with 4G mem installed. I have
> had a few kernel panics over the last few weeks and would like to capture
> a core dump. I have added the following to /etc/rc.conf
>
> dumpdev="AUTO"
> dumpdir=/var/crash
>
> Th
On 12/10/10 14:47, Eitan Adler wrote:
I just pressed the power button on my desktop computer - it seemed
like it was attempting to do an ACPI suspend instead of a power down
like I expected - but I'm not sure.
Either way:
When It got close to the end
I got
Kernel trap 12: page fault in kernel
2010/12/3 Dmitry Postolov :
> Hi to All!
>
> Sorry for my bad English...
>
> On my notebook HP ProBook 4510s (Bios Compaq F17 (latest)) the
> problem of times in some weeks is observed at loading FreeBSD 8.1.
>
> ---
>
> Fatal trap 12: page fault while in kernel mode
> cpuid=0; apic id=00
> fault
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2010/03/17 00:31, Leslie Jensen wrote:
>
> I have set upp aggregation of my wlan and and wired NIC following the
> instructions in the handbook.
>
> http://www.freebsd.org/doc/handbook/network-aggregation.html
>
> I "forgot" to add the if_lagg_lo
Leslie Jensen wrote:
I'm on a 8.0-RELEASE-p2 system.
Actually after more testing I found out that the line
ifconfig_iwn0="ether 00:16:ea:61:01:e8"
in my rc.conf is the culprit. If I comment it out the system will start
but only with the wired interface working.
If you don't comment the lin
On 2010-03-17 09:36, Nikos Vassiliadis wrote:
Leslie Jensen wrote:
I have set upp aggregation of my wlan and and wired NIC following the
instructions in the handbook.
http://www.freebsd.org/doc/handbook/network-aggregation.html
I "forgot" to add the if_lagg_load="YES" in /boot/loader.conf.
Leslie Jensen wrote:
I have set upp aggregation of my wlan and and wired NIC following the
instructions in the handbook.
http://www.freebsd.org/doc/handbook/network-aggregation.html
I "forgot" to add the if_lagg_load="YES" in /boot/loader.conf. When I
rebooted I got a kernel panic.
Should
On Tue, Dec 22, 2009 at 11:52 AM, Jason wrote:
> =
>
>>
>> Any progress for bellow?
>>
>> I have the same problem with PCI SATA Controller ST-Lab A-173 Sil3512
>> It's not RAID, but when copying to HDD:
>> LOG---
>> ad6:FAILURE - device detached
>> g_vfs_done():ad6s1f[WRIT
You may wish to check and see if your firmware is up-to-date on all of your
disk drives, and your controller.
On Mon, Dec 21, 2009 at 10:40:10PM +0200, Alex thus spake:
Dear John,
Any progress for bellow?
I have the same problem with PCI SATA Controller ST-Lab A-173 Sil3512
It's not RAID, but
On Wednesday 12 August 2009 08:01:07 Коньков Евгений wrote:
> Aug 12 15:59:08 host savecore: reboot after panic: integer divide fault
> Aug 12 15:59:08 host savecore: writing core to vmcore.4
>
> How to obtain which process cause system to reboot?
kgdb /boot/kernel/kernel /var/crash/vmcore.4
--
M
...
> # mount -t xfs -o ro /dev/ad0s2 /mnt
> # ls /mnt
> # cp /mnt/my_file /home/zbigniew
I forgot add here that I do then
# umount /mnt
and after that was kernel panic.
I'm sorry for the mistake.
Zbigniew
___
freebsd-questions@freebsd.org mailing lis
On Friday 22 May 2009 05:30:42 Shawn Badger wrote:
> Hi, I installed FreeBSD 7.2 Release on a mini nettop (Intel
> Atom/945gc/ICH7 hardware), and everything seemed to go smoothly.
> However, when I boot the system and the filesystem checks have been
> going for awhile, it always ends in a panic. H
"Garrett Cooper" writes:
> Dag-Erling Smørgrav writes:
> > Peter Jeremy writes:
> > > If you press any key during the first spinner [...] You can then
> > > enter the name of the program you wish to run - eg /boot/loader.old
> > That won't work - he changed the forth code, not the compiled code
On Mon, Jan 12, 2009 at 6:50 AM, Dag-Erling Smørgrav wrote:
> Peter Jeremy writes:
>> Kamlesh Patel writes:
>> > How do i recover the system from this error. I can't reload the
>> > loader.old
>>
>> If you press any key during the first spinner [...] You can then
>> enter the name of the progra
Peter Jeremy writes:
> Kamlesh Patel writes:
> > How do i recover the system from this error. I can't reload the
> > loader.old
>
> If you press any key during the first spinner [...] You can then
> enter the name of the program you wish to run - eg /boot/loader.old
That won't work - he changed
On 2009-Jan-09 00:05:47 -0800, Kamlesh Patel wrote:
>How do i recover the system from this error. I can't reload the loader.old
If you press any key during the first spinner, you should get a prompt
similar to the following:
>> FreeBSD/i386 BOOT
Default: 0:ad(0,a)/boot/loader
boot:
You can then
Kamlesh Patel writes:
> Hi there,
>
> I changed the following file of FreeBSD 7.0:
> sys/boot/forth/beastie.4th
>
> variable rebootkey
> variable mykey (added line)
>
> I built and installed kernel, then i reboot the system, it gives me the
> following error:
>
> -
Update of kernel panic.
Rebuilt kernel without 80211node, seems to have cured the panics.
Removed all wireless support for now.
Thanks to Toni Schmidbauer
--- On Thu, 1/1/09, Mark Busby wrote:
> From: Mark Busby
> Subject: kernel panic
> To: "help help"
> Date: Thursday, January 1, 2009, 2:
At Thu, 1 Jan 2009 12:05:25 -0800 (PST),
Mark Busby wrote:
> Jan 1 08:56:39 mars savecore: reboot after panic: kmem_malloc(12288):
> kmem_map too small: 128778240 total allocated
as you probably already know this means you ran out of kernel memory.
> 80211node 8081 21705K - 808
Thanks, that took care of it.
On Wed, Oct 1, 2008 at 4:49 PM, Manolis Kiagias <[EMAIL PROTECTED]> wrote:
> Walter Venable wrote:
>>
>> Our box, without readily obvious provocation, started doing this today:
>> Panic: softdep_setup_inomapdep: dependency for new inode already exists.
>> cpuid: 0
>>
Walter Venable wrote:
Our box, without readily obvious provocation, started doing this today:
Panic: softdep_setup_inomapdep: dependency for new inode already exists.
cpuid: 0
physical memory: 1971 MB
dumping 78MB: 63 47 31 15
The system then immediately reboots, and hits the panic, reboots, etc
Eric Crist wrote:
Hey folks,
First, please 'reply-all' as I'm not on the list.
I've got a backup server that, every night, offloads things to a
secondary, USB attached hard disk. We've got two of these disks, which
we rotate so as to have a fairly recent off-site version, in the event
of a
Greg Himes wrote:
Hello All,
Last week, one half of my dual port Qlogic fibre channel interface
started causing a page fault panic while probing the second port at boot
time.
I was able to get the system back up by disabling the BIOS on the
second port. The system still sees the 2nd port, bu
since i activate ataidle i have this errors:
ad8: FAILURE - WRITE_DMA48 timed out LBA=314770799
+ad8: TIMEOUT - READ_DMA retrying (1 retry left) LBA=12207
+ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing
request directly
after disable it, this messages are gone.
so
with backtrace, it looks like:
[EMAIL PROTECTED] STORAGE> kgdb kernel.debug /var/crash/vmcore.1
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined
symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free soft
hi,
[EMAIL PROTECTED] STORAGE> kgdb kernel.debug /var/crash/vmcore.1
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined
symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU Ge
At Tue, 20 May 2008 07:59:19 +0200,
Thomas Herzog wrote:
> cat /var/crash/info.1
follow this guide:
http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html
and post the results. if nobody answers, open a pr (problem report)
http://www.freebsd.org/send-pr.html
hth,
toni
--
On Monday 12 of May 2008 22:22:12 Roland Smith wrote:
> It might also be a hardware problem. Testing the RAM would be a good
> place to start.
I bought new RAM and tested it with 'memtest' and now is OK (no error was
found). Hover I still got kernel panic when I do:
# Xorg -configure
# Xorg -conf
On Monday 12 of May 2008 22:22:12 Roland Smith wrote:
> It might also be a hardware problem. Testing the RAM would be a good
> place to start.
Yes. You are right. I tested my memory with 'memtest' and got one error:
Tst Pass Failing AddressGood BadErr-Bits Count
5
On Monday 12 of May 2008 22:22:12 Roland Smith wrote:
> > > How *exactly* did you upgrade your ports? Sometimes old libraries hang
> > > around causing trouble.
> >
> >I used portsnap to download ports:
> > portsnap fetch
> > [...]
>
> Did you do a 'portsnap extract' as well? Fetching alone isn't e
On Monday 12 May 2008 22:22:12 Roland Smith wrote:
> On Mon, May 12, 2008 at 08:34:17PM +0200, Zbigniew Komarnicki wrote:
> > On Monday 12 of May 2008 16:24:44 Roland Smith wrote:
> > In file: "/var/log/dmesg.today" I found at the end of file the following
> > entries:
> > pid 23201 (conftest), u
On Mon, May 12, 2008 at 08:34:17PM +0200, Zbigniew Komarnicki wrote:
> On Monday 12 of May 2008 16:24:44 Roland Smith wrote:
> > How *exactly* did you upgrade your ports? Sometimes old libraries hang
> > around causing trouble.
>
> I simply download the iso file for boot only:
> 7.0-RELEASE-i386-
On Monday 12 of May 2008 16:24:44 Roland Smith wrote:
> How *exactly* did you upgrade your ports? Sometimes old libraries hang
> around causing trouble.
I simply download the iso file for boot only:
7.0-RELEASE-i386-bootonly.iso
Then burn on CD and then install fresh 7.0-RELEASE on hard disk - m
On Mon, May 12, 2008 at 12:51:26PM +0200, Zbigniew Komarnicki wrote:
> Hello!
>
> I decide to go on FreeBSD 7.0-RELEASE. Before I used 6.3-RELEASE.
> But now I cannot get working Xorg. I almost get the kernel panic.
> I install fresh 7.0-RELEASE and update ports by portsnam and everything
> compi
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
"Nathan Alan Souer" <[EMAIL PROTECTED]> writes:
> 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
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
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
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.
my server has been rebooting quite a bit and stopped responding today. i
found this on the console:
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.
my server has been rebooting quite a bit and stopped responding today. i
On Sun, Oct 07, 2007 at 11:01:41AM +0200, Hans Petter Selasky wrote:
> On Saturday 06 October 2007, Joe Altman wrote:
> > chthonic.com/crash-crash-crash
>
> Hi,
>
> Do you have "options KDB" in your kernel config file ?
Following your suggestion, I did try this; and there was no
change from kern
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"
On Wed, Apr 04, 2007 at 08:28:56PM -0400, m yelle wrote:
> 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.
Sorry, that's just not how it works :)
FreeBSD 6.2 supports the same hard
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
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
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 world
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Unfortunately, my /boot/modules is already empty =(
On Feb 26, 2007, at 9:51 PM, Kip Macy wrote:
It looks like it may be loading an out of sync kernel module. Cleaning
out /boot/modules might help.
-Kip
On 2/26/07, Joe Auty <[EMAIL
On 2007-Feb-26 17:38:10 -0500, Joe Auty <[EMAIL PROTECTED]> wrote:
>My system does boot off of disc 1 of the FreeBSD 6.2 CD.
That's a good start. Together with your memtest results, it
suggests that your hardware is OK.
> However,
>even when copying the /boot directory from the CD to my machin
It looks like it may be loading an out of sync kernel module. Cleaning
out /boot/modules might help.
-Kip
On 2/26/07, Joe Auty <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well,
My system does boot off of disc 1 of the FreeBSD 6.2 CD. However,
even w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well,
My system does boot off of disc 1 of the FreeBSD 6.2 CD. However,
even when copying the /boot directory from the CD to my machine, it
still produces the same kernel panic, even when starting in safe
mode. I've run a memtest, and it checke
In <[EMAIL PROTECTED]>, Ted Mittelstaedt <[EMAIL PROTECTED]> typed:
> > For instance, is rebuilding world between point releases (e.g. 5.4 to
> > 5.5) an okay idea, compared to across major releases (e.g. 5.5 to 6.2)?
For the record, I do a rebuild between point releases - actually, I
track -stabl
MAIL PROTECTED]>; ;
Sent: Sunday, February 25, 2007 10:39 PM
Subject: Re: kernel panic at boot on any 6.x OS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 25, 2007, at 7:56 PM, Ted Mittelstaedt wrote:
- Original Message -
From: "Joe Auty" <[EMAIL PROTECTED]>
- Original Message -
From: "Joe Auty" <[EMAIL PROTECTED]>
To: "Ted Mittelstaedt" <[EMAIL PROTECTED]>
Cc: "Daan Vreeken [PA4DAN]" <[EMAIL PROTECTED]>; "Kip Macy"
<[EMAIL PROTECTED]>; ;
Sent: Sunday, February 25, 2007 10:39 P
>; ;
Sent: Sunday, February 25, 2007 8:14 AM
Subject: Re: kernel panic at boot on any 6.x OS
Any idea how this could have happened after disabling everything in
my /etc/loader.conf, and simply running a:
make buildworld
make buildkernel KERNCONF=myconfig
make installkernel KERNCONF=mycon
- Original Message -
From: "Joe Auty" <[EMAIL PROTECTED]>
To: "Daan Vreeken [PA4DAN]" <[EMAIL PROTECTED]>
Cc: "Kip Macy" <[EMAIL PROTECTED]>; ;
Sent: Sunday, February 25, 2007 8:14 AM
Subject: Re: kernel panic at boot on any 6.x OS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 25, 2007, at 11:14 AM, Joe Auty wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 25, 2007, at 5:46 AM, Daan Vreeken [PA4DAN] wrote:
On Sunday 25 February 2007 08:59, Kip Macy wrote:
It looks as if you've hit a device driver th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 25, 2007, at 5:46 AM, Daan Vreeken [PA4DAN] wrote:
On Sunday 25 February 2007 08:59, Kip Macy wrote:
It looks as if you've hit a device driver that is trying to print out
a null string. The message you've given doesn't provide any more
info
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey Kip,
I'd gladly try a snapshot kernel, but I'm not sure which one to pick
out of this list:
ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/6.2-RELEASE/kernels
Any suggestions?
On Feb 25, 2007, at 2:59 AM, Kip Macy wrote:
It looks as if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 25, 2007, at 3:01 AM, LI Xin wrote:
Hi,
Joe Auty wrote:
This problem does not occur within any 5.x OS for me. I would
certainly
like to resolve this issue now, but this sort of debugging is over my
head beyond running fsck (which I've tr
On Sunday 25 February 2007 08:59, Kip Macy wrote:
> It looks as if you've hit a device driver that is trying to print out
> a null string. The message you've given doesn't provide any more
> information than that. If you install a snapshot kernel it will
> probably have ddb compiled in which will a
Hi,
Joe Auty wrote:
> This problem does not occur within any 5.x OS for me. I would certainly
> like to resolve this issue now, but this sort of debugging is over my
> head beyond running fsck (which I've tried). Any ideas here?
Which .ko are you trying to load? try removing them and see if thin
It looks as if you've hit a device driver that is trying to print out
a null string. The message you've given doesn't provide any more
information than that. If you install a snapshot kernel it will
probably have ddb compiled in which will allow you to at least get a
backtrace. I'm sorry you're ha
Mike wrote:
Mike wrote:
Hello,
I got a handful of Dell PE1850 and PE1750 boxes running mail
scanning that we recently upgraded to FreeBSD 6.1.
It started with a new PE1850 (mx4) that we immediately installed 6.1
on, which started having kernel panics- we initially blamed it
on hardware. B
> Mike wrote:
> > Hello,
> >
> > I got a handful of Dell PE1850 and PE1750 boxes running mail
> > scanning that we recently upgraded to FreeBSD 6.1.
> >
> > It started with a new PE1850 (mx4) that we immediately installed 6.1
> > on, which started having kernel panics- we initially blamed it
> > on
Mike wrote:
Hello,
I got a handful of Dell PE1850 and PE1750 boxes running mail
scanning that we recently upgraded to FreeBSD 6.1.
It started with a new PE1850 (mx4) that we immediately installed 6.1
on, which started having kernel panics- we initially blamed it
on hardware. But last week, we
On Fri, May 19, 2006 at 04:59:44PM -0400, Joe Auty wrote:
>
> On May 19, 2006, at 2:38 PM, Kris Kennaway wrote:
>
> >On Thu, May 18, 2006 at 10:54:19PM -0400, Joe Auty wrote:
> >>
> >>On May 18, 2006, at 12:36 AM, Kris Kennaway wrote:
> >>
> >>>On Wed, May 17, 2006 at 07:06:59PM -0400, Joe Auty w
On May 19, 2006, at 2:38 PM, Kris Kennaway wrote:
On Thu, May 18, 2006 at 10:54:19PM -0400, Joe Auty wrote:
On May 18, 2006, at 12:36 AM, Kris Kennaway wrote:
On Wed, May 17, 2006 at 07:06:59PM -0400, Joe Auty wrote:
Hello,
A problem I've had since 6.0 remains in 6.1 where my machine kern
On Thu, May 18, 2006 at 10:54:19PM -0400, Joe Auty wrote:
>
> On May 18, 2006, at 12:36 AM, Kris Kennaway wrote:
>
> > On Wed, May 17, 2006 at 07:06:59PM -0400, Joe Auty wrote:
> >> Hello,
> >>
> >> A problem I've had since 6.0 remains in 6.1 where my machine kernel
> >> panics at boot trying to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 18, 2006, at 12:36 AM, Kris Kennaway wrote:
On Wed, May 17, 2006 at 07:06:59PM -0400, Joe Auty wrote:
Hello,
A problem I've had since 6.0 remains in 6.1 where my machine kernel
panics at boot trying to kldload some module (it doesn't say w
On Thu, May 18, 2006 at 10:57:51AM +0200, Frank Steinborn wrote:
> Kris Kennaway wrote:
> > It sounds like you have an old (6.0) module you're still trying to
> > load. Things like the nvidia driver and other ports are prime
> > candidates.
> >
> > Kris
>
> Does that mean that all the panic-iss
Kris Kennaway wrote:
> It sounds like you have an old (6.0) module you're still trying to
> load. Things like the nvidia driver and other ports are prime
> candidates.
>
> Kris
Does that mean that all the panic-issues with kld(un)load are fixed in
6.1? I crashed an important 6.0-STABLE box sever
On Wed, May 17, 2006 at 07:06:59PM -0400, Joe Auty wrote:
> Hello,
>
> A problem I've had since 6.0 remains in 6.1 where my machine kernel
> panics at boot trying to kldload some module (it doesn't say which
> one). It also does not log this panic.
>
> I suppose this isn't terribly helpful in
On Wed, 17 May 2006, Joe Auty wrote:
A problem I've had since 6.0 remains in 6.1 where my machine kernel
panics at boot trying to kldload some module (it doesn't say which
one). It also does not log this panic.
I suppose this isn't terribly helpful information, but if there is
anything you c
On Thursday 04 May 2006 15:52, Shawn Guillemette wrote:
> Hello all,
>
>
>
>
>
> I have a Digital AlphaPC 164LX 533 MHz, running FreeBSD
> 4.11-RELEASE
>
> I have installed /usr/ports/net/mpd and attempted to make a vpn connection
What kind of VPN? mpd does ppp over serial lines, ether
> a) You're not using the kernel.debug, and b) it's not a sensible
> backtrace. Perhaps it's a side-effect of a) (i.e. you're not running
> kgdb against the same kernel that panicked).
I compiled the kernel using config -g, then rebooted using that kernel. At
some point, the system crashes, th
On Sat, Apr 29, 2006 at 01:03:12AM -0400, Steve Douville wrote:
> My server is rebooting frequently throughout the day. No apparent rhyme or
> reason, different applications can cause it. The following is what I get from
> one of the backtraces.
a) You're not using the kernel.debug, and b) it's
On 12/5/05, Michael P. Soulier <[EMAIL PROTECTED]> wrote:
> On 12/4/05, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> > > Is this true? If so, it would be the very first Unix that I've seen
> > > crash from this kind of user-mistake.
> >
> > Turns out it's pretty hard to fix.
>
> Well, all I know is t
On 2005-12-06 15:19, Martin Tournoy <[EMAIL PROTECTED]> wrote:
>
> Ok, stupid question perhaps, but what is "top-posting", I'm new to the
> whole mailling list stuff, so if you can explain a bit I won't do it
> anymore
>
> On 06 Dec 2005 10:12:40 -0500, Lowell Gilbert
> <[EMAIL PROTECTED]> wrot
mtools, hmm, might want to check that one out
Ok, stupid question perhaps, but what is "top-posting", I'm new to the
whole mailling list stuff, so if you can explain a bit I won't do it
anymore
On 06 Dec 2005 10:12:40 -0500, Lowell Gilbert
<[EMAIL PROTECTED]> wrote:
> Don't top-post, plea
Don't top-post, please.
Martin Tournoy <[EMAIL PROTECTED]> writes:
> My advice:
> Save all your work before you do anything with a floppy
> Don't do anything with a floppy on critical machines
> Think before you act when working with a floppy
Using the mtools port is a lot easier. It uses the W
It happens, I've experienced quite some problems with floppy's and
FreeBSD 5.4 and 6.0
anyway, if you mount a floppy, pull it out and unmount it the kernel
might panic, if the floppy if reading writing and you pull it out the
kernel might panic, if you mount a floppy which is damaged or has a
dama
On Mon, Dec 05, 2005 at 08:37:23AM -0500, Michael P. Soulier wrote:
> On 12/4/05, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> > > Is this true? If so, it would be the very first Unix that I've seen
> > > crash from this kind of user-mistake.
> >
> > Turns out it's pretty hard to fix.
>
> Well, all
On 12/4/05, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> > Is this true? If so, it would be the very first Unix that I've seen
> > crash from this kind of user-mistake.
>
> Turns out it's pretty hard to fix.
Well, all I know is that it does happen on Linux, Solaris... I don't
recall seeing it on HP-
On Sun, Dec 04, 2005 at 05:32:42PM -0500, Michael P. Soulier wrote:
> Hey all,
>
> I'm reading "BSD Hacks" by Dru Lavigne, published by O'Reilly. In the
> section on managing floppies, it mentions that if you pull a floppy
> without umounting it first, the next time to try to access the
> filesyst
1 - 100 of 168 matches
Mail list logo
