What I mean is that I've run an fsck and it doesn't find any
corruptions/inconsitencies.
Also 2.6.17-10, vanilla 2.6.19-rc6, vanilla 2.6.19 boot up fine. A
2.6.19-6 compiled from ubuntu source does not boot. 2.6.19-6 and -7 from
ubuntu does not boot. 2.6.20-2 does boot.
So if you are right, you s
To whom are you talking and about what problem ? The fix works till
2.6.20 and it is in *no way* related to file system corruption. Anyway
it is corrected so no bother.
--
[feisty][linux-image-2.6.19-7] PCMCIA bridge driver i82365 causes "BUG: soft
lockup detected on CPU#0!" on Asus motherboards
There is no bug. What you have is filesystem corruption, and you need to
fix that, else you will likely see this problem again.
Just wanted to make sure you know what the real cause of this is.
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Fix Released => Rejected
** Changed in: lin
That teaches me to speak too soon ;-)
2.6.20 landed. Trying to reproduce there, yields:
---
[EMAIL PROTECTED]:~# modprobe i82365
FATAL: Error inserting i82365
(/lib/modules/2.6.20-2-generic/kernel/drivers/pcmcia/i82365.ko): No such device
---
As it should.
Consider this bug swatted.
--
[feis
I shall test the work-around tonight. My computer is a Shuttle with
nForce2 chipset (someone reported the bug on a Via chipset too above),
GeForce 6 graphics card, and obviously no PCMCIA device.
--
[feisty][linux-image-2.6.19-7] PCMCIA bridge driver i82365 causes "BUG: soft
lockup detected on C
Ben,
The new kernel did NOT fix this bug.
Running package version 2.6.19-7.11, tested it as follows:
modprobe i82365
BUG: soft lockup detected on CPU#0!
*hang*
--
[feisty][linux-image-2.6.19-7] PCMCIA bridge driver i82365 causes "BUG: soft
lockup detected on CPU#0!" on Asus motherboards
** Changed in: linux-source-2.6.19 (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ben Collins
Status: Unconfirmed => Fix Released
** Changed in: linux-source-2.6.19 (Ubuntu)
Sourcepackagename: linux-source-2.6.19 => linux-source-2.6.20
--
[feisty][linux-image-2
The stacktrace occurs right after the kernel message:
pcmcia bridge drive module i82365
Pretty easy to see. ;)
I am having the same issue, also with an ASUS.
--
[feisty][linux-image-2.6.19-7] PCMCIA bridge driver i82365 causes "BUG: soft
lockup detected on CPU#0!" on Asus motherboards
https:/
I thought I'd just add that I also got this issue, and the workaround
mentioned (changing PCMCIA=yes to =no) worked, however I'm not using an
ASUS motherboard - I'm using an ASRock K7S8X (details:
http://www.asrock.com/product/K7S8X.htm ).
--
[feisty][linux-image-2.6.19-7] PCMCIA bridge driver i8
modprobe pcmcia_core is working ok.
modprobe i82365 is not working, "error inserting module, no such device", note
that the i82365.ko file exists. "no such device" seems a correct message since
I do not have any pcmcia device and/or controller.
So the vanilla kernel does not hang.
--
[feisty][
Allcolor_g, can you try running a vanilla 2.6.19 kernel and then issuing the
modprobe by hand? I wonder if this affects upstream.
On paper all that is needed to trigger the bug would be:
modprobe pcmcia_core
modprobe i82365
--
[feisty][linux-image-2.6.19-7] PCMCIA bridge driver i82365 causes
** Summary changed:
- [feisty] [linux-image-2.6.19-6] BUG: soft lockup detected on CPU#0!
+ [feisty][linux-image-2.6.19-7] PCMCIA bridge driver i82365 causes "BUG: soft
lockup detected on CPU#0!" on Asus motherboards
--
[feisty][linux-image-2.6.19-7] PCMCIA bridge driver i82365 causes "BUG: sof
12 matches
Mail list logo
