Re: BIOS causes (exposes?) modprobe (load_module) kernel oops

On Tue, 2006-03-21 at 20:05 -0800, John Z. Bohach wrote:
> Linux 2.6.14.2, yeah, I know, and sorry if this has been fixed...but read on, please,
> this is a new take...

at least enable CONFIG_KALLSYMS to get us a readable backtrace

-
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/

---

• Follow-Ups:
  • Re: BIOS causes (exposes?) modprobe (load_module) kernel oops
    • From: "John Z. Bohach" <[email protected]>

• References:
  • BIOS causes (exposes?) modprobe (load_module) kernel oops
    • From: "John Z. Bohach" <[email protected]>

• Prev by Date: [patch 1/4] cpufreq_conservative: update and align of codebase
• Next by Date: Re: [patch 1/4] cpufreq_conservative: update and align of codebase
• Previous by thread: BIOS causes (exposes?) modprobe (load_module) kernel oops
• Next by thread: Re: BIOS causes (exposes?) modprobe (load_module) kernel oops
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]