Reply
 
Thread Tools Display Modes
  #1  
Old 06-03-2013, 03:19 PM
CraigRodrigues CraigRodrigues is offline
Junior Member
 
Join Date: Jun 2013
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default HP Elitebook 8460p install problem, Bluetooth related
I had a problem installing PC-BSD 9.1 Isotope Edition on
an HP Elitebook 8460p ( http://h10010.www1.hp.com/wwpc/pscmi...oks/8460p.html ).

During the installation process, the FreeBSD kernel panicked and the system rebooted, before the installer had a chance to run.
Here is a picture I was able to take of the kernel panic before the
system rebooted:



From this backtrace:

#0 kdb_backtrace
#1 panic
#2 trap_fatal
#3 trap_pfault
#4 trap
#5 calltrap
#6 ubt_attach
#7 device_attach
#8 usb_probe_and_attach
#9 uhub_explore
#10 uhub_explore
#11 usb_bus_explore
#12 usb_process
#13 fork_exit
#14 fork_trampoline


It looks like the kernel is panicking when it is trying
to attach a Bluetooth device (ubt_attach). This laptop *does* have Bluetooth.

To move things along, I pressed the button on the laptop
which disables networking. I rebooted the laptop,
and the kernel did not panic any more, and I was able to run
the PC-BSD installer.

Has anyone else reported this problem?
I'll look into fixing this if I have time.
Reply With Quote
  #2  
Old 06-23-2013, 09:16 PM
moesasji moesasji is offline
Junior Member
 
Join Date: Jun 2013
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
Default
You are not the only one seeing this "issue" as I get pretty much the same backtrace when trying to install the rolling PC-BSD release using the PCBSD9.1-RELEASE-06-03-2013-x64-USBFULL.img iso.

Only difference is that in my case the backtrace mentions the urtw driver (RTL8187L on an Asus P5K premium motherboard) which uses the urtw driver instead of ubt. So it doesn't appear to be (just) a Bluetooth problem. Also affects wireless, which is a bit more problematic.

The strange thing is that this computer is running a FreeBSD 9.1 Stable snapshot (20130512-r250582) from the 13th of May under which wireless works without issues. So overall pretty surprising to see this happening.

ps) Upon disabling this wireless card in Bios indeed boots properly. To backtrace is indeed triggered by the wireless card.
Reply With Quote
  #3  
Old 06-29-2013, 08:30 AM
moesasji moesasji is offline
Junior Member
 
Join Date: Jun 2013
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
Default
@CraigRodrigues: In case you indeed can find the time to look into this problem. The following thread on the freeBSD mailing list appears to show a very similar backtrace.

http://unix.derkeiler.com/Mailing-Li.../msg00427.html

That thread suggests the problem is associated with VImage.
Reply With Quote
  #4  
Old 07-07-2013, 12:44 AM
CraigRodrigues CraigRodrigues is offline
Junior Member
 
Join Date: Jun 2013
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default
This problem is directly related to VIMAGE being enabled in the PC-BSD kernel config.

I got the exact same kernel panic as the one described here:

http://lists.freebsd.org/pipermail/f...ay/000325.html

Doing some kernel debugging, I got this stack trace:

#0 doadump (textdump=<value optimized out>) at pcpu.h:234
#1 0xffffffff80923e86 in kern_reboot (howto=260) at /usr/home/rodrigc/freebsd/9/sys/kern/kern_shutdown.c:449
#2 0xffffffff80924387 in panic (fmt=0x1 <Address 0x1 out of bounds>) at /usr/home/rodrigc/freebsd/9/sys/kern/kern_shutdown.c:637
#3 0xffffffff80ce97f0 in trap_fatal (frame=0xc, eva=<value optimized out>) at /usr/home/rodrigc/freebsd/9/sys/amd64/amd64/trap.c:879
#4 0xffffffff80ce9b51 in trap_pfault (frame=0xffffff811e2b7700, usermode=0) at /usr/home/rodrigc/freebsd/9/sys/amd64/amd64/trap.c:795
#5 0xffffffff80cea104 in trap (frame=0xffffff811e2b7700) at /usr/home/rodrigc/freebsd/9/sys/amd64/amd64/trap.c:463
#6 0xffffffff80cd3433 in calltrap () at /usr/home/rodrigc/freebsd/9/sys/amd64/amd64/exception.S:228
#7 0xffffffff81cc0bbd in ng_make_node_common (type=0xffffffff81cb6000, nodepp=0xfffffe0124d9c310)
at /usr/home/rodrigc/freebsd/9/sys/modules/netgraph/netgraph/../../../netgraph/ng_base.c:669
#8 0xffffffff81cb320e in ubt_attach (dev=0xfffffe01041f1d00)
at /usr/home/rodrigc/freebsd/9/sys/modules/netgraph/bluetooth/ubt/../../../../netgraph/bluetooth/drivers/ubt/ng_ubt.c:461
#9 0xffffffff80956c9c in device_attach (dev=0xfffffe01041f1d00) at device_if.h:180
#10 0xffffffff8078a61e in usb_probe_and_attach (udev=0xfffffe0124580000, iface_index=<value optimized out>)
at /usr/home/rodrigc/freebsd/9/sys/dev/usb/usb_device.c:1183
#11 0xffffffff80792c4e in uhub_explore (udev=0xfffffe000900c000) at /usr/home/rodrigc/freebsd/9/sys/dev/usb/usb_hub.c:272
#12 0xffffffff80792c74 in uhub_explore (udev=0xfffffe0007ee2000) at /usr/home/rodrigc/freebsd/9/sys/dev/usb/usb_hub.c:286
#13 0xffffffff8077ce46 in usb_bus_explore (pm=<value optimized out>) at /usr/home/rodrigc/freebsd/9/sys/dev/usb/controller/usb_controller.c:359
#14 0xffffffff80796da3 in usb_process (arg=<value optimized out>) at /usr/home/rodrigc/freebsd/9/sys/dev/usb/usb_process.c:169
#15 0xffffffff808f1cef in fork_exit (callout=0xffffffff80796cd0 <usb_process>, arg=0xffffff8001c3cdb0, frame=0xffffff811e2b7b00)
at /usr/home/rodrigc/freebsd/9/sys/kern/kern_fork.c:988
#16 0xffffffff80cd395e in fork_trampoline () at /usr/home/rodrigc/freebsd/9/sys/amd64/amd64/exception.S:602
#17 0x0000000000000000 in ?? ()


