in message <[EMAIL PROTECTED]>,
wrote John Baldwin thusly...
>
> On Friday 18 January 2008 08:50:31 am John Baldwin wrote:
> > On Friday 18 January 2008 05:30:06 am Parv wrote:
> > > There was no page fault or trap 12 message when the panic
> > > happened. After some of messages are printed (as in
On Friday 18 January 2008 08:50:31 am John Baldwin wrote:
> On Friday 18 January 2008 05:30:06 am Parv wrote:
> > There was no page fault or trap 12 message when the panic happened.
> > After some of messages are printed (as in dmesg), kdb is entered ...
> >
> > ioapic0: Assigning PCI IRQ 23 to
On Friday 18 January 2008 05:30:06 am Parv wrote:
> (Dropped Vivek K from recipient list; edited the URLs in my previous
> message.)
>
> in message <[EMAIL PROTECTED]>,
> wrote John Baldwin thusly...
> >
> > On Thursday 17 January 2008 06:05:17 am Parv wrote:
> ...
> > > Speaking of MSI being on b
(Dropped Vivek K from recipient list; edited the URLs in my previous
message.)
in message <[EMAIL PROTECTED]>,
wrote John Baldwin thusly...
>
> On Thursday 17 January 2008 06:05:17 am Parv wrote:
...
> > Speaking of MSI being on by default in recent 6-STABLE ... well,
> > that caused my ThinkPad T
On Thursday 17 January 2008 06:05:17 am Parv wrote:
> in message <[EMAIL PROTECTED]>,
> wrote Vivek Khera thusly...
> >
> >
> > On Jan 10, 2008, at 11:09 AM, John Baldwin wrote:
> >
> >>> *: This is the default behavior for 7.0, I have not encountered
> >>> the problem mentioned above on any 1950
in message <[EMAIL PROTECTED]>,
wrote Vivek Khera thusly...
>
>
> On Jan 10, 2008, at 11:09 AM, John Baldwin wrote:
>
>>> *: This is the default behavior for 7.0, I have not encountered
>>> the problem mentioned above on any 1950/2950 boxes so far I have
>>> tested.
>>
>> I will enable MSI by de
