random panics in RELENG_6
-- Forwarded message --
From: "Ernestas V." <[EMAIL PROTECTED]>
Date: Wed, 17 May 2006 22:06:32 +0300
Subject: random panics in RELENG_6
To: freebsd-current@freebsd.org
Hi,
I'm having kernel panics often with RELENG_6 running on an old AMD K6-2 with
128 mb ram. Below is the stack trace from core file. I'm new to FreeBSD -
just trying it on my router for a few months. Can anyone help me to find out
what's happening?
Hardware used on this pc is ural usb wireless card, rl and dc network cards,
snd_cmi integrated soundcard.
It crashes one time in 1-2 days under normal load (web proxy,ipsec+racoon for
wifi, pppoe gateway to internet). But when I was building the kernel, it
crashed VERY often - ~10-15 times in a few hours until compilation was
done :)
---8<--
This GDB was configured as "i386-marcel-freebsd".
Unread portion of the kernel message buffer:
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x708005c
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc04e84a1
stack pointer = 0x28:0xc86c9cc8
frame pointer = 0x28:0xc86c9cd8
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= resume, IOPL = 0
current process = 235 (ppp)
trap number = 12
panic: page fault
Uptime: 7m3s
Dumping 125 MB (2 chunks)
chunk 0: 1MB (159 pages) ... ok
chunk 1: 125MB (31984 pages) 109 93 77 61 45 29 13
#0 doadump () at pcpu.h:165
165 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb) bt
#0 doadump () at pcpu.h:165
#1 0xc04ff687 in boot (howto=260) at ../../../kern/kern_shutdown.c:399
#2 0xc04ffb78 in panic (fmt=0xc06e218f "%s")
at ../../../kern/kern_shutdown.c:555
#3 0xc06ba558 in trap_fatal (frame=0xc86c9c88, eva=117964892)
at ../../../i386/i386/trap.c:831
#4 0xc06baba9 in trap (frame=
{tf_fs = 8, tf_es = 40, tf_ds = 40, tf_edi = -1066125920, tf_esi =
117964816, tf_ebp = -932406056, tf_isp = -932406092, tf_ebx = -1052732288,
tf_edx = -1052732288, tf_ecx = 1, tf_eax = 4, tf_trapno = 12, tf_err = 0,
tf_eip = -1068596063, tf_cs = 32, tf_eflags = 65543, tf_esp = -1054110784,
tf_ss = -1054110784}) at ../../../i386/i386/trap.c:267
#5 0xc06ac9ba in calltrap () at ../../../i386/i386/exception.s:139
#6 0xc04e84a1 in ithread_schedule (ithread=0xc1409480)
at ../../../kern/kern_intr.c:406
#7 0xc04d258d in hardclock (frame=0xc1409480)
at ../../../kern/kern_clock.c:275
#8 0xc06afb91 in intr_execute_handlers (isrc=0xc07435a0, iframe=0xc86c9d34)
at ../../../i386/i386/intr_machdep.c:203
#9 0xc06bd7ad in atpic_handle_intr (iframe=
{if_vec = 0, if_fs = 59, if_es = 59, if_ds = 59, if_edi = 134987776,
if_esi = 1442, if_ebp = -1077943304, if_ebx = 2048, if_edx = 134999732,
if_ecx = 16, if_eax = 134987776, if_eip = 134664084, if_cs = 51, if_eflags =
642, if_esp = -1077943536, if_ss = 59})
at ../../../i386/isa/atpic.c:558
#10 0xc06aca50 in Xatpic_intr0 () at atpic_vector.s:70
#11 0x0806cf94 in ?? ()
Previous frame inner to this frame (corrupt stack?)
---8<--
Thanks,
Ernestas Vaiciukevicius
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: drm/dri rocks
On Friday 19 May 2006 05:07, Ronald Klop wrote: > Hello, > > This commit of the drm/dri stuff yesterday on 6-STABLE rocks. > It works out of the box on my i810. > > I think FreeBSD is now ready for the desktop since xlock looks really cool. > > Ronald. Pardon? the DRM/DRI stuff yesturday? going by the ports/graphics/dri, it hasn't been touched in over three months. Matty ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Can not build scim-chewing-0.3.0
Thanks, I'll ask maintainer to approve(provide) the patch. On Fri, May 19, 2006 at 11:51:35AM +0800, Chen, Lihong wrote: > Hi clsung, > I can not build scim-chewing 0.3.0 unless modify the Makfile line 24 > to : > CONFIGURE_ENV+= CPPFLAGS="-D__STDC_ISO_10646__ -I/usr/local/include" > > > -- > Chen, Lihong <[EMAIL PROTECTED]> -- Cheng-Lung Sung - clsung@ pgpLtIgE3UJDJ.pgp Description: PGP signature
Can not build scim-chewing-0.3.0
Hi clsung, I can not build scim-chewing 0.3.0 unless modify the Makfile line 24 to : CONFIGURE_ENV+= CPPFLAGS="-D__STDC_ISO_10646__ -I/usr/local/include" -- Chen, Lihong <[EMAIL PROTECTED]> signature.asc Description: This is a digitally signed message part
Re: 5.4-STABLE hangs every few days
On Tue, May 02, 2006 at 01:47:15PM +0200, Kurt Jaeger wrote:
> Hi!
>
> > >Been having problems with my Tyan Thunder i7500 (S2720) dual Xeon
> > >running -STABLE: it's hanging every couple of days.
> >
> > Have you had any luck getting to diagnose the issue? I've been
> > plagued by instability with a S2721-533 ("Thunder i7501 Pro"), also
> > on 5-stable, and didn't have much luck. I can freeze the system with
> > heavy disk I/O, but I can't break to debugger at that point.
>
> I had this issue with a Supermicro P8SCT board.
>
> It really sucked, we replaced it approx. 10 days ago with a
> Intel SE7221BK1-E and are waiting for the tests to reproduce the problem.
Hi Kurt,
Have you had any luck with the SE7221BK1 board? Is it stable?
Thanks
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: drm/dri rocks
On Thu, 2006-05-18 at 19:07 +0200, Ronald Klop wrote: > Hello, > > This commit of the drm/dri stuff yesterday on 6-STABLE rocks. > It works out of the box on my i810. > > I think FreeBSD is now ready for the desktop since xlock looks really cool. > > Ronald. The DRM also works for me, it's good! But I cannot have direct rendering support: error: [drm:pid41500:radeon_do_init_cp] *ERROR* Cannot initialise DRM on this card This card requires a new X.org DDX for 3D From the source code I found it caused by 'CHIP_NEW_MEMMAP' flag. It seems that My FreeBSD must wait the next version x.org to use DRI. -- Chen, Lihong <[EMAIL PROTECTED]> signature.asc Description: This is a digitally signed message part
if_ex + 6.1-R = random reboot
Hi, I've recently recieved this strange error: Fatal trap 12: page fault while in kernel mode fault virtual address = 0xc3a53000 fault code = supervisor write, page not present instruction pointer = 0x20:0xc083cf2e stack pointer = 0x28:0xcc96cc8c frame pointer = 0x28:0xcc96ccd0 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 = 20 (irq11: cbb0 cbb1+*) trap number = 12 panic: page fault Uptime: 3d19h28m10s Cannot dump. No dump device defined. Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... Some messages in dmesg from a few minutes before: xe0: alignment error xe0: discard oversize frame (ether type 0 flags 3 len 7890 > max 1514) xe0: alignment error xe0: discard oversize frame (ether type 0 flags 3 len 7890 > max 1514) xe0: discard oversize frame (ether type 322d flags 3 len 65532 > max 1514) xe0: discard oversize frame (ether type 1c2d flags 3 len 65532 > max 1514) I take it could be relevant... If more debug info is required I'd be happy to compile the kernel with debug symbols and provide more feedback... Or maybe someone understands what's going on from whatever is provided now? The if_xe runs at 100Mbit. Cheers, //m. -- Mateusz Jędrasik <[EMAIL PROTECTED]> pgpgxUFR9adzO.pgp Description: PGP signature
UPDATE Radeon r300 unknown hardware 5460 assuming generic msg xorg logout=reboot
according to my previuos email im sending some more information regarding the system reboot while login out from xorg 6.9/GNOME2. --- GLXINFO OUPUT --- Unknown device ID 5460, please report. Assuming plain R300. *WARN_ONCE* File r300_state.c function r300Enable line 456 TODO - double side stencil ! *** No ctx->FragmentProgram._Current!! -- DMESG OUTPUT drm0: Reserved 0x1 bytes for rid 0x18 type 3 at 0xdfdf drm0: Reserved 0x800 bytes for rid 0x10 type 3 at 0xd000 info: [drm] Setting GART location based on new memory map info: [drm] Loading R300 Microcode info: [drm] writeback test succeeded in 1 usecs drm0: [MPSAFE] Warning: pid 761 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 780 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 780 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 780 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 780 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 780 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 780 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 780 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 780 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 780 used static ldt allocation. See the i386_set_ldt man page for more info error: [drm:pid783:drm_close] *ERROR* can't find authenticator error: [drm:pid787:drm_close] *ERROR* can't find authenticator - XORG CONF - Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice"Mouse0" InputDevice"Touchpad0" InputDevice"Keyboard0" EndSection Section "ServerFlags" Option "DontZoom""false" Option "BlankTime" "30" Option "StandbyTime" "40" Option "SuspendTime" "50" EndSection Section "Files" RgbPath "/usr/X11R6/lib/X11/rgb" ModulePath "/usr/X11R6/lib/modules" FontPath "/usr/X11R6/lib/X11/fonts/misc/" FontPath "/usr/X11R6/lib/X11/fonts/TTF/" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" FontPath "/usr/X11R6/lib/X11/fonts/CID/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" EndSection Section "Module" Load "i2c" Load "bitmap" Load "ddc" SubSection"extmod" Option"omit xfree86-dga" EndSubSection Load "glx" Load "dri" Load "dbe" Load "record" Load "xtrap" Load "type1" Load "int10" Load "vbe" Load "radeon" Load "freetype" Load "synaptics" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "CorePointer" Option "Protocol" "auto" Option "Device" "/dev/sysmouse" Option "Buttons" "7" Option "ZAxisMapping" "4 5" Option "YAxisMapping" "6 7" EndSection Section "Monitor" Identifier "Monitor0" VendorName "LPL" ModelName"0" Option "DPMS" EndSection Section "InputDevice" Identifier "Touchpad0" Driver "synaptics" Option "SendCoreEvents""true" Option "Device""/dev/psm0" Option "Protocol" "auto" Option "LeftEdge" "1700" Option "RightEdge" "5300" Option "TopEdge" "1700" Option "BottomEdge""4200" Option "FingerLow" "25" Option "FingerHigh""30" Option "MaxTapTime""180" Option "MaxTapMove""220" Option "VertScrollDelta" "100" Option "HorizScrollDelta" "100" Option "MinSpeed" "0.06" Option "MaxSpeed" "0.06" Option "AccelFactor" "0.0010" Option "ScrollButtonRepeat""100" Option "UpDownScrolling" "on" Option "UpDownRepeat" "on" O
UPDATE Radeon r300 unknown hardware 5460 assuming generic msg xorg logout=reboot
according to my previuos email im sending some more information regarding the system reboot while login out from xorg 6.9/GNOME2. --- GLXINFO OUPUT --- Unknown device ID 5460, please report. Assuming plain R300. *WARN_ONCE* File r300_state.c function r300Enable line 456 TODO - double side stencil ! *** No ctx->FragmentProgram._Current!! -- DMESG OUTPUT drm0: Reserved 0x1 bytes for rid 0x18 type 3 at 0xdfdf drm0: Reserved 0x800 bytes for rid 0x10 type 3 at 0xd000 info: [drm] Setting GART location based on new memory map info: [drm] Loading R300 Microcode info: [drm] writeback test succeeded in 1 usecs drm0: [MPSAFE] Warning: pid 761 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 780 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 780 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 780 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 780 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 780 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 780 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 780 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 780 used static ldt allocation. See the i386_set_ldt man page for more info Warning: pid 780 used static ldt allocation. See the i386_set_ldt man page for more info error: [drm:pid783:drm_close] *ERROR* can't find authenticator error: [drm:pid787:drm_close] *ERROR* can't find authenticator xorg.conf Description: Binary data ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: update to RELENG_6 fails
Alexander I. Mogilny wrote: > Thanks. I cvsuped my source tree to RELENG_5. Build completed without > errors. Thanks for your answers. No worries. :) Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
drm/dri rocks
Hello, This commit of the drm/dri stuff yesterday on 6-STABLE rocks. It works out of the box on my i810. I think FreeBSD is now ready for the desktop since xlock looks really cool. Ronald. -- Ronald Klop Amsterdam, The Netherlands ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: why the swapping
On Thu, 18 May 2006 13:33:07 +0200, Tim Middleton <[EMAIL PROTECTED]> wrote: Running 6.0-release, with 2 gig ram. Typical memory stats like this (from top): 626M Active, 1045M Inact, 204M Wired, 75M Cache, 112M Buf, 22M Free Under moderately high load i'm seeing a lot of swapping periodically through the day (and then load avg going way, way up, of course). I'm wondering why is there, with so much inactive memory, so much disk swapping? The machine runs some fairly intense stuff, such as squid, postgresql, and zope; but it seems to me there should be enough RAM to cover all of this without swapping. What am I missing? Am i misinterpretting the stats, and just not understanding how the vm works? What is the memory use of your applications? Reported by top (SIZE and RES) or by ps. How much (different) data from/to disk is being processed by your applications in what time interval? Ronald. -- Ronald Klop Amsterdam, The Netherlands ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
why the swapping
> "Tim" == Tim Middleton <[EMAIL PROTECTED]> writes: Tim> Running 6.0-release, with 2 gig ram. Typical memory stats like Tim> this (from top): Tim> 626M Active, 1045M Inact, 204M Wired, 75M Cache, 112M Buf, 22M Tim> Free Tim> Under moderately high load i'm seeing a lot of swapping Tim> periodically through the day (and then load avg going way, way Tim> up, of course). I'm wondering why is there, with so much inactive Tim> memory, so much disk swapping? Tim> The machine runs some fairly intense stuff, such as squid, Tim> postgresql, and zope; but it seems to me there should be enough Tim> RAM to cover all of this without swapping. What am I missing? Am Tim> i misinterpretting the stats, and just not understanding how the Tim> vm works? Swapping in or out? Sswapping out is normal behaviour --- a background kernel thread sweeps memory to move it from active to inactive and inactive dirty pages are occaisionally sent to swap (or the file that's backing them). Swapping in is also normal when processes are launched. Remember that *BSD's "swap in" processes. I believe that mmap() calls also show up in the swap stats ... Swapping doesn't mean what it used to. What should worry you is a process that is blocked to a large degree on paging --- but that's not likely happening. Dave. -- |David Gilbert, Independent Contractor. | Two things can be | |Mail: [EMAIL PROTECTED]| equal if and only if they | |http://daveg.ca | are precisely opposite. | =GLO ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: update to RELENG_6 fails
Doug Barton wrote me on Wed, May 17, 2006 at 09:41:45PM -0700 > Mars G. Miro wrote: > > > For the record, I've successfully updated a 5.4X to 6.1R w/o a hitch. > > I don't think you need to go to 5-stable if you want 6.X. Most apps > > will even still work and dont need to be recompiled. > > As happy as I am to hear that, if you'd read the section in UPDATING that I > was referring to, you'd have seen: > > When upgrading from one major version to another it is generally > best to upgrade to the latest code in the currently installed branch > first, then do an upgrade to the new branch. This is the best-tested > upgrade path, and has the highest probability of being successful. > Please try this approach before reporting problems with a major > version upgrade. > > Which clearly applies to the situation at hand. > Please move this conversation to freebsd-stable. > Thanks. I cvsuped my source tree to RELENG_5. Build completed without errors. Thanks for your answers. -- AIM-UANIC +-[ FreeBSD ]-+ Alexander Mogilny | The Power to Serve! | <> [EMAIL PROTECTED]+-+ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: why the swapping
On Thu, 18 May 2006 07:33:07 -0400 Tim Middleton <[EMAIL PROTECTED]> wrote: > > Running 6.0-release, with 2 gig ram. Typical memory stats like this (from > top): > > 626M Active, > 1045M Inact, > 204M Wired, > 75M Cache, > 112M Buf, > 22M Free > > Under moderately high load i'm seeing a lot of swapping periodically through > the day (and then load avg going way, way up, of course). I'm wondering why > is there, with so much inactive memory, so much disk swapping? > > The machine runs some fairly intense stuff, such as squid, postgresql, and > zope; but it seems to me there should be enough RAM to cover all of this > without swapping. What am I missing? Am i misinterpretting the stats, and > just not understanding how the vm works? > > -- > Tim Middleton | Vex.Net| There is a wisdom that is woe; but there > [EMAIL PROTECTED] | VexTech.ca | is a woe that is madness. --Melville (MD) > maybe you have to set vm.swap_idle_enabled=0 or vm.swap_enabled=0 ? -- Best regards. Alexander "polachok" Polakov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Radeon r300, unknown hardware 5460 assuming generic message, xorg logout=reboot
yesterday i updated my source tree with the latest changes including the commit for the radeon drivers on 05/17/2006 for RELENG_6, i was more that happy to see i finally have dri working in my laptop, the Xorg was hanging while starting previous to this update but now was working and showing direct rendering : yes in the glxinfo output, everything was smoth until i did a logout for xorg, at the moment the machine restarted. Here are the things i notice: 1.- the dmesg out is not showing the memory size for my card, ATI RADEON MOBILITY X300, 64MB. 2.- the Xorg.0.log show between 12 and 15 calls to RadeonLoadPallete(), that is the last thing in the file. 3.- this only happends with dri enable, i tried without dri and everything works. i will provide more information once i have my laptop available, working right now. if you need any help testing this hardware please let me know i will be more than happy to help. Regards, Eprha Carvajal ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pxeboot with amd64 vs i386
On Thu, 18 May 2006, Danny Braniss wrote: DB> > DB> > At that point, lsdev shows the disk devices, but not the pxeboot "disk", which DB> > DB> > leaves me without a kernel, etc. So something is different between the i386 DB> > DB> > and amd64 disks, or maybe there's a problem with my BIOS. I was wondering if DB> > DB> > anyone else had set up a similar configuration and had it work? DB> > DB> > DB> > DB> > Robert N M Watson DB> > DB> DB> > DB> I had similar experience, i recompiled a fresh pxeboot, and it's ok now. DB> > DB> > Hmm, would you please point me to the right pxeboot? I tried both i386 and DB> > amd64 versions from 6.1-R ISOs as well as i386 version from April's RC. DB> DB> i compiled the one in the src of the 6.1-stable. DB> /src/sys/boot/i386/pxeldr DB> i took the easy road, cd /src; make buildkernel, and picked up pxeboot Hmm, which architecture? I just rechecked, and got the same error with mfsroot with all pxeboots and both i386 and amd64 distribs (I think boot/loader phase is the same for them though). Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] *** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Mounting SMB filesystems at boot time
> Since you say mount -a works, it sounds likely you have something in your > fstab preventing auto mounting (noauto??), or perhaps some error is being > generated at boot time (check /var/log/messages?). Maybe if you post your > fstab someone will spot something. Actually, after much oainful digging through rc files (which proved to be a total red herring1) I did find the problem. The dirves are mouted before named is started, hence the machine names need to be in /etc/hosts Stupid error on my part, because I know this is the case for NFS! Sorry for the noise... -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Hard crashes with floppy access
Well, I that was my first thought also. The first one was quite an old disk, but it worked on this very same machine, in fact it was formatted (granted, a very long time ago) on this machine under 6.0. The other disk was brand-new, and it works on one of my other PCs, running 5.5-PRE. I know this whole thing is not a big deal, and I personally wouldn't be happier if the floppy disk went the way of the Dodo, but I guess it's a necessary evil. On Thu, 2006-05-18 at 09:33 -0400, Lowell Gilbert wrote: > Christian Lopez de Castilla Wagner <[EMAIL PROTECTED]> writes: > > > This afternoon I experienced two hard crashes while accessing my floppy > > drive. > > Mounting seemed to work OK, then I tried to copy a file (~24K) to the > > disk and then nothing, having to go for the Reset button. The first time > > this happened under X, the second time on a terminal. > > I have no idea when exactly this started to happen; the last time I used > > a floppy must have been around March... > > > > FreeBSD hellion.clcw 6.1-STABLE FreeBSD 6.1-STABLE #0: Fri May 12 > > 12:55:23 BOT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/20051212 > > i386 > > Are you sure you didn't just have bad media? > I try to access floppies in ways that don't involve actually mounting > them, because they do tend to go bad. -- Christian Lopez de Castilla Wagner [EMAIL PROTECTED] [EMAIL PROTECTED] (+591-705)98290 http://lopisaur.googlepages.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Hard crashes with floppy access
Christian Lopez de Castilla Wagner <[EMAIL PROTECTED]> writes: > This afternoon I experienced two hard crashes while accessing my floppy > drive. > Mounting seemed to work OK, then I tried to copy a file (~24K) to the > disk and then nothing, having to go for the Reset button. The first time > this happened under X, the second time on a terminal. > I have no idea when exactly this started to happen; the last time I used > a floppy must have been around March... > > FreeBSD hellion.clcw 6.1-STABLE FreeBSD 6.1-STABLE #0: Fri May 12 > 12:55:23 BOT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/20051212 > i386 Are you sure you didn't just have bad media? I try to access floppies in ways that don't involve actually mounting them, because they do tend to go bad. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Mounting SMB filesystems at boot time
The following in my fstab works for me (with no extra settings in rc.conf or scripts): //media/files /drives/media/files smbfs rw,-I=192.168.7.25,-N,-u=x 0 0 Since you say mount -a works, it sounds likely you have something in your fstab preventing auto mounting (noauto??), or perhaps some error is being generated at boot time (check /var/log/messages?). Maybe if you post your fstab someone will spot something. -- Tim Middleton | Vex.Net| I care not much for a man's religion whose [EMAIL PROTECTED] | VexTech.ca | dog or cat are not the better for it. [A.L.] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Mounting SMB filesystems at boot time
Have just changed a machine from 4.11 to 6.1 by re-installing. It all works fine, but I cannot work out how to make the SMB filesystems in fstab mount at boot time. I used to do this by copying /usr/src/contrib/smbfs/examples/smbfs.sh.sample to one of the rc directories, but this script does not seem to exist under 6.1. Some googling lead me to comments that adding the line extra_netfs_types="smbfs:SMB" to rc.conf would do the trick, but that doesnt work either. When the system is mounted I can just type 'mount -a' and they all mount fine though! I suppsoe I could copy the 4.11 script over, but I am sthere must be a "correct" way to do this under 6.1. ? The man page simply says to add the lines to fstab. -pcf. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pxeboot with amd64 vs i386
> On Thu, 18 May 2006, Danny Braniss wrote: > > DB> > At that point, lsdev shows the disk devices, but not the pxeboot > "disk", which > DB> > leaves me without a kernel, etc. So something is different between the > i386 > DB> > and amd64 disks, or maybe there's a problem with my BIOS. I was > wondering if > DB> > anyone else had set up a similar configuration and had it work? > DB> > > DB> > Robert N M Watson > DB> > DB> I had similar experience, i recompiled a fresh pxeboot, and it's ok now. > > Hmm, would you please point me to the right pxeboot? I tried both i386 and > amd64 versions from 6.1-R ISOs as well as i386 version from April's RC. i compiled the one in the src of the 6.1-stable. /src/sys/boot/i386/pxeldr i took the easy road, cd /src; make buildkernel, and picked up pxeboot danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pxeboot with amd64 vs i386
On Thu, 18 May 2006, Danny Braniss wrote: DB> > At that point, lsdev shows the disk devices, but not the pxeboot "disk", which DB> > leaves me without a kernel, etc. So something is different between the i386 DB> > and amd64 disks, or maybe there's a problem with my BIOS. I was wondering if DB> > anyone else had set up a similar configuration and had it work? DB> > DB> > Robert N M Watson DB> DB> I had similar experience, i recompiled a fresh pxeboot, and it's ok now. Hmm, would you please point me to the right pxeboot? I tried both i386 and amd64 versions from 6.1-R ISOs as well as i386 version from April's RC. Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] *** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
why the swapping
Running 6.0-release, with 2 gig ram. Typical memory stats like this (from top): 626M Active, 1045M Inact, 204M Wired, 75M Cache, 112M Buf, 22M Free Under moderately high load i'm seeing a lot of swapping periodically through the day (and then load avg going way, way up, of course). I'm wondering why is there, with so much inactive memory, so much disk swapping? The machine runs some fairly intense stuff, such as squid, postgresql, and zope; but it seems to me there should be enough RAM to cover all of this without swapping. What am I missing? Am i misinterpretting the stats, and just not understanding how the vm works? -- Tim Middleton | Vex.Net| There is a wisdom that is woe; but there [EMAIL PROTECTED] | VexTech.ca | is a woe that is madness. --Melville (MD) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Messages from rc-scripts are not displayed at all
On Wed, May 17, 2006, Sergei Mozhaisky wrote: > This does not help :( There is no output at all, commands > aren't display too. Maybe 'dmesg -a' will give you a hint what's going on. -cs ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1 and USB: problems with mounting SonyEricsson K750 flash
[...] > > "Dennis Melentyev" <[EMAIL PROTECTED]> writes: > > > > > I've got a problem with mounting SonyEricsson K750 flash card: > > > 6.1 is not stabily mounting/recognizing device, and, after several tries > > > ended up in creating TWO IDENTICAL device nodes in /dev!!! [...] > So, the only FBSD-related issue left is a duplicated entry in /dev listing. > Reboot helped, but that's not the way it should be. Could someone check the > possibilities to have duplicate entries in directory listing (at least under > /dev)? I have experienced a similar problem on 6.1-RELEASE. I was trying to access a compact flash card through two different USB card readers and somehow I ended up with two identical /dev/daXs1 devices (X was 4 IIRC) which I could not mount. A reboot "fixed" the problem and I could mount the card. A copy of the kernel log: http://spider.netlife.no/~erik2/kernellog.txt -- Erik Stian Tefre ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pxeboot with amd64 vs i386
> > I have my first SMP amd64 box at the office now to work with, and thought it > was all going to be easy. Sadly not, or at least, not yet. :-) > > I configured dhcpd, tftpd, and nfs to export the 6.1 install CD from my > notebook. All good so far. The problem is as follows: if I insert the 6.1 > i386 release CD, it all works great. If I insert the amd64 CD, then I get > the > following after pxeboot has been going for a bit: > > ([EMAIL PROTECTED], Sun May 7 02:16:38 UTC 2006) > Can't work out which disk we are booting from.Guessed BIOS device 0x > not found by probes, defaulting to > disk0: > can't load 'kernel' > > At that point, lsdev shows the disk devices, but not the pxeboot "disk", > which > leaves me without a kernel, etc. So something is different between the i386 > and amd64 disks, or maybe there's a problem with my BIOS. I was wondering if > anyone else had set up a similar configuration and had it work? > > Robert N M Watson I had similar experience, i recompiled a fresh pxeboot, and it's ok now. danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1 and USB: problems with mounting SonyEricsson K750 flash
Hi! 2006/5/17, Bengt Ahlgren <[EMAIL PROTECTED]>: Hi! "Dennis Melentyev" <[EMAIL PROTECTED]> writes: > I've got a problem with mounting SonyEricsson K750 flash card: > 6.1 is not stabily mounting/recognizing device, and, after several tries > ended up in creating TWO IDENTICAL device nodes in /dev!!! > > Has anyone any suggestion on how to resolve such a problem? > > Here is kind of my actions log: > After connecting the cable, got this in console: > umass0: Sony Ericsson Sony Ericsson K750, rev 2.00/0.00, addr 2 > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Removable Direct Access SCSI-0 device > da0: 1.000MB/s transfers > da0: 1902MB (3895296 512 byte sectors: 255H 63S/T 242C) > > so far everything is ok, except the reported disk size: it's 1Gb, not 2Gb. I get a different error, but which could possibly be related. I am running 6.1R on a Thinkpad X40. I just thought my connectors have accumulated too much dirt, because after retrying two-three times it succeeds. But perhaps dirt is not the issue, because when it succeeds in reading the size, mounting and reading works perfectly without errors. Here is what I get about 3 times out of 4 when attaching: [ log skipped] And, correctly when it succeeds: umass0: Sony Ericsson Sony Ericsson K750, rev 2.00/0.00, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 61MB (126912 512 byte sectors: 64H 32S/T 61C) I am not sure when the above problems started. When my phone was new (July 2005) it worked without any problems. I was most likely running 5.4 at that time. It runs perfectly on WinXP. So, connectors should not be an issue. It might be a problem with not-fully-standard things by SE, Also, I tried to play with different FAT types (16/32). FAT16 seemd to be much faster, but also not yet ideal. After I upgraded the phone software yesterday and reformated flash using native phone tools, it helped: da0: Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present umass0: at uhub2 port 2 (addr 2) disconnected ### first try was not successful, but w/o any other errors in console (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry umass0: detached ### Reattached the device umass0: Sony Ericsson Sony Ericsson K750, rev 2.00/0.00, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 951MB (1947648 512 byte sectors: 64H 32S/T 951C) ### And yes, it's finally up and correctly sized So, the only FBSD-related issue left is a duplicated entry in /dev listing. Reboot helped, but that's not the way it should be. Could someone check the possibilities to have duplicate entries in directory listing (at least under /dev)? -- Dennis Melentyev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
