On Fri, Apr 20, 2007 at 08:28:10AM -0700, Jeremy Fitzhardinge wrote:
 > Dave Jones wrote:
 > > -BUG: at arch/i386/kernel/sched-clock.c:170 init_sched_clock()
 > > - [<c01091b5>] show_trace_log_lvl+0x1a/0x30
 > > - [<c010980c>] show_trace+0x12/0x14
 > > - [<c01098cb>] dump_stack+0x16/0x18
 > > - [<c0468dbd>] init_sched_clock+0x58/0x9b
 > > - [<c0461502>] init+0x14b/0x241
 > > - [<c0108d97>] kernel_thread_helper+0x7/0x10
 > > - =======================
 > >
 > > heh, one for Ingo :)
 > Andi, I think.  I've got his firstfloor.org patches applied to this kernel.

Ah, I saw you patched in CFS too, and thought it may be related.

 > > So most of the differences seem to be BIOS/firmware rather than hardware. 
 > > The PCI bus layout is identical for eg.
 > 
 > Do you have Intel wireless?  I realized one chance I'd made was to swap
 > the Atheros wireless with Intel, since it just seems to work better
 > overall.  I'd never had any major suspend/resume problems that I could
 > attribute to madwifi though (lots of minor wifi-related ones though).

yeah, the intel wireless.  Same as teh one in your pci.gz attachment..
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network 
Connection (rev 02)
        Subsystem: Intel Corporation Unknown device 1010
        Flags: bus master, fast devsel, latency 0, IRQ 21

        Dave

-- 
http://www.codemonkey.org.uk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to