SOLVED: Re: Hang after soft reboot.
> On Mon, 24 Feb 2003 [EMAIL PROTECTED] wrote: > > I see. However, good news I appear to have solved this by adding > > > > hw.ata.ata_dma="0" > > > > to /boot/loader.conf Actually, it seems this, and/or this in combination with a custom compiled kernel with most of the unneeded parts removed *has* actually solved this. While testing some network changes recently I actually warm rebooted serveral times sucessfully. Of course now it's fixed I hope to never use it ;) DG To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Hang after soft reboot.
Gah. Correction: that was either a fluke, the problem is intermittent, or I hit the reset button without thinking and through it had worked. Probabbly the last option. More caffeine please. Damn... I was hoping that worked.. Don To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Hang after soft reboot.
On Mon, 24 Feb 2003 [EMAIL PROTECTED] wrote: > I see. However, good news I appear to have solved this by adding > > hw.ata.ata_dma="0" > > to /boot/loader.conf Gah. Correction: that was either a fluke, the problem is intermittent, or I hit the reset button without thinking and through it had worked. Probabbly the last option. More caffeine please. DG To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Hang after soft reboot.
On Mon, 24 Feb 2003, northern snowfall wrote: > >If the extra hacking was done, what would be wrong with that occurring at > >the end of the reboot process, rather than the start of the boot process? > It probably wouldn't *hurt* anything, though, it wouldn't *do* anything, > either. When power cycles the ATA will initialize to the native state. > So, any assertion of pins prior to power cycle would be moot. Don I see. However, good news I appear to have solved this by adding hw.ata.ata_dma="0" to /boot/loader.conf I've no idea why this could be required for a warm boot but not a cold one, but I'm happy it appears to be working now. DG To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Hang after soft reboot.
If the extra hacking was done, what would be wrong with that occurring at the end of the reboot process, rather than the start of the boot process? It probably wouldn't *hurt* anything, though, it wouldn't *do* anything, either. When power cycles the ATA will initialize to the native state. So, any assertion of pins prior to power cycle would be moot. Don To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Hang after soft reboot.
On Thu, 20 Feb 2003, northern snowfall wrote: > Well... all ATA in freebsd are pretty much conglomerated into the same > driver... but, the problem isn't really so much the ATA as it is that > the ATA expects a PM telling it what to do. Since this is something that > must be done via the hardware at boot, FreeBSD doesn't really have a way > to tell the ATA what to do. One solution might be hacking extra reset > controls, etc, into the ATA driver so that this functionality is > asserted on boot. Then, though, there is a possible chicken-egg issue: > you're initializing the disk and snarfing data off the disk at the same > time as attempting a hard reset, which, might cause a lock (or worse). I > think your most painless solution is upgrading your mother board. Don Well I don't have much option to upgrade here, so I just won't do warm reboots. However that does give me some questions: If the extra hacking was done, what would be wrong with that occurring at the end of the reboot process, rather than the start of the boot process? If there's some form of a kernel panic then presumably a reboot would occur causing this hang; what could I do to prevent this? Are their any other times where a reboot could occur out of my control? Thanks again, DG To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Hang after soft reboot.
Would there be any chance that the system is "working" with some generic driver and there is a specific driver for my hard drive controller (it's an ISA card), which would solve this? Well... all ATA in freebsd are pretty much conglomerated into the same driver... but, the problem isn't really so much the ATA as it is that the ATA expects a PM telling it what to do. Since this is something that must be done via the hardware at boot, FreeBSD doesn't really have a way to tell the ATA what to do. One solution might be hacking extra reset controls, etc, into the ATA driver so that this functionality is asserted on boot. Then, though, there is a possible chicken-egg issue: you're initializing the disk and snarfing data off the disk at the same time as attempting a hard reset, which, might cause a lock (or worse). I think your most painless solution is upgrading your mother board. Don To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Hang after soft reboot.
On Thu, 20 Feb 2003, northern snowfall wrote: > This is usually a manifestation of old power interfaces (or lack > there-of) mingling with devices that need to be told when to assert a > RESET via power management. Would there be any chance that the system is "working" with some generic driver and there is a specific driver for my hard drive controller (it's an ISA card), which would solve this? > Solution? Never warm boot. > P.S. if you keep warm booting you might corrupt the ATA Ugh. I'm glad I sorted out that Page fault while in Kernel mode I was getting while trying to compile a new kernel then (internal cache needed to be turned off in the bios--that one slipped past the mem86 tester too). DG To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Hang after soft reboot.
Hi, Hello On a fresh, clean install of 4.7-RELEASE my (old) machine consistently hangs while booting after soft reboot. Powering down and back up again, or pressing the reset button will boot the machine, but if it is rebooted by the OS then it hangs after detecting the isa bus "isa0: on motherboard". This is usually a manifestation of old power interfaces (or lack there-of) mingling with devices that need to be told when to assert a RESET via power management. For example, I have a hurd of Compaq Deskpro that all use the old VIA 586 power controller. Because no OS (that I know of ... except for maybe win*?) has a driver for this chip, I get the same hang you talk about on a warm boot. Since the chipset isn't thunked properly, it doesn't let the ATA know to RESET. This can be a problem when probing the disk for information, but, normally doesn't affect loading the boot sector or the first couple of cylinders. I forget the restriction atm... Anyways, thats most likely your culprit. This is a normal boot up, with the hang point indicated: ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 ata1 at port 0x170-0x177,0x376 irq 15 on isa0 Solution? Never warm boot. Don P.S. if you keep warm booting you might corrupt the ATA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Hang after soft reboot.
Hi, On a fresh, clean install of 4.7-RELEASE my (old) machine consistently hangs while booting after soft reboot. Powering down and back up again, or pressing the reset button will boot the machine, but if it is rebooted by the OS then it hangs after detecting the isa bus "isa0: on motherboard". This is a normal boot up, with the hang point indicated: Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.7-RELEASE #0: Wed Oct 9 15:08:34 GMT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: Cyrix 486DX2 (486-class CPU) Origin = "CyrixInstead" DIR=0x321b Stepping=3 Revision=2 real memory = 20971520 (20480K bytes) config> di pcic1 config> di sn0 config> di lnc0 config> di ie0 config> di fe0 config> di cs0 config> di bt0 config> di aic0 config> di aha0 config> di adv0 config> en ed0 config> po ed0 0x340 config> ir ed0 5 config> iom ed0 0xd8000 config> f ed0 0 config> q avail memory = 15437824 (15076K bytes) Preloaded elf kernel "kernel" at 0xc050f000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc050f09c. md0: Malloc disk npx0: on motherboard npx0: INT 16 interface isa0: on motherboard orm0: at iomem 0xc-0xc5fff on isa0 ep0: <3Com 3C509-TPO EtherLink III> at port 0x300-0x30f irq 10 on isa0 ep0: Ethernet address 00:50:04:22:24:ce ep1: <3Com 3C509-TPO EtherLink III> at port 0x210-0x21f irq 11 on isa0 ep1: Ethernet address 00:a0:24:ef:b9:05 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 ata1 at port 0x170-0x177,0x376 irq 15 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 vga0: at port 0x3b0-0x3cf iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA (mono) <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16450 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16450 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ed0 at port 0x340-0x35f iomem 0xd8000 irq 5 drq 0 on isa0 ed0: address 00:00:1b:4f:39:28, type NE2000 (16 bit) ad0: 234MB [967/16/31] at ata0-master BIOSPIO ad1: 516MB [1120/16/59] at ata0-slave BIOSPIO Mounting root from ufs:/dev/ad0s1a I don't see anything in the Bios which would appear to effect this, and I've been unable to find anything similar in the archives or by searching google. Any ideas (or pointers on where to look) ? Obviously rebooting is something I hope not to have to do very often, but it'd be nice to know it would actually work remotely etc. Thanks, DG To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
