On Fri, Jan 10, 2014 at 02:31:31AM +0100, Rafael J. Wysocki wrote:
[..]
> > It is a fresh instance of kernel booting and it is initializing its data
> > structures fresh. It is *not* re-initializing ACPI in same kernel.
>
> I know. The problem is that the BIOS is generally not stateless and it
On 01/09/2014 10:57 PM, Yasuaki Ishimatsu wrote:
> (2014/01/10 6:44), Vivek Goyal wrote:
>> On Thu, Jan 09, 2014 at 04:34:16PM -0500, KOSAKI Motohiro wrote:
>>> On Thu, Jan 9, 2014 at 10:00 AM, Vivek Goyal wrote:
On Thu, Jan 09, 2014 at 12:00:29AM +0100, Rafael J. Wysocki wrote:
On 01/09/2014 10:57 PM, Yasuaki Ishimatsu wrote:
(2014/01/10 6:44), Vivek Goyal wrote:
On Thu, Jan 09, 2014 at 04:34:16PM -0500, KOSAKI Motohiro wrote:
On Thu, Jan 9, 2014 at 10:00 AM, Vivek Goyal vgo...@redhat.com wrote:
On Thu, Jan 09, 2014 at 12:00:29AM +0100, Rafael J. Wysocki wrote:
On Fri, Jan 10, 2014 at 02:31:31AM +0100, Rafael J. Wysocki wrote:
[..]
It is a fresh instance of kernel booting and it is initializing its data
structures fresh. It is *not* re-initializing ACPI in same kernel.
I know. The problem is that the BIOS is generally not stateless and it
(2014/01/10 6:44), Vivek Goyal wrote:
On Thu, Jan 09, 2014 at 04:34:16PM -0500, KOSAKI Motohiro wrote:
On Thu, Jan 9, 2014 at 10:00 AM, Vivek Goyal wrote:
On Thu, Jan 09, 2014 at 12:00:29AM +0100, Rafael J. Wysocki wrote:
[..]
The system then panics and the kdump/kexec kernel boots. During
On Thursday, January 09, 2014 04:44:25 PM Vivek Goyal wrote:
> On Thu, Jan 09, 2014 at 04:34:16PM -0500, KOSAKI Motohiro wrote:
> > On Thu, Jan 9, 2014 at 10:00 AM, Vivek Goyal wrote:
> > > On Thu, Jan 09, 2014 at 12:00:29AM +0100, Rafael J. Wysocki wrote:
> > >
> > > [..]
> > >> > The system
On Thursday, January 09, 2014 10:00:53 AM Vivek Goyal wrote:
> On Thu, Jan 09, 2014 at 12:00:29AM +0100, Rafael J. Wysocki wrote:
>
> [..]
> > > The system then panics and the kdump/kexec kernel boots. During this boot
> > > ACPi is initialized and the kernel (as can be seen above)
> >
> >
On 01/09/2014 04:44 PM, Vivek Goyal wrote:
> On Thu, Jan 09, 2014 at 04:34:16PM -0500, KOSAKI Motohiro wrote:
>> On Thu, Jan 9, 2014 at 10:00 AM, Vivek Goyal wrote:
>>> On Thu, Jan 09, 2014 at 12:00:29AM +0100, Rafael J. Wysocki wrote:
>
> Makes sense. Something like "acpi_no_memhotplug" or
On Thu, Jan 09, 2014 at 04:34:16PM -0500, KOSAKI Motohiro wrote:
> On Thu, Jan 9, 2014 at 10:00 AM, Vivek Goyal wrote:
> > On Thu, Jan 09, 2014 at 12:00:29AM +0100, Rafael J. Wysocki wrote:
> >
> > [..]
> >> > The system then panics and the kdump/kexec kernel boots. During this
> >> > boot
> >>
On Thu, Jan 9, 2014 at 10:00 AM, Vivek Goyal wrote:
> On Thu, Jan 09, 2014 at 12:00:29AM +0100, Rafael J. Wysocki wrote:
>
> [..]
>> > The system then panics and the kdump/kexec kernel boots. During this boot
>> > ACPi is initialized and the kernel (as can be seen above)
>>
>> Which is a bug.
On Thu, Jan 09, 2014 at 12:00:29AM +0100, Rafael J. Wysocki wrote:
[..]
> > The system then panics and the kdump/kexec kernel boots. During this boot
> > ACPi is initialized and the kernel (as can be seen above)
>
> Which is a bug. You're not supposed to initialize ACPI twice in a row.
[CC
On Thu, Jan 09, 2014 at 12:00:29AM +0100, Rafael J. Wysocki wrote:
[..]
The system then panics and the kdump/kexec kernel boots. During this boot
ACPi is initialized and the kernel (as can be seen above)
Which is a bug. You're not supposed to initialize ACPI twice in a row.
[CC lkml,
On Thu, Jan 9, 2014 at 10:00 AM, Vivek Goyal vgo...@redhat.com wrote:
On Thu, Jan 09, 2014 at 12:00:29AM +0100, Rafael J. Wysocki wrote:
[..]
The system then panics and the kdump/kexec kernel boots. During this boot
ACPi is initialized and the kernel (as can be seen above)
Which is a
On Thu, Jan 09, 2014 at 04:34:16PM -0500, KOSAKI Motohiro wrote:
On Thu, Jan 9, 2014 at 10:00 AM, Vivek Goyal vgo...@redhat.com wrote:
On Thu, Jan 09, 2014 at 12:00:29AM +0100, Rafael J. Wysocki wrote:
[..]
The system then panics and the kdump/kexec kernel boots. During this
boot
On 01/09/2014 04:44 PM, Vivek Goyal wrote:
On Thu, Jan 09, 2014 at 04:34:16PM -0500, KOSAKI Motohiro wrote:
On Thu, Jan 9, 2014 at 10:00 AM, Vivek Goyal vgo...@redhat.com wrote:
On Thu, Jan 09, 2014 at 12:00:29AM +0100, Rafael J. Wysocki wrote:
Makes sense. Something like
On Thursday, January 09, 2014 10:00:53 AM Vivek Goyal wrote:
On Thu, Jan 09, 2014 at 12:00:29AM +0100, Rafael J. Wysocki wrote:
[..]
The system then panics and the kdump/kexec kernel boots. During this boot
ACPi is initialized and the kernel (as can be seen above)
Which is a bug.
On Thursday, January 09, 2014 04:44:25 PM Vivek Goyal wrote:
On Thu, Jan 09, 2014 at 04:34:16PM -0500, KOSAKI Motohiro wrote:
On Thu, Jan 9, 2014 at 10:00 AM, Vivek Goyal vgo...@redhat.com wrote:
On Thu, Jan 09, 2014 at 12:00:29AM +0100, Rafael J. Wysocki wrote:
[..]
The system
(2014/01/10 6:44), Vivek Goyal wrote:
On Thu, Jan 09, 2014 at 04:34:16PM -0500, KOSAKI Motohiro wrote:
On Thu, Jan 9, 2014 at 10:00 AM, Vivek Goyal vgo...@redhat.com wrote:
On Thu, Jan 09, 2014 at 12:00:29AM +0100, Rafael J. Wysocki wrote:
[..]
The system then panics and the kdump/kexec
18 matches
Mail list logo