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
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:
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 <w...@1wt.eu> wrote:
> Hi Chris,
>
> On Tue, Dec 26, 2017 at 01:49:59AM +0000, Chris Rankin wrote:
> (...)
>> [ 35.100181] Call Trace:
>> [ 35
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]
[
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]
[
Hi Linux
http://www.carpediemeventos.cl/case-studies.php?france=2k712cqa9ksz
Chris
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
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
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
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 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 info at http
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
On Friday, 21 February 2014, 9:47, Hans de Goede hdego...@redhat.com 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
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
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
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
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
- 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,
- 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
- 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
- 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 assume
- 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, comm:
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:
[] ?
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:
[c1063806] ?
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,
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*
--- 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* hanging in this
--- 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
> > > []
--- 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:
--- 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:
--- 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
[c0105020] show_trace_log_lvl+0x1a/0x2f
[c0105990] show_trace+0x12/0x14
[c010613d]
--- 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
[c0105020] show_trace_log_lvl+0x1a/0x2f
[c0105990] show_trace+0x12/0x14
[c010613d]
[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
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
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
[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
Linux
--- 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
--- 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 ena
--- Greg KH [EMAIL PROTECTED] wrote:
On Fri, Feb 08, 2008 at 11:31:24PM +, 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.
Does 2.6.24 work? Is this a 2.6.24.1
--- 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
--- 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,
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:
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:
--- 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
--- 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,
--- 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,
Chris
--- 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:
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 kernel was rebuilt after doing a make mrproper. The dmesg
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
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 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
--- 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
--- 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,
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:
-- 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,
--- 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
--- 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. I
--- 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.) But
-- 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
--- 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 :
--- 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 : Adapter
--- 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
--- 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
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;
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/iomem?
--- 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 code. So
> > 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
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 hardware works fine in
an old(!) P120
machine running
--- 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
--- 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 currently
--- 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
--- 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 iwl4965
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
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
--- 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
--- 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 Audio
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.
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.
1 - 100 of 250 matches
Mail list logo
