[Bug 1885249] [NEW] hard lock kernel

2020-06-26 Thread swmike
Public bug reported:

Ubuntu 16.04 guest VM running under vmware hypervisor. VM is used for
running qemu/docker instances of virtual routers.

After upgrade to linux-image-4.4.0-184-generic we get hard-lockup of the
kernel (no interaction on the console, no crash report or anything) as
soon as VM is put under load (several minutes in, 5 virtual routers
started and configured).

VM was running -177 or -178 for ~50 days without issue. I tested -179 as
well, doesn't have this problem. linux-image-4.15.0-106-generic (latest
hwe kernel) also doesn't have this problem. All of these are Ubuntu
provided kernels installed using regular install process.

So to sum up:

Works: 4.4.0-177 to -179. 4.15.0-106 also works.

Doesn't work: 4.4.0-184 causes immediate problems (within 10 minutes
after starting this test/simulation environment). Hard-lockup only
happens during the test and seems to be either memory/load dependent.

Unfortunately I don't have any debug output because of this hard-lockup.

$ sudo dpkg --list | grep -i linux-image
ii  linux-image-4.15.0-106-generic 4.15.0-106.107~16.04.1   
   amd64   
Signed kernel image generic
rc  linux-image-4.4.0-177-generic  4.4.0-177.207
   amd64Signed kernel image generic
rc  linux-image-4.4.0-178-generic  4.4.0-178.208
   amd64Signed kernel image generic
ii  linux-image-4.4.0-179-generic  4.4.0-179.209
   amd64Signed kernel image generic
ii  linux-image-4.4.0-184-generic  4.4.0-184.214
   amd64Signed kernel image generic
ii  linux-image-generic4.4.0.184.190
   amd64Generic Linux kernel image
ii  linux-image-generic-hwe-16.04  4.15.0.106.111   
   amd64Generic Linux kernel image

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-184-generic 4.4.0-184.214
ProcVersionSignature: Ubuntu 4.15.0-106.107~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-106-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.23
Architecture: amd64
Date: Fri Jun 26 07:10:53 2020
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885249

Title:
  hard lock kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1885249/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821843] Re: 4.4.0-143 (xenial) contains a change that breaks out-of-tree modules

2019-04-05 Thread swmike
I was affected by this bug. Thanks for posting it so I could find it. I
installed the hwe kernel packages (4.15 kernel) for ubuntu 16.04,
removed the old 4.4 kernels, then Parallels tools installed just fine.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821843

Title:
  4.4.0-143 (xenial) contains a change that breaks out-of-tree modules

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821843/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1550823] Re: checkarray doesn't work with sh = dash

2016-09-05 Thread swmike
Hi,

I just ran into this. I am active on both the linux-raid mailing list,
and on the #linux-raid IRC channel. We frequently get people in both
places who have problems with their arrays, some of them is because of
lack of frequent "scrubbing" to find read errors on the drives.

This issue needs to be fixed before it turns into a huge disaster. The
current default behaviour of checkarray cron is that it's run first
sunday every month. This is a sensible default, but it's now broken in
Ubuntu.

Please fix this, before people start to lose data because checkarray
isn't currently working.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550823

Title:
  checkarray doesn't work with sh = dash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1550823/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1364091] Re: Possible RAID-6 corruption

2014-10-01 Thread swmike
Great, but what about the kernels for older LTS releases still under
support? Neil stated this affects all kernels back to and including
2.6.32. So I imagine 12.04 LTS and 10.04 LTS are also affected.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1364091

Title:
  Possible RAID-6 corruption

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1364091/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1364091] Re: Possible RAID-6 corruption

2014-09-22 Thread swmike
This problem affects all stable kernels from 2.6.32 and onwards, and
this patch needs to be applied to ALL kernels from that date to avoid
data corruption on double degraded RAID-6 volumes being written to.

This is not an mdadm problem, it's a kernel problem.

** Also affects: linux-kernel (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1364091

Title:
  Possible RAID-6 corruption

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kernel/+bug/1364091/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1364091] Re: Possible RAID-6 corruption

2014-09-22 Thread swmike
** Attachment added: Patch copy/pasted from Linux-raid mailing list
   
https://bugs.launchpad.net/ubuntu/+source/linux-kernel/+bug/1364091/+attachment/4211109/+files/patch-6b2d615d1094183588b11fc1.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1364091

Title:
  Possible RAID-6 corruption

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kernel/+bug/1364091/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1364091] Re: Possible RAID-6 corruption

2014-09-22 Thread swmike
diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
index 6b2d615d1094..183588b11fc1 100644
--- a/drivers/md/raid5.c
+++ b/drivers/md/raid5.c
@@ -3817,6 +3817,8 @@ static void handle_stripe(struct stripe_head *sh)
set_bit(R5_Wantwrite, dev-flags);
if (prexor)
continue;
+   if (s.failed  1)
+   continue;
if (!test_bit(R5_Insync, dev-flags) ||
((i == sh-pd_idx || i == sh-qd_idx)  
 s.failed == 0))

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1364091

Title:
  Possible RAID-6 corruption

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kernel/+bug/1364091/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1096294] Re: 8086:4236 Wifi regression in linux-image-3.2.0-35-generic-pae

2013-04-01 Thread swmike
With 3.2.0-39 and backported 3.6-wireless drivers I now get these:

[302142.996073] iwlwifi :03:00.0: fail to flush all tx fifo queues
[302145.004266] iwlwifi :03:00.0: fail to flush all tx fifo queues
[302147.996316] iwlwifi :03:00.0: fail to flush all tx fifo queues
[302150.996194] iwlwifi :03:00.0: fail to flush all tx fifo queues
[302150.996215] wlan0: deauthenticated from 00:21:91:dc:94:57 (Reason: 6)
[302151.022958] [ cut here ]
[302151.022993] WARNING: at 
/build/buildd/linux-backports-modules-3.2.0-3.2.0/debian/build/build-generic-pae/cw-3.6/drivers/net/wireless/iwlwifi/dvm/tx.c:1187
 iwlagn_rx_reply_tx+0x984/0x9b0 [iwldvm]()
[302151.023003] Hardware name: 7454CTO
[302151.023007] Modules linked in: tcp_diag inet_diag iwldvm(O) iwlwifi(O) 
pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) rfcomm(O) parport_pc 
bnep(O) ppdev binfmt_misc dm_crypt arc4 mac80211(O) dm_multipath 
snd_hda_codec_conexant thinkpad_acpi uvcvideo videodev snd_hda_intel 
snd_hda_codec snd_hwdep snd_pcm btusb(O) bluetooth(O) snd_seq_midi psmouse 
snd_rawmidi serio_raw crystalhd(C) cfg80211(O) snd_seq_midi_event compat(O) 
snd_seq snd_timer snd_seq_device snd soundcore snd_page_alloc nvram tpm_tis 
mei(C) mac_hid coretemp lp parport raid10 raid456 async_raid6_recov async_pq 
raid6_pq async_xor xor async_memcpy async_tx raid1 raid0 multipath linear wmi 
i915 drm_kms_helper drm i2c_algo_bit video [last unloaded: iwlwifi]
[302151.023169] Pid: 0, comm: swapper/0 Tainted: GWC O 
3.2.0-39-generic-pae #62-Ubuntu
[302151.023176] Call Trace:
[302151.023191]  [c159294f] ? printk+0x2d/0x2f
[302151.023204]  [c105a5b2] warn_slowpath_common+0x72/0xa0
[302151.023224]  [f92a6d44] ? iwlagn_rx_reply_tx+0x984/0x9b0 [iwldvm]
[302151.023243]  [f92a6d44] ? iwlagn_rx_reply_tx+0x984/0x9b0 [iwldvm]
[302151.023253]  [c105a602] warn_slowpath_null+0x22/0x30
[302151.023272]  [f92a6d44] iwlagn_rx_reply_tx+0x984/0x9b0 [iwldvm]
[302151.023297]  [f92b03ce] iwl_rx_dispatch+0x6e/0xe0 [iwldvm]
[302151.023308]  [c15a870d] ? _raw_spin_lock_irqsave+0x2d/0x40
[302151.023331]  [f87c3de1] iwl_irq_tasklet+0x761/0xe10 [iwlwifi]
[302151.023344]  [c1061270] ? local_bh_enable_ip+0x90/0x90
[302151.023353]  [c1060d93] tasklet_action+0x63/0x110
[302151.023362]  [c1061270] ? local_bh_enable_ip+0x90/0x90
[302151.023370]  [c10612f1] __do_softirq+0x81/0x1a0
[302151.023379]  [c1061270] ? local_bh_enable_ip+0x90/0x90
[302151.023385]  IRQ  [c1061636] ? irq_exit+0x76/0xa0
[302151.023401]  [c15b00db] ? do_IRQ+0x4b/0xc0
[302151.023411]  [c1017be8] ? sched_clock+0x8/0x10
[302151.023422]  [c107ffeb] ? sched_clock_local+0xcb/0x1c0
[302151.023431]  [c15aff30] ? common_interrupt+0x30/0x38
[302151.023441]  [c10800d8] ? sched_clock_local+0x1b8/0x1c0
[302151.023453]  [c132ad49] ? arch_local_irq_enable+0x7/0xb
[302151.023462]  [c132ba7d] ? acpi_idle_enter_bm+0x228/0x268
[302151.023474]  [c147e86d] ? cpuidle_idle_call+0xad/0x250
[302151.023485]  [c101075c] ? cpu_idle+0x9c/0xe0
[302151.023494]  [c15755a5] ? rest_init+0x5d/0x68
[302151.023505]  [c1879787] ? start_kernel+0x352/0x358
[302151.023514]  [c18793c6] ? pass_bootoption.constprop.2+0xe2/0xe2
[302151.023524]  [c18790ba] ? i386_start_kernel+0xa9/0xaf
[302151.023530] ---[ end trace feca50f599babef7 ]---
[302153.032315] iwlwifi :03:00.0: fail to flush all tx fifo queues
[302153.041310] cfg80211: All devices are disconnected, going to restore 
regulatory settings
[302153.041323] cfg80211: Restoring regulatory settings
[302153.041335] cfg80211: Calling CRDA to update world regulatory domain
[302153.052119] cfg80211: Ignoring regulatory request Set by core since the 
driver uses its own custom regulatory domain
[302153.052130] cfg80211: World regulatory domain updated:
[302153.052135] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
[302153.052144] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[302153.052152] cfg80211:   (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[302153.052160] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[302153.052168] cfg80211:   (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[302153.052175] cfg80211:   (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[302154.086893] cfg80211: Found new beacon on frequency: 5240 MHz (Ch 48) on 
phy2
[302156.406797] wlan0: authenticate with 00:21:91:dc:94:57
[302156.411971] wlan0: send auth to 00:21:91:dc:94:57 (try 1/3)
[302156.612062] wlan0: send auth to 00:21:91:dc:94:57 (try 2/3)
[302156.612606] wlan0: authenticated
[302156.614396] iwlwifi :03:00.0: Microcode SW error detected.  Restarting 
0x200.
[302156.614406] iwlwifi :03:00.0: CSR values:
[302156.614413] iwlwifi :03:00.0: (2nd byte of CSR_INT_COALESCING is 
CSR_INT_PERIODIC_REG)
[302156.614425] iwlwifi :03:00.0:CSR_HW_IF_CONFIG_REG: 0X00488304
[302156.614435] iwlwifi :03:00.0:  CSR_INT_COALESCING: 

[Bug 1096294] Re: 8086:4236 Wifi regression in linux-image-3.2.0-35-generic-pae

2013-03-24 Thread swmike
I rebooted into -39 after it was released. Now my 5Ghz network doesn't
seem to want to stay connected at all. I keep getting disconnected:

Mar 21 18:21:11 swm-laptop kernel: [606888.625371] watchdog: only one watchdog 
can use /dev/watchdog.
Mar 21 18:21:11 swm-laptop kernel: [606888.625377] watchdog: error registering 
/dev/watchdog (err=-16).
Mar 21 18:21:11 swm-laptop kernel: [606888.625379] mei: unable to register 
watchdog device.
Mar 21 18:21:14 swm-laptop kernel: [606891.729033] iwlwifi :03:00.0: Tx 
aggregation enabled on ra = 00:21:91:dc:94:57 ti
d = 0
Mar 21 18:21:16 swm-laptop kernel: [606893.486341] wlan0: deauthenticating from 
00:21:91:dc:94:57 by local choice (reason=3)
Mar 21 18:21:16 swm-laptop kernel: [606893.528541] cfg80211: All devices are 
disconnected, going to restore regulatory settings
Mar 21 18:21:16 swm-laptop kernel: [606893.528548] cfg80211: Restoring 
regulatory settings

Even booting 3.2.0-34 or 3.8.0 helps, so now I'm restricted to 2.4GHz. I
don't know if there was some other change that happened at the same time
(network manager) that might be causing this. I tried booting a daily
build of raring which had the same behaviour. I'm going to install
Windows 7 or windows 8 on a separate harddisk sometime and see if that
works ok, to rule out hardware problem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096294

Title:
  8086:4236 Wifi regression in linux-image-3.2.0-35-generic-pae

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1096294] Re: 8086:4236 Wifi regression in linux-image-3.2.0-35-generic-pae

2013-01-27 Thread swmike
I rebooted this morning, tried 3.2.0-36, didn't work, rebooted into
3.2.0-36 again, didn't work, rmmod/modprobe iwlwifi, still no go.
Rebooted into 3.8-rc5 listed above, wifi immediately started working.
Then rebooted into 3.2.0-36 again, which immediately worked.

No cold start above, just reboots.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096294

Title:
  8086:4236 Wifi regression in linux-image-3.2.0-35-generic-pae

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1096294] Re: 8086:4236 Wifi regression in linux-image-3.2.0-35-generic-pae

2013-01-25 Thread swmike
I downloaded linux-
image-3.8.0-030800rc5-generic_3.8.0-030800rc5.201301251535_i386.deb,
rebooted, noticed that it didn't have the iwlwifi module, rebooted back
into 3.2.0-36, had the wifi problem, rebooted to -34, worked, downloaded
the extra package (linux-image-
extra-3.8.0-030800rc5-generic_3.8.0-030800rc5.201301251535_i386.deb),
rebooted into 3.8.0-rc5, everything worked as it should.

Then I made a mistake and shut the computer down instead of rebooting.
Turned it back on and booted into -36 which worked, rebooted again to
-36 and still worked. So I think I have to wait 1-2 weeks until I can
totally confirm that -36 definitely doesn't work and 3.8.0-rc5 does. I
will update this bug report in 1-2 weeks again to confirm.

This is the dmesg output from 3.8.0-rc5:

[   34.247168] wlan0: authenticate with 00:21:91:dc:94:57
[   34.251974] wlan0: direct probe to 00:21:91:dc:94:57 (try 1/3)
[   34.342850] init: anacron main process (1450) killed by TERM signal
[   34.452035] wlan0: direct probe to 00:21:91:dc:94:57 (try 2/3)
[   34.496062] init: plymouth-stop pre-start process (2082) terminated with 
status 1
[   34.656029] wlan0: direct probe to 00:21:91:dc:94:57 (try 3/3)
[   34.860022] wlan0: authentication with 00:21:91:dc:94:57 timed out
[   42.951286] wlan0: authenticate with 00:21:91:dc:94:57
[   42.956772] wlan0: send auth to 00:21:91:dc:94:57 (try 1/3)
[   43.160038] wlan0: send auth to 00:21:91:dc:94:57 (try 2/3)
[   43.364036] wlan0: send auth to 00:21:91:dc:94:57 (try 3/3)
[   43.473487] wlan0: authenticated
[   43.476077] wlan0: associate with 00:21:91:dc:94:57 (try 1/3)
[   43.477066] wlan0: RX AssocResp from 00:21:91:dc:94:57 (capab=0x111 status=0 
aid=1)
[   43.480544] wlan0: associated
[   43.480610] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   43.480760] cfg80211: Calling CRDA for country: GB
[   43.492207] cfg80211: Regulatory domain changed to country: GB
[   43.492217] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
[   43.492223] cfg80211:   (2402000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 
mBm)
[   43.492229] cfg80211:   (517 KHz - 525 KHz @ 4 KHz), (N/A, 2000 
mBm)
[   43.492234] cfg80211:   (525 KHz - 533 KHz @ 4 KHz), (N/A, 2000 
mBm)
[   43.492239] cfg80211:   (549 KHz - 571 KHz @ 4 KHz), (N/A, 2700 
mBm)
[   43.566951] wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by 
00:21:91:dc:94:57
swmike@swm-laptop:~$ uname -a
Linux swm-laptop 3.8.0-030800rc5-generic #201301251535 SMP Fri Jan 25 20:55:12 
UTC 2013 i686 i686 i386 GNU/Linux

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096294

