Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#12077 - [kernel26] Crash on Load Modules

Attached to Project: Arch Linux
Opened by Dani (compengi) - Monday, 10 November 2008, 19:33 GMT
Last edited by Roman Kyrylych (Romashka) - Sunday, 02 August 2009, 16:57 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture i686
Severity Medium
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I'm having issues during ArchLinux load on my HP Compaq nx5000 laptop. Sometimes during the boot or reboot (it happens in both cases), the system either hanges on `Load Modules` and doesn't display any trace, or it just crashes on load. But, in both cases you would need to shut down your laptop and boot it up again. Sometimes it happens consequently so you would require to boot couple of times to load into the system, or sometimes it just loads normaly without any problem.

PS: See `backtrace` file for the backtrace on the crash. I wrote this trace down from the monitor, so I hope I recopied it correctly.

Additional info:
* uname -a: Linux compengi 2.6.27-ARCH #1 SMP PREEMPT Sat Nov 8 10:11:43 UTC 2008 i686 Intel(R) Pentium(R) M processor 1500MHz GenuineIntel GNU/Linux
* xf86-video-intel 2.3.2-1 (Intel Corporation 82852/855GM Integrated Graphics Device (rev 02))
* alsa-lib 1.0.18-1
- alsa-utils 1.0.18-1
- alsa-oss 1.0.17-1
(Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01))
* lsmod|grep '^snd':
- snd_ac97_codec 100516 2 snd_intel8x0m,snd_intel8x0
- snd 50724 15 snd_pcsp
* lspci:
00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.3 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 01)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 01)
01:04.0 Network controller: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04)
01:06.0 CardBus bridge: Texas Instruments PCI7420 CardBus Controller
01:06.1 CardBus bridge: Texas Instruments PCI7420 CardBus Controller
01:06.3 Mass storage controller: Texas Instruments PCI7420/7620 Combo CardBus, 1394a-2000 OHCI and SD/MS-Pro Controller
01:0d.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link)
01:0e.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)

* /var/log/: My system crashed on Nov 10 19:47:11, So I added all the /var/log/ log lines during that instant, previous boot and next successive boots (Please see the attachment 'Logs During Crash Instant').

Steps to reproduce:
There are no specific steps to reproduce it. It occurs during the system boot or a reboot
   backtrace (1.2 KiB)
   Logs During Crash Instant (4.1 KiB)
   dmesg.log (24.6 KiB)
   kernel.log (76.4 KiB)
   messages.log (66.1 KiB)
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Sunday, 02 August 2009, 16:57 GMT
Reason for closing:  Upstream
Comment by Glenn Matthys (RedShift) - Thursday, 13 November 2008, 16:24 GMT
Can you please blacklist the ethernet/wireless modules and see if the problem still occurs?
Comment by Dani (compengi) - Friday, 14 November 2008, 14:53 GMT
I blacklisted wireless module "ipw2100" and tried to reboot/shutdown many times and load into the system, no sign of crash.
Comment by Glenn Matthys (RedShift) - Friday, 14 November 2008, 14:59 GMT
Then it's probably a race condition. You should file a bugreport at kernel.org.
Comment by Dani (compengi) - Saturday, 15 November 2008, 03:04 GMT
This would sound now funny http://bugzilla.kernel.org/show_bug.cgi?id=12030#c1
Comment by Dani (compengi) - Sunday, 23 November 2008, 19:38 GMT
It's an interesting situation, here they say it's kernel's bug and there they nothing to blame us, contact your distributor. And at the end the end-user bares the consequences. Maybe someone could tell me what on earth is going on?
Comment by Glenn Matthys (RedShift) - Sunday, 23 November 2008, 19:53 GMT
Dani forgot to mention in the bugreport that blacklisting ipw2100 solves his problem... So the orginal bug reporter failed to submit a proper bugreport to kernel.org.
Comment by Thomas Bächler (brain0) - Thursday, 11 December 2008, 07:56 GMT
Dani, you probably have to compile your own kernel with vanilla sources from kernel.org and reproduce the problem there to get help on kernel.org. I can just say that we don't apply "random patches" as they claim. Only ACPI got some, but that is not involved here, and some drivers (not the wireless drivers) get bugfixes.
Comment by Aaron Griffin (phrakture) - Wednesday, 11 February 2009, 20:07 GMT
Status on this? Is this fixed?
Comment by Eugene Markow (ejmarkow) - Sunday, 02 August 2009, 10:28 GMT
  • Field changed: Percent Complete (100% → 0%)
The exact type of crash and bug (and resolution - Blacklisting the Wireless Ethernet Controller Module) after "Loading Modules" has been occurring on my HP Compaq Laptop for every Kernel Version since the original Bug Report was made. This bug obviously hasn't been resolved upstream.

The only minor differences are:

- This bug has been occurring on previous kernels since the original bug report right up to the latest kernel Version (2.6.30.4-ARCHMOD). My kernel has been customized and compiled manually from the source located at www.kernel.org.

- My laptop is also a HP Compaq but different model (Presario CQ50).

- My wireless Ethernet controller is an Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01). Hence, I had to blacklist the module "ath5k" in rc.conf.
Comment by Roman Kyrylych (Romashka) - Sunday, 02 August 2009, 10:30 GMT
The bugzilla report has Status: REJECTED INSUFFICIENT_DATA
I suggest requesting reopen it with providing more data.
Also, do you have the same bug with Arch default kernel?
Comment by Eugene Markow (ejmarkow) - Sunday, 02 August 2009, 11:19 GMT
An update for this Bug Report will be made ASAP with additional info. For now, I recommend the temporary solution to this issue (blacklisting the Wireless Kernel Module in rc.conf) be made available to other users via the Arch Wiki. I've exprienced this bug with a customized Kernel which I compiled from source myself, and not the Arch default kernel. I always compile my kernels using the 'traditional' method (without package manager). A bug report will be filed to bugzilla to reflect more sufficient data. Once I blacklist my Atheros wireless module, there are no longer any crashes / freezes and everything works fine.

Here is my uname -a:

Linux Galicja 2.6.30.4-ARCHMOD #1 PREEMPT Fri Jul 31 07:48:00 CEST 2009 x86_64 Genuine Intel(R) CPU 575 @ 2.00GHz GenuineIntel GNU/Linux


Comment by Roman Kyrylych (Romashka) - Sunday, 02 August 2009, 16:57 GMT
Since there's no patch we can apply and blacklisting should be done by users manually anyway - I don't see a reason to keep this open.
Feel free to add a notice about this issue with instructions for workaround to the wiki.
Thank you for reporting to kernel bugzilla.

Loading...