ed)
sn0: not probed (disabled)
vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0
fb0: vga0, vga, type:VGA (5), flags:0x7007f
fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa 0x2
fb0: init mode:24, bios mode:3, current mode:24
fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k
VGA parameters
rts with 2 removable, self powered
pcib7: at device 30.0 on pci0
pci7: on pcib7
pci_cfgintr: 7:1 INTA BIOS irq 11
pci7: at device 1.0 (no driver attached)
isab0: at device 31.0 on pci0
isa0: on isab0
atapci0: port
0x2060-0x206f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device 31
Does anyone have any thoughts regarding this? I would like to get 5.1 on
this server.
Thank you,
Stephane Raimbault.
- Original Message -
From: ""Stephane Raimbault"" <[EMAIL PROTECTED]>
Newsgroups: mailing.freebsd.current
Sent: Wednesday, October 29, 2003
"Kris Kennaway" <[EMAIL PROTECTED]>
To: "Stephane Raimbault" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, October 29, 2003 4:11 PM
Subject: Re: 5.1-R and 5.1-C floppies will not boot on SuperMicro 6023P-8R
Hi,
I'm trying to install 5.1-R or 5.1-C from floppies redirected output to serial port
and it won't boot to the install screen. 4.9-R floppies with output redirected to
serial port works and installs properly. This is what I get on my serial console when
I try to boot on 5.1-C (similar to 5.
something alert me if I'm running out of this
memory... I'm sure we would of caught this months ago if I was monitoring for this?
Thanks again for everything you have done to assist me thru this problem.
Stephane Raimbault.
[EMAIL PROTECTED] (Bosko Milekic) wrote in message news:<
Hi Brooks,
I'm curious, what should that option be set to if one does have an SMP
kernel running on 2x 2.4Ghz Xeon Processors (Hyper thread enabled)
Mine is currently set to
machdep.hlt_logical_cpus: 1
Thanks,
Stephane.
- Original Message -
From: "Brooks Davis" <[EMAIL PROTECTED]>
News
; output before the crash.
>
> Is this a re-occuring crash for you? I thought we fixed this already.
> Are you sure you have the absolute latest -current? (or are you supping
> RELENG_5_1, which still has this problem?)
>
> -Bosko
>
> On Mon, Aug 11, 2003 at 03:45:14PM -060
rash.
>
> Is this a re-occuring crash for you? I thought we fixed this already.
> Are you sure you have the absolute latest -current? (or are you supping
> RELENG_5_1, which still has this problem?)
>
> -Bosko
>
> On Mon, Aug 11, 2003 at 03:45:14PM -0600, Stephane Rai
tion: inline
> Content-Transfer-Encoding: quoted-printable
>
> On Tue, Aug 12, 2003 at 05:05:49PM -0600, Stephane Raimbault wrote:
> > Hi Brooks,
> >=20
> > I'm curious, what should that option be set to if one does have an SMP
> > kernel running o
bfbffab8 ---
Let me know if there is other data you need from me.
Thanks again,
Stephane.
- Original Message -
From: "Stephane Raimbault" <[EMAIL PROTECTED]>
To: "Bosko Milekic" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, July 3
kernel panic
>
> On Wed, Jul 30, 2003 at 09:25:34AM -0600, Stephane Raimbault wrote:
> > Hi Bosko,
> >
> > My kernel panic'd again this morning. I had removed all the USB devices
> > from my kernel and had set my /etc/rc.conf to usbd_enable="NO" and
provide any further information to help analyze this
problem.
Thanks,
Stephane Raimbault.
- Original Message -
From: "Bosko Milekic" <[EMAIL PROTECTED]>
Newsgroups: mailing.freebsd.current
Sent: Sunday, July 27, 2003 8:56
Subject: Re: FreeBSD 5.1-R kernel panic
>
>
Hi Bosko,
Thanks for your response. I do not use USB on the system... I'll try
removing those devices from the kernel and see if the problem continues.
I will let you know.
Thanks,
Stephane Raimbault.
- Original Message -
From: "Bosko Milekic" <[EMAIL PROT
thing else I need to provide... can I
re-compile the kernel without the "options DDB" now, or should I provide the
same info next time in panic's to confirm it's the same problem?
Thanks,
Stephane.
I've attached the file debug.txt which contains the panic info. Let me kno
9
Subject: Re: FreeBSD 5.1-R kernel panic
> Stephane Raimbault wrote:
> > Hi Thanks for your response,
> >
> > I do not have PAE enabled... I've been hesitant of turning it on, I'm
not
> > sure if it's too stable, I noticed that the asr driver is in t
t+0xce
mi_startup() at mi_startup+0xb5
begin() at begin+0x2c
db>
---
Thanks,
Stephane.
- Original Message -
From: "Bosko Milekic" <[EMAIL PROTECTED]>
Newsgroups: mailing.freebsd.current
Sent: Wednesday, July 23, 2003 10:14
Subject: Re: FreeBSD 5.1-R kernel panic
>
nel panic
>
> On Wed, Jul 23, 2003 at 09:24:24AM -0600, Stephane Raimbault wrote:
> > Thanks Bosko,
> >
> > I've changed my /boot/loader.conf to reflect the kern.vm.kmem.size
option.
> >
> > kern.vm.kmem.size="35"
> >
> > As far as chan
ot;Bosko Milekic" <[EMAIL PROTECTED]>
Newsgroups: mailing.freebsd.current
Sent: Wednesday, July 23, 2003 9:14
Subject: Re: FreeBSD 5.1-R kernel panic
>
> On Wed, Jul 23, 2003 at 09:08:18AM -0600, Stephane Raimbault wrote:
> ...
> > I was looking at uping the kern.vm.kme
developers handbook, I seem to remember seeing something about it in there.
Thanks,
Stephane.
- Original Message -
From: ""Stephane Raimbault"" <[EMAIL PROTECTED]>
Newsgroups: mailing.freebsd.current
Sent: Tuesday, July 22, 2003 0:33
Subject: Re: FreeBSD 5.1-R
es to
return stability to our system. If the new kernel with the updated
kern_malloc.c doesn't help, I'll look at increasing the values you
suggested.
Thanks for the info, and I'll keep you posted with what I find.
Thanks again,
Stephane Raimbault
- Original Message
to assist in identifiying and resolving this problem?
Thanks,
Stephane Raimbault.
%cat /var/run/dmesg.boot
76.232.138 in via em0
panic: kmem_malloc(4096): kmem_map too small: 275251200 total allocated
cpuid = 0; lapic.id =
boot() called on cpu#0
syncing disks, buffers remaining... 7154 7154
22 matches
Mail list logo