Title:
  8086:4236 Wifi regression in linux-image-3.2.0-35-generic-pae

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1096294] Re: Wifi regressioin in linux-image-3.2.0-35-generic-pae

2013-01-23 Thread swmike
Hello. Thanks for the interest in my problem.

I updated bios just now:

 *-firmware
  description: BIOS
  vendor: LENOVO
  physical id: 0
  version: 6DET72WW (3.22 )
  date: 10/25/2012
  size: 128KiB
  capacity: 8128KiB

I am now running -26 kernel. First cold boot after BIOS update worked ok
(wifi started working after a few direct probe retries), then I rebooted
again and got the excessive retries and wifi wouldn't associate. I tried
rmmod/modprobe iwlwifi 4 times, still no go, same behaviour. I then
rebooted the router and rmmod/insmod again, and then things started
working. The behaviour is a bit erratic, but it seems that the problem
occurs after 1-2 weeks of uptime for the router. Cold booting the X200
doesn't usually solve the problem either, I tried that with the -35
kernel.

I have had the X200 and the DIR-855 router for 4 years and never seen
this behaviour before the 3.2.0-35 kernel.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096294

Title:
  Wifi regressioin in linux-image-3.2.0-35-generic-pae

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1096294] Re: Wifi regressioin in linux-image-3.2.0-35-generic-pae

2013-01-23 Thread swmike
Hello. Typo above, I meant to say I am running -36 kernel. Sorry.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096294

Title:
  Wifi regressioin in linux-image-3.2.0-35-generic-pae

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1096294] Re: Wifi regressioin in linux-image-3.2.0-35-generic-pae

2013-01-18 Thread swmike
I just upgraded to the latest version, -36. The problem still occurs,
but I would like to quantify my statement.

Sometimes it just works after reboot. The last time I rebooted into -36,
it didn't work:

[   27.331188] wlan0: direct probe to 00:21:91:dc:94:57 (try 1/3)
[   27.528030] wlan0: direct probe to 00:21:91:dc:94:57 (try 2/3)
[   27.728030] wlan0: direct probe to 00:21:91:dc:94:57 (try 3/3)
[   27.928030] wlan0: direct probe to 00:21:91:dc:94:57 timed out
[   36.032700] wlan0: direct probe to 00:21:91:dc:94:57 (try 1/3)
[   36.232028] wlan0: direct probe to 00:21:91:dc:94:57 (try 2/3)
[   36.432030] wlan0: direct probe to 00:21:91:dc:94:57 (try 3/3)
[   36.632043] wlan0: direct probe to 00:21:91:dc:94:57 timed out
[   44.940623] wlan0: direct probe to 00:21:91:dc:94:57 (try 1/3)
[   45.140051] wlan0: direct probe to 00:21:91:dc:94:57 (try 2/3)
[   45.340044] wlan0: direct probe to 00:21:91:dc:94:57 (try 3/3)
[   45.540044] wlan0: direct probe to 00:21:91:dc:94:57 timed out
[   61.945281] wlan0: direct probe to 00:21:91:dc:94:57 (try 1/3)
[   62.144064] wlan0: direct probe to 00:21:91:dc:94:57 (try 2/3)
[   62.344069] wlan0: direct probe to 00:21:91:dc:94:57 (try 3/3)
[   62.544064] wlan0: direct probe to 00:21:91:dc:94:57 timed out
[   70.851155] wlan0: direct probe to 00:21:91:dc:94:57 (try 1/3)
[   71.048040] wlan0: direct probe to 00:21:91:dc:94:57 (try 2/3)
[   71.248147] wlan0: direct probe to 00:21:91:dc:94:57 (try 3/3)
[   71.448132] wlan0: direct probe to 00:21:91:dc:94:57 timed out

I then rmmod iwlwifi and insmoded it again:

Then after a few retries, it started working:

[   79.664793] iwlwifi :03:00.0: PCI INT A disabled
[   84.661642] Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
[   84.661645] Copyright(c) 2003-2011 Intel Corporation
[   84.661694] iwlwifi :03:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17
[   84.661706] iwlwifi :03:00.0: setting latency timer to 64
[   84.661730] iwlwifi :03:00.0: pci_resource_len = 0x2000
[   84.661732] iwlwifi :03:00.0: pci_resource_base = f845c000
[   84.661734] iwlwifi :03:00.0: HW Revision ID = 0x0
[   84.661819] iwlwifi :03:00.0: irq 44 for MSI/MSI-X
[   84.661861] iwlwifi :03:00.0: Detected Intel(R) Ultimate N WiFi Link 
5300 AGN, REV=0x24
[   84.661922] iwlwifi :03:00.0: L1 Disabled; Enabling L0S
[   84.683775] iwlwifi :03:00.0: device EEPROM VER=0x11f, CALIB=0x4
[   84.683778] iwlwifi :03:00.0: Device SKU: 0Xf0
[   84.683802] iwlwifi :03:00.0: Tunable channels: 13 802.11bg, 24 802.11a 
channels
[   84.687839] iwlwifi :03:00.0: loaded firmware version 8.83.5.1 build 
33692
[   84.688113] Registered led device: phy1-led
[   84.688143] cfg80211: Ignoring regulatory request Set by core since the 
driver uses its own custom regulatory domain
[   84.689366] ieee80211 phy1: Selected rate control algorithm 'iwl-agn-rs'
[   84.701998] iwlwifi :03:00.0: L1 Disabled; Enabling L0S
[   84.705005] iwlwifi :03:00.0: Radio type=0x0-0x2-0x0
[   84.857046] iwlwifi :03:00.0: L1 Disabled; Enabling L0S
[   84.860047] iwlwifi :03:00.0: Radio type=0x0-0x2-0x0
[   84.909114] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   84.910215] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   86.730788] cfg80211: Found new beacon on frequency: 5200 MHz (Ch 40) on phy1
[   92.666348] wlan0: direct probe to 00:21:91:dc:94:57 (try 1/3)
[   92.864153] wlan0: direct probe to 00:21:91:dc:94:57 (try 2/3)
[   93.064230] wlan0: direct probe to 00:21:91:dc:94:57 (try 3/3)
[   93.264175] wlan0: direct probe to 00:21:91:dc:94:57 timed out
[  101.366922] wlan0: direct probe to 00:21:91:dc:94:57 (try 1/3)
[  101.564078] wlan0: direct probe to 00:21:91:dc:94:57 (try 2/3)
[  101.565194] wlan0: direct probe responded
[  101.580086] wlan0: authenticate with 00:21:91:dc:94:57 (try 1)
[  101.580568] wlan0: authenticated
[  101.586846] wlan0: associate with 00:21:91:dc:94:57 (try 1)
[  101.784051] wlan0: associate with 00:21:91:dc:94:57 (try 2)
[  101.785446] wlan0: RX AssocResp from 00:21:91:dc:94:57 (capab=0x111 status=0 
aid=3)
[  101.785454] wlan0: associated
[  101.794763] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  101.794823] cfg80211: Calling CRDA for country: GB
[  101.801145] cfg80211: Updating information on frequency 2412 MHz for a 20 
MHz width channel with regulatory rule:
[  101.801149] cfg80211: 2402000 KHz - 2482000 KHz @ 4 KHz), (N/A mBi, 2000 
mBm)
[  101.801152] cfg80211: Updating information on frequency 2417 MHz for a 20 
MHz width channel with regulatory rule:
[  101.801154] cfg80211: 2402000 KHz - 2482000 KHz @ 4 KHz), (N/A mBi, 2000 
mBm)
[  101.801156] cfg80211: Updating information on frequency 2422 MHz for a 20 
MHz width channel with regulatory rule:
[  101.801159] cfg80211: 2402000 KHz - 2482000 KHz @ 4 KHz), (N/A mBi, 2000 
mBm)
[  101.801161] cfg80211: Updating information on frequency 2427 MHz for a 20 
MHz width channel with regulatory rule:
[  

[Bug 1096294] Re: Wifi regressioin in linux-image-3.2.0-35-generic-pae

2013-01-04 Thread swmike
: CONEXANT Analog [CONEXANT Analog]
+Subdevices: 1/1
+Subdevice #0: subdevice #0
+ ApportVersion: 2.0.1-0ubuntu15.1
+ Architecture: i386
+ ArecordDevices:
+   List of CAPTURE Hardware Devices 
+  card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
+Subdevices: 1/1
+Subdevice #0: subdevice #0
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  swmike 2420 F pulseaudio
+ CRDA:
+  country GB:
+   (2402 - 2482 @ 40), (N/A, 20)
+   (5170 - 5250 @ 40), (N/A, 20)
+   (5250 - 5330 @ 40), (N/A, 20), DFS
+   (5490 - 5710 @ 40), (N/A, 27), DFS
+ Card0.Amixer.info:
+  Card hw:0 'Intel'/'HDA Intel at 0xf2b2 irq 49'
+Mixer name : 'Conexant CX20561 (Hermosa)'
+Components : 'HDA:14f15051,17aa20ff,0010'
+Controls  : 21
+Simple ctrls  : 13
+ Card29.Amixer.info:
+  Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
7XHT24WW-1.06'
+Mixer name : 'ThinkPad EC 7XHT24WW-1.06'
+Components : ''
+Controls  : 1
+Simple ctrls  : 1
+ Card29.Amixer.values:
+  Simple mixer control 'Console',0
+Capabilities: pswitch pswitch-joined penum
+Playback channels: Mono
+Mono: Playback [on]
+ DistroRelease: Ubuntu 12.04
+ EcryptfsInUse: Yes
+ HibernationDevice: RESUME=/dev/sda6
+ MachineType: LENOVO 7454CTO
+ MarkForUpload: True
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: root=UUID=2a9a0898-4ec3-4685-a9ac-9afae45ad815 ro quiet 
splash
+ ProcVersionSignature: Ubuntu 3.2.0-35.55-generic-pae 3.2.34
+ PulseList:
+  Error: command ['pacmd', 'list'] failed with exit code 1: Home directory 
/home/swmike not ours.
+  No PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-3.2.0-35-generic-pae N/A
+  linux-backports-modules-3.2.0-35-generic-pae  N/A
+  linux-firmware1.79.1
+ StagingDrivers: crystalhd mei
+ Tags:  precise staging
+ Uname: Linux 3.2.0-35-generic-pae i686
+ UpgradeStatus: Upgraded to precise on 2012-04-27 (253 days ago)
+ UserGroups:
+  
+ WpaSupplicantLog:
+  
+ dmi.bios.date: 05/16/2011
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: 6DET70WW (3.20 )
+ dmi.board.name: 7454CTO
+ dmi.board.vendor: LENOVO
+ dmi.board.version: Not Available
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: Not Available
+ dmi.modalias: 
dmi:bvnLENOVO:bvr6DET70WW(3.20):bd05/16/2011:svnLENOVO:pn7454CTO:pvrThinkPadX200:rvnLENOVO:rn7454CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
+ dmi.product.name: 7454CTO
+ dmi.product.version: ThinkPad X200
+ dmi.sys.vendor: LENOVO

** Attachment added: AcpiTables.txt
   
https://bugs.launchpad.net/bugs/1096294/+attachment/3474650/+files/AcpiTables.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096294

Title:
  Wifi regressioin in linux-image-3.2.0-35-generic-pae

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1096294] AlsaDevices.txt

2013-01-04 Thread swmike
apport information

** Attachment added: AlsaDevices.txt
   
https://bugs.launchpad.net/bugs/1096294/+attachment/3474651/+files/AlsaDevices.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096294

Title:
  Wifi regressioin in linux-image-3.2.0-35-generic-pae

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1096294] BootDmesg.txt

2013-01-04 Thread swmike
apport information

** Attachment added: BootDmesg.txt
   
https://bugs.launchpad.net/bugs/1096294/+attachment/3474652/+files/BootDmesg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096294

Title:
  Wifi regressioin in linux-image-3.2.0-35-generic-pae

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1096294] Card0.Amixer.values.txt

2013-01-04 Thread swmike
apport information

