On 2016-02-11 14:40, Larry Rosenman wrote:
> On 2016-02-11 14:25, Kristof Provost wrote:
>
> On 11 Feb 2016, at 21:23, Larry Rosenman wrote:
> From which system(s) perspective do you want the packet captures?
> (Firewall, FreeBSD, Windows)? I wouldn't expect it to make much of a
> difference
Spoke too soon...
I applied the patch (kern_module.diff - which was successful)
# cd /usr/src# patch
To: Hans Petter Selasky ; "freebsd-current@freebsd.org"
Sent: Thursday, 11 February 2016, 22:19
Subject: Re: Open Sound System - OSS "soundon" command causes KERNEL PANIC
FreeBSD-11
We
On 2016-02-11 14:25, Kristof Provost wrote:
>> On 11 Feb 2016, at 21:23, Larry Rosenman wrote:
>> From which system(s) perspective do you want the packet captures?
>> (Firewall, FreeBSD, Windows)?
> I wouldn't expect it to make much of a difference in this case.
> Let's start with whatever is e
> On 11 Feb 2016, at 21:23, Larry Rosenman wrote:
>
> From which system(s) perspective do you want the packet captures?
> (Firewall, FreeBSD, Windows)?
I wouldn’t expect it to make much of a difference in this case.
Let’s start with whatever is easiest.
Regards,
Kristof
___
On 2016-02-11 04:14, Kristof Provost wrote:
On 2016-02-10 20:38:02 (-0600), Larry Rosenman wrote:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206904
I've also posted lots of info to freebsd-net, and not gotten any
response.
Summary:
Cable Modem-> EM0 on a pfSense Firewall (FreeBSD 10.1
This is actually triggered when using large blocks.
"recordsize=1M"
going back to 128k and I no longer panic.
On Thu, Feb 11, 2016 at 9:10 AM, Daniel Nebdal wrote:
> On Thu, Feb 11, 2016 at 3:04 PM, Hans Petter Selasky
> wrote:
> > On 02/11/16 15:00, Daniel Nebdal wrote:
> >>
> >> plugging in
On Thu, Feb 11, 2016 at 3:04 PM, Hans Petter Selasky wrote:
> On 02/11/16 15:00, Daniel Nebdal wrote:
>>
>> plugging in a
>> USB keyboard post-panic didn't do much
>
>
> Hi,
>
> USB enumeration is disabled in the debugger. You need to plug it in
> pre-crash :-) Same with any USB crash dump device(
On Sat, Jan 30, 2016 at 6:16 AM, Ultima wrote:
> Just upgraded from 10-STABLE to head r295051 and I still have kernel
> panics. I then tested with bsdinstall and found that the panics no longer
> occur. I believe the issue is that some of my datasets are set to
> recordsize=1M, this is most likel
On 02/11/16 15:00, Daniel Nebdal wrote:
plugging in a
USB keyboard post-panic didn't do much
Hi,
USB enumeration is disabled in the debugger. You need to plug it in
pre-crash :-) Same with any USB crash dump device(s).
--HPS
___
freebsd-current@fr
Well done!!
Fixed. Thanks!
From: Hans Petter Selasky
To: Greg Quinlan ; "freebsd-current@freebsd.org"
Sent: Thursday, 11 February 2016, 17:54
Subject: Re: Open Sound System - OSS "soundon" command causes KERNEL PANIC
FreeBSD-11
On 02/11/16 03:02, Greg Quinlan wrote:
> Hi HPS,
>
On Thu, Feb 11, 2016 at 11:19:56AM +0100, Hans Petter Selasky wrote:
> On 02/11/16 11:14, Konstantin Belousov wrote:
> > On Thu, Feb 11, 2016 at 07:54:57AM +0100, Hans Petter Selasky wrote:
> >> On 02/11/16 03:02, Greg Quinlan wrote:
> >>> Hi HPS,
> >>> Note: Does not happen on FreeBSD 10.1-Stable!
On 02/11/16 11:14, Konstantin Belousov wrote:
On Thu, Feb 11, 2016 at 07:54:57AM +0100, Hans Petter Selasky wrote:
On 02/11/16 03:02, Greg Quinlan wrote:
Hi HPS,
Note: Does not happen on FreeBSD 10.1-Stable!
Yes, that's because WITNESS is off in 10.x by default.
Does the attached patch solv
On 2016-02-10 20:38:02 (-0600), Larry Rosenman wrote:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206904
>
> I've also posted lots of info to freebsd-net, and not gotten any
> response.
>
> Summary:
>
> Cable Modem-> EM0 on a pfSense Firewall (FreeBSD 10.1, pfSense 2.2.6)
>
On Thu, Feb 11, 2016 at 07:54:57AM +0100, Hans Petter Selasky wrote:
> On 02/11/16 03:02, Greg Quinlan wrote:
> > Hi HPS,
> > Note: Does not happen on FreeBSD 10.1-Stable!
> >
>
> Yes, that's because WITNESS is off in 10.x by default.
>
> Does the attached patch solve your problem?
No, the patch
On 10/02/2016 01:02, John Baldwin wrote:
> I'm actually not certain of what triggered the fault. The check that emits
> the printf should also be failing the kldload with EEXIST (but that doesn't
> work for the case where both are compiled into the kernel). The new driver
> should have just never
15 matches
Mail list logo