> According to Alan Cox:
> > > eth0: Setting full-duplex based on MII #3 link partner capability of 41e1.
> > > Starting system log daemon: syslogd klogd.
> > > kmalloc: Size (4294959124) too large
> >
> > Something tried to allocate negative bytes.
>
> Yep, but what ? Is there a way to let kmalloc print a stack trace
> when this happens? *(int*)0=0; should cause an oops, right ?
There's another way too. (used ikd salesman:) If you want to know what
led up to any event that you know where it's happening, you can enable
ktracer and insert SUSPEND_MCOUNT at the failure point. This will stop
further tracing. From there, it's just a matter of working backward
through the ktrace output.
-Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/