Re: Page fault, GEOM problem??
On 23 jan 2006, at 01.17, Michael S. Eubanks wrote: On Sun, 2006-01-22 at 23:51 +0100, Johan Ström wrote: ...snip... On 22 jan 2006, at 22.58, Michael S. Eubanks wrote: This card does afaik dont have raid functionalitys (I've never read anything about it either on the web, the cards box or anywhere else..). I'm running GENERIC, which does include ataraid.. What does your dmesg identify your card as? atapci0: port 0xb800-0xb87f, 0xb400-0xb4ff mem 0xfb80-0xfb800fff,0xfb00-0xfb01 irq 19 at device 12.0 on pci0 Is it the same PDC chipset? -- Johan No, I have a different controller. My mistake. I think what is happening is the DMA read command is failing, therefore causing the device to be disconnected, and the kernel can't write to the disk from that point on (this is somewhat obvious given the output below). Nov 29 20:36:54 elfi kernel: subdisk10: detached Nov 29 20:36:54 elfi kernel: ad10: detached Nov 29 20:36:54 elfi kernel: unknown: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=426562704 Nov 29 20:36:54 elfi kernel: GEOM_MIRROR: Device gm0s1: provider ad10s1 disconnected. The message seen from the last line above is generated in any of the following scenarios (from g_mirror.c): 1. Device wasn't running yet, but disk disappear. 2. Disk was active and disapppear. 3. Disk disappear during synchronization process. Nov 29 20:36:54 elfi kernel: GEOM_MIRROR: Request failed (error=6). ad10s1[WRITE(offset=134356992, length=16384)] As far as recovering the disk, I remember seeing something about booting to single user mode and using fsck after a core dump in a previous post. I'm assuming the disks worked initially and that you were able to label them etc? Is there any possibility that the disk state may be altered by a power saving feature or setting in the BIOS and FreeBSD just doesn't know when it happens until the next time it tries to access the disk? For recovering, i've always done a direct reboot, the gmirror rebuilds the mirror and fsck is run. No problems reading labels etc, and never has been, only problem has been these sporadic crashes.. And the read/write performance (see earlier in thread)... This is a server, so all bios setting for powersaving is (should be) shut of. Bios should thus never make the disk go to sleep. -Michael Thanks for trying to help! -- Johan
Re: dhclient wedged
On Sun, Jan 22, 2006 at 02:18:28PM -0800, Brooks Davis wrote: > > This definitly sounds like something particular to your dhcp servers. > It would be nice if we could fix it, but without some debugging help > that's going to be pretty much impossible. If you can recompile > dhclient with debugging symbols and when it goes into a spin, use the > debugger to figure out where it's spinning, that would be useful. > See this post for details: > > http://lists.freebsd.org/pipermail/freebsd-current/2005-August/054224.html > I'm recompiling at the moment. Will follow up with debugging results when it fails. -- Kelly D. Grills [EMAIL PROTECTED] pgpT2QVOSEkvS.pgp Description: PGP signature
Re: Page fault, GEOM problem??
I just checked the specs for the sata II controller on the promise site. It doesn't look like that particular controller is a RAID controller so you can discard my last post. I imagine you have the correct devices. -Michael ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: system laggy under load, SCHED_BSD
On Sun, Jan 22, 2006 at 03:26:01PM -0800, Kevin Oberman wrote: > It has been, but I never received any response to my last message. > > I eliminated shared IRQs and have only the mouse and keyboard under giant. No > improvement. > > I enabled mutes profiling and posted the results. I'll admit not have much > expertise, but nothing obvious. FWIW, GIANT was not an issue according to the > profile data. It came while I was on holidays and I lost track of it, but the excel spreadsheet you posted was a bit useless to me :) Please send me the data in a readable format and I'll take a look, thanks. Kris pgpp8EyI0q9wL.pgp Description: PGP signature
Re: system laggy under load, SCHED_BSD
> > --pWyiEgJYm5f9v55/ > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On Sun, Jan 22, 2006 at 11:00:28PM +0100, Tobias Roth wrote: > > Hi > >=20 > > Since some time, I experience extremely bad system behaviour under > > load. For instance when compiling something, or unpacking a large > > archive, the system is almost unusable, even the mouse pointer > > reacts sloppy. > >=20 > > My system: > >=20 > > 6.0-STABLE FreeBSD 6.0-STABLE #7: Sun Jan 22 15:53:39 CET 2006 i386 > >=20 > > I use SCHED_BSD. > >=20 > > How can I diagnose the problem, or provide more information? What > > factors might influence what I experience? I cannot give a more precise > > point in time as when this started, since I switched versions and > > systems a few times recently. > > This has been discussed a number of times: the short answer is to look > for interrupt storms (vmstat -i), interrupt sharing (also vmstat -i), > and in particular shared interrupts involving usb or other drivers > still under Giant. It has been, but I never received any response to my last message. I eliminated shared IRQs and have only the mouse and keyboard under giant. No improvement. I enabled mutes profiling and posted the results. I'll admit not have much expertise, but nothing obvious. FWIW, GIANT was not an issue according to the profile data. I'm afraid that my chance to work on this is probably at an end as I received a replacement for my trusty old Dell (a dual core AMD 64 4400+), and I doubt that the Dell will be around for more than a week or so. If there is something I can try to look at before then, I'd be happy to, but I am at a total loss as to what the problem might be. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Page fault, GEOM problem??
On 22 jan 2006, at 22.58, Michael S. Eubanks wrote: ...snip... Can there be problems with the mobo/controllercard? Or is it more likely to be driver realted? Promise lists my motherboard (asus a7v333) in their manual for the controllercard (promise sataII 150 TX4). ...snip... After looking at the dmesg output, I am curious whether you are using the promise sataII 150 TX4 controller for the raid disks? I see you are using 6.0-RELEASE whereas I'm using 5.4-STABLE with that particular controller. My dmesg output for the disk array looks like the following: Hi! Thanks for response! Yes, this is a Promise SATAII 150 TX4 controller.. But afaik it doesnt do raid?? ad4: 238475MB [484521/16/63] at ata2-master SATA150 ad6: 238475MB [484521/16/63] at ata3-master SATA150 ad8: 238475MB [484521/16/63] at ata4-master SATA150 ad10: 238475MB [484521/16/63] at ata5- master SATA150 ar0: 953900MB [65535/255/63] status: READY subdisks: disk0 READY on ad4 at ata2-master disk1 READY on ad6 at ata3-master disk2 READY on ad8 at ata4-master disk3 READY on ad10 at ata5-master The device I mount as my raid filesystem is ar0s1 and I believe it corresponds to ``device ataraid'' in the kernel. I read the raid mirroring page in the handbook, although, I'm thinking your controller should represent each disk as ``ar0'' and handle the mirroring itself (possibly consisting of two sets of two disks). I really don't know though. No /dev/ar*.. It looks like the RAID1 mirroring tutorial is for systems that don't actually have a raid controller. Hence, the RAID0 tutorial is the one that I would be using if I did not use the promise controller. Because I _DO_ use the controller, I am simply able to manipulate the ar0 disk array as a single disk. I imagine your setup will differ, but I hope this helps. This card does afaik dont have raid functionalitys (I've never read anything about it either on the web, the cards box or anywhere else..). I'm running GENERIC, which does include ataraid.. What does your dmesg identify your card as? atapci0: port 0xb800-0xb87f, 0xb400-0xb4ff mem 0xfb80-0xfb800fff,0xfb00-0xfb01 irq 19 at device 12.0 on pci0 Is it the same PDC chipset? -- Johan -Michael ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable- [EMAIL PROTECTED]"
Re: system laggy under load, SCHED_BSD
On Sun, Jan 22, 2006 at 11:00:28PM +0100, Tobias Roth wrote: > Hi > > Since some time, I experience extremely bad system behaviour under > load. For instance when compiling something, or unpacking a large > archive, the system is almost unusable, even the mouse pointer > reacts sloppy. > > My system: > > 6.0-STABLE FreeBSD 6.0-STABLE #7: Sun Jan 22 15:53:39 CET 2006 i386 > > I use SCHED_BSD. > > How can I diagnose the problem, or provide more information? What > factors might influence what I experience? I cannot give a more precise > point in time as when this started, since I switched versions and > systems a few times recently. This has been discussed a number of times: the short answer is to look for interrupt storms (vmstat -i), interrupt sharing (also vmstat -i), and in particular shared interrupts involving usb or other drivers still under Giant. Kris pgpSYc9ten4qi.pgp Description: PGP signature
Re: dhclient wedged
On Sun, Jan 22, 2006 at 09:51:43AM -0600, Kelly D. Grills wrote: > On Sun, Jan 22, 2006 at 02:52:44AM -0500, Forrest Aldrich wrote: > > > > I reported this problem a few OS versions back... pre-6. I'm on > > FreeBSD-6-STABLE, and I've found the dhclient once again "wedged" in a > > mode that was eating a lot of CPU. > > > > The solution is to kill it, and restart. > > > > I'm on Comcast's network, so I don't really know if their DHCP server is > > doing something that FreeBSD's stock dhclient doesn't like; however, I > > wonder if someone else has noticed this problem, etc. > > > Yes, I've also had the same problem (6.0-RELEASE), on Comcast also. > I installed isc-dhcp3-client-3.0.3_1 from ports and haven't had a > problem since. (crossing fingers ;=) This definitly sounds like something particular to your dhcp servers. It would be nice if we could fix it, but without some debugging help that's going to be pretty much impossible. If you can recompile dhclient with debugging symbols and when it goes into a spin, use the debugger to figure out where it's spinning, that would be useful. See this post for details: http://lists.freebsd.org/pipermail/freebsd-current/2005-August/054224.html -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 pgp5Iv4wgDxY6.pgp Description: PGP signature
system laggy under load, SCHED_BSD
Hi Since some time, I experience extremely bad system behaviour under load. For instance when compiling something, or unpacking a large archive, the system is almost unusable, even the mouse pointer reacts sloppy. My system: 6.0-STABLE FreeBSD 6.0-STABLE #7: Sun Jan 22 15:53:39 CET 2006 i386 I use SCHED_BSD. How can I diagnose the problem, or provide more information? What factors might influence what I experience? I cannot give a more precise point in time as when this started, since I switched versions and systems a few times recently. Thanks, t. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic: mb_dtor_mbuf: M_EXT set
On Sun, 22 Jan 2006 15:16:24 +0100 Christian Brueffer <[EMAIL PROTECTED]> wrote: > On Sun, Jan 22, 2006 at 04:17:12PM +0300, Gleb Smirnoff wrote: > > On Sat, Jan 21, 2006 at 03:09:02PM +0300, Gleb Smirnoff wrote: > > T> This should be fixed in src/sys/kern_mbuf.c, rev. 1.9.2.3 > > > > And another bogus panic is removed in 1.9.2.4 > > > > The kernel is working again, thanks! It's working in regard of vr0, thank you. However now my computer resets w/o anything logged when starting kde; if I only startx it doesn't happen (without exec startkde in .xinitrc); I commented out any fancy options like dri with no effect and it also happen if I kldunload snd_via8233 before starting kde. This is with 1.9.2.3 (cvsupped around 21 to 22 midnight; it didn't happen with sources from 19. -- IOnut - Unregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" BOFH excuse #153: Big to little endian conversion error ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Page fault, GEOM problem??
...snip... > > Can there be problems with the mobo/controllercard? Or is it more > > likely to be driver realted? Promise lists my motherboard (asus > > a7v333) in their manual for the controllercard (promise sataII 150 > > TX4). > > ...snip... After looking at the dmesg output, I am curious whether you are using the promise sataII 150 TX4 controller for the raid disks? I see you are using 6.0-RELEASE whereas I'm using 5.4-STABLE with that particular controller. My dmesg output for the disk array looks like the following: ad4: 238475MB [484521/16/63] at ata2-master SATA150 ad6: 238475MB [484521/16/63] at ata3-master SATA150 ad8: 238475MB [484521/16/63] at ata4-master SATA150 ad10: 238475MB [484521/16/63] at ata5-master SATA150 ar0: 953900MB [65535/255/63] status: READY subdisks: disk0 READY on ad4 at ata2-master disk1 READY on ad6 at ata3-master disk2 READY on ad8 at ata4-master disk3 READY on ad10 at ata5-master The device I mount as my raid filesystem is ar0s1 and I believe it corresponds to ``device ataraid'' in the kernel. I read the raid mirroring page in the handbook, although, I'm thinking your controller should represent each disk as ``ar0'' and handle the mirroring itself (possibly consisting of two sets of two disks). I really don't know though. It looks like the RAID1 mirroring tutorial is for systems that don't actually have a raid controller. Hence, the RAID0 tutorial is the one that I would be using if I did not use the promise controller. Because I _DO_ use the controller, I am simply able to manipulate the ar0 disk array as a single disk. I imagine your setup will differ, but I hope this helps. -Michael ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
PCMCIA USB card problems
I've got an 4 Port PCMCIA connector with a VIA chipset. The manual claims it's an OHCI/EHCI device, but FreeBSD identifies it as an VIA 83C572 UHCI device. After the identification there is a nonesaying errormessage and the system crashs. Compiling the kernel without UHCI I get the following output when I put the card into the slot: cardbus0: Expecting link target, got 0xff cardbus0: Resource not specified in CIS: id=14, size=100 cardbus0: Resource not specified in CIS: id=20, size=20 cardbus0: at device 0.0 (no driver attached) cardbus0: Expecting link target, got 0xff cardbus0: Resource not specified in CIS: id=14, size=100 cardbus0: Resource not specified in CIS: id=20, size=20 cardbus0: at device 0.1 (no driver attached) cardbus0: Expecting link target, got 0xff cardbus0: Resource not specified in CIS: id=10, size=100 cardbus0: Resource not specified in CIS: id=14, size=100 ehci1: mem 0xc0208000-0xc02080ff,0xc0209000-0xc02090ff irq 11 at device 0.2 on cardbus0 ehci1: [GIANT-LOCKED] usb1: EHCI version 1.0 usb1: wrong number of companions (2 != 0) usb1: unrecoverable error, controller halted usb1: blocking intrs 0x10 usb1: run timeout ehci1: USB init failed err=13 device_attach: ehci1 attach returned 5 The system doesn't crash, but obviously it doesn't work either. Anyway that output looks more useful, maybe someone here can give me a hint, or is the chipset simply not supportet (the VIA 83C572 is in the supportet hardware list, but I don't know weather that realy is the chipset or just what FreeBSD thinks it is). signature.asc Description: OpenPGP digital signature
3ware firmware problem under 6.0-STABLE
Hi there, I've built 6.0-STABLE as of today after a fresh 6.0 install on a Supermicro motherboard with a 3Ware 9000S-12 , and TWA_FLASH_FIRMWARE compiled in. The driver went from 3.60.00.017 to 3.60.02.012 , but the firmware could not be written. Here's the dmesg: twa0: [FAST] twa0: INFO: (0x15: 0x100c): Flashing bundled firmware...: twa0: ERROR: (0x03: 0x0232): Binary image architecture incompatible: opcode=0x56 twa0: ERROR: (0x15: 0x1006): Firmware flash failed: cmd = 0x16, chunk # 0, cmd status = 2 twa0: INFO: (0x15: 0x1017): Issuing hard (commanded) reset to the controller...: twa0: WARNING: (0x15: 0x100d): Unable to flash bundled firmware. Attempting to work with fw on ctlr...: twa0: INFO: (0x15: 0x1300): Controller details:: Model 9500S-12, 12 ports, Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047 3ware device driver for 9000 series storage controllers, version: 3.60.02.012 twa0: <3ware 9000 series Storage Controller> port 0x2000-0x20ff mem 0xdd20-0xdd2000ff,0xdf80-0xdfff irq 72 at device 2.0 on pci3 da0: <3ware Logical Disk 00 1.00> Fixed Direct Access SCSI-0 device Any ideas ? Thanks in advance! -Carlos ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dhclient wedged
On Sun, Jan 22, 2006 at 02:52:44AM -0500, Forrest Aldrich wrote: > > I reported this problem a few OS versions back... pre-6. I'm on > FreeBSD-6-STABLE, and I've found the dhclient once again "wedged" in a > mode that was eating a lot of CPU. > > The solution is to kill it, and restart. > > I'm on Comcast's network, so I don't really know if their DHCP server is > doing something that FreeBSD's stock dhclient doesn't like; however, I > wonder if someone else has noticed this problem, etc. > Yes, I've also had the same problem (6.0-RELEASE), on Comcast also. I installed isc-dhcp3-client-3.0.3_1 from ports and haven't had a problem since. (crossing fingers ;=) -- Kelly D. Grills [EMAIL PROTECTED] pgpDlQTBKxIUa.pgp Description: PGP signature
Re: panic: mb_dtor_mbuf: M_EXT set
On Sun, Jan 22, 2006 at 04:17:12PM +0300, Gleb Smirnoff wrote: > On Sat, Jan 21, 2006 at 03:09:02PM +0300, Gleb Smirnoff wrote: > T> This should be fixed in src/sys/kern_mbuf.c, rev. 1.9.2.3 > > And another bogus panic is removed in 1.9.2.4 > The kernel is working again, thanks! - Christian -- Christian Brueffer [EMAIL PROTECTED] [EMAIL PROTECTED] GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D pgp0q3IKlKZS6.pgp Description: PGP signature
Re: Best release for IBM laptop R51
Graham North <[EMAIL PROTECTED]> wrote: > I am planning to load FreeBSD as a dual boot on new IBM laptop. > The model is an R51 which comes with: > Radeon 7500 - video > Intel Pro/1000 NT Mobile > Intel Pro/Wireless 2200BG > Integrated Audio > Intel 82802 UltraATA > Can anyone tell me whether the above hardware is all supported and > stable in FreeBSD. I had RELENG_5 installed on my ThinkPad R51 UN0K6GE until two weeks ago when I switched to RELENG_6. It was stable with 5.4 and is stable now. I just updated to get some of the new features. > Should I therefore download 6.0-Release and then just cvsup and > rebuild?? Is this a better option than using 5.4 at this point? I'd skip 5.4. It was good, but 6.0 is even better. Fabian -- http://www.fabiankeil.de/ signature.asc Description: PGP signature
Re: panic: mb_dtor_mbuf: M_EXT set
On Sat, Jan 21, 2006 at 03:09:02PM +0300, Gleb Smirnoff wrote: T> This should be fixed in src/sys/kern_mbuf.c, rev. 1.9.2.3 And another bogus panic is removed in 1.9.2.4 -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Best release for IBM laptop R51
On Sat, Jan 21, 2006 at 01:20:47PM -0800, Graham North wrote: > I am planning to load FreeBSD as a dual boot on new IBM laptop. > The model is an R51 which comes with: I also used to run FreeBSD 6.0 on a R51, the only difference I can see is that my TP has a Radeon 9000. Everything should work and I would also recommend 6.0, except for an annoying problem with wlan/wpa_supplicant: the wlan connection will be dead from time to time (see PR kern/88793). bye, Uwe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: uma panic while unloading sbp.ko
On Sun, 22 Jan 2006 12:44:53 +0100 Marc "UBM" Bocklet <[EMAIL PROTECTED]> wrote: [panic and debug info] Stupid me forgot to attach the debug info. Bye Marc -- "And what rough beast, its hour come round at last, Slouches towards Bethlehem to be born?" W.B. Yeats, The Second Coming backtrace: *** Tracing pid 3168 tid 100195 td 0xc41cf960 uma_zfree_internal(c1061960,c32ef400,0,1,3,0,c106c8c0,dacd7c60) at uma_zfree_internal+0x120 uma_zfree_arg(c1061960,c32ef400,0,c0807c76,0) at uma_zfree_arg+0x3ea malloc_uninit(c0993100,c0807c76,dacd7c5c,dacd7c60,0) at malloc_uninit+0x109 linker_file_sysuninit(c32e4600,c0846120,0,c3d01100,0) at linker_file_sysuninit+0xa0 linker_file_unload(c32e4600,0,dacd7cd0,c05fa4f8,c41cf960) at linker_file_unload+0x144 kern_kldunload(c41cf960,7,0,dacd7d30,c07c2310) at kern_kldunload+0xd2 kldunloadf(c41cf960,dacd7d04,8,c41cf960,4) at kldunloadf+0x2c syscall(3b,3b,3b,7,bfbfee72) at syscall+0x380 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (444, FreeBSD ELF32, kldunloadf), eip = 0x280ba877, esp = 0xbfbfe90c, ebp = 0xbfbfed78 --- *** panic string: *** sbp0: detached Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x15 fault code = supervisor read, page not present instruction pointer = 0x20:0xc0759760 stack pointer = 0x28:0xdacd7bc8 frame pointer = 0x28:0xdacd7be8 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 = 3168 (kldunload) *** output of "show uma": *** db> show uma Zone AllocsFrees UsedCache NetGraph items 24771234 247712340 390 FFS2 dinode 3308171 3298325 984611169 FFS1 dinode0000 FFS inode 3308171 3298325 984613470 SWAPMETA1927415886 3388 280 pfosfp 1880 188 193 pfospfen 3450 345 87 pfiaddrpl0000 pfstatescrub0000 pffrcent0000 pffrcache0000 pffrag0000 pffrent0000 pfrkentry20000 pfrkentry0000 pfrktable0000 pfpooladdrpl0000 pfaltqpl0000 pfstatepl0000 pfrulepl0000 pfsrctrpl0000 rtentry 87 59 28 88 unpcb 8182 8133 49 119 ripcb 15 141 65 sackhole13044130440 507 tcpreass 566092 5660920 507 hostcache 4947 4814 133 817 syncache29421294210 195 tcptw14889148872 466 tcpcb4912948973 156 532 inpcb4912948971 158 722 udpcb2100320991 12 98 socket7843778217 220 506 KNOTE30031300310 168 PIPE9236792348 19 323 DIRHASH1439913634 765 595 NFSNODE0000 NFSMOUNT0000 NAMEI 10775109 107751090 180 L VFS Cache3227232246 26 312 S VFS Cache 3684054 36736231043116449 VNODEPOLL101 99 VNODE 3317412 3307499 991322861 ata_composite0000 ata_request 246253 2462530 323 g_bio 6311045 63110450 580 ACL UMA zone 18859235 188592350 40 mbuf_cluster 2212812 2212110 7020 mbuf 64727120
uma panic while unloading sbp.ko
Hiho! :-) I encountered a non-repeatable panic with FreeBSD greatsheep 6.0-STABLE FreeBSD 6.0-STABLE #4: Sun Jan 15 16:13:56 CET 200 6 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SUBMARINE_SMP i386 System was built at the end of november 2005. The panic: sbp0: detached Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x15 fault code = supervisor read, page not present instruction pointer = 0x20:0xc0759760 stack pointer = 0x28:0xdacd7bc8 frame pointer = 0x28:0xdacd7be8 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 = 3168 (kldunload) Backtrace: Tracing pid 3168 tid 100195 td 0xc41cf960 uma_zfree_internal(c1061960,c32ef400,0,1,3,0,c106c8c0,dacd7c60) at uma_zfree_internal+0x120 uma_zfree_arg(c1061960,c32ef400,0,c0807c76,0) at uma_zfree_arg+0x3ea malloc_uninit(c0993100,c0807c76,dacd7c5c,dacd7c60,0) at malloc_uninit+0x109 linker_file_sysuninit(c32e4600,c0846120,0,c3d01100,0) at linker_file_sysuninit+0xa0 linker_file_unload(c32e4600,0,dacd7cd0,c05fa4f8,c41cf960) at linker_file_unload+0x144 kern_kldunload(c41cf960,7,0,dacd7d30,c07c2310) at kern_kldunload+0xd2 kldunloadf(c41cf960,dacd7d04,8,c41cf960,4) at kldunloadf+0x2c syscall(3b,3b,3b,7,bfbfee72) at syscall+0x380 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (444, FreeBSD ELF32, kldunloadf), eip = 0x280ba877, esp = 0xbfbfe90c, ebp = 0xbfbfed78 --- What I did: Connect a non-working external firewire hdd-case to my firewire pci card. Disconnected it. Unloaded sbp.ko (no device was registered, as the stupid case is obviously broken) and my system panicked. Further debug information is attached (show uma, show threads). Thanks in advance for your help :-) Bye Marc -- "And what rough beast, its hour come round at last, Slouches towards Bethlehem to be born?" W.B. Yeats, The Second Coming ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PXE Installation
> On Fri, 2006-01-20 at 03:36 +0100, Karel Miklav wrote: > > Hi, > > > > I'm trying to install FreeBSD 6.0 to a sub-notebook without > > floppy or optical unit. > > > Please give me a hand, I'm playing with this for whole week. > > > nice game aint it? sure of your friends is tcpdump :) > > > steps to follow (more below), create: > > 1 pxeboot > 2 exports a nfs bootdir > 3 populate bootdir > 4 config dhcpd.conf > 5 add hosts to dns or /etc/hosts > 6 proper config for the bootdir > > 1. pxe > >mkdir /tftboot >cp /boot/pxeboot /tftboot/ >change in /etc/inetd.conf (remove #) > >#tftp dgram udp waitroot/usr/libexec/tftpd >tftpd -l -s /tftpboot > to >tftp dgram udp waitroot/usr/libexec/tftpd >tftpd -l -s /tftpboot > >/etc/rc.d/inetd restart > > 2. exports a nfs bootdir > > add this line to /etc/exports > > /usr/ -maproot=0 -alldirs > this should be more secure: /usr -ro -maproot=root -alldirs ... danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PXE Installation
On Fri, 2006-01-20 at 03:36 +0100, Karel Miklav wrote:
> Hi,
>
> I'm trying to install FreeBSD 6.0 to a sub-notebook without
> floppy or optical unit.
>
>
> Please give me a hand, I'm playing with this for whole week.
>
nice game aint it? sure of your friends is tcpdump :)
steps to follow (more below), create:
1 pxeboot
2 exports a nfs bootdir
3 populate bootdir
4 config dhcpd.conf
5 add hosts to dns or /etc/hosts
6 proper config for the bootdir
1. pxe
mkdir /tftboot
cp /boot/pxeboot /tftboot/
change in /etc/inetd.conf (remove #)
#tftp dgram udp waitroot/usr/libexec/tftpd
tftpd -l -s /tftpboot
to
tftp dgram udp waitroot/usr/libexec/tftpd
tftpd -l -s /tftpboot
/etc/rc.d/inetd restart
2. exports a nfs bootdir
add this line to /etc/exports
/usr/ -maproot=0 -alldirs
add to /etc/rc.conf:
rpcbind_enable="yes"
nfs_server_enable="yes"
reboot (or restart this services nfsd mountd)
3. populate bootdir
cd /usr/src
make buildworld
make buildkernel
make installworld DESTDIR=/usr/bootdir
make distribution DESTDIR=/usr/bootdir
make installkernel DESTDIR=/usr/bootdir
4. add someting like this to your /usr/local/etc/dhcpd.conf
host workstation {
hardware ethernet 00:13:d4:22:69:0c;
fixed-address 192.168.1.6;
filename "pxeboot";
option root-path "192.168.1.2:/usr/workstation";
option domain-name "martenvijn.nl";
option domain-name-servers 192.168.1.2;
}
change the ipnumbers for your ipspace, macaddress and local config
sh /usr/local/etc/rc.d/isc-dhcpd.sh restart
5. in the hostfiles in /etc/hosts and /bootdir/etc/hosts
192.168.1.6 bert
192.168.1.2 ernie
I use dns for this.
6. in /usr/bootdir/etc/rc.conf
hostname="workstation.martenvijn.nl"
rpcbind_enable="yes"
nfs_client_enable="yes"
populate_var="yes"
in /usr/bootdir/etc/fstab
192.168.1.2:/usr/bootdir / nfs rw,soft,lockd 0 0
md /varmfs rw,-s64m,-M 2 0
md /tmpmfs rw,-s64m,-M 2 0
This should be it. boot laptop and run sysinstall.
Note: This not a very secure setup,
cheers Marten
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PXE Installation
On Fri, 2006-01-20 at 03:36 +0100, Karel Miklav wrote:
> Hi,
>
> I'm trying to install FreeBSD 6.0 to a sub-notebook without
> floppy or optical unit.
> Please give me a hand, I'm playing with this for whole week.
>
nice game aint it? sure of your friends is tcpdump :)
steps to follow (more below), create:
1 pxeboot
2 exports a nfs bootdir
3 populate bootdir
4 config dhcpd.conf
5 add hosts to dns or /etc/hosts
6 proper config for the bootdir
1. pxe
mkdir /tftboot
cp /boot/pxeboot /tftboot/
change in /etc/inetd.conf (remove #)
#tftp dgram udp waitroot/usr/libexec/tftpd
tftpd -l -s /tftpboot
to
tftp dgram udp waitroot/usr/libexec/tftpd
tftpd -l -s /tftpboot
/etc/rc.d/inetd restart
2. exports a nfs bootdir
add this line to /etc/exports
/usr/ -maproot=0 -alldirs
add to /etc/rc.conf:
rpcbind_enable="yes"
nfs_server_enable="yes"
reboot (or restart this services nfsd mountd)
3. populate bootdir
cd /usr/src
make buildworld
make buildkernel
make installworld DESTDIR=/usr/bootdir
make distribution DESTDIR=/usr/bootdir
make installkernel DESTDIR=/usr/bootdir
4. add someting like this to your /usr/local/etc/dhcpd.conf
host workstation {
hardware ethernet 00:13:d4:22:69:0c;
fixed-address 192.168.1.6;
filename "pxeboot";
option root-path "192.168.1.2:/usr/workstation";
option domain-name "martenvijn.nl";
option domain-name-servers 192.168.1.2;
}
change the ipnumbers for your ipspace, macaddress and local config
sh /usr/local/etc/rc.d/isc-dhcpd.sh restart
5. in the hostfiles in /etc/hosts and /bootdir/etc/hosts
192.168.1.6 bert
192.168.1.2 ernie
I use dns for this.
6. in /usr/bootdir/etc/rc.conf
hostname="workstation.martenvijn.nl"
rpcbind_enable="yes"
nfs_client_enable="yes"
populate_var="yes"
in /usr/bootdir/etc/fstab
192.168.1.2:/usr/bootdir / nfs rw,soft,lockd 0 0
md /varmfs rw,-s64m,-M 2 0
md /tmpmfs rw,-s64m,-M 2 0
This should be it. boot laptop and run sysinstall.
Note: This not a very secure setup,
cheers Marten
> --
>
> Regards,
> Karel Miklav
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "[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: Using [Open]LDAP for authentication
On Sunday 22 January 2006 15:44, Andrew Zenk wrote: > My guess is that you have a group (wheel) defined in /etc/group that > is conflisting with the one in ldap. I've had this issue before. I > solved it by deleteing the offending group from the group file. > Another solution would be to tell sudo to look for a different group > and make sure the LDAP group is unique. Yeah, I worked around it by adding the few sudo/su users to the group file. I am surprised that this is necessary though - I would expect nss to look through all resources and merge group entries. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgp0tPuOXbI1n.pgp Description: PGP signature