** Attachment added: Card0.Amixer.values.txt
   
https://bugs.launchpad.net/bugs/1096294/+attachment/3474653/+files/Card0.Amixer.values.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096294

Title:
  Wifi regressioin in linux-image-3.2.0-35-generic-pae

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1096294] Card0.Codecs.codec.0.txt

2013-01-04 Thread swmike
apport information

** Attachment added: Card0.Codecs.codec.0.txt
   
https://bugs.launchpad.net/bugs/1096294/+attachment/3474654/+files/Card0.Codecs.codec.0.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096294

Title:
  Wifi regressioin in linux-image-3.2.0-35-generic-pae

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1096294] CurrentDmesg.txt

2013-01-04 Thread swmike
apport information

** Attachment added: CurrentDmesg.txt
   
https://bugs.launchpad.net/bugs/1096294/+attachment/3474655/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096294

Title:
  Wifi regressioin in linux-image-3.2.0-35-generic-pae

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1096294] IwConfig.txt

2013-01-04 Thread swmike
apport information

** Attachment added: IwConfig.txt
   
https://bugs.launchpad.net/bugs/1096294/+attachment/3474656/+files/IwConfig.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096294

Title:
  Wifi regressioin in linux-image-3.2.0-35-generic-pae

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1096294] Lspci.txt

2013-01-04 Thread swmike
apport information

** Attachment added: Lspci.txt
   https://bugs.launchpad.net/bugs/1096294/+attachment/3474657/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096294

Title:
  Wifi regressioin in linux-image-3.2.0-35-generic-pae

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1096294] Lsusb.txt

2013-01-04 Thread swmike
apport information

** Attachment added: Lsusb.txt
   https://bugs.launchpad.net/bugs/1096294/+attachment/3474658/+files/Lsusb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096294

Title:
  Wifi regressioin in linux-image-3.2.0-35-generic-pae

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1096294] PciMultimedia.txt

2013-01-04 Thread swmike
apport information

** Attachment added: PciMultimedia.txt
   
https://bugs.launchpad.net/bugs/1096294/+attachment/3474659/+files/PciMultimedia.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096294

Title:
  Wifi regressioin in linux-image-3.2.0-35-generic-pae

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1096294] ProcCpuinfo.txt

2013-01-04 Thread swmike
apport information

** Attachment added: ProcCpuinfo.txt
   
https://bugs.launchpad.net/bugs/1096294/+attachment/3474660/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096294

Title:
  Wifi regressioin in linux-image-3.2.0-35-generic-pae

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1096294] ProcEnviron.txt

2013-01-04 Thread swmike
apport information

** Attachment added: ProcEnviron.txt
   
https://bugs.launchpad.net/bugs/1096294/+attachment/3474661/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096294

Title:
  Wifi regressioin in linux-image-3.2.0-35-generic-pae

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1096294] ProcInterrupts.txt

2013-01-04 Thread swmike
apport information

** Attachment added: ProcInterrupts.txt
   
https://bugs.launchpad.net/bugs/1096294/+attachment/3474662/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096294

Title:
  Wifi regressioin in linux-image-3.2.0-35-generic-pae

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1096294] ProcModules.txt

2013-01-04 Thread swmike
apport information

** Attachment added: ProcModules.txt
   
https://bugs.launchpad.net/bugs/1096294/+attachment/3474663/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096294

Title:
  Wifi regressioin in linux-image-3.2.0-35-generic-pae

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1096294] RfKill.txt

2013-01-04 Thread swmike
apport information

** Attachment added: RfKill.txt
   https://bugs.launchpad.net/bugs/1096294/+attachment/3474664/+files/RfKill.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096294

Title:
  Wifi regressioin in linux-image-3.2.0-35-generic-pae

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1096294] UdevDb.txt

2013-01-04 Thread swmike
apport information

** Attachment added: UdevDb.txt
   https://bugs.launchpad.net/bugs/1096294/+attachment/3474665/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096294

Title:
  Wifi regressioin in linux-image-3.2.0-35-generic-pae

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1096294] UdevLog.txt

2013-01-04 Thread swmike
apport information

** Attachment added: UdevLog.txt
   
https://bugs.launchpad.net/bugs/1096294/+attachment/3474666/+files/UdevLog.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096294

Title:
  Wifi regressioin in linux-image-3.2.0-35-generic-pae

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1096294] WifiSyslog.txt

2013-01-04 Thread swmike
apport information

** Attachment added: WifiSyslog.txt
   
https://bugs.launchpad.net/bugs/1096294/+attachment/3474667/+files/WifiSyslog.txt

** Changed in: linux (Ubuntu)
   Status: Incomplete = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096294

Title:
  Wifi regressioin in linux-image-3.2.0-35-generic-pae

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1096294] [NEW] Wifi regressioin in linux-image-3.2.0-35-generic-pae

2013-01-04 Thread swmike
Public bug reported:

Hello.

I have a Thinkpad X200 with Intel 5300 wifi card.

03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300
Subsystem: Intel Corporation Device 1011
Physical Slot: 1
Flags: bus master, fast devsel, latency 0, IRQ 48
Memory at f2a0 (64-bit, non-prefetchable) [size=8K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 00-21-6a-ff-ff-03-8c-26
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

After upgrading to 3.2.0-35 from 3.2.0-34 I have problems connecting to
my D-link DIR-855 on 5GHz. After rebooting the computer, I frequently
have to reboot my router in order to connect. Reloading (rmmod/modprobe)
iwlwifi doesn't help. I tried several times back and forth between
3.2.0-35 and 3.2.0-34 and with 3.2.0-34 I can always connect without
rebooting the router, but with -35 I have yet to be able to connect
directly after boot without rebooting the router. I can disconnect the
wifi (bring my computer with me in suspended mode, be somewhere else and
use it, and then bring it back home) and it can successfully connect.
It's just the initial connect after boot that is affected.

When it's trying to connect with -35 I get the following:

Jan  5 06:51:33 swm-laptop kernel: [   19.458855] cfg80211: Found new beacon on 
frequency: 5240 MHz (Ch 48) on phy0
Jan  5 06:51:38 swm-laptop kernel: [   24.955771] wlan0: direct probe to 
00:21:91:dc:94:57 (try 1/3)
Jan  5 06:51:38 swm-laptop kernel: [   25.152031] wlan0: direct probe to 
00:21:91:dc:94:57 (try 2/3)
Jan  5 06:51:39 swm-laptop kernel: [   25.352043] wlan0: direct probe to 
00:21:91:dc:94:57 (try 3/3)
Jan  5 06:51:39 swm-laptop kernel: [   25.552027] wlan0: direct probe to 
00:21:91:dc:94:57 timed out
Jan  5 06:51:47 swm-laptop kernel: [   33.759793] wlan0: direct probe to 
00:21:91:dc:94:57 (try 1/3)
Jan  5 06:51:47 swm-laptop kernel: [   33.956034] wlan0: direct probe to 
00:21:91:dc:94:57 (try 2/3)
Jan  5 06:51:47 swm-laptop kernel: [   34.156044] wlan0: direct probe to 
00:21:91:dc:94:57 (try 3/3)
Jan  5 06:51:48 swm-laptop kernel: [   34.356035] wlan0: direct probe to 
00:21:91:dc:94:57 timed out

After rebooting the router and rebooting with -35 again, I get the
following:

Jan  5 06:53:48 swm-laptop kernel: [   19.491134] cfg80211: Found new beacon on 
frequency: 5200 MHz (Ch 40) on phy0
Jan  5 06:53:54 swm-laptop kernel: [   25.334809] wlan0: authenticate with 
00:21:91:dc:94:57 (try 1)
Jan  5 06:53:54 swm-laptop kernel: [   25.532032] wlan0: authenticate with 
00:21:91:dc:94:57 (try 2)
Jan  5 06:53:54 swm-laptop kernel: [   25.533294] wlan0: authenticated
Jan  5 06:53:54 swm-laptop kernel: [   25.539144] wlan0: associate with 
00:21:91:dc:94:57 (try 1)
Jan  5 06:53:54 swm-laptop kernel: [   25.736038] wlan0: associate with 
00:21:91:dc:94:57 (try 2)
Jan  5 06:53:54 swm-laptop kernel: [   25.737848] wlan0: RX AssocResp from 
00:21:91:dc:94:57 (capab=0x111 status=0 aid=3)
Jan  5 06:53:54 swm-laptop kernel: [   25.737851] wlan0: associated
Jan  5 06:53:54 swm-laptop kernel: [   25.744338] ADDRCONF(NETDEV_CHANGE): 
wlan0: link becomes ready
Jan  5 06:53:54 swm-laptop kernel: [   25.744413] cfg80211: Calling CRDA for 
country: GB
Jan  5 06:53:54 swm-laptop kernel: [   25.750032] cfg80211: Updating 
information on frequency 2412 MHz for a 20 MHz width chan
nel with regulatory rule:
Jan  5 06:53:54 swm-laptop kernel: [   25.750036] cfg80211: 2402000 KHz - 
2482000 KHz @ 4 KHz), (N/A mBi, 2000 mBm)

... snip

Jan  5 06:53:54 swm-laptop kernel: [   25.750206] cfg80211: (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Jan  5 06:53:54 swm-laptop kernel: [   25.750209] cfg80211: (2402000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm)
Jan  5 06:53:54 swm-laptop kernel: [   25.750211] cfg80211: (517 KHz - 
525 KHz @ 4 KHz), (N/A, 2000 mBm)
Jan  5 06:53:54 swm-laptop kernel: [   25.750214] cfg80211: (525 KHz - 
533 KHz @ 4 KHz), (N/A, 2000 mBm)
Jan  5 06:53:54 swm-laptop kernel: [   25.750216] cfg80211: (549 KHz - 
571 KHz @ 4 KHz), (N/A, 2700 mBm)
Jan  5 06:53:54 swm-laptop kernel: [   25.840049] cfg80211: Found new beacon on 
frequency: 5200 MHz (Ch 40) on phy0
Jan  5 06:54:03 swm-laptop kernel: [   34.794517] iwlwifi :03:00.0: Tx 
aggregation enabled on ra = 00:21:91:dc:94:57 tid = 0

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096294

Title:
  Wifi regressioin in linux-image-3.2.0-35-generic-pae

To manage notifications about this bug go to:

[Bug 1030735] [NEW] problem hot-adding spare / internal bitmap problem

2012-07-30 Thread swmike
Public bug reported:

Hi.

I reported a problem with md-raid to the linux-raid mailing list:

http://www.spinics.net/lists/raid/msg39876.html

I there was told that this was a known bug in the mdadm version included
in 12.04 LTS, and asked to upgrade to 3.2.4 or later, which I did by
means of the mdadm version currently in proposed-upgrades. This worked
fine, so I am just creating this bug to encourage you to release the
version in proposed-upgrades as it seems to fix my problem.

I have however not rebooted the box, so the changes to initrd etc I have
not tested.

** Affects: mdadm (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1030735

Title:
  problem hot-adding spare / internal bitmap problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1030735/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 778857] Re: Intel Wireless 5300 stops working intermittently

2012-04-06 Thread swmike
I also have an X200 with 5300 Wifi. I had all kinds of problems, with
11.04, all problems went away with 11.10 with its 3.0.x kernel. Now even
11n works correctly.

I would recommend that this is marked as fixed for 11.10.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/778857

Title:
  Intel Wireless 5300 stops working intermittently

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/778857/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 778857] Re: Intel Wireless 5300 stops working intermittently

2011-05-08 Thread swmike
I have the exact same computer and wifi card (and Dlink DIR-855 access
point) and I found this discussion:

http://ubuntuforums.org/showthread.php?t=1605338

I applied the discussed workaround and rebooted:

:/etc/modprobe.d$ cat intel-5300-iwlagn-disable11n.conf
options iwlagn 11n_disable=1

This seems to have solved the problem, no wifi problem for 75 minutes
yet anyway.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/778857

Title:
  Intel Wireless 5300 stops working intermittently

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 647488] Re: when xorg starts, screen is corrupted

2010-10-08 Thread swmike
I dist-upgraded today and indeed, the issue didn't re-appear so it seems
fixed.

-- 
when xorg starts, screen is corrupted
https://bugs.launchpad.net/bugs/647488
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 647488] Re: when xorg starts, screen is corrupted

2010-10-02 Thread swmike
I do not have any xorg.conf file created, so it's running default.

With nomodeset I get 660 fps in glxgears, without it I get 60.

I don't really know what part of the solutions in the 6411525 bug you
want me to try, I don't really see any of them being applicable to my
problem.

I just distupgraded again and the problem still remains.

-- 
when xorg starts, screen is corrupted
https://bugs.launchpad.net/bugs/647488
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 647488] [NEW] when xorg starts, screen is corrupted

2010-09-25 Thread swmike
Public bug reported:

Binary package hint: xorg

I have a thinkpad T40 with a radeon mobility 7500.

On Sep 11 2010 I dist-upgraded my Ubuntu 10.10 and rebooted without any
problems, shut it off an didn't use it anymore.

On Sep 25 2010 I did the same, rebooted, and then after normal boot the
login screen is either black or has a few lines of pixels. System is
very unstable, after a few alt-ctrl-f1 and so on, the system freezes.

I have tried kernels 2.6.35-17, -20 and -22, plus a 2.6.36-rc5 from
kernel-ppa. All behave the same.

Doing FN-F7 (the switcher between internal/external screen) once most of
the times give a working screen. After login it's black/corrupted again,
FN-F7 workaround works again. I saw the machine freeze a couple of
times, seems generally unstable.

Booting with nomodeset makes everything work as normal without any
noticable stability problems. Doing the bug reporting on it now.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Sat Sep 25 14:57:00 2010
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5)
Lsusb:
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: IBM 23738CG
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
 Socket 1:
   3.3V 32-bit PC Card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic 
root=UUID=b6ee6e59-e112-4049-a362-cc8747b8bca4 ro quiet splash nomodeset
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
dmi.bios.date: 06/18/2007
dmi.bios.vendor: IBM
dmi.bios.version: 1RETDRWW (3.23 )
dmi.board.name: 23738CG
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn23738CG:pvrThinkPadT40:rvnIBM:rn23738CG:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 23738CG
dmi.product.version: ThinkPad T40
dmi.sys.vendor: IBM
system:
 distro: Ubuntu
 codename:   maverick
 architecture:   i686
 kernel: 2.6.35-22-generic

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug corruption i386 maverick

