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.
What can I do
the computer is not responding to the keyboard. When I power
off the Sony recorder the computer screen displays a page fault panic.
The panic behavior reminds of what happenes when I pull a USB thumb drive
without dismounting ... it is probably not specific to this device.
To rub salt in my wounds
I've been playing around with some multicast stuff with rtpdump
and I have what appears to be a 100%-repeatable panic on
7.1-PRERELEASE (csupped on 20080905):
(kgdb) bt
#0 doadump () at pcpu.h:196
#1 0xc078f8c7 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
#2 0xc078fb
What modules are loaded from loader.conf?
I had two distinct issues on one machine that were entirely due to
module loading. One was sound, using snd_driver instead of a specific
sound driver caused the machine to reboot. The other issue was
nvidia. The binary nvidia driver caused an instant
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Meaghan Hayes wrote:
> When I try to boot FreeBSD, it cycles through all of my hardware etc.
> as with a regular boot then says:
>
> panic: ohci_add_done: addr 0x7fef16d0 not found
>
> and tells me that it's rebooting, an
When I try to boot FreeBSD, it cycles through all of my hardware etc.
as with a regular boot then says:
panic: ohci_add_done: addr 0x7fef16d0 not found
and tells me that it's rebooting, and just keeps doing this.
I was told that it was most likely a USB issue, especially if I had
recently
ed as "i386-marcel-freebsd".
Unread portion of the kernel message buffer:
panic: softdep_deallocate_dependencies: dangling deps
cpuid = 0
Uptime: 11d20h37m38s
Physical memory: 1011 MB
Dumping 201 MB: 186 170 154 138 122 106 90 74 58 42 26 10
#0 doadump () at pcpu.h:195
195__asm __
uot;i386-marcel-freebsd".
Unread portion of the kernel message buffer:
panic: softdep_deallocate_dependencies: dangling deps
cpuid = 0
Uptime: 11d20h37m38s
Physical memory: 1011 MB
Dumping 201 MB: 186 170 154 138 122 106 90 74 58 42 26 10
#0 doadump () at pcpu.h:195
195 __asm __
Hello, when I try to install FreeBSD 7.0 I have some problems:
after booting and loading kernel (I boot from CD) I saw blue screen with grey
box in center with text:
"Probing devices please wait (this can take a while)..." and on screen was
writen:
>/: write failed, filesystem i
Michael Grant wrote:
On Tue, Jul 15, 2008 at 10:44 PM, Kris Kennaway <[EMAIL PROTECTED]> wrote:
Michael Grant wrote:
I have been having panics on one of my machines, roughly every week or
so. I was running 6.3 pre-release and then I updated to 6.3 p2 and I
still have the panic, here
On Tue, Jul 15, 2008 at 10:44 PM, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> Michael Grant wrote:
>>
>> I have been having panics on one of my machines, roughly every week or
>> so. I was running 6.3 pre-release and then I updated to 6.3 p2 and I
>> still have t
nd
> > nForce 430 chipsets).
[snip]
> You should add options WITNESS also and this will probably generate
> additional debugging and/or a panic before the error occurs.
I rebuilt the kernel yesterday and the system obligingly panicked for me
this morning. This time things went as
David Gurvich wrote:
Can you disable smp? I see reports on the same issue with 6.3 that
imply it may be related to smp.
You are spreading FUD :-) There is no information provided upon which
to base that conclusion.
Kris
___
freebsd-questions@free
Can you disable smp? I see reports on the same issue with 6.3 that
imply it may be related to smp.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTE
Michael Grant wrote:
I have been having panics on one of my machines, roughly every week or
so. I was running 6.3 pre-release and then I updated to 6.3 p2 and I
still have the panic, here's the message that appears on the console:
panic: kmem_kernel trap 12 with interrupts disabled
I have been having panics on one of my machines, roughly every week or
so. I was running 6.3 pre-release and then I updated to 6.3 p2 and I
still have the panic, here's the message that appears on the console:
panic: kmem_kernel trap 12 with interrupts disabled
Fatal trap 12: page fault
e 430 chipsets).
[snip]
You should add options WITNESS also and this will probably generate
additional debugging and/or a panic before the error occurs.
OK, done that. The first reboot came up OK, sods law being what it is
the next few boots will be clean and I'll have to wait a while for
re
nd
> > nForce 430 chipsets).
[snip]
> You should add options WITNESS also and this will probably generate
> additional debugging and/or a panic before the error occurs.
OK, done that. The first reboot came up OK, sods law being what it is
the next few boots will be clean and I'll
DB
options KDB
options KDB_UNATTENDED
You should add options WITNESS also and this will probably generate
additional debugging and/or a panic before the error occurs.
But I'm still a bit dubious as to whether I've really managed to create
a debugging kernel. I was under the impress
I'm getting frequent panics due to spin lock held too long when booting
my recently built 6.3 system with an Athlon 4850e dual core processor
on a Foxconn 6150M2MA motherboard (GeForce 6150 and nForce 430
chipsets).
FreeBSD curlew.lan 6.3-STABLE FreeBSD 6.3-STABLE #2: Sat Jul 12 09:43:21
BST
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Mel and all,
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
iEYEARECAAYFAkh2CcUACgkQvVxKL9VSxXr6rgCgmK63mJx8GlFmsKELMnZ8EtZ6
/BQAoIW/3f7dt+bxjZnBy38V75Irv/Tc
=mPiu
-END PGP SIGNATURE-
2008/7/10 Mel <[EMAIL PROTECTED]>:
> Pro
R2 800 1GB * 2
>
> I want to install FreeBSD 7.0 on it, so I downloaded the FreeBSD 7.0/amd64
> ISO. When I boot the computer (Booting FreeBSD), following lines was
> printed on my screen:
>
> hptrr: no controller detected
> panic: ohci_add_done: addr 0x6fff1ce0 not found
>
7.0 on it, so I downloaded the FreeBSD 7.0/amd64 ISO.
When I boot the computer (Booting FreeBSD), following lines was
printed on my screen:
hptrr: no controller detected
panic: ohci_add_done: addr 0x6fff1ce0 not found
cpuid = 0
uptime: 1s
Cannot dump. No dump device defined.
than I tried the "
I get a kernel panic whenever I connect my digital camera (Olympus
C-2040Z) on my 7.0 system. It looks like a rev. 7 related problem,
everything works fine on the same PC if I boot into rev. 6.3.
This might already be covered by PR usb/117313: [umass] [panic] panic on
usb camera
Wednesday 25 June 2008 17:24:58 kirjutas Pietro Cerutti:
> Toomas Aas wrote:
> | Are there known conditions under which the core dump really isn't
> | recorded, or am I simply missing something obvious?
>
> Yes, if the panic occurs before the filesystem supposed to contain
g: FreeBSD 7.0-STABLE #258: Tue Jun 10 05:54:42 CDT 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/ENCONTACTO
Panic String: page fault
Dump Parity: 2395754794
Bounds: 2
Dump Status: good
the vmcore is about 300M so I'm not attaching it;) I could put it on
line at a moments notice. I
-STABLE #258: Tue Jun 10 05:54:42 CDT 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/ENCONTACTO
Panic String: page fault
Dump Parity: 2395754794
Bounds: 2
Dump Status: good
the vmcore is about 300M so I'm not attaching it;) I could put it
on line at a moments notice. I think that what I
= DPL 0, pres 1, def32 1,
> >>>> gran 1 Jun 12 23:02:41 UnixBox2 kernel: processor eflags =
> >>>> interrupt enabled, resume, IOPL = 0
> >>>> Jun 12 23:02:41 UnixBox2 kernel: current process= 925
> >>>> (cp) Ju
resume, IOPL = 0
Jun 12 23:02:41 UnixBox2 kernel: current process= 925 (cp)
Jun 12 23:02:41 UnixBox2 kernel: trap number= 12
Jun 12 23:02:41 UnixBox2 kernel: panic: page fault
Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1
Jun 12 23:02:41 UnixBox2 kernel: Uptime: 1h21m59s
Jun 12 23
12 23:02:41 UnixBox2 kernel: current process= 925 (cp)
Jun 12 23:02:41 UnixBox2 kernel: trap number= 12
Jun 12 23:02:41 UnixBox2 kernel: panic: page fault
Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1
Jun 12 23:02:41 UnixBox2 kernel: Uptime: 1h21m59s
Jun 12 23:02:41 UnixBox2 kernel:
[Don't top-post, please.]
>> It's quite likely to be due to bad hardware though.
Ryan Coleman <[EMAIL PROTECTED]> writes:
> I'm sure. I could get different RAM this weekend, but that just makes
> me angry. I bought all the items from recommended lists on NewEgg two
> weeks ago. This is probably
I'm sure. I could get different RAM this weekend, but that just makes me
angry. I bought all the items from recommended lists on NewEgg two weeks
ago. This is probably the 11th crash in 12 days.
It's quite likely to be due to bad hardware though.
Kris
___
kernel: current process= 925 (cp)
Jun 12 23:02:41 UnixBox2 kernel: trap number= 12
Jun 12 23:02:41 UnixBox2 kernel: panic: page fault
Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1
Jun 12 23:02:41 UnixBox2 kernel: Uptime: 1h21m59s
Jun 12 23:02:41 UnixBox2 kernel: Cannot dump. No dump
led, resume, IOPL = 0
> Jun 12 23:02:41 UnixBox2 kernel: current process= 925 (cp)
> Jun 12 23:02:41 UnixBox2 kernel: trap number = 12
> Jun 12 23:02:41 UnixBox2 kernel: panic: page fault
> Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1
> Jun 12 23:02:41 UnixBox2 kernel:
eflags = interrupt
enabled, resume, IOPL = 0
Jun 12 23:02:41 UnixBox2 kernel: current process= 925 (cp)
Jun 12 23:02:41 UnixBox2 kernel: trap number= 12
Jun 12 23:02:41 UnixBox2 kernel: panic: page fault
Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1
Jun 12 23:02:41 UnixBox2 kernel:
process= 1385 (cp)
Jun 13 14:32:21 UnixBox2 kernel: trap number= 12
Jun 13 14:32:21 UnixBox2 kernel: panic: page fault
Jun 13 14:32:21 UnixBox2 kernel: cpuid = 1
Jun 13 14:32:21 UnixBox2 kernel: Uptime: 4h54m13s
Jun 13 14:32:21 UnixBox2 kernel: Cannot dump. No dump
Jun 12 23:02:41 UnixBox2 kernel: panic: page fault
Jun 12 23:02:41 UnixBox2 kernel: cpuid = 1
Jun 12 23:02:41 UnixBox2 kernel: Uptime: 1h21m59s
Jun 12 23:02:41 UnixBox2 kernel: Cannot dump. No dump device defined.
This is a regular occurrence, but varies by source. Brand new fBSD 6.3
machine
: [EMAIL PROTECTED]
> Subject: Re: reboot after panic : page fault for two
> consecutive days nowwith FreeBSD stable 7.0
>
> Quoting "Kris Kennaway" <[EMAIL PROTECTED]>:
>
> > eculp wrote:
> >> This is on a relatively new Dell dualcore with 4G of ram
> r
reeBSD 7.0-STABLE #258: Tue Jun 10 05:54:42 CDT 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/ENCONTACTO
Panic String: page fault
Dump Parity: 2395754794
Bounds: 2
Dump Status: good
the vmcore is about 300M so I'm not attaching it;) I could put it
on line at a moments notice. I th
EMAIL PROTECTED]:/usr/obj/usr/src/sys/ENCONTACTO
Panic String: page fault
Dump Parity: 2395754794
Bounds: 2
Dump Status: good
the vmcore is about 300M so I'm not attaching it;) I could put it on
line at a moments notice. I think that what I need is probably a crash
course on debugging
e Jun 10 05:54:42 CDT 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/ENCONTACTO
Panic String: page fault
Dump Parity: 2395754794
Bounds: 2
Dump Status: good
the vmcore is about 300M so I'm not attaching it;) I could put it on
line at a moments notice. I think that what I need is pr
ECTED]:/usr/obj/usr/src/sys/ENCONTACTO
Panic String: page fault
Dump Parity: 2395754794
Bounds: 2
Dump Status: good
the vmcore is about 300M so I'm not attaching it;) I could put it on
line at a moments notice. I think that what I need is probably a
crash course on debugging a cras
panic as
well as runs, but it detects all the USB devices AFTER boot has been
done, how ever X dosent seem to want to recognise it.
There other issues, however with having to swap from 1 comp to
another running from FreeBSD, i have no ability to paste dmesg or
anything like that.
ports
ouple of panics with it over
a day or two; I can't pinpoint what is causing it, it has panicked when I'm
not there and nothing seems to be going on. I recompiled the kernel shortly
after install, so don't know if it will panic on the generic kernel alone.
There is a vmcore in
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
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, but politely
ely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "amd64-marcel-freebsd".
Unread portion of the kernel message buffer:
ad8: FAILURE - WRITE_DMA48 timed out LBA=314770767
g_vfs_done():ad8s1a[WRITE(offset=161162592256, length=16384)]error = 5
pa
B was configured as "amd64-marcel-freebsd".
Unread portion of the kernel message buffer:
ad8: FAILURE - WRITE_DMA48 timed out LBA=314770767
g_vfs_done():ad8s1a[WRITE(offset=161162592256, length=16384)]error = 5
panic: flush_pagedep_deps: flush failed
cpuid = 0
Uptime: 3d15h11m52s
Physical
amd64-marcel-freebsd".
Unread portion of the kernel message buffer:
ad8: FAILURE - WRITE_DMA48 timed out LBA=314770767
g_vfs_done():ad8s1a[WRITE(offset=161162592256, length=16384)]error = 5
panic: flush_pagedep_deps: flush failed
cpuid = 0
Uptime: 3d15h11m52s
Physical memory: 1011 MB
Dumping
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
--
: FreeBSD Kernel Dump
Version String: FreeBSD 7.0-RELEASE-p1 #4: Wed May 14 10:10:03 CEST 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/STORAGE
Panic String: flush_pagedep_deps: flush failed
Dump Parity: 4068726879
Bounds: 1
Dump Status: good
anyone knows whats going on?
thanks
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 -
Kris Kennaway wrote:
Christopher Key wrote:
Can anyone suggest what I should be doing to try to get a crash dump
successfully to further diagnose this? Is there anything else
relevant I should post?
Configure DDB and obtain the traceback from that instead (see the
developers handbook)
Christopher Key wrote:
Can anyone suggest what I should be doing to try to get a crash dump
successfully to further diagnose this? Is there anything else relevant
I should post?
Configure DDB and obtain the traceback from that instead (see the
developers handbook)
Kris
__
27;m unable to get a crash dump. After the panic, all I get in the
console is,
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x5c05df
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc05bc0a0
stack poin
51-MHz
686-class CPU)
Origin = "AuthenticAMD" Id = 0x60fb2 Stepping = 2
Features=0x178bfbff
Features2=0x2001
AMD
Features=0xea500800
AMD Features2=0x11f
Cores per package: 2
real memory = 1878917120 (1791 MB)
avail memory = 1828098048 (1743 MB)
ACPI APIC Table:
AP #1
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, but politely
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
r/crash by default. See "dumpdir" in
> /etc/defaults/rc.conf. Try
>
> kgdb /boot/kernel/kernel.symbols /var/crash/vmcore.8
I will try it. Thank you.
> > Why Xorg do kernel panic?
>
> It has access to system internals via /dev/mem and /dev/io. So it can
> potent
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 Monday 12 May 2008 15:16:48 Aminuddin Abdullah wrote:
> I have 5 servers running almost at 70mbit/sec and each one of them will
> crash/reboot after more than 24 hours. The most it can stay up is 48 hours.
>
> How do I increase this memory from the default 320MB?
After some digging it looks li
:
> 7.0-RELEASE-i386-bootonly.iso
>
> Then burn on CD and then install fresh 7.0-RELEASE on hard disk - minimal
> system. Next I used portsnap to download ports:
> portsnap fetch
> [...]
Did you do a 'portsnap extract' as well? Fetching alone isn't enou
d disk - minimal
system. Next I used portsnap to download ports:
portsnap fetch
[...]
Then go to /usr/ports/x11/xorg and:
make install clean
After that, when I log as normal user and typed:
startx
got the first kernel panic. Then I used:
Xorg -configure
X -config /root/xorg.conf.new
and again
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
Architecture Version: 2
Dump Length: 2145722368B (2046 MB)
Blocksize: 512
Dumptime: Mon May 8 11:28:55 2008
Hostname: XXX
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 6.3-RELEASE #0: Wed Jan 16 04:45:45 UTC 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP
Panic String
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
compiled by ports system. After instalign 'xorg' ports I do the following
On Sun, 11 May 2008 00:17:03 +0200, Gilles <[EMAIL PROTECTED]>
wrote:
>No problem there. I did create my own /usr/local/etc/smb.conf, and
>smbpasswd is living under /usr/local/etc/samba/. The n-1 version
>worked fine, and this version was installed about a week ago.
I uninstalled, recompiled the P
On Sat, 10 May 2008 23:08:45 +0200, Mel
<[EMAIL PROTECTED]> wrote:
>Not sure it's related, but did you read the message you get before you
>installed this version?
>( cd /usr/ports/net/samba3 && make pre-everything)
# cd /usr/ports/net/samba3 && make pre-everything
===> NOTICE: This version of p
On Saturday 10 May 2008 15:40:02 Gilles wrote:
> [2008/05/10 10:29:59, 0] lib/util_tdb.c:tdb_log(664)
> tdb(/var/db/samba/locking.tdb): tdb_reopen: open failed (No such
> file or directory)
> FWIW, I downloaded the latest ports and compiled it recently to get
> samba-3.0.28a,1. I didn't get thi
Hello
I got a bunch of PANIC messages this morning on a FreeBSD 6.3 host,
and had to restart Samba:
[2008/05/10 10:28:51, 0] lib/util.c:smb_panic(1633)
PANIC (pid 43086): tdb_reopen_all failed.
[2008/05/10 10:28:51, 0] lib/util.c:log_stack_trace(1737)
BACKTRACE: 3 stack frames
ame pointer = 0x28:0xcc218c00
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 25 (irq11: ohci0)
trap number = 12
panic: page fault
Uptime:
tput from when a umass device is plugged in?
If you get a kernel panic, what does it say?
Is there anything in the logfiles?
> I have 7.0-rc1
> i386 on a laptop that also behaves mysteriously with umass devices
> (although it just takes 5 minutes to mount and then has gibberish, not
>
I've got an 7.0 amd64 system that plugging in any umass device will
cause it to immediately crash. You can plug in any ugen, ucom, or ums
with no ill effects and they work fine. Modern man cannot live
without the usb flash device. Anyone have any ideas? I have 7.0-rc1
i386 on a laptop that also
On Wed, Mar 26, 2008 at 05:35:05PM +, Alphons Fonz van Werven wrote:
> Sam Leffler wrote:
>
>> I am aware only of issues with USB adapters being removed while
>> wpa_supplicant is running.
>
> Actually, there's more I'm afraid.
>
> iwi: Don't know because I don't use that one. But it's a "c
Vince wrote:
there are some patches I missed?
Entirely possible, I'm running these versions
Thanks Vince, I'll check it out tomorrow (as well as gathering debug info
for the rum driver, btw), as it's getting quite late now.
At the moment, I have FreeBSD on my laptop but I can't do much wit
Alphons "Fonz" van Werven wrote:
Vince wrote:
under 7-current
Just noted the -current thingy. I'm running 7-release, with or without a
patch by Andrew (2 kernels available). If it works with 7-current, perhaps
there are some patches I missed?
Alphons
Entirely possible, I'm running these ve
Alphons "Fonz" van Werven wrote:
Vince wrote:
Not true. under 7-current for me wpa works on my wpi adapter.
Care to elaborate on what you did? Because in my and some other people's
cases
we can't get wpi to work with wpa_supplicant no matter what we try.
Alphons (as can be seen in some pre
Vince wrote:
under 7-current
Just noted the -current thingy. I'm running 7-release, with or without a
patch by Andrew (2 kernels available). If it works with 7-current, perhaps
there are some patches I missed?
Alphons
--
All right, that does it Bill [Donahue]. I'm pretty sure that killing Je
;m working in my office from around 9 o'clock and
each day after 4 hours the system panic'ed:
Mar 25 09:02:43 rebelion syslogd: kernel boot file is /boot/kernel/kernel
Mar 25 13:00:03 rebelion savecore: reboot after panic: clist reservation botch
Mar 26 09:11:04 rebelion syslogd: kerne
Vince wrote:
Not true. under 7-current for me wpa works on my wpi adapter.
Care to elaborate on what you did? Because in my and some other people's cases
we can't get wpi to work with wpa_supplicant no matter what we try.
Alphons (as can be seen in some previous threads)
--
All right, that d
wpi
and
if I'm not mistaken it was the same person who initiated
development of
both drivers.
wpi: No panics, but just doesn't work with wpa_supplicant at all (fails to
associate). This is a known problem and people are working on it.
Not true. under 7-current for me
Sam Leffler wrote:
I am aware only of issues with USB adapters being removed while
wpa_supplicant is running.
Actually, there's more I'm afraid.
iwi: Don't know because I don't use that one. But it's a "cousin" of wpi and
if I'm not mistaken it was the same person who initiated developme
Alphons "Fonz" van Werven wrote:
Matthias Apitz wrote:
the main difference between home and work is: WEP at home and WPA2 at
work;
Which WiFi board are you using? Several drivers are known to cause
panics when
used with WPA.
I am aware only of issues with USB adapters being removed while
El día Wednesday, March 26, 2008 a las 01:47:01PM +, Alphons Fonz van
Werven escribió:
> Matthias Apitz wrote:
>
> >the main difference between home and work is: WEP at home and WPA2 at
> >work;
>
> Which WiFi board are you using? Several drivers are known to cause panics
> when
> used wit
Matthias Apitz wrote:
the main difference between home and work is: WEP at home and WPA2 at
work;
Which WiFi board are you using? Several drivers are known to cause panics when
used with WPA.
Alphons
--
All right, that does it Bill [Donahue]. I'm pretty sure that killing Jesus
is not very Ch
rom around 9 o'clock and
each day after 4 hours the system panic'ed:
Mar 25 09:02:43 rebelion syslogd: kernel boot file is /boot/kernel/kernel
Mar 25 13:00:03 rebelion savecore: reboot after panic: clist reservation botch
Mar 26 09:11:04 rebelion syslogd: kernel boot file is /boot/ker
Hi
I had a kernel panic on an Acer TravelMate. I use zfs and this is a i386.
This is 7-stable, built kernel and world yesterday.
I was playing music with mpg321, using X (mozilla) and the panic happened
while (as root) I typed 'sysctl -a|grep recvspace'
[EMAIL PROTECTED] /usr/obj/usr/s
Hello everyone,
I tried the 6.3 to 7.0 upgrade with cvsup & Co. i already had the
gmirror device functioning properly
after first mergemaster -p i did boot the 7.0 with nextboot to try. ok,
the second mergemaster passed smooth and i tried to boot with old kernel
cause forgot about the nextboot
Hello everyone,
I tried the 6.3 to 7.0 upgrade with cvsup & Co. i already had the
gmirror device functioning properly
after first mergemaster -p i did boot the 7.0 with nextboot to try. ok,
the second mergemaster passed smooth and i tried to boot with old kernel
cause forgot about the nextboot
rap number = 12
panic: page fault
cpuid = 0
Uptime: 1m9s
Physical memory: 2033 MB
Dumping 179 MB: 164 148 132 116 (CTRL-C to abort) 100 84 68 52 36 20 4
#0 doadump () at pcpu.h:195
195 pcpu.h: No such file or directory.
in pcpu.h
This can be traced back to somewhere within the
On 3/7/08, Stacey Roberts <[EMAIL PROTECTED]> wrote:
> Hi Bob,
> Thanks for the response..,
>
> On Fri, 07 Mar 2008, Bob Johnson wrote:
>
> > On 3/7/08, Stacey Roberts <[EMAIL PROTECTED]> wrote:
[...]
> > Yep. The HP BIOS is a bit bogus. It won't reveal memory information to
> > the AMD64 boot code
Hi Bob,
Thanks for the response..,
On Fri, 07 Mar 2008, Bob Johnson wrote:
> On 3/7/08, Stacey Roberts <[EMAIL PROTECTED]> wrote:
> > Hello,
> > Is anyone aware if this issue is fixed in FreeBSD 7.0-RELEASE / STABLE?
> >
>
> It is NOT fixed in -RELEASE and I doubt it is fixed in -STABLE.
>
> workstation
> at work, but the installation CDs always fail with the error: panic: No BIOS
> smap info from loader.
>
Yep. The HP BIOS is a bit bogus. It won't reveal memory information to
the AMD64 boot code.
> My case appear exactly as is referenced in the above PR fil
Hello,
Is anyone aware if this issue is fixed in FreeBSD 7.0-RELEASE / STABLE?
I've been trying to get FreeBSD-7 amd64 installed on an HP dc7700p workstation
at work, but the installation CDs always fail with the error: panic: No BIOS
smap info from loader.
My case appear exactly
El día Saturday, March 01, 2008 a las 02:52:41PM +0100, Matthias Apitz escribió:
>
> Hello,
>
> I'm installing 7.0R on a Fujitsu Siemens Lifebook C series
> X11 comes up but the box panic's on first console switch or
> on exit of X (fully reproduceable, also with ACPI off);
>
> I've put the Xor
02, 2008 10:12 AM
> To: freebsd-questions@freebsd.org
> Subject: Re: ndis0 panic when ifconfig inet IP address
>
>
> Update:
>
> I wasn't able to solve the problem so resorted to installing FreeBSD 6.3
> instead, and got the wireless working without any difficulty. I
Update:
I wasn't able to solve the problem so resorted to installing FreeBSD 6.3
instead, and got the wireless working without any difficulty. I guess
that some of the ndis kernel code has been changed in 7.0 that is
causing my system to panic.
Glenn
> I have just upgraded my Asus A2
Hello,
I'm installing 7.0R on a Fujitsu Siemens Lifebook C series
X11 comes up but the box panic's on first console switch or
on exit of X (fully reproduceable, also with ACPI off);
I've put the Xorg.0.log and /etc/X11/xorg.conf here is someone wants
to have a look:
http://www.unixarea.de/Xorg
I have just upgraded my Asus A2 notebook from 6.1 to FreeBSD 7.0-RELEASE
#0 by doing a full clean install. (completely repartitioned my disc
prior to installing)
This notebook uses the Broadcom bcmwl5 wireless drivers which worked
faultlessly using ndis on 6.1
I can kldload ndis and driver bcmwl5
ikely to make code misbehave.
>
>
> 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/sys/boot/i386/loader/../../co
201 - 300 of 1049 matches
Mail list logo
