[lkml]   [2002]   [Mar]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subjectboot_cpu_data.x86_vendor corruption on dual AMD
I'm involved with debugging a driver problem which only appears
on dual AMD systems. When the driver's module_init() is called,
boot_cpu_data.x86_vendor is 0 (Intel) instead of 2 (AMD), causing
incorrect code to be selected and eventually an oops.

We've so far traced it to the call to smp_init() in init/main.c.
Before this call, boot_cpu_data.x86_vendor is 2 (correct), but
after the call, the field is 0.

I've been looking through the code but haven't found any obvious
bug candidates, so we've resorted to debug printouts and binary
search. (I'm giving directions, another person is doing the tests
at a remote site, so progress is slow.)

The kernel in question is 2.4.18, but we've seen this in other
2.4 kernels too. Choice of compiler (gcc-2.96-98/egcs-2.91.66)
and CONFIG_MK7 on or off doesn't seem to make any difference.
The box (Tyan) is otherwise stable, and the CPUs are Athlon MPs.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:24    [W:0.043 / U:1.092 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site