Re: no internet after build world-kern install
ok i finley got this all fix now im going to post in what i did so that its in the archives so if any one has this issue/problem maby itll help them out what i did was edit /boot/device.hints then i added hint.acpi.0.disabled=1 saved then rebooted and vwalol it worked i had internet access back once agin - Original Message - From: whitevamp [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, December 08, 2004 7:56 PM Subject: Re: no internet after build world-kern install ok i still havent got this resolved yet , heres an up date of things i have tryed to no avail , swaped out eth cards, swaped out cables, hooked up the box straight upto the dsl modem, looked around on the box to see if a firewall was getting started some ware and couldnt find one . so heres a recap of whats going on. cant ping any thing out side the box weather it be domain name or numeric ip address can ping localhost , 127.0.0.1 netstat -rn shows correct settings ( or i think) output is destiongatway netif default65.102.x.x( my dsl modem ip )xl0 65.102.x.x/x( reserverd ip )link#1 xl0 65.102.x.x( my ip ) xl0 (address) lo0 65.102.x.x( my dslmodem ip )link#1 xl0 127.0.0.1127.0.0.1 lo0 NOTE: i do have 2 netcards in this box the second card is not assigned an ip address --- Original Message - From: whitevamp [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, December 08, 2004 1:00 PM Subject: no internet after build world-kern install I have done a buildworld from 4.9 to 5.3 and also installed a new custom kernel and after all whent ok i rebooted the box and goto ping yahoo.com and i cant get out , and i also tryed pinging my outhere ip address and nothing on eathere one it just say destination unreachable. so i whent back and rebuilt a new kern with all defaults execpt i added options IPFIREWALL_DEFAULT_TO_ACCEPT and i still cant ping out . i have checked to see if the net card was up , if i do a ifconfig it shows it as active there, i have whent into rc.conf and removed out my firewal script that i did have running , still nuthilg, and durring boot its showing my net card there so what would be causeing this? if you need more info just let me know ohh and yea i do have a ip assigned to my net card IE:65.102.x.x and thanks inadvance for any help that you can give me on this. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re[2]: no internet after build world-kern install
You could probably send an excerpt of dmesg regarding your NICs also. Since this is not a common problem the proper drivers can be kinda broken basically. Say, I didn't experience any problems upgrading from 4.10 to 5.3 with fxp. ok i finley got this all fix now im going to post in what i did so that its in the archives so if any one has this issue/problem maby itll help them out what i did was edit /boot/device.hints then i added hint.acpi.0.disabled=1 saved then rebooted and vwalol it worked i had internet access back once agin - Original Message - From: whitevamp [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, December 08, 2004 7:56 PM Subject: Re: no internet after build world-kern install ok i still havent got this resolved yet , heres an up date of things i have tryed to no avail , swaped out eth cards, swaped out cables, hooked up the box straight upto the dsl modem, looked around on the box to see if a firewall was getting started some ware and couldnt find one . so heres a recap of whats going on. cant ping any thing out side the box weather it be domain name or numeric ip address can ping localhost , 127.0.0.1 netstat -rn shows correct settings ( or i think) output is destiongatway netif default65.102.x.x( my dsl modem ip )xl0 65.102.x.x/x( reserverd ip )link#1 xl0 65.102.x.x( my ip ) xl0 (address) lo0 65.102.x.x( my dslmodem ip )link#1 xl0 127.0.0.1127.0.0.1 lo0 NOTE: i do have 2 netcards in this box the second card is not assigned an ip address --- Original Message - From: whitevamp [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, December 08, 2004 1:00 PM Subject: no internet after build world-kern install I have done a buildworld from 4.9 to 5.3 and also installed a new custom kernel and after all whent ok i rebooted the box and goto ping yahoo.com and i cant get out , and i also tryed pinging my outhere ip address and nothing on eathere one it just say destination unreachable. so i whent back and rebuilt a new kern with all defaults execpt i added options IPFIREWALL_DEFAULT_TO_ACCEPT and i still cant ping out . i have checked to see if the net card was up , if i do a ifconfig it shows it as active there, i have whent into rc.conf and removed out my firewal script that i did have running , still nuthilg, and durring boot its showing my net card there so what would be causeing this? if you need more info just let me know ohh and yea i do have a ip assigned to my net card IE:65.102.x.x and thanks inadvance for any help that you can give me on this. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hw.ata.ata_dma=0: can I do this during bootup at the loader prompt?
On Thu, 09 Dec 2004 14:24:35 +0900, Rob [EMAIL PROTECTED] wrote: Hi, In /boot/loader.conf, I have hw.ata.ata_dma=0 to prevent a WRITE_DMA failure crash at bootup. Unfortunately, this forces my UDMA100 harddisk to operate at PIO4 speed. There are patches flying around on this mailing list that might solve the problem. I'm very keen on testing such patches, but I should remove the line in loader.conf. However, if the patch does not work, I end up with an unbootable disk. It would be nice if I can set hw.ata.ata_dma=0 at the loader prompt during bootup, so that the system at least will boot from harddisk. Is that possible? I'm not sure if I understand what you want, but you can use eg 'atacontrol mode channel udma33 udma33' to set your hard drive to UDMA-33 after the system has booted. Arjan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem booting a Compaq Proliant 1600.
I've tried researching this on google and playing around with various things myself to no avail. I should probably submit this as a bug report, but I'm not sure it is... I have a Compaq Proliant 1600 server. It's a large box with four SCSI disks, and (I believe) three controllers. It's a beast. It's currently running 4.3-STABLE quite nicely, but I've been trying to upgrade it to 4.9, 4.10 or 5.3 to no avail. I've tried from CDs and from source. The problem is that when I boot the new kernel, everything looks OK (it's hard to see the dmesg before it scrolls off during boot). However, when it gets to the Waiting 15 seconds for SCSI devices to settle, it then prompts me for the name of the root filesystem device. Usually, all my disks are mounted under sym0, sym1 or sym2. I see all three devices during the boot but they're not available when I hit '?' in the menu that asks the name of the root FS device. When I boot the 4.3-STABLE kernel, I get the following (normal) operation: Mounting root from ufs:da0s1a da0 at sym0 bus 0 target 0 lun 0 da0: COMPAQ HB00931B93 A195 Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled da0: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) and so on. As a minor quibble, I need to type '2:da(0,a)' at the boot prompt due to some confusion between what the BIOS thinks is device0 and what the kernel thinks is device0 but that's not a big deal, it just prevents auto-booting. Not sure if that makes any difference. Does anyone have any ideas? - Der -- Dermot Tynan Kalopa Media Limited http://www.kalopa.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hw.ata.ata_dma=0: can I do this during bootup at the loader prompt?
Arjan Van Leeuwen wrote: On Thu, 09 Dec 2004 14:24:35 +0900, Rob [EMAIL PROTECTED] wrote: Hi, In /boot/loader.conf, I have hw.ata.ata_dma=0 to prevent a WRITE_DMA failure crash at bootup. Unfortunately, this forces my UDMA100 harddisk to operate at PIO4 speed. There are patches flying around on this mailing list that might solve the problem. I'm very keen on testing such patches, but I should remove the line in loader.conf. However, if the patch does not work, I end up with an unbootable disk. It would be nice if I can set hw.ata.ata_dma=0 at the loader prompt during bootup, so that the system at least will boot from harddisk. Is that possible? I'm not sure if I understand what you want, but you can use eg 'atacontrol mode channel udma33 udma33' to set your hard drive to UDMA-33 after the system has booted. No, that's no option. The situation is this: I have a harddisk with FreeBSD 5.3, which fails to boot. It would boot if I had hw.ata.ata_dma=0 in /boot/loader.conf; however, that file is empty, so the bootup crashes with a WRITE_DMA failure when the kernel loads. I can get at the bootloader prompt during the boot. What I want to know is: can I type something here that has the same effect as hw.ata.ata_dma=0 in /boot/loader.conf? Then I can continue loading the kernel. Thanks, Rob. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hw.ata.ata_dma=0: can I do this during bootup at the loader prompt?
On Thu, 09 Dec 2004 21:04:19 +0900, Rob [EMAIL PROTECTED] wrote: Arjan Van Leeuwen wrote: On Thu, 09 Dec 2004 14:24:35 +0900, Rob [EMAIL PROTECTED] wrote: Hi, In /boot/loader.conf, I have hw.ata.ata_dma=0 to prevent a WRITE_DMA failure crash at bootup. Unfortunately, this forces my UDMA100 harddisk to operate at PIO4 speed. There are patches flying around on this mailing list that might solve the problem. I'm very keen on testing such patches, but I should remove the line in loader.conf. However, if the patch does not work, I end up with an unbootable disk. It would be nice if I can set hw.ata.ata_dma=0 at the loader prompt during bootup, so that the system at least will boot from harddisk. Is that possible? I'm not sure if I understand what you want, but you can use eg 'atacontrol mode channel udma33 udma33' to set your hard drive to UDMA-33 after the system has booted. No, that's no option. The situation is this: I have a harddisk with FreeBSD 5.3, which fails to boot. It would boot if I had hw.ata.ata_dma=0 in /boot/loader.conf; however, that file is empty, so the bootup crashes with a WRITE_DMA failure when the kernel loads. I can get at the bootloader prompt during the boot. What I want to know is: can I type something here that has the same effect as hw.ata.ata_dma=0 in /boot/loader.conf? Then I can continue loading the kernel. Ah, ok, now I understand. set hw.ata.ata_dma=0 boot Arjan Thanks, Rob. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [TEST] ng_bridge ng_l2tp ng_lmi
The list of untested nodes has been narrowed down to the following three: ng_bridge, ng_l2tp, ng_lmi Please, if you use one of these three test this patch: http://people.freebsd.org/~glebius/totest/netgraph_callout T On Thu, Dec 02, 2004 at 06:10:48PM +0300, Gleb Smirnoff wrote: T T Dear collegues, T T T T we are working on making netgraph ISR mpsafe. To do it we need to T T fix all (ab)users of bare timeout(9) in src/sys/netgraph. These T T timeout calls are running in synch with netgraph now because timeout(9) T T is Giant-locked. As soon as we mark ISR mpsafe, they are going to break. T T T T This patch semi-mechanically changes all timeout(9) calls to ng_callout(9), T T which runs scheduled callouts in netgraph context: T T T T http://people.freebsd.org/~glebius/totest/netgraph_callout T T T T It can be applied to HEAD or RELENG_5 (not 5.3-RELEASE). It patches T T the following nodes: T T T T ng_bridge.c T T ng_l2tp.c T T ng_lmi.c T T ng_ppp.c T T ng_pppoe.c T T ng_tty.c T T T T If you are using at least one of them, then I'm asking you to test the T T patch and respond. Thanks in advance! T T T T P.S. Sorry for crossposting. The target users are both RELENG_5 and CURRENT. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hw.ata.ata_dma=0: can I do this during bootup at the loader prompt?
Rob wrote: Hi, In /boot/loader.conf, I have hw.ata.ata_dma=0 to prevent a WRITE_DMA failure crash at bootup. Unfortunately, this forces my UDMA100 harddisk to operate at PIO4 speed. There are patches flying around on this mailing list that might solve the problem. I'm very keen on testing such patches, but I should remove the line in loader.conf. However, if the patch does not work, I end up with an unbootable disk. It would be nice if I can set hw.ata.ata_dma=0 at the loader prompt during bootup, so that the system at least will boot from harddisk. Is that possible? Yes, that's possible. Drop the loader to the prompt and do the following: set hw.ata.ata_dma=0 boot Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Installation attempt results in shutdown
Hello! I am trying to install FreeBSD on my laptop (HP/Compaq nx9105), but as soon as I choose an alternative on the first menu that appears my computer shuts down. It happened both with 5.1 and 5.2.1, and it happens no matter which alternative I choose. I really have no clue what to do. I have tried asking around, but most people told me to send a mail to this adress, so I would be really happy if you have an answer for me :) Thanks in advance /David ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installation attempt results in shutdown
Btw, the most recent *stable* release is 5.3. You'd better use this one. What do you mean an alternative on the first menu? Please choose the stage you experience shutdown in from the following link: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-start.html Hello! I am trying to install FreeBSD on my laptop (HP/Compaq nx9105), but as soon as I choose an alternative on the first menu that appears my computer shuts down. It happened both with 5.1 and 5.2.1, and it happens no matter which alternative I choose. I really have no clue what to do. I have tried asking around, but most people told me to send a mail to this adress, so I would be really happy if you have an answer for me :) Thanks in advance /David ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
is it possible to mount a vinum-fs on 2 hosts?
Hello, i have a little problem. I hav Host A andHost B both are connected to an SAN through an QLA2200 Fibre-Channel (man isp). On the SAN are 14 Disks da0-da13 these Disks are configured w/ vinum to an RAID 10 Filesystem. Now i have the Problem i would make Host A to an PDC and HOST B to an BDC. To be redundant in an fail of the PDC (Host A) i would have access to the SAN from BDC (Host B). Now i Know the Problem of an already mounted Filesystem. I would mount the Filesystem on both Hosts, may i cannot update the Filesystemdescriptors from Host A on Host B. Give it an option or knob for these problematic situation, or must i junk through the Shell-Scripting-Hell with ping/pong...;-) Can anyone help me? Tahnks for your interrest an Help. Greetings Michael ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
5.3 SMP kernels now available via FreeBSD Update
In response to popular demand, I am now providing both GENERIC and SMP kernels via FreeBSD Update to people running FreeBSD 5.3. To take advantage of this on your FreeBSD 5.3 (and only 5.3!) SMP system, run the following commands as root: # touch /boot/kernel/SMP # freebsd-update fetch (this should mention downloading a new /boot/kernel/SMP file) # freebsd-update install (likewise, this should mention installing /boot/kernel/SMP) # echo 'bootfile=SMP' /boot/loader.conf and reboot. You should now find that `uname -ri` outputs 5.3-SECURITY SMP. Note again that this does not apply to any FreeBSD releases other than 5.3. Colin Percival ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hw.ata.ata_dma=0: can I do this during bootup at the loader prompt?
* Scott Long [EMAIL PROTECTED] [041209 15:59]: Hello, It would be nice if I can set hw.ata.ata_dma=0 at the loader prompt during bootup, so that the system at least will boot from harddisk. Is that possible? Yes, that's possible. Drop the loader to the prompt and do the following: set hw.ata.ata_dma=0 boot btw: I have a similar problems, but not with the boot disc, but one of my data drives, thus I want ata_dma enabled for the other discs. I have to dispatch a atacontrol mode 1 foo UDMA33 to set this drive (slave on second controller) to UDMA33 (otherwise it would use UDMA100). But I have to do it before /etc/rc.d/fsck starts accessing the device. Right now I've added above line to the beginning of aforesaid script. Is there a nicer/better place to tell the kernel (don't like editing the rc-scripts). Best regards Christian -- http://www.lackas.net/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: misc/74786: Smartlink Modem causes interrupt storm on RELENG_4 and RELENG_5
[cc'ing to FreeBSD-Stable] Hi, I know that the proposed patches I submitted are not the best patches, but given that the next release of RELENG_4 is coming out, would it not be better to commit those to RELENG_4 as they allow the modem to work when it shares an interrupt with another device ? The sio and interrupt handling code in RELENG_5 is different enough that I doubt the patches you are proposing would make it back to RELENG_4. This at least lets the modem work and prevents the machine from locking up in an interrupt storm on RELENG_4 without breaking any functionality (as far as I know). ---Mike At 02:22 AM 08/12/2004, Bruce Evans wrote: I think I understand this now. sio can indeed drive the interrupt (after you open an sio device, but not immediately at the end of the attach except in the serial console case). The main bugs are: 1. sio asks for exclusive access to the interrupt for no good reason (some buses like isa might only support exclusive accesses, but sio doesn't care). uhci gets access first in your configuration, so allocation of the interrupt resource fails. 2. Error handling for the failure in (1) is null, so both devices are successfully attached. 3. sio sets a flag to tell it to use polling if there is no interrupt resource, but it doesn't set the flag if the interrupt resource couldn't be allocated or if the interrupt couldn't be set up. 4. Upper layers provide negative help for debugging (3) using their own version of (3). They print irq N in boot messages if an interrupt resource justs exists. This doesn't mean that the device is using it. 5. Device interrupts are still enabled in polling mode. This depends on nothing else sucessfully setting up the (shared) interrupt. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
3.5 ISO-Image for download
Hello, does anyone know a source, where I can download a 3.5(1)-RELEASE ISO-Image? Kind regards, Thomas. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3.5 ISO-Image for download
On Thu, Dec 09, 2004 at 08:30:39PM +0100, Thoamas Krause -CI- wrote: does anyone know a source, where I can download a 3.5(1)-RELEASE ISO-Image? ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases/i386/ -- Ken Smith - From there to here, from here to | [EMAIL PROTECTED] there, funny things are everywhere. | - Theodore Geisel | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DMA errors with SATA on 5.x [one fix]/ SATA DVD+RW
Søren Schmidt wrote: Garance A Drosihn wrote: At 1:01 AM -0600 12/7/04, Tim Welch wrote: I'm getting NID not found/DMA errors on 5-STABLE with a Seagate 200gb sata drive: ad2: FAILURE - WRITE_DMA status=51READY,DSC,ERROR error=10NID_NOT_FOUND LBA=268435455 This appears to be a result of 48-bit addressing. Any time a write is attempted to the sector above, I get multiple messages like this. It continues until I shut down. After a bit of googling I found this post: http://lists.freebsd.org/pipermail/freebsd-hackers/2004-October/008821.html and applied the change suggested. It seems to have fixed the problem, and I've had no troubles from this since Nov. 18th when I applied that patch. I'm running an Intel 875PBZ board with the ich5 controller. The drive in question is a Seagate ST3200822AS/3.01 (as reported by dmesg). So the question is, will this patch be committed anytime soon? That looks like a pretty safe patch to make. The message says he just reduced the 48-bit trigger level by one: Yes, I suggested that way back on the lists, and it seems to help those that had this problem. I have had it for quite some time in ATA-mkIII here as well, and since it has no real impact otherwise I've committed it to -current... Hi guys, This is the first post I have seen on stable about SATA. (ok, maybe I'm not subscribed to the right lists) Anyway I bought a brand new beautiful Plextor DVD+RW SATA drive (PX712SA) for use on my AMD64+3800 machine. Win XP64-beta won't recognize it, and neither will FreeBSD 5.3-RELEASE, AMD64. I am wondering what I am doing wrong? If you are willing to help just email me and I can send dmesg and/or kernel config file to you and keep it off the list. I am using the socket 939 chip on an Abit AV8 mobo. Only one of the two SATA channels is used. I have two SCSI 160 drives, one for Windoze and one for FBSD. So the only thing normal IDE is used for is the floppy drive. Thanks if you can help, Rob. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DMA errors with SATA on 5.x [one fix]/ SATA DVD+RW
Rob wrote: Hi guys, This is the first post I have seen on stable about SATA. (ok, maybe I'm not subscribed to the right lists) Anyway I bought a brand new beautiful Plextor DVD+RW SATA drive (PX712SA) for use on my AMD64+3800 machine. Win XP64-beta won't recognize it, and neither will FreeBSD 5.3-RELEASE, AMD64. I am wondering what I am doing wrong? If you are willing to help just email me and I can send dmesg and/or kernel config file to you and keep it off the list. I am using the socket 939 chip on an Abit AV8 mobo. Only one of the two SATA channels is used. I have two SCSI 160 drives, one for Windoze and one for FBSD. So the only thing normal IDE is used for is the floppy drive. SATA ATAPI devices are not supported yet. There are a few gotcha's though. Not all SATA controllers does support SATA ATAPI even if out driver would, so its a mixed blessing for now. Anyhow, as soon as I can get my hands on a SATA ATAPI device, be certain that I'll get support in there, for those controllers that support it that is. However SATA ATAPI devices are still extremely rare, at least in this part of the woods... -- -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
pf-related panic in rn_walktree? in 5.3-RELEASE
Hey,
I'm seeing a semi-reproducable panic with pfctl in 5.3-RELEASE. The
machine is an IPv6 router/firewall, the pf firewall includes rules for
both ipv4 and ipv6. Sadly, the machine is not running with a debug
kernel, but I do have dumps of the panics. It's a single processor
machine with one fxp card and one xl card. IPv4 is only on the xl card,
ipv6 is also native on the xl card and is on a vlan(4) on the fxp card.
I've actually had three panics with this machine today, the latter two of
which were while running pfctl, and the first was when running sysctl -a
(which I guess also looks at pf-related values). I only have dumps of the
two pfctl panics, but I'm not sure the dumps can yield any secrets as in
both cases the stacks seem to have been smashed. However, it does seem
that both panics occured in rn_walktree.
First panic:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x8
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc067ec6a
stack pointer = 0x10:0xc8856820
frame pointer = 0x10:0xc885682c
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 = 1060 (pfctl)
trap number = 12
panic: page fault
Uptime: 2h48m2s
Dumping 128 MB
16 32 48 64 80 96 112
(kgdb) bt
#0 0xc060bc12 in doadump ()
#1 0xc060c1e5 in boot ()
#2 0xc060c4a1 in panic ()
#3 0xc07b6060 in trap_fatal ()
#4 0xc07b5dcb in trap_pfault ()
#5 0xc07b5a0d in trap ()
#6 0xc07a5a9a in calltrap ()
#7 0xc0670018 in if_attachdomain1 ()
#8 0xc15bc90f in ?? ()
#9 0xc159a300 in ?? ()
#10 0xc15bcfe0 in ?? ()
#11 0xc8856840 in ?? ()
#12 0x in ?? ()
#13 0x in ?? ()
#14 0x in ?? ()
#15 0x in ?? ()
#16 0xc15e44d8 in ?? ()
#17 0xc15e44d8 in ?? ()
(etc etc - another 40 ?? lines not inside fucntions)
see below 2nd packet for more info on this panic.
Second panic:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xc13f53
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc067ec6a
stack pointer = 0x10:0xc8842818
frame pointer = 0x10:0xc8842824
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 = 564 (pfctl)
trap number = 12
panic: page fault
Uptime: 9m54s
Dumping 128 MB
16 32 48 64 80 96 112
(kgdb) bt
#0 0xc060bc12 in doadump ()
#1 0xc060c1e5 in boot ()
#2 0xc060c4a1 in panic ()
#3 0xc07b6060 in trap_fatal ()
#4 0xc07b5dcb in trap_pfault ()
#5 0xc07b5a0d in trap ()
#6 0xc07a5a9a in calltrap ()
#7 0x0018 in ?? ()
#8 0x0010 in ?? ()
#9 0xc1750010 in ?? ()
#10 0xc8842838 in ?? ()
#11 0xc16091f0 in ?? ()
#12 0xc8842824 in ?? ()
#13 0xc8842804 in ?? ()
#14 0xc1594734 in ?? ()
#15 0x00c13f4b in ?? ()
#16 0xc159475d in ?? ()
#17 0xc159475d in ?? ()
#18 0x000c in ?? ()
#19 0x in ?? ()
#20 0xc067ec6a in rn_walktree ()
#21 0xc15cd890 in ?? ()
#22 0xc1594700 in ?? ()
#23 0xc15cdfe0 in ?? ()
#24 0xc8842838 in ?? ()
#25 0x0002 in ?? ()
#26 0xc884286c in ?? ()
#27 0x0006 in ?? ()
#28 0x in ?? ()
(etc etc - another 60 lines not inside functions)
In both cases the panic was caused at instruction pointer 0xc067ec6a,
which seems to be line 1069 in rn_walktree (i'll spare you the
disassembly, just trust me :)
1062 for (;;) {
1063 base = rn;
1064 /* If at right child go back up, otherwise, go right */
1065 while (rn-rn_parent-rn_right == rn
1066 (rn-rn_flags RNF_ROOT) == 0)
1067 rn = rn-rn_parent;
1068 /* Find the next *leaf* since next node might vanish,
too */
1069 ---for (rn = rn-rn_parent-rn_right; rn-rn_bit = 0;)
1070 rn = rn-rn_left;
1071 next = rn;
1072 /* Process leaves */
1073 while ((rn = base)) {
1074 base = rn-rn_dupedkey;
1075 if (!(rn-rn_flags RNF_ROOT)
1076 (error = (*f)(rn, w)))
1077 return (error);
1078 }
1079 rn = next;
1080 if (rn-rn_flags RNF_ROOT)
1081 return (0);
1082 }
(specifically, it's the read of rn-rn_bit that triggers the panic)
And at this point I can't really investigate this further. I guess the
radix tree is corrupt, but I suspect it's going to be hard to establish
what events actually happened leading up to the panic.
I'm relatively happy that the hardware is OK, it's been running linux for
over
Re: DMA errors with SATA on 5.x [one fix]/ SATA DVD+RW
Sren Schmidt [EMAIL PROTECTED] probably said: SATA ATAPI devices are not supported yet. There are a few gotcha's though. Not all SATA controllers does support SATA ATAPI even if out driver would, so its a mixed blessing for now. Anyhow, as soon as I can get my hands on a SATA ATAPI device, be certain that I'll get support in there If it's something you'd like to work on I'd happily put some money towards sending a drive in your direction... P. -- pir ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DMA errors with SATA on 5.x [one fix]/ SATA DVD+RW
Peter Radcliffe wrote: Sren Schmidt [EMAIL PROTECTED] probably said: SATA ATAPI devices are not supported yet. There are a few gotcha's though. Not all SATA controllers does support SATA ATAPI even if out driver would, so its a mixed blessing for now. Anyhow, as soon as I can get my hands on a SATA ATAPI device, be certain that I'll get support in there If it's something you'd like to work on I'd happily put some money towards sending a drive in your direction... P. Same here, I could remove it and ship it to you today, probably 2nd day air, or one of the cheaper but fast services. If P, however, doesn't have to tear his computer all apart LOL, maybe that might be a better solution for me. Sincerely, Rob. ps. I just found a disk that shipped with the mobo. I thought it was a SATA raid driver, but it looks from the title SATA Driver Disk that it might be more generic. At least I might be able to get Windoze working with this drive. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DMA errors with SATA on 5.x [one fix]/ SATA DVD+RW
Rob [EMAIL PROTECTED] probably said: Same here, I could remove it and ship it to you today, probably 2nd day air, or one of the cheaper but fast services. If P, however, doesn't have to tear his computer all apart LOL, maybe that might be a better solution for me. I was more suggesting buying one and having it directly shipped... The support would likely be useful to me in the medium term so if I can contribute towards helping that happen I would. P. -- pir ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: crashdumps not working
On Wed, 8 Dec 2004, Michael Nottebrock wrote: I.e., do the individual elements work from the debugger. If they do, then we can try the same from entering the debugger following the panic, and see how things differ. All of the above works when entering the debugger from the watchdog timeout, too. :-\ So it's basically sounding like it's really something about the call to panic() in the non-debugger scenario. I'm off on vacation for a week or so, but once I get back I'll be happy to take a further look if no one else has gotten to it by then. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Principal Research Scientist, McAfee Research ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DMA errors with SATA on 5.x [one fix]/ SATA DVD+RW
Peter Radcliffe wrote: Sren Schmidt [EMAIL PROTECTED] probably said: SATA ATAPI devices are not supported yet. There are a few gotcha's though. Not all SATA controllers does support SATA ATAPI even if out driver would, so its a mixed blessing for now. Anyhow, as soon as I can get my hands on a SATA ATAPI device, be certain that I'll get support in there If it's something you'd like to work on I'd happily put some money towards sending a drive in your direction... I'm going to work on it soon thats for sure, however I have lots on the burner currently so its no rush. However all kinds of (S)ATA/ATAPI gear is always most welcome here in the lab, the levels of support I can provide is directly proportional to the amount of HW I have access to :) -- -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DMA errors with SATA on 5.x [one fix]/ SATA DVD+RW
At 9:49 PM +0100 12/9/04, Søren Schmidt wrote: I'm going to work on it soon thats for sure, however I have lots on the burner currently so its no rush. However all kinds of (S)ATA/ATAPI gear is always most welcome here in the lab, the levels of support I can provide is directly proportional to the amount of HW I have access to :) I am not great at mailing things. My sister is still waiting for me to mail her christmas presents for *last* year... Do you have a paypal account? I could send some money that way, and then you could get whatever devices seem the most important to the work you have been doing. That way you might get something from me before SATA becomes obsolete... -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: lock (sleep mutex) inp not locked
On Mon, 29 Nov 2004, Christian Brueffer wrote: got this panic today on an SMP system. Modifications to the kernel are polling and altq support for the sf driver and removed SMP ifdefs from sys/kern/kern_poll.c. FreeBSD haakonia.hitnet.RWTH-Aachen.DE 5.3-STABLE FreeBSD 5.3-STABLE #61: Sat Nov 27 02:59:01 CET 2004 [EMAIL PROTECTED]:/usr/home/build/usr/home/build/src/sys/LORIEN i386 Sources are from November 22nd. Crashdump and debug kernel are available for further investigation. Sorry I didn't see this post before; thanks for the pointer. Could you tell me the revision of tcp_input.c, and the line number for tcp_input+0x2fb0? I have a number of locking tweaks in HEAD for TCP that are on the MFC path, so it might already be fixed there. Thanks! Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Principal Research Scientist, McAfee Research panic: lock (sleep mutex) inp not locked @ /usr/home/build/src/sys/netinet/tcp_input.c:2521 cpuid = 1 KDB: enter: panic [thread 100034] Stopped at kdb_enter+0x2b: nop db tr kdb_enter(c06c6c54) at kdb_enter+0x2b panic(c06caa02,c06db3d0,c06d57ce,c06d2493,9d9) at panic+0x127 witness_unlock(c3f4d57c,8,c06d2493,9d9) at witness_unlock+0xbc _mtx_unlock_flags(c3f4d57c,0,c06d2493,9d9,0) at _mtx_unlock_flags+0x5b tcp_input(c44bb000,14,5cb5e289,0,0) at tcp_input+0x2fb0 ip_input(c44bb000) at ip_input+0x52d netisr_dispatch(2,c44bb000,0,c44b0800,c1a93c00) at netisr_dispatch+0x58 ether_demux(c1a93c00,c44bb000,297,96,d74f6400) at ether_demux+0x292 ether_input(c1a93c00,c44bb000,c1a93e84,0,c0833d13) at ether_input+0x269 sf_rxeof(c1a93c00,c1a93c00,c1a93e84,c07276c0,d543ecbc) at sf_rxeof+0x183 sf_poll_locked(c1a93c00,0,5,c1a93e84,0) at sf_poll_locked+0x6b sf_poll(c1a93c00,0,5) at sf_poll+0x2e netisr_poll(0) at netisr_poll+0x188 swi_net(0) at swi_net+0x81 ithread_loop(c19e1080,d543ed48,c19e1080,c051aa34,0) at ithread_loop+0x124 fork_exit(c051aa34,c19e1080,d543ed48) at fork_exit+0xa4 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xd543ed7c, ebp = 0 --- db show locks exclusive sleep mutex tcp r = 0 (0xc0755dac) locked @ /usr/home/build/src/sys/netinet/tcp_input.c:617 exclusive sleep mutex Giant r = 1 (0xc0728320) locked @ /usr/home/build/src/sys/kern/kern_poll.c:332 db show pcpu cpuid= 1 curthread= 0xc19e3640: pid 38 swi1: net curpcb = 0xd543eda0 fpcurthread = none idlethread = 0xc19a84b0: pid 11 idle: cpu1 APIC ID = 1 currentldt = 0x28 spin locks held: db - 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DMA errors with SATA on 5.x [one fix]/ SATA DVD+RW
Garance A Drosihn wrote: At 9:49 PM +0100 12/9/04, Søren Schmidt wrote: I'm going to work on it soon thats for sure, however I have lots on the burner currently so its no rush. However all kinds of (S)ATA/ATAPI gear is always most welcome here in the lab, the levels of support I can provide is directly proportional to the amount of HW I have access to :) I am not great at mailing things. My sister is still waiting for me to mail her christmas presents for *last* year... Do you have a paypal account? I could send some money that way, and then you could get whatever devices seem the most important to the work you have been doing. That way you might get something from me before SATA becomes obsolete... Well, you probably should take care of your sister first :) And no I dont have a paypal account, so far I've got by fine without it, by using other means as checks, wiretransfers etc etc... -- -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DMA errors with SATA on 5.x [one fix]/ SATA DVD+RW
Sren Schmidt [EMAIL PROTECTED] probably said: Well, you probably should take care of your sister first :) And no I dont have a paypal account, so far I've got by fine without it, by using other means as checks, wiretransfers etc etc... Do you have a list of things (particular devices or general categories) that would be useful for your work and an address ? :) P. -- pir ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SOLVVED vinum crashes the Box... WRONG POSTING
On Thursday, 9 December 2004 at 14:52:14 +0100, Michael Schuh wrote: Hello, sorry for my wrong posting, it was late at night and i have *not* doublechecked my configuration. If you get a panic, it's not your fault. You shouldn't be able to panic the machine with an invalid configuration. It's still worth finding out what happened. Greg -- See complete headers for address and phone numbers. pgpfOdFRYobfU.pgp Description: PGP signature
Re: Re[2]: no internet after build world-kern install
upon the recimendation of dima im posting an excerpt from dmesg listing my net cards xl0: 3Com 3c905C-TX Fast Etherlink XL port 0xbc00-0xbc7f mem 0xe2001000-0xe200107f irq 5 at device 9.0 on pci0 miibus0: MII bus on xl0 xlphy0: 3c905C 10/100 internal PHY on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:50:da:26:bc:a2 xl1: 3Com 3c905B-TX Fast Etherlink XL port 0xc000-0xc07f mem 0xe200-0xe27f irq 12 at device 10.0 on pci0 miibus1: MII bus on xl1 xlphy1: 3Com internal media interface on miibus1 xlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl1: Ethernet address: 00:10:5a:29:84:73 - Original Message - From: dima [EMAIL PROTECTED] To: whitevamp [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, December 09, 2004 3:34 AM Subject: Re[2]: no internet after build world-kern install You could probably send an excerpt of dmesg regarding your NICs also. Since this is not a common problem the proper drivers can be kinda broken basically. Say, I didn't experience any problems upgrading from 4.10 to 5.3 with fxp. ok i finley got this all fix now im going to post in what i did so that its in the archives so if any one has this issue/problem maby itll help them out what i did was edit /boot/device.hints then i added hint.acpi.0.disabled=1 saved then rebooted and vwalol it worked i had internet access back once agin - Original Message - From: whitevamp [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, December 08, 2004 7:56 PM Subject: Re: no internet after build world-kern install ok i still havent got this resolved yet , heres an up date of things i have tryed to no avail , swaped out eth cards, swaped out cables, hooked up the box straight upto the dsl modem, looked around on the box to see if a firewall was getting started some ware and couldnt find one . so heres a recap of whats going on. cant ping any thing out side the box weather it be domain name or numeric ip address can ping localhost , 127.0.0.1 netstat -rn shows correct settings ( or i think) output is destiongatway netif default65.102.x.x( my dsl modem ip )xl0 65.102.x.x/x( reserverd ip )link#1 xl0 65.102.x.x( my ip ) xl0 (address) lo0 65.102.x.x( my dslmodem ip )link#1 xl0 127.0.0.1127.0.0.1 lo0 NOTE: i do have 2 netcards in this box the second card is not assigned an ip address --- Original Message - From: whitevamp [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, December 08, 2004 1:00 PM Subject: no internet after build world-kern install I have done a buildworld from 4.9 to 5.3 and also installed a new custom kernel and after all whent ok i rebooted the box and goto ping yahoo.com and i cant get out , and i also tryed pinging my outhere ip address and nothing on eathere one it just say destination unreachable. so i whent back and rebuilt a new kern with all defaults execpt i added options IPFIREWALL_DEFAULT_TO_ACCEPT and i still cant ping out . i have checked to see if the net card was up , if i do a ifconfig it shows it as active there, i have whent into rc.conf and removed out my firewal script that i did have running , still nuthilg, and durring boot its showing my net card there so what would be causeing this? if you need more info just let me know ohh and yea i do have a ip assigned to my net card IE:65.102.x.x and thanks inadvance for any help that you can give me on this. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
sys/bitypes.h (4.10)?
I'm getting reports from a user who can't build a port on 4.10, because his system has a sys/bitypes.h header which contains definitions that collide with sys/inttypes.h and sys/types.h. As far as I can tell, there is no sys/bitypes.h in 4.10. In fact, I can't find this header file in the repository except as a part of BIND, where it is provided as a compatibility header for FreeBSD. Did we ever install this? Where is sys/bitypes.h from and is its presence normal or an error? -- Christian naddy Weisgerber [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DMA errors with SATA on 5.x [one fix]/ SATA DVD+RW
Peter Radcliffe wrote: Rob [EMAIL PROTECTED] probably said: Same here, I could remove it and ship it to you today, probably 2nd day air, or one of the cheaper but fast services. If P, however, doesn't have to tear his computer all apart LOL, maybe that might be a better solution for me. I was more suggesting buying one and having it directly shipped... The support would likely be useful to me in the medium term so if I can contribute towards helping that happen I would. P. Yes, if there is a solution that doesn't require me to tear apart my computer I would prefer that, haha. It was an incredible pain routing all the cables and such with the dual scsi 160's in there. But I would be happy to donate money if needed. I use PayPal also, but could send check. Rob ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
freeze
I've had a server freeze three times on me know and I have no idea what the problem is... of course nothing gets output to the logs. The first time it was at 3AM on a Sunday so I thought the problem must be one of the periodic scripts. But those seemed fine when run by hand. The second two times it was just after 11PM on a Thursday. Does anyone know what could be running at that time? This is a dual Xeon machine and the kernel and world were compiled with a pentium4 CPUTYPE, but I thought that could be the problem so the last time it froze I recompiled everything for i686. But it froze again. There are still some installed ports compiled for pentium4. Now I'm thinking it could be PAE. I'm using the PAE config file that ships with 5.3 with a few extra settings. I think I'm going to disable that. Is there any way I can get more information if/when it freezes next time? Thanks. Aaron Stephanic ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
if_em int_throttle_ceil patch
Hi, Jeremie and Lists. The previous patch to change if_em's int_throttle_ceil into sysctl-able cause a kernel panic. If you set em's int_throttle_ceil=0 and then reconfigure the em, it cause a diveded by zero panic. This patch for original if_em.[ch] which is attached to this mail is corrected this problem. -- Shunsuke SHINOMIYA [EMAIL PROTECTED] if_em.diff Description: Binary data ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem booting a Compaq Proliant 1600.
I've tried researching this on google and playing around with various things myself to no avail. I should probably submit this as a bug report, but I'm not sure it is... I have a Compaq Proliant 1600 server. It's a large box with four SCSI disks, and (I believe) three controllers. It's a beast. It's currently running 4.3-STABLE quite nicely, but I've been trying to upgrade it to 4.9, 4.10 or 5.3 to no avail. I've tried from CDs and from source. The problem is that when I boot the new kernel, everything looks OK (it's hard to see the dmesg before it scrolls off during boot). However, when it gets to the Waiting 15 seconds for SCSI devices to settle, it then prompts me for the name of the root filesystem device. Usually, all my disks are mounted under sym0, sym1 or sym2. I see all three devices during the boot but they're not available when I hit '?' in the menu that asks the name of the root FS device. When I boot the 4.3-STABLE kernel, I get the following (normal) operation: Mounting root from ufs:da0s1a da0 at sym0 bus 0 target 0 lun 0 da0: COMPAQ HB00931B93 A195 Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled da0: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) and so on. As a minor quibble, I need to type '2:da(0,a)' at the boot prompt due to some confusion between what the BIOS thinks is device0 and what the kernel thinks is device0 but that's not a big deal, it just prevents auto-booting. Not sure if that makes any difference. Does anyone have any ideas? - Der -- Dermot Tynan Kalopa Media Limited http://www.kalopa.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem booting a Compaq Proliant 1600.
I had a similar problem with a machine with two Adaptec 2940UW controllers. When I upgraded from somethng like 4.7 to 4.8 the machine stopped booting. My workaround was to go with a single controller. The problem seems to be that at some point in the 4.X development cycle the way in which SCSI controllers and disks are enumerated was changed. You might have more luck getting an answer on the freebsd-scsi mailing list. (I'm afraid I didn't, I asked about the same question and got no answers) I'm about to start working with a 5.3-STABLE box with an onboard dual-channel controller and an Adaptec 39160 dual channel controller in a PCI slot, so I'm expecting to run into this again. (I do know that the controllers and disks are enumerated by sysctl entries (sysctl -a). I am wondering if booting off a live CD would allow you to run sysctl and find out how the physical disks and controllers are mapped to devices. Mike Squires ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
