x86: split e820 reserved entries record to late v2
Quoted 38 lines
I installed the kernel and it booted OK. There was a delay when my MTA (exim4) loaded, but that happens sometimes. However, I got a call trace I've never seen before. This could just be a fluke, but I'm passing it along in case it's meaningful. I grabbed the trace on TTY1 by logging in on TTY2 and using 'setterm -append 1':
===== SETTERM OUTPUT =====
Clocksource tsc unstable (delta = -98677795 ns)
NETDEV WATCHDOG: eth0 (r8169): transmit timed out------------[ cut here ]------------ WARNING: at net/sched/sch_generic.c:221 dev_watchdog+0x21e/0x250() Modules linked in: ipv6 cpufreq_userspace pcspkr 8250_pnp 8250 serial_core evdev Pid: 0, comm: swapper Not tainted 2.6.27-rc4.080829.yh-patches-tip #1 Call Trace: [] warn_on_slowpath+0x64/0xb0 [] printk+0x4e/0x5a [] lock_timer_base+0x34/0x70 [] __mod_timer+0xb0/0xd0 [] getnstimeofday+0x48/0xc0 [] dev_watchdog+0x21e/0x250 [] scheduler_tick+0xcf/0x220 [] cascade+0x7b/0xa0 [] dev_watchdog+0x0/0x250 [] run_timer_softirq+0x13c/0x210 [] ktime_get+0xc/0x50 [] __do_softirq+0x73/0xf0 [] call_softirq+0x1c/0x30 [] do_softirq+0x35/0x70 [] irq_exit+0x8d/0x90 [] smp_apic_timer_interrupt+0x86/0xd0 [] apic_timer_interrupt+0x66/0x70 [] lapic_next_event+0x0/0x20 [] default_idle+0x3a/0x40 [] c1e_idle+0x34/0xe0 [] cpu_idle+0x56/0xa0 ---[ end trace 28095e4c2b529c2a ]---
Quoted 6 lines
r8169: eth0: link up
===== END SETTERM OUTPUT =====Other than this strangeness, everything seems OK with your patches. This looks like some random networking annoyance to me, not really related to the regression patches, but I'll let better minds be the judge of that.
Update: this strangeness cannot be reproduced with a couple of reboots, so I'm thinking it was just bad luck that it happened while testing your patches.
Thanks Yinghai,
DW
Quoted 7 lines · David Witbrodt
Update: this strangeness cannot be reproduced with a couple of reboots, so I'm thinking it was just bad luck that it happened while testing your patches.
can you check tip/master now? Ingo fixed it arlready...
YH