Thanks for your suggestion. I checked the Bios setup. There is an option of
LAN/WLAN switching, which was on, and created the problem I reported earlier.
Therefore, I request you to close the bug.
Thanks again for your time.
Subhashis
On Saturday, 12 April 2014 4:06 AM, Ben Hutchings wrote:
ted, and it gives me a busybox shell.
However, when kernel panic happened it happened much earlier, and no
commands would
work (including ALT-Sysrq-B to reboot).
I could cause the old kernel to also panic in one such occasion.
Hope these give some clues.
Regards,
Subhashis
On Wed, May 1, 2013
Hi,
> This panic is expected if the root filesystem could not be mounted. So
> the question is, why did that fail? Is the root device a simple
> partition or logical volume? Is the physical device attached by SATA,
> USB, or other means?
The root device is a simple partition '/dev/sda2' (the d
Hi,
Thanks for your mail.
I have not found any such problem after upgrading to Etch.
Etch kernel ran fine for a few days I used.
I am running unmodified stock kernel 2.6.20.10 for more than 2 months,
and the system never locked up in this time.
Therefore, you can close the bug from Etch onwards
. 8 8 8 0 0 24 8 16 16 16 0 0 0 Slow
---This is certainly repeatable.SubhashisOn 16/07/06, Bastian Blank <[EMAIL PROTECTED]
> wrote:severity 378487 importanttags 378487 moreinfothanksOn Sun, Jul 16, 2006
Package: linux-2.6
Version: 2.6.17-3
Severity: critical
Justification: breaks the whole system
I have downloaded the kernel source linux-2.6_2.6.17.orig.tar.gz,
linux-2.6_2.6.17-3.diff.gz and linux-2.6_2.6.17-3.dsc from Debian
Unstable, and used 'dpkg-source -x linux-2.6_2.6.17-3.dsc' which unpac
6 matches
Mail list logo
