On 11/22/21 12:55 PM, Warner Losh wrote:
On Mon, Nov 22, 2021 at 10:51 AM Chuck Tuffli wrote:
On Mon, Nov 22, 2021 at 9:34 AM Chris wrote:
On 2021-11-22 08:47, Chuck Tuffli wrote:
Running on a recent-ish -current
# uname -a
FreeBSD stargate.tuffli.net 14.0-CURRENT FreeBSD 14.0-CURRENT
On 8/2/19 6:19 PM, Steve Kargl wrote:
I have a Dell XPS 13 that reports the wifi chip is
a Qualcomm Atheros 6147. I've found Adrain's WIP
driver, and built it. I'm seeing the panic reported
at
https://lists.freebsd.org/pipermail/freebsd-current/2019-February/072769.html
Does anyone have a
On 2019-05-21 07:06, Vladimir Kondratyev wrote:
On 20.05.2019 16:23, Anthony Jenkins wrote:
I'm running (a somewhat dated) FreeBSD 13.0-CURRENT (git commit
68c8581f7, Tue. Feb 12 13:01:55 2019) on a UEFI laptop with an Intel
UHD display, booting a ZFS root filesystem (gptzfsboot(8)). I'm
regards
Markus
Anthony Jenkins via freebsd-x11 writes:
I'm running (a somewhat dated) FreeBSD 13.0-CURRENT (git commit
68c8581f7, Tue. Feb 12 13:01:55 2019) on a UEFI laptop with an Intel
UHD display, booting a ZFS root filesystem (gptzfsboot(8)).
CORRECTION: I installed (merged) /boot/boot1
kernel module from the graphics/drm-current-kmod port is loaded by
rc.conf(4)'s 'kld_list' variable. When I do manually set the console
resolution using 'mode 1', it is reset to maximum resolution when
i915(4) is loaded.
Thanks in advance,
Anthony Jenkins
_
eue=0xf80002ced800) at /usr/src/sys/kern/subr_taskqueue.c:467
#23 0x807cb628 in taskqueue_thread_loop (arg=) at
/usr/src/sys/kern/subr_taskqueue.c:773
#24 0x80730354 in fork_exit (callout=0x807cb5a0
, arg=0xfe00b6c8c078,
frame=0xfe00aa8279c0) at /usr/src/sy
On 12/19/18 10:41 AM, Anthony Jenkins wrote:
[snip]
I'm not feeling too confident about the condition of the FreeBSD ig4
driver; the PCI attach code was calling pci_alloc_msi() wrong, passing
a pointer to the rid (0) instead of a pointer to a count variable, and
not passing
On 12/10/18 3:57 PM, John Baldwin wrote:
On 12/10/18 12:19 PM, Ian Lepore wrote:
On Mon, 2018-12-10 at 14:42 -0500, Anthony Jenkins wrote:
On 12/10/18 1:26 PM, John Baldwin wrote:
On 12/10/18 9:00 AM, Anthony Jenkins wrote:
Hi all,
I'm trying to port an Intel PCI I2C controller from Linux
On 12/11/18 9:02 AM, Emiel Kollof wrote:
Anthony Jenkins schreef op 2018-12-10 18:00:
Hi all,
I'm trying to port an Intel PCI I2C controller from Linux to
FreeBSD. Linux represents this device as an MFD (multi-function
device), meaning it has these "sub-devices" that can be
On 12/10/18 1:26 PM, John Baldwin wrote:
On 12/10/18 9:00 AM, Anthony Jenkins wrote:
Hi all,
I'm trying to port an Intel PCI I2C controller from Linux to FreeBSD.
Linux represents this device as an MFD (multi-function device), meaning
it has these "sub-devices" that can be handed of
rolled via
access to a PCI memory region and an IRQ), but it's a sub-device of an
actual PCI device (lpss(4)) attached to PCI.
How would my ig4_lpss attachment get information from the lpss(4) driver
about what it probed?
Thanks,
Anthony Jenkins
References:
- intel-lpss.c -
https://g
tics' for 'Synaptics Touchpad'
[24.843]Option "_source" "server/udev"
[24.843]Option "name" "Synaptics Touchpad"
[24.843]Option "path" "/dev/input/event3"
[24.843]Option "device" "/dev/input/event3"
set module_path /boot/kernel # ?
I don't think module_path is set to its default "/boot/kernel;/boot/modules"
when booting to loader(8) prompt...
Anthony Jenkins
From: Steven Hartland <kill...@multiplay.co.uk>
To: freebsd-current@freebsd.o
On 03/03/2016 09:39 AM, Jakob Alvermark wrote:
> Hi,
>
> On Thu, March 3, 2016 14:46, Anthony Jenkins wrote:
>
>> The other issue is just me being jealous of EFI Linux showing up in a
>> toplevel BIOS boot menu:
>>
>> Selecting "F9 - Boot Device O
- Boot From EFI File
- Notebook Hard Drive
How did Ubuntu get in there? Some attribute of its EFI boot file that
tells the BIOS (or boot manager EFI app) to add an entry for it? How do
I get FreeBSD in there?
Thanks!
--
Anthony Jenkins
___
fre
On 02/22/2016 11:51 AM, Hans Petter Selasky wrote:
> On 02/22/16 17:39, Anthony Jenkins wrote:
>>
>>
>> On 02/22/2016 02:11 AM, Hans Petter Selasky wrote:
>>> On 02/22/16 03:16, Anthony Jenkins wrote:
>>>> Yes. I have an eGalax touchscreen and it's doin
On 02/22/2016 02:11 AM, Hans Petter Selasky wrote:
> On 02/22/16 03:16, Anthony Jenkins wrote:
>> Yes. I have an eGalax touchscreen and it's doing the same thing. The
>> number of items it's reporting is 256 (according to my preliminary
>> debugging), causing the warning.
Yes. I have an eGalax touchscreen and it's doing the same thing. The
number of items it's reporting is 256 (according to my preliminary
debugging), causing the warning. I think these things are a special
subclass of HID for multitouch touchscreens which we don't support (yet).
Anthony
---
>>
>> However, I am not sure about an exact mechanism of the hard system hang that
>> I
>> experienced without the patch.
>>
>> BTW, I noticed that only very few drivers make explicit calls to
>> pci_set_powerstate and pci_save_state/pci_restore_state.
>>
was
hoping to debug some SMP on the new box /whine.
--
Anthony Jenkins
http://www.mindspring.com/~abjenkins/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
not mangling
these terms, I've only done Linux kernel work to-date). Is the pcm code
maintainer looking into this also?
--
Anthony Jenkins
http://www.mindspring.com/~abjenkins/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
with the coredump a bit.
--
Anthony Jenkins
http://www.mindspring.com/~abjenkins/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
you have to do
is 'unset acpi_load' at the boot loader prompt. I had tried 'set
acpi_load=NO', and finally 'unset module_path' to keep the kernel from
finding /boot/kernel/acpi.ko.
Hope this helps,
Anthony Jenkins
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
On Monday 2002-July-08 19:47, Don Lewis wrote:
On 8 Jul, Anthony Jenkins wrote:
I've been looking at the pcm code and I can see where it locks, then
allocates memory with the M_WAITOK flag thing. I'm wondering if there's
a standard procedure for fixing these... would I just nail down
On Monday 2002-July-08 14:08, Josef Karthauser wrote:
On a new kernel I appear to be getting dumps now (along with the crashes
;). Actually it's pretty stable, but there are random crashes occuring,
usually I come back to the machine when I've not used it for a new hours
and find it in
had something to do with it. I'll hand-copy the trace
here; any debugging info needed while my box is stuck at the debugger,
lemme know:
--
Anthony Jenkins
Additional TCP options:.
Starting background filesystem checks
Wed Jul 3 13:24:09 EDT 2002
FreeBSD/i386 (foo) (ttyv0)
login: mode
locked in
*Giant state and sucking 50% the CPU/WCPU measure.)
--
Anthony Jenkins
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
more adept at FreeBSD kernel work, so any debugging
suggestions or requests for more info would be greatly appreciated.
TIA,
Anthony Jenkins
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
), regardless of whether I'm using the device or not.
Luckily this mouse has a USB-to-PS/2 adapter. Guess I don't need sound
or USB
Anthony
Anthony Jenkins wrote:
Hi,
Ever since cvsup'ing/building a new kernel a couple weeks ago I've had
ridiculously high interrupt state percentages shown
29 matches
Mail list logo