-- 
when xorg starts, screen is corrupted
https://bugs.launchpad.net/bugs/647488
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 647488] Re: when xorg starts, screen is corrupted

2010-09-25 Thread swmike

** Attachment added: BootDmesg.txt
   
https://bugs.launchpad.net/bugs/647488/+attachment/1634776/+files/BootDmesg.txt

** Attachment added: CurrentDmesg.txt
   
https://bugs.launchpad.net/bugs/647488/+attachment/1634777/+files/CurrentDmesg.txt

** Attachment added: Dependencies.txt
   
https://bugs.launchpad.net/bugs/647488/+attachment/1634778/+files/Dependencies.txt

** Attachment added: GdmLog.txt
   https://bugs.launchpad.net/bugs/647488/+attachment/1634779/+files/GdmLog.txt

** Attachment added: GdmLog1.txt
   https://bugs.launchpad.net/bugs/647488/+attachment/1634780/+files/GdmLog1.txt

** Attachment added: GdmLog2.txt
   https://bugs.launchpad.net/bugs/647488/+attachment/1634781/+files/GdmLog2.txt

** Attachment added: Lspci.txt
   https://bugs.launchpad.net/bugs/647488/+attachment/1634782/+files/Lspci.txt

** Attachment added: PciDisplay.txt
   
https://bugs.launchpad.net/bugs/647488/+attachment/1634783/+files/PciDisplay.txt

** Attachment added: ProcCpuinfo.txt
   
https://bugs.launchpad.net/bugs/647488/+attachment/1634784/+files/ProcCpuinfo.txt

** Attachment added: ProcInterrupts.txt
   
https://bugs.launchpad.net/bugs/647488/+attachment/1634785/+files/ProcInterrupts.txt

** Attachment added: ProcModules.txt
   
https://bugs.launchpad.net/bugs/647488/+attachment/1634786/+files/ProcModules.txt

** Attachment added: RelatedPackageVersions.txt
   
https://bugs.launchpad.net/bugs/647488/+attachment/1634787/+files/RelatedPackageVersions.txt

** Attachment added: UdevDb.txt
   https://bugs.launchpad.net/bugs/647488/+attachment/1634788/+files/UdevDb.txt

** Attachment added: UdevLog.txt
   https://bugs.launchpad.net/bugs/647488/+attachment/1634789/+files/UdevLog.txt

** Attachment added: XorgLog.txt
   https://bugs.launchpad.net/bugs/647488/+attachment/1634790/+files/XorgLog.txt

** Attachment added: XorgLogOld.txt
   
https://bugs.launchpad.net/bugs/647488/+attachment/1634791/+files/XorgLogOld.txt

** Attachment added: Xrandr.txt
   https://bugs.launchpad.net/bugs/647488/+attachment/1634792/+files/Xrandr.txt

** Attachment added: glxinfo.txt
   https://bugs.launchpad.net/bugs/647488/+attachment/1634793/+files/glxinfo.txt

** Attachment added: peripherals.txt
   
https://bugs.launchpad.net/bugs/647488/+attachment/1634794/+files/peripherals.txt

** Attachment added: setxkbmap.txt
   
https://bugs.launchpad.net/bugs/647488/+attachment/1634795/+files/setxkbmap.txt

** Attachment added: xdpyinfo.txt
   
https://bugs.launchpad.net/bugs/647488/+attachment/1634796/+files/xdpyinfo.txt

** Attachment added: xkbcomp.txt
   https://bugs.launchpad.net/bugs/647488/+attachment/1634797/+files/xkbcomp.txt

-- 
when xorg starts, screen is corrupted
https://bugs.launchpad.net/bugs/647488
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 575368] Re: opening mplayer stops sound

2010-07-25 Thread swmike
I've had this issue for 2 months now  (workaround mplayer -ao alsa), I
don't really want to use proposed packages, is there an estimation
when this will be fixed for everybody?

-- 
opening mplayer stops sound
https://bugs.launchpad.net/bugs/575368
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 439761] Re: swapper allocation failure?

2010-05-16 Thread swmike
Hi.

I just ran into this problem with fully updated 10.04. Please see
attached dmesg file, the swapper failure output is from the end.

X went into D-state after this and I had to reboot to get it back.

** Attachment added: dmesg from the event
   http://launchpadlibrarian.net/48555069/dmesg.100516.txt

-- 
swapper allocation failure?
https://bugs.launchpad.net/bugs/439761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 296275] Re: swapper: page allocation failure

2010-05-16 Thread swmike
#439761 seems to handle the same issue.

-- 
swapper: page allocation failure
https://bugs.launchpad.net/bugs/296275
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 516524] Re: text plugin: mountall status clobbers passphrase prompt

2010-05-15 Thread swmike
I'd just like to add that as far as I can see, this is completely fixed
in 10.04 and works beautifully, but it's still a problem in 9.10 (which
is not a problem for me personally).

-- 
text plugin: mountall status clobbers passphrase prompt
https://bugs.launchpad.net/bugs/516524
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 345226] Re: after resume, sshfs mounted dir can't be remounted immediately

2010-05-14 Thread swmike
I am now at 10.04 and the problem persists.

swm...@swm-laptop:~$ apport-collect 345226
The authorization page:
   
(https://edge.launchpad.net/+authorize-token?oauth_token=7279kJBV8SnpTzLLrL0wallow_permission=WRITE_PRIVATE)
should be opening in your browser. After you have authorized
this program to access Launchpad on your behalf you should come
back here and press Enter to finish the authentication process.

Package sshfs-fuse not installed and no hook available, ignoring
swm...@swm-laptop:~$ sudo dpkg --list | grep sshfs
[sudo] password for swmike: 
ii  sshfs  2.2-1build1  
   filesystem client based on SSH File Transfer


But basically what's happening is that the tcp session sshfs is running over 
has stalled after resuming suspend. I believe just as an IPv4 address is 
flushed after suspend, all active TCP sessions depending on that tcp session 
needs to be flushed as well. I am sshfs:ing from a 10.04 server as well, and 
the weird thing is that I can't find any TCP/22 corresponding to sshfs on 
either server or client, the only thing I can find is a unix socket:

swm...@swm-laptop:~$ netstat -anp | grep sshfs
unix  2  [ ] STREAM CONNECTED 889086   2201/sshfs  

swm...@swm-laptop:~$ ps auxw | grep sshfs
swmike2201  0.0  0.0  44916  1240 ?Ssl  May13   0:00 sshfs ub6: ub

I'm doing this over IPv6 btw. After killing sshfs and re-establishing
the sshfs session I now see a TCP/22 session belonging to ssh process,
so I guess sshfs talks to ssh via a stream socket.

-- 
after resume, sshfs mounted dir can't be remounted immediately
https://bugs.launchpad.net/bugs/345226
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 215497] Re: IPv6 configuration is not flushed when interface goes down

2010-05-08 Thread swmike
This problem still occurs in fully updated 10.04 LTS, just verified it.

I was connected to the network on both wlan0 and eth0 (different
networks for both IPv4 and IPv6), and unplugging eth0 made IPv4
addresses go away but the IPv6 addresses (and routes) were still present
so all IPv6 traffic was blackholed. I had to manually delete both IPv6
address and default and subnet route to eth0 to get IPv6 working again.

-- 
IPv6 configuration is not flushed when interface goes down
https://bugs.launchpad.net/bugs/215497
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 516524] Re: mountall status clobbers passphrase prompt with plymouth text plugin

2010-02-21 Thread swmike
Thanks for the excellent analysis of where the problem lies.

I would also like to add that on one machine I have /home on a
md-cryptsetup-lvm(pv/vg/lv)-xfs volume, just so whoever does the
testing includes this scenario in the testing before release. I can
verify myself if needed.

Thanks again to everybody involved!

-- 
mountall status clobbers passphrase prompt with plymouth text plugin
https://bugs.launchpad.net/bugs/516524
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 516524] Re: Passphrase request at bootup doesn't work properly

2010-02-07 Thread swmike
Basically this is done according to the following guide:

https://help.ubuntu.com/community/EncryptedFilesystemHowto3

Here's how to reproduce (even though this reproduction is actually worse
than what I've seen before, now I'm afraid of rebooting my karmic box
because it won't come up again):

Installed karmic alpha 2, and then dist-upgraded everything.

apt-get install mdadm
apt-get install cryptsetup
mdadm --create --level=1 --raid-devices=2 /dev/md0 /dev/sdb1 missing
cryptsetup luksFormat /dev/md0
cryptsetup luksOpen /dev/md0 md0_crypt
mkfs.ext3 /dev/mapper/md0_crypt
mkdir /t

/etc/crypttab:
# target name source device key file  options
md0_crypt /dev/md0 none luks

# /etc/fstab: add this
/dev/mapper/md0_crypt /t ext3 defaults 0 2

/etc/mdadm/mdadm.conf add this (change uuid):
ARRAY /dev/md0 level=raid1 num-device=2 UUID=c0357b84:18cb2297:8282d032:d2636449

That results in it just waiting for the volume, doesn't ask for the
crypt password. Then if you press esc, it drops to regular console and
you're allowed to enter the passphrase (cosmetically broken, but seems
to work to enter the passphrase).

Then after the crypted volume has been opened, nothing more happens.
Won't even go to rescue mode if that's chosen.

Will attach PNGs from the boot process.

-- 
Passphrase request at bootup doesn't work properly
https://bugs.launchpad.net/bugs/516524
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 516524] Re: Passphrase request at bootup doesn't work properly

2010-02-07 Thread swmike
What is shown when just booting straight up with the configuration.

** Attachment added: Screenshot-10.04-test [Running] - VirtualBox OSE.png
   
http://launchpadlibrarian.net/38868516/Screenshot-10.04-test%20%5BRunning%5D%20-%20VirtualBox%20OSE.png

-- 
Passphrase request at bootup doesn't work properly
https://bugs.launchpad.net/bugs/516524
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 516524] Re: Passphrase request at bootup doesn't work properly

2010-02-07 Thread swmike
After pressing ESC, or when removing quiet splash from grub.

** Attachment added: Screenshot-10.04-test [Running] - VirtualBox OSE-1.png
   
http://launchpadlibrarian.net/38868522/Screenshot-10.04-test%20%5BRunning%5D%20-%20VirtualBox%20OSE-1.png

-- 
Passphrase request at bootup doesn't work properly
https://bugs.launchpad.net/bugs/516524
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 516524] Re: Passphrase request at bootup doesn't work properly

2010-02-07 Thread swmike
After entering the passphrase nothing more happens, doesn't matter if
one tries rescue mode or not.

** Attachment added: Screenshot-10.04-test [Running] - VirtualBox OSE-2.png
   
http://launchpadlibrarian.net/38868535/Screenshot-10.04-test%20%5BRunning%5D%20-%20VirtualBox%20OSE-2.png

-- 
Passphrase request at bootup doesn't work properly
https://bugs.launchpad.net/bugs/516524
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 516524] Re: Passphrase request at bootup doesn't work properly

2010-02-07 Thread swmike
Even when failing the passphrase, nothing more happens, not even when
trying to go to rescue mode.

I had to boot live usb in the virtual machine to remove the /t-entry
from fstab to be able to get to the machine again so I could get the
information needed.

** Attachment added: Screenshot-10.04-test [Running] - VirtualBox OSE-3.png
   
http://launchpadlibrarian.net/38868561/Screenshot-10.04-test%20%5BRunning%5D%20-%20VirtualBox%20OSE-3.png

-- 
Passphrase request at bootup doesn't work properly
https://bugs.launchpad.net/bugs/516524
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 516524] [NEW] Passphrase request at bootup doesn't work properly

2010-02-03 Thread swmike
Public bug reported:

Hello.

I have two machines with crypted /home (one machine, this is directly on
a partition) and the other with crypted /home (on md) and / (using
alternate install method in 8.04 or 8.10). I have since upgraded these
to 9.10 and 10.04 respectively, and the 10.04 machines was running 9.10
at one point. Both of them worked perfectly in 9.04 in respect to the
passphrase was asked correctly and the boot procedure worked properly.

On all these machines, the entering of passphrase at boot works very
badly. Booting without quiet and splash yields the possibility to
enter it blindly in the boot process, because the request for passphrase
doesn't seem to be in the right place in the bootup process (at least
for crypted /home). With the machine with just crypted /home, I have to
type it multiple times (blindly) and after a few attempts it works.
Sometimes I have to drop to shell to do it manually and then resuming
the boot process.

With the 10.04 machine I also had the problem that when running with
splash and quiet, if the md the crypted volume resided on didn't come up
correctly, this wasn't even detected at all and the boot process would
just wait endlessly without asking to drop to rescue mode.

My crypted volumes are properly entered in /etc/crypttab:

sdb1_crypt /dev/disk/by-uuid/b23e9d57-2ecf-4411-bcbd-23ca39e924e5 none luks
md0_crypt /dev/md0 none luks

My guess is that crypted volumes (either directly on partitions or on
md) isn't part of the verification process for releases? I can supply
more information if needed, but I think it'll be pretty easy to
reproduce, just create a partition on the system, cryptsetup
luksFormat it, enter it in /etc/crypttab, start it manually, create an
fs on the /dev/mapper/volume , and then put this in /etc/fstab. Then
start to induce problems in the boot process and see what happens.

I can provide more information as needed, I can create a video as well
if needed.

** Affects: ubuntu
 Importance: Undecided
 Status: New

-- 
Passphrase request at bootup doesn't work properly
https://bugs.launchpad.net/bugs/516524
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 473876] Re: [LENOVO 7454CTO] suspend/resume failure

2009-11-13 Thread swmike
I have tried the workaround found in http://launchpad.net/~x301/
(deactivating CPU cores during suspend/resume) which worked well for me
in 8.10, this didn't help (actually gave me flashing moon during
suspend phase and not only during resume).

I also tried stopping gdm so I had no X server running, and then running
/etc/acpi/sleep.sh as root, this resulted in flashing moon-freeze
during suspend (didn't suspend properly) within 2-3 attempts (replicated
twice, first time it happened on second attempt, second time it happened
on third attempt).

I so far have not seen the problem occuring when it's actually
suspending (only when resuming) when I run with X server running and
without the workaround. I'm going to try to use it normally (with X)
with the workaround and report back later if it seems to change
anything.

