I have just upgraded an old K6 200 box to 2.6.23.1. It has oopsed
overnight. Unfortunately the kernel is tainted by madwifi modules. As it
is used headless as a wireless router, I can't remove them, but the
trace looks to be in the pdflush/ext2 code.
Config attached. Let me know if you want more
I have just upgraded an old K6 200 box to 2.6.23.1. It has oopsed
overnight. Unfortunately the kernel is tainted by madwifi modules. As it
is used headless as a wireless router, I can't remove them, but the
trace looks to be in the pdflush/ext2 code.
Config attached. Let me know if you want more
This oops appeared over night on a box running 2.6.23-rc5 (recent with the
tcp_input.c fix).
I can't find a similar one reported.
Mark
BUG: unable to handle kernel NULL pointer dereference at virtual address
007e
printing eip:
c02625bf
*pde =
Oops: 0002 [#1]
PREEMPT
Modules
This oops appeared over night on a box running 2.6.23-rc5 (recent with the
tcp_input.c fix).
I can't find a similar one reported.
Mark
BUG: unable to handle kernel NULL pointer dereference at virtual address
007e
printing eip:
c02625bf
*pde =
Oops: 0002 [#1]
PREEMPT
Modules
On Thu, Sep 06, 2007 at 03:25:55PM +0530, Satyam Sharma wrote:
> This is a GCC bug (regression, actually, as you've found out) -- no two
> ways about it. Although different from the kind Jeff mentioned couple days
> back -- that was about wising GCC up to false positives and /not/ emitting
>
On Thu, Sep 06, 2007 at 03:25:55PM +0530, Satyam Sharma wrote:
This is a GCC bug (regression, actually, as you've found out) -- no two
ways about it. Although different from the kind Jeff mentioned couple days
back -- that was about wising GCC up to false positives and /not/ emitting
version.
This program has absolutely no warranty.
Mark Hindley
Thanks,
Mark
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FA
On Tue, Sep 04, 2007 at 11:17:57AM +0200, Steffen Klassert wrote:
> The only warning that I was able to trigger with gcc 4.2 is in the case of a
> .config
> without PCI support. In this case I get
>
> drivers/net/3c59x.c: In function 'vortex_up':
> drivers/net/3c59x.c:1672: warning: 'err' is
> > > drivers/net/3c59x.c:1495: warning: 'err' may be used uninitialized in
> > > this function
> >
> > This came in with the recently applied
> > 3c59x-check-return-of-pci_enable_device patch
> > from Mark Hindley. I just compiled it on a PCI o
be used uninitialized in
this function
This came in with the recently applied
3c59x-check-return-of-pci_enable_device patch
from Mark Hindley. I just compiled it on a PCI only machine so far,
therefore I did
not notice the warning yet.
Hmm, the .config I built with had PCI=y as well
On Tue, Sep 04, 2007 at 11:17:57AM +0200, Steffen Klassert wrote:
The only warning that I was able to trigger with gcc 4.2 is in the case of a
.config
without PCI support. In this case I get
drivers/net/3c59x.c: In function 'vortex_up':
drivers/net/3c59x.c:1672: warning: 'err' is used
version.
This program has absolutely no warranty.
Mark Hindley
Thanks,
Mark
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org
I have now got an oops trace out of this box, which I presume has been
the cause of the previously observed hangs.
To my inexperienced eye it looks like it is related to via-rhine.
Thanks
Mark
BUG: unable to handle kernel NULL pointer dereference at virtual address
0025
Hi,
I recently been trying 2.6.2{2,3} kernels on a box with a Via C3
processor. It was previously running 2.6.18 without problems. I have
been getting random hangs, sysrq unresponsive, nothing in logs or on
serial console. Require power cycle to reset. Take between a few minutes
and days to
I have now got an oops trace out of this box, which I presume has been
the cause of the previously observed hangs.
To my inexperienced eye it looks like it is related to via-rhine.
Thanks
Mark
BUG: unable to handle kernel NULL pointer dereference at virtual address
0025
On Sun, Jul 29, 2007 at 11:19:47AM -0400, Alan Stern wrote:
> On Sun, 29 Jul 2007, Mark Hindley wrote:
>
> > Hi,
> >
> > I have just tried 2.6.23-rc1 on my Acer Aspire 1350.
> >
> > On boot I get the following error as the uhci_hcd module is loaded:
> >
On Sun, Jul 29, 2007 at 11:19:47AM -0400, Alan Stern wrote:
On Sun, 29 Jul 2007, Mark Hindley wrote:
Hi,
I have just tried 2.6.23-rc1 on my Acer Aspire 1350.
On boot I get the following error as the uhci_hcd module is loaded:
Jul 28 18:23:20 mercury kernel: ACPI: PCI Interrupt
commit 36d139ccebba6a1082b743fbedb53c5a5097987c
Author: Mark Hindley <[EMAIL PROTECTED]>
Date: Sat Jul 21 22:56:08 2007 +0100
Check return of pci_enable_device in vortex_up().
Signed-off-by: Mark Hindley <[EMAIL PROTECTED]>
diff --git a/drivers/net/3c59x.c b/drivers
commit 36d139ccebba6a1082b743fbedb53c5a5097987c
Author: Mark Hindley [EMAIL PROTECTED]
Date: Sat Jul 21 22:56:08 2007 +0100
Check return of pci_enable_device in vortex_up().
Signed-off-by: Mark Hindley [EMAIL PROTECTED]
diff --git a/drivers/net/3c59x.c b/drivers/net/3c59x.c
index
Alan Cox writes:
> I think the problem here thought isnt the 3c509 and SB card, its the kernel
> plug and play code. You might want to try building kernels with no PnP support
> at all and see how they behave
I agree. I have been having problems with isapnp reliably finding my
ALS100 since
Alan Cox writes:
I think the problem here thought isnt the 3c509 and SB card, its the kernel
plug and play code. You might want to try building kernels with no PnP support
at all and see how they behave
I agree. I have been having problems with isapnp reliably finding my
ALS100 since
Philipp Rumpf writes:
> On Wed, Jan 10, 2001 at 05:55:05PM +0100, Daniel Phillips wrote:
> > Mark Hindley wrote:
> > > I am running 2.4.0 final. I got the following failed paging request which
> > > produced a complete freeze.
> > >
> > > As you
Philipp Rumpf writes:
On Wed, Jan 10, 2001 at 05:55:05PM +0100, Daniel Phillips wrote:
Mark Hindley wrote:
I am running 2.4.0 final. I got the following failed paging request which
produced a complete freeze.
As you can see it was precipitated by cron starting to run some
Hi,
I am running 2.4.0 final. I got the following failed paging request which
produced a complete freeze.
As you can see it was precipitated by cron starting to run some
housekeeping stuff overnight.
Has anyone else had prblems?
Mark
Jan 10 02:25:01 hindleyhome /USR/SBIN/CRON[3823]: (root)
Hi,
I am running 2.4.0 final. I got the following failed paging request which
produced a complete freeze.
As you can see it was precipitated by cron starting to run some
housekeeping stuff overnight.
Has anyone else had prblems?
Mark
Jan 10 02:25:01 hindleyhome /USR/SBIN/CRON[3823]: (root)
I can not mount an cd in either my cdrom or cdrw drives. Both are ide
drives using scsi-ide emulation.
During the mount the logs show:
Nov 23 10:03:27 hindleyhome kernel: VFS: Disk change detected on device sr(11,0)
Nov 23 10:03:29 hindleyhome kernel: ISO 9660 Extensions: Microsoft Joliet
I can not mount an cd in either my cdrom or cdrw drives. Both are ide
drives using scsi-ide emulation.
During the mount the logs show:
Nov 23 10:03:27 hindleyhome kernel: VFS: Disk change detected on device sr(11,0)
Nov 23 10:03:29 hindleyhome kernel: ISO 9660 Extensions: Microsoft Joliet
I conceed. The opl3 pnp patch still stands.
I will have to look again at why the sb driver wasn't finding the mpu.
Sigh
Mark
Mark Hindley
Director of the Music Centre
University of St Andrews
01334 462226/7
http://www.st-andrews.ac.uk/services/music
-
To unsubscribe from this list: send
>It changes the command line properties people already use. It also cannot be
>neccessary since 'uart401' is static.
So why does the kernel command-line uart401=1 make a builtin uart401
driver look for the mpu at 0x1 rather than persuade the sb driver to to do
a pnp lookup for it?
art401 to uart401probe to avoid conflict
with uart401 module
+ * Bugfix ALS-110 pnp info
+ * Mark Hindley <[EMAIL PROTECTED]>
*/
#include
@@ -195,7 +199,7 @@
static int isapnpjump = 0;
static int multiple= 1;
static int reverse = 0;
-static int uart401 = 0;
to uart401probe to avoid conflict
with uart401 module
+ * Bugfix ALS-110 pnp info
+ * Mark Hindley [EMAIL PROTECTED]
*/
#include linux/config.h
@@ -195,7 +199,7 @@
static int isapnpjump = 0;
static int multiple= 1;
static int reverse = 0;
-static int uart401 = 0;
+static
It changes the command line properties people already use. It also cannot be
neccessary since 'uart401' is static.
So why does the kernel command-line uart401=1 make a builtin uart401
driver look for the mpu at 0x1 rather than persuade the sb driver to to do
a pnp lookup for it?
Mark Hindley
I conceed. The opl3 pnp patch still stands.
I will have to look again at why the sb driver wasn't finding the mpu.
Sigh
Mark
Mark Hindley
Director of the Music Centre
University of St Andrews
01334 462226/7
http://www.st-andrews.ac.uk/services/music
-
To unsubscribe from this list: send
>On Sat, 11 Nov 2000, Stephen Thomas wrote:
>
>> Mark Hindley wrote:
>> > I am trying to setup my ALS 110 soundcard under my build of kernel
>> > 2.4.0-test10.
>> >
>> > I have built in isapnp support and also the sb and opl3 drivers.
>> >
On Sat, 11 Nov 2000, Stephen Thomas wrote:
Mark Hindley wrote:
I am trying to setup my ALS 110 soundcard under my build of kernel
2.4.0-test10.
I have built in isapnp support and also the sb and opl3 drivers.
However, even though I pass opl3=0x388 on the Kernel command line all
I
I am trying to setup my ALS 110 soundcard under my build of kernel
2.4.0-test10.
I have built in isapnp support and also the sb and opl3 drivers.
The sb driver works fine other than complaining about a missing 16 bit
DMA (which I understand is missing from the card anyway). I can play
and
I am trying to setup my ALS 110 soundcard under my build of kernel
2.4.0-test10.
I have built in isapnp support and also the sb and opl3 drivers.
The sb driver works fine other than complaining about a missing 16 bit
DMA (which I understand is missing from the card anyway). I can play
and
I was having trouble booting new builds of both 2.2.17 and
2.4.0-test8. They both boot as far as
loop: registered device at major 7
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:pio, hdb:pio
I was having trouble booting new builds of both 2.2.17 and
2.4.0-test8. They both boot as far as
loop: registered device at major 7
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:pio, hdb:pio
No joy with specifying the memory size. I have 64MB. I have tried mem=64M and
32/16/8. Still just reboots.
Any other suggestions?
Mark
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at
No joy with specifying the memory size. I have 64MB. I have tried mem=64M and
32/16/8. Still just reboots.
Any other suggestions?
Mark
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at
gt; Any suggestions about where to go? How can I be sure the hardware is okay?
>> How can I isolate what is causing the reboot?
>
>serial console, for one.
I only have one machine, so I think that is out, although I am getting out
of my depth here. What would I need?
Mark
Mark Hi
I have just spent a frustrating day trying to rebuild the 2.2.17 kernel for
my new Debian potato installation.
It configures and builds fine. I am using 'make bzdisk' and then booting
from the resulting floppy.
When the new kernel boots it just reboots itself. The screen flash is so
brief that
I have just spent a frustrating day trying to rebuild the 2.2.17 kernel for
my new Debian potato installation.
It configures and builds fine. I am using 'make bzdisk' and then booting
from the resulting floppy.
When the new kernel boots it just reboots itself. The screen flash is so
brief that
the hardware is okay?
How can I isolate what is causing the reboot?
serial console, for one.
I only have one machine, so I think that is out, although I am getting out
of my depth here. What would I need?
Mark
Mark Hindley
Director of the Music Centre
University of St Andrews
01334 462226/7
http
45 matches
Mail list logo
