Re: syscons hangs with -current
On Tue, 11 Jul 2000 10:54:47 MST, Eric Anholt wrote: > What I did do, I went into sys/dev/fb/vga.c and commented out the > second vga head detection. Works beautifully now, though it would be > better to actually figure out why it was finding another vga card. > Still, it's up and running. I'd discuss this with Kazutaka YOKOTA <[EMAIL PROTECTED]> Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: syscons hangs with -current
I'm afraid I don't quite understand how that desribes the fix to my problem (Freezing on boot after having probed a non-existant vga1 and sc1). What I did do, I went into sys/dev/fb/vga.c and commented out the second vga head detection. Works beautifully now, though it would be better to actually figure out why it was finding another vga card. Still, it's up and running. Now, if I could just figure out why ppp doesn't work (keeps complaining about "tun0: Warning: Add route failed: 0.0.0.0: errno: Network is unreachable", dials, and then sits and does nothing.) >On Mon, 10 Jul 2000 10:39:44 MST, Eric Anholt wrote: > >> Nope, same old device sc 1. I've tried unmodified GENERIC, and it >> does the same thing. Why am I special? > >I believe that the attached commit message describes the fix to the >problem. However, I'd recommend going all the way to rev 1.10 or >whatever the latest is by the time you get this mail. :-) > >Ciao, >Sheldon. > > >green 2000/07/10 23:47:38 PDT > > Modified files: > sys/dev/randomdevyarrow.c > Log: > One should never allocate 4-kilobyte structs and such on the interrupt > stack. It's bad for your machine's health. > > Make the two huge structs in reseed() static to prevent crashes. This > is the bug that people have been running into and panic()ing on for the > past few days. > > Reviewed by:phk > > Revision ChangesPath > 1.8 +7 -3 src/sys/dev/randomdev/yarrow.c -- -- Eric Anholt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: syscons hangs with -current
On Tue, Jul 11, 2000 at 07:00:52PM +0200, Sheldon Hearn wrote: > > > On Mon, 10 Jul 2000 11:14:16 MST, Eric Anholt wrote: > > > I am getting freezes on -current as of my last two updates, Jul. 9 > > and today, Jul. 10. My previous update was around Jun 14. I can > > boot the kernel from the last update just fine, though ppp doesn't > > work due to net changes. > > Just as a datapoint, I'm getting reboots and hard locks shortly after > reboot (no more than 20 minutes) using a kernel built from sources from > around 22H30 last night. > I had the same problem beginning yesterday. My sources were updated at 1500 UTC Jul 10. System would run for between 15 and 25 minutes before a panic (something about supervisor mode, sorry I didn't do any tracking, I assumed I'd missed the SMP commits HEADS UP).. Retrieved sources as of 1700UTC Jul 11 built cleanly and have been running fine. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: syscons hangs with -current
On Mon, 10 Jul 2000 11:14:16 MST, Eric Anholt wrote: > I am getting freezes on -current as of my last two updates, Jul. 9 > and today, Jul. 10. My previous update was around Jun 14. I can > boot the kernel from the last update just fine, though ppp doesn't > work due to net changes. Just as a datapoint, I'm getting reboots and hard locks shortly after reboot (no more than 20 minutes) using a kernel built from sources from around 22H30 last night. A kernel from around the same time on Friday last week does not exhibit the problem. > sc1: at flags 0x100 on isa0 Note, though, that my box _does_ make it _well_ past the kernel probe stage and doesn't show the peculiar sc1 device at probe time. Any idea what that is, by the way? You haven't perhaps got ``device sc 2'' or something crazy in your kernel config file? Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
