Re: 5.2-RELEASE TODO
Tom wrote: On Tue, 2 Dec 2003, Eric Anderson wrote: Tom wrote: Just to be complete, there are already a whole bunch of machines that will not boot 5.x, irregardless of the ACPI issues. I've never been able to boot 5.x with ACPI on or off, on any of the 5 Dell PowerEdge 6350 servers I have here, even though they run 4.9 perfectly. I have a PR open on it. So even without the ACPI issues on some hardware, there are still other reasons why 5.x is going to fail to boot. Are you using a PERC in those boxes? I've seen issues with PERC controllers on 5.1, but 4.8 worked fine. I received a patch, which fixed it, but it's a bit hard to install the os, and then rebuild world without rebooting the machine. :) Well, there are so many kinds of PERC cards. Some are just Mylex cards. Others are MegaRAID. I think they use some Adaptec now. My troubles were with the MegaRAID variant, I'm not sure about the others.. Either way, I tried booting the install CD with all cards disconnected, just to see if I could get the installer up to the main menu. No go. The display switches off as soon as sysinstall starts probing devices. It appears to panic, but the display is dead. Once I was able to use scrolllock at the critical moment just before the kernel starts sysinstall, and prevent the display from switch off, but when I release the scroll lock, I was at the DDB prompt. Not good. First - I hope you mean the cards are physically OUT of the machine - it seemed to me that if they had a logical disk configuration on the card, it would hang. Although, it sounds like your problem is different. Actually, it kind of sounds like it thinks you are doing the "-p" boot thing to check for keyboard and roll over to the serial port. Other than that, I'm out of ideas (doesn't take long for that to happen though!).. :( Eric -- ------ Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
EHCI problems - Revisited
Just curious who is working on the EHCI stuff? I am running -current as of today, and playing with EHCI support. I have a Sandisk 256mb USB 2.0 "Cruzer" memory stick, that doesn't quite work right with EHCI enabled. Here's my dmesg fragment: Dec 2 16:47:28 neutrino kernel: ehci0: mem 0xf4fffc00-0xf4ff irq 11 at device 29.7 on pci0 Dec 2 16:47:28 neutrino kernel: ehci0: (New EHCI DeviceId=0x24cd8086) Dec 2 16:47:28 neutrino kernel: ehci_pci_attach: companion usb0 Dec 2 16:47:28 neutrino kernel: ehci_pci_attach: companion usb1 Dec 2 16:47:28 neutrino kernel: ehci_pci_attach: companion usb2 Dec 2 16:47:28 neutrino kernel: usb3: EHCI version 1.0 Dec 2 16:47:28 neutrino kernel: usb3: companion controllers, 2 ports each: usb0 usb1 usb2 Dec 2 16:47:28 neutrino kernel: usb3: on ehci0 Dec 2 16:47:28 neutrino kernel: usb3: USB revision 2.0 Dec 2 16:47:28 neutrino kernel: uhub3: (0x8086) EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 Dec 2 16:47:28 neutrino kernel: uhub3: 6 ports with 6 removable, self powered and here's what happens when I plug in the memory stick: Dec 2 16:48:43 neutrino kernel: usb3: unrecoverable error, controller halted Dec 2 16:48:43 neutrino kernel: usb3: blocking intrs 0x10 Dec 2 16:49:08 neutrino kernel: usb3: port reset timeout Here are some lines from pciconf -l: [EMAIL PROTECTED]:29:0:class=0x0c0300 card=0x45418086 chip=0x24c28086 rev=0x01 hdr=0x00 [EMAIL PROTECTED]:29:1:class=0x0c0300 card=0x45418086 chip=0x24c48086 rev=0x01 hdr=0x00 [EMAIL PROTECTED]:29:2:class=0x0c0300 card=0x45418086 chip=0x24c78086 rev=0x01 hdr=0x00 [EMAIL PROTECTED]:29:7:class=0x0c0320 card=0x011d1028 chip=0x24cd8086 rev=0x01 hdr=0x00 I saw some threads from August or so, saying that Intel EHCI controllers are not supported yet, but not much else. Just wondering if there are some patches for me to try, or any testing I can help with. Eric -- ------ Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.2-RELEASE TODO
Tom wrote: Just to be complete, there are already a whole bunch of machines that will not boot 5.x, irregardless of the ACPI issues. I've never been able to boot 5.x with ACPI on or off, on any of the 5 Dell PowerEdge 6350 servers I have here, even though they run 4.9 perfectly. I have a PR open on it. So even without the ACPI issues on some hardware, there are still other reasons why 5.x is going to fail to boot. Are you using a PERC in those boxes? I've seen issues with PERC controllers on 5.1, but 4.8 worked fine. I received a patch, which fixed it, but it's a bit hard to install the os, and then rebuild world without rebooting the machine. :) Eric -- -- Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Periodic Scripts - Configuration problem?
Jonathan T. Sage wrote: [EMAIL PROTECTED] wrote: I recently change the hostname of my FreeBSD host to remove a hyphen from the name (i.e. skrap-node to skrapnode) Since then, all of the periodic output scripts send their mail output to [EMAIL PROTECTED] instead of [EMAIL PROTECTED] Only the mail delivery failures make it to my inbox. Mail works fine for all users, this just affects the periodic scripts. I have tried grep'ing for the incorrect hostname in the /etc/periodic/blah... But haven't found anything. the easiest thing to check right now is the output of "hostname". also, i *think* that the periodic scripts send mail to root (i.e., they don't add the domain), so perhaps sendmail is adding this? try: # sendmail -bv root if that is the case, check /etc/mail/sendmail.cf for the hardcoded hostname, or give sendmail a bit of -HUP (make restart in /etc/mail) Also, check /etc/mail/aliases, and /etc/hosts Eric -- ------ Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [Fwd: re: ath0 lost connection]
Eric Anderson wrote: [..snip..] ath_rate_ctl: 2M -> 1M (0 ok, 1 err, 1 retr) If you are down to 1M, I think you may need to check signal strength and such. I'd start with my testing near the AP (in sight of it at least). Ok - I don't usually talk to myself (not in public anyway) - but here are my findings. When in 11b mode, everything works fine (I didn't try going to the edge of my coverage area though - too comfortable on my couch). When in 11g mode, I see the rate flap up and down between 48M and 24M, and each time it switches, it loses some packets in between modes. I just now manually set my client (FreeBSD of course) to 36M, and it seems to be holding up for now. Here's all I did: ifconfig ath0 media OFDM/36Mbps mode 11g Give that a try on the FreeBSD AP, and see if that helps at all (you may want to try the 11b modes, like: ifconfig ath0 media DS/2Mbps mode 11b or something.. Eric -- -- Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [Fwd: re: ath0 lost connection]
Marcos Biscaysaqu wrote: After this I loss the connection and I have to restart the box: this is getting worse :( I haven't seen the debug mode kill my box, but anything can happen on -current :) ath_start: encapsulation failure ath_rate_ctl: 5M -> 2M (0 ok, 1 err, 1 retr) These ^^ are what I am talking about - I think when the signal is low or the connection is lossy (dropping packets or something) it auto drops the rate to a lower number (as it should) - and this is when you are seeing the delays, dropped packets, whatever. If you set the rate to a static number (say, 2M), then possibly it won't attempt any changes, and you can at least know what is causing the packet loss. [..snip..] ath_rate_ctl: 5M -> 11M (10 ok, 0 err, 0 retr) Now the signal got better, so it bumped it up to 11M.. ath_start: encapsulation failure I have no idea what that is trying to tell you .. (besides the obvious) ath_rate_ctl: 2M -> 1M (0 ok, 1 err, 1 retr) If you are down to 1M, I think you may need to check signal strength and such. I'd start with my testing near the AP (in sight of it at least). Eric -- ------ Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [Fwd: re: ath0 lost connection]
Marcos Biscaysaqu wrote: Hi Eric. I have no loss connection on 11b only on 11g, so for the moment im keep working with a Athreos Wireless card on hostap in 11b connecting 34 clients, and really is working VERY well until I have lot of Ierrs and Oerrs and the ping to the client go from 2 ms to 1000 ms and all work very slow until the errors go down and is fast again. I tried different AP and different wireless card and the Atheros wireless card even in 11b is faster than any comecial 11b AP, fixing the errors problem will be a very fast and strong AP. I wish to know fix it, but Im don't know how, Im only can help testing. :( Hmm - I wonder if you are losing packets when the device thinks the signal is weak, and it attempts to lower the connection speed to increase reliability. Maybe try forcing it down to a low speed (like 1mb/s or something?) and seeing if it continues to happen.. Maybe also try setting: sysctl hw.ath.debug=1 and watch your dmesg/messages for hints.. Eric Eric Anderson wrote: Marcos Biscaysaqu wrote: On a simpler yet related config, I have a linksys ag520 pci card running with a linksys a/b/g AP. IT occasionally just loses connectivity, but simply re-execing the ifconfig line brings it back. Haven't found a rhyme or reason yet. I'd send this to the FBSD list, but I just moved server IP blocks and the reverse DNS stuff hasn't propagated yet. I'm having the same problem - Sam knows about it (I've been annoying him for about a week and a half with info - sorry Sam!).. I think he may be working on it, but he may want more details from you. One question - does it drop when in A, B, and G modes? Or just one mode? It seemed to me that my connection was better when using 11b mode (to a B/G ap). Just curious. Also - is "shared" mode authentication ever going to work in FreeBSD? Does anyone know what the problem with it is? Eric -- ------ Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [Fwd: re: ath0 lost connection]
Marcos Biscaysaqu wrote: On a simpler yet related config, I have a linksys ag520 pci card running with a linksys a/b/g AP. IT occasionally just loses connectivity, but simply re-execing the ifconfig line brings it back. Haven't found a rhyme or reason yet. I'd send this to the FBSD list, but I just moved server IP blocks and the reverse DNS stuff hasn't propagated yet. I'm having the same problem - Sam knows about it (I've been annoying him for about a week and a half with info - sorry Sam!).. I think he may be working on it, but he may want more details from you. One question - does it drop when in A, B, and G modes? Or just one mode? It seemed to me that my connection was better when using 11b mode (to a B/G ap). Just curious. Also - is "shared" mode authentication ever going to work in FreeBSD? Does anyone know what the problem with it is? Eric -- -- Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: requesting vinum help
Could a vinum guru please contact me via email? I've lost 2 vinum volumes as a result of the latest fiasco and naturally am eager to figure out what's going on and recover the data. This isn't necessarily directed at you - I'm just using this email as a footstep to send this general comment - I am kind of under the assumption that -current is more of a test bed, and anything can happen at any time, which is why it's bad to run -current on a machine you care deeply about (at least its data). I think I've seen at least 5 mails in the past few weeks about people getting jammed into a corner with (what sounds like) production type boxes, or at least important boxes (or they wouldn't need a vinum?).. It seems odd to me that they wouldn't give it a whirl first before attempting to use it on a box they seem so protective of. Anyway, I'm just stating that running -current is for testing and developing, not really for production - at least I'm fairly certain. Feel free to delete this mail and ignore me.. Eric -- -- Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Cardbus cards break bge0
I recently cvsup'ed (last week anyway), and build/installed world/kernel etc. Now, when I connect a cardbus card (firewire cards, ethernet, wireless, etc), my broadcom bge0 interface goes crazy, stops functioning, and I get this: Nov 19 10:18:32 neutrino kernel: cardbus0: Resource not specified in CIS: id=10, size=1 Nov 19 10:18:32 neutrino kernel: bge1: mem 0xf601-0xf601 irq 11 at device 0.0 on cardbus0 Nov 19 10:18:32 neutrino kernel: bge1: RX CPU self-diagnostics failed! Nov 19 10:18:32 neutrino kernel: bge1: chip initialization failed Nov 19 10:18:32 neutrino kernel: device_probe_and_attach: bge1 attach returned 6 Nov 19 10:18:32 neutrino kernel: cbb0: CardBus card activation failed Nov 19 10:18:32 neutrino kernel: bge0: PHY read timed out Nov 19 10:18:48 neutrino last message repeated 85 times My gigabit ethernet (the broadcom) card device (which is onboard - this is a laptop) is bge0. Notice above it complains about bge1, then the "PHY read timed out" errors start. If I boot with the card installed, here's what I get: Nov 19 10:23:35 neutrino kernel: bge0: PHY read timed out Nov 19 10:23:35 neutrino last message repeated 9 times Nov 19 10:23:35 neutrino kernel: bge0: RX CPU self-diagnostics failed! Nov 19 10:23:35 neutrino kernel: bge0: flow-through queue init failed Nov 19 10:23:35 neutrino kernel: bge0: initialization failure Anyone have any ideas on what caused this breakage? Eric -- ------ Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em0 on install
Randy Bush wrote: trying to install using the 5.1-release mini cd and em0. it seems not to dhcp (looked with tcpdump) despite my saying Yes (and no to ipv6). am i missing a clue? Not plugged in to a Cisco switch, are you? gawd no! you would even suggest such a thing in public? sheesh! :-) I forgot to add the :) at the end.. it was meant as a joke.. :) -- -- Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em0 on install
Randy Bush wrote: trying to install using the 5.1-release mini cd and em0. it seems not to dhcp (looked with tcpdump) despite my saying Yes (and no to ipv6). am i missing a clue? Not plugged in to a Cisco switch, are you? -- -- Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: VMWare build failure
Scott Likens wrote: On Thu, 2003-11-20 at 12:38, Ben Paley wrote: Hello all. I think this is a -current issue. When I started using -current I began to get weird behaviour from vmware2: eventually every time I powered on the virtual machine the screen would freeze up so I couldn't get a console, and then the whole machine - the REAL machine, I mean - would reboot. Bit rubbish, huh? [snip] First off if you're running -CURRENT you want emulators/vmware3, missing header would conclude you don't have the header installed that it wants. Guessing you're running -CURRENT you have the kernel source installed, so my suggestion is to run vmware3. Unless you have a specific reason to run 2? Maybe he doesn't run 3 because it also doesn't build: /usr/ports/emulators/vmware3/work/vmware-distrib/vmmon-only/freebsd/driver.c:303:35: i386/isa/intr_machdep.h: No such file or directory /usr/ports/emulators/vmware3/work/vmware-distrib/vmmon-only/include/vm_asm.h: In function `Div643264': /usr/ports/emulators/vmware3/work/vmware-distrib/vmmon-only/include/vm_asm.h:1033: warning: use of memory input without lvalue in asm operand 4 is deprecated *** Error code 1 Stop in /usr/ports/emulators/vmware3/work/vmware-distrib/vmmon-only. *** Error code 1 Stop in /usr/ports/emulators/vmware3/work/vmware-distrib/vmmon-only. *** Error code 1 Stop in /usr/ports/emulators/vmware3/work/vmware-distrib. *** Error code 1 Stop in /usr/ports/emulators/vmware3. *** Error code 1 Stop in /usr/ports/emulators/vmware3. So same thing with vmware3 - note that the file (intr_machdep.h) doesn't exist in that location - but it does in other locations. I tried copying one of the others over to that spot, and rebuilding, but still fails (with new errors as expected).. :( Eric -- ------ Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: acpi_cpu_idle panic (Was: Re: kernel panic with todays source)
Nate Lawson wrote: On Tue, 18 Nov 2003, Eric Anderson wrote: Nate Lawson wrote: cvsup to -current as of today would be a good first start. The code was committed Nov 15. Then boot with acpi enabled and post the output of sysctl hw.acpi.cpu. You can try different levels by doing sysctl hw.acpi.cpu.cx_lowest=x where x is 0...(number_supported_states - 1) Thanks! I've rebuilt and am happy to say that nothing is hosed and I booted successfully :) Here's my sysctl output: $ sysctl hw.acpi.cpu hw.acpi.cpu.max_speed: 8 hw.acpi.cpu.current_speed: 4 hw.acpi.cpu.performance_speed: 8 hw.acpi.cpu.economy_speed: 4 You should run a benchmark with different values for hw.acpi.cpu.current_speed to be sure the throttling control still works ok. I left it mostly intact so you shouldn't see any problems but it's still good to test. As you change it, you should see dmesg output of "acpi_cpu0: set speed to xx%" I can change the hw.acpi.cpu.economy_speed value, but the current_speed is read only. When I set economy speed, it automatically bumps the current speed down to my economy value (as expected). However, no dmesg output. The only note I see is when going from AC to battery, I get: kernel: system power profile changed to 'economy' and of course going back to aAC shows 'performance' instead of economy. I never see any "set speed to xx%". hw.acpi.cpu.cx_supported: C1/1 C2/1 C3/85 C3/185 hw.acpi.cpu.cx_lowest: 0 hw.acpi.cpu.cx_history: 23589/0 0/0 0/0 0/0 I played with the different levels a bit, and can't tell much difference in them. Let me know what else I can try to break with this. Just for the info, I booted with a/c plugged in, but did the sysctl running on battery. You should set hw.acpi.cpu.cx_lowest to 1 regularly and 2 or 3 if you're using battery. This will save on heat. I'd also be interested in if you'd set it to 3 while on battery and run a typical workload for an hour and then send me the result of sysctl hw.acpi.cpu. The cx_history value helps me know if my scheduler is accurate. I'll try this tomorrow - anyway to get it to automatically set it to a value when going in to economy mode? Eric Anderson Systems Administrator Centaur Technology Say hi to Tom Crispin for me. :) He says "hi" :) (small world, eh?) On a side note - can I do anything with the "lid control switch" acpi piece? I'd like to make it turn off the screen and go into a sleep mode (it goes into sleep, but the screen stays lit up). Thanks for the great work! Eric -- -- Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
bge0 read timed out / cardbus activation
I recently cvsup'ed (yesterday, and again this morning), and build/installed world/kernel etc. Now, when I connect a cardbus card (in this case, it's a firewire card), my broadcom bge0 interface goes crazy, stops functioning, and I get this: Nov 19 10:18:32 neutrino kernel: cardbus0: Resource not specified in CIS: id=10, size=1 Nov 19 10:18:32 neutrino kernel: bge1: mem 0xf601-0xf601 irq 11 at device 0.0 on cardbus0 Nov 19 10:18:32 neutrino kernel: bge1: RX CPU self-diagnostics failed! Nov 19 10:18:32 neutrino kernel: bge1: chip initialization failed Nov 19 10:18:32 neutrino kernel: device_probe_and_attach: bge1 attach returned 6 Nov 19 10:18:32 neutrino kernel: cbb0: CardBus card activation failed Nov 19 10:18:32 neutrino kernel: bge0: PHY read timed out Nov 19 10:18:48 neutrino last message repeated 85 times My gigabit ethernet (the broadcom) card device (which is onboard - this is a laptop) is bge0. Notice above it complains about bge1, then the "PHY read timed out" errors start. If I boot with the card installed, here's what I get: Nov 19 10:23:35 neutrino kernel: bge0: PHY read timed out Nov 19 10:23:35 neutrino last message repeated 9 times Nov 19 10:23:35 neutrino kernel: bge0: RX CPU self-diagnostics failed! Nov 19 10:23:35 neutrino kernel: bge0: flow-through queue init failed Nov 19 10:23:35 neutrino kernel: bge0: initialization failure Anyone have any ideas on what caused this breakage? Eric -- ------ Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATAPI CD Changer problem in -CURRENT
Christian Laursen wrote: I just upgraded my workstation from 5.1-RELEASE to todays -CURRENT. When I boot it, I get the following messages about my CD drives: acd0-5: CDROM with 6 CD changer at ata1-master PIO4 acd6: DVDROM at ata1-slave PIO4 acd0-5: FAILURE - LOAD_UNLOAD status=51 sensekey=ILLEGAL REQUEST error=4 acd0-5: FAILURE - LOAD_UNLOAD status=51 sensekey=ILLEGAL REQUEST error=4 acd0-5: FAILURE - LOAD_UNLOAD status=51 sensekey=ILLEGAL REQUEST error=4 acd0-5: FAILURE - LOAD_UNLOAD status=51 sensekey=ILLEGAL REQUEST error=4 I get the 4 failures after the 2 first slots (both containing a CD) have been probed, and I guess there is an error for every empty slot. In 5.1-RELEASE the kernel didn't change through the drives while booting. It is a little annoying, but not my main concern. The real problem is, that only the first slot works. When I try to mount a cd from the second slot (acd1), I get this: borg# mount /drv/cd2 cd9660: /dev/acd1: Input/output error It doesn't make any difference whether acd0 is mounted or not. If you need further information about the problem, let me know. I'm seeing the same thing on my laptop with an internal DVDROM/CDRW drive. Never did that before (something changed since Nov 14th-ish). Eric -- -- Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: acpi_cpu_idle panic (Was: Re: kernel panic with todays source)
Nate Lawson wrote: Ok - what do I need to do to try this new acpi stuff out? I'm running -current as of Nov 14th, and I'd like to help debug/test this on my notebook.. cvsup to -current as of today would be a good first start. The code was committed Nov 15. Then boot with acpi enabled and post the output of sysctl hw.acpi.cpu. You can try different levels by doing sysctl hw.acpi.cpu.cx_lowest=x where x is 0...(number_supported_states - 1) Thanks! I've rebuilt and am happy to say that nothing is hosed and I booted successfully :) Here's my sysctl output: $ sysctl hw.acpi.cpu hw.acpi.cpu.max_speed: 8 hw.acpi.cpu.current_speed: 4 hw.acpi.cpu.performance_speed: 8 hw.acpi.cpu.economy_speed: 4 hw.acpi.cpu.cx_supported: C1/1 C2/1 C3/85 C3/185 hw.acpi.cpu.cx_lowest: 0 hw.acpi.cpu.cx_history: 23589/0 0/0 0/0 0/0 I played with the different levels a bit, and can't tell much difference in them. Let me know what else I can try to break with this. Just for the info, I booted with a/c plugged in, but did the sysctl running on battery. Thanks Nate for the hints.. Eric -- ------ Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: acpi_cpu_idle panic (Was: Re: kernel panic with todays source)
Harald Schmalzbauer wrote: On Tuesday 18 November 2003 18:58, you wrote: On Tue, 18 Nov 2003, Harald Schmalzbauer wrote: On Tuesday 18 November 2003 03:37, you wrote: Sorry I wasn't more clear. I need you to print the contents like this: print *cpu_cx_count cpu_cx_count 1 cpu_cx_lowest 0 cpu_idle_hook c0468300 cpu_cx_next 0 I hope these are the correct values. Thanks, those are the correct values for your box. I just posted a patch that should address the boot-time panic. Please revert old patches and try it. Yep, this looks good. Perhaps you're interested in the following line which arose for the first time during boot: C0? cx_next 0 cx_count 1 And here is what you requested in your first patch: cale:~> sysctl hw.acpi.cpu hw.acpi.cpu.cx_supported: C1/0 hw.acpi.cpu.cx_lowest: 0 hw.acpi.cpu.cx_history: 0/0 Ok - what do I need to do to try this new acpi stuff out? I'm running -current as of Nov 14th, and I'd like to help debug/test this on my notebook.. Eric -- -- Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unattended reboot was Re: signal 12's everywhere on Currentwith update this morning.
Sheldon Hearn wrote: On (2003/11/13 14:02), Eric Anderson wrote: I'm not having any luck - I'm started to feel like I'm missing something here :) I cvsup'd yesterday afternoon, and did my usual make buildworld, kernel, install kernel, single user mode, then make installworld - except it bombed on the installworld. I ignored the message moved on. You missed a step. The HEADS UP sent to -current said you needed to reboot between kernel install and world install. This is the strictly safe way of upgrading always. However, many people skip the reboot (and even the drop to single-user mode) as a shortcut. Sometimes, the shortcut works. This time, it doesn't. :-) Unfortunately, I had unsubscribed myself from the list a few weeks ago when I went to a Usenix conference, and forgot to resubscribe! Woops. All fixed up now though. At least now I know what I did wrong - thanks! Eric -- ------ Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unattended reboot was Re: signal 12's everywhere on Currentwith update this morning.
[EMAIL PROTECTED] wrote: Mensaje citado por Eric Anderson <[EMAIL PROTECTED]>: | I'm not having any luck - I'm started to feel like I'm missing something | here :) You're getting signal 11's. That could indicate memory problems. I get signal 12's with the changes to the statfs structure. I assume that you rebooted after the "bombed installworld", didn't you? If not that just might be the solution, if you did the problem could be else where. Thanks ed, but it isn't a memory problem.. After the bombed installworld, I rebooted, and it came up (running the kernel I built with the src that bombed), and now I'm in a corner - however Andy Farkas gave me a hint to put in an older kernel (maybe the one from 5.1-RELEASE?) and reboot using that kernel, then rebuild world and install world.. I think my world is older than my kernel.. Eric -- ------ Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unattended reboot was Re: signal 12's everywhere on Currentwith update this morning.
I'm not having any luck - I'm started to feel like I'm missing something here :) I cvsup'd yesterday afternoon, and did my usual make buildworld, kernel, install kernel, single user mode, then make installworld - except it bombed on the installworld. I ignored the message moved on. So, this morning, I cvsup'ed again, and started over. Here's what I get when doing a make buildworld: -- >>> stage 1.1: legacy release compatibility shims -- ===> tools/build /usr/obj/usr/src/i386/usr/src/tools/build created for /usr/src/tools/build cd /usr/src/tools/build; make buildincludes; make installincludes rm -f .depend mkdep -f .depend -a-I/usr/obj/usr/src/i386/legacy/usr/include /usr/src/tools/build/dummy.c cc -O -pipe -I/usr/obj/usr/src/i386/legacy/usr/include -c /usr/src/tools/build/dummy.c building static egacy library ranlib libegacy.a sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libegacy.a /usr/obj/usr/src/i386/legacy/usr/lib *** Signal 11 Stop in /usr/src/tools/build. *** Error code 1 Stop in /usr/src. *** Error code 1 I've tried rm'ing the /usr/obj subdirs, and even moving /usr/src out of the way and re cvsuping the whole tree, still no luck.. How am I being stupid here? Eric -- ------ Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atheron driver and netgear WG511T
hi, i get this when inserting my Netgear WG511T card into my laptop: ath0: mem 0x8801-0x8801 irq 11 at device 0.0 on cardbus0 ath0: unable to attach hardware; HAL status 13 device_probe_and_attach: ath0 attach returned 6 the ath manpage says that this chip should be supported... any ideas? Do you have the: device ath_hal line in your kernel config? Eric -- -- Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
MS Optical USB mouse flaky in -CURRENT
Ok, I've been using my M$ IntelliMouse (Optical USB) with FreeBSD for a while now. On several machines, with 4.8-RELEASE it works flawlessly, however under 5.1-RELEASE and 5-CURRENT, it randomly stops working. I can get it back working again by running "usbdevs", sometimes a few times, and the mouse will come back to life. Anyone have any ideas on this? What can I do to help debug this? Eric -- -- Eric Anderson Systems Administrator Centaur Technology All generalizations are false, including this one. -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: errors using wi driver in -CURRENT
I only seem to have problems when trying to connect to access points or devices with authmode set to shared, but when I set everything to OPEN, but still use a WEP key, I can make it work (as a client, not as an access point). I would agree something is seriously borked and really wish the authmode stuff would work. I'm willing to help in any way I can, but I'm not much of a C programmer or driver hacker to begin work on it myself.. Eric Soeren Schmidt wrote: It seems Bruce Cran wrote: Just to chime in here, I've spent 2 weeks of various trial and errors to get two Lucent Wavelan's (one 4.8, one -current) to talk to each other. Dispite my more or less futile experiments this would not work no matter what (even asking on -mobile and trying what came up there didn't help). Since I can use the cards perfectly between two 4.8 boxes (and have been for about 2 years), my take is that the wi driver in -current is borked useless, at least for some cards (It worked in 5.0 but broke on the way to 5.1 IIRC). just my .01 EUR... -- ------ Eric Anderson Systems Administrator Centaur Technology Attitudes are contagious, is yours worth catching? -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 'Hard error reading fsbn' in 5.1 but not 5.0?
Darren Pilgrim wrote: Just now, my 120GB western digital, immediately upon the mounting of all filesystems during startup, made a faint "click", then my screen filled with errors of the form: ad6: hard error reading fsbn -# of -#--# error=10 That's not an exact quote, of course, since the messages scrolled by so fast I couldn't actually read parts of them. Those # signs are in place of large numbers (most were 12-18 digits). This was in 5.1-R, fresh install, in the first 15G of the disk, just after having booted into DOS to create some DOS partitions after the FreeBSD slice. I booted back into 5.0, and am presently writing across the entire disk with this command: fdisk -I /dev/ad6 && dd if=/dev/zero of=/dev/ad6s1 bs=1m At more than 33 minutes into it at 24+MB/sec, there have been no such errors and the portion of the disk that was being mounted has already been covered by zeros. Darren - I've seen this before (actually, on western digital drives) a few times, and I'll tell you it's never good. Each time, I thought "maybe it's a bug somewhere in the OS" because I could rebuild the OS on the drive, and the error would seem to disappear - for awhile. Then the drive would get worse, and rapidly deteriorate into a door stop. I'm not sure if it's software or not, but I would double check your backups and start making plans to swap the drive. Eric -- ------ Eric Anderson Systems Administrator Centaur Technology Attitudes are contagious, is yours worth catching? -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
