From: C. R. O. <cr...@nc...> - 2004-06-25 17:03:14
|
Dan Aloni wrote: > On Thu, Jun 24, 2004 at 06:37:39PM +0200, Jaroslaw Kowalski wrote: >> I upgraded but that didn't fix the issue. I could repeat the error >> performing more or less the same steps. OS: Win2003 EE/Athlon XP >> 2500+=20 >>=20 >> This happened when I rpmmed on my colinux over SSH. After the crash >> the network became unusable but the rest of the system stayed >> responsive.=20 >=20 > Very odd, I'll take a further look into this. On a possibly related note, I installed the 20040622 snapshot last night and it made my Windows XP box somewhat unresponsive. Clicking on the "Start" button would not always bring up the menu, system was generally very sluggish. XP native Bridged Networking is in use. Not sure if it helps, but I have a panel on the front of my machine that shows the current POST codes while my machine is booting up. When I started the 20040622 snapshot that panel changed from displaying "FF" (the general ASUS "finished the POST and everything is OK" code) to a "2". I didn't notice this with the release version. --cro |
From: C. R. O. <cr...@nc...> - 2004-06-26 16:58:02
|
IA0KDQoJDQoNCglDYW4geW91IHBsZWFzZSBjaGVjayB5b3VyIEFTVVMgbWFudWFsIGZvciB3aGF0 ICIyIiBtZWFucz8NCg0KSSB0cmllZCB0byBkdXBsaWNhdGUgdGhpcyBtb3JuaW5nLiAgSSBnb3Qg dGhyZWUgZGlmZmVyZW50IGNvZGVzOiAxZCwgMWYsIGFuZCAyZS4gIFRoZSBBc3VzIG1hbnVhbCBz YXlzIHRoZXNlIGNvZGVzIGFyZSBhbGwgIlJlc2VydmVkIi4gIFRoZSBBd2FyZCBQT1NUIGNvZGVz IGxpc3QgYXQNCiANCmh0dHA6Ly9iaW9zY2VudHJhbC5jb20vcG9zdGNvZGVzL2F3YXJkYmlvcy5o dG0NCiANCmlzbid0IGhlbHBpbmcgbXVjaCBlaXRoZXIgKFRoaXMgQXN1cyBNb2JvLCBhbiBBN1Yy NjZFLCBpcyBiYXNlZCBvbiBBd2FyZCkuDQoNCi0tDQpEYW4gQWxvbmkNCmRhLXhAY29saW51eC5v cmcNCg0KDQo= |
From: <co...@ew...> - 2004-06-26 18:59:04
|
> I tried to duplicate this morning. I got three different codes: 1d, 1f, > and 2e. The Asus manual says these codes are all "Reserved". The Award > POST codes list at > http://bioscentral.com/postcodes/awardbios.htm Your display will show anything written to port 80 so it isn't necessarily the motherboard issuing the post code. If somewhere in the kernel it does something like this: mov dl, 80 outb dl, 1d ....then you will see 1d show up on the display. I have seen in the kernel code where it will use writing to port 80 as an extra long io delay but I've not looked in a while. This could be random and meaningless as far as the port-80 codes are concerned. Compile this and see what ya get: #include <sys/io.h> main() { int i; ioperm(0x80, 1, 1); for (i = 0; i < 0xFF; i++) { outb(i & 0xFF, 0x80); usleep(500000); } } It should cycle through 00-FF on your display in 1/2 second increments if my guess is right. Also, I don't recall if it was port 80 or port 0x80 so you might change that if I'm wrong. I don't have a post code to test the card. Depending on your gcc version you might need to compile w/ "-O". Ahh, here it is! It is 0x80. See asm-i386/io.h. 2.4.20 shows this: 314 #define __SLOW_DOWN_IO "\noutb %%al,$0x80" What would we do without http://lxr.linux.no? -Eric -- Eric Wheeler Vice President National Security Concepts, Inc. PO Box 3567 Tualatin, OR 97062 http://www.nsci.us/ Voice: (503) 293-7656 Fax: (503) 885-0770 |
From: Dan A. <da...@co...> - 2004-06-26 10:01:29
|
On Fri, Jun 25, 2004 at 10:02:38AM -0700, C. R. Oldham wrote: > Dan Aloni wrote: > > On Thu, Jun 24, 2004 at 06:37:39PM +0200, Jaroslaw Kowalski wrote: > >> I upgraded but that didn't fix the issue. I could repeat the error > >> performing more or less the same steps. OS: Win2003 EE/Athlon XP > >> 2500+ > >> > >> This happened when I rpmmed on my colinux over SSH. After the crash > >> the network became unusable but the rest of the system stayed > >> responsive. > > > > Very odd, I'll take a further look into this. > > On a possibly related note, I installed the 20040622 snapshot last night > and it made my Windows XP box somewhat unresponsive. Clicking on the > "Start" button would not always bring up the menu, system was generally > very sluggish. XP native Bridged Networking is in use. > > Not sure if it helps, but I have a panel on the front of my machine that > shows the current POST codes while my machine is booting up. When I > started the 20040622 snapshot that panel changed from displaying "FF" > (the general ASUS "finished the POST and everything is OK" code) to a > "2". I didn't notice this with the release version. Look to me like we might have not completely eliminated all the "badness" that happens when the 2.6.x version of the coLinux kernel. Can you please check your ASUS manual for what "2" means? -- Dan Aloni da...@co... |