HELP! /usr/bin/as core dump after 'make world' from RELENG_6 to RELENG_7

ore" and got gdb.core file ... Is there any way to recover from this terrible stuation? BTW, I wonder why. Because a few days ago, I successfully updated my another FreeBSD/pc98 box from older 6.2-STABLE to 7.4-PRERELEASE and then 8.1-PRERELEASE with the

Re: recovering from the 6.3 xorg mess

there was no pointerr - but this is well documented as a problem > if you google for it. My G550 is fine with xorg 7.3 and FreeBSD/i386 8.0-CURRENT. The installation informations are available at http://home.jp.freebsd.org/~nakaji/g550/ BTW, I think freebsd-x11 is better place. -- NAKAJI Hiro

Re: FreeBSD 7.0-BETA2 Available

TI Radeon X1300 on it. Xorg 7.3 works well with this video card with vesa driver. I put the /var/run/dmesg.boot of ML115 at http://heimat.jp/~nakaji/FreeBSD/ML115/dmesg.boot -- NAKAJI Hiroyuki ___ freebsd-stable@freebsd.org mailing list http://lists.

Re: More data on 7.2-RELEASE "hangs"

e machines, too. Thanks. >>>>> In <20090513040719.d17...@hub.org> >>>>> "Marc G. Fournier" wrote: > Don't know if this helps with anything, but it just hung after 2days > again ... nothing on the console ... top process running at the tim

Big problem still remains with 7.2-STABLE locking up

rs, the box rebooted while I was in bed last night. Watchdogd functions very well. Advice? Thanks. -- NAKAJI Hiroyuki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Big problem still remains with 7.2-STABLE locking up

. > > The kernel configuration is: > ... > > options BREAK_TO_DEBUGGER > When the box locks up, can you actyually break to the debugger ? This is how > we eventually tracked down my problem. No. I have never seen the debugger, Ctrl+Alt+Esc cannot break. And because this box

Re: Big problem still remains with 7.2-STABLE locking up

ocks structure > states once we identify something useful (ideally, keeping the machine > up in DDB for that would be very useful, but often not viable) Thank you for instruction. I'll try. -- NAKAJI Hiroyuki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Big problem still remains with 7.2-STABLE locking up

es once we identify something useful (ideally, keeping the machine > up in DDB for that would be very useful, but often not viable) > Let me know. > Attilio -- NAKAJI Hiroyuki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Big problem still remains with 7.2-STABLE locking up

S:330 #19 0x00080074d17c in ?? () Previous frame inner to this frame (corrupt stack?) > 4) Dump the content so that we can further look at locks structure > states once we identify something useful (ideally, keeping the machine > up in DDB for that would be very useful, but often n

Re: Big problem still remains with 7.2-STABLE locking up

p://www.heimat.gr.jp/~nakaji/localhost/dcons.log ^^^ > I'm following up privately with the user, news to come hopefully. Thanks. I'll try. -- NAKAJI Hiroyuki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/fr

Re: 7.2-release/amd64: panic, spin lock held too long

at he had found the problem and is working on it. You can see Attilio's guide to collect debug informations: http://lists.freebsd.org/pipermail/freebsd-stable/2009-June/050528.html -- NAKAJI Hiroyuki ___ freebsd-stable@freebsd.org mailing list htt

Re: 7.2-release/amd64: panic, spin lock held too long

>>>>> In <3bbf2fe10907221748j7f317ce0yc13bc5d01b49...@mail.gmail.com> >>>>> Attilio Rao wrote: > 2009/7/23 NAKAJI Hiroyuki : > >>>>>> In <4a667469.1080...@gmail.com> > >>>>>> "C. C. Tang" wro

Re: FreeBSD 6.1-BETA2/FreeBSD 5.5-BETA2 Available

ooted with bootonly.iso. But after the message, Waiting 5 seconds for SCSI devices to settle the PC stacks and ScreenLock key is no use. Can I use serial console to record the boot messages? Thanks. -- NAKAJI Hiroyuki ___ freebsd-stable@freebsd.org ma

Re: FreeBSD 6.1-BETA2/FreeBSD 5.5-BETA2 Available

ave to disable ACPI timer for anything >= 6.0-RELEASE. > To disable it, at the boot menu, select 6 to get a prompt, then type > set debug.acpi.disabled="timer" > boot > and see if it still locks up. -- NAKAJI Hiroyuki ___ fre

Re: FreeBSD 6.1-BETA2/FreeBSD 5.5-BETA2 Available

xed. I added a note to the PR 91910 with dmesg.out. > BTW, you can permanently disable the timer by adding the debug line > to /boot/loader.conf. Yes, I added it too. Now it works well. Thanks. -- NAKAJI Hiroyuki ___ freebsd-stable@freebsd.o

Re: ANNOUNCE: [FreeBSD-Announce] FreeBSD 5.4-RELEASE is now available

tallation and download larger iso file. > MD5 (5.4-RELEASE-i386-disc1.iso) = 3dbb37485535e129354bc099e24aed99 With this CD or 3 froppies, the installation goes well. What is different? -- NAKAJI Hiroyuki ___ freebsd-stable@freebsd.org mailing lis

Re: ANNOUNCE: [FreeBSD-Announce] FreeBSD 5.4-RELEASE is now available

; stucks. > Worked for me. Maybe you burnt it on a bad medium? Maybe. Or CD-R drive may have some problem, because disc1 was burnt on another same medium but with another DVD-R drive. Anyway, 5.4-RELEASE is now working. Thanks. -- NAKAJI Hiroyuki __

[RELENG_4] buildkernel failure with MAKEOBJDIRPREFIX

rc/sys/CONFIG/kernel.debug. I think this is a bug of make, *.mk or other Makefiles in /sys but I cannot fix it. (*) When running /usr/sbin/ppp to connect to the provider with PPPoE, the system gets panic with 'fatal trap 12' after several days of uptime. I have seen this panic twi

Re: [RELENG_4] buildkernel failure with MAKEOBJDIRPREFIX

able > and should not be set on make's command line or in /etc/make.conf. I see. Thanks. -- NAKAJI Hiroyuki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"

[RELENG_5] kernel cannot boot after 2005.09.05.12.00.00 on my laptop

are NG But I cannot find what change was imported in this 8 hours. Does someone know? Thanks in advance. P.S. I did not test any kernel (GENERIC without USB). And could not find proper key words to search from an archive... -- NAKAJI Hiroyuki ___ free

Re: buildworld fails

>>>>> In <[EMAIL PROTECTED]> >>>>> [EMAIL PROTECTED] (NAKAJI Hiroyuki) wrote: Sean> Are you building with -DNOCLEANDIR? nakaji> Ah, yes. I deleted -DNOCLEANDIR from my buildworld script and am nakaji> rebuilding world. Thanks to Matsushita-san.