-- 
[LENOVO 7454CTO] suspend/resume failure
https://bugs.launchpad.net/bugs/473876
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 473876] Re: [LENOVO 7454CTO] suspend/resume failure

2009-11-13 Thread swmike
The problem with freeze when running sleep.sh occurs even when doing
this from booting with single in the grub boot statement. When the
freeze occurs, the backlight is still lit, screen looks exactly as it
did before pressing enter, apart from the blinking moon.

-- 
[LENOVO 7454CTO] suspend/resume failure
https://bugs.launchpad.net/bugs/473876
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 473876] Re: [LENOVO 7454CTO] suspend/resume failure

2009-11-04 Thread swmike
I would like to supplement this bug report with a correction of what I
stated above. The screen does come on before the moon LED starts
flashing, so basically the password prompt is seen on the screen before
everything freezes.

-- 
[LENOVO 7454CTO] suspend/resume failure
https://bugs.launchpad.net/bugs/473876
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 473876] Re: [LENOVO 7454CTO] suspend/resume failure

2009-11-04 Thread swmike
When I was running 9.04, this wasn't a problem, so it's a regression
(was running 9.04 for the whole release cycle).

** Tags added: regression-release

-- 
[LENOVO 7454CTO] suspend/resume failure
https://bugs.launchpad.net/bugs/473876
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 335570] Re: [LENOVO 7454CTO] suspend/resume failure

2009-11-03 Thread swmike
I have had numerous problems with my X200 when resuming from suspend,
nothing starts up after opening the lid, the moon is flashing. This is
with fully updated karmic with the release kernel.

I do not have any more information as the machine never comes out of
suspend so I can see logs etc. It doesn't happen all the time.

-- 
[LENOVO 7454CTO] suspend/resume failure
https://bugs.launchpad.net/bugs/335570
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 296275] Re: swapper: page allocation failure

2009-10-19 Thread swmike
I just got this on a newer kernel:

[377422.270379] swapper: page allocation failure. order:0, mode:0x4020
[377422.270384] Pid: 0, comm: swapper Not tainted 2.6.28-15-generic #52-Ubuntu
[377422.270387] Call Trace:
[377422.270389]  IRQ  [802b6e1e] __alloc_pages_internal+0x3ee/0x500
[377422.270401]  [802dfe58] alloc_slab_page+0x28/0x30
[377422.270405]  [802e0f1a] new_slab+0x5a/0x210
[377422.270408]  [802e2538] __slab_alloc+0x188/0x290
[377422.270413]  [8024782c] ? find_busiest_group+0x1dc/0x9a0
[377422.270418]  [805aa17f] ? __netdev_alloc_skb+0x1f/0x40
[377422.270422]  [802e3447] __kmalloc_track_caller+0xd7/0x110
[377422.270425]  [805aa17f] ? __netdev_alloc_skb+0x1f/0x40
[377422.270429]  [805a9e1e] __alloc_skb+0x6e/0x150
[377422.270432]  [805aa17f] __netdev_alloc_skb+0x1f/0x40
[377422.270447]  [a00ad780] sky2_rx_alloc+0x80/0x140 [sky2]
[377422.270454]  [a00b09a9] receive_new+0x29/0x160 [sky2]
[377422.270460]  [a00b0c23] sky2_receive+0x143/0x280 [sky2]
[377422.270466]  [a00b220d] sky2_status_intr+0x17d/0x5a0 [sky2]
[377422.270473]  [a00b2697] sky2_poll+0x67/0x160 [sky2]
[377422.270477]  [805b4024] net_rx_action+0x104/0x240
[377422.270480]  [80256c4c] __do_softirq+0x9c/0x170
[377422.270484]  [80213d8c] call_softirq+0x1c/0x30
[377422.270488]  [80214ffd] do_softirq+0x5d/0xa0
[377422.270491]  [802569cd] irq_exit+0x8d/0xa0
[377422.270494]  [802152c5] do_IRQ+0xc5/0x110
[377422.270497]  [80212bf3] ret_from_intr+0x0/0x29
[377422.270499]  EOI  [8021a95a] ? mwait_idle+0x4a/0x50
[377422.270507]  [80210dd2] ? enter_idle+0x22/0x30
[377422.270511]  [80210e85] ? cpu_idle+0x65/0xc0
[377422.270515]  [806878cc] ? rest_init+0x5c/0x70
[377422.270517] Mem-Info:
[377422.270519] DMA per-cpu:
[377422.270521] CPU0: hi:0, btch:   1 usd:   0
[377422.270523] CPU1: hi:0, btch:   1 usd:   0
[377422.270525] DMA32 per-cpu:
[377422.270527] CPU0: hi:  186, btch:  31 usd: 175
[377422.270530] CPU1: hi:  186, btch:  31 usd: 181
[377422.270531] Normal per-cpu:
[377422.270533] CPU0: hi:  186, btch:  31 usd: 170
[377422.270535] CPU1: hi:  186, btch:  31 usd: 178
[377422.270539] Active_anon:113789 active_file:35082 inactive_anon:20522
[377422.270540]  inactive_file:1761059 unevictable:7 dirty:523227 
writeback:2505 unstable:0
[377422.270542]  free:7779 slab:66831 mapped:45316 pagetables:5195 bounce:0
[377422.270546] DMA free:6700kB min:4kB low:4kB high:4kB active_anon:0kB 
inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB 
present:5560kB pages_scanned:0 all_unreclaimable? yes
[377422.270549] lowmem_reserve[]: 0 2999 8049 8049
[377422.270556] DMA32 free:21788kB min:4276kB low:5344kB high:6412kB 
active_anon:25384kB inactive_anon:8872kB active_file:41816kB 
inactive_file:2592776kB unevictable:0kB present:3071712kB pages_scanned:0 
all_unreclaimable? no
[377422.270559] lowmem_reserve[]: 0 0 5050 5050
[377422.270565] Normal free:2628kB min:7200kB low:9000kB high:10800kB 
active_anon:429772kB inactive_anon:73216kB active_file:98512kB 
inactive_file:4451460kB unevictable:28kB present:5171200kB pages_scanned:136 
all_unreclaimable? no
[377422.270569] lowmem_reserve[]: 0 0 0 0
[377422.270573] DMA: 5*4kB 5*8kB 5*16kB 5*32kB 4*64kB 4*128kB 2*256kB 2*512kB 
0*1024kB 0*2048kB 1*4096kB = 6700kB
[377422.270585] DMA32: 5111*4kB 0*8kB 6*16kB 1*32kB 0*64kB 1*128kB 2*256kB 
1*512kB 0*1024kB 0*2048kB 0*4096kB = 21724kB
[377422.270595] Normal: 354*4kB 5*8kB 15*16kB 0*32kB 0*64kB 1*128kB 3*256kB 
0*512kB 0*1024kB 0*2048kB 0*4096kB = 2592kB
[377422.270606] 1797687 total pagecache pages
[377422.270608] 0 pages in swap cache
[377422.270610] Swap cache stats: add 0, delete 0, find 0/0
[377422.270612] Free swap  = 0kB
[377422.270614] Total swap = 0kB
[377422.274370] 2359280 pages RAM
[377422.274370] 339669 pages reserved
[377422.274370] 1841342 pages shared
[377422.274370] 230304 pages non-shared

-- 
swapper: page allocation failure
https://bugs.launchpad.net/bugs/296275
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 296275] Re: swapper: page allocation failure

2009-09-03 Thread swmike
Hi,

I have been running 9.04 for quite a while now (since its release), but
I have also upgraded to 8 gigs of ram and limited the TCP window size
used.

With these changes I have not seen the problem, so I don't know if they
still are there but that these changes made me not hit the problems
anymore.

-- 
swapper: page allocation failure
https://bugs.launchpad.net/bugs/296275
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 263260] Re: ipv6 stops working after a while

2009-09-03 Thread swmike
I have been successfully running 9.04 with the ubuntu provided kernels
since its release and haven't seen the problem since.

-- 
ipv6 stops working after a while
https://bugs.launchpad.net/bugs/263260
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 215497] Re: disable networking leaves ipv6 enabled

2009-07-26 Thread swmike
When you roam between different IPv6-enabled wlans it doesn't flush the
RA-learned addresses/routing when you change wlan:s, so after a while
you might have 3-4 different IPv6 /64 assigned to the wlan0 interface,
which of course doesn't work because it only has routing to the last one
but tries to use them all.

When wlan0 goes down, all v6-information needs to be flushed. This was
tested in jaunty. After flushing all info (routes and /64 dev) in ip -6
r l things started working again.

-- 
disable networking leaves ipv6 enabled
https://bugs.launchpad.net/bugs/215497
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 243251] Re: via velocity induced kernel oops/crash

2009-07-23 Thread swmike
I don't have this motherboard in use anymore (was too unstable) so I
have no idea whether this is still a problem or not.

-- 
via velocity induced kernel oops/crash
https://bugs.launchpad.net/bugs/243251
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 345226] [NEW] after resume, sshfs mounted dir can't be remounted immediately

2009-03-18 Thread swmike
Public bug reported:

Binary package hint: sshfs

After resuming from sleep on fully updated 9.04, sshfs mounted dir can't
be immediately remounted without using fusermount -u. So, I mounted the
sshfs dir, then put the laptop to sleep, then resumed it, then this
happens:

swm...@swm-laptop:~$ sshfs ub: ub
swm...@ub's password: 
fusermount: failed to open /etc/fuse.conf: Permission denied
mount: according to mtab, ub: is already mounted on /home/swmike/ub

swm...@swm-laptop:~$ fusermount -u ub
umount: /home/swmike/ub: not mounted
swm...@swm-laptop:~$ sshfs ub: ub
swm...@ub's password: 
swm...@swm-laptop:~$

This behaviour wasn't present as far as I can remember in 8.10, then the
sshfs mount just went away after sleep/resume and one could mount it
again without having to do fusermount -u.

This is on a 9.04 that I did fresh install on back in the alpha2 days or
so.

ii  sshfs  2.1-1
filesystem client based on SSH File Transfer

** Affects: sshfs-fuse (Ubuntu)
 Importance: Undecided
 Status: New

-- 
after resume, sshfs mounted dir can't be remounted immediately
https://bugs.launchpad.net/bugs/345226
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 331092] Re: iwlagn driver fails to find 5GHz draft-N access point with CONFIG_WIRELESS_OLD_REGULATORY=n for all intel wireless cards

2009-03-14 Thread swmike
Just as an update, I have a D-link DIR-855 purchased in Europe (I have
not updated the firmware so it should be the local one) and a Thinkpad
X200 with Intel 5300 purchased in the US, and it works properly for me.

-- 
iwlagn driver fails to find 5GHz draft-N access point with 
CONFIG_WIRELESS_OLD_REGULATORY=n for all intel wireless cards
https://bugs.launchpad.net/bugs/331092
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 331092] Re: iwlagn driver fails to find 5GHz draft-N access point with CONFIG_WIRELESS_OLD_REGULATORY=n for all intel wireless cards

2009-03-13 Thread swmike
Confirmed working on Thinkpad X200 with 5300 card.

-- 
iwlagn driver fails to find 5GHz draft-N access point with 
CONFIG_WIRELESS_OLD_REGULATORY=n for all intel wireless cards
https://bugs.launchpad.net/bugs/331092
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 331092] Re: IWL 5300 fails to find 5GHz draft-N access point with CONFIG_WIRELESS_OLD_REGULATORY=n

2009-02-25 Thread swmike
I tried adding:

options cfg80211 ieee80211_regdom=EU

on my Thinkpad X200 with Intel 5300. Makes wireless stop working
altogether, with the following log output:

