-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Used bsd.rd -current and increased my RAM to 3.1GB. No luck.

Looked into changing MAXDSIZ in
/usr/src/sys/arch/amd64/include/vmparam.h and compiling a bsd.rd from
- -STABLE just so I can run fsck_ffs.

Increasing MAXDSIZ from (1*1024*1024*1024) to (2*1024*1024*1024),
which is well within my RAM limits and larger than the number the
error says it is having trouble allocating (183MB).

This change doesn't compile.

it dies in /usr/src/sys/kern/exec_elf.c:444:

 /* CRAP - map_findspace does not avoid daddr+MAXDSIZ */

if ((addr + size > (vaddr_t)p->p_vmspace->vm_daddr) &&

(addr < (vaddr_t)p->p_vmspace->vm_daddr + MAXDSIZ))

addr = round_page((vaddr_t)p->p_vmspace->vm_daddr +

MAXDSIZ);

And this is where my expertise ends. Any suggestions?

Jason
Comment: http://getfiregpg.org

iD8DBQFI2sTt2ZVbbZM1O8gRAolkAJ4mY1D3m7jSE2TukDjGA6m2unN8swCgk6DM
hfZOHPlbHfj4rzNUeIom40s=
=+P/Q
-----END PGP SIGNATURE-----
On Wed, Sep 24, 2008 at 3:27 PM, Jason Sidabras <[EMAIL PROTECTED]>wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Yeah, I tried amd64 bsd.rd from current and I have 3.1GB of ram.
>
> Working on trying to free the 0.9 GB from my bios but going from 2GB
> to 3GB with the bsd.rd kernel did not help.
>
> - -Jason
>
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (MingW32)
> Comment: http://getfiregpg.org
>
> iD8DBQFI2qKH2ZVbbZM1O8gRAlIWAKCLC+wF0upGpZYgKtgyk/gA0eeRaQCeKxmU
> T8CwmJ/en+ecsMtHsmaKSPk=
> =gYvy
> -----END PGP SIGNATURE-----
> On Wed, Sep 24, 2008 at 2:30 PM, Chris Kuethe <[EMAIL PROTECTED]>wrote:
>
>> I also told him to get a -current amd64 with >3.5GB. i've got a few
>> things running on my amd64 at home w/ 4.1GB working set.
>>
>> On Wed, Sep 24, 2008 at 10:38 AM, Otto Moerbeek <[EMAIL PROTECTED]> wrote:
>> > On Wed, Sep 24, 2008 at 12:25:53PM -0500, Jason Sidabras wrote:
>> >
>> >> Thanks Ted and Chris,
>> >>
>> >> I have to go pick up some more RAM, i don't have a system I can take
>> down to
>> >> shift this over.
>> >
>> > That won't help. You are running into MAXDSIZE, which is not increased
>> > by adding RAM.
>> >
>> >        -Otto
>> >
>> >>
>> >> Jason
>> >>
>> >> On Wed, Sep 24, 2008 at 12:17 PM, Jason Sidabras
>> >> <[EMAIL PROTECTED]>wrote:
>> >>
>> >> > -----BEGIN PGP SIGNED MESSAGE-----
>> >> > Hash: SHA1
>> >> >
>> >> > Thanks Chris,
>> >> >
>> >> > I am a little worried about running `fsck -p` in case of loss of data
>> >> > but I did it and edited my fstab.
>> >> >
>> >> > once booted I still have no luck running fsck_ffs:
>> >> >
>> >> > error is now:
>> >> >
>> >> > cannot alloc NNN bytes for statemap
>> >> > dmesg follows:
>> >> >
>> >> > OpenBSD 4.3 (GENERIC.MP) #1582: Wed Mar 12 11:16:45 MDT 2008
>> >> >
>> >> > [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
>> >> > real mem = 2138632192 (2039MB)
>> >> > avail mem = 2065088512 (1969MB)
>> >> > mainbus0 at root
>> >> > bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf0100 (31 entries)
>> >> > bios0: vendor Award Software International, Inc. version "F5" date
>> >> > 03/25/2008
>> >> > bios0: Gigabyte Technology Co., Ltd. 945GCM-S2C
>> >> > acpi0 at bios0: rev 0
>> >> > acpi0: tables DSDT FACP HPET MCFG APIC SSDT SSDT
>> >> > acpi0: wakeup devices PEX0(S5) PEX1(S5) PEX2(S5) PEX3(S5) PEX4(S5)
>> >> > PEX5(S5) HUB0(S5) UAR1(S1) USB0(S1) USB1(S1) USB2(S1) USB3(S1)
>> >> > USBE(S1) AZAL(S5) PCI0(S5)
>> >> > acpitimer0 at acpi0: 3579545 Hz, 24 bits
>> >> > acpihpet0 at acpi0: 14318179 Hz
>> >> > acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
>> >> > cpu0 at mainbus0: apid 0 (boot processor)
>> >> > cpu0: Intel(R) Core(TM)2 Duo CPU E7200 @ 2.53GHz, 2533.64 MHz
>> >> > cpu0:
>> >> >
>> >> >
>> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,EST,TM2,CX16,xTPR,NXE,LONG
>> >> > cpu0: 3MB 64b/line 8-way L2 cache
>> >> > cpu0: apic clock running at 266MHz
>> >> > cpu1 at mainbus0: apid 1 (application processor)
>> >> > cpu1: Intel(R) Core(TM)2 Duo CPU E7200 @ 2.53GHz, 2533.33 MHz
>> >> > cpu1:
>> >> >
>> >> >
>> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,EST,TM2,CX16,xTPR,NXE,LONG
>> >> > cpu1: 3MB 64b/line 8-way L2 cache
>> >> > ioapic0 at mainbus0 apid 2 pa 0xfec00000, version 20, 24 pins
>> >> > ioapic0: misconfigured as apic 0, remapped to apid 2
>> >> > acpiprt0 at acpi0: bus 0 (PCI0)
>> >> > acpiprt1 at acpi0: bus 4 (PEX0)
>> >> > acpiprt2 at acpi0: bus 5 (PEX1)
>> >> > acpiprt3 at acpi0: bus -1 (PEX2)
>> >> > acpiprt4 at acpi0: bus -1 (PEX3)
>> >> > acpiprt5 at acpi0: bus -1 (PEX4)
>> >> > acpiprt6 at acpi0: bus -1 (PEX5)
>> >> > acpiprt7 at acpi0: bus 6 (HUB0)
>> >> > acpicpu0 at acpi0: FVS, 2400, 1600 MHz
>> >> > acpicpu1 at acpi0
>> >> > acpibtn0 at acpi0: PWRB
>> >> > pci0 at mainbus0 bus 0: configuration mode 1
>> >> > pchb0 at pci0 dev 0 function 0 "Intel 82945G Host" rev 0x02
>> >> > agp0 at pchb0: aperture at 0xc0000000, size 0x10000000
>> >> > ppb0 at pci0 dev 1 function 0 "Intel 82945G PCIE" rev 0x02: apic 2
>> int
>> >> > 16 (irq 5)
>> >> > pci1 at ppb0 bus 1
>> >> > ppb1 at pci1 dev 0 function 0 "Intel IOP333 PCIE-PCIX" rev 0x00
>> >> > pci2 at ppb1 bus 2
>> >> > arc0 at pci2 dev 14 function 0 "Areca ARC-1220" rev 0x00: apic 2 int
>> 18
>> >> > (irq 10)
>> >> > arc0: 8 ports, 256MB SDRAM, firmware V1.43 2007-4-17
>> >> > scsibus0 at arc0: 16 targets
>> >> > sd0 at scsibus0 targ 0 lun 0: <Areca, ARC-1220-VOL#00, R001> SCSI3
>> >> > 0/direct fixed
>> >> > sd0: 2861022MB, 44966 cyl, 511 head, 255 sec, 512 bytes/sec,
>> >> > 5859374592 sec total
>> >> > ppb2 at pci1 dev 0 function 2 "Intel IOP333 PCIE-PCIX" rev 0x00
>> >> > pci3 at ppb2 bus 3
>> >> > vga1 at pci0 dev 2 function 0 "Intel 82945G Video" rev 0x02
>> >> > wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
>> >> > wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
>> >> > azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x01:
>> >> > apic 2 int 16 (irq 5)
>> >> > azalia0: codec[s]: Realtek/0x0662
>> >> > audio0 at azalia0
>> >> > ppb3 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x01: apic 2
>> >> > int 16 (irq 5)
>> >> > pci4 at ppb3 bus 4
>> >> > ppb4 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x01: apic 2
>> >> > int 17 (irq 12)
>> >> > pci5 at ppb4 bus 5
>> >> > re0 at pci5 dev 0 function 0 "Realtek 8101E" rev 0x01: RTL8101E
>> >> > (0x3400), apic 2 int 17 (irq 12), address 00:1f:d0:63:70:5f
>> >> > rlphy0 at re0 phy 7: RTL8201L 10/100 PHY, rev. 1
>> >> > uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x01: apic 2
>> >> > int 23 (irq 3)
>> >> > uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x01: apic 2
>> >> > int 19 (irq 11)
>> >> > uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x01: apic 2
>> >> > int 18 (irq 10)
>> >> > uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x01: apic 2
>> >> > int 16 (irq 5)
>> >> > ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x01: apic 2
>> >> > int 23 (irq 3)
>> >> > usb0 at ehci0: USB revision 2.0
>> >> > uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
>> >> > ppb5 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0xe1
>> >> > pci6 at ppb5 bus 6
>> >> > pcib0 at pci0 dev 31 function 0 "Intel 82801GB LPC" rev 0x01
>> >> > pciide0 at pci0 dev 31 function 2 "Intel 82801GB SATA" rev 0x01: DMA,
>> >> > channel 0 wired to compatibility, channel 1 wired to compatibility
>> >> > wd0 at pciide0 channel 0 drive 0: <ST3250310NS>
>> >> > wd0: 16-sector PIO, LBA48, 238474MB, 488395055 sectors
>> >> > wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
>> >> > ichiic0 at pci0 dev 31 function 3 "Intel 82801GB SMBus" rev 0x01:
>> apic
>> >> > 2 int 19 (irq 11)
>> >> > iic0 at ichiic0
>> >> > spdmem0 at iic0 addr 0x50: 1GB DDR2 SDRAM ECC PC2-5300CL5
>> >> > spdmem1 at iic0 addr 0x52: 1GB DDR2 SDRAM ECC PC2-5300CL5
>> >> > usb1 at uhci0: USB revision 1.0
>> >> > uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
>> >> > usb2 at uhci1: USB revision 1.0
>> >> > uhub2 at usb2 "Intel UHCI root hub" rev 1.00/1.00 addr 1
>> >> > usb3 at uhci2: USB revision 1.0
>> >> > uhub3 at usb3 "Intel UHCI root hub" rev 1.00/1.00 addr 1
>> >> > usb4 at uhci3: USB revision 1.0
>> >> > uhub4 at usb4 "Intel UHCI root hub" rev 1.00/1.00 addr 1
>> >> > isa0 at pcib0
>> >> > isadma0 at isa0
>> >> > com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
>> >> > pckbc0 at isa0 port 0x60/5
>> >> > pckbd0 at pckbc0 (kbd slot)
>> >> > pckbc0: using irq 1 for kbd slot
>> >> > wskbd0 at pckbd0: console keyboard, using wsdisplay0
>> >> > pcppi0 at isa0 port 0x61
>> >> > midi0 at pcppi0: <PC speaker>
>> >> > spkr0 at pcppi0
>> >> > lpt0 at isa0 port 0x378/4 irq 7
>> >> > it0 at isa0 port 0x290/8: IT8718F rev 0x05
>> >> > fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
>> >> > softraid0 at root
>> >> > root on wd0a swap on wd0b dump on wd0b
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > -----BEGIN PGP SIGNATURE-----
>> >> > Version: GnuPG v1.4.7 (MingW32)
>> >> > Comment: http://getfiregpg.org
>> >> >
>> >> > iD8DBQFI2nYk2ZVbbZM1O8gRAqpvAJ9HgUSJq+uWZEqe51IHLMaoLqFHKwCeM40v
>> >> > RdTNJ/Jpll/yvUlOjsyA0Aw=
>> >> > =5OQ1
>> >> > -----END PGP SIGNATURE-----
>> >> > On Wed, Sep 24, 2008 at 11:59 AM, Chris Kuethe <
>> [EMAIL PROTECTED]>wrote:
>> >> >
>> >> >> well you can do this
>> >> >>    fsck -p
>> >> >>    mount -a
>> >> >>    TERM=vt220 vi /etc/fstab
>> >> >>        (comment out the raid)
>> >> >>    exit
>> >> >>
>> >> >> to at least get your system booted multiuser again.
>> >> >>
>> >> >> maybe boot a -current bsd.rd and fsck inside that? some improvements
>> >> >> have been made to reduce fsck's memory usage....
>> >> >>
>> >> >> On Wed, Sep 24, 2008 at 9:34 AM, Jason Sidabras
>> >> >> <[EMAIL PROTECTED]> wrote:
>> >> >> > -----BEGIN PGP SIGNED MESSAGE-----
>> >> >> > Hash: SHA1
>> >> >> >
>> >> >> > Hello,
>> >> >> >
>> >> >> > I just had a massive power failure and my raid drive is failing
>> with a:
>> >> >> >
>> >> >> > cannot alloc NNN bytes for blockmap
>> >> >> > cannot alloc NNN bytes for lncntp
>> >> >> >
>> >> >> > searching the archives and man pages for both OpenBSD and FreeBSD
>> >> >> reveals:
>> >> >> >
>> >> >> > fsck_ffs(3) freebsd
>> >> >> > "Fsck_ffs's request for memory for its virtual memory tables
>> >> >> > failed. This should never happen. Fsck_ffs terminates on
>> >> >> > this error condition. See a guru."
>> >> >> >
>> >> >> > So here I am. The raid drive is on a hardware raid areca 1220, in
>> the
>> >> >> > raid bios and volume check shows no errors so I am led to believe
>> the
>> >> >> > raid is still in tact.
>> >> >> >
>> >> >> > Booting OpenBSD 4.3 drops to single user and says to manually run
>> >> >> > fsck_ffs. Doing so produces no different results, just the above
>> error
>> >> >> > messages.
>> >> >> >
>> >> >> > /etc/fstab (line of interest):
>> >> >> > /dev/sd0a /pub_raid ffs rw,noexec,softdep 0 2
>> >> >> >
>> >> >> > I can't seem to edit my fstab in single user mode because
>> everything
>> >> >> > is ro. System has 2GB of real memory and is running bsd.mpGENERIC. I
>> >> >> > can get a dmesg but it will take me some time to get a serial
>> >> >> > connected to this machine.
>> >> >> >
>> >> >> > Any answers besides reformat would be splended. I am booting into
>> >> >> > single CPU bsd now to see if that makes a difference.
>> >> >> >
>> >> >> > Thanks in advance.
>> >> >> >
>> >> >> > Jason
>> >> >> > Comment: http://getfiregpg.org
>> >> >> >
>> >> >> > iD8DBQFI2mv92ZVbbZM1O8gRAtNLAJ0Ssfns0r9fvbW8brXX2qF5hoVRYwCfTmNg
>> >> >> > pksgAgF30Rx3MnNPK5XDwOQ=
>> >> >> > =Hl35
>> >> >> > -----END PGP SIGNATURE-----
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> GDB has a 'break' feature; why doesn't it have 'fix' too?
>> >
>> >
>>
>>
>>
>> --
>> GDB has a 'break' feature; why doesn't it have 'fix' too?

Reply via email to