** Changed in: intellinuxwireless
Importance: Unknown = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/263059
Title:
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
--
** Tags added: iso-testing
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Just upgraded to Intrepid and am hit with this extraordinarily
irritating problem. 2.6.27-9.19 has CONFIG_HAVE_DYNAMIC_FTRACE=y. I
assume at some point between 7.12 and 9.19 it was reenabled?
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
It was CONFIG_DYNAMIC_FTRACE that got (and still is) disabled. My
system's working fine - are you sure the bug described here is what
happens to you (look at the load of linked pictures)?
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You
** Changed in: intellinuxwireless
Status: Confirmed = Invalid
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: intellinuxwireless
Status: In Progress = Confirmed
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
My 8.10 installation will only boot up at home. Anywhere else it hangs
at Configuring network interfaces. It seems it will only boot up if
it is in the presence of my default network connection.
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
Spoke too soon, my Mini 9 with a Dell pulled Intel 3945ABG is hanging
again.
Even worse, when it hangs the system gets *HOT*. Too hot to actually
hold. And it only took about 60 seconds.
Not good.
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
Spoke too soo, my Mini 9 is hanging again.
Even worse, when it hangs the system gets *HOT*. Too hot to actually
hold. And it only took about 60 seconds.
Not good.
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug
Spoke too soon, my Mini 9 is hanging again.
Even worse, when it hangs the system gets *HOT*. Too hot to actually
hold. And it only took about 60 seconds.
Not good.
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug
Just wanted to confirm that this works on a Dell Inspiron Mini 9 with a
Dell pulled Intel 3945ABG card. Before, my system would quite reliably
hang. Now, it works fine.
Thanks for all the hard work fixing this.
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
** Changed in: intellinuxwireless
Status: Confirmed = In Progress
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
-7.12 seems to work reliably for me as well. I'm the original reporter.
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I removed all modprobe workarounds and system boots reliably now (lenovo
thinkpad X60s).
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
What's 2.6.27-7.12? Is that an Ubuntu kernel, or a Linux kernel?
I'm now running 2.6.27-7-generic #1 SMP Fri Oct 17 22:24:21 UTC 2008 i686
GNU/Linux (without the .12), and there are no further updates available. Is
that the version that has fixed the bug for you? I can't tell right away
because
On Sun, Oct 19, 2008 at 09:18:37PM -, xinit wrote:
Same here. 2 boots and no problems. Don't see any related fixes in the
changelog though.
Notably, this upload disabled the ftrace feature in the kernel. This is a
new feature in 2.6.27 which is suspected to have bugs related to loadable
On Mon, Oct 20, 2008 at 08:15:32AM -, Sander Jonkers wrote:
What's 2.6.27-7.12? Is that an Ubuntu kernel, or a Linux kernel?
cat /proc/version_signature
--
- mdz
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this
Sander, 2.6.27-7.12 is an actual version of the package see
http://packages.ubuntu.com/intrepid/linux-image-2.6.27-7-generic or
package description in your favorite package manager.
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You
Will try it later, for now I can just confirm that enabling
CONFIG_DYNAMIC_FTRACE caused hangs again (didn't touch other config
parts).
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug notification because you are a
I booted the old and new kernels today. The old kernel would hang 3
times out of 3 when my wired cable wasn't plugged, and didn't hang 3
times out of 3 when it was plugged (probably a timing issue with e1000e
when the cable is plugged).
The new kernel booted successfully 6 times out of 6 (half
Marking this fixed by:
linux (2.6.27-7.12) intrepid; urgency=low
[...]
* disable CONFIG_DYNAMIC_FTRACE due to possible memory corruption on
module unload
** Changed in: linux (Ubuntu Intrepid)
Status: In Progress = Fix Released
--
[regression] 2.6.27-7 sometimes fails to boot
Scott's test script runs successfully over 100 iterations with -7.12.
I successfully booted -7.12 with quiet splash two times and with
quiet two times. With either of those, previous kernels almost always
hung for me. Booting without quiet still works fine (just as in
previous kernels).
So this
I'm up over 1,000 iterations with the new kernel. I am content that
disabling ftrace has fixed the problem.
From the available information, and note that I'm *way* out of my
comfort zone and area of expertise here, I would hypothesise that having
the __init section of another module discarded
I had the same problem with =2.6.27-3
Since some days (2.6.27.7) the problem seems to be fixed.
I have a Dell Precision M90 Notebook.
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug notification because you are a
Another 15 boots without a hang. Tried to find a pattern in the syslogs
but there is none. iwl3945 seems to usually get loaded earlier but not
always.
I've suspected the ftrace change too and am currently building a kernel
with this option enabled.
--
[regression] 2.6.27-7 sometimes fails to
Could someone with the relevant hardware try Scott's minimal test case
under 2.6.27-7.12 and see if it still breaks?
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug notification because you are a member of Ubuntu
Tested in Sony VGN-SZ140P
This machine wasn't booting with the kernel with the bug. With the 2.6.27-7.12
kernel it boots correctly every time I tried (20 times).
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug
I'm experiencing the same thing on an HP Compac nc6320. Haven't tried
out any workarounds yet, but at boot, I have about 20% success and
booting nicely.
lscpi:
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML
and 945GT Express Memory Controller Hub [8086:27a0] (rev
I was having the same problem on my lenovo Z61m laptop which also uses
the iwl3945 driver. It would consistently fail on every other boot
attempt. Since I ran the Update Manager last night, it hasn't failed to
boot once. Maybe it is fixed now.
--
[regression] 2.6.27-7 sometimes fails to boot
The 2.6.27 kernel has survived 2 cold boots here too. Previously that
did never happen. I'll test some more.
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug notification because you are a member of Ubuntu
Bugs, which
Same here. 2 boots and no problems. Don't see any related fixes in the
changelog though.
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
15 boots without a hang. Fixed with 2.6.27-7.12?
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hello i don't know if it is related to this bug but now i hang on boot and
shutdown for more than 15 second at each boot.
My wifi load or not load and when it load my connection is so weak i can not do
anything. I ve got when i m connecting to the wire more than 700kb/s and with
my wifi
On Sat, Oct 18, 2008 at 04:59:01PM -, taiebot65 wrote:
Hello i don't know if it is related to this bug but now i hang on boot and
shutdown for more than 15 second at each boot.
My wifi load or not load and when it load my connection is so weak i can not
do anything. I ve got when i m
The only thing we know: a five (probably less) seconds delay stops the
hangs.
So I removed everything [up to Loading hardware drivers...] before the
module gets loaded during a successful delayed boot by either
blacklisting it, removing the driver, disabling it in the kernel, and
adding acpi=off
The i3945 part of this bug is a red herring. It also happens with an
ipw2200 on a Thinkpad T42 (bug #284406). I'm wondering if the problem is
hardware related. Can anyone confirm this hang using a 64 bit kernel?
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
Again sorry for a me not post; using a 64 bit kernel here I have no
problems. Cannot say for a 32 bit kernel though. You can find my lspci
output in earlier comments.
Il giorno ven, 17/10/2008 alle 13.23 +, Tim Gardner ha scritto:
The i3945 part of this bug is a red herring. It also happens
I've created an extremely minimal test case that replicates this bug.
First I compiled a custom kernel, this had almost all core parts
compiled in and only true drivers as modules. I attach the config
here.
Notably this only leaves iwl3945 and tg3 as modules for me.
The hang still occurred at
Next I eliminated userspace from the problem. I commented out the
start on startup line from /etc/event.d/rcS and instead added the
attached sysinit job.
This performs the absolute minimum necessary to get udev running, and
sets off the trigger.
I still had the hang, so it's not a race with
To make sure it wasn't any udev background processing, I cut out all the
non-essential udev rules.
I was left with just this:
# ls /etc/udev/rules.d
20-names.rules
40-basic-permissions.rules
40-permissions.rules
80-programs.rules
85-ifupdown.rules
90-modprobe.rules
NOTE that I explicitly
I blacklisted iwl3945, and the boot goes normally with no hang
(replicated about 50 times)
So I tried the following at the shell:
# while true; do modprobe iwl3945; sleep 0.1; modprobe -r iwl3945; sleep
0.1; done
Unfortunately this did not cause a hang, even after hundreds of
iterations.
The
Not only does this hang, frequently; I also saw the following
*wonderful* error message a few times:
Uhhuh. NMI received for unknown reason b1 on CPU 0.
You have some hardware problem, likely on the PCI bus.
Dazed and confused, but trying to continue.
Substituting tg3 for another driver
Note that I am able to reproduce the hang with the kill switch both on
and off, but it is far more common with the kill switch on (device
disabled)
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug notification because
On Fri, Oct 17, 2008 at 04:00:42PM -, Scott James Remnant wrote:
Note that I am able to reproduce the hang with the kill switch both on
and off, but it is far more common with the kill switch on (device
disabled)
That's consistent with my testing on David's machine: the frequency went up
Affects me too, happens on a HP 6510b. When it fails to boot my display
shows a lot of graphic error, thats why I first supposed it is an
graphic driver related error.
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug
On Wed, Oct 15, 2008 at 10:33:55PM -, Loïc Minier wrote:
I tried disabling snd-hda-intel, but I could reproduce the hang.
Interestingly, the hang happened further in the boot, at Activating
Yes, the hang seems to occur while the iwl3945 driver is initializing, which
continues after the
Matt Zimmerman wrote:
Can anyone else confirm, as stated in the bug description, that the problem
appeared between 2.6.27-1 and 2.6.27-2?
I don't remember that I ever used 2.6.27-1 kernel. Is there a simple way
to install it? I think that many people started to test 8.10 later, than
the kernel
Another helpful thing to try would be to try the instrumented iwl3945.ko
and iwlcore.ko modules I'm attaching now. These will print additional
debug information, so boot the system without quiet or splash and
send us a photo of what appears on the screen when it hangs.
** Attachment added:
Definitely happening with -2. Now trying -1 to see, if -2 is where it
started. Will then use your module the get more info.
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug notification because you are a member of
Unlike the bug reporter I also have hangs with -1.2. -1.1 not available,
so I tested 2.6.26-5.17 which turned out to be fine. Can anyone confirm
this?
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug notification
** Description changed:
- 2.6.27-7 (and -2 through -6) fails to boot on my system (Dell XPS M1710
- laptop). 2.6.27-1 boots fine.
+ Problem: Intrepid fails to boot on a variety of laptops using the
+ iwl3945 driver.
- I haven't been able to find a boot log, unfortunately. If I watch the
- boot
With a Thinkpad T60, 2.6.27-1 also caused a hard lockup for me. See bug
263330. I think the working on 2.6.27-1 must have been a red herring,
explainable since the problem is intermittent.
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
The kernel bug tracker which is attached to this report does list the
issue as RESOLVED/CODE_FIX. See
http://bugzilla.kernel.org/show_bug.cgi?id=11746 - does this help us?
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this
** Description changed:
Problem: Intrepid fails to boot on a variety of laptops using the
iwl3945 driver.
- Affected versions: 2.6.27-2 through 2.6.27-7. By at least one report,
- 2.6.27-1 does not exhibit the problem.
+ Affected versions: all 2.6.27 Intrepid kernels. 2.6.26 is reported
tor 2008-10-16 klockan 08:21 + skrev Matt Zimmerman:
Can anyone else confirm, as stated in the bug description, that the problem
appeared between 2.6.27-1 and 2.6.27-2?
I'm the bug reporter. I just tried 2.6.27-1.2, and it hanged.
I can't say for sure whether I ran 2.6.27-1.1
On Thu, Oct 16, 2008 at 12:26:43PM -, Stephan Klein wrote:
The kernel bug tracker which is attached to this report does list the
issue as RESOLVED/CODE_FIX. See
http://bugzilla.kernel.org/show_bug.cgi?id=11746 - does this help us?
No, unfortunately that is a different issue (bug 275227)
Here are my results with instrumented modules posted by Matt.
Different sequences each time.
Kernel 2.6.27-7-generic #1 SMP Fri Oct 10 03:55:24 UTC 2008 i686 GNU/Linux
Hope it helps.
** Attachment added: Screenshots, dmesg and lspci of hangs and successful boot
The screenshots with instrumented modules seem to indicate that the hang
is occurring sometimes while iwl3945 is initializing, and other times
after it is finished initializing. This hints that something else
happening in parallel is triggering the hang.
--
[regression] 2.6.27-7 sometimes fails
After blacklisting rfkill (just tried it because the driver was added with
2.6.27) the phy0 line showed up for the first time:
http://img.xrmb2.net/images/436677.jpeg
Wasn't there one hang later, though.
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
I think there is some weird racy stuff going on with rf-kill. In the
i3945 init code you can see that it disables the PCI device right before
it registers the rf-kill handler. This doesn't prevent the handler from
being called which looks like it might access the device, even though
its disabled.
Not very useful, but I'd like to add a I am NOT affected by this bug
comment. I use a Dell Inspiron 6400, Nvidia Driver, IWL3945, and I have
been using Intrepid both from live cd and as my default OS for two weeks
now. I have never had any problem at boot time, and actually this driver
is at its
On Thu, Oct 16, 2008 at 09:13:13AM -, Sander Jonkers wrote:
On Thu, Oct 16, 2008 at 10:41 AM, Alexey Balmashnov
[EMAIL PROTECTED] wrote:
Matt Zimmerman wrote:
Can anyone else confirm, as stated in the bug description, that the
problem
appeared between 2.6.27-1 and 2.6.27-2?
Screens of hangs with modified modules (sorry for the bad quality;
glossy screen and bad light):
http://img.xrmb2.net/images/724465.jpeg
http://img.xrmb2.net/images/718885.jpeg
http://img.xrmb2.net/images/166153.jpeg
http://img.xrmb2.net/images/331195.jpeg
http://img.xrmb2.net/images/409108.jpeg
On Thu, Oct 16, 2008 at 10:41 AM, Alexey Balmashnov
[EMAIL PROTECTED] wrote:
Matt Zimmerman wrote:
Can anyone else confirm, as stated in the bug description, that the problem
appeared between 2.6.27-1 and 2.6.27-2?
I don't remember that I ever used 2.6.27-1 kernel. Is there a simple way
Not very useful, but I'd like to add a I am NOT affected by this bug
comment. I use a Dell Inspiron 6400, Nvidia
Driver, IWL3945, and I have been using Intrepid both from live cd and as my
default OS for two weeks now. I have
never had any problem at boot time, and actually this driver
Luke12: Might be a very special model though. I myself have a Dell
Inspiron 6400 (though without NVidia), and I do have the bug.
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug notification because you are a member of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263059/comments/43
also has an Inspirion 6400 and the bug. Maybe the output of lspci -nn
could be helpful?
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug
What graphics driver are people using? I had funny interactions around
networking/compiz/radeon r500 using the open source radeon driver, which
I'm using at the moment.
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug
Here's my lspci -nn output.
** Attachment added: lspcinn
http://launchpadlibrarian.net/18612675/lspcinn
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug notification because you are a member of Ubuntu
Bugs, which
I use the Intel 915 driver (module i915) for graphics.
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hi, I'm experiencing the same bug with my ASUS F3JC laptop wich is
equiped with an ipw3945 card too. I don't think the graphic card has
something to see with this bug since I've a nVIDIA and the bug seems to
happen with Intel and Ati cards as well. I don't know if this is
important but I don't
I booted into the live cd (I think it had kernel -5 on it) today with no
problem also. That was on a Lenovo machine
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug notification because you are a member of Ubuntu
Bugs,
Neither do I actually; I have not experienced this bug either with nv
driver or the nvidia one. I am attaching here my lspci -nn. As for the
kernel version, I am using the last one provided, which is
2.6.27-7-generic. I have all the available updates repositories enabled.
Il giorno gio,
LumpyCustard: Please remember you usually need multiple boots (about 1
in 5 for me) to get a hang.
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Tim: when I tried my modprobe -r / modprobe loops, I tried playing with
the hardware wifi kill switch and didn't get the driver to catch in
hundreds of modprobe/modprobe -r cycles and a dozen of kill switch
on/off cycles.
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
I've narrowed it down to a call to ieee80211_register_hw() from within
the i3945 wireless driver, so I don't think its driver specific. Its
very racy, and seems to only happen at boot time.
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
FWIW, I just started to experience the hang very late, more like
2.6.27-5; definitively not yet in -3. However, I hardly ever reboot,
most of the time I just hibernate (which has never had this problem,
BTW).
I also could never reproduce it without quiet, and quite reliably with
quiet. Typically
I have to retract my last statement about the hang happening in
ieee80211_register_hw(). I have now observed the i3945 module init
process complete at least once right before a hang. That's going to make
things much more difficult because now I don't really know where to
look.
--
[regression]
I am seeing very similar problems with ipw2200. See bug #284406 for
details. All 2.6.27 kernels starting with 2.6.27-2.3-generic exhibit
the problem for me (I haven't tried a 2.6.27 kernel earlier than -2.3).
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
I tried some kernel debug features (without any change in behavior):
CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC=y
CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=1
CONFIG_DEBUG_LOCK_ALLOC=y
CONFIG_DEBUG_MUTEXES=y
CONFIG_DEBUG_PI_LIST=y
CONFIG_DEBUG_RT_MUTEXES=y
CONFIG_DEBUG_SPINLOCK=y
for what its worth, i've also seen the system hard freeze when trying to
connect to a wireless network. I've also only gotten 2 or 3 successful
boots (of course the first boot after upgrade worked!) in 15-20 tries
before booting from the install cd and blacklisting iwl3945 in
/etc/modprobe.d.
--
I also found that (didn't think it was worth mentioning before).
The first time I booted after upgrading, it was fine (then the auto-clean
kicked in and deleted all my old kernels)... then it wasn't fine.
Was this the same with everyone else?
--
[regression] 2.6.27-7 sometimes fails to boot
Nope, when I first updated I couldn't log in from the start. After a few
unsuccessful attempts to boot the 2.6.27 kernel, I settled on 2.6.24 and
only found out through this issue that the lockup actually only happens
sometimes. So, no. Pure random race condition, it seems.
--
[regression]
No, not with me. At first I had the idea it was related to a cold versus a
warm reboot, but now my hypothesis is that the halts happen randomly, with a
50 - 70% chance.
So the workaround of blacklist modprobe is very useful; it saves a lot a
time.
--
[regression] 2.6.27-7 sometimes fails to
I can confirm that blacklisting iwl3945 stops the hangs while
blacklisting snd_hda_intel (which gets initialized at the same time) did
not help.
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug notification because you
The description says that this problem appeared between 2.6.27-1 and
2.6.27-2. Can anyone else experiencing this problem confirm that?
If so, we can start reviewing the changes between those versions and
narrow the possibilities.
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945
It's been reported that, rather than blacklisting iwl3945, it's
sufficient to do the following:
echo 'install iwl3945 { sleep 5; /sbin/modprobe --ignore-install
iwl3945; }' | sudo tee /etc/modprobe.d/iwl3945
This introduces an artificial delay in the startup process before
loading iwl3945. It
Can the users who can reproduce this provide the full output from lspci
-nn on their systems?
Is anyone on the kernel team able to reproduce this problem?
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug notification
** Changed in: linux (Ubuntu Intrepid)
Target: None = ubuntu-8.10
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I can confirm the bug below is output from lspci -nn
If I have quiet on the command line it happens, remove it and the system
does not lock up.
pci=nomsi on the kernel line did not effect the bug, still happened.
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML
and
Some notes from debug I did in another bug: I tried modprobe -r /
modprobe in a loop and couldn't trigger the bug.
I also noticed that snd-hda-intel was often on the screen when it
crashed, so I tried modprobing that as well at the same time, to no
luck.
Finally, I also get hangs with
On Thu, Oct 16, 2008 at 12:07 AM, Steve Langasek
[EMAIL PROTECTED] wrote:
Can the users who can reproduce this provide the full output from lspci
-nn on their systems?
Attached.
--
Lucian
** Attachment added: iwl3945_2.6.27-7_regression__lspci_nn
** Attachment added: lspci-nn.txt
http://launchpadlibrarian.net/18585443/lspci-nn.txt
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Encountered this today while running a daily-live CD on my Thinkpad T61p. Not
only got a hang, but also (very) loud beeps during boot very soon after the
kernel was loaded.
Couldn't reproduce immediately so I wondered what it could be (now found this
bugreport).
Anyway, my lspci -nn is
This is mine! I still get hangs once in 4 times. I am running the
2.6.27-7 kernel.
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML
and 945GT Express Memory Controller Hub [8086:27a0] (rev 03)
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile
On Wed, Oct 15, 2008 at 09:25:20PM -, Loïc Minier wrote:
Some notes from debug I did in another bug: I tried modprobe -r /
modprobe in a loop and couldn't trigger the bug.
I also noticed that snd-hda-intel was often on the screen when it
crashed, so I tried modprobing that as well at the
Screen picture taken at lockup
** Attachment added: Screen pictures take at lockup, at the WiFI driver lockup
point
http://launchpadlibrarian.net/18585830/100_2226.JPG
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this
Screen picture taken at next reboot and it also locked up different
point.
** Attachment added: Screen picture taken at next reboot and it also locked up
different point.
http://launchpadlibrarian.net/18585859/100_2228.JPG
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
** Attachment added: lspci
http://launchpadlibrarian.net/18586463/lspci
--
[regression] 2.6.27-7 sometimes fails to boot (iwl3945 issue?)
https://bugs.launchpad.net/bugs/263059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Based on David's screenshots, and comparing to dmesg for a successful
boot on the same machine, it looks like it's crashing between:
iwl3945: Tunable channels: 11 802.11bg, 13 802.11a channels
and
phy0: Selected rate control algorithm 'iwl-3945-rs'
Is that consistent with what others are seeing?
1 - 100 of 148 matches
Mail list logo
