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 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
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"
Console problem with ALT-F# keys
Hello Current, I have recently discovered a problem and I was wondering if anyone has experienced this or if they can verify that it is not just my hardware. 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) I have recently installed this into a new machine and had chance to use the console for building kernel and ports (not to mention moving tons of files from one server to another.) What I am seeing is when I switch consoles from one to another, if I do them quickly there is no problem - Things work as I expect them to. However, if I keep the ALT key pressed for about 5 seconds and then hit another F key, it acts as if I had released the ALT key and presents only the F-key code to the console. I have tried a few experiments to try and help diagnose the problem. All the below tests were done with a keyboard attached to the PS2 port: 1) If you hold down the ALT key only for any length of time, the next F key will register as ALT-F# 2) If you do an ALT-F key and then continue to hold the ALT key down and within about 5 seconds strike another F-key, the console will see the ALT-F key correctly. 3) If you do an ALT-F key and the continue to hold the ALT key - wait more than about 5 seconds and then strike another f-key, the console will only see the F-Key strike. Since this is a new machine and the first install of BSD on it, I don't have anything to eliminate a hardware quirk with it. Its possible it may be the machine - I don't know. Would someone be willing to try the above tests and if its a BSD issue, I can submit a PR for it. Thanks 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
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
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
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
> 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 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
> > 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, 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: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
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 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
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, 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 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
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
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 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
console problem
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
Re: stange console problem
Chad David wrote: > Problem solved. > > cp GENERIC.hints DEBUG.hints > > Without them it isn't very happy... did I miss this as a requirement > somewhere, or is my hardware/timing just a little funky? Yes, you were not reading the commit messages or UPDATING or -current. You should have a /boot/device.hints for your machine. You dont need GENERIC.hints or DEBUG.hints if you have this set up correctly. As a head start, you can cp GENERIC.hints to /boot/device.hints and you're done. config and 'make install' will not let you forget this.. Were you installing your kernel by hand or something? > Chad > > On Tue, Jan 30, 2001 at 04:03:10PM +0100, Rogier R. Mulhuijzen wrote: > > > > >None of this has any bearing on the problem, which was caused by a bug > > >in gensetdefs.pl. Please update your source tree and rebuild your > > >kernel. > > > > Eek. I had the gensetdefs.pl problem too, but my machine just seemed to > > lock. He says his machine does go on running. > > > > I have been pretty tied up lately, so maybe I read his post a bit too quick ly. > > > > DocWilco > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: stange console problem
Problem solved. cp GENERIC.hints DEBUG.hints Without them it isn't very happy... did I miss this as a requirement somewhere, or is my hardware/timing just a little funky? Chad On Tue, Jan 30, 2001 at 04:03:10PM +0100, Rogier R. Mulhuijzen wrote: > > >None of this has any bearing on the problem, which was caused by a bug > >in gensetdefs.pl. Please update your source tree and rebuild your > >kernel. > > Eek. I had the gensetdefs.pl problem too, but my machine just seemed to > lock. He says his machine does go on running. > > I have been pretty tied up lately, so maybe I read his post a bit too quickly. > > DocWilco > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: stange console problem
>None of this has any bearing on the problem, which was caused by a bug >in gensetdefs.pl. Please update your source tree and rebuild your >kernel. Eek. I had the gensetdefs.pl problem too, but my machine just seemed to lock. He says his machine does go on running. I have been pretty tied up lately, so maybe I read his post a bit too quickly. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: stange console problem
"Rogier R. Mulhuijzen" <[EMAIL PROTECTED]> writes: > Have you tried removing the 'makeoptions' line and using 'config -g > ' instead? > [...] > Also, when you copy the GENERIC file to another name, do you update the > ident line? None of this has any bearing on the problem, which was caused by a bug in gensetdefs.pl. Please update your source tree and rebuild your kernel. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: stange console problem
> >If I copy GENERIC to DEBUG and recompile the kernel it will not >boot properly copy the file back to GENERIC and everything >seems fine? > >I have searched the archives and read UPDATING, but nothing jumps >out at me. > >Does anybody have any idea where I could look next? > >Chad > >On Sun, Jan 28, 2001 at 10:16:02PM -0700, Chad David wrote: > > On a current from last Sunday I recompiled > > a new kernel with just makeoptions DEBUG=-g > > and options DDB added to GENERIC and when > > I boot I see the first few spins of the loader > > booting the kernel and then all video output stops. > > After the boot finishs I get a login prompt but no > > keyboard response or video after that. Have you tried removing the 'makeoptions' line and using 'config -g ' instead? That's how I build my debug kernels, and that worked fine last time I did it (last week or so). Also, when you copy the GENERIC file to another name, do you update the ident line? This should normally not matter but you never know with debugging kernels. In both cases you would need to examine the config utility. DocWilco To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: stange console problem
In reply to my own post (which nobody has replied to, perhaps because I never actually phrased a question :-) )... I have found that if the kernel config file is named GENERIC, it will boot just fine; otherwise, I loose the console. I have done a cvsup tonight as well as a make world and many different kernels. If I copy GENERIC to DEBUG and recompile the kernel it will not boot properly copy the file back to GENERIC and everything seems fine? I have searched the archives and read UPDATING, but nothing jumps out at me. Does anybody have any idea where I could look next? Chad On Sun, Jan 28, 2001 at 10:16:02PM -0700, Chad David wrote: > On a current from last Sunday I recompiled > a new kernel with just makeoptions DEBUG=-g > and options DDB added to GENERIC and when > I boot I see the first few spins of the loader > booting the kernel and then all video output stops. > After the boot finishs I get a login prompt but no > keyboard response or video after that. > > I am able to ssh into the box, and all seems well > from the "inside". If I recompile GENERIC it works > just fine. > > Here is a dmesg, I noticed a few things but nothing I know > how to fix.. > > Chad > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
stange console problem
On a current from last Sunday I recompiled a new kernel with just makeoptions DEBUG=-g and options DDB added to GENERIC and when I boot I see the first few spins of the loader booting the kernel and then all video output stops. After the boot finishs I get a login prompt but no keyboard response or video after that. I am able to ssh into the box, and all seems well from the "inside". If I recompile GENERIC it works just fine. Here is a dmesg, I noticed a few things but nothing I know how to fix.. Chad Copyright (c) 1992-2001 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 5.0-CURRENT #2: Sun Jan 28 23:17:40 MST 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/DEBUG Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (367.50-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x660 Stepping = 0 Features=0x183f9ff real memory = 134152192 (131008K bytes) avail memory = 125595648 (122652K bytes) Preloaded elf kernel "kernel" at 0xc04e7000. Pentium Pro MTRR support enabled WARNING: Driver mistake: destroy_dev on 154/0 Using $PIR table, 6 entries at 0xc00fded0 apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xe000-0xe01f at device 7.2 on pci0 pci_cfgintr_virgin: using routable PCI-only interrupt 11 pci_cfgintr: 0:7 INTD routed to irq 11 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at 7.3 (no driver attached) xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xe400-0xe47f mem 0xe500-0xe57f irq 11 at device 9.0 on pci0 xl0: Ethernet address: 00:10:4b:6e:0a:87 miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x0> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sio0: <16550A-compatible COM port> at port 0x3f8-0x407 irq 4 on isa0 sio0: type 16550A fdc0: at port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on isa0 ppc0: at port 0x378-0x387 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 sio1: <16550A-compatible COM port> at port 0x2f8-0x307 irq 3 on isa0 sio1: type 16550A sbc0: at port 0x220-0x22f,0x331-0x332,0x388-0x38b irq 5 drq 1,5 on isa0 pcm0: on sbc0 xl0 XXX: driver didn't initialize queue mtx lp0 XXX: driver didn't initialize queue mtx gif0 XXX: driver didn't initialize queue mtx gif1 XXX: driver didn't initialize queue mtx gif2 XXX: driver didn't initialize queue mtx gif3 XXX: driver didn't initialize queue mtx lo0 XXX: driver didn't initialize queue mtx ppp0 XXX: driver didn't initialize queue mtx faith0 XXX: driver didn't initialize queue mtx ad0: 6187MB [13410/15/63] at ata0-master UDMA33 Mounting root from ufs:/dev/ad0s4a To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Odd console problem
Under VMware 2... Under world and kernel of yesterday, between the sio1 and sbc0 kernel messages during console boot, various character cease to appear on the screen. (e.g. r, t, u & s). All virtual consoles appear completely unable to display these characters. Otherwise the systems appears sane. Booting an old April 20th Kernel is fine. Any ideas please, before I get in too deep...? -- Mark Knight PGP Public Key: finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
