Re: Console problem with ALT-F# keys
Hi, On Friday 26 August 2011 07:56:04 Pegasus Mc Cleaft wrote: I have recently installed this into a new machine and had chance to did you solve your problem? I have had a similar problem yesterday after upgrading my ports via packages. I could not even switch to the consoles anymore. This was solved after I compiled X and the drivers from the ports and installed them. Erich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Console problem with ALT-F# keys
On Saturday 27 August 2011 13:11:43 Erich Dollansky wrote: Hi, On Friday 26 August 2011 07:56:04 Pegasus Mc Cleaft wrote: I have recently installed this into a new machine and had chance to did you solve your problem? I have had a similar problem yesterday after upgrading my ports via packages. I could not even switch to the consoles anymore. Hi Erich, No, I havent.. But I am leaning towards a hardware quirk at this point. Since the original post, I have done a bit more digging and had a chance to test against another machine and it does not have the same problem. I also found out that even though I had connected a PS2 keyboard to the motherboards PS2 ports, these are not conventional ports. They look like they are actually connected to a converter that sits on the motherboards USB controller. On the second test machine, I attached a PS2 keyboard to the PS2 Port and a USB keyboard (Sun type 6) to the USB ports. Neither of the keyboards have this problem.. With this in mind, I am fairly sure its not a BSD issue and suspect its whatever converter they put on this Intel motherboard. Weird... Peg ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Console problem with ALT-F# keys
Hi-- On Aug 25, 2011, at 5:56 PM, Pegasus Mc Cleaft wrote: I am running FreeBSD 9.0-BETA1 r225125 compiled with LLVM on a Xeon processor (CPUTYPE=core2 and CFLAGS= -mmmx -msse -msse2 -msse3 -O2 -fno-strict-aliasing -pipe) The FreeBSD kernel doesn't use MMX or SSE by explicit design choice. See sys/conf/kern.mk: # [ ... ] Explicitly prohibit the use of SSE and other SIMD # operations inside the kernel itself. These operations are exclusively # reserved for user applications. # .if ${MACHINE_ARCH} == i386 ${CC} != icc CFLAGS+=-mno-align-long-strings -mpreferred-stack-boundary=2 \ -mno-mmx -mno-3dnow -mno-sse -mno-sse2 INLINE_LIMIT?= 8000 .endif Trying to override the default compiler flags to force it to use MMX/SSE is simply not going to work. Regards, -- -Chuck ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: console problem
Chuck Robey wrote: I've been on vacation for the last week, so I haven't been watching -current like a good boy should, but I've suddenly been seeing a serious problem, and it *might* not have been reported, and seeing as code freeze is almost here, it's worth risking a bit of embarrassment, I guess. Anyhow, it's the console, it's been locking up. I just retried it with a kernel cvsupped not 2 hours ago, and it's still here. All the vty's lock up, and once even froze the PC speaker (beeping annoyingly at me). I see the hanging Speaker problem on an Asus A7V with an Athlon 2000+ and 256 Megs of RAM, so it seems not SMP related, nor Tyan related. Holm -- FreibergNet Systemhaus GbR Holm Tiffe * Administration, Development Systemhaus für Daten- und Netzwerktechnik phone +49 3731 781279 Unternehmensgruppe Liebscher Partnerfax +49 3731 781377 D-09599 Freiberg * Am St. Niclas Schacht 13 http://www.freibergnet.de To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: console problem
This problem and the general 'console freeze' problem, and possibly even the 'floppy doesn't work anymore' problem should be fixed. The problem was with the ahc and ahd drivers corrupting the callout list used to trigger timeouts in the kernel. Scott -Original Message- From: Holm Tiffe [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 04, 2002 7:27 AM To: [EMAIL PROTECTED] Subject: Re: console problem Chuck Robey wrote: I've been on vacation for the last week, so I haven't been watching -current like a good boy should, but I've suddenly been seeing a serious problem, and it *might* not have been reported, and seeing as code freeze is almost here, it's worth risking a bit of embarrassment, I guess. Anyhow, it's the console, it's been locking up. I just retried it with a kernel cvsupped not 2 hours ago, and it's still here. All the vty's lock up, and once even froze the PC speaker (beeping annoyingly at me). I see the hanging Speaker problem on an Asus A7V with an Athlon 2000+ and 256 Megs of RAM, so it seems not SMP related, nor Tyan related. Holm -- FreibergNet Systemhaus GbR Holm Tiffe * Administration, Development Systemhaus für Daten- und Netzwerktechnik phone +49 3731 781279 Unternehmensgruppe Liebscher Partnerfax +49 3731 781377 D-09599 Freiberg * Am St. Niclas Schacht 13 http://www.freibergnet.de To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: console problem
On Wed, 4 Dec 2002, Long, Scott wrote: This problem and the general 'console freeze' problem, and possibly even the 'floppy doesn't work anymore' problem should be fixed. The problem was with the ahc and ahd drivers corrupting the callout list used to trigger timeouts in the kernel. Pardon me for taking this long to answer, but the surest method of proving the fix was a sufficient torture test. It's quite finished now, and this is indeed a fix. I'm curious how you got to looking into the ahc driver for an ostensible syscons bug ... just perusing commit logs? Scott -Original Message- From: Holm Tiffe [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 04, 2002 7:27 AM To: [EMAIL PROTECTED] Subject: Re: console problem Chuck Robey wrote: I've been on vacation for the last week, so I haven't been watching -current like a good boy should, but I've suddenly been seeing a serious problem, and it *might* not have been reported, and seeing as code freeze is almost here, it's worth risking a bit of embarrassment, I guess. Anyhow, it's the console, it's been locking up. I just retried it with a kernel cvsupped not 2 hours ago, and it's still here. All the vty's lock up, and once even froze the PC speaker (beeping annoyingly at me). I see the hanging Speaker problem on an Asus A7V with an Athlon 2000+ and 256 Megs of RAM, so it seems not SMP related, nor Tyan related. Holm -- FreibergNet Systemhaus GbR Holm Tiffe * Administration, Development Systemhaus für Daten- und Netzwerktechnik phone +49 3731 781279 Unternehmensgruppe Liebscher Partnerfax +49 3731 781377 D-09599 Freiberg * Am St. Niclas Schacht 13 http://www.freibergnet.de To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: console problem
It's not the fact that I have an extra, unused on-board video (checked). Also, when the video output stops, the console still works fine for input (keyboard never stops working normally). Also, I can successfully start X just fine. It's just the vty's output that is stopped (all vtys, alt-Fn has no effect on output, only input). It's not wiped, just no further changes. I tried issuing a vidcontrol; before lockup, color change works fine, after, no effect. It's acting as if the mapping in memory to the video buffer has changed. The problem is that the syscons driver stops updating the display because it's timeout call to scrn_timeout() gets lost and/or never re-armed. The causes could be one or more of the following: 1) a race in the syscons code that determines whether or not to re-arm the periodic timeout. 2) a race in the callout code that results in random timeouts getting lost. Since syscons timeout happens 10 times a second, it has a high chance of being affected. 3) breakage in softclock, resulting in timeouts not being triggered at all. I highly doubt this one since the rest of the machine works fine. Note that while it happens easily on SMP machines, I was able to trigger it last night on a UP box in the form of the syscons bell getting turned on but not off. My SMP box died while trying to debug this and I haven't been able to get access to another one yet. If anyone is interested in looking at it, /sys/dev/syscons/syscons.c:scrn_timeout() is a good place to start. Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: console problem
On Sun, Dec 01, 2002 at 04:07:32PM -0500, Chuck Robey [EMAIL PROTECTED] wrote: I've been on vacation for the last week, so I haven't been watching -current like a good boy should, but I've suddenly been seeing a serious problem, and it *might* not have been reported, and seeing as code freeze is almost here, it's worth risking a bit of embarrassment, I guess. Anyhow, it's the console, it's been locking up. I just retried it with a kernel cvsupped not 2 hours ago, and it's still here. All the vty's lock up, and once even froze the PC speaker (beeping annoyingly at me). There don't seem to be any hung processes. I can use X, and I can also ssh into the box, so it's the console only. Can't switch to different vty's, and the one i'm on is frozen, no response to any keys. It seems to come on more quickly if I do something serious, like a buildkernel. Happened once on startup, but even though rc hadn't finished, I WAS able to ssh into the box and shut it down (indicating to me that rc had finished, just no response from the console). Machine is a 2 processor Tyan Thunder, 1G memory, two Athlons, scsi disks and eide both. It's interesting that you seem to have almost same machine as I have. Tyan Thunder with SCSI and ATA disks, SMP and the only difference seems to be memory size, 1GB vs. 512MB. Not counting network interfaces and such. I've also lost console after rebuild yesterday. The kernel from Nov. 29 works. Mine (console) not locks up but is simply missing from the start. Otherwise system is up and running. I don't think it's coincidence, something is broken and related to the Tyan mobos we have. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: console problem
On Mon, 2 Dec 2002, Vallo Kallaste wrote: Anyhow, it's the console, it's been locking up. I just retried it with a kernel cvsupped not 2 hours ago, and it's still here. All the vty's lock up, and once even froze the PC speaker (beeping annoyingly at me). There don't seem to be any hung processes. I can use X, and I can also ssh into the box, so it's the console only. Can't switch to different vty's, and the one i'm on is frozen, no response to any keys. It seems to come on more quickly if I do something serious, like a buildkernel. Happened once on startup, but even though rc hadn't finished, I WAS able to ssh into the box and shut it down (indicating to me that rc had finished, just no response from the console). Machine is a 2 processor Tyan Thunder, 1G memory, two Athlons, scsi disks and eide both. It's interesting that you seem to have almost same machine as I have. Tyan Thunder with SCSI and ATA disks, SMP and the only difference seems to be memory size, 1GB vs. 512MB. Not counting network interfaces and such. I've also lost console after rebuild yesterday. The kernel from Nov. 29 works. Mine (console) not locks up but is simply missing from the start. Otherwise system is up and running. I don't think it's coincidence, something is broken and related to the Tyan mobos we have. Are you using the on-board video? I have an extra video card, and had to reflash the board because before reflash, I used to have this problem. It went away after reflash, and your references to the mobo reminded me. Tonight, I'll see if the video just goes back to the onboard card. Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: console problem
On Mon, Dec 02, 2002 at 09:04:22AM -0500, Chuck Robey [EMAIL PROTECTED] wrote: Machine is a 2 processor Tyan Thunder, 1G memory, two Athlons, scsi disks and eide both. It's interesting that you seem to have almost same machine as I have. Tyan Thunder with SCSI and ATA disks, SMP and the only difference seems to be memory size, 1GB vs. 512MB. Not counting network interfaces and such. I've also lost console after rebuild yesterday. The kernel from Nov. 29 works. Mine (console) not locks up but is simply missing from the start. Otherwise system is up and running. I don't think it's coincidence, something is broken and related to the Tyan mobos we have. Are you using the on-board video? I have an extra video card, and had to reflash the board because before reflash, I used to have this problem. It went away after reflash, and your references to the mobo reminded me. Tonight, I'll see if the video just goes back to the onboard card. I'm not aware of any Tyan Thunder mobos which have onboard integrated video. I have addon AGP video card, Matrox G400 with 32MB of memory and single head. Umm, I made mistake identifying your board as similar to mine, sorry. I _had_ Tyan Thunder (S1836 variety), but it's been replaced long ago with Tyan Thunderbolt, S1837UANG. The original burned down because of faulty current regulator on the mb and took one of my processors together in the process. I'll not forget it, even after the current mb has been working fine for two and half years. Sorry about confusion. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: console problem
On Mon, Dec 02, 2002 at 04:33:27PM +0200, Vallo Kallaste wrote: I'm not aware of any Tyan Thunder mobos which have onboard integrated video. They *all* do. (meaning all the Tyan dual-K7 Thunders) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: console problem
At 02:59 PM 12/2/2002 +0200, Vallo Kallaste wrote: On Sun, Dec 01, 2002 at 04:07:32PM -0500, Chuck Robey [EMAIL PROTECTED] wrote: I've been on vacation for the last week, so I haven't been watching -current like a good boy should, but I've suddenly been seeing a serious problem, and it *might* not have been reported, and seeing as code freeze is almost here, it's worth risking a bit of embarrassment, I guess. Anyhow, it's the console, it's been locking up. I just retried it with a kernel cvsupped not 2 hours ago, and it's still here. All the vty's lock up, and once even froze the PC speaker (beeping annoyingly at me). There don't seem to be any hung processes. I can use X, and I can also ssh into the box, so it's the console only. Can't switch to different vty's, and the one i'm on is frozen, no response to any keys. It seems to come on more quickly if I do something serious, like a buildkernel. Happened once on startup, but even though rc hadn't finished, I WAS able to ssh into the box and shut it down (indicating to me that rc had finished, just no response from the console). Machine is a 2 processor Tyan Thunder, 1G memory, two Athlons, scsi disks and eide both. It's interesting that you seem to have almost same machine as I have. Tyan Thunder with SCSI and ATA disks, SMP and the only difference seems to be memory size, 1GB vs. 512MB. Not counting network interfaces and such. I've also lost console after rebuild yesterday. The kernel from Nov. 29 works. Mine (console) not locks up but is simply missing from the start. Otherwise system is up and running. I don't think it's coincidence, something is broken and related to the Tyan mobos we have. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message I have the same problem here on an Intel PR440FX dual pentium-pro MB. Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: console problem
On Mon, Dec 02, 2002 at 10:33:55AM -0800, David O'Brien [EMAIL PROTECTED] wrote: On Mon, Dec 02, 2002 at 04:33:27PM +0200, Vallo Kallaste wrote: I'm not aware of any Tyan Thunder mobos which have onboard integrated video. They *all* do. (meaning all the Tyan dual-K7 Thunders) Sorry about confusion, I was so bound to my Thunder(bolt). The S183[67] are Slot1 boards. Seems that marketing buzzword thunder got the water turbid once again. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: console problem
On Mon, Dec 02, 2002 at 10:40:21AM -0800, Manfred Antar wrote: There don't seem to be any hung processes. I can use X, and I can also ssh into the box, so it's the console only. Can't switch to different vty's, and the one i'm on is frozen, no response to any keys. Same here on this morning's kernel (PST) on a Dell Precision 420 SMP system (Intel 840 chipset). The problem appears to also be present on an SMP kernel built on Nov 25th. No problems with UP kernels. It seems to be an output-related problem because I can login blindly to the machine to start X. Also, when I press Ctl-Alt-Del to shut the machine down, the missing output (banner, login prompts, shell prompts/commands) suddenly appears on the console. Hth, -- Jos Backus _/ _/_/_/ Sunnyvale, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/_/ jos at catnook.com_/_/ _/_/_/ require 'std/disclaimer' To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: console problem
On Mon, Dec 02, 2002 at 10:40:21AM -0800, Manfred Antar wrote: There don't seem to be any hung processes. I can use X, and I can also ssh into the box, so it's the console only. Can't switch to different vty's, and the one i'm on is frozen, no response to any keys. Same here on this morning's kernel (PST) on a Dell Precision 420 SMP system (Intel 840 chipset). The problem appears to also be present on an SMP kernel built on Nov 25th. No problems with UP kernels. It seems to be an output-related problem because I can login blindly to the machine to start X. Also, when I press Ctl-Alt-Del to shut the machine down, the missing output (banner, login prompts, shell prompts/commands) suddenly appears on the console. I was seeing the problem on my 2x550Mhz machine yesterday, but the machine died of other causes before I could fully track it down. What I found is that the timeout function of syscons (scrn_timeout()) stops getting called after a certain random point during the processing of the rc scripts. It happened most often when the network was being configured. Without this timeout, the console never gets updated except when flushed by a kernel printf. As you noted, input still works fine. Unfortunately, I wasn't able to track this down any farther. Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: console problem
On Mon, 2 Dec 2002, Manfred Antar wrote: Anyhow, it's the console, it's been locking up. I just retried it with a kernel cvsupped not 2 hours ago, and it's still here. All the vty's lock up, and once even froze the PC speaker (beeping annoyingly at me). There don't seem to be any hung processes. I can use X, and I can also ssh into the box, so it's the console only. Can't switch to different vty's, and the one i'm on is frozen, no response to any keys. It seems to come on more quickly if I do something serious, like a buildkernel. Happened once on startup, but even though rc hadn't finished, I WAS able to ssh into the box and shut it down (indicating to me that rc had finished, just no response from the console). Machine is a 2 processor Tyan Thunder, 1G memory, two Athlons, scsi disks and eide both. It's interesting that you seem to have almost same machine as I have. Tyan Thunder with SCSI and ATA disks, SMP and the only I have the same problem here on an Intel PR440FX dual pentium-pro MB. Manfred It's not the fact that I have an extra, unused on-board video (checked). Also, when the video output stops, the console still works fine for input (keyboard never stops working normally). Also, I can successfully start X just fine. It's just the vty's output that is stopped (all vtys, alt-Fn has no effect on output, only input). It's not wiped, just no further changes. I tried issuing a vidcontrol; before lockup, color change works fine, after, no effect. It's acting as if the mapping in memory to the video buffer has changed. Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: console problem
At 04:07 PM 12/1/2002 -0500, Chuck Robey wrote: I've been on vacation for the last week, so I haven't been watching -current like a good boy should, but I've suddenly been seeing a serious problem, and it *might* not have been reported, and seeing as code freeze is almost here, it's worth risking a bit of embarrassment, I guess. Anyhow, it's the console, it's been locking up. I just retried it with a kernel cvsupped not 2 hours ago, and it's still here. All the vty's lock up, and once even froze the PC speaker (beeping annoyingly at me). There don't seem to be any hung processes. I can use X, and I can also ssh into the box, so it's the console only. Can't switch to different vty's, and the one i'm on is frozen, no response to any keys. It seems to come on more quickly if I do something serious, like a buildkernel. Happened once on startup, but even though rc hadn't finished, I WAS able to ssh into the box and shut it down (indicating to me that rc had finished, just no response from the console). Machine is a 2 processor Tyan Thunder, 1G memory, two Athlons, scsi disks and eide both. Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message I'm seeing the same here and the same on a serial console. Kernel from Friday 29 Nov. 8pm PST sources works So it happened sometime after that Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: console problem
On Sun, 1 Dec 2002, Manfred Antar wrote: Anyhow, it's the console, it's been locking up. I just retried it with a kernel cvsupped not 2 hours ago, and it's still here. All the vty's lock up, and once even froze the PC speaker (beeping annoyingly at me). There don't seem to be any hung processes. I can use X, and I can also ssh into the box, so it's the console only. Can't switch to different vty's, and the one i'm on is frozen, no response to any keys. It seems to come on more quickly if I do something serious, like a buildkernel. Happened once on startup, but even though rc hadn't finished, I WAS able to ssh into the box and shut it down (indicating to me that rc had finished, just no response from the console). Machine is a 2 processor Tyan Thunder, 1G memory, two Athlons, scsi disks and eide both. I'm seeing the same here and the same on a serial console. Kernel from Friday 29 Nov. 8pm PST sources works So it happened sometime after that Manfred OK, did two full rebuilds,once using ssh, once using x. The one using ssh was fine, the one using X did hang the console, but the only way to notice that was because the PC speaker hangs while sounding off. I read the commitlogs, the only one that seemed at all connected with the console was this one (a weak link, admittedly): begin commit message imp 2002/11/29 16:49:43 PST Modified files: sys/kern subr_bus.c Log: devd kernel improvements: 1) Record all device events when devctl is enabled, rather than just when devd has devctl open. This is necessary to prevent races between when a device arrives, and when devd starts. 2) Add hw.bus.devctl_disable to disable devctl, this can also be set as a tunable. 3) Fix async support. Reset nonblocking and async_td in open. remove async flags. 4) Free all memory when devctl is disabled. Approved by: re (blanket) Revision ChangesPath 1.117 +38 -21src/sys/kern/subr_bus.c ===end commit message== I cc'ed Warner on this. Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: console problem
At 06:52 PM 12/1/2002 -0500, Chuck Robey wrote: On Sun, 1 Dec 2002, Manfred Antar wrote: Anyhow, it's the console, it's been locking up. I just retried it with a kernel cvsupped not 2 hours ago, and it's still here. All the vty's lock up, and once even froze the PC speaker (beeping annoyingly at me). There don't seem to be any hung processes. I can use X, and I can also ssh into the box, so it's the console only. Can't switch to different vty's, and the one i'm on is frozen, no response to any keys. It seems to come on more quickly if I do something serious, like a buildkernel. Happened once on startup, but even though rc hadn't finished, I WAS able to ssh into the box and shut it down (indicating to me that rc had finished, just no response from the console). Machine is a 2 processor Tyan Thunder, 1G memory, two Athlons, scsi disks and eide both. I'm seeing the same here and the same on a serial console. Kernel from Friday 29 Nov. 8pm PST sources works So it happened sometime after that Manfred OK, did two full rebuilds,once using ssh, once using x. The one using ssh was fine, the one using X did hang the console, but the only way to notice that was because the PC speaker hangs while sounding off. I read the commitlogs, the only one that seemed at all connected with the console was this one (a weak link, admittedly): begin commit message imp 2002/11/29 16:49:43 PST Modified files: sys/kern subr_bus.c Log: devd kernel improvements: 1) Record all device events when devctl is enabled, rather than just when devd has devctl open. This is necessary to prevent races between when a device arrives, and when devd starts. 2) Add hw.bus.devctl_disable to disable devctl, this can also be set as a tunable. 3) Fix async support. Reset nonblocking and async_td in open. remove async flags. 4) Free all memory when devctl is disabled. Approved by: re (blanket) Revision ChangesPath 1.117 +38 -21src/sys/kern/subr_bus.c ===end commit message== Chuck I tried backing out sub_bus.c to the earlier version and still the same thing happens So it must be something else Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message