On Fri, Mar 19, 2010 at 7:09 AM, David Wolfskill wrote:
> On Fri, Mar 19, 2010 at 01:09:11PM +, Rui Paulo wrote:
>> ...
>> > Do you all have either out-of-tree modules or modules that you did not
>> > re-build when re-compiling your kernel?
>>
>> I have in-tree modules, but I tried a clean bui
On Fri, Mar 19, 2010 at 01:09:11PM +, Rui Paulo wrote:
> ...
> > Do you all have either out-of-tree modules or modules that you did not
> > re-build when re-compiling your kernel?
>
> I have in-tree modules, but I tried a clean build.
I corresponded with kmacy@ a bit yesterday.
Pending resol
On 18 Mar 2010, at 22:15, K. Macy wrote:
> On Thu, Mar 18, 2010 at 1:38 PM, K. Macy wrote:
I have the same panic. I'll try to revert 205266.
>>>
>>> Yes, 205266 is the culprit.
>>
>> Try updating. I've made the change a no-op until I can track the problem
>> down.
>
> Do you all h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/18/10 18:15, K. Macy wrote:
> On Thu, Mar 18, 2010 at 1:38 PM, K. Macy wrote:
I have the same panic. I'll try to revert 205266.
>>>
>>> Yes, 205266 is the culprit.
>>
>> Try updating. I've made the change a no-op until I can track the
On Thu, Mar 18, 2010 at 1:38 PM, K. Macy wrote:
>>>
>>> I have the same panic. I'll try to revert 205266.
>>
>> Yes, 205266 is the culprit.
>
> Try updating. I've made the change a no-op until I can track the problem down.
Do you all have either out-of-tree modules or modules that you did not
re-
>>
>> I have the same panic. I'll try to revert 205266.
>
> Yes, 205266 is the culprit.
Try updating. I've made the change a no-op until I can track the problem down.
-Kip
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/lis
On 18 Mar 2010, at 13:35, David Wolfskill wrote:
> On first reboot after building & installing; yesterday (@r205249) was OK:
>
> 3 1. Boot FreeBSD [default] 3 |_| |_| \___|\___|
> 3 2. Boot FreeBSD with ACPI disabled 3 _ _
> 3 3. Boot FreeBSD in Saf
On 18 Mar 2010, at 13:48, Rui Paulo wrote:
>
> On 18 Mar 2010, at 13:35, David Wolfskill wrote:
>
>> On first reboot after building & installing; yesterday (@r205249) was OK:
>>
>> 3 1. Boot FreeBSD [default] 3 |_| |_| \___|\___|
>> 3 2. Boot FreeBSD with ACPI disabled
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/18/10 09:35, David Wolfskill wrote:
> On first reboot after building & installing; yesterday (@r205249) was OK:
[ .. ]
> --- trap 0xc, eip = 0xc08853d6, esp = 0xc1420bb0, ebp = 0xc1420bd0 ---
> _mtx_lock_flags(f000ff53,0,c0cd0df2,9a2,0,...) at
On first reboot after building & installing; yesterday (@r205249) was OK:
3 1. Boot FreeBSD [default] 3 |_| |_| \___|\___|
3 2. Boot FreeBSD with ACPI disabled 3 _ _
3 3. Boot FreeBSD in Safe Mode 3 | _ \ / | __ \
3 4. Boot Fr
10 matches
Mail list logo