[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#800792: linux-image-4.2.0-1-amd64 hangs during boot at network



Am Samstag, 3. Oktober 2015, 19:02:53 schrieb Geert Stappers:

 

Hi Geert,

 

I will see, if I can help.

>

> Please provide more information, example given:

>

> * Log messages

Sorry, I believe, there are no usable logfiles available as it happens at boot.

 

> * Hardware being used

The problem appears on all my systems. I have a notebook with nvidia network card (MCP51), a desktop with a rtl-8169 and a EEEPC 1005HA netbook on which I write this mail:
01:00.0 Ethernet controller: Qualcomm Atheros AR8132 Fast Ethernet (rev c0)
02:00.0 Network controller: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01
)

 


 

> * Which kernel modules being used

I am using standard kernel modules. For wlan on the notebook it is ath5k.ko, on the netbook it uses ath9k.ko.

 

> * What you mean by boot. Is a cold boot or a resume after suspend?

The term "at boot" means a cold boot, when the device was powered off and starts first. Besides I want to mention, that resuming from suspend, the wlan device does not work again. I forgot this to mention, but maybe this is another bug. This behaviour also appears since kernel 4.0 and higher. With 3.16 this also worked fine.

 

> * kernel boot parameters

>

 

See my /etc/default/grub:

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=1024x600
GRUB_GFXPAYLOAD_LINUX=keep

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
    
Hope this helps.

 

Best

 

Hans

 

>

> Groeten

> Geert Stappers

 


Reply to: