Hi,
I have a 1 GHz Coppermine PC with 512 MB RAM, and it is failing to boot with
the nmi_watchdog=1
option. This kernel was rebuilt after doing a "make mrproper". The dmesg log
follows:
Linux version 2.6.24 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070925 (Red Hat
4.1.2-33)) #1
SMP PREEMPT Sat
Hi,
I have tried to boot a 2.6.24 kernel on my 1 GHz Coppermine / 512 MB RAM PC.
(This is without the
nmi_watchdog=1 option.) However, the ATA layer is failing to initialise:
Linux version 2.6.24 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070925 (Red Hat
4.1.2-33)) #1
SMP PREEMPT Sat Feb 2 22:21:
Hi,
I have recently added a Radeon HD4670 to one of my older PCs, and have noticed
that it has IRQ trouble when I try to enable the HDMI audio:
irq 17: nobody cared (try booting with the "irqpoll" option)
Pid: 0, comm: swapper/0 Not tainted 3.5.3 #2
Call Trace:
[] ? __report_bad_irq+0x11/0x94
- Original Message -
> Did you try any workaround boot options such as irqpoll, pci=nocrs or
> whatever?
No, because wouldn't "irqpoll" have forced polling for every IRQ on the box? I
need to avoid polling on the video card's IRQ because it noticeably impacts the
responsiveness. (I assu
- Original Message -
> Did you try any workaround boot options such as irqpoll, pci=nocrs or
> whatever?
OK, the "irqpoll=1" option does help here. Although this message is obviously
scary:
Misrouted IRQ fixup and polling support enabled
This may significantly impact system performance
- Original Message -
> Did you try any workaround boot options such as irqpoll, pci=nocrs or
>whatever?
Actually, it turns out that booting with "irqpoll=1" simply means that this
problem takes longer to happen:
irq 17: nobody cared (try booting with the "irqpoll" option)
Pid: 3347, c
Hi,
I have recently upgraded my oldest PC from 3.4.8 to 3.5.4, but was puzzled to
discover that the keyboard no longer worked unless I also added the
i8042_nokbd=1 boot parameter. It turns out that 3.4.8 didn't use the i8042
keyboard device anyway:
>From 3.4.8:
...
i8042 aux: probe of 00:07 f
Hi,
I have managed to boot 2.6.24.1 on this machine, with the NMI watchdog enabled,
by using the
"acpi=noirq" option. (There does seem to be some unhappiness with bridge
symlinks in sysfs,
though.)
Cheers,
Chris
__
Sent from Yah
[Try this again, except this time I'll force the attachment as inline text!]
Hi,
I have managed to boot 2.6.24.1 on this machine, with the NMI watchdog enabled,
by using the
"acpi=noirq" option. (There does seem to be some unhappiness with bridge
symlinks in sysfs,
though.)
Cheers,
Chris
Linu
--- Andrew Morton <[EMAIL PROTECTED]> wrote:
> and here it hangs, I assume?
Oops, I think you have misunderstood. The hang happens if I *don't* specify
acpi=noirq, whereas in
this case I did. I have already reported the original hang under threads:
http://www.ussg.iu.edu/hypermail/linux/kernel/0
--- Andrew Morton <[EMAIL PROTECTED]> wrote:
> > sysfs: duplicate filename 'bridge' can not be created
> > WARNING: at fs/sysfs/dir.c:424 sysfs_add_one()
> > Pid: 1, comm: swapper Not tainted 2.6.24.1 #1
> > [] show_trace_log_lvl+0x1a/0x2f
> > [] show_trace+0x12/0x14
> > [] dump_stack+0x6c/0x72
--- Stephen Hemminger <[EMAIL PROTECTED]> wrote:
> > > sysfs: duplicate filename 'bridge' can not be created
> > > WARNING: at fs/sysfs/dir.c:424 sysfs_add_one()
> > > Pid: 1, comm: swapper Not tainted 2.6.24.1 #1
> > > [] show_trace_log_lvl+0x1a/0x2f
> > > [] show_trace+0x12/0x14
> > > [] dump_
--- Kay Sievers <[EMAIL PROTECTED]> wrote:
> Greg,
> it seems that:
> arch/x86/pci/legacy.c :: pci_legacy_init()
>
> tries to create already created "bridge" symlinks in 2.6.24. So we
> discover the same devices twice? Can this be a reason for the hang?
No, it can't be because it's *not* hangin
--- Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Sat, 2 Feb 2008 23:36:42 + (GMT)
> Chris Rankin <[EMAIL PROTECTED]> wrote:
> > I have a 1 GHz Coppermine PC with 512 MB RAM, and it is failing to boot
> > with the
> nmi_watchdog=1
> > option. This
--- Andrew Morton <[EMAIL PROTECTED]> wrote:
> It isn't clear (to me) where in this mess we disabled interrupts around the
> set_cpus_allowed(). Chris, if this is repeatable it would be helpful to
> set CONFIG_FRAME_POINTER=y which hopefully will get us a cleaner trace,
Here you go,
Cheers,
Chri
--- Andrew Morton <[EMAIL PROTECTED]> wrote:
> So it's a CONFIG_SMP=y kernel on a single-cpu machine?
Correct.
> It is unclear to me what clocksource (if any) your machine is using.
The 2.6.23.x kernel uses the TSC:
...
ACPI: Core revision 20070126
CPU0: Intel Pentium III (Coppermine) stepping 06
And the same thing with 2.6.24.1.
Cheers,
Chris
Linux version 2.6.24.1 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070925 (Red Hat
4.1.2-33))
#1 SMP PREEMPT Fri Feb 8 22:41:10 GMT 2008
BIOS-provided physical RAM map:
BIOS-e820: - 0009fc00 (usable)
BIOS-e820: 0009f
Hi,
I've just tried booting the 2.6.24.1 kernel, except without nmi_watchdog being
enabled. It looks
like there are IRQs still not being enabled.
Cheers,
Chris
Linux version 2.6.24.1 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070925 (Red Hat
4.1.2-33))
#1 SMP PREEMPT Fri Feb 8 22:41:10 GMT 2008
--- Greg KH <[EMAIL PROTECTED]> wrote:
> On Fri, Feb 08, 2008 at 11:31:24PM +0000, Chris Rankin wrote:
> > I've just tried booting the 2.6.24.1 kernel, except without
> > nmi_watchdog being enabled. It looks like there are IRQs still not
> > being enabled.
&
--- Greg KH <[EMAIL PROTECTED]> wrote:
> Does any older kernel version work? 2.6.23? Newer ones?
Everything up to and including 2.6.23.11 works fine. I never tried
2.6.23.{12,13,14,15}, but I
expect they're fine too.
> 2.6.24-git15?
No idea. This box isn't really set up to use git. Anyway, I w
--- Oliver Pinter <[EMAIL PROTECTED]> wrote:
> here is the snapshots in patch format:
> ftp://ftp.kernel.org/pub/linux/kernel/v2.6/snapshots
Thanks, they're very pretty. But what exactly are they patches *between*?
Cheers,
Chris
___
Hi,
This is a strange NMI lockup - I have no idea what triggered it and so cannot
possibly reproduce
it. Requests to try (try "what"?) with 2.6.24.x would be similarly unhelpful.
But anyway, here it is. A perfectly normal boot of 2.6.23.16 on a dual P4 Xeon
(HT enabled, to
give 4 logical CPUs)
Hi,
I have an ENSONIQ SoundScape PNP sound card, and I am noticing
problems with it under linux-2.4.0-prerelease and linux-2.4.0. I have
created 2 diffs which solve the most pressing problem (and sort a few
messages out), but the driver seems to have deeper issues which I
would like to discuss wi
? "SoundScape PNP" : "SoundScape",
hw_config->io_base,
hw_config->irq,
hw_config->dma,
diff -urN -X dontdiff linux-vanilla/drivers/sound/audio.c
linux-2.4.0/drivers/sound/audio.c
--- linux-vanilla
missing #include
+ * Chris Rankin: Update the module-usage counter for the coprocessor
*/
#include
@@ -71,6 +72,7 @@
int bits;
int dev_type = dev & 0x0f;
int mode = translate_mode(file);
+ struct coproc_operations *coprocessor;
dev = dev
Hi,
I have made further tweaks to the sscape module:
- removed two redundant calls to release_region()
- set the default MIDI volume(s?) to 100. These volume settings aren't
accessible from any mixer I have. Therefore set them to "maximum" and
use the volume control on the speaker instead.
C
Hi,
I have an old ISA-PNP soundcard whose driver doesn't currently use the
ISA-PNP services. I have therefore been activating this card by
writing to the /proc/isapnp interface. And in an idle moment, I tried
an "auto" instruction:
cat > /proc/isapnp << EOF
card 0 ENS3081
dev 0 ENS
auto
EOF
Hi,
This patch fixes a problem that I was having with the ENSONIQ
SoundScape mixer: basically, the mixer device was owned by the ad1848
module but was being deallocated when the sscape module was
unloaded. This patch hands the mixer device to the sscape module
instead so that the sscape module -c
Hi,
This is a revised version of my ad1848 patch; instead of modifying the
static structures, update the "owner" fields in the audio_devs[] and
mixer_devs[] structures instead.
Chris
--- linux-vanilla/drivers/sound/ad1848.cFri Aug 11 16:26:43 2000
+++ linux-2.4.0-ac3/drivers/sound/ad18
> > +
> > + if (owner)
> > + ad1848_mixer_operations.owner = owner;
> > +
> > if ((e = sound_install_mixer(MIXER_DRIVER_VERSION,
> > dev_name,
> > &ad1848_mixer_operations,
> >
> > BTW Isn't it ever-so-slightly dodgy modifying the static
>
> Very.
>
> > operations
Hi,
This patch makes the mpu401_synth_operations structure respect
attach_mpu401()'s "owner" parameter. This should prevent more sound
module from being accidentally unloaded.
Cheers,
Chris
--- linux-vanilla/drivers/sound/mpu401.cFri Jan 5 23:14:08 2001
+++ linux-2.4.0-ac3/drivers/sou
Hi,
I am trying to add ISA-PNP support to the ENSONIQ SoundScape driver,
but am suffering from a lack of examples: the only one I have is my
own. Can anyone who is using the sscape.o driver to control their
soundcard please email me with their working module parameters, plus
the output from eithe
Hi,
This is an incredibly boring patch that just adds "const" to some of
the ISA-PNP function prototypes. It compiles cleanly with gcc-2.95.2.
Cheers,
Chris
--- linux-vanilla/include/linux/isapnp.hSun Dec 31 19:11:06 2000
+++ linux-2.4.0-ac3/include/linux/isapnp.h Wed Jan 10 17:08:
still generic
* Horst von Brand: Add missing #include
+ * Chris Rankin: Update the module-usage counter for the coprocessor,
+ * and decrement the counters again if we cannot open
+ * the audio device.
*/
#include
@@ -71,6 +74,8 @@
int bi
Hi,
I have been trying out 2.4.0-ac6, and the RedHat 6.1 init scripts really don't like
it. (They liked 2.4.0-ac3 OK.) The visible symptom is that rc.sysinit now hangs,
waiting for me to press 'i'. Once I do, it successfully hands over to the correct
runlevel script, and I can go back to non-i
Hi,
I have just compiled 2.4.0-ac7, and this kernel boots up OK (no more
processes missing from the output of "ps -ef", either). However, I am
now getting an unresolved symbol "queued_sectors" in scsi_mod.o when I
run depmod.
I've done a "make mproper; ; make oldconfig;
make dep" and none of the
Hi,
I was going to save this patch until people (Alan) returned from
linux.conf.au, but seeing as 2.4.0-ac10 has just been posted ...
This patch makes the uart401 honour the module owner for MIDI and
synth devices, and then moves the MIDI operations into the text
section.
Chris
--- linux-2.4.0/
Hi,
I have just compiled Linux 2.2.18 (UP) and Linux 2.4.0-test12 (SMP,
devfs), and in each case I compiled the msr and cpuid drivers as
modules. However, when I tried to read from the devices (using "cat"),
I got oopses from both 2.2.18 and 2.4.0-test12. Neither the msr.o nor
the cpuid.o modules
Devfs might explain the 2.4.0-test12 oopses, but it can't possibly
explain the oops with 2.2.18. I don't use devfs with 2.2.18.
Chris
> Looks like a devfs problem; complain to the appropriate people. I refuse
> to touch that particular devfs code.
>
> > I have just compiled Linux 2.2.18 (UP)
> Looks like a devfs problem; complain to the appropriate people. I refuse
> to touch that particular devfs code.
I've had a quick look at both the 2.2.18 and 2.4.0-test12 drivers for
msr and cpuid, and I've noticed something curious.
This is the comment from 2.4.0-test12, cpuid.c:
/*
* cpui
OK, I've just tried repeating this experiment on 2.2.18 (no devfs) and
it oopsed this time, so there's obviously something else going on
here.
$ ksymoops -m /boot/System.map-2.2.18 < oops2.txt
ksymoops 2.3.4 on i586 2.2.18. Options used
-V (default)
-k /proc/ksyms (default)
-l /p
Maybe other 16 bit cards in this code could behave
* the same.
+ * Chris Rankin: Use spinlocks instead of CLI/STI
*/
+#include
+
#include "sound_config.h"
#include "sb_mixer.h"
@@ -43,23 +46,22 @@
if (mode == OPE
> spin_lock_irqsave() and save_flags()+cli() are identical on
> uniprocessor builds.
OK, so a UP-build proves nothing ...
> cli() is quite putrid on SMP and should be shot.
This much I understand ...
> You can test your patch on uniprocessor hardware - just build
> an SMP kernel and run it. I
this code could behave
* the same.
+ * Chris Rankin: Use spinlocks instead of CLI/STI
*/
+#include
+
#include "sound_config.h"
#include "sb_mixer.h"
@@ -43,23 +46,22 @@
if (mode == OPEN_READ)
> > --- linux-2.4.0/drivers/sound/sb.h.orig Fri Jan 26 13:57:40 2001
> > +++ linux-2.4.0/drivers/sound/sb.h Fri Jan 26 13:58:42 2001
> > @@ -137,6 +137,8 @@
> >void (*midi_input_intr) (int dev, unsigned char data);
> >void *midi_irq_cookie; /* IRQ cookie for the
Linux 2.4.5, SMP, devfs, < 1 GB memory, compiled with gcc-2.95.3
Hi,
I have just experimented with using reiserfs; since I didn't have a
hard disc partition free I used a 250MB Zip disc instead with my USB
drive. I didn't do anything clever with parameters or anything; just
"mkreisferfs /dev/sda
Hi,
Thanks for the patch; I successfully unmounted my reiserfs USB Zip 250
MB disc. However, the box then locked up hard when I unmounted an NFS
mount and tried to switch to another virtual console.
Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
> That's... interesting. With that patch changes to fs/super.c should make
> no difference whatsoever.
>
> OK, can you reproduce NFS lockup on 2.4.5-pre5 (without that patch)
> and on 2.4.5-pre3 (ditto)?
>
> There were NFS changes in -pre4 and -pre5 and umount ones in -pre6. The
> latter need t
ing.
Chris
My video card is a Matrox G400 AGP 32MB with TV-OUT, and I'm not using
the frame buffer driver.
> On Sat, 26 May 2001, Chris Rankin wrote:
>
> > Hi,
> >
> > Thanks for the patch; I successfully unmounted my reiserfs USB Zip 250
> > MB disc. Howeve
Hi,
It looks like my CDROM driver had a busy night last night
... ;-). This was with Linux 2.4.5, dual Pentium III, devfs, < 1GB
memory. There was no CDROM in the drive, but I had kept the CD player
running anyway.
Cheers,
Chris
May 27 02:10:03 twopit kernel: hdc: ATAPI 32X CD-ROM CD-R/RW drive,
REF: Linux 2.4.5, 2.4.4, 2.4.3 (and probably earlier);
devfs;
SMP (dual PIII);
< 1GB main memory
Hi,
Has anyone noticed their Linux box lock up hard (as in cannot even be
pinged from the local network) when switching from a text vc to a vc
running X? This has happened for me even
Hi, thanks for confirming this. But if it's Matrox's code (we are
talking about the mga_hal_drv.o module for X, correct?) then the ball
is in their court. Has anyone reported this to them so that they can
fix it?
Cheers,
Chris
> On Mon, May 28, 2001 at 12:24:50AM +0200, Ben Twijnstra wrote:
> >
> > On Mon, 22 Oct 2007 13:43:16 +0100 (BST) Chris Rankin <[EMAIL PROTECTED]>
> > wrote:
> > > I have a Netgear MA301 PLX wireless networking adapter which wants to use
> > > the hostap_plx
> > > driver in Linux 2.6.23.1. This very same piece of
Hi,
I've recently been having trouble loading the hostap_plx 802.11b wireless
networking driver, and
this evening I managed to narrow the problem down to these lines of code by
copying code from
hostap_plx into a "test driver" until the test driver also locked the PC up:
/* read CIS; it
--- Arjan van de Ven <[EMAIL PROTECTED]> wrote:
> can you check if the attr_mem is properly ioremap'd ?
> (probably with ioremap_nocache)
Can you elaborate, please? I am not familiar with these I/O primitives.
> I wonder if there's anything else in that area as well..
So I should check /proc/iom
--- Stefano Brivio <[EMAIL PROTECTED]> wrote:
> Not a fix, but if you load the module with ignore_cis = 1, it should work.
Well, if the I/O memory mapping is broken then wouldn't that just move the
problem down to the
next attempt to access it?
Cheers,
Chris
--- Arjan van de Ven <[EMAIL PROTECTED]> wrote:
> the memory you feed to readl() and co isnt the actual PCI resource;
> you need to use ioremap() on the PCI resource to get a pointer that you can
> then feed to
> readl()
I gathered that much, and there is indeed a call to ioremap() in the cod
--- Arjan van de Ven <[EMAIL PROTECTED]> wrote:
> > > I wonder if there's anything else in that area as well..
This is what /proc/iomem contains:
-0009f7ff : System RAM
0009f800-0009 : reserved
000a-000b : Video RAM area
000c-000cbfff : Video ROM
000e4000-000e : Adapte
--- Andrew Morton <[EMAIL PROTECTED]> wrote:
> It might be interesting to see what value of `i' is causing it to fall over.
I tried unrolling the loop, but a single byte read for i = 0 is enough to lock
things up.
> Did any earlier version of the 2.6 kernel work OK?
Unfortunately, I don't know.
--- Andrew Morton <[EMAIL PROTECTED]> wrote:
> hm. Could be some platform thing. Strange. It might be worth checking
> around that ioremap, make sure that the value which it returned is the one
> which is being used in the function-which-hangs, etc.
OK, not difficult to try. (This is x86, BTW.)
-- Andrew Morton <[EMAIL PROTECTED]> wrote:
> hostap_plx.c first appeared in 2.6.14.
>
Just a thought: How far back will I be able to compile kernels correctly with
gcc 4.1.2?
Specifically:
gcc (GCC) 4.1.2 20070925 (Red Hat 4.1.2-33)
Cheers,
Chris
Hi,
Do you remember that oops in sysfs a few versions ago? (Kernel bug 8198) Well,
it's bck in
2.6.22.9...
Cheers,
Chris
_
Do not compromise. Get unlimited storage and first rate spam protection with
Yahoo! Mail.
http://uk.mail.ya
--- Tejun Heo <[EMAIL PROTECTED]> wrote:
> This isn't really related to sysfs. It seems module count was too low
> and went away while there still were holders. What were you doing when
> it happened? Can you reproduce it?
I haven't tried reproducing it, but all I was doing was selecting the Au
--- Andrew Morton <[EMAIL PROTECTED]> wrote:
> > > Did any earlier version of the 2.6 kernel work OK?
Kernel 2.6.14 does not work any better than 2.6.23.x, and my F8 userspace
environment rejects a
2.4.35 kernel. I will try a 2.6.0 kernel next, but have noticed tonight that a
stock Fedora kernel
Hi,
My dual Xeon P4 (HT enabled), 2 GB RAM box crashed last night while playing
World of Warcraft
under Wine (Mesa 7.1, Radeon 9550 card). This is what appeared on the serial
console.
Cheers,
Chris
BUG: NMI Watchdog detected LOCKUP on CPU3, eip c0102aac, registers:
CPU:3
EIP:0060:[]
Hi,
I hacked together this quick patch to make the "master" raw IO device
appear in devfs. It seems odd that I need *both* devfs_register...()
calls but the first one only seems to make the entry appear in
/proc/devices.
The logical corollary to this patch is to make raw IO devices
magically appe
Hi,
I have written this patch so that /dev/raw now appears in a devfs
filesystem. I haven't tried to support the /dev/rawN devices because
I'm not sure that it would be worthwhile. (Seeing as you need to bind
them by hand manually anyway.)
Cheers,
Chris
--- linux-2.4.5/drivers/char/raw.c.orig S
Hi,
My dual Xeon P4 (with HT, 1 GB RAM) has just oopsed on
shutdown, due to a lockup in the CFQ scheduler (I
think). The compiler was gcc-3.4.3.
NMI Watchdog detected LOCKUP on CPU2, eip c026d86d,
registers:
Modules linked in: snd_pcm_oss snd_mixer_oss
snd_usb_audio snd_usb_lib snd_intel8x0 snd_s
[gcc-3.4.3, Linux-2.6.11-SMP, Dual P4 Xeon with HT enabled]
Hi,
My Linux 2.6.11 box oopsed when I tried to logout. I have switched to using the
anticipatory
scheduler instead.
Cheers,
Chris
NMI Watchdog detected LOCKUP on CPU1, eip c0275cc7, registers:
Modules linked in: snd_pcm_oss snd_mixer_
I have one IDE hard disc, but I was using a USB memory stick at one point.
(Notice the usb-storage
and vfat modules in my list.) Could that be the troublesome SCSI device?
--- Jens Axboe <[EMAIL PROTECTED]> wrote:
> On Sun, Mar 27 2005, Chris Rankin wrote:
> > [gcc-3.4.3, Linux-2
>> > I have one IDE hard disc, but I was using a USB memory stick at one
> > point. (Notice the usb-storage and vfat modules in my list.) Could
> > that be the troublesome SCSI device?
--- Jens Axboe <[EMAIL PROTECTED]> wrote:
> Yes, it probably is. What happens is that you insert the stick and do
--- Raman Gupta <[EMAIL PROTECTED]> wrote:
> I just found this bug:
>
> http://bugzilla.kernel.org/show_bug.cgi?id=8198
>
> This seems to indicate the problem was resolved in 2.6.21.2.
>
> However, I also found this, where you reported the problem was back in
> 2.6.22.9 (which is what I am curr
--- Dan Williams <[EMAIL PROTECTED]> wrote:
> This same sort of problem was just fixed for iwl4965. The fix for that
> was to disable device interrupts until everything the driver needed
> (including interrupt handler) was set up and ready before re-enabling
> them, I think. See the thread "iwl49
Hi,
I am running a 2.6.22 kernel on a dual P4 Xeon (HT enabled) with 2 GB RAM, and
I have just found
this BUG in my dmesg log:
nfsd: last server has exited
nfsd: unexporting all filesystems
BUG: atomic counter underflow at:
[] kref_put+0x66/0x84
[] sysfs_hash_and_remove+0xb8/0x12d
[] sysfs_ha
--- Satyam Sharma <[EMAIL PROTECTED]> wrote:
> I expect this is easy to reproduce at will (when shutting down nfs
> services, probably), right?
I'm not sure about the "at will" part because this is the first time I've seen
it since 2.6.22 was
released. However, I was upgrading my Fedora 7 nfs-uti
Hi,
I have a Netgear MA301 PLX wireless networking adapter which wants to use the
hostap_plx driver in
Linux 2.6.23.1. This very same piece of hardware works fine in an old(!) P120
machine running
2.4.33, but makes the 2.6.23.1 kernel freeze as soon as the pci_enable_device()
function is called
Hi,
I have been testing my wireless zd1211rw driver with kismet, but have noticed
my logs filling up
with these messages instead:
BUG: sleeping function called from invalid context at kernel/mutex.c:86
in_atomic():0, irqs_disabled():1
[] mutex_lock+0x12/0x1a
[] netdev_run_todo+0x10/0x1f1
[] d
This is for a 2.6.18.6 UP-preempt kernel compiled with gcc-4.1.1, BTW.
Cheers,
Chris
___
The all-new Yahoo! Mail goes wherever you go - free your email address from
your Internet provider. http://uk.docs.yahoo.com/nowyou
Hi,
This patch writes the USB vendor and product IDs into the
/sys/class/input/inputX/id/ files, so
that udev can find them. A rule like this does the trick for me:
KERNEL="event*", SYSFS{../id/vendor}=="2040", SYSFS{../id/product}=="9301",
SYMLINK+="input/dvb-remote"
--- linux-2.6.18/drivers/m
> But 2.6.18.x must be over now, because the -stable team didn't release a
> 2.6.18.7 to match
> 2.6.19.2, and all of 2.6.x except for 2.6.19.2 has that weird file corruption
> bug .
Personally, I dumped 2.6.19.x like a hot coal as soon as I tripped over this
bug:
http://bugzilla.kernel.org/sh
> That's surely no reason to dump 2.6.19.x, you'll find the occasional
> such report on every(?) release since page mapcount went into 2.6.7.
This was the only time I've seen it, before or since.
> Oftentimes it's bad RAM (try memtest86)
There is nothing wrong with my RAM. I tested it quite exte
> > But MY kernel is clearly untainted.
> > So what other explanation is there apart from a kernel bug?
> If it's me you're asking: I don't know (overheating, cosmic rays, ...)
I suppose what I'm *really* asking is what the basis is for assuming that this
*isn't* a kernel
bug and can therefore b
--- Hugh Dickins <[EMAIL PROTECTED]> wrote:
> All I'm claiming is that it's no more a reason to avoid 2.6.19*
> than to avoid any other release (the kernels before 2.6.7 happened
> to have no such check, but that doesn't imply they were any safer).
There is *one* reason to avoid 2.6.19.x: it has a
--- Mark Rustad <[EMAIL PROTECTED]> wrote:
> Well, do you have ECC memory? If not, it is at least possible that
> that the solar flares that occurred last month may have affected your
> system.
I am going to assume that you are being facaetious, because it would be the
rarified pinnacle of
su
--- Alan <[EMAIL PROTECTED]> wrote:
> A one off non repeatable error experienced by two people out of the
> millions using it does fit the cosmic ray description quite well.
Actually it's "unrepeated", not "non repeatable". And that's because I switched
back to 2.6.18.x
immediately since I no lon
--- Mark Rustad <[EMAIL PROTECTED]> wrote:
> Exactly. Halting use of a version of the kernel based on a single
> incident provides no insight to the source of the problem. It could
> be anything...
There is a world of difference between a polite request for more information
(although I gave y
--- Mark Rustad <[EMAIL PROTECTED]> wrote:
> We'll never know if any of these things were correlated with the
> solar flares because they all seem to be one-off failures. I do find
> it interesting though. Our systems seem to be doing statistically
> better this month. What do you think?
Per
--- Ken Moffat <[EMAIL PROTECTED]> wrote:
> At the moment, you have a problem that nobody recognises. If you're not
> willing to test if the problem happens repeatably, (you appear to
> have had one failure and immediately reverted to an old kernel), who
> do you think will be able to fix it?
Thi
Hi,
I have just booted 2.6.20.1 on my Pentium 3 machine, which has a G400 MAX
graphics card. This
machine uses the Matrox framebuffer and TV-OUT modules, and I have found these
warnings in the
kernel log:
**WARNING** I2C adapter driver [DDC:fb0 #0] forgot to specify physical device;
fix it!
**
Hi,
This looks like a memory fault to me; are those 0x6b characters "slab
poisoning"? This is the dual
P4 Xeon / 2 GB RAM machine, and I'm guessing that udevd has just loaded
snd_rtctimer (because
that's the module at the top of the list):
BUG: unable to handle kernel paging request at virtual
--- Randy Dunlap <[EMAIL PROTECTED]> wrote:
> Do you have any of the preceding kernel log messages?
> or can you get them?
Unfortunately, there was none. I posted everything there was. Race condition,
perhaps?
Cheers,
Chris
___
--- Takashi Iwai <[EMAIL PROTECTED]> wrote:
> snd_timer_global_register() itself doesn't issue any tasklet, so it
> shouldn't be needed.
Hmm, this bug looks interesting:
http://www.ussg.iu.edu/hypermail/linux/kernel/0702.3/0514.html
Yes, my machine *is* a dual P4 with HT enabled...
Cheers,
Chr
--- Pekka Enberg <[EMAIL PROTECTED]> wrote:
> > Call Trace:
> > [] sysfs_release+0x2d/0x4c
> > [] __fput+0x96/0x13c
>
> So udevd is closing a sysfs attribute file but the pointer passed to
> module_put is bogus. Looks like the sysfs dentry was already taken
> down by release_sysfs_dirent(). Can
--- Pekka Enberg <[EMAIL PROTECTED]> wrote:
> Yeah, but the oops looks more like a reference counting problem with
> sysfs dentries. No harm in trying out the patch or reproducing without
> CONFIG_SCHED_SMT though.
>
Nope, no difference. Again, this happened while trying to start World of
Warcra
--- Pekka J Enberg <[EMAIL PROTECTED]> wrote:
> Please apply this patch to your kernel and try to reproduce:
Ta-DA
BUG: unable to handle kernel paging request at virtual address 6b6b6d6b
printing eip:
c0130113
*pde =
Oops: 0002 [#1]
PREEMPT SMP
last sysfs file: /clas
Oh yes - I'd better mention what my Ethernet devices are:
$ cat /proc/net/dev
Inter-| Receive| Transmit
face |bytespackets errs drop fifo frame compressed multicast|bytes
packets errs drop fifo
colls carrier compressed
lo: 820705 1
--- Ken Moffat <[EMAIL PROTECTED]> wrote:
> I can't, but Dave Jones had a similar problem earlier this month,
> archived at http://uwsg.iu.edu/hypermail/linux/kernel/0701.0/1822.html
> which I think is a followup from
> http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg105370.html
> - a
> Ok. I've finally figured out what is going on. The code is race free but the
> programmer was an
> idiot.
Hi,
Could this IRQ problem account for this bug as well, please? Or is yours
strictly a 2.6.19.x
issue?
http://bugzilla.kernel.org/show_bug.cgi?id=7847
I have a dual P4 Xeon box (HT ena
Hi,
I just tripped this bug when compiling xine-lib on 2.6.19.1. This is on a dual
P4, SMP and HT, 2
GB RAM, compiled with gcc-4.1.1.
Cheers,
Chris
Eeek! page_mapcount(page) went negative! (-1)
page->flags = 14
page->count = 0
page->mapping =
[ cut here ]
Hi,
I experienced this BUG while playing World of Warcraft with a Radeon 9200 AGPx8
video card and
FC7:
BUG: NMI Watchdog detected LOCKUP on CPU3, eip c019f98f, registers:
Modules linked in: snd_rtctimer snd_seq_midi radeon drm cpufreq_ondemand
p4_clockmod speedstep_lib
nfsd exportfs autofs4 ee
1 - 100 of 132 matches
Mail list logo