and the error occurred on line 669 in ng_base.c:

#7 0xffffffff81cc0bbd in ng_make_node_common (type=0xffffffff81cb6000, nodepp=0xfffffe0124d9c310)
at /usr/home/rodrigc/freebsd/9/sys/modules/netgraph/netgraph/../../../netgraph/ng_base.c:669
669 node->nd_ID = V_nextID++; /* 137/sec for 1 year before wrap */
(kgdb) l
664
665 /* Get an ID and put us in the hash chain. */
666 IDHASH_WLOCK();
667 for (; { /* wrap protection, even if silly */
668 node_p node2 = NULL;
669 node->nd_ID = V_nextID++; /* 137/sec for 1 year before wrap */
670
671 /* Is there a problem with the new number? */
672 NG_IDHASH_FIND(node->nd_ID, node2); /* already taken? */
673 if ((node->nd_ID != 0) && (node2 == NULL)) {


It turns out that when VIMAGE is defined in the kernel, V_nextID is not an int any more,
it is a macro. line 669 expands to something that looks like:

node->nd_ID = (*(__typeof(vnet_entry_nextID)*) (((((__curthread())->td_vnet))->vnet_data_base) + (uintptr_t)&vnet_entry_nextID))++;

I am not sure where in that macro expansion the error is occurring.


I am not familiar with the Netgraph code, but in the above URL
on the freebsd-virtualization list, there was some discussion
between the authors of VIMAGE, netgraph, and bluetooth stack,
but there were no followup items.

Last edited by CraigRodrigues; 07-07-2013 at 02:29 AM. Reason: Fix typo
Reply With Quote
  #5  
Old 07-19-2013, 09:04 PM
CraigRodrigues CraigRodrigues is offline
Junior Member
 
Join Date: Jun 2013
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default
I exchanged some e-mails from a few FreeBSD developers,
Adrian Chadd and Marko Zec, and based on some patches
they had, I committed this patch to FreeBSD:

http://lists.freebsd.org/pipermail/s...ly/071878.html

With this patch, I could boot PC-BSD on my HP Elitebook 8460p
with VIMAGE enabled in the kernel, and it booted fine.
I even tested Bluetooth, by pairing my Samsung Galaxy SIII phone
to my laptop, and transferring a file over bluetooth with obexapp.

@moesasji: I think my patch also fixes problems with USB Ethernet devices
+ VIMAGE.
I don't have a USB Ethernet device to test it, so if you could
test the patch, that would be great.
Reply With Quote
  #6  
Old 07-22-2013, 06:43 PM
kmoore134's Avatar
kmoore134 kmoore134 is offline
Administrator
 
Join Date: May 2005
Location: Knoxville, TN
Posts: 2,568
Thanks: 0
Thanked 162 Times in 127 Posts
Default
Craig, is this the same patch you had sent me earlier? I included that one in the most recent ISOs.
__________________
----
Kris Moore
PC-BSD Founder
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 08:11 AM.


Powered by vBulletin® Version 3.8.5
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.

Copyright 2005-2010, The PC-BSD Project. PC-BSD and the PC-BSD logo are registered trademarks of iXsystems.
All other content is freely available for sharing under the terms of the Creative Commons Attribution License.