Re: FreeBSD 7.x hang-on-boot on Dell 1950
Hi all, I have dell 1950 / Single Xeon , 8G RAM , SAS Host without RAID / im my hands. Yesterday we have install FreeBSD7.2 AMD. After INITIAL install all works fine and next step was cvsup base kernel rebuild. This steps are also fine BUT after first reboot from SINGLE mode to MULTIUSER mode the system has the same strange behavior, like described in this thread: Very slow passed boot init on fdc0 and it has very very slow and strange responce in text consloe switching. So the server was inusable. Next step was to shutdown the server from power button and just boot-up again and it .. was fine: fdc0 is reported like this: fdc0: does not respond for less a second and normal booting processed is goin on. The server is working well and stable now. Zaphod Beeblebrox wrote: On Sun, Nov 22, 2009 at 11:47 PM, Zaphod Beeblebrox zbee...@gmail.comwrote: On Sun, Nov 22, 2009 at 9:09 PM, Zaphod Beeblebrox zbee...@gmail.comwrote: On Fri, Nov 13, 2009 at 9:44 PM, Jeremy Chadwick free...@jdc.parodius.com wrote: This 1950 may predate that a bit, but I'm not sure how to nail it down exactly, other than by it's hardware components. Anyways, 7.0 does the same thing --- still wedged. I haven't seen anyone recommend this as a test method yet -- disabling fdc prior to the kernel booting via the loader prompt: - Press 6 at the menu, - At the loader prompt, type: set hint.fdc.0.disabled=1 boot -v (or without -v; your choice) You shouldn't need to set hint.fd.0.disabled=1, since fd0 would normally bind to fdc0; disable the latter and you disable the lesser. The intention here is to rule out the device attachment failures from fdc as the source of the deadlock. Entertainingly, it does not. Aparently that hint doesn't stop the code from trying to attach fdc0 when acpi says so. I suppose I need to know the console command to disable acpi and fdc. but it still wedges at device_attach: fdc0 attach returned 6 with the above. OK. With both floppy and acpi disabled, it dies calling start_init several times, the last being /stand/sysinstal (which should work). I don't see it starting the other CPUs. It hangs hard... no keyboard working (ie: no caps lock). OK... I finally figured out what makes this Dell boot. The system as I got it has 2 dual core (Xeon) processors. If I remove one processor (so now it has one dual-core processor), Then the system boots !?! ... so there's something wrong with how FreeBSD is going multiprocessor (works with RedHat, it would appear) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 7.x hang-on-boot on Dell 1950
On Sun, Nov 22, 2009 at 11:47 PM, Zaphod Beeblebrox zbee...@gmail.comwrote: On Sun, Nov 22, 2009 at 9:09 PM, Zaphod Beeblebrox zbee...@gmail.comwrote: On Fri, Nov 13, 2009 at 9:44 PM, Jeremy Chadwick free...@jdc.parodius.com wrote: This 1950 may predate that a bit, but I'm not sure how to nail it down exactly, other than by it's hardware components. Anyways, 7.0 does the same thing --- still wedged. I haven't seen anyone recommend this as a test method yet -- disabling fdc prior to the kernel booting via the loader prompt: - Press 6 at the menu, - At the loader prompt, type: set hint.fdc.0.disabled=1 boot -v (or without -v; your choice) You shouldn't need to set hint.fd.0.disabled=1, since fd0 would normally bind to fdc0; disable the latter and you disable the lesser. The intention here is to rule out the device attachment failures from fdc as the source of the deadlock. Entertainingly, it does not. Aparently that hint doesn't stop the code from trying to attach fdc0 when acpi says so. I suppose I need to know the console command to disable acpi and fdc. but it still wedges at device_attach: fdc0 attach returned 6 with the above. OK. With both floppy and acpi disabled, it dies calling start_init several times, the last being /stand/sysinstal (which should work). I don't see it starting the other CPUs. It hangs hard... no keyboard working (ie: no caps lock). OK... I finally figured out what makes this Dell boot. The system as I got it has 2 dual core (Xeon) processors. If I remove one processor (so now it has one dual-core processor), Then the system boots !?! ... so there's something wrong with how FreeBSD is going multiprocessor (works with RedHat, it would appear) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 7.x hang-on-boot on Dell 1950
On Fri, Nov 13, 2009 at 9:44 PM, Jeremy Chadwick free...@jdc.parodius.comwrote: This 1950 may predate that a bit, but I'm not sure how to nail it down exactly, other than by it's hardware components. Anyways, 7.0 does the same thing --- still wedged. I haven't seen anyone recommend this as a test method yet -- disabling fdc prior to the kernel booting via the loader prompt: - Press 6 at the menu, - At the loader prompt, type: set hint.fdc.0.disabled=1 boot -v (or without -v; your choice) You shouldn't need to set hint.fd.0.disabled=1, since fd0 would normally bind to fdc0; disable the latter and you disable the lesser. The intention here is to rule out the device attachment failures from fdc as the source of the deadlock. Entertainingly, it does not. Aparently that hint doesn't stop the code from trying to attach fdc0 when acpi says so. I suppose I need to know the console command to disable acpi and fdc. but it still wedges at device_attach: fdc0 attach returned 6 with the above. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 7.x hang-on-boot on Dell 1950
On Thu, 2009-11-12 at 16:56 -0500, Zaphod Beeblebrox wrote: I've now verified that 8.0-RC3 does the same thing, BTW. Anyways... no. There is no floppy option in the BIOS. It's not in Dell BIOS absolutely sucks. You get what you pay for. We have 25+ 9th gen systems. Revision 1, with the older HT Xeons, are all lemons. The only thing that runs stable on them in ESXi R3 of the 1950 with the PERC6 and DRAC5 works fine on 6.3/amd64, 7.2, etc. ~BAS any of the sub-menus (which is how Dell's BIOS is organized). I'm also not-so-sure that the floppy is where it's stopping because the non-ACPI boot doesn't ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 7.x hang-on-boot on Dell 1950
On Sun, Nov 22, 2009 at 9:09 PM, Zaphod Beeblebrox zbee...@gmail.comwrote: On Fri, Nov 13, 2009 at 9:44 PM, Jeremy Chadwick free...@jdc.parodius.com wrote: This 1950 may predate that a bit, but I'm not sure how to nail it down exactly, other than by it's hardware components. Anyways, 7.0 does the same thing --- still wedged. I haven't seen anyone recommend this as a test method yet -- disabling fdc prior to the kernel booting via the loader prompt: - Press 6 at the menu, - At the loader prompt, type: set hint.fdc.0.disabled=1 boot -v (or without -v; your choice) You shouldn't need to set hint.fd.0.disabled=1, since fd0 would normally bind to fdc0; disable the latter and you disable the lesser. The intention here is to rule out the device attachment failures from fdc as the source of the deadlock. Entertainingly, it does not. Aparently that hint doesn't stop the code from trying to attach fdc0 when acpi says so. I suppose I need to know the console command to disable acpi and fdc. but it still wedges at device_attach: fdc0 attach returned 6 with the above. OK. With both floppy and acpi disabled, it dies calling start_init several times, the last being /stand/sysinstal (which should work). I don't see it starting the other CPUs. It hangs hard... no keyboard working (ie: no caps lock). ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 7.x hang-on-boot on Dell 1950
Zaphod Beeblebrox wrote: I have a dell 1950 here on the floor. Since 1950 seems to refer to a lot of things with a lot of configurations, I'm going to attempt to narrow that down a bit. It's got 2x 2.33Ghz dual core pentiums (stepping 06-0F-6 according to the bios) in it and it has an SAS RAID card that FreeBSD recognises. I've upgraded the BIOS to 2.6.1. It has two SAS 70G drives in a RAID 1 configuration and it has a DVD (although it will only boot from CDs). If it helps, it's between 2 and 3 years old, I think. If I allow the machine to boot normally, it stopps after checking the floppy (there is no floppy) with the following message: fdc0: floppy drive controller port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 If I boot the machine without ACPI, it seems to stop at the same place (stopping after having checked the ata controller, which checks right before the floppy) If I boot the machine verbose, I get no more information --- it stopps at the same place. I have tried this (so far) with 7.2-R and 7.1-R. Both do the same thing. Can you try with 7.0 (should be available on ftp-archive)? I have a 1950 from Sept '07 that's now running 7.2-STABLE i386 with the fd devices removed. It started out as 7.0-RELEASE, so maybe its a problem introduced since then? Also, you didn't mention if you were running i386 or amd64. Richard ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 7.x hang-on-boot on Dell 1950
On Fri, Nov 13, 2009 at 9:30 AM, Richard Tector richardtec...@thekeelecentre.com wrote: Can you try with 7.0 (should be available on ftp-archive)? I can confirm that 7.0 exhibits the same behaviour (and is incidentally very chatty about probing the raid controller) I have a 1950 from Sept '07 that's now running 7.2-STABLE i386 with the fd devices removed. It started out as 7.0-RELEASE, so maybe its a problem introduced since then? Also, you didn't mention if you were running i386 or amd64. This 1950 may predate that a bit, but I'm not sure how to nail it down exactly, other than by it's hardware components. Anyways, 7.0 does the same thing --- still wedged. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 7.x hang-on-boot on Dell 1950
On Fri, Nov 13, 2009 at 08:57:56PM -0500, Zaphod Beeblebrox wrote: On Fri, Nov 13, 2009 at 9:30 AM, Richard Tector richardtec...@thekeelecentre.com wrote: Can you try with 7.0 (should be available on ftp-archive)? I can confirm that 7.0 exhibits the same behaviour (and is incidentally very chatty about probing the raid controller) I have a 1950 from Sept '07 that's now running 7.2-STABLE i386 with the fd devices removed. It started out as 7.0-RELEASE, so maybe its a problem introduced since then? Also, you didn't mention if you were running i386 or amd64. This 1950 may predate that a bit, but I'm not sure how to nail it down exactly, other than by it's hardware components. Anyways, 7.0 does the same thing --- still wedged. I haven't seen anyone recommend this as a test method yet -- disabling fdc prior to the kernel booting via the loader prompt: - Press 6 at the menu, - At the loader prompt, type: set hint.fdc.0.disabled=1 boot -v (or without -v; your choice) You shouldn't need to set hint.fd.0.disabled=1, since fd0 would normally bind to fdc0; disable the latter and you disable the lesser. The intention here is to rule out the device attachment failures from fdc as the source of the deadlock. For sake of comparison, on our systems (non-Dell), this is what we see during fdc/fd probe and shortly after: fdc0: floppy drive controller port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] fd0: 1440-KB 3.5 drive on fdc0 drive 0 cpu0: ACPI CPU on acpi0 I'd have recommended disabling ACPI but you tried it already with the same results. :-) -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
FreeBSD 7.x hang-on-boot on Dell 1950
I have a dell 1950 here on the floor. Since 1950 seems to refer to a lot of things with a lot of configurations, I'm going to attempt to narrow that down a bit. It's got 2x 2.33Ghz dual core pentiums (stepping 06-0F-6 according to the bios) in it and it has an SAS RAID card that FreeBSD recognises. I've upgraded the BIOS to 2.6.1. It has two SAS 70G drives in a RAID 1 configuration and it has a DVD (although it will only boot from CDs). If it helps, it's between 2 and 3 years old, I think. If I allow the machine to boot normally, it stopps after checking the floppy (there is no floppy) with the following message: fdc0: floppy drive controller port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 If I boot the machine without ACPI, it seems to stop at the same place (stopping after having checked the ata controller, which checks right before the floppy) If I boot the machine verbose, I get no more information --- it stopps at the same place. I have tried this (so far) with 7.2-R and 7.1-R. Both do the same thing. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 7.x hang-on-boot on Dell 1950
On Thu, Nov 12, 2009 at 2:46 PM, Zaphod Beeblebrox zbee...@gmail.comwrote: I have a dell 1950 here on the floor. Since 1950 seems to refer to a lot of things with a lot of configurations, I'm going to attempt to narrow that down a bit. It's got 2x 2.33Ghz dual core pentiums (stepping 06-0F-6 according to the bios) in it and it has an SAS RAID card that FreeBSD recognises. I've upgraded the BIOS to 2.6.1. It has two SAS 70G drives in a RAID 1 configuration and it has a DVD (although it will only boot from CDs). If it helps, it's between 2 and 3 years old, I think. If I allow the machine to boot normally, it stopps after checking the floppy (there is no floppy) with the following message: fdc0: floppy drive controller port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 If I boot the machine without ACPI, it seems to stop at the same place (stopping after having checked the ata controller, which checks right before the floppy) If I boot the machine verbose, I get no more information --- it stopps at the same place. I have tried this (so far) with 7.2-R and 7.1-R. Both do the same thing. Can you disable the floppy drive and controller? There are usually separate options on different screens. -- Adam Vande More ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
FreeBSD 7.x hang-on-boot on Dell 1950
On Thu, Nov 12, 2009 at 4:27 PM, Adam Vande More amvandem...@gmail.comwrote: On Thu, Nov 12, 2009 at 2:46 PM, Zaphod Beeblebrox zbee...@gmail.comwrote: fdc0: floppy drive controller port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 If I boot the machine without ACPI, it seems to stop at the same place (stopping after having checked the ata controller, which checks right before the floppy) If I boot the machine verbose, I get no more information --- it stopps at the same place. Can you disable the floppy drive and controller? There are usually separate options on different screens. I've now verified that 8.0-RC3 does the same thing, BTW. Anyways... no. There is no floppy option in the BIOS. It's not in any of the sub-menus (which is how Dell's BIOS is organized). I'm also not-so-sure that the floppy is where it's stopping because the non-ACPI boot doesn't mention the floppy at all ... leading me to believe it's whatever is checked after the floppy that is at fault... but even the verbose boot doesn't let me know what that might be. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
