David S. wrote:
Hello there,
unfortunately my newly acquired Lenovo Desktop, Model Number A5790R
will Kernel Panic before during boot. The install of i386 4.6 itself
goes fine. I tried to boot with acpi disabled, to no avail. Also i
played around with various settings in the BIOS pertaining to
On Mon, Nov 16, 2009 at 8:49 PM, Jonathan Gray wrote:
> On Mon, Nov 16, 2009 at 08:31:59PM +0800, David S. wrote:
>> Hello there,
>>
>> unfortunately my newly acquired Lenovo Desktop, Model Number A5790R
>> will Kernel Panic before during boot. The install of i386 4.6 i
On Mon, Nov 16, 2009 at 08:31:59PM +0800, David S. wrote:
> Hello there,
>
> unfortunately my newly acquired Lenovo Desktop, Model Number A5790R
> will Kernel Panic before during boot. The install of i386 4.6 itself
> goes fine. I tried to boot with acpi disabled, to no avail.
Hello there,
unfortunately my newly acquired Lenovo Desktop, Model Number A5790R
will Kernel Panic before during boot. The install of i386 4.6 itself
goes fine. I tried to boot with acpi disabled, to no avail. Also i
played around with various settings in the BIOS pertaining to certain
CPU
2009, Matthew Dempsky wrote:
> On Mon, May 11, 2009 at 8:34 PM, Matthew Dempsky wrote:
> > I just installed the latest OpenBSD/i386 snapshot on my Aspire One,
> > and if I run "ifconfig ath0 scan", it results in a kernel panic.
>
> Doh, just found in the archi
On Mon, May 11, 2009 at 8:34 PM, Matthew Dempsky wrote:
> I just installed the latest OpenBSD/i386 snapshot on my Aspire One,
> and if I run "ifconfig ath0 scan", it results in a kernel panic.
Doh, just found in the archives that this is a known issue.
I couldn't find men
I just installed the latest OpenBSD/i386 snapshot on my Aspire One,
and if I run "ifconfig ath0 scan", it results in a kernel panic.
Also worth pointing out, if I touch the touchpad at all during the
installer, it results in a few lines of "pckbcintr: no dev for slot
1". Thi
On Fri, 08 May 2009 17:41:08 -0400
Dan wrote:
> Today after I executed a stop on apache the machine crashed and
> generated a /var/crash with:
> 2.0Kbounds
> 6.5Mbsd.0
> 2.0Kbsd.0.core
> 2.0Kminfree
>
>
> I have been searching and have not found a site in regards to debug
> this
> Today after I executed a stop on apache the machine crashed and generated a
> /var/crash with:
> 2.0Kbounds
> 6.5Mbsd.0
> 2.0Kbsd.0.core
> 2.0Kminfree
man savecore
Today after I executed a stop on apache the machine crashed and generated a
/var/crash with:
2.0Kbounds
6.5Mbsd.0
2.0Kbsd.0.core
2.0Kminfree
I have been searching and have not found a site in regards to debug this on
OpenBSD. Could somebody shed some light?
Thank you.
Daniel
Hi,
I got a "bad ref count" panic message while trying to access a directory
on a 45 GB ext3 partition. Below is what I managed to salvage. Any
workarounds for this? Anyway, got GNOME on OpenBSD up and running, made
very easy, great!
Bill
-
On Tue, 28 Apr 2009 02:34:40 +0200 "Erwin van Maanen"
wrote:
> I've tried to do include the panic and trace with the screenshots i
> attached, i'm afraid i dont know another way to get the info across.
> I can appreciate the devs not being able to look at the/each
> virtualization issue, i was ju
dag 27 april 2009 17:48
To: Erwin van Maanen
Cc: misc@openbsd.org
Subject: Re: vmware esxi 3.5u4: amd64 4.4 generic bsd.mp kernel panic
On Mon, 27 Apr 2009 16:16:57 +0200 "Erwin van Maanen"
wrote:
> Running OpenBSD on a vmware esxi server, whenever i boot the amd64
> bsd.mp versi
On Mon, 27 Apr 2009 16:16:57 +0200 "Erwin van Maanen"
wrote:
> Running OpenBSD on a vmware esxi server, whenever i boot the amd64
> bsd.mp version i get stuck with kernel panic.
>
> panic: fp_save ipi didn't
>
>
>
> I've tried several things:
On 2009-04-27, Erwin van Maanen wrote:
> Running OpenBSD on a vmware esxi server, whenever i boot the amd64 bsd.mp
> version i get stuck with kernel panic.
please try 4.5 or -current; esxi amd64 MP works fine in -current for sure.
Running OpenBSD on a vmware esxi server, whenever i boot the amd64 bsd.mp
version i get stuck with kernel panic.
panic: fp_save ipi didn't
I've tried several things:
- amd64 bsd.mp, without network card(s): boots normal
- amd64 bsd.mp, with tricked network card to flexible (
Hi Daniel and Misc@,
On Sun, 08 Mar 2009 06:29:22 +0700, Daniel Ouellet
wrote:
Claudio Jeker wrote:
Fell free to disagree, that's fair.
Sorry, I don't get it a non-developer tries to educate a developer
about
how kernel crashes should be reported? Sorry most of your standpoints
are
j
Hi All,
On Sun, 08 Mar 2009 18:01:50 +0700, FRLinux wrote:
On Sat, Mar 7, 2009 at 11:29 PM, Daniel Ouellet
wrote:
I was clearly out of place.
Same to you Steph, I shouldn't have reacted so quickly to your email
address
and have wrongly concluded to an other Linux quick miss place question
Stefan Sperling wrote:
On Sat, Mar 07, 2009 at 06:29:22PM -0500, Daniel Ouellet wrote:
Claudio Jeker wrote:
Fell free to disagree, that's fair.
Sorry, I don't get it a non-developer tries to educate a developer about
how kernel crashes should be reported? Sorry most of your standpoints are
ju
On Sat, Mar 07, 2009 at 06:29:22PM -0500, Daniel Ouellet wrote:
> Claudio Jeker wrote:
>>> Fell free to disagree, that's fair.
>>>
>>
>> Sorry, I don't get it a non-developer tries to educate a developer about
>> how kernel crashes should be reported? Sorry most of your standpoints are
>> just wron
On Sat, Mar 7, 2009 at 11:29 PM, Daniel Ouellet wrote:
> I was clearly out of place.
>
> Same to you Steph, I shouldn't have reacted so quickly to your email address
> and have wrongly concluded to an other Linux quick miss place question, or
> reaction.
What I've learned from this is fairly simp
Claudio Jeker wrote:
Fell free to disagree, that's fair.
Sorry, I don't get it a non-developer tries to educate a developer about
how kernel crashes should be reported? Sorry most of your standpoints are
just wrong. Sure people are encuraged to run snapshot kernels but
selfbuilt kernels are fi
Hi Claudio and Misc@,
On Sat, 07 Mar 2009 14:35:30 +0700, Claudio Jeker
wrote:
On Fri, Mar 06, 2009 at 08:58:08PM -0500, Daniel Ouellet wrote:
Stefan Sperling wrote:
On Fri, Mar 06, 2009 at 06:07:00PM -0500, Daniel Ouellet wrote:
Insan Praja SW wrote:
Hi,
On Sat, 07 Mar 2009 03:17:57 +07
On Fri, Mar 6, 2009 at 9:24 PM, Robert wrote:
> Wrong.
> Reporting problems with kernels built from unmodified source is fine.
Appologies, I stant corrected.
Steph
On Fri, Mar 06, 2009 at 08:58:08PM -0500, Daniel Ouellet wrote:
> Stefan Sperling wrote:
>> And note that there have recently been changes in the way pf
>> keeps track of icmp, so this may well be a valid report.
>
> Could sure be I give you that. However, still true that snapshot is the
> way to
On Fri, 06 Mar 2009 20:58:08 -0500 Daniel Ouellet
wrote:
> Fell free to disagree, that's fair.
>
> Best,
> Daniel
With all due respect Daniel, I disagree, and I think you've misread
things a bit. The original poster, Insan Praja, stated he had a panic
with both a GENERIC kernel, and with the sn
On Fri, Mar 06, 2009 at 08:58:08PM -0500, Daniel Ouellet wrote:
> Stefan Sperling wrote:
>> On Fri, Mar 06, 2009 at 06:07:00PM -0500, Daniel Ouellet wrote:
>>> Insan Praja SW wrote:
Hi,
On Sat, 07 Mar 2009 03:17:57 +0700, FRLinux wrote:
> On Fri, Mar 6, 2009 at 7:12 PM, Insan Pr
Stefan Sperling wrote:
On Fri, Mar 06, 2009 at 06:07:00PM -0500, Daniel Ouellet wrote:
Insan Praja SW wrote:
Hi,
On Sat, 07 Mar 2009 03:17:57 +0700, FRLinux wrote:
On Fri, Mar 6, 2009 at 7:12 PM, Insan Praja SW
wrote:
Hi Misc@,
on a i386 kernel recent build (6th march), I got panic. It say
On Fri, Mar 06, 2009 at 06:07:00PM -0500, Daniel Ouellet wrote:
> Insan Praja SW wrote:
>> Hi,
>> On Sat, 07 Mar 2009 03:17:57 +0700, FRLinux wrote:
>>
>>> On Fri, Mar 6, 2009 at 7:12 PM, Insan Praja SW
>>> wrote:
Hi Misc@,
on a i386 kernel recent build (6th march), I got panic. It say
Insan Praja SW wrote:
Hi,
On Sat, 07 Mar 2009 03:17:57 +0700, FRLinux wrote:
On Fri, Mar 6, 2009 at 7:12 PM, Insan Praja SW
wrote:
Hi Misc@,
on a i386 kernel recent build (6th march), I got panic. It says:
Hello,
As far as I know, home built kernel is not supported, you need to try
out a
On Fri, 6 Mar 2009 20:17:57 +
FRLinux wrote:
> Hello,
>
> As far as I know, home built kernel is not supported, you need to try
> out a snapshot instead and see if it works.
>
> Cheers,
> Steph
Wrong.
Reporting problems with kernels built from unmodified source is fine.
- Robert
Hi,
On Sat, 07 Mar 2009 03:17:57 +0700, FRLinux wrote:
On Fri, Mar 6, 2009 at 7:12 PM, Insan Praja SW
wrote:
Hi Misc@,
on a i386 kernel recent build (6th march), I got panic. It says:
Hello,
As far as I know, home built kernel is not supported, you need to try
out a snapshot instead and s
On Fri, Mar 6, 2009 at 7:12 PM, Insan Praja SW wrote:
> Hi Misc@,
> on a i386 kernel recent build (6th march), I got panic. It says:
Hello,
As far as I know, home built kernel is not supported, you need to try
out a snapshot instead and see if it works.
Cheers,
Steph
Hi Misc@,
on a i386 kernel recent build (6th march), I got panic. It says:
uvm_fault(0xd08079c0, 0x0, 0, 1) -> e
kernel: page fault trap, code=0
Stopped at pf_icmp_mapping+0x45: movw 0x4(%eax),%ax
ddb> trace
pf_icmp_mapping(dc2c5ba0,8,dc2c5b34,dc2c5b38,dc2c5b3c,dc2c5b3e,2) at
pf_icmp_mapping+0x4
On Sun, Jan 11, 2009 at 1:40 PM, Tom Cosgrove
wrote:
> This appears to be fixed in -current/the latest snapshot.
>
> Can you try a version >= the following (which fixed exactly the same
> problem on my laptop):
>
>OpenBSD 4.4-current (GENERIC.MP) #32: Fri Jan 9 10:34:10 MST 2009
>t...
This appears to be fixed in -current/the latest snapshot.
Can you try a version >= the following (which fixed exactly the same
problem on my laptop):
OpenBSD 4.4-current (GENERIC.MP) #32: Fri Jan 9 10:34:10 MST 2009
t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
Hi
This is the first problem I've had with OpenBSD, I think I've attached all
relevant information but if i've neglected anything please let me know.
I'm getting the following panic at boot time with the latest snapshot dated
1/9/09
uvm_fault(0xd08084a0, 0x12e3e000, 0, 3) -> e
kernel: page fault t
SMP related inter-process-interrupts, likely your ATI Rage XL is causing the
problem,
but this is a very wilde guess, perhaps try to replace ands see if happens
again?
I've got a V440 running, however it headless.
ioan
>>> Michael <[EMAIL PROTECTED]> 30/07/2008 12:24:46 >>>
Hi all,
I just ha
Hi again,
Michael schrieb:
I just had my v440 crash on me with a weird message (at the end of the
dmesg). Any ideas why that happened?
Noone? Wrong list? Would tech@ or sparc@ be better?
console is /[EMAIL PROTECTED],60/[EMAIL PROTECTED]/[EMAIL PROTECTED],3f8
Copyright (c) 1982, 1986,
Hi all,
I just had my v440 crash on me with a weird message (at the end of the
dmesg). Any ideas why that happened?
console is /[EMAIL PROTECTED],60/[EMAIL PROTECTED]/[EMAIL PROTECTED],3f8
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. Al
Oops, sorry for not leaving feedback, it is indeed stable again with rev.
1.607. I have been pushing it quite hard for 24 hours now and it keeps
running fine now.
>
>
> 2008/7/8 David Krause <[EMAIL PROTECTED]>:
>
> * Karl Karlsson <[EMAIL PROTECTED]> [080706 07:37]:
>> > That last one that got fi
On Tue, 08 Jul 2008 21:59:43 +0700, David Krause <[EMAIL PROTECTED]>
wrote:
Hi Misc@,
Currently I am on AMD64 4.4-beta, and yes.. I got the latest source from
July 7, and yes, it is been a stable machine for about a day, no complains
or anything.
Thanks all,
Insan
* Insan Praja SW <[EMA
* Karl Karlsson <[EMAIL PROTECTED]> [2008-07-06 14:36]:
> That last one that got fixed by henning seems to work now, however i hit
> another one.
>
> Scenario-NATing OBSD i386 acting as gw and and redirecting a port 39965 to
> laptop behind running WinXP. Regular surfing works ok and is stable but
That last one that got fixed by henning seems to work now, however i hit
another one.
Scenario-NATing OBSD i386 acting as gw and and redirecting a port 39965 to
laptop behind running WinXP. Regular surfing works ok and is stable but if i
start ytorrent and 3-4 different torrents this panics instan
* Insan Praja SW <[EMAIL PROTECTED]> [2008-06-24 18:32]:
> Stopped at pf_state_tree_RB_REMOVE_COLOR + 0x1C0: cmpl $0x1,0x40(%rsi)
sometimes it takes a few reads until things are obvious.
please try this diff.
Index: pf.c
===
RCS fil
Not an AMD64 specific thing then?
On Thu, 2008-07-03 at 15:03 +0200, Henning Brauer wrote:
> * Insan Praja SW <[EMAIL PROTECTED]> [2008-06-24 18:32]:
> > Hi Misc@,
> > I currently caught a kernel panic that says:
> > uvm_fault(0x 80b7b0e0, 0x0, 0, 1) ->
Thursday, July 03, 2008 9:04 AM
> > To: misc@openbsd.org
> > Subject: Re: Kernel Panic on AMD64 24 June snapshot
> >
> > * Insan Praja SW <[EMAIL PROTECTED]> [2008-06-24 18:32]:
> > > Hi Misc@,
> > > I currently caught a kernel panic that says:
> &
giovanni schrieb:
well, I'm not alone
same behaviour as stated in:
http://marc.info/?l=openbsd-misc&m=121396323512149&w=2
moreover if I do not use any wpa it does not panic. did you try this?
Hi Giovanni,
no, I did not really tested it, I only tried out wpa and saw that it
worked with wpa
Yes I know its experimental... ;-)
I bought a ASUS WL-130N, installed the latest snapshot (from July 2nd)
and tried WPA
I build the pre-shared key
# wpa-psk ZELDA start123
0x763b94d25e9800f80f926fcc26d7fdf52b3b565209456bd0aa31973fbd8d5ce2
and put it in my /etc/hostname.ral0
# cat /etc/hostname
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of Henning Brauer
> Sent: Thursday, July 03, 2008 9:04 AM
> To: misc@openbsd.org
> Subject: Re: Kernel Panic on AMD64 24 June snapshot
>
> * Insan Praja SW <[EMAIL PROTECTED]> [2008-06-24 18:32]:
> > H
* Insan Praja SW <[EMAIL PROTECTED]> [2008-06-24 18:32]:
> Hi Misc@,
> I currently caught a kernel panic that says:
> uvm_fault(0x 80b7b0e0, 0x0, 0, 1) -> e
> kernel : page fault trap, code=0
> Stopped at pf_state_tree_RB_REMOVE_COLOR + 0x1C0: cmpl $0x1,0x40(%rsi
x1948
pf_test_rule() at pf_test_rule+0x4d8
pf_test() at pf_test+0x944
ipv4_input() at ipv4_input+0x153
ipintr() at ipintr+0x6d
Xsoftnet() at Xsoftnet+0x4a
interrupt ---
end trace frame" 0x0, count: -10
0:
ddb{0}>
and this is the kernel panic before I update:
uvm_fault(0x 8
On Wed, 25 Jun 2008 20:47:50 +0700, Insan Praja SW <[EMAIL PROTECTED]>
wrote:
Sorry, the title should be "25 June AMD64 Snapshots Kernel Panic"
Thanks,
Insan
Hi Misc@,
This is a recent panic I got on "OpenBSD 4.3-current (GENERIC.MP) #8:
Wed Jun 25 09:55:34 WIT 2008&quo
On Tue, 24 Jun 2008 23:55:47 +0700, Stuart Henderson <[EMAIL PROTECTED]>
wrote:
In gmane.os.openbsd.misc, you wrote:
Stopped at pf_state_tree_RB_REMOVE_COLOR + 0x1C0: cmpl $0x1,0x40(%rsi)
OpenBSD 4.3-current (GENERIC.MP) #7: Tue Jun 24 20:27:50 WIT 2008
We can't tell which files are in
Hi Misc@,
I currently caught a kernel panic that says:
uvm_fault(0x 80b7b0e0, 0x0, 0, 1) -> e
kernel : page fault trap, code=0
Stopped at pf_state_tree_RB_REMOVE_COLOR + 0x1C0: cmpl $0x1,0x40(%rsi)
ddb {0}> trace
pf_state_tree_RB_REMOVE_COLOR() at pf_state_tree_RB_REMOVE_COLOR
Josh Grosse wrote:
On Mon, 14 Apr 2008 08:57:55 -0700, Dag Richards wrote
Then I performed a boot dump, I have
drwxrwx--- 2 root wheel 512 Apr 14 07:53 ./
drwxr-xr-x 25 root wheel 512 Aug 28 2007 ../
-rw--- 1 root wheel 2 Apr 14 07:51 bounds
-rw---
On Mon, 14 Apr 2008 08:57:55 -0700, Dag Richards wrote
> Then I performed a boot dump, I have
> drwxrwx--- 2 root wheel 512 Apr 14 07:53 ./
> drwxr-xr-x 25 root wheel 512 Aug 28 2007 ../
> -rw--- 1 root wheel 2 Apr 14 07:51 bounds
> -rw--- 1 root w
Understand that I am not (quite) reporting a panic without a ps and trace.
I had kernel panic this weekend on my standby vpn firewall, this is the
third time this has happened in the last 300 days or so, always with the
same panic.
I run with ddb.log=1
I ran ps and trace expecting the output
Hello,
today one of my freshly upgraded machines after one week of normal
work hanged up.
Don't think it's hardware related, machine was working with 4.2-
stable for last 3 months without doubt.
Any idea what caused that hangup ?
I saw the following on the console and could only to
VS, and i still have the trouble, last cvs checkout and build
was yesterday.
On the panic, in ddb, i typed trace, ps, boot dump or boot crash. I
failed to find the kernel panic in /var/log/messages*. I have space in
all partitions, read http://www.openbsd.org/report.html, crash(4),
savecore(8) have ddb.
Oups... Correct version with attachement. Sorry.
When booting a 4.2-current kernel on a HP Compaq dc7800, the system crashes if
ACPI is enabled (this is by default with current).
Attached a dmesg. I can test patches if necessary.
The same problem arises on Linux 2.6, so this might be related to
When booting a 4.2-current kernel on a HP Compaq dc7800, the system crashes if
ACPI is enabled (this is by default with current).
Attached a dmesg. I can test patches if necessary.
The same problem arises on Linux 2.6, so this might be related to the BIOS.
Sincerely,
Aur
Dear all,
Recently I've installed a fujitsu-siemens motherboard with obsd 4.1. At
first, it works. Then, after I use amd64 kernel and configure ot with:
option MSGMNB=16384 # max # of bytes in a queue
option MSGMNI=80 # number of message queue identifiers
option MSGSEG=4096 # number of message seg
Reading the wd man page, I assumed that flash cards were supported in
Openbsd 4.1. This particular combo of SanDisk's CompactFlash PC Card
Adapter model SDAD-38-A10 with two different SanDisk compactflash
cards generated kernel panic as soon as the compact flash cards were
inserted i
to go terribly wrong, I can even scan
with `ifconfig -M uath0`. However, it cannot associate with any access
points. And if I have the device in at startup I get a pretty nasty
kernel panic. It is also worth noting that I am not actually detaching
the device when those events come up in the dmesg.
It
`. However, it cannot associate with any access
points. And if I have the device in at startup I get a pretty nasty
kernel panic. It is also worth noting that I am not actually detaching
the device when those events come up in the dmesg.
I have posted this previously to bugs@, but I decided to repost it
Greetings:
I will not have time for a proper bug report until this evening when I
get home, but I thought I would throw this out there for now.
This issue is reproducible, and it occurred in the previous snapshot
as well. Briefly, here is how it happens:
I have net.inet.ip.forwarding=1, and two
On Mon, 30 Oct 2006 10:47:13 -0800
Ben Calvert <[EMAIL PROTECTED]> wrote:
> This is on a 400mhz 1st gen tibook. It boots & runs fine with 3.9.
>
> Unfortunately the keyboard isn't doing anything useful, so all i can
> report is what's on the screen:
>
> the last message is:
> -
> openpic0
This is on a 400mhz 1st gen tibook. It boots & runs fine with 3.9.
Unfortunately the keyboard isn't doing anything useful, so all i can
report is what's on the screen:
the last message is:
-
openpic0 at macobio0 offset 0x4000panic: trap type 200 at 2eafb0
( openpic_do_pending_int+0x230
Hello misc@,
I just wanted to do my unfrequent updates to -current (using snapshots),
but for some reason bsd.rd panics (I transcribed messages by hand, see
below), but bsd does not panic (just copied it to / using my installed
snapshot).
Here is the last couple of lines:
ath0 at pci1 dev 2 funct
On Wed, 11 Oct 2006, Damien Bergamini wrote:
| Here are the appropriate dmesg lines:
| ral0 at pci1 dev 9 function 0 "Ralink RT2561S" rev 0x00: irq 12, address
| 00:16:b6:98:85:1f
| ral0: MAC/BBP RT2661B, RF RT2527
Another appropriate dmesg line would have been the OS version and
the architectu
I'm trying to install a Linksys G (WMP54G) wireless pci adapter. I've
checked the man pages for the ral driver and this is one of the cards
listed as being supported.
Here are the appropriate dmesg lines:
ral0 at pci1 dev 9 function 0 "Ralink RT2561S" rev 0x00: irq 12, address
00:16:b6:98:85:1
T. Valent wrote:
I am still not sure if MFS helps me. My project is an embedded system
that does not have a swap. I'm pretty sure the system will not run out
of memory. So am I supposed to create the MFS on swap though I don't
have any?
From an "embedded" box running from CF and without swap:
>> Anyway, I agree with you here that I maybe should have taken a closer
>> look at MFS. I just didn't take it into consideration because I have
>> worked with rdconfig since OpenBSD 3.2 without problems.
>
> There's not much crosslinking in the manual between them, I wonder
> whether rd(4) should
On 2006/10/04 18:35, T. Valent wrote:
> I am still not sure if MFS helps me. My project is an embedded system
> that does not have a swap. I'm pretty sure the system will not run out
> of memory. So am I supposed to create the MFS on swap though I don't
> have any?
Yes, this is fine. You don't nee
>>>> Problem: Using disklabel on /dev/rd0c causes a kernel panic.
>>> I think you're looking for mount_mfs(8), its use is demonstrated
>>> in fstab(5).
>> No. MFS != ramdisk
> Exactly. rd(4) is for ramdisks built-in to kernels, MFS is for
> normal use
On 2006/10/04 17:17, T. Valent wrote:
> >> Problem: Using disklabel on /dev/rd0c causes a kernel panic.
> > I think you're looking for mount_mfs(8), its use is demonstrated
> > in fstab(5).
>
> No. MFS != ramdisk
Exactly. rd(4) is for ramdisks built-in t
>> Problem: Using disklabel on /dev/rd0c causes a kernel panic.
> I think you're looking for mount_mfs(8), its use is demonstrated
> in fstab(5).
No. MFS != ramdisk
Just try what I wrote in my first mail. Create a ramdisk with rdconfig
and then you'll see what I mean.
T.
On 2006/10/04 11:05, T. Valent wrote:
> Problem: Using disklabel on /dev/rd0c causes a kernel panic.
I think you're looking for mount_mfs(8), its use is demonstrated
in fstab(5).
In case anyone could be interested:
I found a workaround. As far as I understand the disk structure of an
internal ramdisk, I would regard the workaround as to be senseless, but
it works:
OpenBSD 3.9:
Problem: Using disklabel on /dev/rd0c causes a kernel panic.
Workaround: Use fdisk on rd0
Hi!
Using the ramdisk kernel feature results in a kernel problem when I use
the disklabel command on the ramdisk.
This is what I do :
Use 3.9 (tried sys.tgz from mirror as well as updated sources from cvs)
in /usr/src/sys/arch/i386/conf
cp GENERIC Test
echo pseudo-device rd 1
This sounds like bad hardware to me. Have you tried installing your CD
set
elsewhere?
Ok, so I made a memtest86 boot cd to test out this machine. At the moment
it is 59% of the way through the testing and it's only found 7,016 memory
errors, that's not that bad, right? :-)
So bad hardware it
This sounds like bad hardware to me. Have you tried installing your CD set
elsewhere?
/marco
On Thu, Aug 24, 2006 at 10:00:50AM -0500, Jeff Bromberger wrote:
> I'm a new openbsd user (or I should say I'm attempting to be) and I'm not
> having a ton of luck here. I bought the cd set (i386) and
On 8/24/06, Jeff Bromberger <[EMAIL PROTECTED]> wrote:
I'm a new openbsd user (or I should say I'm attempting to be) and I'm not
having a ton of luck here. I bought the cd set (i386) and it arrived
yesterday. During the install, the base39.tgz file seemed to be corrupt and
the install would cr
I'm a new openbsd user (or I should say I'm attempting to be) and I'm not
having a ton of luck here. I bought the cd set (i386) and it arrived
yesterday. During the install, the base39.tgz file seemed to be corrupt and
the install would crash, the kernel would panic and the machine would reboot.
We have a G3 mac here running mail/dns and this morning it died. I had
to reboot it, so I wasn't able to run trace or ps. Any clues as to what
may have happened? I don't see anything in my logs.
from dmesg:
===
kern dsi on addr 3c200068 iar 304430
panic: trap type 300 at 304430 (uvm_unmap_remov
Stuart Henderson wrote:
On 2006/07/13 10:09, Federico Giannici wrote:
When I had a bad cpu in May I hardly saw the problem with April 24
kernel (still available in snapshots/i386/non-pae) - I had to run
`stress' and `make build' together and wait a while to see it,
whereas the May 7 snapshot fai
On 2006/07/13 10:09, Federico Giannici wrote:
> >When I had a bad cpu in May I hardly saw the problem with April 24
> >kernel (still available in snapshots/i386/non-pae) - I had to run
> >`stress' and `make build' together and wait a while to see it,
> >whereas the May 7 snapshot failed very quickl
Stuart Henderson wrote:
On 2006/07/12 11:59, Federico Giannici wrote:
Probably you already know it: the i386 snapshot of Jul 4 (both MP and
SP) made our system to freeze (usually after a few hours, sometime after
a few minutes) and a couple of time made the system crash with a page fault.
We
Any ideas what can be a wrong?
on -Current (3.8, 3.9, 3.9STABLE too)
ahd0: target 0 using asynchronous transfers
ahd0: SCB = 508 Not Active!
panic: Waiting list traversal
Stopped ad Debugger+0x4:popl %ebp
after some seconds it freezes
No newer BIOS available
And SMP kernel is not wor
On 2006/07/12 11:59, Federico Giannici wrote:
> Probably you already know it: the i386 snapshot of Jul 4 (both MP and
> SP) made our system to freeze (usually after a few hours, sometime after
> a few minutes) and a couple of time made the system crash with a page fault.
>
> We downgraded to 3.9
Probably you already know it: the i386 snapshot of Jul 4 (both MP and
SP) made our system to freeze (usually after a few hours, sometime after
a few minutes) and a couple of time made the system crash with a page fault.
We downgraded to 3.9 and the problems disappeared.
Bye.
Federico Gianni
I had almost the same problem here too.
Box is dell 1850 with MP-board, 1 CPU inside, running GENERIC.MP.
It stopped to accept any connections, but:
1. responded to ping very quickly
2. syn-scan gave out that ports were open (those which should be open)
4. no heavy traffic incoming
3. no dumps on c
Hello all,
We also faced similar problem several times after upgrading to 3.9.
What could be the problem?
regards
murthy
Federico Giannici wrote:
> It happened again: one of our servers with OpenBSD i386 3.9-current MP
> of a couple days ago crashed with the following kernel error:
>
It happened again: one of our servers with OpenBSD i386 3.9-current MP
of a couple days ago crashed with the following kernel error:
uvm_fault(0xd071cd68, 0xeb64c000, 0, 1) -> e
kernel: page fault trap, code=0
Stopped at pmap_page_remove_86+0x114 movl 0(%eax,%edx,4),%eax
Unfortunately I wasn'
sa wrote:
+ afsd_ieee80211_newstate: bogus xmit rate 11 setup
You can reproduce this panic by changing from 11g to 11b.
I reported a quite similar pamic (SIC :) [1] some time ago, but
following source-changes (briefly), I have not seen any changes that I
think would solve it. In my case t
I have seen no feedback on this kernel panic.
I'd like to know if this could be a kernel bug or it may be caused by
some hardware problem.
Thanks.
Original Message
Subject: Kernel Panic with 3.9-stable MP
Date: Tue, 04 Jul 2006 19:37:32 +0200
From: Federico Gia
n 11b without a problem. When changing to 11g I get a
lot of drops (e.g. when I ping ral0 from my portable I receive a lot of
request time-outs. I don't have this when running in 11b).
When changing ral0 back to 11b I got a kernel panic; I used "sh -x
/etc/netstart ral0" to reco
This is the second time this server crash since we switched to the MP
kernel, about a month ago.
I have found the following blue text in the console (it may contain some
errors because I copied it by hand):
uvm_fault( 0xd05cc660, 0xec3de000, 0, 1 ) -> e
Fatal page fault in supervisor mode
tra
shed
> > - We CTRL+C out of software raid rebuild on MASTER, that caused the
> > boot to fail.
> > - We rebooted MASTER while BACKUP was rebuilding it's raid.
> > - When they both came up, they both crashed.
> > - Now we are just running the BACKUP (we didn't hoo
401 - 500 of 562 matches
Mail list logo
