Kernel panic after adding ehci & acpi

[Louis LeBlanc]

On 01/30/05 04:32 PM, Louis LeBlanc sat at the `puter and typed:
> This is wierd.  I just rebuilt and installed a new kernel with a few
> additions, including ehci and acpi, and the kernel seems to be
> panicking on startup.  In 5 years, I've never had a FreeBSD kernel
> actually panic on me.
> 
> I already have the uhci and ohci devices in my kernel config, I added
> the ehci in hopes of getting USB 2.0 support.  That part seems to be
> fine:
> Tn 30 15:59:42 keyslapper kernel: ehci0: [GIANT-LOCKED]
> Jan 30 15:59:42 keyslapper kernel: ehci_pci_attach: companion usb0
> Jan 30 15:59:42 keyslapper kernel: ehci_pci_attach: companion usb1
> Jan 30 15:59:42 keyslapper kernel: ehci_pci_attach: companion usb2
> Jan 30 15:59:42 keyslapper kernel: ehci_pci_attach: companion usb3
> Jan 30 15:59:42 keyslapper kernel: usb4: EHCI version 1.0
> Jan 30 15:59:42 keyslapper kernel: usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3
> Jan 30 15:59:42 keyslapper kernel: usb4: <EHCI (generic) USB 2.0 controller> on ehci0
> Jan 30 15:59:42 keyslapper kernel: usb4: USB revision 2.0
> Jan 30 15:59:42 keyslapper kernel: uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
> Jan 30 15:59:42 keyslapper kernel: uhub4: 8 ports with 8 removable, self powered
> 
> 
> The panic message is as follows (partially)
> Fatal Trap 12: Page Fualt while in kernel mode
> CPUID = 0; acpi id = 00
> Fault Firtual Address 0x20
> Fault code = Supervisor read, Page not present
> instruction pointer 0x8:0xC0440AEA
> 
> etc.
> 
> I had to restart in safe mode, but I can't figure out where the
> problem is.  Any ideas?
> 
> I had hoped to use the acpi module to monitor system temperature, but
> I suspect it is the cause of the problem.  If so, I'd just as soon
> remove it.  I am aware that some of the acpi stuff is experimental,
> so I'm wondering if anyone can confirm that this is the problem, or
> can confirm that the CPU_ENABLE_TCC cpu options work on the Dell
> Dimension 8300 (P4 3.0G w/HT).
> 
> My last boot showed some log data on the acpi0 device, but this safe
> boot didn't.  Should I just eliminate it and skip the CPU_ENABLE_TCC
> option?


I know I'm responding to my own post, but here's the update:

It appears the problem is the ehci device for usb 2.0 support.

I'm confused.  I added this as specified in the handbook, and it
implies pretty clearly that it won't conflict with the USB 1.0
drivers, but I'm getting constant panics.  Once I removed the ehci
device from the kernel, it works fine.

I also noticed that the handbook said this was buggy code. Is there
any idea when this will be stabilized?

BTW, I'm running FreeBSD 5.3 RELEASE-p3; I neglected to mention that
before.

TIA
Lou
-- 
Louis LeBlanc                          FreeBSD-at-keyslapper-DOT-net
Fully Funded Hobbyist,                   KeySlapper Extrordinaire :)
Key fingerprint = C5E7 4762 F071 CE3B ED51  4FB8 AF85 A2FE 80C8 D9A2

idleness, n.:
  Leisure gone to seed.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20050130/db944fa1/attachment.bin