cfg80211: Unknown parameter `ieee80211_regdom'

So the workaround from bug #288401 doesn't seem to be applicable here.

-- 
IWL 5300 fails to find 5GHz draft-N access point with 
CONFIG_WIRELESS_OLD_REGULATORY=n
https://bugs.launchpad.net/bugs/331092
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 331708] Re: wireless regression Intel 5300 stops working

2009-02-20 Thread swmike
** Description changed:

  I have a Lenovo Thinkpad X200 with Intel 5300ABGN.
  
  With linux-image-2.6.28-8-generic I can't connect to my D-link DIR-855
  wireless AP. I see a few other wireless networks with iwlist scanning,
  but not my 5GHz network. This has started misbehaving since linux-
  image-2.6.28-7-generic but seems to have stopped working completely in
  linux-image-2.6.28-8-generic.
  
  03:00.0 Network controller: Intel Corporation Wireless WiFi Link 5300
Subsystem: Intel Corporation Device 1011
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 2297
Region 0: Memory at f250 (64-bit, non-prefetchable) [size=8K]
Capabilities: access denied
Kernel driver in use: iwlagn
Kernel modules: iwlagn
  
  Wireless has worked flawlessly with 8.10 and up until linux-
  image-2.6.28-6-generic (I have been on Jaunty alpha since around
  christmas).
+ 
+ This could be a same problem described in #331092.

-- 
wireless regression Intel 5300 stops working
https://bugs.launchpad.net/bugs/331708
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 331708] [NEW] wireless regression Intel 5300 stops working

2009-02-19 Thread swmike
Public bug reported:

I have a Lenovo Thinkpad X200 with Intel 5300ABGN.

With linux-image-2.6.28-8-generic I can't connect to my D-link DIR-855
wireless AP. I see a few other wireless networks with iwlist scanning,
but not my 5GHz network. This has started misbehaving since linux-
image-2.6.28-7-generic but seems to have stopped working completely in
linux-image-2.6.28-8-generic.

03:00.0 Network controller: Intel Corporation Wireless WiFi Link 5300
Subsystem: Intel Corporation Device 1011
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 2297
Region 0: Memory at f250 (64-bit, non-prefetchable) [size=8K]
Capabilities: access denied
Kernel driver in use: iwlagn
Kernel modules: iwlagn

Wireless has worked flawlessly with 8.10 and up until linux-
image-2.6.28-6-generic (I have been on Jaunty alpha since around
christmas).

** Affects: ubuntu
 Importance: Undecided
 Status: New

-- 
wireless regression Intel 5300 stops working
https://bugs.launchpad.net/bugs/331708
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 327230] Re: Lost all graphics on Jaunty after last update.

2009-02-10 Thread swmike
For me everything works as normal when I boot 2.6.28-6, but it doesn't
work with 2.6.28-7 (This is on Lenovo Thinkpad X200 (Intel Centrino2
with GMA 4500 graphics).

-- 
Lost all graphics on Jaunty after last update.
https://bugs.launchpad.net/bugs/327230
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 327505] [NEW] graphics regression in 2.6.28-7 on intel GM4500 in jaunty

2009-02-09 Thread swmike
Public bug reported:

Binary package hint: linux-image-2.6.28-7-generic

When booting 2.6.28-7 on my Lenovo X200 with Intel GM4500 graphics
everything is normal until GDM starts, then I get a weird graphics
effect (vivid colours run across the screen for a second), then
everything goes black and keyboard stops working (not even caps lock
does anything).

HD seems to be working occasionally, so I guess the whole computer isn't
frozen. Booting back into 2.6.28-6 works as it should, so I guess this
is some kind of interaction with the intel graphics driver in the
2.6.28-7.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
graphics regression in 2.6.28-7 on intel GM4500 in jaunty
https://bugs.launchpad.net/bugs/327505
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 323878] [NEW] sound doesn't work until manually execute start-pulseaudio-x11

2009-02-01 Thread swmike
Public bug reported:

I am using a Lenovo Thinkpad X200 with Ubuntu 9.04 Alpha 3 (fully
updated). With the update of pulseaudio thursday, something went wrong
(worked well up until this update).

Symptoms: Sound doesn't work, mute button on thinkpad doesn't do
anything, volume up/down works (icon comes up and slider goes up and
down, still no sound).

If I kill pulseaudio process manually and execute start-pulseaudio-x11
from rxvt, sound starts working again.

I am not sure if this is really a pulseaudio problem or if it caused by
something gnome-related, but I thought I'd report it against pulseaudio.

From dpkg:

ii  pulseaudio0.9.14-0ubuntu2
PulseAudio sound server

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Status: New

-- 
sound doesn't work until manually execute start-pulseaudio-x11
https://bugs.launchpad.net/bugs/323878
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 323878] Re: sound doesn't work until manually execute start-pulseaudio-x11

2009-02-01 Thread swmike
*** This bug is a duplicate of bug 322374 ***
https://bugs.launchpad.net/bugs/322374

Marked as duplicate. If the other bug had a mention of the word
pulseaudio (one word) and/or sound it would be easier to find.

** This bug has been marked a duplicate of bug 322374
   [jaunty regression] Pulse Audio finds no card for output

-- 
sound doesn't work until manually execute start-pulseaudio-x11
https://bugs.launchpad.net/bugs/323878
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 296275] [NEW] swapper: page allocation failure

2008-11-10 Thread swmike
Public bug reported:

When running rtorrent with a lot of open TCP connections, I get page
allocation failures. Fully apt-get update:d 8.10.

I include lspci and complete dmesg (in same file).

$ uname -a
Linux ub 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:06 UTC 2008 x86_64 GNU/Linux

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
swapper: page allocation failure
https://bugs.launchpad.net/bugs/296275
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 296275] Re: swapper: page allocation failure

2008-11-10 Thread swmike
** Description changed:

  When running rtorrent with a lot of open TCP connections, I get page
  allocation failures. Fully apt-get update:d 8.10.
  
  I include lspci and complete dmesg (in same file).
  
  $ uname -a
  Linux ub 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:06 UTC 2008 x86_64 GNU/Linux
+ 
+ This is an Asus P5E-WS-PRO motherboard (Intel X38 based) with E6600
+ processor, and 2 gig ram.

-- 
swapper: page allocation failure
https://bugs.launchpad.net/bugs/296275
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 296275] Re: swapper: page allocation failure

2008-11-10 Thread swmike

** Attachment added: dmesg and lspci
   http://launchpadlibrarian.net/19534884/output.txt

-- 
swapper: page allocation failure
https://bugs.launchpad.net/bugs/296275
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 276943] Re: Resume from suspend doesn't not work on the Mobile 4 Series chipsets

2008-10-24 Thread swmike
I just want to chime in that I have the same problem. Lenovo X200,
resume from sleep gives me a mouse pointer on a black screen, and then
no response from the system. Default 8.10-rc install, intel display
drivers.

This is the only issue I have at this time with Intrepid...

-- 
Resume from suspend doesn't not work on the Mobile 4 Series chipsets
https://bugs.launchpad.net/bugs/276943
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 263260] Re: ipv6 stops working after a while

2008-09-04 Thread swmike
I have now tried kernel.org latest kernels of 2.6.25, 2.6.26 and 2.6.27
and they all have the same problem, I also booted a harlddy installation
with my kernel.org 2.6.26.3, and it had the same problem also.

The weird thing is that I had ipv6 working perfectly with my old hardy
installation (hard drive broke so I had to re-install).

I'm at loss as to what is going on here... No configuration has changed
on the cisco router and it's running a very recent IOS so there should
be no problem there either. I have disabled IGMP snooping on my switch,
didn't change anything either.

-- 
ipv6 stops working after a while
https://bugs.launchpad.net/bugs/263260
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 263260] Re: ipv6 stops working after a while

2008-09-03 Thread swmike
I ran the cron script for 14 hours, still worked, then I did the
following:

MikaelA7200Inf3#clear ipv6 neighbors
MikaelA7200Inf3#show ipv6 neighbors
MikaelA7200Inf3#

Now ping doesn't work again.

08:01:23.566375 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 
2a00:801:b::10  2a00:801::f: [icmp6 sum ok] ICMP6, echo request, length 64, 
seq 213
08:01:24.566375 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 
2a00:801:b::10  2a00:801::f: [icmp6 sum ok] ICMP6, echo request, length 64, 
seq 214
08:01:25.566346 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 32) 
fe80::240:63ff:fef5:17c2  2a00:801:b::1: [icmp6 sum ok] ICMP6, neighbor 
solicitation, length 32, who has 2a00:801:b::1
  source link-address option (1), length 8 (1): 00:40:63:f5:17:c2
0x:  0040 63f5 17c2
08:01:25.566992 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 
2a00:801:b::10  2a00:801::f: [icmp6 sum ok] ICMP6, echo request, length 64, 
seq 215
08:01:25.567307 IP6 (class 0xe0, hlim 255, next-header ICMPv6 (58) payload 
length: 24) 2a00:801:b::1  fe80::240:63ff:fef5:17c2: [icmp6 sum ok] ICMP6, 
neighbor advertisement, length 24, tgt is 2a00:801:b::1, Flags [router, 
solicited]
08:01:26.566375 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 
2a00:801:b::10  2a00:801::f: [icmp6 sum ok] ICMP6, echo request, length 64, 
seq 216
08:01:27.566374 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 
2a00:801:b::10  2a00:801::f: [icmp6 sum ok] ICMP6, echo request, length 64, 
seq 217
08:01:28.566375 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 
2a00:801:b::10  2a00:801::f: [icmp6 sum ok] ICMP6, echo request, length 64, 
seq 218
08:01:29.566375 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 
2a00:801:b::10  2a00:801::f: [icmp6 sum ok] ICMP6, echo request, length 64, 
seq 219
08:01:30.564590 IP6 (class 0xe0, hlim 255, next-header ICMPv6 (58) payload 
length: 32) fe80::20a:42ff:fedd:5470  fe80::240:63ff:fef5:17c2: [icmp6 sum ok] 
ICMP6, neighbor solicitation, length 32, who has fe80::240:63ff:fef5:17c2
  source link-address option (1), length 8 (1): 00:0a:42:dd:54:70
0x:  000a 42dd 5470
08:01:30.564622 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 24) 
fe80::240:63ff:fef5:17c2  fe80::20a:42ff:fedd:5470: [icmp6 sum ok] ICMP6, 
neighbor advertisement, length 24, tgt is fe80::240:63ff:fef5:17c2, Flags 
[solicited]
08:01:30.566380 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 
2a00:801:b::10  2a00:801::f: [icmp6 sum ok] ICMP6, echo request, length 64, 
seq 220
08:01:31.566377 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 
2a00:801:b::10  2a00:801::f: [icmp6 sum ok] ICMP6, echo request, length 64, 
seq 221
08:01:32.566375 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 
2a00:801:b::10  2a00:801::f: [icmp6 sum ok] ICMP6, echo request, length 64, 
seq 222

on the cisco router:

Sep  3 08:01:22.567: ICMPv6-ND: Sending NS for 2A00:801:B::10 on 
GigabitEthernet4/0
Sep  3 08:01:23.567: ICMPv6-ND: Sending NS for 2A00:801:B::10 on 
GigabitEthernet4/0
Sep  3 08:01:24.567: ICMPv6-ND: INCMP deleted: 2A00:801:B::10
Sep  3 08:01:24.567: ICMPv6-ND: INCMP - DELETE: 2A00:801:B::10
Sep  3 08:01:24.567: ICMPv6-ND: DELETE - INCMP: 2A00:801:B::10
Sep  3 08:01:24.567: ICMPv6-ND: Sending NS for 2A00:801:B::10 on 
GigabitEthernet4/0
Sep  3 08:01:25.563: ICMPv6-ND: Received NS for 2A00:801:B::1 on 
GigabitEthernet4/0 from FE80::240:63FF:FEF5:17C2
Sep  3 08:01:25.563: ICMPv6-ND: Sending NA for 2A00:801:B::1 on 
GigabitEthernet4/0
Sep  3 08:01:25.563: ICMPv6-ND: STALE - DELAY: FE80::240:63FF:FEF5:17C2
Sep  3 08:01:25.567: ICMPv6-ND: Sending NS for 2A00:801:B::10 on 
GigabitEthernet4/0
Sep  3 08:01:26.567: ICMPv6-ND: Sending NS for 2A00:801:B::10 on 
GigabitEthernet4/0
Sep  3 08:01:27.568: ICMPv6-ND: INCMP deleted: 2A00:801:B::10
Sep  3 08:01:27.568: ICMPv6-ND: INCMP - DELETE: 2A00:801:B::10
Sep  3 08:01:27.568: ICMPv6-ND: DELETE - INCMP: 2A00:801:B::10
Sep  3 08:01:27.568: ICMPv6-ND: Sending NS for 2A00:801:B::10 on 
GigabitEthernet4/0
Sep  3 08:01:28.568: ICMPv6-ND: Sending NS for 2A00:801:B::10 on 
GigabitEthernet4/0
Sep  3 08:01:29.568: ICMPv6-ND: Sending NS for 2A00:801:B::10 on 
GigabitEthernet4/0
Sep  3 08:01:30.564: ICMPv6-ND: DELAY - PROBE: FE80::240:63FF:FEF5:17C2
Sep  3 08:01:30.564: ICMPv6-ND: Sending NS for FE80::240:63FF:FEF5:17C2 on 
GigabitEthernet4/0
Sep  3 08:01:30.564: ICMPv6-ND: Received NA for FE80::240:63FF:FEF5:17C2 on 
GigabitEthernet4/0 from FE80::240:63FF:FEF5:17C2
Sep  3 08:01:30.564: ICMPv6-ND: PROBE - REACH: FE80::240:63FF:FEF5:17C2
Sep  3 08:01:30.568: ICMPv6-ND: INCMP deleted: 2A00:801:B::10
Sep  3 08:01:30.568: ICMPv6-ND: INCMP - DELETE: 2A00:801:B::10
Sep  3 08:01:30.568: ICMPv6-ND: DELETE - INCMP: 2A00:801:B::10
Sep  3 08:01:30.568: ICMPv6-ND: Sending NS for 2A00:801:B::10 on 
GigabitEthernet4/0

MikaelA7200Inf3#show ipv6 neighbors
IPv6 Address  Age 

[Bug 263260] Re: ipv6 stops working after a while

2008-09-02 Thread swmike
MikaelA7200Inf3#show ipv6 neighbors
MikaelA7200Inf3#

No neighbours due to no activity for 8+ hours (I rebooted with
2.6.26-5-generic last night, tried it again this morning (4-6 hours
without activity, still worked, then I tried it now after 8+ hours of
inactivity and it didn't work)) and the status after trying to send
pings from the linux box was the following:

MikaelA7200Inf3#show ipv6 neighbors
IPv6 Address  Age Link-layer Addr State Interface
FE80::240:63FF:FEF5:17C20 0040.63f5.17c2  REACH Gi4/0


[EMAIL PROTECTED]:~$ ip -6 n sh
2a00:801:b::1 dev eth0 lladdr 00:0a:42:dd:54:70 router STALE
[EMAIL PROTECTED]:~$ ping6 ipv6
PING ipv6(ipv6.swm.pp.se) 56 data bytes
^C
--- ipv6 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

[EMAIL PROTECTED]:~$ ip -6 n sh
2a00:801:b::1 dev eth0 lladdr 00:0a:42:dd:54:70 router DELAY
[EMAIL PROTECTED]:~$ ip -6 n sh
2a00:801:b::1 dev eth0 lladdr 00:0a:42:dd:54:70 router DELAY
[EMAIL PROTECTED]:~$ ping6 ipv6
PING ipv6(ipv6.swm.pp.se) 56 data bytes
^C
--- ipv6 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1012ms

[EMAIL PROTECTED]:~$ ip -6 n sh
2a00:801:b::1 dev eth0 lladdr 00:0a:42:dd:54:70 router REACHABLE
[EMAIL PROTECTED]:~$ ping6 ipv6
PING ipv6(ipv6.swm.pp.se) 56 data bytes
^C
--- ipv6 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 1999ms

[EMAIL PROTECTED]:~$ ip -6 n sh
fe80::20a:42ff:fedd:5470 dev eth0 lladdr 00:0a:42:dd:54:70 DELAY
2a00:801:b::1 dev eth0 lladdr 00:0a:42:dd:54:70 router REACHABLE

So this problem seems to occur  after more than 6 hours of inactivity
when the ns has completely timeouted, and I'm affected both by
2.6.26-5-generic and 2.6.27-2-generic. I didn't have this problem with a
kernel.org 2.6.26.3 that I compiled myself and ran for 38 days on hardy.

Could it be firewall related? I haven't done any configuration on
anything like Apparmour or anything like that, so I'm running default
settnigs in aspect to any firewall related applications.

-- 
ipv6 stops working after a while
https://bugs.launchpad.net/bugs/263260
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 263260] Re: ipv6 stops working after a while

2008-09-02 Thread swmike
I have restarted networking (networking stop  ifconfig eth0 down 
networking start  killall dhclient  networking reload)

Now everything works again. I have created a cron script that is run
every hour, that pings an ipv6 address. If the problem hasn't occured by
tomorrow again, then it must have something to do with neighbour
discovery from scratch, whether this is in the kernel or it's some
application or firewall that's causing the problem.

-- 
ipv6 stops working after a while
https://bugs.launchpad.net/bugs/263260
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 263260] Re: ipv6 stops working after a while

2008-09-01 Thread swmike
I've booted 2.6.26-5-generic now and going to let it run for 24 hours
and see what happens.

IPv6 is working right now after reboot anyway.

-- 
ipv6 stops working after a while
https://bugs.launchpad.net/bugs/263260
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 158018] Re: 7.10 installation doesn't work with MSI NX7600GT

2008-08-31 Thread swmike
Here is the output from uname, lspci, discover (didn't work, said no
bus found, should I use discover or discover1 package?), xresprobe.

** Attachment added: output from different diag commands
   http://launchpadlibrarian.net/17183938/gfxinfo.txt

-- 
7.10 installation doesn't work with MSI NX7600GT
https://bugs.launchpad.net/bugs/158018
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 158018] Re: 7.10 installation doesn't work with MSI NX7600GT

2008-08-31 Thread swmike
Couldn't get anything working (went into failsafe mode in 800x600) when
doing dpkg-reconfigure xserver-xorg so I ran it with an empty
xorg.conf instead. Hope it helps.

** Attachment added: xorg.0.log when running with empty xorg.conf
   http://launchpadlibrarian.net/17183942/Xorg.0.log

-- 
7.10 installation doesn't work with MSI NX7600GT
https://bugs.launchpad.net/bugs/158018
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 263260] [NEW] ipv6 stops working after a while

2008-08-31 Thread swmike
Public bug reported:

Binary package hint: linux-image-2.6.27-2-generic

I have configured ipv6 statically in /etc/network/interfaces. Had this
running with 8.04 and both 2.6.24 and own-compiled 2.6.26.3, no
problems. Now after fresh install of 8.10a4 I am having IPv6 trouble.

After bringing it up after boot, everything works:

Cisco router:

#show ipv6 neighbors 
IPv6 Address  Age Link-layer Addr State Interface
FE80::240:63FF:FEF5:17C20 0040.63f5.17c2  STALE Gi4/0
2A00:801:B::10  0 0040.63f5.17c2  STALE Gi4/0

On linux box:

PING 2a00:801:b::1(2a00:801:b::1) 56 data bytes
64 bytes from 2a00:801:b::1: icmp_seq=1 ttl=64 time=0.658 ms
64 bytes from 2a00:801:b::1: icmp_seq=2 ttl=64 time=0.332 ms
^C
--- 2a00:801:b::1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.332/0.495/0.658/0.163 ms
[EMAIL PROTECTED]:/mnt/tt/grub# ip -6 n
fe80::20a:42ff:fedd:5470 dev eth0 lladdr 00:0a:42:dd:54:70 DELAY
2a00:801:b::1 dev eth0 lladdr 00:0a:42:dd:54:70 router REACHABLE

Everything is fine, I can download updates via apt-get etc (via ipv6).

After a while the nd goes stale, and cisco router cannot reach the
neighbour anymore:

Aug 31 13:15:52.783: ICMPv6-ND: REACH - STALE: FE80::240:63FF:FEF5:17C2
Aug 31 13:17:43.176: ICMPv6: Sending echo request to 2A00:801:B::10
Aug 31 13:17:43.176: ICMPv6-ND: DELETE - INCMP: 2A00:801:B::10
Aug 31 13:17:43.176: ICMPv6-ND: Sending NS for 2A00:801:B::10 on 
GigabitEthernet4/0
Aug 31 13:17:44.176: ICMPv6-ND: Sending NS for 2A00:801:B::10 on 
GigabitEthernet4/0
Aug 31 13:17:45.176: ICMPv6-ND: Sending NS for 2A00:801:B::10 on 
GigabitEthernet4/0
Aug 31 13:17:45.176: ICMPv6: Sending echo request to 2A00:801:B::10
Aug 31 13:17:46.176: ICMPv6-ND: INCMP deleted: 2A00:801:B::10
Aug 31 13:17:46.176: ICMPv6-ND: INCMP - DELETE: 2A00:801:B::10
Aug 31 13:17:47.176: ICMPv6: Sending echo request to 2A00:801:B::10
Aug 31 13:17:47.176: ICMPv6-ND: DELETE - INCMP: 2A00:801:B::10
Aug 31 13:17:47.176: ICMPv6-ND: Sending NS for 2A00:801:B::10 on 
GigabitEthernet4/0
Aug 31 13:17:48.176: ICMPv6-ND: Sending NS for 2A00:801:B::10 on 
GigabitEthernet4/0
Aug 31 13:17:49.176: ICMPv6-ND: Sending NS for 2A00:801:B::10 on 
GigabitEthernet4/0
Aug 31 13:17:49.176: ICMPv6: Sending echo request to 2A00:801:B::10
Aug 31 13:17:50.176: ICMPv6-ND: INCMP deleted: 2A00:801:B::10
Aug 31 13:17:50.176: ICMPv6-ND: INCMP - DELETE: 2A00:801:B::10
Aug 31 13:17:51.176: ICMPv6: Sending echo request to 2A00:801:B::10
Aug 31 13:17:51.176: ICMPv6-ND: DELETE - INCMP: 2A00:801:B::10
Aug 31 13:17:51.176: ICMPv6-ND: Sending NS for 2A00:801:B::10 on 
GigabitEthernet4/0
Aug 31 13:17:52.176: ICMPv6-ND: Sending NS for 2A00:801:B::10 on 
GigabitEthernet4/0
Aug 31 13:17:53.176: ICMPv6-ND: Sending NS for 2A00:801:B::10 on 
GigabitEthernet4/0
Aug 31 13:17:54.176: ICMPv6-ND: INCMP deleted: 2A00:801:B::10

Linux machine also shows itself as being stale, but if I debug ICMP on
the cisco router, I can see that the linux machine is sending ICMP
packets to the cisco, and it's trying to respond but can't because the
nd is stale.

Weird thing is that tcpdump -p -n proto ipv6 doesn't show any packets,
tcpdump -p -n icmp doesn't show any ipv6 packets either, so I am
having a hard time troubleshooting this. Any ideas?

PS. It might be related to Networkmanager, because I don't have
Networkmanager in System-Administration to set up the IPv4 and IPv6
addresses in, so for IPv4 I'm having to kill off dhclient each time I
restart the network because networkmanager seems to think I should be
running dhcp on the interface. This might have some IPv6 implication as
well, I don't know.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
ipv6 stops working after a while
https://bugs.launchpad.net/bugs/263260
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 263260] Re: ipv6 stops working after a while

2008-08-31 Thread swmike
After I restarted networking (networking stop, ifconfig eth0 down,
networking start, kill dhclient) ipv6 worked for a few hours. now it
doesn't again:

[EMAIL PROTECTED]:~# ping6 2a00:801:b::1
PING 2a00:801:b::1(2a00:801:b::1) 56 data bytes
^C
--- 2a00:801:b::1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2013ms

The commands asked for:

[EMAIL PROTECTED]:# ip -6 n sh
2a00:801:b::1 dev eth0 lladdr 00:0a:42:dd:54:70 router REACHABLE
[EMAIL PROTECTED]:# ip -6 r sh
2a00:801:b::/64 dev eth0  proto kernel  metric 256  mtu 1500 advmss 1440 
hoplimit 4294967295
fe80::/64 dev eth0  proto kernel  metric 256  mtu 1500 advmss 1440 hoplimit 
4294967295
default via 2a00:801:b::1 dev eth0  metric 1  mtu 1500 advmss 1440 hoplimit 
4294967295
[EMAIL PROTECTED]:# ip -6 a sh
1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
3: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qlen 1000
inet6 2a00:801:b::10/64 scope global 
   valid_lft forever preferred_lft forever
inet6 fe80::240:63ff:fef5:17c2/64 scope link 
   valid_lft forever preferred_lft forever

On the cisco:
MikaelA7200Inf3#show ipv6 neighbors 
IPv6 Address  Age Link-layer Addr State Interface
FE80::240:63FF:FEF5:17C21 0040.63f5.17c2  STALE Gi4/0

MikaelA7200Inf3#debug ipv6 icmp 
ICMP packet debugging is on
MikaelA7200Inf3#
Aug 31 23:42:34.898: ICMPv6: Received echo request from 2A00:801:B::10
Aug 31 23:42:34.898: ICMPv6: Sending echo reply to 2A00:801:B::10
Aug 31 23:42:35.914: ICMPv6: Received echo request from 2A00:801:B::10
Aug 31 23:42:35.914: ICMPv6: Sending echo reply to 2A00:801:B::10
Aug 31 23:42:36.914: ICMPv6: Received echo request from 2A00:801:B::10
Aug 31 23:42:36.914: ICMPv6: Sending echo reply to 2A00:801:B::10
Aug 31 23:42:37.914: ICMPv6: Received echo request from 2A00:801:B::10
Aug 31 23:42:37.914: ICMPv6: Sending echo reply to 2A00:801:B::10
Aug 31 23:42:39.898: ICMPv6: Received ICMPv6 packet from 
FE80::240:63FF:FEF5:17C2, type 135
Aug 31 23:42:44.898: ICMPv6: Received ICMPv6 packet from 
FE80::240:63FF:FEF5:17C2, type 136

MikaelA7200Inf3#debug ipv6 nd 
ICMP Neighbor Discovery events debugging is on

Aug 31 23:43:47.158: ICMPv6-ND: DELETE - INCMP: 2A00:801:B::10
Aug 31 23:43:47.158: ICMPv6-ND: Sending NS for 2A00:801:B::10 on 
GigabitEthernet4/0
Aug 31 23:43:48.158: ICMPv6-ND: Sending NS for 2A00:801:B::10 on 
GigabitEthernet4/0
Aug 31 23:43:48.170: ICMPv6: Received echo request from 2A00:801:B::10
Aug 31 23:43:48.170: ICMPv6: Sending echo reply to 2A00:801:B::10
Aug 31 23:43:49.158: ICMPv6-ND: Sending NS for 2A00:801:B::10 on 
GigabitEthernet4/0
Aug 31 23:43:49.170: ICMPv6: Received echo request from 2A00:801:B::10
Aug 31 23:43:49.170: ICMPv6: Sending echo reply to 2A00:801:B::10
Aug 31 23:43:50.158: ICMPv6-ND: INCMP deleted: 2A00:801:B::10
Aug 31 23:43:50.158: ICMPv6-ND: INCMP - DELETE: 2A00:801:B::10
Aug 31 23:43:50.170: ICMPv6: Received echo request from 2A00:801:B::10
Aug 31 23:43:50.170: ICMPv6: Sending echo reply to 2A00:801:B::10
Aug 31 23:43:50.170: ICMPv6-ND: DELETE - INCMP: 2A00:801:B::10
Aug 31 23:43:50.174: ICMPv6-ND: Sending NS for 2A00:801:B::10 on 
GigabitEthernet4/0
Aug 31 23:43:51.170: ICMPv6-ND: Sending NS for 2A00:801:B::10 on 
GigabitEthernet4/0
Aug 31 23:43:51.170: ICMPv6: Received echo request from 2A00:801:B::10
Aug 31 23:43:51.170: ICMPv6: Sending echo reply to 2A00:801:B::10
Aug 31 23:43:52.154: ICMPv6: Received ICMPv6 packet from 
FE80::240:63FF:FEF5:17C2, type 135
Aug 31 23:43:52.154: ICMPv6-ND: Received NS for 2A00:801:B::1 on 
GigabitEthernet4/0 from FE80::240:63FF:FEF5:17C2
Aug 31 23:43:52.158: ICMPv6-ND: Sending NA for 2A00:801:B::1 on 
GigabitEthernet4/0
Aug 31 23:43:52.158: ICMPv6-ND: STALE - DELAY: FE80::240:63FF:FEF5:17C2
Aug 31 23:43:52.170: ICMPv6-ND: Sending NS for 2A00:801:B::10 on 
GigabitEthernet4/0
Aug 31 23:43:52.170: ICMPv6: Received echo request from 2A00:801:B::10
Aug 31 23:43:52.170: ICMPv6: Sending echo reply to 2A00:801:B::10
Aug 31 23:43:53.170: ICMPv6-ND: INCMP deleted: 2A00:801:B::10
Aug 31 23:43:53.170: ICMPv6-ND: INCMP - DELETE: 2A00:801:B::10

[EMAIL PROTECTED]:~# tcpdump -n -p not ip
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
23:44:48.300611 IP6 2a00:801:b::10  2a00:801:b::1: ICMP6, echo request, seq 1, 
length 64
23:44:49.313502 IP6 2a00:801:b::10  2a00:801:b::1: ICMP6, echo request, seq 2, 
length 64
23:44:50.313515 IP6 2a00:801:b::10  2a00:801:b::1: ICMP6, echo request, seq 3, 
length 64
23:44:51.313515 IP6 2a00:801:b::10  2a00:801:b::1: ICMP6, echo request, seq 4, 
length 64
23:44:52.313516 IP6 2a00:801:b::10  2a00:801:b::1: ICMP6, echo request, seq 5, 
length 64
23:44:53.297484 IP6 fe80::240:63ff:fef5:17c2  2a00:801:b::1: ICMP6, neighbor 
solicitation, who has 2a00:801:b::1, length 32
23:44:53.298330 IP6 2a00:801:b::1  

[Bug 150611] Re: swapper: page allocation failure. order:1 in ipv4 stack

2008-08-31 Thread swmike
I've now been running 2.6.27-2-generic for 36 hours and trying to put
some load on it, and haven't seen any hiccups yet. The problem still
exists in 2.6.24, but I guess it won't be fixed, and 2.6.26 and 2.6.27
both seem fine.

Let's close this and I'll re-open a new bug against 2.6.27 if I get
problems in the future.

-- 
swapper: page allocation failure. order:1 in ipv4 stack
https://bugs.launchpad.net/bugs/150611
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 158018] Re: 7.10 installation doesn't work with MSI NX7600GT

2008-08-30 Thread swmike
I just installed alpha4 again, and if I choose safe mode the
installation screen is all garbled but not garbled enough so that I
can't get thru the complete install. After reboot, X boots properly and
I get a 1280x1024 screen that is not garbled, but is not the correct
resolution either.

So it seems the alpha4 installer in safe mode does things that
subsequently installed X doesn't do (or the other way around).

-- 
7.10 installation doesn't work with MSI NX7600GT
https://bugs.launchpad.net/bugs/158018
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 158018] Re: 7.10 installation doesn't work with MSI NX7600GT

2008-08-30 Thread swmike
Sorry, when I say not the correct resolution, I have a 1920x1200
monitor and I only get 1280x1024 on it.

-- 
7.10 installation doesn't work with MSI NX7600GT
https://bugs.launchpad.net/bugs/158018
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 158018] Re: 7.10 installation doesn't work with MSI NX7600GT

2008-08-30 Thread swmike
After doing dist-upgrade and rebooting again with 2.6.27 kernel, I get
the identical garbled graphics as in the installer.

If I then install nvidia proprietary driver 177 I get good graphics and
acceleration is working.

-- 
7.10 installation doesn't work with MSI NX7600GT
https://bugs.launchpad.net/bugs/158018
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 243251] Re: via velocity induced kernel oops/crash

2008-08-29 Thread swmike
I will either re-install alpha4 and upgrade to 2.6.27 kernel or wait for
alpha5, depending on time during the weekend.

-- 
via velocity induced kernel oops/crash
https://bugs.launchpad.net/bugs/243251
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 158018] Re: 7.10 installation doesn't work with MSI NX7600GT

2008-08-28 Thread swmike
I just verified that the problem still occurs with 8.10 alpha 4,looks
like identical problem.

-- 
7.10 installation doesn't work with MSI NX7600GT
https://bugs.launchpad.net/bugs/158018
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 235074] Re: via velocity induced page allocation failure

2008-08-27 Thread swmike

I'm currently running a stock 2.6.26 from kernel.org with has proven itself 
stable:

Linux via 2.6.26 #1 SMP Mon Jul 14 08:07:27 CEST 2008 i686 GNU/Linux
 20:46:13 up 38 days, 23:12,  5 users,  load average: 0.76, 0.46, 0.28

So I guess intrepid should be stable since it's also based on 2.6.26.
I'm not really ready to run intrepid on this box due to it being alpha
software, so I can't verify myself.

-- 
via velocity induced page allocation failure
https://bugs.launchpad.net/bugs/235074
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 243251] Re: via velocity induced kernel oops/crash

2008-07-07 Thread swmike
I have been running a own-compiled 2.6.26-rc8 now for 6 days with
sometimes very heavy load and no oops or crash, so whatever the problem
is, it seems to be fixed in 2.6.26-rc8.

-- 
via velocity induced kernel oops/crash
https://bugs.launchpad.net/bugs/243251
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 243251] [NEW] via velocity induced kernel oops/crash

2008-06-26 Thread swmike
Public bug reported:

Binary package hint: linux-image-2.6.24-19-generic

Same hardware as in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/235074

Behaviour changed after upgrading to 2.6.24-19, now kernel crashes
(capslock+scroll lock flashes)

Kernel message:

[ 1303.400070] BUG: unable to handle kernel NULL pointer dereference at virtual 
address 0004
[ 1303.425667] printing eip: c02db82a *pde =  
[ 1303.440302] Oops: 0002 [#1] SMP 
[ 1303.449940] Modules linked in: isofs udf af_packet rfcomm l2cap bluetooth 
ppdev cpufreq_conservative cpufreq_stats cpufreq_ondemand cpufreq_userspace 
cpufreq_powersave freq_table dock container sbs sbshc video output battery 
iptable_filter ip_tables x_tables xfs sha256_generic aes_i586 dm_crypt ac 
max6650 padlock_sha padlock_aes blkcipher parport_pc lp parport snd_hda_intel 
snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_hwdep snd_seq_dummy 
snd_seq_oss snd_seq_midi snd_rawmidi evdev snd_seq_midi_event snd_seq snd_timer 
snd_seq_device snd soundcore ipv6 pcspkr i2c_viapro nvidia(P) agpgart i2c_core 
button shpchp pci_hotplug ext3 jbd mbcache usbhid hid sg sr_mod cdrom sd_mod 
pata_acpi via_rhine mii ehci_hcd via_velocity crc_ccitt uhci_hcd pata_via ahci 
ata_generic usbcore libata scsi_mod raid10 raid456 async_xor async_memcpy 
async_tx xor raid1 raid0 multipath linear md_mod dm_mirror dm_snapshot dm_mod 
thermal processor fan fbcon tileblit font bitblit softcursor fuse
[ 1303.707275] 
[ 1303.711703] Pid: 0, comm: swapper Tainted: P(2.6.24-19-generic #1)
[ 1303.732217] EIP: 0060:[c02db82a] EFLAGS: 00010246 CPU: 0
[ 1303.748586] EIP is at tcp_ack+0x39a/0x1d90
[ 1303.760797] EAX:  EBX: f54c6600 ECX: 0001 EDX: 
[ 1303.779495] ESI: f63bf300 EDI: 0001 EBP: f54c6620 ESP: c041dc9c
[ 1303.798192]  DS: 007b ES: 007b FS: 00d8 GS:  SS: 0068
[ 1303.814296] Process swapper (pid: 0, ti=c041c000 task=c03ea3a0 
task.ti=c041c000)
[ 1303.835848] Stack:  0003 c04df674 f6bc07e0 c03ea3a0 0092 
f63bf380  
[ 1303.860870]0401 f5583cc0   0001 f6bc07e0 
280229ca 21d311de 
[ 1303.885897]28022bc8  004d    
0001 c0b87577 
[ 1303.910921] Call Trace:
[ 1303.918828]  [c02e04d7] tcp_rcv_established+0x587/0x930
[ 1303.934948]  [f8913d20] velocity_intr+0x60/0x680 [via_velocity]
[ 1303.953167]  [c031c338] _read_lock_bh+0x8/0x20
[ 1303.966952]  [f8c366cb] ipt_do_table+0x20b/0x4b0 [ip_tables]
[ 1303.984382]  [c02e7000] tcp_v4_do_rcv+0x340/0x6e0
[ 1303.998950]  [c02c8909] ip_route_input+0x39/0xdf0
[ 1304.013548]  [c0146ce4] getnstimeofday+0x34/0xe0
[ 1304.027864]  [f8c32080] ipt_hook+0x0/0x20 [iptable_filter]
[ 1304.044774]  [c02e9bed] tcp_v4_rcv+0x7bd/0x9a0
[ 1304.058596]  [c02cb809] ip_local_deliver_finish+0xf9/0x210
[ 1304.075505]  [c02cb49f] ip_rcv_finish+0xff/0x370
[ 1304.089818]  [c021871f] strlcpy+0x1f/0x60
[ 1304.102314]  [f8c9645a] packet_rcv_spkt+0x2a/0x1a0 [af_packet]
[ 1304.120257]  [c02a3d55] __alloc_skb+0x55/0x120
[ 1304.134045]  [c02cba10] ip_rcv+0x0/0x290
[ 1304.146276]  [c02a8fb9] netif_receive_skb+0x379/0x440
[ 1304.161895]  [c02ab9b5] process_backlog+0x75/0xe0
[ 1304.176471]  [c02ab38d] net_rx_action+0x12d/0x210
[ 1304.191059]  [c0131d72] __do_softirq+0x82/0x110
[ 1304.205118]  [c0131e55] do_softirq+0x55/0x60
[ 1304.218384]  [c013213d] irq_exit+0x6d/0x80
[ 1304.231127]  [c0106f20] do_IRQ+0x40/0x70
[ 1304.243359]  [f8960900] ata_down_xfermask_limit+0x150/0x1f0 [libata]
[ 1304.262893]  [c0105413] common_interrupt+0x23/0x30
[ 1304.277716]  [c0102f40] default_idle+0x0/0x60
[ 1304.291258]  [c011ec62] native_safe_halt+0x2/0x10
[ 1304.305825]  [c0102f7c] default_idle+0x3c/0x60
[ 1304.319604]  [c0102695] cpu_idle+0x45/0xd0
[ 1304.332355]  [c0421a5f] start_kernel+0x31f/0x3b0
[ 1304.346658]  [c0421130] unknown_bootoption+0x0/0x1e0
[ 1304.362022]  ===
[ 1304.372673] Code: 83 4c 24 7c 04 8b 44 24 74 85 c0 0f 84 71 03 00 00 8b 44 
24 18 83 68 08 01 8b 43 04 8b 13 c7 43 04 00 00 00 00 c7 03 00 00 00 00 89 42 
04 89 10 8b 43 50 05 b0 00 00 00 3b 83 a8 00 00 00 0f 8f 
[ 1304.429719] EIP: [c02db82a] tcp_ack+0x39a/0x1d90 SS:ESP 0068:c041dc9c
[ 1304.449523] Kernel panic - not syncing: Fatal exception in interrupt

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
via velocity induced kernel oops/crash
https://bugs.launchpad.net/bugs/243251
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 243251] Re: via velocity induced kernel oops/crash

2008-06-26 Thread swmike

** Attachment added: bootup log and crash message (from serial console)
   http://launchpadlibrarian.net/15624197/via-080626-1.log

-- 
via velocity induced kernel oops/crash
https://bugs.launchpad.net/bugs/243251
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 235074] Re: via velocity induced page allocation failure

2008-05-27 Thread swmike
$ lspci
00:00.0 Host bridge: VIA Technologies, Inc. P4M900 Host Bridge
00:00.1 Host bridge: VIA Technologies, Inc. P4M900 Host Bridge
00:00.2 Host bridge: VIA Technologies, Inc. P4M900 Host Bridge
00:00.3 Host bridge: VIA Technologies, Inc. P4M900 Host Bridge
00:00.4 Host bridge: VIA Technologies, Inc. P4M900 Host Bridge
00:00.5 PIC: VIA Technologies, Inc. P4M900 I/O APIC Interrupt Controller
00:00.6 Host bridge: VIA Technologies, Inc. P4M900 Security Device
00:00.7 Host bridge: VIA Technologies, Inc. P4M900 Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
00:02.0 PCI bridge: VIA Technologies, Inc. P4M900 PCI to PCI Bridge Controller 
(rev 80)
00:03.0 PCI bridge: VIA Technologies, Inc. P4M900 PCI to PCI Bridge Controller 
(rev 80)
00:0f.0 SATA controller: VIA Technologies, Inc. SATA RAID Controller (rev 20)
00:0f.1 IDE interface: VIA Technologies, Inc. 
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 07)
00:10.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 
Controller (rev 91)
00:10.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 
Controller (rev 91)
00:10.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 
Controller (rev 91)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 90)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8251 PCI to ISA Bridge
00:11.7 Host bridge: VIA Technologies, Inc. VT8251 Ultra VLINK Controller
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 7c)
00:13.0 Host bridge: VIA Technologies, Inc. VT8251 Host Bridge
02:00.0 VGA compatible controller: nVidia Corporation G70 [GeForce 7600 GT] 
(rev a1)
03:00.0 Ethernet controller: VIA Technologies, Inc. VT6120/VT6121/VT6122 
Gigabit Ethernet Adapter (rev 82)
80:00.0 PCI bridge: VIA Technologies, Inc. VT8251 PCIE Root Port
80:00.1 PCI bridge: VIA Technologies, Inc. VT8251 PCIE Root Port
80:01.0 Audio device: VIA Technologies, Inc. VIA High Definition Audio 
Controller

-- 
via velocity induced page allocation failure
https://bugs.launchpad.net/bugs/235074
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 150611] Re: swapper: page allocation failure. order:1 in ipv4 stack

2008-05-27 Thread swmike
Could it be related to:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/235074

If it is, then it's confirmed for Hardy.

-- 
swapper: page allocation failure. order:1 in ipv4 stack
https://bugs.launchpad.net/bugs/150611
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 158018] Re: 7.10 installation doesn't work with MSI NX7600GT

2008-02-04 Thread swmike
Here is the lspci information:

The MSI 7600GT with HDMI:

01:00.0 VGA compatible controller: nVidia Corporation G70 [GeForce 7600 GT] 
(rev a1) (prog-if 00 [VGA])
Subsystem: Micro-Star International Co., Ltd. Unknown device 0690
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at e400 (32-bit, non-prefetchable) [size=16M]
Memory at d000 (64-bit, prefetchable) [size=256M]
Memory at e500 (64-bit, non-prefetchable) [size=16M]
I/O ports at 7000 [size=128]
[virtual] Expansion ROM at e600 [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 
Enable-
Capabilities: [78] Express Endpoint IRQ 0

the 6200LE:

01:00.0 VGA compatible controller: nVidia Corporation NV44 [GeForce 6200 LE] 
(rev a1) (prog-if 00 [VGA])
Subsystem: ASUSTeK Computer Inc. Unknown device 8205
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at e400 (32-bit, non-prefetchable) [size=16M]
Memory at d000 (64-bit, prefetchable) [size=256M]
Memory at e500 (64-bit, non-prefetchable) [size=16M]
[virtual] Expansion ROM at e600 [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 
Enable-
Capabilities: [78] Express Endpoint IRQ 0

The ASUS 7600GT:

01:00.0 VGA compatible controller: nVidia Corporation G70 [GeForce 7600 GT] 
(rev a1) (prog-if 00 [VGA])
Subsystem: ASUSTeK Computer Inc. Unknown device 81f7
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at e400 (32-bit, non-prefetchable) [size=16M]
Memory at d000 (64-bit, prefetchable) [size=256M]
Memory at e500 (64-bit, non-prefetchable) [size=16M]
I/O ports at 7000 [size=128]
[virtual] Expansion ROM at e600 [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 
Enable-
Capabilities: [78] Express Endpoint IRQ 0

-- 
7.10 installation doesn't work with MSI NX7600GT
https://bugs.launchpad.net/bugs/158018
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 158018] Re: 7.10 installation doesn't work with MSI NX7600GT

2008-01-17 Thread swmike
I tried two different 7600GT based cards, the ASUS one with 2xDVI works
ok, the MSI one with 1xDVI and 1xHDMI does not (looks the same as with
7.10)

Everything looks ok in the installer (the livecd I guess it should be
called) until X is started, then the graphics is garbled.

I have made a youtube video of the video startup (at the start black
screen when I just killed the X server by ctrl-alt-backspace) just to
indicate what kind of garbleness it is. It can be seen at
http://www.youtube.com/watch?v=LoKyth4pdK8

-- 
7.10 installation doesn't work with MSI NX7600GT
https://bugs.launchpad.net/bugs/158018
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


  1   2   >