Hi,
Theee warnings ares not present in my dmesg log from 5.11.8:
[ 43.390159] [ cut here ]
[ 43.393574] WARNING: CPU: 2 PID: 1268 at
drivers/gpu/drm/ttm/ttm_bo.c:517 ttm_bo_release+0x172/0x282 [ttm]
[ 43.401940] Modules linked in: nf_nat_ftp nf_conntrack_ftp cfg80211
Linux https://bitly.com/3sZmFP2 Chris
Hi,
I've just noticed these oopsen in my dmesg logs. These are from 5.8.3:
[ 61.599710] [ cut here ]
[ 61.603145] WARNING: CPU: 0 PID: 1756 at
drivers/gpu/drm/drm_modeset_lock.c:185
drm_warn_on_modeset_not_all_locked+0x66/0x6e [drm]
[ 61.613699] Modules linked in: nf
Linuxhttps://bit.ly/2XrWvrc
Chris
Linux
https://j.mp/2XC439z
Chris Rankin
Yeandle https://goo.gl/Fp94bb
Chris Rankin
Hi.
I've suddenly realised that my kernel dmesg logs contain lines like:
[0.00] found SMP MP-table at [mem 0x000f5c20-0x000f5c2f]
mapped at [(ptrval)]
[0.00] Base memory trampoline at [(ptrval)] 98000 size 24576
and
[0.00] percpu: Embedded 41 pages/cpu @(
Linux
http://awesomebestwallpapers.us/tlv2k5j/wtuds/hosting/writereview/contactdo.php?produce=hz10y3pp5a0k
Chris Rankin
Hi,
Reverting this patch seems to have fixed things.
Thanks,
Chris
On 26 December 2017 at 06:21, Willy Tarreau wrote:
> Hi Chris,
>
> On Tue, Dec 26, 2017 at 01:49:59AM +0000, Chris Rankin wrote:
> (...)
>> [ 35.100181] Call Trace:
>> [ 35.102709] dump_stack+0x
Hi,
I've just raised https://bugzilla.kernel.org/show_bug.cgi?id=198271
because the new 4.14.9 kernel is generating lots of BUG warnings, e.g.
[ 35.069924] BUG: using smp_processor_id() in preemptible []
code: avahi-daemon/761
[ 35.078187] caller is ip6_pol_route+0x46b/0x509 [ipv6]
[
advantages and disadvantages of both action, and
inaction, can be peer-reviewed on both the legal and technical side.
--
David C. Rankin, J.D.,P.E.
Hi Linux
http://www.carpediemeventos.cl/case-studies.php?france=2k712cqa9ksz
Chris
Still no sign of the 4.9.3 patches on the FTP site... Oops?
Cheers,
Chris
Good morning linux
http://www.scanman.com.au/particularly.php?stick=2ubmk03m5uy9q
Chris Rankin
greetings linux
http://profedu.online/escape.php?race=1q5xsgykw917
My Best
Chris Rankin
Hi linux
http://teethcaredentalstudio.com/dark.php?result=9nyxatqeuqq612pzp
Chris Rankin
ranki...@yahoo.com
Sent from my iPhone
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo inf
HI,
Good day!
We are mailbox supplier, and we have researched & designed some new product.
If you are interested in, I'll Email you a catalogue of our various products
Our Advantage Small volume products , materials , packaging , custom content,
etc. according to customer requirements to complete
Hi
We are suppliers of Mailbox,
If you are interested, please contact us.
Email:i...@tdmailbox.com
Web:
www.tdmailbox.comN�Р骒r��yb�X�肚�v�^�)藓{.n�+�伐�{��赙zXФ�≤�}��财�z�&j:+v�����赙zZ+��+zf＂�h���~i���z� �wア�?�ㄨ��&�)撷f��^j谦y�m��@A�a囤�
0鹅h���i
HI,
Good day!
We are mailbox supplier, and we have researched & designed some new product.
If you are interested in, I'll Email you a catalogue of our various products
Our Advantage Small volume products , materials , packaging , custom content,
etc. according to customer requirements to complete
On Friday, 21 February 2014, 9:47, Hans de Goede wrote:
> This is likely caused by the camera being plugged into a usb-bus which
> already is used
> by other reserved-bandwidth devices such as mice, keyboard, usb soundcards,
> etc.
> If possible USB-3 ports are preferred over USB-2 ports or co
Hi,
I have an old Logitech webcam, with USB IDs 046d:08b3. When I try to use this
camera now, I see this error in the dmesg log:
[ 2883.852464] pwc: isoc_init() submit_urb 0 failed with error -28
This error is apparently ENOSPC, which made me suspect that I was trying to use
a mode that wou
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
- 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
- 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?
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
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
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)
--- 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
--- 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_
--- 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
--- 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
[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
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
--- 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
___
--- 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
--- 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.
&
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
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
--- 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
--- 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:
> 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
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 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
--- 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:[]
-- 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
--- 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:
> 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.
--- 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
--- 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
--- 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:
> 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
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
> > 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
--- 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 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
--- 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
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
--- 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 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
> Why not. I boot back and forth randomly between old and new IDE kernels
> without problems. The root fs loaded is set in kernel or grub (or on most
> distros nowdays by label scanning from initrd) so just works. Then mount
> label or uuid based mounting does the rest.
You say that, but I remembe
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
Shouldn't this patch from Tejun be applied to 2.6.21.x as well as 2.6.20.x?
Tejun Heo (2):
...
driver-core: don't free devt_attr till the device is released
Cheers,
Chris
___
Yahoo! Answers - Got a question? Someone out
--- Jeff Garzik <[EMAIL PROTECTED]> wrote:
> Grab the 'always use polling SETXFER' patch...
Yes, that did the trick!
scsi1 : ata_piix
usb 1-2: new full speed USB device using uhci_hcd and address 3
usb 1-2: configuration #1 chosen from 1 choice
ata2.00: ATAPI, max UDMA/33
ata2.01: ATAPI, max UDMA
Hi,
I have tried replacing the old IDE layer on my dual P4 machine with the PATA
driver instead, but
the CDRW drive on the second IDE bus (the old /dev/hdd drive) is never
recognised:
ata1: PATA max UDMA/100 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x0001ffa0 irq 14
ata2: PATA max UDMA/100 cmd 0x000
--- Tejun Heo <[EMAIL PROTECTED]> wrote:
> Looking at the code, class
> device is already doing it that way, so here's the full-assed fix.
> Chris, can you please test the attached patch?
Tejun,
So far so good; my 2.6.20.11+patch kernel hasn't oopsed yet. I'm going to start
using this kernel
as
--- Tejun Heo <[EMAIL PROTECTED]> wrote:
> Okay, here's a half-assed fix. With this patch applied, if you try to
> unload a module while you're opening it's dev attribute, kernel will
> oops later when the file is accessed or closed later but it should fix
> the bug winecfg triggers. I really dun
--- Tejun Heo <[EMAIL PROTECTED]> wrote:
> So, we can fix the problem Chris is seeing by breaking module unload (by
> allowing it to unload too early). It doesn't sound too hot but module
> unloading race is much less likely than sysfs node deletion/open race.
Yikes! Just temporary breakage, I ho
. Is this udev??? If so, can I safely update udev
without destroying my 2.6.13-15.15 setup?? Can it be anything else?? Any
help would be appreciated.
Thanks!
--
David C. Rankin, J.D., P.E.
510 Ochiltree Street
Nacogdoches, Texas 75961
(936) 715-9333
(936) 715-9339 fax
www.rankinlawfirm.com
--
Hmm, THAT looks familiar...
http://bugzilla.kernel.org/show_bug.cgi?id=8198
Yes, it is in 2.6.20.x.
Cheers,
Chris
___
Yahoo! Answers - Got a question? Someone out there knows the answer. Try it
now.
http://uk.answers.yahoo.com/
-
[Linux version 2.6.20.4 ([EMAIL PROTECTED]) (gcc version 4.1.1 20070105 (Red
Hat 4.1.1-51))
#1 PREEMPT Sun Mar 25 17:31:32 BST 2007]
Hi,
I have just booted the 2.6.20.4 kernel on an old 350 MHz P2, and am now seeing
these messages in
my boot log:
Setting up standard PCI resources
ACPI: Interpr
--- Pekka Enberg <[EMAIL PROTECTED]> wrote:
> Please try out the following patch to see if we catch a reference
> counting underflow:
>
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20/2.6.20-mm2/broken-out/detect-atomic-counter-underflows.patch
Sure, I can do that.
Cheers,
Ch
--- Pekka Enberg <[EMAIL PROTECTED]> wrote:
> On 3/16/07, Greg KH <[EMAIL PROTECTED]> wrote:
> > Is there any way you can use 'git bisect' to try to track down the root
> > cause of this?
>
> Chris, If 2.6.19 works for you, could you please do a git bisect for
> this bug? See the following URL for
Marco Berizzi wrote:
> Here is:
>
> Mar 14 03:42:25 Mimosa kernel: [ cut here ]
> Mar 14 03:42:25 Mimosa kernel: kernel BUG at mm/slab.c:610!
> Mar 14 03:42:25 Mimosa kernel: invalid opcode: [#1]
> Mar 14 03:42:25 Mimosa kernel: Modules linked in: sch_sfq sch_htb
cls_fw
Hi,
It looks like 2.6.20.2 is still doing Bad Things in /sys.
Cheers,
Chris
BUG: unable to handle kernel paging request at virtual address 6b6b6d6b
printing eip:
c01300ff
*pde =
Oops: 0002 [#1]
PREEMPT SMP
Modules linked in: radeon drm pwc eeprom cpufreq_ondemand p4_clockmod
speedstep
--- Pekka J Enberg <[EMAIL PROTECTED]> wrote:
> It should give us a better clue which sysfs file is causing the oops.
This BUG happened during boot-up! The only USB device I have is a pwc webcam:
$ /sbin/lsusb
Bus 004 Device 001: ID :
Bus 003 Device 001: ID :
Bus 002 Device 001: I
--- Pekka J Enberg <[EMAIL PROTECTED]> wrote:
> Please apply this patch to your kernel and try to reproduce:
>
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20/2.6.20-mm2/broken-out/gregkh-driver-sysfs-crash-debugging.patch
>
> It should give us a better clue which sysfs file
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
--- 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
--- 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 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
--- 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
--- 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
___
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
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!
**
> 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
--- 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
--- 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
--- 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
--- 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
--- 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:
> 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
--- 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
> > 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
> 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 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
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
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,
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
1 - 100 of 138 matches
Mail list logo
