On Wed, 23 May 2007 10:46:05 -0700 (PDT)
Linus Torvalds <[EMAIL PROTECTED]> wrote:
>
>
> On Wed, 23 May 2007, Mike Houston wrote:
> >
> > I still happen to have a Windows Vista install kicking around, so
> > to make sure we're not flogging a dead horse I booted that and
> > let it set up the
On Wed, 23 May 2007 10:46:05 -0700 (PDT)
Linus Torvalds [EMAIL PROTECTED] wrote:
On Wed, 23 May 2007, Mike Houston wrote:
I still happen to have a Windows Vista install kicking around, so
to make sure we're not flogging a dead horse I booted that and
let it set up the yukon2 chip
On Wed, 23 May 2007 10:46:05 -0700 (PDT)
Linus Torvalds <[EMAIL PROTECTED]> wrote:
>
>
> On Wed, 23 May 2007, Mike Houston wrote:
> >
> > I still happen to have a Windows Vista install kicking around, so to
> > make sure we're not flogging a dead horse I booted that and let it
> > set up the
On Wed, 23 May 2007, Mike Houston wrote:
>
> I still happen to have a Windows Vista install kicking around, so to
> make sure we're not flogging a dead horse I booted that and let it
> set up the yukon2 chip and I tested it. (more to make sure that
> eeprom update didn't break it). I used it
On Tue, 22 May 2007 17:00:18 -0700 (PDT)
Linus Torvalds <[EMAIL PROTECTED]> wrote:
> and the load off "sk->sk_prot->ioctl" oopses, because "sk->sk_prot"
> is corrupt and contains 0x8e3cad42, which is not a valid kernel
> pointer.
>
> The other oops is even worse.
>
> I also think it meshes
On Tue, 22 May 2007 18:53:33 -0700 (PDT)
Linus Torvalds <[EMAIL PROTECTED]> wrote:
>
>
> On Tue, 22 May 2007, Stephen Hemminger wrote:
> >
> > It looks like the chip reads the wrong memory sometimes. The problem happens
> > only on the on-board NIC's and only on this kind of motherboard.
>
>
On Tue, 22 May 2007 18:53:33 -0700 (PDT)
Linus Torvalds [EMAIL PROTECTED] wrote:
On Tue, 22 May 2007, Stephen Hemminger wrote:
It looks like the chip reads the wrong memory sometimes. The problem happens
only on the on-board NIC's and only on this kind of motherboard.
Do you know
On Tue, 22 May 2007 17:00:18 -0700 (PDT)
Linus Torvalds [EMAIL PROTECTED] wrote:
and the load off sk-sk_prot-ioctl oopses, because sk-sk_prot
is corrupt and contains 0x8e3cad42, which is not a valid kernel
pointer.
The other oops is even worse.
I also think it meshes with
sky2
On Wed, 23 May 2007, Mike Houston wrote:
I still happen to have a Windows Vista install kicking around, so to
make sure we're not flogging a dead horse I booted that and let it
set up the yukon2 chip and I tested it. (more to make sure that
eeprom update didn't break it). I used it for a
On Wed, 23 May 2007 10:46:05 -0700 (PDT)
Linus Torvalds [EMAIL PROTECTED] wrote:
On Wed, 23 May 2007, Mike Houston wrote:
I still happen to have a Windows Vista install kicking around, so to
make sure we're not flogging a dead horse I booted that and let it
set up the yukon2 chip
On Tue, 22 May 2007, Stephen Hemminger wrote:
>
> It looks like the chip reads the wrong memory sometimes. The problem happens
> only on the on-board NIC's and only on this kind of motherboard.
Do you know if it happens for particular addresses? (Ie, can you tell what
the physical address of
Linus Torvalds wrote:
On Tue, 22 May 2007, Mike Houston wrote:
In this case I actually had the kernel crash. First time for me ever
having a kernel oops! System locked up with keyboard LED's blinking.
Not sure if anyone wants to see all of it (maybe some screwy
userland stuff involved), so
On Tue, 22 May 2007, Mike Houston wrote:
>
> In this case I actually had the kernel crash. First time for me ever
> having a kernel oops! System locked up with keyboard LED's blinking.
>
> Not sure if anyone wants to see all of it (maybe some screwy
> userland stuff involved), so I won't
On Mon, 21 May 2007 21:31:46 -0700
Stephen Hemminger <[EMAIL PROTECTED]> wrote:
> There maybe some hardware level interaction with SATA controller.
> I saw no failures running off i386 kernel of PATA drive and quickly
> see errors with SATA/AHCI and x86_64.
AHCI SATA on i386, but I'm not sure
Linus Torvalds wrote:
>
> I can't really see that being a real problem in this day and age of PCI-X
> etc, but it _used_ to be a possible issue a decade ago. Maybe you've found
> a case where it matters even on modern hardware? We occasionally used to
> set the PCI latency timer to make people
On Mon, 21 May 2007 22:04:26 -0700 (PDT)
Linus Torvalds <[EMAIL PROTECTED]> wrote:
>
>
> On Mon, 21 May 2007, Stephen Hemminger wrote:
> >
> > AHCI on this motherboard doesn't seem to use MSI. The problems occur
> > even if I boot with nomsi.
>
> Have you tried playing with PCI latency
On Mon, 21 May 2007 22:04:26 -0700 (PDT)
Linus Torvalds [EMAIL PROTECTED] wrote:
On Mon, 21 May 2007, Stephen Hemminger wrote:
AHCI on this motherboard doesn't seem to use MSI. The problems occur
even if I boot with nomsi.
Have you tried playing with PCI latency counters etc?
Linus Torvalds wrote:
I can't really see that being a real problem in this day and age of PCI-X
etc, but it _used_ to be a possible issue a decade ago. Maybe you've found
a case where it matters even on modern hardware? We occasionally used to
set the PCI latency timer to make people
On Mon, 21 May 2007 21:31:46 -0700
Stephen Hemminger [EMAIL PROTECTED] wrote:
There maybe some hardware level interaction with SATA controller.
I saw no failures running off i386 kernel of PATA drive and quickly
see errors with SATA/AHCI and x86_64.
AHCI SATA on i386, but I'm not sure that
On Tue, 22 May 2007, Mike Houston wrote:
In this case I actually had the kernel crash. First time for me ever
having a kernel oops! System locked up with keyboard LED's blinking.
Not sure if anyone wants to see all of it (maybe some screwy
userland stuff involved), so I won't include
Linus Torvalds wrote:
On Tue, 22 May 2007, Mike Houston wrote:
In this case I actually had the kernel crash. First time for me ever
having a kernel oops! System locked up with keyboard LED's blinking.
Not sure if anyone wants to see all of it (maybe some screwy
userland stuff involved), so
On Tue, 22 May 2007, Stephen Hemminger wrote:
It looks like the chip reads the wrong memory sometimes. The problem happens
only on the on-board NIC's and only on this kind of motherboard.
Do you know if it happens for particular addresses? (Ie, can you tell what
the physical address of the
On Mon, 21 May 2007, Stephen Hemminger wrote:
>
> AHCI on this motherboard doesn't seem to use MSI. The problems occur
> even if I boot with nomsi.
Have you tried playing with PCI latency counters etc?
Maybe the SATA/AHCI thing is better at saturating the bus, and the sky2
hardware gets
On Tue, 22 May 2007 00:36:15 -0400
Jeff Garzik <[EMAIL PROTECTED]> wrote:
> Stephen Hemminger wrote:
> > There maybe some hardware level interaction with SATA controller.
> > I saw no failures running off i386 kernel of PATA drive and quickly
> > see errors with SATA/AHCI and x86_64.
>
>
> I
Stephen Hemminger wrote:
There maybe some hardware level interaction with SATA controller.
I saw no failures running off i386 kernel of PATA drive and quickly
see errors with SATA/AHCI and x86_64.
I presume AHCI is the only other device in the system using PCI MSI,
when you see problems?
On Mon, 21 May 2007 22:58:06 -0400
Mike Houston <[EMAIL PROTECTED]> wrote:
> On Mon, 21 May 2007 10:37:55 -0700
> Stephen Hemminger <[EMAIL PROTECTED]> wrote:
>
> > On Mon, 21 May 2007 13:10:55 -0400
> > Mike Houston <[EMAIL PROTECTED]> wrote:
> >
> > > On Mon, 21 May 2007 08:45:49 -0700
> > >
On Mon, 21 May 2007 10:37:55 -0700
Stephen Hemminger <[EMAIL PROTECTED]> wrote:
> On Mon, 21 May 2007 13:10:55 -0400
> Mike Houston <[EMAIL PROTECTED]> wrote:
>
> > On Mon, 21 May 2007 08:45:49 -0700
> > Stephen Hemminger <[EMAIL PROTECTED]> wrote:
> >
> > > It's almost certainly a problem with
On Mon, 21 May 2007 13:10:55 -0400
Mike Houston <[EMAIL PROTECTED]> wrote:
> On Mon, 21 May 2007 08:45:49 -0700
> Stephen Hemminger <[EMAIL PROTECTED]> wrote:
>
> > It's almost certainly a problem with the BIOS and hardware (not a
> > sky2) driver issue. Since there are many similar boards and
>
On Mon, 21 May 2007 08:45:49 -0700
Stephen Hemminger <[EMAIL PROTECTED]> wrote:
> It's almost certainly a problem with the BIOS and hardware (not a
> sky2) driver issue. Since there are many similar boards and
> configurations, I made the decision not to enforce restrictions in
> the driver.
>>
On Sun, 20 May 2007 17:05:06 -0400
Mike Houston <[EMAIL PROTECTED]> wrote:
> On Fri, 18 May 2007 22:17:14 -0700 (PDT)
> Linus Torvalds <[EMAIL PROTECTED]> wrote:
>
>
> > Stephen Hemminger (7):
> > [TCP] slow start: Make comments and code logic clearer.
> > *** sky2: remove Gigabyte
Dan Kruchinin napsal(a):
> Hi.
>
> There is a BUG message from SLUB during boot process:
> --
> May 21 05:39:10 midgard kernel: [ 31.177484] BUG: at
> include/linux/slub_def.h:77 kmalloc_index()
> May 21 05:39:10 midgard kernel: [ 31.178355] []
> show_trace_log_lvl+0x1a/0x30
> May 21
Dan Kruchinin napsal(a):
Hi.
There is a BUG message from SLUB during boot process:
--
May 21 05:39:10 midgard kernel: [ 31.177484] BUG: at
include/linux/slub_def.h:77 kmalloc_index()
May 21 05:39:10 midgard kernel: [ 31.178355] [c01062ca]
show_trace_log_lvl+0x1a/0x30
May 21 05:39:10
On Sun, 20 May 2007 17:05:06 -0400
Mike Houston [EMAIL PROTECTED] wrote:
On Fri, 18 May 2007 22:17:14 -0700 (PDT)
Linus Torvalds [EMAIL PROTECTED] wrote:
Stephen Hemminger (7):
[TCP] slow start: Make comments and code logic clearer.
*** sky2: remove Gigabyte 88e8056
On Mon, 21 May 2007 08:45:49 -0700
Stephen Hemminger [EMAIL PROTECTED] wrote:
It's almost certainly a problem with the BIOS and hardware (not a
sky2) driver issue. Since there are many similar boards and
configurations, I made the decision not to enforce restrictions in
the driver.
May 20
On Mon, 21 May 2007 13:10:55 -0400
Mike Houston [EMAIL PROTECTED] wrote:
On Mon, 21 May 2007 08:45:49 -0700
Stephen Hemminger [EMAIL PROTECTED] wrote:
It's almost certainly a problem with the BIOS and hardware (not a
sky2) driver issue. Since there are many similar boards and
On Mon, 21 May 2007 10:37:55 -0700
Stephen Hemminger [EMAIL PROTECTED] wrote:
On Mon, 21 May 2007 13:10:55 -0400
Mike Houston [EMAIL PROTECTED] wrote:
On Mon, 21 May 2007 08:45:49 -0700
Stephen Hemminger [EMAIL PROTECTED] wrote:
It's almost certainly a problem with the BIOS and
On Mon, 21 May 2007 22:58:06 -0400
Mike Houston [EMAIL PROTECTED] wrote:
On Mon, 21 May 2007 10:37:55 -0700
Stephen Hemminger [EMAIL PROTECTED] wrote:
On Mon, 21 May 2007 13:10:55 -0400
Mike Houston [EMAIL PROTECTED] wrote:
On Mon, 21 May 2007 08:45:49 -0700
Stephen Hemminger
Stephen Hemminger wrote:
There maybe some hardware level interaction with SATA controller.
I saw no failures running off i386 kernel of PATA drive and quickly
see errors with SATA/AHCI and x86_64.
I presume AHCI is the only other device in the system using PCI MSI,
when you see problems?
On Tue, 22 May 2007 00:36:15 -0400
Jeff Garzik [EMAIL PROTECTED] wrote:
Stephen Hemminger wrote:
There maybe some hardware level interaction with SATA controller.
I saw no failures running off i386 kernel of PATA drive and quickly
see errors with SATA/AHCI and x86_64.
I presume AHCI
On Mon, 21 May 2007, Stephen Hemminger wrote:
AHCI on this motherboard doesn't seem to use MSI. The problems occur
even if I boot with nomsi.
Have you tried playing with PCI latency counters etc?
Maybe the SATA/AHCI thing is better at saturating the bus, and the sky2
hardware gets upset
Hi.
There is a BUG message from SLUB during boot process:
--
May 21 05:39:10 midgard kernel: [ 31.177484] BUG: at
include/linux/slub_def.h:77 kmalloc_index()
May 21 05:39:10 midgard kernel: [ 31.178355] []
show_trace_log_lvl+0x1a/0x30
May 21 05:39:10 midgard kernel: [ 31.179263] []
On Fri, 18 May 2007 22:17:14 -0700 (PDT)
Linus Torvalds <[EMAIL PROTECTED]> wrote:
> Stephen Hemminger (7):
> [TCP] slow start: Make comments and code logic clearer.
> *** sky2: remove Gigabyte 88e8056 restriction ***
> sky2: PHY register settings
> sky2: keep track of
On Sunday, 20 May 2007 15:01, Krzysztof Halasa wrote:
> "Rafael J. Wysocki" <[EMAIL PROTECTED]> writes:
>
> > Running 'make -j' kernel compilation on my test box (Athlon64 X2, 2 SATA
> > drives
> > with 6 software RAID1 ext3 and reiserfs partitions, 2 GB of RAM) makes it
> > completely
"Rafael J. Wysocki" <[EMAIL PROTECTED]> writes:
> Running 'make -j' kernel compilation on my test box (Athlon64 X2, 2 SATA
> drives
> with 6 software RAID1 ext3 and reiserfs partitions, 2 GB of RAM) makes it
> completely unresponsive. I can't even move the mouse pointer when it's
> running, I
Hi,
On Saturday, 19 May 2007 07:17, Linus Torvalds wrote:
>
> It's out there, both patches/tarballs and git trees are updated (although
> mirroring might still be ongoing)
>
> Various random fixes all over - the shortlog (appended) is fairly
> readable. The most notable ones are probably more
Hi,
On Saturday, 19 May 2007 07:17, Linus Torvalds wrote:
It's out there, both patches/tarballs and git trees are updated (although
mirroring might still be ongoing)
Various random fixes all over - the shortlog (appended) is fairly
readable. The most notable ones are probably more SLUB
Rafael J. Wysocki [EMAIL PROTECTED] writes:
Running 'make -j' kernel compilation on my test box (Athlon64 X2, 2 SATA
drives
with 6 software RAID1 ext3 and reiserfs partitions, 2 GB of RAM) makes it
completely unresponsive. I can't even move the mouse pointer when it's
running, I can't log
On Sunday, 20 May 2007 15:01, Krzysztof Halasa wrote:
Rafael J. Wysocki [EMAIL PROTECTED] writes:
Running 'make -j' kernel compilation on my test box (Athlon64 X2, 2 SATA
drives
with 6 software RAID1 ext3 and reiserfs partitions, 2 GB of RAM) makes it
completely unresponsive. I can't
On Fri, 18 May 2007 22:17:14 -0700 (PDT)
Linus Torvalds [EMAIL PROTECTED] wrote:
Stephen Hemminger (7):
[TCP] slow start: Make comments and code logic clearer.
*** sky2: remove Gigabyte 88e8056 restriction ***
sky2: PHY register settings
sky2: keep track of receive
Hi.
There is a BUG message from SLUB during boot process:
--
May 21 05:39:10 midgard kernel: [ 31.177484] BUG: at
include/linux/slub_def.h:77 kmalloc_index()
May 21 05:39:10 midgard kernel: [ 31.178355] [c01062ca]
show_trace_log_lvl+0x1a/0x30
May 21 05:39:10 midgard kernel: [ 31.179263]
Linus Torvalds wrote:
>
> It's out there, both patches/tarballs and git trees are updated (although
> mirroring might still be ongoing)
>
trivia
make: Entering directory `/home/bor/src/linux-git'
GEN /home/bor/build/linux-2.6.22/Makefile
scripts/kconfig/conf -s arch/i386/Kconfig
Linus Torvalds wrote:
It's out there, both patches/tarballs and git trees are updated (although
mirroring might still be ongoing)
trivia
make: Entering directory `/home/bor/src/linux-git'
GEN /home/bor/build/linux-2.6.22/Makefile
scripts/kconfig/conf -s arch/i386/Kconfig
It's out there, both patches/tarballs and git trees are updated (although
mirroring might still be ongoing)
Various random fixes all over - the shortlog (appended) is fairly
readable. The most notable ones are probably more SLUB fixes, and the
epoll optimizations and cleanups.
But there's
It's out there, both patches/tarballs and git trees are updated (although
mirroring might still be ongoing)
Various random fixes all over - the shortlog (appended) is fairly
readable. The most notable ones are probably more SLUB fixes, and the
epoll optimizations and cleanups.
But there's
54 matches
Mail list logo
