Re: 5.2-BETA dsp.c duplicate lock
Maxime Henrion wrote: > Mathew Kanner wrote: > [patch ripped] >> >> Maxime, >> I think it would be better to isolate the changes (DUP_OK flag >> and lock creation) to just the channel code, no need to touch every >> driver. > > Yes, but to do this I'd need either to make the channel code use > mtx_init() directly, which would defeat the purpose of the USING_MUTEX > define, or to completely unifdef -U it. Since I had no idea if this code > was actually used or not, I went the safe way and just changed the > snd_mtxcreate() wrapper interface to accept mutex options. For what it's > worth, there is at least one direct invokation of mtx_init() in the sound > drivers, so it seems this define is actually already broken. > > This needs to be sorted out before committing this patch if we need to, > but for now, I just wanted to see if using MTX_DUPOK solved the problem or > not. I'll try to test later today. Thanks! -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.2-BETA dsp.c duplicate lock
Jesse Guardiani wrote: > I get this every time I `startx`. I didn't see it in > the archive either: > > > acquiring duplicate lock of same type: "pcm channel" > 1st pcm0:record:0 @ /usr/src/sys/dev/sound/pcm/dsp.c:144 > 2nd pcm0:virtual:0 @ /usr/src/sys/dev/sound/pcm/dsp.c:146 > Stack backtrace: > backtrace(c089b7e5,c3c96a54,c0a8f35a,92,200246) at backtrace+0x17 > witness_lock(c3c6aa80,8,c0a8f35a,92,2002) at witness_lock+0x672 > _mtx_lock_flags(c3c6aa80,0,c0a8f35a,92,c4) at _mtx_lock_flags+0xba > getchns(c3d07700,e473faf0,e473faf4,3000,c3b86980) at getchns+0x1b5 > dsp_poll(c3d07700,c4,c403e640,c097fce0,0) at dsp_poll+0x46 > spec_poll(e473fb48,e473fb68,c06d600c,e473fb48,c0937ca0) at spec_poll+0x180 > spec_vnoperate(e473fb48,c0937ca0,c438db2c,c4,c4361a80) at > spec_vnoperate+0x18 vn_poll(c4599110,c4,c4361a80,c403e640,c4361a80) at > vn_poll+0x3c pollscan(c403e640,e473fbd8,3,3e1,18) at pollscan+0xb3 > poll(c403e640,e473fd14,c08b631d,3ee,3) at poll+0x252 > syscall(2f,2f,2f,,bfbfe748) at syscall+0x2c0 > Xint0x80_syscall() at Xint0x80_syscall+0x1d > --- syscall (209), eip = 0x2869322f, esp = 0xbfbfe70c, ebp = 0xbfbfe768 > --- > I this a known LOR? Or do I need to submit a pr? -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
another 5.2-BETA lock order reversal
Checked the archive and didn't see this one listed yet: lock order reversal 1st 0xc4047134 filedesc structure (filedesc structure)[EMAIL PROTECTED]/usr/src/sys/kern/sys_ generic.c:896 2nd 0xc0956a80 Giant (Giant)[EMAIL PROTECTED]/usr/src/sys/fs/specfs/spec_vnops.c:377 Stack backtrace: backtrace(c089b89c,c0956a80,c0897b1f,c0897b1f,c0893352) at backtrace+0x17 witness_lock(c0956a80,8,c0893352,179,0) at witness_lock+0x672 _mtx_lock_flags(c0956a80,0,c0893352,179,c089bea3) at _mtx_lock_flags+0xba spec_poll(e476fafc,e476fb1c,c06d600c,e476fafc,c0937ca0) at spec_poll+0x134 spec_vnoperate(e476fafc,c0937ca0,c3c7e410,40,c435d680) at spec_vnoperate+0x18 vn_poll(c45992a8,40,c435d680,c43323c0,c435d680) at vn_poll+0x3c selscan(c43323c0,e476fb9c,e476fb8c,1,4) at selscan+0x141 kern_select(c43323c0,1,bfbfe890,0,bfbfe810) at kern_select+0x37f select(c43323c0,e476fd14,c08b631d,3ee,5) at select+0x66 syscall(2f,2f,2f,0,0) at syscall+0x2c0 Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (93), eip = 0x2845b94f, esp = 0xbfbfe7cc, ebp = 0xbfbfe928 --- -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB 1.0 IDE to ATAPI drive enclosure failure
Jesse Guardiani wrote: > This is interesting: > > > [17:[EMAIL PROTECTED]:[~]# camcontrol devlist > at scbus1 target 0 lun 0 (da0,pass0) > > [17:[EMAIL PROTECTED]:[~]# camcontrol inquiry 1:0:0 > pass0: Fixed Direct Access SCSI-0 device > pass0: Serial Number > pass0: 1.000MB/s transfers > > > So it looks like it's just not recognizing the file system on da0. > Perhaps I should try `camcontrol format`? It would probably take for ever > to format a 32Gb disk over a 1M link, but I could leave it on over > night... > > I originally formatted this disk by putting it in my primary drive sled > in my laptop and running a partitioning program... I just upgraded to FreeBSD 5.2-BETA and this drive works now! Apparently something in the umass driver has changed for the better since 5.1-RELEASE and 4.8-RELEASE (the systems I tested the drive on that didn't work). Woo hoo! -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5.2-BETA dsp.c duplicate lock
I get this every time I `startx`. I didn't see it in the archive either: acquiring duplicate lock of same type: "pcm channel" 1st pcm0:record:0 @ /usr/src/sys/dev/sound/pcm/dsp.c:144 2nd pcm0:virtual:0 @ /usr/src/sys/dev/sound/pcm/dsp.c:146 Stack backtrace: backtrace(c089b7e5,c3c96a54,c0a8f35a,92,200246) at backtrace+0x17 witness_lock(c3c6aa80,8,c0a8f35a,92,2002) at witness_lock+0x672 _mtx_lock_flags(c3c6aa80,0,c0a8f35a,92,c4) at _mtx_lock_flags+0xba getchns(c3d07700,e473faf0,e473faf4,3000,c3b86980) at getchns+0x1b5 dsp_poll(c3d07700,c4,c403e640,c097fce0,0) at dsp_poll+0x46 spec_poll(e473fb48,e473fb68,c06d600c,e473fb48,c0937ca0) at spec_poll+0x180 spec_vnoperate(e473fb48,c0937ca0,c438db2c,c4,c4361a80) at spec_vnoperate+0x18 vn_poll(c4599110,c4,c4361a80,c403e640,c4361a80) at vn_poll+0x3c pollscan(c403e640,e473fbd8,3,3e1,18) at pollscan+0xb3 poll(c403e640,e473fd14,c08b631d,3ee,3) at poll+0x252 syscall(2f,2f,2f,,bfbfe748) at syscall+0x2c0 Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (209), eip = 0x2869322f, esp = 0xbfbfe70c, ebp = 0xbfbfe768 --- -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
LOR w/5.2-BETA
I got this LOR today after upgrading my IBM Thinkpad A30p from 5.1-RELEASE to 5.2-BETA: lock order reversal 1st 0xc43d8ad4 vm object (vm object) @ /usr/src/sys/vm/swap_pager.c:1323 2nd 0xc098cf60 swap_pager swhash (swap_pager swhash) @ /usr/src/sys/vm/swap_pag er.c:1838 3rd 0xc10368c4 vm object (vm object) @ /usr/src/sys/vm/uma_core.c:876 Stack backtrace: backtrace(c089b8b5,c10368c4,c08afa80,c08afa80,c08b0961) at backtrace+0x17 witness_lock(c10368c4,8,c08b0961,36c,c3c7da80) at witness_lock+0x672 _mtx_lock_flags(c10368c4,0,c08b0961,36c,c3c7da94) at _mtx_lock_flags+0xba obj_alloc(c3c7da80,1000,d2a6ba03,101,c095b220) at obj_alloc+0x3f slab_zalloc(c3c7da80,1,8,c08b0961,68c) at slab_zalloc+0xb3 uma_zone_slab(c3c7da80,1,c08b0961,68c,c3c7db20) at uma_zone_slab+0xd6 uma_zalloc_internal(c3c7da80,0,1,5c1,c08ae87a,72e) at uma_zalloc_internal+0x3e uma_zalloc_arg(c3c7da80,0,1,72e,2) at uma_zalloc_arg+0x3ab swp_pager_meta_build(c43d8ad4,19,0,2,0) at swp_pager_meta_build+0x174 swap_pager_putpages(c43d8ad4,d2a6bbd0,1,0,d2a6bb40) at swap_pager_putpages+0x32d default_pager_putpages(c43d8ad4,d2a6bbd0,1,0,d2a6bb40) at default_pager_putpages +0x2e vm_pageout_flush(d2a6bbd0,1,0,eb,0) at vm_pageout_flush+0x17a vm_pageout_clean(c160b7a8,0,c08b077c,32a,0) at vm_pageout_clean+0x305 vm_pageout_scan(0,0,c08b077c,5a9,1f4) at vm_pageout_scan+0x64c vm_pageout(0,d2a6bd48,c0895fd8,311,0) at vm_pageout+0x31b fork_exit(c07e7e60,0,d2a6bd48) at fork_exit+0xb4 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xd2a6bd7c, ebp = 0 --- -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ISO IMAGES
Will ISO images be released for 5.2-BETA i386? Or is that strictly an -RC thing? Thanks. -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB 1.0 IDE to ATAPI drive enclosure failure
This is interesting: [17:[EMAIL PROTECTED]:[~]# camcontrol devlist at scbus1 target 0 lun 0 (da0,pass0) [17:[EMAIL PROTECTED]:[~]# camcontrol inquiry 1:0:0 pass0: Fixed Direct Access SCSI-0 device pass0: Serial Number pass0: 1.000MB/s transfers So it looks like it's just not recognizing the file system on da0. Perhaps I should try `camcontrol format`? It would probably take for ever to format a 32Gb disk over a 1M link, but I could leave it on over night... I originally formatted this disk by putting it in my primary drive sled in my laptop and running a partitioning program... -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB 1.0 IDE to ATAPI drive enclosure failure
Barney Wolff wrote: > On Mon, Nov 24, 2003 at 04:44:02PM -0500, Jesse Guardiani wrote: >> >> I'm running FreeBSD 5.1-RELEASE. I just bought a generic >> USB 1.1/2.0/firewire external drive enclosure for my 32gb >> Travelstar 2.0" 12.5mm hard drive. >> >> The device shows up like this: >> >> Nov 18 14:06:16 trevarthan kernel: umass0: Acer Labs USB 2.0 Storage >> Device, rev 2.00/1.03, addr 3 Nov 18 14:06:16 trevarthan kernel: da0 at >> umass-sim0 bus 0 target 0 lun 0 Nov 18 14:06:17 trevarthan kernel: da0: >> Fixed Direct Access SCSI-0 device Nov 18 >> 14:06:17 trevarthan kernel: da0: 1.000MB/s transfers Nov 18 14:06:17 >> trevarthan kernel: da0: 30520MB (62506080 512 byte sectors: 255H 63S/T >> 3890C) >> >> But `ls -al /dev/da*` reveals no slices: > > If you're using an ohci usb controller, perhaps you need a patch. > Browse the -current archives for the last week or so. Sorry, I didn't realize that might be important. Pretty sure it's UHCI: [17:[EMAIL PROTECTED]:[~]% usbdevs addr 1: UHCI root hub, Intel addr 1: UHCI root hub, Intel addr 2: USB Receiver, Logitech addr 1: UHCI root hub, Intel And from dmesg.boot: uhci0: port 0x1800-0x181f irq 9 at device 29.0 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x1820-0x183f irq 11 at device 29.1 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x1840-0x185f irq 9 at device 29.2 on pci0 usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
USB 1.0 IDE to ATAPI drive enclosure failure
Howdy list, I'm running FreeBSD 5.1-RELEASE. I just bought a generic USB 1.1/2.0/firewire external drive enclosure for my 32gb Travelstar 2.0" 12.5mm hard drive. The device shows up like this: Nov 18 14:06:16 trevarthan kernel: umass0: Acer Labs USB 2.0 Storage Device, rev 2.00/1.03, addr 3 Nov 18 14:06:16 trevarthan kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Nov 18 14:06:17 trevarthan kernel: da0: Fixed Direct Access SCSI-0 device Nov 18 14:06:17 trevarthan kernel: da0: 1.000MB/s transfers Nov 18 14:06:17 trevarthan kernel: da0: 30520MB (62506080 512 byte sectors: 255H 63S/T 3890C) But `ls -al /dev/da*` reveals no slices: crw-r- 1 root operator4, 22 Nov 18 13:35 /dev/da0 The hard disk inside this enclosure was formatted with a 10gig FAT32 partition. It works fine in a Coolmax Gemini 2.5" USB 2.0/1.1 drive enclosure (which shows up as IDE->ATA under Windows XP), and it works fine in this enclosure as long as I'm running Windows XP (but it shows up differently than the Gemini under XP: IDE-ATAPI). It just doesn't work under FreeBSD 5.1-RELEASE or FreeBSD 4.8-RELEASE for some reason... I've found the following links relating to similar problems: http://lists.freebsd.org/pipermail/freebsd-current/2003-August/008504.html http://lists.freebsd.org/pipermail/freebsd-hardware/2003-July/000393.html But no solutions. Has the USB code been updated since FreeBSD 5.1-RELEASE? Is there a chance it will work if I cvsup to -CURRENT? I contacted the gentleman from the first link above, and he said that the only thing different about his configuration (other than hardware) is that: 1.) He connects through a USB hub 2.) He runs -CURRENT from Nov 7th I can't seem get my hands on a USB hub, so it looks like my only option is -CURRENT. Does anyone have any clues to help get this drive working? I'm all for debugging of any kind, including coding. I'm just not sure where to start. Thanks! -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atheros (ath) driver bridging
Sam Leffler wrote: >> Yes, I was referring to bridging two wireless interfaces. > > David Young (of netbsd) has plans for WDS support that should fit into the > existing 802.11 layer. With his design you should be able to bridge WDS > links using the standard bridge support. No ETA. I appologize for my ignorance, but when you say 'WDS', do you mean something having to do with 802.11f? I've been trying to figure out just what WDS is from this thread: http://lists.personaltelco.net/pipermail/general/2002q1/005791.html But so far I'm not getting a clear picture. Jason Luther seems to indicate that WDS is largely proprietary thus far, which makes me wonder how a NetBSD guy could do anything useful with it. I think it may be IEEE standard reading time for me: http://standards.ieee.org/getieee802/802.11.html Thanks. -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atheros (ath) driver bridging
Sam Leffler wrote: >> Is the ath(4) driver, like the wi(4) driver, incapable of performing >> bridging? > > Sorry, answered too quickly. ath and wi have the same restrictions. You > can use bridging to hookup a wired and wireless network but not two > wireless networks. I can't tell from your posting what you are trying to > do. Yes, I was refering to bridging two wireless interfaces. I suppose that if I had a soekris 4521 box I could run a crossover between the ethernet interfaces and bridge wi-eth ... eth-wi... :) Just a tad inefficient, but it might work... -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
atheros (ath) driver bridging
Howdy list, Is the ath(4) driver, like the wi(4) driver, incapable of performing bridging? For reference, this is from the bridge(4) manpage: Bridging requires interfaces to be put in promiscuous mode, and transmit packets with Ethernet source addresses. Some interfaces (e.g. wi(4)) do not support this functionality. Also, bridging is not compatible with interfaces which use hardware loopback, because there is no way to tell locally generated packets from externally generated ones. ath(4) manpage: http://www.freebsd.org/cgi/man.cgi?query=ath&apropos=0&sektion=0&manpath=FreeBSD+5.1-current&format=html wi(4) manpage: http://www.freebsd.org/cgi/man.cgi?query=wi&sektion=4&apropos=0&manpath=FreeBSD+5.1-current bridge(4) manpage: http://www.freebsd.org/cgi/man.cgi?query=bridge&apropos=0&sektion=0&manpath=FreeBSD+5.1-current&format=html Just curious. Thanks! -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: route problems in 5.1-RELEASE
Martin Blapp wrote: > > Hi, > >>Normally, if I want to swap from wi0 to fxp0, all I >>have to do is: >> >>killall dhclient >>ifconfig wi0 down >>ifconfig fxp0 up >>dhclient fxp0 > > Why don't you just update to 5.X, run mergemaster- > > Then just remove the wi0 card and plug in a ethernet > cable to the internal NIC ? This works wonderful here. > No manual interaction needed anymore. Dhclient had a bunch > of fixes for this problem, the rc system had it too. All of > them are fixed. Ok. Glad to hear it. I would update to -CURRENT, but I'm a little worried about my ATA drive not being detected with the new ATAng stuff. :) Not to mention the hastle of having to compile all my userland stuff from source. (You can't use packages with -CURRENT, right? Or am I mistaken?) This isn't a beater laptop. I actually use it for real work. So maybe I'll just wait for 5.2-RELEASE... -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: route problems in 5.1-RELEASE
Kevin Oberman wrote: >> From: Jesse Guardiani <[EMAIL PROTECTED]> >> Date: Thu, 11 Sep 2003 16:19:42 -0400 >> Sender: [EMAIL PROTECTED] >> >> Howdy list, >> >> I'm having major problems with the route command today. >> My machine is an IBM Thinkpad A30p laptop, running FreeBSD >> 5.1-RELEASE. >> >> I have two interfaces. wi0 and fxp0 >> >> Normally, if I want to swap from wi0 to fxp0, all I >> have to do is: >> >> killall dhclient >> ifconfig wi0 down >> ifconfig fxp0 up >> dhclient fxp0 >> >> And I'm done. However, ocassionally this backfires, >> like it did today: > > Jesse, > > Try changing your list of commands to: > killall dhclient > ifconfig wi0 down > route flush > ifconfig fxp0 up > dhclient fxp0 > > That should fix it up. Sorry for neglecting to mention it, but I did that, multiple times, in multiple places. I _didn't_ do it the FIRST time, but I did do multiple times after that. Perhaps I should do it the first time, from now on? Would that prevent the problem? -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
route problems in 5.1-RELEASE
Howdy list, I'm having major problems with the route command today. My machine is an IBM Thinkpad A30p laptop, running FreeBSD 5.1-RELEASE. I have two interfaces. wi0 and fxp0 Normally, if I want to swap from wi0 to fxp0, all I have to do is: killall dhclient ifconfig wi0 down ifconfig fxp0 up dhclient fxp0 And I'm done. However, ocassionally this backfires, like it did today: My fxp0 interface is up: fxp0: flags=8843 mtu 1500 inet6 fe80::2d0:59ff:feaa:70ec%fxp0 prefixlen 64 scopeid 0x3 inet 192.168.1.101 netmask 0xff00 broadcast 192.168.1.255 ether 00:d0:59:aa:70:ec media: Ethernet autoselect (100baseTX ) status: active And my wi0 interface is down: wi0: flags=8802 mtu 1500 inet6 fe80::220:e0ff:fe8a:9061%wi0 prefixlen 64 scopeid 0x2 inet 192.168.1.47 netmask 0xff00 broadcast 192.168.1.255 ether 00:20:e0:8a:90:61 media: IEEE 802.11 Wireless Ethernet autoselect (none) ssid WingNET 1:WingNET stationname "FreeBSD WaveLAN/IEEE node" channel -1 authmode OPEN powersavemode OFF powersavesleep 100 wepmode MIXED weptxkey 1 wepkey 1:128-bit But routes to the internet are still wanting to use the wi0 interface for some reason: [16:[EMAIL PROTECTED]:[~]# route get 206.30.215.2 route to: 206.30.215.2 destination: 206.30.215.2 gateway: 192.168.1.1 interface: wi0 flags: recvpipe sendpipe ssthresh rtt,msecrttvar hopcount mtu expire 0 0 0 0 0 0 1500 3584 [16:[EMAIL PROTECTED]:[~]# I can change the interface on a per-route basis, but not globally: [16:[EMAIL PROTECTED]:[~]# route change 206.30.215.2 -iface fxp0 change host 206.30.215.2: gateway fxp0 [16:[EMAIL PROTECTED]:[~]# route get 206.30.215.2 route to: 206.30.215.2 destination: 206.30.215.2 gateway: fxp0:0.d0.59.aa.70.ec interface: fxp0 flags: recvpipe sendpipe ssthresh rtt,msecrttvar hopcount mtu expire 0 0 0 0 0 0 1500 3582 [16:[EMAIL PROTECTED]:[~]# route get 206.30.215.4 route to: 206.30.215.4 destination: default mask: default gateway: 192.168.1.1 interface: wi0 flags: recvpipe sendpipe ssthresh rtt,msecrttvar hopcount mtu expire 0 0 0 0 0 0 1500 0 [16:[EMAIL PROTECTED]:[~]# Some funky combination of: ifconfig wi0 -alias And restarting dhclient fixed the problem, but it took forever. 1.) Is this a bug? 2.) If so, has it already been fixed in -CURRENT? Thanks! -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
KSE howto?
Howdy list, Is there a KSE howto guide anywhere? I'm thinking about updating my FreeBSD 5.1-RELEASE system to -CURRENT and compiling XFree, KDE, MySQL, and Apache2 with KSE support, just for fun. But I don't know how to enable KSE support at compile time... Thanks! -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Benchmarking KSE and SMPng
[EMAIL PROTECTED] wrote:
> Quoting Roderick van Domburg <[EMAIL PROTECTED]>:
>
>> > Just in case you don't know, there is no 5-STABLE yet. All the 5.x
>> Releases have
>> > been based on -CURRENT.
>>
>> Indeed, I stand corrected.
>>
>> > > Question is then which {application,theoretical} benchmarks to run
>> > > under which circumstances. Although I've heard of bonnie et al, I'm
>> > > new to the benchmarking business and welcome any suggestions.
>> > >
>> > Something that might be interesting to try is running mysql with
>> > libc_r, linuxthreads, libkse, and libthr, using the included mysql
>> > benchmarks that
>> come
>> > with mysql. I used those benchmarks to test mysql on a few of the
>> > machines
>> I
>> > needed to install it on at one point, and I know mysql utilizes
>> > threads.
>> Off
>> > the top of my head I can't think of anything other than databases that
>> > performed badly on FreeBSD before due to threading issues.
>>
>> How about Apache2 or locked subsystems (I/O and networking spring to
>> mind)?
>>
> Good call. I hadn't thought of that because I've always just used the
> preforking mpm in apache.
I'm very interested in hearing what you find from your benchmarks.
I've been wondering how much better KSE currently is in CURRENT ever since
I started running 5.1-RELEASE on my laptop a few months ago. But I don't
have the time to do extensive benchmarking, and I don't have a spare machine
to run them on. (hey, I need my laptop for work.)
I've also heard that 5.x ships with added kernel debugging and such. If that's
true, it might be a good idea to turn that off (not sure how.).
Also, running similar benchmarks on a 4.8 system would make a good comparison.
--
Jesse Guardiani, Systems Administrator
WingNET Internet Services,
P.O. Box 2605 // Cleveland, TN 37320-2605
423-559-LINK (v) 423-559-5145 (f)
http://www.wingnet.net
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
atheros (ath) driver, hostAP?
Howdy list, I'm running FreeBSD 5.1-RELEASE, and I'm considering messing around with some Soekris boards and making some embedded routers with built-in wireless access points and VPN stuff. I know I can do that with the Prism chipsets, but can I run in hostAP mode with the ath driver on an Atheros chipset? Seeing as how I don't run -CURRENT, I can't just run 'man ath'. Any info appreciated! Thanks! -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
dhclient/route buggy under 5.1-RELEASE
8088000,0x2,0x2710) 946 mozilla-bin RET poll 0 946 mozilla-bin CALL gettimeofday(0x28875178,0) 946 mozilla-bin RET gettimeofday 0 946 mozilla-bin CALL kevent(0xc,0,0,0xbfbfdeb0,0x1,0xbfbfde00) 946 mozilla-bin RET kevent 0 946 mozilla-bin CALL fstat(0xd,0xbfbfdda0) 946 mozilla-bin RET fstat 0 946 mozilla-bin CALL close(0xd) 946 mozilla-bin RET close 0 946 mozilla-bin CALL socket(0x2,0x2,0) 946 mozilla-bin RET socket 13/0xd 946 mozilla-bin CALL fcntl(0xd,0x3,0) 946 mozilla-bin RET fcntl 2 946 mozilla-bin CALL fcntl(0xd,0x4,0x6) 946 mozilla-bin RET fcntl 0 946 mozilla-bin CALL sendto(0xd,0xbfbfe130,0x1c,0,0x28956740,0x10) 946 mozilla-bin GIO fd 13 wrote 28 bytes "\M-m\M-q\^A\0\0\^A\0\0\0\0\0\0 trevarthan\0\0\^A\0\^A" -- END kdump OUTPUT -- I seem to remember someone else having trouble with this same (or similar) thing a month or so ago. Again, just an FYI. I'm not sure what caused it. Thanks! -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.1 on an A31p
Ben Laurie wrote: > So, after a long pause, I'm trying to get 5.x working on my IBM A31p. > I've made a boot CD from the 5.1 ISO images, vintage a week or so ago. > When I boot (in any mode, ACPI on or off, or Safe), it dies immediately > after discovering firewire: > > firewire0: on fwohci0 > > > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x2c > fault code = supervisor read, page not present > instruction pointer= 0x8:0xc02e5a50 > stack pointer = 0x10:0xc0ae39b0 > frame pointer = 0x10:0xc0ae39b4 > 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= 0 (swapper) > trap number= 12 > panic: page fault > > Now what? I had the same problem on an IBM A30p with 5.1. Do this at the boot loader prompt: set hw.pci.allow_unsupported_io_range=1 That should take care of it. You'll need to place the part after 'set' in your /boot/device.hints file after you complete the install, otherwise your kernel will continue to fail at boot. HTH. -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: acpi patch for dell laptop?
Eirik Oeverby wrote: > Crap. > I just saw that I had no quotes around the '1'. Will it still get that > setting, or do I have to change it and try again? > (My line says > hw.pci.allow_unsupported_io_range=1 > while I believe (according to the other examples in the file) it should > say > hw.pci.allow_unsupported_io_range="1" > . Does this make a difference?) I really don't know. It doesn't make a difference at the boot loader prompt, but I'm not sure if it matters in the device.hints file. Only way to be sure is to try it. -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: acpi patch for dell laptop?
Eirik Oeverby wrote: > On Mon, 23 Jun 2003 10:53:32 -0400 > Jesse Guardiani <[EMAIL PROTECTED]> wrote: > >> > And with ACPI disabled, the machine refuses totally to >> > boot, it hangs at 'Mounting root from ...'. If I undock the machine, >> > I can boot with and without ACPI, with the latter option being the >> > only usable (stable) mode. >> >> Just out of curiosity, have you tried setting >> >> hw.pci.allow_unsupported_io_range=1 >> >> in your /boot/device.hints file? I've found that this option fixes >> many unbootable laptops - especially thinkpads. > > Hmm.. Yes, I think I have. Atleast it's in my device.hints file now - > however I don't know if I tried docking it and booting without ACPI > after I put that line in.. Perhaps I should try again, but my gut > feeling tells me it's not gonna make any difference. Atleast as long as > its undocked it had no effect on any of the other problems I'm > experiencing. Try again and let me know. > > /Eirik -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: acpi patch for dell laptop?
Eirik Oeverby wrote: [...] > And with ACPI disabled, the machine refuses totally to > boot, it hangs at 'Mounting root from ...'. If I undock the machine, I > can boot with and without ACPI, with the latter option being the only > usable (stable) mode. Just out of curiosity, have you tried setting hw.pci.allow_unsupported_io_range=1 in your /boot/device.hints file? I've found that this option fixes many unbootable laptops - especially thinkpads. -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: APM problem in 5.1-RELEASE
Jesse Guardiani wrote:
> Things I would like to improve upon:
>
> 1.) I need to find some way to automatically kill any processes that are
> using (or have opened) the /dev/acd0 device BEFORE executing apm -z
> from /etc/rc.suspend.
OK. The following pipeline does a pretty good job of this:
# Kill any process currently using /dev/acd0
kill -KILL `fstat /dev/acd0 | sed -Ee 's/[[:space:]]+/ /g' | cut -d ' ' -f 3`
It isn't perfect (i.e. if more than one process has /dev/acd0 open, it won't
kill the second process), but I can expand on this to make it fit just about
any need.
[...]
> 2.) I'd love to automate (or do away with) the process of switching to
> a VTY from X before executing 'atacontrol detach 1'.
This from Tobias Roth:
-
to do this automatically, change your /etc/rc.suspend and /etc/rc.resume
like this:
/etc.rc.suspend: insert this line just before the 'logger' line:
vidcontrol -s 2 < /dev/ttyv0
/etc/rc.resume: insert this line just before the 'logger' line:
vidcontrol -s 1 < /dev/ttyv0
-
This works pretty darn well! Thanks Tobias!
I can now suspend my machine from X without fear of kernel panic!
Thanks for the help everyone!
Here is my rc.suspend, just in case someone else with an IBM Thinkpad A30p
needs it:
-- /etc/rc.suspend --
#!/bin/sh
#
# Copyright (c) 1999 Mitsuru IWASAKI
# All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
# 1. Redistributions of source code must retain the above copyright
#notice, this list of conditions and the following disclaimer.
# 2. Redistributions in binary form must reproduce the above copyright
#notice, this list of conditions and the following disclaimer in the
#documentation and/or other materials provided with the distribution.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
# ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
# FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
# OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
# OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
# SUCH DAMAGE.
#
# $FreeBSD: src/etc/rc.suspend,v 1.4 2000/10/08 19:18:24 obrien Exp $
#
# sample run command file for APM Suspend Event
if [ -r /var/run/rc.suspend.pid ]; then
exit 1
fi
echo $$ > /var/run/rc.suspend.pid
# If you have troubles on suspending with PC-CARD modem, try this.
# See also contrib/pccardq.c (Only for PAO users).
# pccardq | awk -F '~' '$5 == "filled" && $4 ~ /sio/ \
# { printf("pccardc power %d 0", $1); }' | sh
logger -t apmd suspend at `date +'%Y%m%d %H:%M:%S'`
# Kill any process currently using /dev/acd0
kill -KILL `fstat /dev/acd0 | sed -Ee 's/[[:space:]]+/ /g' | cut -d ' ' -f 3`
# switch to a TTY
vidcontrol -s 1 < /dev/ttyv0
# detach buggy CD-ROM before suspending.
sync && sync && sync
atacontrol detach 1
sleep 1
sync && sync && sync
sleep 1
rm -f /var/run/rc.suspend.pid
zzz
exit 0
-- end /etc/rc.suspend --
And here is my /etc/rc.resume:
-- /etc/rc.resume --
#!/bin/sh
#
# Copyright (c) 1999 Mitsuru IWASAKI
# All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
# 1. Redistributions of source code must retain the above copyright
#notice, this list of conditions and the following disclaimer.
# 2. Redistributions in binary form must reproduce the above copyright
#notice, this list of conditions and the following disclaimer in the
#documentation and/or other materials provided with the distribution.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
# ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
# FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
# DAMAGES (INCLUDING, BUT NOT LIMITED TO
Re: APM problem in 5.1-RELEASE
Jesse Guardiani wrote: > Jesse Guardiani wrote: > >> Jesse Guardiani wrote: >> >>> Darryl Okahata wrote: >>> >>>> Jesse Guardiani <[EMAIL PROTECTED]> wrote: >> >> [...] >> >>> Now, if I can just get that lousy CD-ROM to not crash my system on >>> resume I'll be a VERY happy man... I did some more testing on this last night, and it appears that the atacontrol detach method _does_ work, but only in specialized circumstances. I have modified my /etc/rc.suspend to call 'atacontrol detach 1' _before_ it calls 'apm -z'. I have also modified my /etc/rc.resume to call 'atacontrol attach 1' _after_ syncing the disks. If anyone wants to have a look at these files, just let me know. When it works: -- 1.) I have to be looking at a VTY, not X. (Geez. Just when I thought I got around this with the kernel option SC_NO_SUSPEND_VTYSWITCH...) 2.) The /dev/acd0 device has to be unused, otherwise the kernel panics. This means I have to stop playing any CDs and terminate the CD playing program. I assume this means that the device has to be _not_ open, but I haven't really performed much testing in this area. When it doesn't work: - 1.) If I try to suspend while looking at X, the kernel panics and auto- reboots. 2.) If I try to suspend while anything is accessing the acd0 device the kernel panics and auto-reboots. Those things aside, I can usually suspend my machine within 8 seconds, as long as the hard disk isn't under high load. And it comes back on-line in under 3 seconds. I've tested this 6 or 7 times in a row, swapping back and forth from X before doing the next suspend, so I'm pretty confident that it's reliable. A plus is that the little green "drive in use" light on the side of my Ultrabay goes off when the machine is in suspend mode, and since I call: atacontrol attach 1 Upon resume from suspend, I could very easily swap out my drives while in suspend mode. I've tested this. Pretty neat! Things I would like to improve upon: 1.) I need to find some way to automatically kill any processes that are using (or have opened) the /dev/acd0 device BEFORE executing apm -z from /etc/rc.suspend. If I can accomplish that, then I will have successfully eliminated the "stupid human" factor that sometimes causes me to forget I have a program running that uses the /dev/acd0 device. Does anyone have any ideas here? 2.) I'd love to automate (or do away with) the process of switching to a VTY from X before executing 'atacontrol detach 1'. Can anyone give me a _reason_ why I have to do that? It just seems odd to me. Thanks! -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: APM problem in 5.1-RELEASE
Jesse Guardiani wrote: > Jesse Guardiani wrote: > >> Darryl Okahata wrote: >> >>> Jesse Guardiani <[EMAIL PROTECTED]> wrote: > > [...] > >> Now, if I can just get that lousy CD-ROM to not crash my system on >> resume I'll be a VERY happy man... > > > Well, I'm getting a bit closer now. > > I rebooted and reinstalled the CD drive, then I executed: > > atacontrol detach 1 Nevermind. After detaching ata 1three times and reattaching it I was treated to an automatic reboot on the third detach... Perhaps this drive is buggy? Wish I had another DVD UltraBay 2000 drive to test with... -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: APM problem in 5.1-RELEASE
Jesse Guardiani wrote: > Darryl Okahata wrote: > >> Jesse Guardiani <[EMAIL PROTECTED]> wrote: [...] > Now, if I can just get that lousy CD-ROM to not crash my system on > resume I'll be a VERY happy man... Well, I'm getting a bit closer now. I rebooted and reinstalled the CD drive, then I executed: atacontrol detach 1 And suspended the system with Fn+F4. I then resumed the system and it came back on-line just fine. So I ran this: atacontrol attach 1 Which successfully reattached my CD drive. Here's the output I got from 'atacontrol attach 1': Jun 19 18:46:21 trevarthan kernel: stray irq 15 Jun 19 18:46:31 trevarthan kernel: ata1-slave: timeout waiting for interrupt Jun 19 18:46:31 trevarthan kernel: ata1-slave: ATAPI identify failed Jun 19 18:46:31 trevarthan kernel: acd0: DVD-ROM at ata1-master UDMA33 Does that 'stray irq 15' mean anything to anyone? I tried scripting this process from /etc/rc.suspend and /etc/rc.resume, but I was rewarded with an incomplete suspend and an automatic reboot... drat. At least I can suspend the laptop now with the CD drive in the bay. It's slow, but it's better than a reboot. I'm still hoping to iron this problem out 100% though. -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: APM problem in 5.1-RELEASE
Darryl Okahata wrote: > Jesse Guardiani <[EMAIL PROTECTED]> wrote: > >> 1.) When in X Windows (this never happened in Linux. What gives?) > > Another WAG: have you tried this kernel option?: > > options SC_NO_SUSPEND_VTYSWITCH > > It prevented X11 from crashing my A31 (but didn't help with the display > corruption). > Wo! It works! Hurray for FreeBSD! Now, if I can just get that lousy CD-ROM to not crash my system on resume I'll be a VERY happy man... BTW, what the heck does that option DO? -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: APM problem in 5.1-RELEASE
Darryl Okahata wrote: > Jesse Guardiani <[EMAIL PROTECTED]> wrote: [...] >Is there any way to disable the ata1-slave? BIOS? I looked. No BIOS config options for ATA devices whatsoever. This is probably because I'm using an IBM Thinkpad with an Ultrabay 2000 (containing a floppy drive currently) and an Ultrabay Plus (containing my CD-ROM drive). I would imagine that the IBM BIOS tells the ATA chipset what each drive is good for automatically. > Kernel setting??? > I hope so, but I haven't found one yet... Maybe it's a hw sysctl or something... -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: APM problem in 5.1-RELEASE
Tobias Roth wrote: > On Thu, Jun 19, 2003 at 08:23:09PM +0200, Sheldon Hearn wrote: >> On (2003/06/19 20:06), Tobias Roth wrote: >> >> > you compare a stable linux kernel branch with an unstable freebsd >> > branch. please make yourself familiar with freebsds (and possibly >> > linux') release process before you make statements like this. you will >> > only piss off the people that are trying to help you. >> >> While I understand the desire to "protect FreeBSD", I don't think you're >> being fair. >> >> Jesse was providing useful information, and drew logical conclusions >> from it. > > ok. i hereby apologize to Jesse. i didn't mean to sound too harsh. Don't sweat it. I understand. I like FreeBSD too. However, I'd like to note here that I HAVE tried APM support under 4.8-RELEASE on this laptop, and I couldn't even get 4.8 to detect APM in the BIOS at kernel boot. That may very well have been correctable with an obscure kernel option, but I doubt it. I'm pretty familiar with 4.8 as I run it on all of my servers. So, in short, I'm only running 5.1-RELEASE right now because 4.8 wouldn't detect APM at all... But I'm not here to gripe about it. I want to fix it. I want to make it better. I very strongly dislike giving Linux praise over FreeBSD. It's painful. :) So let's try to figure out why this CD-ROM keeps me from resuming after suspend, shall we? -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: APM problem in 5.1-RELEASE
Jesse Guardiani wrote: > Darryl Okahata wrote: > >> Jesse Guardiani <[EMAIL PROTECTED]> wrote: >> >>> Help! This APM BIOS suspends fine under Linux (2.4.18 >>> kernel)! I've tried everything I can think of to >>> get suspend working under 5.1-RELEASE! >> >> Wild-a** guess: >> >>> ata1-slave: timeout waiting for interrupt >>> ata1-slave: ATAPI identify failed >> >> I don't get this in my dmesg (and I have an A31, where apm seems to >> work). As you say it seems to be hanging during ATA reset, perhaps this >> has something to do with it? Is there any way to disable the >> ata1-slave? BIOS? Kernel setting??? > > I was actually wondering the same thing. I think the > next time I boot I'll try disabling ata1 altogether > with a hint and see if that works. > > I'll be looking for a setting to disable just the slave > in the meantime... OK. Here's an update. This is some funky junk: First off, I'd like to note, once again, that APM works PERFECTLY under Linux on this laptop with a 2.4.18 and 2.4.20 kernel. I could even suspend and resume from X Windows without problems. FreeBSD's APM code must not be as mature as Linux's, or Linux's APM code has patches applied to deal with my (possibly) quirky BIOS. As I said I would do in my last post, I tried to set: hint.ata.1.disabled="1" at the loader prompt to disable the second ATA channel (and my CDROM/DVD-ROM). This didn't work. The ata1 device was still detected and my laptop still froze on resume. But then I had a brilliant idea: Why not remove the CD-ROM drive from the bay? So I did. And Lo, it works! I have posted my APM resume log at the bottom of this message so everyone can see where my system normally freezes. #Further APM usage notes: (All notes are applicable _only_ with the CD-ROM/DVD-ROM REMOVED from the UltraBay Plus drive bay!) # --- # When suspend works # --- 1.) When logged into a VTY 2.) The _FIRST_ time I use 'zzz', but all further suspends lock the system. 3.) ANYTIME I use Fn+F4, as long as it isn't preceeded by a 'zzz' suspend AND I'm looking at a VTY (as opposed to X Windows). # - # When suspend locks my system # - 1.) When in X Windows (this never happened in Linux. What gives?) 2.) When I suspend using either Fn+F4 _OR_ 'zzz' after I have used 'zzz' once. (I think this may have something to do with the fact that 'zzz' doesn't sync the disks and pause before going into suspend, whereas Fn+F4 does.) I'm still very interested in getting suspend to work when my CD-ROM is installed. I can live with the other quirks, but I need my CD-ROM. Does anyone have any ideas? Does anyone know how to disable ata1-slave? (ata1-master is my CD-ROM. Please see previous posts for dmesg.) -- begin APM resume log -- fwohci0: fwohci_pci_suspend fwohci0: fwohci_pci_resume: power_state = 0x fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. fwohci0: Initiate bus reset ata0: resetting devices .. fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) done ata1: resetting devices .. >>>>>> This is where it freezes when my CD-ROM is installed <<<<<< done ums0: at uhub1 port 1 (addr 2) disconnected ums0: detached Jun 19 11:56:04 trevarthan kernel: wakeup from sleeping state (slept 00:00:12) Jun 19 11:56:04 trevarthan moused: unable to open /dev/ums0: No such file or dir ectory ums0: Logitech USB Receiver, rev 1.10/16.00, addr 2, iclass 3/1 ums0: 7 buttons and Z dir. -- end APM resume log -- Thanks! -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: APM problem in 5.1-RELEASE
Darryl Okahata wrote: > Jesse Guardiani <[EMAIL PROTECTED]> wrote: > >> Help! This APM BIOS suspends fine under Linux (2.4.18 >> kernel)! I've tried everything I can think of to >> get suspend working under 5.1-RELEASE! > > Wild-a** guess: > >> ata1-slave: timeout waiting for interrupt >> ata1-slave: ATAPI identify failed > > I don't get this in my dmesg (and I have an A31, where apm seems to > work). As you say it seems to be hanging during ATA reset, perhaps this > has something to do with it? Is there any way to disable the > ata1-slave? BIOS? Kernel setting??? I was actually wondering the same thing. I think the next time I boot I'll try disabling ata1 altogether with a hint and see if that works. I'll be looking for a setting to disable just the slave in the meantime... Thanks. -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
APM problem in 5.1-RELEASE
5 at device 31.5 on pci0 pcm0: pci0: at device 31.6 (no driver attached) eisa0: on motherboard eisa0: unknown card @[EMAIL PROTECTED] (0x0100) at slot 1 orm0: at iomem 0xe-0xe,0xdc000-0xd,0xd1000-0xd1fff,0xd-0xd0fff,0xc-0xc on isa0 pmtimer0 on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: at port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 pcic0 at port 0x3e0 iomem 0xa-0xa1fff irq 3 on isa0 pcic_attach: attach found no sockets device_probe_and_attach: pcic0 attach returned 6 ppc0: at port 0x3bc-0x3c3 irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: can't assign resources (port) unknown: can't assign resources (memory) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (irq) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) Timecounters tick every 10.000 msec fwohci0: BUS reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) ata1-slave: timeout waiting for interrupt ata1-slave: ATAPI identify failed ad0: 45780MB [93015/16/63] at ata0-master UDMA100 acd0: DVD-ROM at ata1-master PIO4 Mounting root from ufs:/dev/ad0s3a WARNING: / was not properly dismounted WARNING: /tmp was not properly dismounted WARNING: /usr was not properly dismounted /usr: mount pending error: blocks 16 files 1 WARNING: /var was not properly dismounted /var: mount pending error: blocks 68 files 13 -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ACPI mailling list?
Howdy list, Is there an ACPI mailling list I can join to help debug/test ACPI? I'm a decent C programmer, and I'd really like to get ACPI support working on my IBM Thinkpad A30p. Unfortunately, no-one has responded to my questions about ACPI on this laptop. Is anyone actively working on ACPI support? Thanks. -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: qmail uses 100% cpu after FreeBSD-5.0 to 5.1 upgrade
Thorsten Schroeder wrote: > Hi, > > On Mon, 16 Jun 2003, Don Lewis wrote: > >> > FreeBSD 5.1-CURRENT #1: Thu Jun 5 19:29:29 CEST 2003 >> > >> > fifo_vnops.c: >> > >> > $FreeBSD: src/sys/fs/fifofs/fifo_vnops.c,v 1.87 2003/06/01 06:24:32 >> > truckman Exp $ > >> Try upgrading to 1.88 and applying this patch: >> >> Index: sys/fs/fifofs/fifo_vnops.c >> === >> RCS file: /home/ncvs/src/sys/fs/fifofs/fifo_vnops.c,v >> retrieving revision 1.88 >> diff -u -r1.88 fifo_vnops.c >> --- sys/fs/fifofs/fifo_vnops.c 13 Jun 2003 06:58:11 - 1.88 >> +++ sys/fs/fifofs/fifo_vnops.c 16 Jun 2003 08:44:20 - > [...] > > Yes! This seems to work fine :) I run qmail on my 4.8 servers. For my sanity, is this a problem in 5.1-RELEASE, or in code after 5.1-RELEASE? We haven't upgraded to 5.1 yet (and don't intend to for a while), but I thought I'd ask since this bug would cripple our mail server. -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
